← Features

Imports

The one door for everything the site already has on paper or in another system — each contractor's programme, the drawing office's floor plans, survey layers, a bulk restore, and the contractual defect register.

Very little about a construction site starts life in SimOps. The programme is in P6, the floor plans are in the drawing office's CAD, the survey is a shapefile, and the defect register lives in whatever system the contract names. The Imports panel (Z) is the single place those things come in — a stack of source cards, each opening its own workflow in place.

What comes in

  • Floor plans (DXF). A CAD drawing becomes a per-building, per-level Floor plan — rendered as native vector by default, with raster as the fallback.
  • Programmes. A contractor's P6 .xer export, native Asta Powerproject .pp file, or .pdf print, read into work lines and the links between them.
  • Reference layers. A shapefile or GeoJSON landing as a static reference layer — buildings, zones, roads: the Reference features the rest of the app reasons about.
  • Site data. A SimOps GeoJSON or CSV export restored back into a site: workers, plant, areas, roving crews, deliveries, points of interest, text labels and reference features.
  • Defects. A per-contractor export of the contractual quality register (see Defects).

Most cards answer to the manage-any band (entity_manage_any) — importing is a site-shaping act. Reference layers additionally sit on layer_manage, the programme's write verbs on work_plan_manage, and the defects card is capability-derived from defect_view / defect_import so a contractor who may read their own register sees the card without being handed the upload.

Bulk import: look before you commit

A bulk file is never applied on sight. Upload runs a dry run first, which parses the whole file and reports every row into one of four buckets — valid, warning, error, or skipped (kinds SimOps deliberately declines to rebuild from an export, like casework and stock). You read the preview, exclude what you don't want, and only then commit. Nothing is written until you do, and the prepared import is consumed on commit, so a double-submit is refused rather than duplicated.

The programme: one door, and every activity is a line

A Programme is one contractor's plan as handed over in a file — a durable, site-scoped identity, never itself a file. Each handed-over file lands under it as an immutable Programme revision, and the revision's work breakdown, activities and logic are kept as the record of what that file said (Staging). There is no curation step after that: every task and milestone in the file becomes a Work line the moment the ingest finishes, under the file's own headings, and every relationship between two of them becomes a Work dependency.

The upload form asks one question first — New programme, or An update to an existing one? — and never guesses. A new programme names its contractor (required: a programme speaks for one contractor, even when it describes others' work) and may name itself; left blank, the first good ingest names it from the file. The rev label is optional and prefilled from the file. An update picks the programme it updates, and never renames it. When the file is read, the uploader gets one summary — "Eldon Industrial programme · 1,240 lines · 1,860 links · 4 dropped" — and if a programme's first file fails, it reads failed and offers Upload again.

What a revision was read from is carried on its face, because fidelity differs — a P6 XER export and a native Powerproject file both carry full logic, while a PDF print is degraded: lines and dates only, day-precision, and blind to logic. The badge says which, so nobody reads a PDF's silence as evidence of absence.

A programme update applies itself

When the next revision arrives, uploading it is the attended act: a Programme update applies as the ingest's last step. The file owns what the file says — each imported line takes its activity's name, code and printed dates (read-only on the line), new activities become lines, and the imported links become the file's relationships. The site owns what the site made — tokens, a line's place, evidence, hand-drawn links. A line whose activity has left the file is deleted when it carries nothing of the site's, and kept as an Orphaned line under "No longer in the programme" when it does. Status follows the file until the site touches the line. The summary names what moved ("+12 lines · 340 dates moved · 3 gone"), and opens with "Wrong file?" when more than half the lines went; the latest update can be undone from the programme's header. A PDF update never deletes a line and never touches links (Logic pointer). Undoing an update whose previous revision is a PDF still takes the undone file's links back: the imported links become those of the newest earlier revision that carries logic, or none if there is no such revision. Hand-drawn links are never touched.

Where the programme lives

This card is the door and the history, read-only: the site's programmes (name, contractor, latest rev and data date, standing), where the selected programme reads once: its row opens in place into its revision history with its fidelity and ingest badges. The upload form sits above the list and the files the programme could not read below it. A programme's name opens it on the Plan Gantt in the Work home (W), where its lines already are — and where its verbs live, on the programme header's ⋯ menu: upload an update, rename, change contractor, undo this update, delete. The same form opens from the Gantt's + Programme. A late line carries its slip there as a dashed tail to its expected finish (Slip chip), amber within the site's slip threshold and red beyond it, derived at read time and never stored.

Two planners, one door: P6 and Powerproject

Not every programme is a P6 programme. A main contractor planning in Asta Powerproject hands over a .pp file, and that file goes through the same door as an XER — you upload it as a new programme or an update exactly as you would an export, and it lands as a revision badged Powerproject.

A .pp is a second full-fidelity format, not a degraded one. It carries the same things an XER does: every activity and milestone, the work-breakdown bands, the target and scheduled dates, actual starts and finishes, durations, calendars, the activity-code libraries, and the whole logic network with its lag — so a .pp revision mints its lines and links and updates like any other, and its update moves both the current revision and the logic basis. Mixing formats across revisions is an ordinary update: an XER after a .pp, or a .pp after an XER, reads as changes, not as a fresh start.

Three things a Powerproject file does not carry, and no amount of reading will find them:

  • late dates — the backward pass a P6 export brings with it,
  • total float, and
  • the critical path flag, unless the planner happened to have longest-path display switched on when they saved.

They are absent because the file does not hold them, not because the import lost them: SimOps shows a — rather than inventing a number. The badge's tooltip says exactly this on every .pp revision.

When a file is refused

Unreadable bytes are refused at the door, before anything is created — upload a spreadsheet or a Word document and you get "not a programme SimOps can read" and no revision row to clean up. A file that is a Powerproject database but cannot be turned into a programme lands as a failed revision that names why, in the refused-row list under the revision list:

What happened What to do
The file is password-protected Re-save it from Powerproject without a password.
It was written by a Powerproject version SimOps cannot read Re-save it from a supported version, or send a P6 XER export instead.
It holds more than one project Split it so each uploaded revision carries a single project.
It stages no activities Check the programme chart was actually saved into the file.

An XER has the same shape of refusal: a file that says it is an XER but carries no project, WBS or activity tables fails with "no programme tables", and wants re-exporting from P6.

The fallback

A Powerproject seat can also export a P6 XER, and that export lands through this door today with nothing new to configure. It is the fallback rather than the road, because the export flattens things on the way out — codes, lags and baselines are pre-folded, and it adds a per-revision dialog somebody has to remember to drive. Send the .pp where you can.

What deliberately isn't here

Permit XLSX import is not an Imports card. It moved to the permits board, where the permits it creates live — see Configuring permits.

In a demo world the DXF import is read-only. The card is visible — you can walk up to the door and see what it does — but its action is locked with a "read-only in the demo sandbox" marker, and the import route itself refuses outright, because the raster pipeline is disabled there for memory safety. A deliberate carve-out, not a bug: on a demo site the door can be shown, never opened.

See it / try it

Where to go next

Was this page useful? Report a problem

No cookies and no third-party analytics. A verdict records this page's path — and a search that finds nothing records the words you typed — in this site's own server log.

Generated from source · SimOops living system reference