It understands the project,
not just the schedule.
Activities, documents, obligations, events, evidence, and people — one connected model, of which the schedule is one view.
The schedule is a view,
not the model.
Activities, documents, obligations, events, evidence, and people live in one connected graph — the programme is its temporal representation, not its boundary.
The contract's rules,
held as facts.
An event arms a rule, a deadline clock starts for the responsible party — the contract's conditional requirements, held where the schedule can watch them.
- Event
- The occurrence that arms the rule — a certificate issued, an instruction given.
- Rule
- What the contract requires once the event has happened.
- Clock
- The deadline running from the event. Clocks monitor; they never move CPM dates.
- Party and evidence
- Who owes the obligation, and the document that proves it.
The delay narrative,
already assembled.
Every event that changed a date, in order, with its actor, source, and evidence — exportable as the chronology a claims consultant can cite, without months of reconstruction.
Drift and the party responsible
Headline forecast against baseline, per-area variance, open obligation clocks, blockers with the responsible party named, and a digest of what changed — one surface, always computed.
Control surface — drift, blockers, digest, inbox
The project's current state, computed from the model rather than reported into it.
2880 × 1800
Access follows
the WBS.
Roles scope to the EPS and WBS, every change writes to an immutable audit trail, and each company's data is isolated at the infrastructure layer.
- Roles and scopes
- A permission applies where you grant it — a node, a project, a subtree.
- Audit trail
- Every audited operation recorded with its actor and time.
- Tenant isolation
- Enforced below application code, not by a query filter.