Battery Bank: Managing UPS & Backup Power Lifecycles in Modern Buildings

Why UPS battery health becomes a building operations issue fast

In this episode of Built, Wired & Secured, Alex Morgan sits down with Michael Harrington and James Rogers to talk about a building system most people ignore until it fails: the battery-backed UPS. The conversation opens with a familiar operations nightmare. Power returns, the lights come back, but key systems still do not behave normally. Card readers stop accepting credentials. HVAC controllers act unpredictably. Tenant-critical devices go offline or refuse connections. From the outside, the event can look small. Inside the building, it creates immediate disruption.

The core message is simple: battery failures are often silent. There is usually no dramatic warning, no smoke, and no obvious catastrophe until a real outage exposes lost runtime that disappeared long before anyone noticed. For property managers, facilities leaders, and IT teams, that makes UPS battery health a reliability issue, not just an electrical maintenance detail.

What actually shortens battery life

Michael explains that temperature is the most important physical factor. When battery rooms run above the manufacturer’s recommended range, expected life drops quickly. But heat is not the only problem. The group also points to:

• Float voltage that is set too high, accelerating internal corrosion
• Frequent cycling, which reduces available capacity over time
• Ambient humidity that affects long-term health
• High-resistance intercell connections that weaken the entire string
• A single bad cell in a series string pulling down overall performance

One important lesson from the episode is that status lights can create false confidence. A UPS can show a healthy indicator while the battery bank is already degraded. The team stresses that inverter status is not the same thing as verified battery health. Hands-on testing methods such as conductance or internal resistance checks can reveal deterioration much earlier than a runtime estimate or a green light on the front panel.

They also share a practical warning about spares: storing replacement batteries in poor conditions can ruin them before they are ever needed. In one example, a spare lost a large portion of its useful life simply because it sat through summer heat on a mezzanine.

Monitoring versus fixed replacement schedules

A major part of the discussion centers on the budget question many organizations face: should they invest in monitoring and replace only when data shows decline, or should they just replace batteries on a fixed schedule every few years?

The answer in this episode is not either-or. It is hybrid. The speakers make clear that monitoring alone is not enough. Sensors can fail. Dashboards can be ignored. Alerts can go unread. Without ownership and response processes, monitoring becomes another false layer of confidence.

At the same time, fixed interval replacement has limitations too. It is easy to budget and simple to explain, but it can waste money in cooler, low-cycle environments where batteries may still be healthy. Telemetry, when paired with real accountability, can help prioritize capital and avoid unnecessary replacements.

The right questions, according to the group, are operational:

• Who watches the alerts?
• Who approves replacements?
• What response SLA applies when a threshold is crossed?
• How quickly can parts be swapped when a battery bank degrades?

That framing matters because the real risk is not just battery chemistry. It is organizational delay.

Why ownership and handoffs matter more than people think

One of the strongest themes in the episode is that backup power works best when facilities and IT have clearly defined roles. Facilities should own environmental conditions, physical maintenance, and spare storage. IT should own the dependency map: which systems truly need runtime, what failure is acceptable, and which loads must stay online for tenant service, safety, or clinical continuity.

The team warns against vague vendor arrangements. “Maintenance included” is not enough if no one can answer basic questions later. The speakers describe a site where annual runtime tests existed only in a vendor portal. When a string failed, everyone pointed somewhere else. Procurement questioned warranty coverage. The vendor referenced prior passing tests. Facilities lacked a shared operating history. The technical issue became a documentation and accountability issue.

The recommended fix is straightforward:

• Export reports into the CMMS
• Assign a battery health owner
• Set replacement triggers tied to measurable metrics
• Keep records for installed strings and spare strings in one place

That level of discipline turns backup power from a purchase into a managed operational program.

A practical hybrid program for modern buildings

For teams trying to balance risk and cost, the episode lays out a practical model. Lower-risk, non-critical loads may be fine with scheduled replacement and periodic spot checks. Higher-risk systems need more. If a UPS supports tenant safety systems, clinical equipment, access control, or other critical building functions, the recommendation is to invest in continuous telemetry and to keep at least one full spare string on site.

But even there, the conversation stays grounded in process. A spare is only helpful if it is stored properly, exercised under load at regular intervals, and documented just like the installed bank. Letting a spare sit untouched for years creates a dangerous illusion of readiness.

The checklist property managers can use right away

James gives listeners a practical operating checklist that can be put into use immediately:

