CRIAD
Integrators and OEMs · Use case 03

Factory against site revisions

The site drawing moved after the factory drawing was frozen. We found out at delivery.

Factory drawings and site drawings are connected to the same elements. When either side issues a revision, the elements it touches are flagged, and the other side sees it before the unit ships.

Every answer cites its source. People decide.

How it works

Ask. Inspect. Verify. Publish.

1

Ask

A plain-language question.

"A site revision just landed. Does it touch anything we are building?"
2

Inspect

The full blast radius, on the model.

The elements drawn on the revised sheet, with the factory drawings that describe the same elements.
3

Verify

Checked against the governing drawings and specs.

The new revision is compared with the last, and the changed elements are checked against the factory drawing and the spec.
4

Publish

A dashboard, report or register, citations attached.

A change notice per affected unit: what moved, which factory drawing it touches, sources cited.
Worked example

One job, start to finish.

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

Reference campus
  1. 01

    The telecom layout on the reference campus goes from rev 1 to rev 2.

  2. 02

    Every rack drawn on that sheet is flagged.

  3. 03

    Factory drawings that describe those racks are listed against the change.

  4. 04

    Your engineer sees it while the unit is still in the factory.

Telecom layoutrev 1
ABC0.60 m

illustrative example

What rev 2 touches

  • Rack row C moved 0.60 m
  • 12 racks affected
  • Install plan: 1 package to re-sequence
  • Who needs to know: 3 trades

Flagged before anyone builds to the old sheet.

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