datum

Product · Delay analysis

The days come from the network, never from a model.

datum reparses the Primavera XER, recomputes the critical path deterministically, and links confirmed events to the activities they hit. Anomalies in the schedule are reported, not silently trusted.

A CPM engine, not an opinion

Forward and backward pass, per-activity calendars, lags and constraints - recomputed from the file and compared against it, with every delta reported. Real-world schedule mess (orphan logic, negative lags) is recorded, never crashed on.

CPM · forward/backward pass
A1020 Substructure
A1080 Light Wall procurement
A1140 Envelope close-in
A1200 Fit-out zone C

Critical path in accent. Float, lags and calendars computed by code - never by a model.

Causation you can defend

Each confirmed event links to the schedule activities it affected, and the impact in days comes from the network. Where a linkage cannot be established, the claim says exactly that - datum never bridges an evidential gap with prose.

Linkage · event to impact
02 Feb 2006 · late instructionA1080 Light Wall procurementcritical path · days computed

If a linkage cannot be established, the claim says so - it never bridges the gap with prose.

Honest inputs, honest outputs

The analysis states its basis: which schedule versions, which confirmed events, which windows. Anything uncertain is flagged for your planner rather than absorbed into a number.

Record health
153 documents read, OCR'd and indexed
2 poor scans flagged for manual review
0 unreadable files · 0 uncertain dates

Flagged documents are excluded from confidence claims until resolved.

See it on your own matter. Pilots run on a real record, with your reviewers in command.

Request a pilot