IFC / BIM ingestion
IFC semantic ingestion with IfcOpenShell, and a transparent fallback parser that labels its own reduced fidelity rather than hiding it.
Connect geometry, schedule, evidence and intelligence to understand the project in space, time and context — and to see where it is heading.
Drag to orbit
ROOF-B-023 · Connection plate install
Compare baseline, actual progress and a forecast range built from reconciled actuals rather than reported ones.
Interactive illustration — drag the data date to see how a forecast cone responds.
Every answer is constructed from records you can open. Where evidence is missing, the Twin says so instead of producing a plausible sentence.
Every claim below is built from records, not retrieved text. Open one to see the source.
Roof Zone B is 4 days behind baseline and has consumed its float. Two causes account for most of the variance, and a third is adding to it.
Crane unavailability on 15 August cost a full shift of steel erection.
A partial connection-plate delivery on 16 August left the crew short of 42 units, with the balance not due until 24 August.
Rework on six under-torqued connections is adding an estimated 1.5 days.
The activity is now critical, with two successors exposed.
Why this confidence: Four independent records, three of them primary sources, all within the variance window. No contradicting evidence found.
The product reports these fields on every answer. This demo shows the same ones.
IFC semantic ingestion with IfcOpenShell, and a transparent fallback parser that labels its own reduced fidelity rather than hiding it.
IFC converted to GLB and 3D Tiles 1.1, with LOD0/1/2 and Cesium spatial streaming for models too large to load whole.
Conversion runs as partitioned jobs with worker leases, cancel and resume, and a content-addressed cache that skips work already done.
Activities bound to entities, with baseline, actual and forecast state per element, and an S-curve derived from the schedule itself.
A portfolio view across projects and a side-by-side comparison workspace, not just a single-project dashboard.
Observations, recommendations, approvals and executions written to a hash-chained log, with an endpoint that re-walks the chain and reports the first break.
Live project events over WebSocket with Redis fan-out across replicas, and a cached shell that keeps working offline, queueing comments until reconnect.
BM25 retrieval over project records, derived claims, verified citations, and an enforced downgrade when nothing matches.
P10/P50/P90 computed from measured activity slippage, each result reporting its model, sample size and calibration state.