• Daily: confirm there are no active UPS alarms and verify battery room temperature is in range
• Weekly: review runtime estimates and investigate any drift
• Monthly: log conductance or internal resistance and compare against baseline
• Semiannually: exercise a spare string under load for a short interval
• Annually: perform a full-load runtime test and store the report in the CMMS
• Always: keep at least one full spare string on site for critical battery banks, stored cool and charged

The team also advises defining escalation paths in advance. If a threshold is crossed at 3:00 a.m., everyone should already know who gets called, who can authorize replacement, and how to move quickly without budget or approval delays.

What to require from vendors

The episode closes the loop with three concrete vendor requirements listeners can insist on:

• Specific test protocols and written data delivery requirements
• Replacement obligations tied to measurable metrics, not vague promises
• On-site spares or same-day provisioning guarantees for critical banks

The speakers also recommend a yearly tabletop exercise for UPS failure response, including notifications, spare swapping, and tenant communications. That is where unclear responsibilities usually become obvious.

The takeaway

The biggest lesson from this episode is that backup power should be treated as an operational program, not a one-time equipment purchase. Monitoring helps prioritize. Hands-on checks confirm actual condition. Spares reduce recovery time. Clear ownership prevents preventable delays. In modern buildings, that combination protects tenant trust, avoids longer outages, and keeps critical services available when the power flickers and expectations do not.

Backup power is only reliable if the battery program is reliable

Modern buildings depend on far more than lights and outlets. Access control, HVAC controls, communications, tenant systems, and in some environments even clinical monitoring all rely on uninterrupted power for graceful operation through short outages and unstable power events. That is why UPS systems matter so much. But as discussed in this episode of Built, Wired & Secured, the real point of failure is often not the UPS chassis itself. It is the battery string quietly degrading in the background.

In “Battery Bank: Managing UPS & Backup Power Lifecycles in Modern Buildings,” Alex Morgan talks with Michael Harrington and James Rogers about a problem that hides in plain sight. A building may appear protected because the UPS has power, indicator lights are green, and the equipment has not raised obvious alarms. Then a real outage occurs, and the system delivers far less runtime than expected. That gap between perceived readiness and actual readiness is where small power disturbances become business disruptions.

For property managers, facilities leaders, IT teams, and owners of tenant-sensitive environments, this is not just a maintenance conversation. It is an operational risk management conversation.

Why battery failures create outsized operational fallout

The episode opens with a realistic scenario: power returns, lobby lights come back, but card readers, HVAC controllers, and tenant-critical equipment begin failing or behaving unpredictably. From the tenant perspective, the root cause barely matters. What they experience is slower elevators, failed badge access, unstable services, and delayed recovery.

That matters because tenant trust erodes quickly when core building systems feel unreliable. In healthcare or clinically adjacent environments, the stakes are even higher. In commercial real estate, these incidents can affect occupant satisfaction, operations teams, and vendor coordination all at once. The technical issue may begin with battery capacity loss, but the business effect shows up as downtime, frustration, and reputational damage.

The panel’s argument is clear: if the loss of UPS runtime affects tenant operations, safety systems, or clinical workflows, then batteries must be managed as critical assets rather than commodity consumables.

What degrades a UPS battery bank faster than expected

Michael highlights temperature as the leading factor in battery lifespan. That alone should change how many teams think about battery rooms and closets. If the ambient environment drifts above recommended conditions, expected life can fall much faster than the replacement plan assumed.

But the discussion goes further than room temperature. The speakers identify several failure drivers that often escape day-to-day attention:

• Improper float voltage, which can accelerate internal corrosion
• Frequent cycling, which consumes battery capacity more quickly
• Humidity and environmental conditions that affect long-term health
• High-resistance intercell connections
• Single weak cells in a series string that drag down the full bank

This matters because many building teams still rely too heavily on superficial indicators. A UPS may show normal status while battery health is already compromised. That is why the panel stresses hands-on verification methods such as conductance testing or internal resistance measurement. These approaches catch deterioration earlier than a generic runtime estimate or a status LED ever will.

The same principle applies to spares. Replacement batteries are not automatically good simply because they are unused. The episode includes an example of a spare that lost significant life while sitting in hot storage. That one detail exposes a broader truth: backup power resilience depends just as much on storage discipline and lifecycle handling as it does on buying the right hardware.

The false choice between monitoring and replacement schedules

Many organizations frame UPS lifecycle planning as a financial tradeoff. Either install telemetry and replace only what data says is failing, or stick to a fixed replacement schedule and keep budgeting simple. The episode rejects that binary.

James makes an important operational point: monitoring without process is dangerous. Sensors can fail. Dashboards can be ignored. Alerts can go unread when nobody owns the response. In those cases, monitoring becomes an expensive layer of false reassurance.

