What ships should match what was designed.
Racks, power and cooling skids, prefabricated modules, switchgear, controls and security systems: if you build it off site and it has to fit, connect and be approved on site, the documents have to agree. Criad keeps your factory drawings, the site drawings, the spec and the model in one connected record. Open specs such as Open Rack V3 (ORv3) and the Project Deschutes CDU specification load as documents, so each check cites a clause your customer already knows.
Where the slot goes
Your equipment is built weeks before the site is ready for it. If the site drawing moves after the factory drawing is frozen, you find out at delivery. A product approval that sits holds a build slot. A question about envelope, connections or service clearance waits on several parties while the slot passes.
Site and factory drawings are linked to the same elements. A revision from either side re-runs the interface and envelope checks, so the slot holds and what arrives matches what was approved. Schematic, not to scale.
Four issues, in your words.
The site drawing moved after the factory drawing was frozen. We found out at delivery.
Will it fit where it is going: envelope, weight, and the clearance to service it?
The BOM and the model count different things, and nobody can say which is right.
The client changed the cooling unit spec mid-project. What arrived is not what was approved, and the paperwork does not show it.
Envelope and clearance
Will it fit where it is going: envelope, weight, and the clearance to service it?
Load the open spec as a document: Open Rack V3 (ORv3), Open Rack Wide, or the Project Deschutes CDU specification. Criad checks rack envelope and weight against the hall, and CDU service clearance against the spec, measured on the model.
Open this use caseSpec against drawing · cooling unit clearance
Maintenance clearance clause
Cooling units shall be installed so that
the clear space to the nearest rack is
not less than 0.6 m for maintenance.
Clearance is measured to the rack face.
42 of 118
Ranked by authority
Measured on the model, all 16 units
1.45 m
rev 1 · issued 17 Jul 2026
Plan detail, unit to nearest rack row
Reference campus
Hall 2 cooling layout
rev 1
issued 17 Jul 2026
Interface points that meet
The unit arrived and the connections were not where the site expected them.
A skid, a module or a rack row meets the building at a handful of points: power, cooling, network, structure. Criad holds both sides of each interface, yours and the site's, and checks position, size and type against each other on every revision from either party.
Open this use caseFactory 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.
Open this use caseillustrative 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.
Product approval, first time
Our product meets the spec. Getting that agreed takes round after round of comments.
Send the submittal with the proof already in it. Criad checks your product data against each clause of the project spec and against the space it goes into, and produces the clause by clause sheet the reviewer would otherwise build by hand.
Open this use caseSpec against submittal · electrical cabinet depth
Cabinet envelope clause
Free-standing cabinets shall fit the
envelope shown on the layout drawings.
Depth shall not exceed 0.92 m.
Deeper units require a design change.
42 of 118
Ranked by authority
Modelled depth against the limit
0.90 m · request 1.0 m
Data sheet · depth 1.0 m
Overall dimensions (W × D × H):
0.60 × 1.00 × 2.00 m
96 units · one long-lead order
3 of 12
BOM against model
The BOM and the model count different things, and nobody can say which is right.
Counts are read straight from the model and every item is linked to its spec and its order. The BOM is compared line by line, and each difference is listed by hall with the elements behind it.
Open this use caseBOM against model · Hall 2
7 lines · 2 differences
| Item | BOM | Model | Note |
|---|---|---|---|
| Racks, 42U | 240 | 240 | one approved product |
| Electrical cabinets | 16 | 16 | long-lead, one order |
| Cooling units | 15 | 16 | one unit missing from the BOM |
| Distribution frames | 19 | 19 | |
| Sprinkler heads | 640 | 660 | 20 heads short against the fire layout |
| Chilled water pipe segments | 84 | 84 | |
| LV and comms tray runs | 60 | 60 |
Model counts from the reference campus. The BOM column is illustrative. Differences are listed, never averaged; people decide which side is right.
Shipped against approved
What arrived is not what was approved, and the paperwork does not show it.
Each unit is linked to its approved product, its order and its position. At delivery, what arrived is checked against what was approved, and a mismatch goes to the person who accepts the delivery, with the evidence.
Open this use caseA finding, as it would be raised
A delivered unit differs from the approved product
- Specenvelope 0.60 x 1.20 x 2.00 magrees
- Approvedone rack product, 1,440 unitsagrees
- Deliveredone unit differs from the approved productconflicts
- Paperworkdoes not show the differenceno ruling
The mismatch goes to the person who accepts the delivery, with the evidence.
Judge it on a real job.
Book a call. Bring a real question from a job you know, and see how the answer and its evidence come together.
Your project, as it is. Drawings, specs, model and programme come in without retyping.
Your questions, with evidence. Every answer cites the sheet, the clause or the measurement.
Your people decide. Every decision keeps its evidence for later review.
Stop waiting. Start building.
Book a call with the founders. Thirty minutes, your questions, and what Criad looks like on a data centre build.