CRIAD
Owners and operators · Use case 04

Check once, repeat on every site

Every campus repeats the last one. Every project team still checks it again by hand.

Your campuses repeat: your project knowledge should too. Every element is linked to its drawing, spec, order and status, so a check written on one site re-runs on the next.

Book a callSee the platform

Every answer cites its source. People decide.

How it works

Ask. Inspect. Verify. Publish.

1

Ask

A plain-language question.

"Do the racks in every hall fit the envelope in the spec?"
2

Inspect

The full blast radius, on the model.

Every rack on the campus, by hall, with the ones that fail shown on the model.
3

Verify

Checked against the governing drawings and specs.

Each rack is measured on real geometry against the limit in the governing spec clause.
4

Publish

A dashboard, report or register, citations attached.

A campus check report, clause and measurement attached. The same check is ready to run on the next site.
Worked example

One job, start to finish.

Values come from a structured reference campus, not from a client project.

Reference campus
  1. 01

    Reference campus: rack envelope limit 0.60 x 1.20 x 2.00 m, from the spec.

  2. 02

    240 racks per hall, 1,440 on campus, each one measured.

  3. 03

    The check is written once.

  4. 04

    On site 2 the files come in as they are and the same check runs again.

SITE 1 · STRUCTURED

HALL 1✓
HALL 2✓
HALL 3✓
HALL 4✓
  1. 1Ingest as issued: model, 152 sheets, specs
  2. 2Link: element → drawing · spec · order · status
  3. 3Verify: by authority, measured on geometry

One campus, fully structured

SITE 2

same checks · re-run ✓

SITE 3

same checks · re-run ✓

SITE N

same checks · re-run ✓

Knowledge compounds across the fleet

OPERATIONS · FROM DAY ONE

> which rack is this?

✓ schedule row, spec, approvals attached

> what serves it?

✓ rack ← distribution frame ← fibre entry

> still under warranty?

✓ O&M row and warranty on record

The record stays live and queryable for decades

example queries from a structured reference campus

Platform capabilities used

The same capabilities serve every segment. Each one links to its section.

Previous use caseProgress you can audit
Next use caseApprove a change with every knock-on in view
Back to Owners and operators

Stop waiting. Start building.

Book a call with the founders. Thirty minutes, your questions, and what Criad looks like on a data centre build.

Book a call