Skip to main content
Case Studies

Emergency data-centre battery maintenance led to a dedicated service agreement

Mitsubishi Electric reports that DataBank PIT2 needed emergency VRLA battery maintenance for four UPS systems within one week, outside its existing UPS agreement. [1]

Published operating context

The manufacturer source identifies the customer, application and intervention. It is the primary evidence for the project facts. Guidance for another site comes from the separately identified technical references. No manufacturer result is represented as an independent measurement.

The manufacturer says the emergency battery work required coordination within a one-week deadline. [1]

Published case sequence: Published context; Published intervention; Attributed result.

Figure 1: Published case sequence.

Reported challenge

The battery scope was outside the existing UPS master service agreement. [1]

Operational risk is not limited to a complete outage. A voltage variation, short interruption, transfer, weakened battery, overload, high temperature or unowned alarm can interrupt the protected function. The first task for a similar project is therefore to measure load, read the event history and name the consequence of interruption.

Published response

Mitsubishi reports that PIT2 remained on schedule and added a battery-maintenance master service agreement for future work. [1]

The published sequence shows a solution selected for one context. It does not prove that the same rating, model, runtime or architecture fits elsewhere. A new project must confirm voltage, conductors, grounding, bypass, alternate source, clearances, environment and delivery route before purchase.

Evidence boundary: OEM facts; GDF method; Missing site records.

Figure 2: Evidence boundary.

Engineering qualification for another site

The design register separates known, measured, customer-stated, calculated and unresolved inputs. It covers normal watts and VA, peaks, runtime, power factor, phase loading, generator, temperature, cooling, batteries, communications and the work window. An unknown that changes safety, capacity, runtime or maintainability blocks firm selection.

States to prove include normal operation, source loss, stored-energy support, alternate source, static bypass, maintenance bypass, component isolation and return to normal. For each state, the record names the load path, remaining protection, reserve, permitted duration, alarms, switching authority and rollback condition.

Implementation controls

The purchase record binds the exact model, voltage, rating, batteries, bypass, accessories, network interface, certification, warranty and startup. A substitution requires a dedicated source and a fresh check of every criterion. Custom or non-cancellable equipment receives a separate release gate.

The UPS services can be used to define the survey, commissioning or maintenance scope that must produce this site evidence.

Case-specific decision matrix: One-week response sequence: The documented emergency response sequence and the target response time in the agreement, with the escalation contacts; Hold if the response sequence and target time are not in the signed agreement; Four-UPS maintenance state: For each of the four UPS: the maintenance state, bypass availability, and the safe work boundary during service; Do not begin service on any unit without its bypass and safe work boundary confirmed; Battery work outside the agreement: The battery scope inside versus outside the agreement, and the approval path and pricing for out-of-scope battery work; Do not perform out-of-scope battery work without a separate approval; Future battery coverage and response terms: The future battery-coverage option and the response terms carried into the renewed agreement; Keep the deficiency open until future battery coverage and response terms are agreed in writing.

Figure 3: Case-specific decision matrix.

Reported results and measurement limits

The results above are manufacturer-reported. The public source is not an independent audit and may omit load profile, event logs, runtime tests, costs, failures, settings and observation duration. Those omissions do not disprove the published result, but they prevent conversion of that result into a guarantee for another site.

Records to carry forward

The closeout file retains the load survey, as-built one-line, models and serials, battery configuration, settings, firmware, transfer tests, alarms, deficiencies, corrections and final state. It also names the owner for alarms, updates, spares and the next lifecycle decision.

Subject-specific decision register

Four decisions govern this publication: one-week response sequence, four-ups maintenance state, battery work outside the agreement and future battery coverage and response terms. They form a reviewable register instead of a generic checklist. Each row has an input, source, owner, acceptance condition and consequence when evidence is missing.

Decision Required evidence Stop condition
One-week response sequence The documented emergency response sequence and the target response time in the agreement, with the escalation contacts Hold if the response sequence and target time are not in the signed agreement
Four-UPS maintenance state For each of the four UPS: the maintenance state, bypass availability, and the safe work boundary during service Do not begin service on any unit without its bypass and safe work boundary confirmed
Battery work outside the agreement The battery scope inside versus outside the agreement, and the approval path and pricing for out-of-scope battery work Do not perform out-of-scope battery work without a separate approval
Future battery coverage and response terms The future battery-coverage option and the response terms carried into the renewed agreement Keep the deficiency open until future battery coverage and response terms are agreed in writing

The site survey records load, source, room, environment, bypass, delivery route and operating constraints [4]. Calculations and assumptions retain units, load state and source [5]. This connection prevents a catalogue value or a case outcome from becoming the default value for a new installation.

The state register separates normal operation, source loss, stored-energy support, static bypass, maintenance bypass, isolation and return [6]. It states what supplies the load, remaining protection, energized sources, permitted duration, alarms and the point where work must stop.

Monitoring identifies card, firmware, protocols, network segment, accounts, logs and alarm owner [7]. Read-only remains the starting point. A remote command or automated shutdown requires an approved need, dependency map and tested rollback.

Commissioning establishes criteria before testing and retains measurements, events, deficiencies, corrections and final state [8]. The service agreement states response, exclusions, spares, maintenance window, report and next lifecycle decision [9].

The cited GDF field pattern is used only for the comparable-project method [10]. It does not mean that GDF performed the manufacturer case. Customer facts, products, quantities and results remain attributed to the manufacturer source.

Sources

  1. Mitsubishi Electric, DataBank PIT2: Supporting a Local Data Center. https://mitsubishicritical.com/wp-content/uploads/2025/02/sa-enl0099-supporting-a-local-data-center.pdf
  2. GDF Technologies internal knowledge library, UPS Battery Testing and Condition Assessment. Local library: UPS Maintenance/UPS Battery Testing and Condition Assessment.md
  3. GDF Technologies internal knowledge library, UPS Service Contracts and PM Agreements. Local library: Service Contracts & PM Agreements/UPS Service Contracts and PM Agreements.md
  4. GDF Technologies internal knowledge library, UPS Site Survey and Requirements Capture. Local library: UPS Solutions & Quotes/UPS Site Survey and Requirements Capture.md
  5. GDF Technologies internal knowledge library, UPS Engineering Calculations and Independent Design Verification. Local library: UPS Solutions & Quotes/UPS Engineering Calculations and Independent Design Verification.md
  6. GDF Technologies internal knowledge library, UPS Maintenance MOP Safety Boundaries and Go-No-Go Criteria. Local library: UPS Maintenance/UPS Maintenance MOP Safety Boundaries and Go-No-Go Criteria.md
  7. GDF Technologies internal knowledge library, UPS Monitoring Cybersecurity and Network Integration. Local library: Monitoring, SNMP & Shutdown/UPS Monitoring Cybersecurity and Network Integration.md
  8. GDF Technologies internal knowledge library, UPS Commissioning and Acceptance Testing. Local library: Installation & Commissioning/UPS Commissioning and Acceptance Testing.md
  9. GDF Technologies internal knowledge library, UPS Service SLA Design and Coverage Scoping. Local library: Service Contracts & PM Agreements/UPS Service SLA Design and Coverage Scoping.md
  10. GDF Technologies, GDF Field Case Library: Engineering and Quoting Patterns. Local library: UPS Solutions & Quotes/GDF Field Case Library – Engineering and Quoting Patterns.md
Christian Barkley
Director, GDF Technologies

inConnect with the author on LinkedIn

GDF Technologies services every UPS brand covered here, across Canada. See our preventive UPS maintenance plans or call (514) 252-8324 for on site support.

Close Menu