Start with the acceptance boundary
Vertiv’s commissioning material separates preparation, checks and integrated assessment rather than treating delivery as a single event. Its prefabricated facility material describes an integrated package, but the package must still join a particular site. The practical implication is to define the intended acceptance evidence while requirements are being agreed, instead of leaving completion criteria until the end.
Our suggested record names the proposed equipment configuration, the site interfaces, the parties reviewing each boundary and the evidence required at handover. Separate supplier factory acceptance, site equipment acceptance, integrated facility behavior and customer workload evaluation. These checkpoints answer different questions. An acceptance record should also identify unresolved items and the decision authority for closing them. A signed delivery receipt cannot answer all of those questions, even when equipment arrived undamaged and on schedule.
Commissioning your data center for greater availability and safety — Vertiv (external source) · Prefabricated Data Center brochure — Vertiv (external source)Factory integration has a bounded test scope
Prefabrication can move selected assembly and testing into a factory environment. OCP’s liquid-cooling integration guidance discusses manufacturing and testing before transport as part of a broader logistics process. That evidence is useful because it records what the supplier assembled and checked. Its scope depends on the equipment, conditions and interfaces present during the test.
A buyer should request a plain-language test boundary: what configuration was tested, what was simulated, what remained outside the factory and what exceptions were recorded? Carry those limitations into the site plan. Our analysis favors a chain of evidence in which each later checkpoint closes earlier uncertainties. It would be misleading to call a factory result a complete site result when the actual utility supply, heat rejection, network paths or installed configuration were absent.
Liquid Cooling Integration and Logistics White Paper, revision1.0 — Open Compute Project (external source) · Network edge enabled by prefabricated modular data centers — Schneider Electric (external source)Treat transport as a handoff
OCP’s logistics discussion covers handling and transport of liquid-cooled equipment and its later integration. These are not merely commercial shipping details. Preparation, receipt and reinstatement need coordination with the supplier’s instructions and the project’s qualified engineering team. This article does not provide transport, lifting or electrical work procedures.
For planning, maintain a transfer record connecting the factory configuration to the equipment received on site. Record the responsible parties, inspection evidence and any changes or exceptions. A useful commercial question is who owns a discrepancy discovered after delivery, and how acceptance pauses until that discrepancy is assessed. Preserve the source documents rather than replacing them with a vague completion label. The objective is traceability across the handoff, not a promise that every module follows an identical transport process.
Liquid Cooling Integration and Logistics White Paper, revision1.0 — Open Compute Project (external source)The site join is an integration milestone
The prefabricated package meets external civil, electrical, cooling and network interfaces at the installation site. Vertiv’s startup and commissioning services distinguish equipment startup from commissioning activities. A useful readiness plan therefore shows required external dependencies before the package can be evaluated under its intended operating conditions. Prefabrication does not remove the need for site approvals and qualified installation.
Our interface register asks whether each upstream service matches the accepted design, whether the installed equipment matches the factory record and which open items prevent the next checkpoint. Keep responsibility visible across different suppliers. A completed enclosure can coexist with an incomplete external dependency. Conversely, an energized site can still lack accepted equipment. Progress reporting becomes more useful when it names the boundary that has been completed instead of describing the whole project as ready.
Prefabricated Data Center brochure — Vertiv (external source) · Startup and Site Acceptance Test — Vertiv (external source)Assess integrated behavior
Vertiv’s commissioning guidance frames integrated testing as a way to evaluate facility behavior, including interactions among systems. Equipment-level startup does not by itself demonstrate the response of the entire installation. The project’s qualified commissioning team must establish the applicable test scope and safe procedures; a general website guide cannot prescribe them.
For procurement and governance, ask which scenarios were assessed, what assumptions and temporary arrangements applied, which exceptions remain and how the operator received the results. A report should make pass criteria and configuration identity inspectable. Our proposed status model distinguishes checked equipment, assessed integrated behavior and accepted operating handover. This avoids turning an isolated successful test into a claim that all normal and abnormal operating conditions have been proven.
Commissioning your data center for greater availability and safety — Vertiv (external source)Connect the facility to a compute product
A facility handover and a customer compute acceptance are separate boundaries in our proposed operating model. A future dedicated cluster evaluation would need an agreed system configuration and workload criteria. A managed inference evaluation would additionally need a checkpoint, runtime, request distribution and quality boundary. Those decisions belong in a service acceptance record rather than being inferred from building power or rack count.
Use the existing inference benchmark methodology to define measurements before any test runs. State what the buyer observes, which failures count, how concurrency is controlled and what constitutes a completed response. Keep a facility milestone and a software-service milestone in separate fields. Aguasto has not executed the commissioning or GPU workload evaluations described here. The publication provides a method for preparing evidence, not operating instructions or a report of completed Aguasto work.
Sources & verification
The register preserves each source's publication and verification date. Manufacturer claims and documentation are attributed; Aguasto has not run the cited products in production.
- Commissioning your data center for greater availability and safety — Vertiv ↗
Commissioning scope spans requirements/design/construction/operations; Vendor startup, integrated test and turnover are distinct. Publication: date not stated in the reviewed source. Verified: 2026-10-13.
- Prefabricated Data Center brochure — Vertiv ↗
Factory/site/service integration phases; Engineering, acceptance plans, installation and commissioning roles. Publication: date not stated in the reviewed source. Verified: 2026-10-13.
- Liquid Cooling Integration and Logistics White Paper, revision1.0 — Open Compute Project ↗
FWS/TCS/CDU terminology and liquid-to-liquid isolation; Manufacturing, transport, inspection and commissioning handoffs; Wetted materials and project-specific tests. Publication: date not stated in the reviewed source. Verified: 2026-10-13.
- Network edge enabled by prefabricated modular data centers — Schneider Electric ↗
Factory assembly and site work may proceed in parallel. Publication: 2022-05-17. Verified: 2026-10-13.
- Startup and Site Acceptance Test — Vertiv ↗
Electrical/mechanical startup checks; Functional testing in operational modes and integrated site acceptance. Publication: date not stated in the reviewed source. Verified: 2026-10-13.