1. Identify the configuration behind the label.
Start with the selected rack, IT equipment, power arrangement, and document revisions. The OCP Rack & Power project includes several architectures and interface specifications; a reference to OCP alone does not identify the complete configuration. For an ORv3 proposal, compare the vendor’s equipment list with the applicable frame and IT gear documentation, then record any options or adaptations that affect the site.
- Which rack model, revision, power shelves, and IT chassis are included?
- What is the proposed operating load, and what evidence supports that planning assumption?
- Which interfaces are vendor-confirmed, and which still need a joint review?
2. Follow the rack from delivery to its final position.
The ORv3 base specification allows external frame dimensions to vary by developer, so use the selected product’s drawings and shipping information. Walk the delivery route with facilities and the installation partner before the delivery date becomes a dependency. Include the condition in which the rack will arrive: empty, partially populated, or fully assembled. That choice changes the handling discussion.
- Are packaging dimensions, loaded weight, doors, lifts, turns, and staging areas documented?
- Who will confirm the route, floor-loading basis, positioning method, and installation clearances?
- Can the operating team access the components that will need regular inspection or replacement?
3. Trace power and cooling responsibilities across the boundary.
Ask the project parties to connect facility requirements to the exact rack configuration. Keep power capacity assumptions separate from equipment ratings and planned growth. If liquid cooling is included, identify the selected chassis, manifold, cooling distribution, and facility connections together. The ORv3 IT Gear Design Guide addresses blind-mate liquid-cooling interfaces and access considerations; vendor documentation should explain how the proposed combination applies at your site.
- Who confirms electrical compatibility, available capacity, connection responsibilities, and the supporting records?
- Which cooling requirements come from the equipment vendor, and who validates facility-side availability?
- Where are the ownership boundaries for connections, monitoring, maintenance, and changes?
4. Review the operating model before the equipment arrives.
Bring operators into the review while layouts and responsibilities can still change. Discuss how a failed component will be identified, accessed, replaced, and returned to service through the site’s procedures. Check whether alarms reach the people responsible for responding and whether a vendor support agreement covers the proposed configuration. A drawing can show an interface without explaining who manages it during an incident.
- Which procedures, training, spare components, and support contacts need to be ready?
- Who maintains power shelves, cooling interfaces, sensors, and shared facility equipment?
- Which operating services or neighboring racks constrain installation and future maintenance?
5. Define what closes a readiness question.
Finish with a review register rather than a general statement that the site is ready. For each open item, record the requirement, evidence received, responsible party, decision needed, and closure condition. Agree which items must close before procurement, delivery, installation, or operational handover. This gives leadership a practical sequence without hiding unresolved assumptions inside a single approval.
- Request current drawings, equipment requirements, and the agreed interface schedule.
- Identify completion and test records to be supplied by the responsible project parties.
- Assign the owner of the final handover package and the remaining action list.
Our team brings OCP rack experience together with facility assessment, critical operations, and HPC deployment experience. An engagement can help organize the evidence and coordination needed for your next decision, whether the starting point is a vendor proposal or a planned site upgrade.
Technical references
Use the selected equipment documentation and project requirements when defining your review.