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 · Controls and OT
Map each critical OT component to its intended outage behavior and required alternate-power duration, then prove the project-defined transition.
Use before: Integrated systems testing · Operations acceptance and ready for service
Sources: National Institute of Standards and Technology
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
Apply equivalent governance to primary and redundant OT paths and prove project-defined normal-to-emergency or manual transition and recovery.
Use before: Integrated systems testing · Operations acceptance and ready for service
Sources: National Institute of Standards and Technology
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 · Cooling
Before startup, load testing, or partial operation with an incomplete or altered building envelope, reconcile the actual temporary thermal load and prove the available cooling configuration can maintain project-accepted conditions.
Use before: Installation turnover · Startup · Functional performance testing · Integrated systems testing
Sources: ASHRAE · Tornado Datacenter GmbH & Co. KG
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 · Controls and OT
Inventory backed-up OT logic, configuration, images, and rules; prove safe restoration or an approved compensating integrity method.
Use before: Early-life review · Integrated systems testing · Operations acceptance and ready for service
Sources: National Institute of Standards and Technology
Read PearlPearl · Cooling
Before planned maintenance changes cooling redundancy, prove the exact maintenance-state topology, remaining cooling path and accepted capacity for every affected critical load area.
Use before: Installation turnover · Functional performance testing · Integrated systems testing
Sources: Proton · Uptime Institute
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