CRIAD
Integrators and OEMs · Use case 02

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.

Every answer cites its source. People decide.

How it works

Ask. Inspect. Verify. Publish.

1

Ask

A plain-language question.

"Do our connection points still match the site design?"
2

Inspect

The full blast radius, on the model.

Each interface on the model: your side, the site side, and the distance between them.
3

Verify

Checked against the governing drawings and specs.

Position, size and type are measured on the model and checked against the interface schedule and the spec. The governing document is named.
4

Publish

A dashboard, report or register, citations attached.

An interface register per unit: agreed, moved or missing, with the sheet and revision for each side.
Worked example

One job, start to finish.

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

Reference campus
  1. 01

    Trace one rack on the reference campus: rack, distribution frame, fibre entry.

  2. 02

    Each link in the path is an interface with two sides.

  3. 03

    A revision from either side re-runs the check.

  4. 04

    The register goes to both parties, so the question is settled before the unit ships.

Fire water plant Fire water plant · a skid meets the building
Highlighted: the elements the answer refers to

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