The gap in the project controls stack
A typical project controls environment has a scheduling engine, a cost system, a progress measurement tool and a reporting layer. Every one of those depends on an activity network that a planner produced manually from drawings and models. On a plant with thousands of items that is weeks of work, it is difficult to audit, and it has to be redone whenever the model is revised.
- Scheduling tools schedule an activity network; they do not create one from engineering data.
- 4D tools animate an existing schedule against a model rather than deriving the sequence from it.
- Progress and cost systems inherit whatever logic the original planner applied, correct or not.
- Two planners given the same model produce two different sequences, so the baseline is not reproducible.
What Sensali does in that stack
| Stage | Input | Output |
|---|
| Extract geometry | Navisworks model (NWD/NWC) | Item hierarchy, containment and connectivity |
| Standardise engineering data | Model properties and project documentation | Consistent discipline, tag and attribute set |
| Identify process areas | Standardised item set | Every item assigned to a physical process area |
| Generate construction sequence | Process areas and methodology rules | Dependency-correct activity network |
| Export Primavera P6 | Activity network with durations and resources | XER file ready to import |
Evidence rather than claims
Process area assignment, which is what makes area gating possible, has been measured at 98.8% accuracy against engineering documentation on the models processed so far. 264,000 hours of construction work have been run through the pipeline. Durations and crew sizes are taken from project engineering and staffing data at a 1:1 basis rather than estimated, so the resulting network can be compared directly against a manually produced baseline.
Who it is for
- Asset owners who need clear visibility into construction schedules and project risk.
- Oil and gas majors and mining companies funding capital projects.
- Infrastructure and heavy industrial owners managing capital project risk.
- Owner teams reviewing schedule logic against project data and 3D models.
The owner's independent layer
Sensali gives asset owners a consistent basis for understanding project scope, reviewing construction sequences and assessing schedule risk. Traceable data, inspectable reasoning and owner held evidence support your project controls team without adding a large manual checking workload.
Organised Project Data
Messy equipment lists, norms, line lists, 3D models and disconnected spreadsheets become one structured canonical dataset. Every value carries provenance to its exact source file. Assumptions are disclosed, not hidden.
MDN: Minimum Data Needed
A live checklist exposes missing or incomplete data before the schedule is built and tells the owner what is needed. Standard norms can be used where client rates are unavailable. Inputs, assumptions and standard values stay visible and editable.
Independent Schedule Generation with Cited Reasoning
Sensali derives the schedule from underlying project data, giving asset owners an inspectable basis for planning. Each activity's sequencing and duration has inspectable cited reasoning from engineering logic, client historical data or geometry derived facts.
4D Simulation of Schedule (Beta)
The independently generated schedule is animated over the real project model so the owner can visually review whether the installation sequence is physically plausible.
Evidence PDF
Export a citation backed audit record for one activity or the whole schedule. The owner holds the reasoning and supporting sources independently for schedule disputes, delay claims and audits.
P6 Schedule Comparison
Upload an existing P6 schedule and compare it with the generated version. Review differences in sequencing and durations, with their planning implications explained in plain English to support project reviews and decisions.
Confidentiality
An NDA is available before any model or project data is shared, project data is never reused between customers, and deployment inside customer-controlled environments is supported.
Where to go next
The full pipeline is described on Navisworks to Primavera P6, the sequencing rules on construction sequencing automation, and the export format on Primavera P6 XER export.