Escalate Repeated Battery Failures to Population-Level Disposition
After repeated consequential battery failures, define the credible common-mode population and obtain an explicit retain, inspect, quarantine, modify, or replace disposition before accepting the remaining units.
After these repeated battery failures, what is the credible common-mode equipment population, and what evidence supports retaining, inspecting, quarantining, modifying, or replacing every unit in that population before we accept or rely on it?
Create a controlled population inventory for every potentially related battery unit or cabinet, including available manufacturer, model, lot or serial grouping, production period, design revision, supplier, configuration, location, installation condition, commissioning state, environment, and operating history
Reconcile every known failure, fire alert, near miss, abnormal acceptance result, damaged unit, warranty return, OEM notice, and relevant corrective action to that inventory
Define a provisional common-mode population and document the technical basis for including or excluding each unit or subgroup; do not expand the boundary to a manufacturer, chemistry, site, or equipment class without evidence
Obtain and reconcile the OEM, supplier, electrical engineer, owner technical authority, commissioning authority, and relevant safety or fire-marshal assessments needed to test the population hypothesis
Place unresolved units or subgroups into the project-approved hold, quarantine, conditional-use, or other controlled state until the responsible technical authority records a disposition
Implement the accepted retain, inspect, modify, repair, replace, or other disposition and complete any required inspection, replacement, corrective-work, retest, and acceptance evidence before release
What the sources describe
On September 8, 2025, Chesterfield Fire and EMS responded to a fire alert at Chirisa Technology Parks' CTP-01 data center near Richmond, Virginia. CTP said a single battery caught fire, the fire was contained within the cabinet and extinguished by suppression, and personnel were safely evacuated. CTP described the event as the fourth alert of this kind at the facility and announced that all batteries would be immediately removed and replaced with units from a different manufacturer. WTVR separately reported four fire-service calls at the facility within the preceding year, and Data Center Dynamics reported that the August 20 incident was also in a battery room. CTP said it believed a manufacturing defect caused the September event, but no independent forensic determination, common equipment identity, or shared root cause across all events is established in this package.
battery supplier · Before the relevant work begins
Every potentially related unit or cabinet is uniquely identified and mapped to the available manufacturer, model, lot or serial grouping, production period, revision, supplier, configuration, location, commissioning state, environment, and operating history used to define the population.
Failure and recurrence evidence register
battery supplier · Before the relevant work begins
Every known failure, alert, near miss, abnormal test result, damaged unit, warranty return, OEM notice, and relevant corrective action is reconciled to the population matrix with source and date.
Technical common-mode population assessment
battery supplier · Before the relevant work begins
The responsible technical parties document the credible shared factors, the evidence for inclusion and exclusion, unresolved uncertainty, and why the selected boundary is neither narrower nor broader than the available evidence supports.
Signed population disposition record
battery supplier · Before the relevant work begins
Every unit or bounded subgroup has an explicit retain, inspect, hold, quarantine, modify, repair, replace, or other approved disposition with accountable authority and release conditions.
Population corrective-action completion record
battery supplier · Before the relevant work begins
Required inspections, quarantines, repairs, modifications, replacements, labeling, configuration changes, and related field actions are complete and reconciled to the disposition record.
Population retest and acceptance evidence
battery supplier · Before the relevant work begins
The project-defined inspection and retest scope is complete, results meet accepted criteria, exceptions are closed or formally accepted, and the responsible authority records release before energization, turnover, or continued reliance.
Conditions to resolve before proceeding
The potentially affected population cannot be bounded with traceable equipment identity and shared-factor data
Repeated failures are being closed as isolated unit issues without a documented population-level assessment
A retain or release decision relies primarily on the fact that remaining units have not yet failed
A plausible shared factor identified by the technical team has not been evaluated or dispositioned
The accepted corrective action has no defined inspection, replacement, test, or acceptance evidence for the affected population
New evidence materially expands or changes the credible population after a prior release decision
Where the lesson comes from
Sources
Use the original material to understand the evidence, scope, and context behind this Pearl. Suggested project actions are Build Pearls’ interpretation.
Chirisa data center in Virginia suffers second fire in three weeks
Data Center Dynamics · Source date: 2025-09-08 · Article comparison with August 20 incident; Article update quoting CTP's LinkedIn statement; September 8, 2025 incident report · Accessed: 2026-09-03
CTP-01 September 8 battery-fire update and fleet replacement decision
Chirisa Technology Parks · Source date: 2025-09-11 · Company LinkedIn update beginning 'Last Monday, September 8'; Company LinkedIn update, containment description; Company LinkedIn update, corrective-action statement; Company LinkedIn update, incident description; Company LinkedIn update, recurrence statement; Company LinkedIn update; operator belief, not an independent forensic finding · Accessed: 2026-09-03
General Commissioning Requirements — Failure Due to Manufacturer Defect
U.S. Department of Veterans Affairs · Section 01 91 00, 'Failure Due to Manufacturer Defect'; Section 01 91 00, 'Failure Due to Manufacturer Defect,' item 3 · Accessed: 2026-09-03
The article does not establish a common manufacturing defect across the repeated events or identify the affected battery population.
The article establishes repeated fire-service responses but does not establish that every event involved the same battery manufacturer, model, lot, chemistry, or failure mechanism.
The article's chronology should not be converted into a universal numeric escalation threshold.
The public evidence does not identify the battery manufacturer, model, chemistry, lot, production period, exact failure mechanism, or whether all four CTP-01 alerts shared one cause.
The report does not publish the Fire Marshal's investigation, forensic reports, equipment records, or final root-cause determination.
The specification applies to its contract context and does not establish the appropriate population boundary for batteries on another project.
The update does not establish that all four alerts shared one root cause.
The update does not identify battery manufacturer, model, chemistry, lot, production period, failure mechanism, or the exact population boundary of the batteries being replaced.
WTVR's four-incident chronology establishes recurrence at the facility but not a shared equipment identity across every incident.
The project can obtain traceable battery equipment identity, procurement, installation, commissioning, warranty, and failure records sufficient to test a common-mode hypothesis.
Qualified technical parties can distinguish a credible shared population from coincidental or externally caused failures.
The Pearl will be implemented through existing commissioning, nonconformance, OEM, safety, quarantine, change-control, and owner authorization processes.
Fire at Chirisa Technology Park is fourth within the last year, Chesterfield Fire and EMS says
WTVR CBS 6 · Source date: 2025-09-08 · Article chronology of prior fire-department calls; Article quoting Chesterfield County statement; Article text quoting Chesterfield Fire and EMS · Accessed: 2026-09-03