Data Center Lithium-Ion UPS Battery Maintenance: Monitoring, Testing, and Replacement Planning

Lithium-ion UPS batteries play a critical role in maintaining power continuity in data centers. However, battery maintenance involves more than checking state of charge (SOC) or replacing batteries according to age. Teams need to monitor battery condition, investigate abnormal readings, verify battery management system (BMS) communication, and plan maintenance without compromising the required backup capability.

For data center managers, UPS OEMs, and system integrators, an effective maintenance plan connects battery monitoring with operational risk, corrective action, and documented acceptance testing.

This guide explains how to manage lithium-ion UPS battery maintenance, investigate BMS alerts, prioritize replacement decisions, and verify a replacement system before returning it to service.

1. Establish a Lithium-Ion UPS Battery Maintenance Baseline

A reliable maintenance plan starts with a documented baseline. Without one, maintenance teams may struggle to distinguish a meaningful change in battery condition from normal operating variation or a monitoring issue.

For each UPS battery system, record the following information:

• Battery configuration: Battery model, chemistry, module or string arrangement, rated voltage, capacity, and installation date.

• UPS operating requirements: UPS manufacturer and model, protected load, required backup duration, charging requirements, and redundancy arrangement.

• Commissioning baseline: Initial test results, available battery measurements, configured operating limits, alarms, and approved system settings.

• BMS and communication setup: Available monitoring parameters, communication interface, relevant protocol and configuration details, alarm mapping, and monitoring-system connections.

• Maintenance history: Inspection results, BMS alerts, communication faults, test records, corrective actions, and replacement history.

Use these records to establish inspection and testing intervals based on the battery manufacturer's instructions, applicable standards, system design, site criticality, and operating conditions. Requirements differ across battery designs and installations, so maintenance procedures should be specific to the installed system rather than copied from another battery chemistry or configuration.

The plan should also define who reviews monitoring data, how significant alarms are escalated, and what evidence is needed to close a maintenance issue. Assign an owner and due date to each corrective action, and document any interim controls required under site procedures.

2. Use BMS Monitoring Data to Assess Battery Condition

A battery management system provides information that can help maintenance teams identify abnormal operating conditions and decide when further investigation is needed. The available data depends on the battery design, BMS capabilities, and system integration.

Depending on the configuration, monitoring may include:

• Voltage: Available cell-, module-, or string-level measurements, where supported.

• Temperature: Available sensor readings and temperature-related alerts.

• Current: Charging or discharging current and relevant operating conditions.

• SOC and SOH: Estimated state of charge and state of health, according to the system's measurement or estimation method.

• Alarms and protection status: Reported warnings, fault conditions, and available protection-state information.

• Communication status: Connection health, communication errors, and missing or inconsistent data.

The presence of these parameters should not be assumed for every system. Maintenance teams should first confirm which measurements and status signals are actually available and what they mean in the manufacturer's documentation.

When an abnormal reading appears, follow a structured review:

1. Verify the data. Check timestamps, sensor status, communication logs, and whether the reading is consistent with other available measurements.

2. Compare with the baseline. Review the historical trend and relevant operating conditions rather than relying on a single data point.

3. Check related indicators. Determine whether other voltage, temperature, current, or alarm information supports the initial finding.

4. Assess operational risk. Consider the manufacturer's limits, the persistence and severity of the issue, system redundancy, and the consequences of reduced backup capability.

5. Define the next action. Depending on the evidence, this may involve continued monitoring, qualified inspection, diagnostic testing, corrective maintenance, or replacement assessment.

6. Record the outcome. Document the evidence reviewed, the decision, the responsible person, and the required follow-up.

SOC and SOH are useful monitoring indicators, but neither independently verifies that a battery system can support the required load for the specified backup duration. That assessment depends on the system design, operating conditions, battery condition, and appropriate performance-test evidence.

For additional background, see Four Maintenance Methods for UPS Lithium-Ion Batteries.

3. Practical Example: Investigating a Lithium-Ion Battery Temperature Deviation

Illustrative maintenance scenario, not a documented ACE Battery customer case.

A data center monitoring team notices that one battery module consistently reports a higher temperature than comparable modules under similar operating conditions. The UPS has not reported an immediate functional failure, but the temperature deviation persists.

The team must determine whether the reading reflects a sensor or communication problem, a difference in operating conditions, or a battery-related issue requiring corrective action.

Step 1: Validate the measurement

The team reviews the timestamp, sensor status, communication logs, related alarms, and recent changes in ambient conditions, charging activity, or load.

If the reading is inconsistent with other evidence, qualified personnel investigate the measurement and communication path according to the manufacturer's procedures. A communication fault or invalid sensor reading should not automatically be classified as a battery defect.