On the other side, fixed interval replacement may be easy to budget, but it can also be blunt and inefficient. In a cool, low-cycle environment, a full battery string may still be healthy at the replacement date. Replacing it early can waste capital that could have been directed toward higher-risk systems.

The more effective model is hybrid. Telemetry helps prioritize and identify emerging issues. Scheduled checks provide structure. Replacement planning stays tied to real risk, not assumptions. Most importantly, the organization defines who receives alerts, who approves replacement, and what happens when a threshold is crossed.

That last part is where many programs fail. The battery may be degrading, but the bigger failure is organizational indecision.

Facilities, IT, and vendors all have a role

Another strong takeaway from the episode is that UPS health sits at the intersection of facilities and IT. Neither team can manage the risk alone.

Facilities should own the environmental conditions, physical inspection routines, maintenance coordination, and spare storage practices. IT should own the dependency map: which devices and systems must remain online, what acceptable runtime looks like, and which outages would directly affect tenants, safety, or clinical services.

Vendors can provide testing and replacement support, but the panel warns against vague maintenance language in contracts. “Maintenance included” is not a control framework. If contracts do not specify testing methods, cadence, report delivery, response timing, and replacement triggers, then critical information often ends up trapped in a vendor portal or scattered across email threads.

The speakers share a practical example of this breakdown. A site had annual runtime testing, but the records lived only in the vendor’s system. When a string later failed, there was no shared operational history. Procurement, facilities, and the vendor each saw the issue differently. What should have been a straightforward maintenance event turned into a dispute over evidence and responsibility.

The solution was not complicated. Export reports into the CMMS. Assign a battery health owner. Track measurable metrics. Document installed strings and spares together. In other words, make battery health visible inside the organization instead of outsourcing all memory to a vendor.

What a right-sized UPS battery program looks like

The episode offers a practical framework that building teams can apply without overcomplicating the budget.

For lower-risk, non-critical loads, a scheduled replacement cycle with periodic spot checks may be enough. But for higher-risk systems, especially those supporting tenant safety, badge access, clinical workflows, or other operationally critical functions, the recommendation is stronger:

• Use continuous telemetry
• Perform verification testing on a regular cadence
• Keep at least one full spare string on site
• Store that spare properly in a cool, charged condition
• Exercise the spare under load every six months
• Maintain spare records in the same log as the installed string

This is where operational maturity shows. A spare that sits untouched for years is not a resilience plan. It is a line item. Resilience comes from knowing the spare is viable, accessible, and tied into a process people can execute under pressure.

A simple checklist with real impact

One of the most useful parts of the conversation is the concrete checklist property managers can put into practice immediately. The panel recommends:

• Daily alarm review and temperature checks
• Weekly review of runtime trends and drift
• Monthly conductance or internal resistance logging against baseline
• Semiannual spare-string exercise under load
• Annual full-load runtime testing with reports stored in CMMS

Just as important, they recommend predefined escalation paths. If battery health crosses a trigger overnight, everyone should already know who is contacted, who can approve emergency replacement, and how the team communicates internally and externally. That avoids the worst kind of outage delay: waiting on organizational decisions while systems remain at risk.

Vendor expectations should be specific, not implied

The speakers also give listeners three clear demands to make of vendors:

• Document exact test protocols, frequencies, and report delivery requirements
• Define replacement obligations using measurable metrics like conductance thresholds
• Provide on-site spares or same-day provisioning guarantees for critical banks

They add one more high-value practice: run a yearly tabletop exercise for UPS failure. Walk through who gets notified, how spares are swapped, how tenant communication works, and where authority sits if replacement is needed outside the normal budget process. These exercises often expose ownership gaps faster than any policy document.

Backup power should be managed like a program, not purchased like a product

The final takeaway from this episode is especially relevant for modern buildings. Backup power only does its job when the surrounding operating model is mature. Monitoring helps prioritize action. Hands-on checks verify real health. Properly maintained spares compress recovery time. Clear ownership removes hesitation when conditions deteriorate.

That is the difference between having a UPS and having a reliable backup power program. If your building supports tenant-critical services, access control, life-safety-adjacent systems, or clinical operations, it is worth asking the same question raised in the episode: what breaks if this goes down?

The answer should drive your replacement horizon, your monitoring investment, your spares plan, and your contracts. If you want a more structured starting point, listen to the full episode and use it to benchmark how your facilities, IT, and vendor workflows handle battery lifecycle risk today. A little routine discipline now can prevent a much larger tenant-facing disruption later.