Explore Pearls
A Pearl is a practical construction lesson: what happened, why it matters, and what to check before similar work begins.
Loading Pearls…
39 Pearls in the collection
Pearl · Critical power
Prove that each ATS can transfer the actual critical load onto a correctly rated and protected failover path without an unintended trip or loss of redundancy.
Use before: Integrated systems testing · Functional performance testing · Installation turnover
Sources: Google Cloud
Read PearlPearl · Controls and OT
Document instrument type, range, accuracy or calibration status, and placement against the signal the commissioning evidence must resolve.
Use before: Functional performance testing · Integrated systems testing · Reliability / load demonstration
Sources: U.S. Department of Energy, Federal Energy Management Program, with National Renewable Energy Laboratory
Read PearlPearl · Controls and OT
Before a coordinated OT or controls-network change, prove the exact aggregate scope and resulting topology, then demonstrate that rollback or stabilization remains executable when the changed path is degraded or unavailable.
Use before: Startup · Functional performance testing · Integrated systems testing · Installation turnover
Sources: Microsoft Azure · National Institute of Standards and Technology
Read PearlPearl · UPS and batteries
Before live work changes critical-power redundancy, prove the temporary topology, remaining support path, finite contingency, and rollback.
Use before: Startup · Functional performance testing · Integrated systems testing · Installation turnover
Sources: Nebius · Uptime Institute
Read PearlPearl · Critical power
Validate applicable electrical configurations at forecast initial and partial load and document how future buildout changes the operating basis.
Use before: Energisation · Functional performance testing · Reliability / load demonstration
Sources: U.S. Department of Energy, Federal Energy Management Program, with National Renewable Energy Laboratory
Read PearlPearl · Controls and OT
Before operational reliance, prove that at least one project-approved cooling-state and room-temperature alert path remains available and reaches named responders when the primary BMS or its monitoring domain is unavailable.
Use before: Installation turnover · Startup · Functional performance testing · Integrated systems testing
Sources: Nebius · Nebius Service Health Status
Read PearlPearl · Controls and OT
Before integrated acceptance, prove every consequential fire or suppression input produces the required effects—and only the required effects—across power, HVAC, controls, and adjacent zones.
Use before: Startup · Functional performance testing · Integrated systems testing · Installation turnover
Sources: NASA Lessons Learned Information System / Jet Propulsion Laboratory · National Fire Protection Association · National Institute of Standards and Technology
Read PearlPearl · Liquid cooling
After final quick-disconnect cycling and hose routing, prove each consequential liquid-cooling connection is fully engaged, mechanically supported within the project-approved envelope, and leak-tight in its final installed state.
Use before: Installation turnover · Startup · Functional performance testing
Sources: Colder Products Company (CPC) · Open Data Center Committee (ODCC) · Sohu / 数策Y字
Read PearlPearl · Controls and OT
Prove that source-transfer controls block every prohibited source combination and complete every required transfer before UPS autonomy becomes consequential.
Use before: Factory acceptance testing and submittals · Integrated systems testing · Functional performance testing · Installation turnover
Sources: Dranetz Technologies, Inc. · Microsoft Azure
Read Pearl