Step 2: Compare the reading with approved limits

The team compares the verified reading with the applicable manufacturer limits and the module's historical trend. It checks whether the deviation persists and whether related measurements or alarms indicate another abnormal condition.

There is no universal temperature difference that automatically requires replacement across all lithium-ion battery systems. The significance of the finding depends on the battery specification, operating conditions, available measurements, and manufacturer's guidance.

Step 3: Decide whether monitoring, corrective action, or escalation is required

The next step depends on the evidence:

• The reading cannot be validated: Investigate the sensor or communication issue and verify the data before drawing conclusions about battery condition.

• The reading is verified and remains within approved limits: Assess the trend and related indicators to determine whether additional monitoring or inspection is warranted.

• The reading exceeds an applicable limit or is accompanied by a significant alarm: Follow the manufacturer's escalation and safety procedures. Qualified personnel should determine whether further diagnostics, operational restrictions, or replacement assessment is required.

• The cause remains unresolved: Keep the issue open, document the risk assessment, and assign a clear next action.

If the system reports a serious battery fault or shows signs of a potentially hazardous condition, such as abnormal heating, swelling, or an unusual odor, personnel should follow the manufacturer's emergency procedures and site safety protocols. They should not treat the event as a routine monitoring issue or continue normal operation simply to collect more data.

Before any maintenance activity that could affect the protected load, the team must assess available redundancy, operational constraints, and the approved work procedure.

Step 4: Verify the corrective action

After corrective work, review follow-up measurements and confirm whether the original finding has been resolved. Record the evidence used to make that determination.

If the issue remains unexplained, the maintenance record should remain open with an assigned owner and a documented next step.

The practical lesson: BMS monitoring helps teams identify and investigate abnormal conditions, but an alarm alone does not prove that a battery must be replaced. Decisions should be based on verified data, manufacturer requirements, and the operational consequences of the finding.

4. Use a Maintenance Log to Track Battery Risks and Actions

A maintenance log turns monitoring information into an actionable record. It should show what happened, why it matters, what must happen next, and whether the issue has been resolved.

The following template can be adapted for a maintenance spreadsheet, asset register, or computerized maintenance management system (CMMS).

Example maintenance record

This example does not assign an arbitrary temperature threshold or assume the module is defective. Actual priorities and actions must follow the applicable product requirements and site procedures.

Review maintenance records regularly to identify recurring BMS alerts, unresolved communication faults, repeated abnormal measurements, and approaching replacement needs. Close an issue only when the required action and outcome have been documented, or when an exception has been formally handled through the site's approved process.

5. Prioritize Lithium-Ion UPS Battery Replacement

For data centers with multiple UPS systems, replacement decisions should consider battery condition and operational risk rather than age alone.

• Condition evidence: Review confirmed test results, persistent abnormal measurements, BMS alerts, applicable manufacturer limits, and maintenance history.
• Operational criticality: Consider the consequences if the battery cannot deliver the required backup performance and whether the affected system supports a critical load.
• Redundancy and maintenance windows: Determine whether approved alternative power paths can support the protected load during the planned work. Do not assume that redundancy makes every intervention safe.
• Procurement and deployment lead time: Allow time for technical review, configuration approval, manufacturing, delivery, installation, commissioning, and coordination across multiple UPS systems.
• Configuration and integration requirements: Confirm that the proposed battery meets the required electrical specifications, charging requirements, mechanical constraints, BMS communication needs, and project validation criteria.

Battery age remains useful for forecasting and planning, but it should be considered alongside condition evidence and manufacturer recommendations. Conversely, the absence of alarms does not prove that the battery can deliver the required backup duration.

For more detail on identifying replacement needs, see How to Tell If a UPS Battery Needs Replacing.

6. Verify the Replacement Battery System Before Returning It to Service

Replacing a lithium-ion UPS battery requires more than confirming that the UPS powers on. The installed configuration, BMS communication, charging behavior, applicable protection functions, and required performance evidence must be checked against the approved design and acceptance criteria.

The following checklist is a practical starting point. The exact procedure depends on the UPS documentation, battery manufacturer's instructions, system architecture, and approved commissioning plan.

Phase 1: Confirm the approved battery configuration

• Verify that the installed battery model and configuration match the approved design and procurement documentation.

• Check the specified voltage range, capacity, series/parallel arrangement, discharge requirements, and other relevant electrical characteristics.

• Confirm mechanical fit, mounting, cabling, connectors, polarity, and applicable protection arrangements.

• Verify that required installation inspections have been completed and identified installation issues have been addressed.

Phase 2: Verify BMS communication and system interaction

