The worst fire hour in a hyperscale build arrives before the suppression works

The two fires the DCD piece leans on both happened in operating buildings, and the author's conclusion from them is that traditional fire protection is not always sufficient ^[12]. That is an argument about construction sites that the piece does not quite make. Singapore took 36 hours of firefighting and lost two battery rooms and two power supply rooms ^[8]. Add the Korean incident and the two events consumed 46 hours between them ^[18]. If a battery room with its protection in service needs that, the same thermal runaway chain reaction ^[7] in a room whose detection and suppression have not been commissioned is not the smaller version of the problem.

The evidence base is thin in a specific way worth naming. Counting the piece's own examples gives five battery-linked incidents across four locations, including two at a Virginia facility and a small explosion in a battery room at a Microsoft campus in Goodyear, Arizona ^[19]. Not one of them is a construction-phase fire. The author asserts a gap between the hazards present on site and the measures deployed against them ^[17], but offers no site incident to size it. Anyone budgeting for this is pricing an exposure with no loss history attached.

What changes the contractor's position is scope, not severity. NFPA 855 sets minimum requirements for the design, installation and operation of stationary energy storage, with criteria for siting, ventilation and emergency response ^[13]. NFPA 800 is being written as a full lifecycle code, reaching manufacturing, transport, installation and end-of-life ^[14]. Transport and installation are the phases a builder owns outright. Meanwhile the batteries actually multiplying on an active site are the ones in tools and temporary site power ^[6], which are not stationary storage and sit outside the standard that most projects cite as their benchmark.

Interpretation is the other variable. The piece reports that implementation varies between jurisdictions, project teams and authorities having jurisdiction ^[15], and that construction-phase requirements in particular are read more flexibly, with many projects aiming at minimum compliance ^[16]. Flexibility is pleasant until a delay has to be allocated. There is no operator to hand a burnt-out temporary store to at 70 percent complete, so the time comes out of the programme and the money comes out of whichever contract clause covers it.

For scale of attention, contrast the loudest objection to the largest proposed campus of this cycle. In Utah, the argument was 40,000 acres, nearly three times Manhattan, and researchers warning about local temperature effects ^[1][3]; developers agreed to halve it, to roughly 20,000 acres ^[2][4]. Fire did not feature. Data centres have long been treated as low-fire-risk environments, an assumption battery storage is now testing ^[20], and the author's position is that prevention now sits alongside power availability as a determinant of whether a project lands ^[21]. On the construction schedule, that is where it already sits.