Early access is open. Bring one real project and we will build its breakdown, vocabulary and workflow live in the session. Request a demo →
Data centres · Starter pack shipped
Multi-stage colour-tag flows, high client scrutiny, and repeated builds where blueprint reuse compounds with every hall. Register a CRAH unit and its airflow, loop-check and IST records exist before anyone opens a laptop.
1,920
Generated automatically on registration
Cairn OS is for work that has to be proven, not just reported. A project is broken down into every individual item it contains. Each item carries the records that prove it reached each stage, and each record carries who signed it and when.
The engine holds no vocabulary of its own. You define what your levels, items, records and stages are called, and every screen, dashboard and export uses your words. That is how one system fits any project shape without being rebuilt for it, and how progress, sign-off and traceability end up in one place rather than three.
That is the whole argument. Change the vocabulary and every screen, dashboard and export follows, because the shape of the data never depended on the words in the first place.
| Tag | Equipment Type | Sub-system | System | ITR | Stage | Status |
|---|---|---|---|---|---|---|
| MSB-01-A | SWITCHBOARD | LV DISTRIBUTION | ELECTRICAL | ITR-04 INSULATION | FUNCTIONAL | SIGNED |
| CRAH-03-12 | CRAH UNIT | HALL 3 COOLING | MECHANICAL | ITR-11 AIRFLOW | START-UP | IN PROGRESS |
| UPS-02-B | UPS | CRITICAL POWER | ELECTRICAL | ITR-07 LOAD BANK | FUNCTIONAL | VERIFIED |
| FA-L2-118 | FIRE DETECTOR | LEVEL 2 DETECTION | FIRE SYSTEMS | ITR-02 POINT TEST | QA-QC | ISSUE |
| PDU-03-07 | PDU | HALL 3 POWER | ELECTRICAL | ITR-05 POLARITY | INSTALLED | OPEN |
| CHW-P-04 | PUMP | CHILLED WATER | MECHANICAL | ITR-09 FLOW RATE | START-UP | IN PROGRESS |
Demonstration data · in data centres vocabulary
Everything is configuration, not code: your vocabulary, your breakdown, your stages, your forms. No single industry's workflow is hard-wired in.
Systems and sub-systems, phases and plots, hulls and blocks, claims and bundles: every level, item and record wears the words your teams already use. Change the vocabulary, not the product, and every screen, dashboard and export follows.
Two levels or seven, Cairn OS does not care. Build the tree your project actually has, register items at any node, and completion rolls up every branch to the top. Add a secondary classification axis (areas, disciplines, work packs) and slice progress across it.
Run pre-construction and build stages side by side, or a different process per phase of the project. Each branch resolves its own workflow. Gates hold the next stage closed until the threshold you set is met, and stamped waivers keep accepted risk on the record.
The equipment type is the hub. Register an item and Cairn OS reads your matrix and generates its data sheet and every inspection record it needs, stage by stage. Forms are versioned immutably, validated server-side, and signed against the specific tag.
Completion, blockers, skylines and the S-curve, computed from a read model that updates the moment a record is signed. No overnight batch, no “as of last Friday”. Drill from the whole project down to a single signature.
Photos, installed components and signatures attach to the tag and the record, not to a folder. When a system is ready, the handover pack and certificate assemble themselves from records that were complete all along.
Define your breakdown tree at whatever depth fits, name every level in your own vocabulary, and set the stages your process moves through: installed, inspected, tested, energised, commissioned, or whatever yours are called. Start from a blank sheet, a starter pack, or a blueprint exported from a previous project.
For each equipment type, pick the data sheet that captures its attributes and the ITRs that apply at each stage. The matrix is the single decision point: get it right once and every registration after that is automatic.
Register tags one by one or import thousands in bulk, with row-level validation before anything is committed. Every tag arrives with its data sheet and its full set of ITR shells already generated. Field engineers fill, photograph, and sign; context fields like project, unit and stage fill themselves.
Every signature recomputes completion up the tree, re-evaluates your gates, and updates every dashboard. Blockers surface themselves. Punch items are tracked to closure. When the last record on a system is signed, handover is a button, not a project.
Every dashboard reads from a live model that updates the moment a record is signed. Drill from any number on any chart down to the tag, the record and the signature behind it.
Project completion
63.4%
8,142 of 12,480 records signed
Skyline
What is blocking progression
Demonstration project. Cairn OS, project overview.
Every form is versioned immutably: publish a new revision and in-flight records stay on theirs, so an audit never finds a moving target. Validation runs on the server. Every answer is projected into a queryable shape, so dashboards read real data, not attachments.
ITR-09 · FLOW RATE VERIFICATION
CHW-P-04 · CHILLED WATER · REV 3
Flow readings
| # | Point | Design l/s | Actual l/s | Dev |
|---|---|---|---|---|
| 1 | Header A | 42.0 | 41.6 | -1.0% |
| 2 | Header B | 42.0 | 39.1 | -6.9% |
| 3 | Bypass | 12.0 | 12.2 | +1.7% |
Mean deviation −2.1% · calculated
Demonstration record. Cairn OS, forms and ITR engine.
Yes. Nothing about any single industry is hard-coded. The breakdown depth, the names of every level, the stages, the record types and the forms are all configuration. Cairn OS runs housing developments, data centres, vessels and process plants with equal comfort, because to the engine they are all the same thing: a tree of items moving through your stages.
The difference is the matrix and the roll-up. Cairn OS does not just host forms: it knows which records every item needs, generates them on registration, and recomputes project completion the moment one is signed. The paperwork and the progress reporting are the same data, so they cannot disagree.
Yes, and you do not have to rebuild them by hand. Upload a photo or PDF of your current paper form and the AI builder reconstructs it as a live digital form with validation and conditional logic, ready for your review before anything is published.
Nothing, and that is the point. Form versions are immutable once published. Records already underway stay on the version they started on; new records use the new version. Audits see exactly what was signed, as it was signed.
The import validates every row and reports the errors before anything is committed. You fix the file, not the database.
Yes. External reviewers get read-only access scoped to their project through a separate API, using keys you issue, scope and revoke. They can review records, evidence and progress, and their review actions are captured, but they cannot alter the record.
In Microsoft Azure, isolated per tenant, with evidence in Azure Blob Storage. You can export registers and reports at any time, export whole project blueprints for reuse, and higher tiers add the Power BI feed and scheduled exports into your own storage.
No surprises: AI is metered per call, every call is visible in your usage ledger, and allowances are bundled per tier with clear overage. You will always know what you used and what it cost.
Bring one real data centre project. In one session we build its breakdown, its vocabulary and its workflow live, and you watch a tag go from registered to signed with the dashboard moving behind it.
Request a demo →No seats to count during early access · trycairn@cairn-os.com