• Confirm that the UPS and BMS communicate as designed, where communication is part of the approved system architecture.

• Verify that expected battery status, monitoring values, and alarms are available at the intended monitoring interface.

• Check applicable communication settings, alarm mapping, and configuration requirements against the approved integration documentation.

• Verify that the relevant protection functions and alarm responses meet the approved design and manufacturer's requirements.

• Investigate communication errors, unexpected alarms, and configuration mismatches before proceeding.

Communication checks must reflect the actual interface and integration design. Supporting a communication protocol does not automatically establish compatibility with every UPS model or firmware configuration.

Phase 3: Complete the approved commissioning tests

• Perform the inspections and commissioning tests specified in the approved procedure.

• Verify charging behavior and relevant battery/UPS operating parameters against manufacturer requirements.

• Complete required functional or performance tests under approved operating conditions, with suitable power-protection and recovery arrangements.

• Record the test method, acceptance criteria, results, exceptions, and corrective actions.

Not every project requires the same test sequence. A discharge test can reduce available stored energy and affect operational resilience. It should therefore be planned and authorized by qualified personnel, with an appropriate recovery plan, rather than performed automatically after every replacement.

Successful startup and normal communication do not, by themselves, demonstrate that the battery meets the required backup duration or discharge performance. Where these requirements apply, acceptance should be based on the approved test method and documented acceptance criteria.

Phase 4: Confirm operational readiness and close out

• Confirm that the system has returned to the approved operating state and that the required backup and redundancy arrangements have been restored.

• Resolve or formally document outstanding alarms, deviations, and limitations in accordance with the approved acceptance process.

• Update the asset register with the installed configuration, relevant serial or module identifiers, and commissioning date.

• Save commissioning results, BMS/UPS configuration records, and relevant baseline measurements.

• Assign an owner and deadline for any remaining follow-up actions.

Acceptance decision: The system should be accepted only when the applicable criteria have been met and the evidence recorded. Any deviation must be resolved or handled through the approved exception process before the system is declared ready for normal operation.

For facilities planning future capacity changes or staged battery additions, see UPS Battery System Expansion Planning.

7. Use Maintenance Records for Long-Term UPS Planning

Review maintenance records across the facility to identify recurring BMS alerts, unresolved corrective actions, systems approaching manufacturer-recommended service milestones, and potential replacement requirements.

Use these findings to coordinate inspection windows, replacement budgets, spare requirements, and engineering reviews. Reassess the plan when the facility changes its critical load, required backup duration, redundancy design, UPS configuration, or expansion strategy.

Maintenance history can also help teams distinguish between battery-related issues and problems involving sensors, communication, system integration, installation, or operating conditions. For additional context on UPS failure prevention, see How to Reduce UPS Power Supply Failure Rate and Extend Battery Pack Life.

Conclusion: Build a Verifiable Lithium-Ion UPS Maintenance Process

Effective data center lithium-ion UPS battery maintenance combines documented baselines, BMS monitoring reviews, risk-based testing, replacement prioritization, and a clear post-replacement acceptance process.

For UPS OEMs and data center integrators, these practices begin at the design and procurement stage. Battery configuration, discharge profile, required backup duration, BMS communication, charging requirements, mechanical constraints, and validation criteria all influence system integration and long-term maintainability.

ACE Battery provides customized lithium-ion battery configurations and supports project-specific BMS communication and integration requirements for UPS applications. Depending on project needs, customization may address electrical specifications, battery configuration, discharge profiles, mechanical constraints, communication interfaces, and BMS requirements.

For a technical evaluation, prepare the UPS manufacturer and model, target DC voltage range, load and discharge profile, required backup duration, charging requirements, available communication documentation, installation constraints, and validation criteria. These details help define the battery requirements and identify the integration work needed for the target application.

Compatibility with the target UPS and compliance with project performance requirements should be confirmed through technical review and the applicable validation process. Supporting a communication protocol alone does not guarantee compatibility with every UPS model or firmware configuration.

Discuss your custom lithium-ion UPS battery requirements with ACE Battery to review battery configuration, BMS communication needs, and project-specific integration requirements. Defining these requirements early helps OEMs, system integrators, and data center teams plan procurement, commissioning, and future maintenance more effectively.

References

• IEEE Standards Association — verify the applicable edition and exact catalog entry for IEEE 1184, Guide for Batteries for Uninterruptible Power Supply Systems.

• IEC Webstore — identify the applicable battery safety and performance standards for the specific lithium-ion system and application.

Select standards and maintenance practices appropriate to the installed battery design, system architecture, and project requirements. Confirm the current editions and applicability of all referenced standards before publication.