Tenant standards, checked before the corridor is built
The tenant has its own pathway and conduit standard. We found the difference after the corridor was built.
Every tenant brings a standard of its own for pathways, conduit, containment and labelling, and it rarely matches the base-build spec line for line. Criad loads the tenant standard beside the spec, shows where the two disagree, and checks the model against both before the corridor is built, not after.
Every answer cites its source. People decide.
How it works
Ask. Inspect. Verify. Publish.
Ask
A plain-language question.
Inspect
The full blast radius, on the model.
Verify
Checked against the governing drawings and specs.
Publish
A dashboard, report or register, citations attached.
One job, start to finish.
Values come from a structured reference campus, not from a client project.
- 01
Reference campus, Hall 2: the containment run is one connected path on the model.
- 02
Each element on it knows the sheet it is drawn on and the clause that limits it.
- 03
A tenant standard is loaded as one more document and ranked against the spec and the code: 360 degrees of bend between pull points (NEC, TIA-569), 200 mm power to data separation for unscreened cables (EN 50174-2).
- 04
The differences are listed, with both clauses, before anything is built.
Tenant standard against drawing · containment route
Stricter than the code limit of 360 degrees
No junction boxes on tenant pathways.
Total bend between pull points shall
not exceed 180 degrees.
Pull points shall be shown on the drawings.
17 of 64
Ranked by authority
Counted on the drawing
360 degrees
rev 1 · pull points shown
Riser drop: 4 × 90 degree turns
between the frame and the first pull point
Reference campus
LV containment, riser to Hall 2
rev 1
pull points shown
Platform capabilities used
The same capabilities serve every segment. Each one links to its section.
Stop waiting. Start building.
Book a call with the founders. Thirty minutes, your questions, and what Criad looks like on a data centre build.