Archive / current issue
Category: Operations
Shift handoffs, evidence packs, and maintenance calendar discipline.
-
1–2 minutes
What operators should verify in the first maintenance cycle
A short, repeatable inspection rhythm for liquid-cooled AI infrastructure.
-
1–2 minutes
EOPs define the first minutes when the site is off script
Emergency procedures only work when they are short, practiced, and specific to the site.
-
1–2 minutes
Why the chiller is only one part of the thermal chain
The chiller matters, but the operating margin comes from the full cooling stack.
-
1–2 minutes
MOPs control state changes without creating side effects
When equipment state changes, the sequence has to be deliberate, validated, and reversible.
-
1–2 minutes
Air cooling vs. liquid cooling in AI hyperscale racks
Where air still fits, where liquid becomes mandatory, and why hybrid plants are often the practical answer.
-
1–2 minutes
SOPs define the normal operating envelope
Routine operations only work when the team agrees on the baseline, the setpoints, and the handoff rules.
-
1–2 minutes
GB200, GB300, and Vera Rubin reset the cooling baseline
A technical look at the liquid-first thermal stack now shaping AI hyperscale operations.
-
1–2 minutes
SOP, MOP, and EOP are the real control plane for AI hyperscale operations
Procedures are not paperwork; they are the operating system for normal work, state-changing maintenance, and emergencies.
-
1–2 minutes
From feed failure to recovery: the workflow that keeps data centers out of firefighting mode
The safest way to handle a one-side electrical feed failure is to run a short, repeatable workflow that keeps the site stable, preserves options, and verifies recovery.
-
1–2 minutes
What to check after one electrical feed fails: the power, cooling, and controls sequence
A feed loss is not only an electrical event. It can change the operating margin of power, cooling, and controls, so the next step is to inspect what is now exposed.
Data Center Health 