Show Notes
Why Power Problems Still Break Buildings When the Lights Stay On
This episode of Built, Wired & Secured focuses on a failure mode that many owners, facilities leaders, and technology teams underestimate: operational downtime caused not by a total loss of power, but by poor power quality and badly managed power transfers. The opening scenario sets the tone. A storm hits at 2 a.m., the generator starts, and the automatic transfer switch moves the building over as designed. But access controllers, elevator controllers, and HVAC controls reboot into fault states. Power is technically available, yet the building is functionally impaired.
That distinction drives the entire discussion. Tenants do not judge resilience by whether electricity is present at the panel. They judge it by whether they can badge in, move through the building, run business systems, and keep critical operations online. The episode makes the case that reliable building operations depend on understanding how electrical events affect operational technology in the real world.
What Actually Causes These Hidden Failures
The conversation starts with the root causes that often sit between electrical design intent and operational reality.
- Harmonics from modern loads: LED drivers, variable frequency drives, and server power supplies create waveform distortion. Even when nominal voltage looks acceptable, those distorted waveforms can stress neutrals and UPS components.
- UPS sizing mismatches: A UPS may be sized on paper for runtime under steady-state conditions, but still fail under actual operating conditions if it cannot handle inrush current or additional heat caused by harmonic loading.
- Transfer timing issues: Generator-backed systems can still create disruptive events depending on how the transfer is executed. Sensitive devices may not tolerate voltage sags, frequency shifts, or phase angle changes during switching.
- Neutral distortion and unbalanced nonlinear loads: These conditions can create overheating, odd phase-to-phase voltage behavior, and intermittent trips that are difficult to diagnose.
One of the most important insights in the episode is that these failures are often not dramatic. They do not always look like a catastrophic outage. Instead, they appear as controllers that reset unexpectedly, protective devices that trip without an obvious cause, or systems that become flaky after a transfer event. That is what makes them operationally dangerous. Troubleshooting can consume days while tenants feel the impact immediately.
Soft Transfer vs. Hard Transfer
A major portion of the episode breaks down transfer dynamics in practical terms. The discussion compares soft transfer and hard transfer approaches and explains why those choices matter more than many teams realize.
- Soft transfer: Attempts to synchronize utility and generator power before switching, reducing sudden changes in voltage and frequency.
- Hard transfer: Disconnects the utility source first and then connects the generator source, which can create voltage sags and phase angle jumps.
The key takeaway is not that one method is universally right, but that design teams and operators need to understand the consequences. Sensitive controllers may interpret transfer disturbances as faults even when backup systems technically performed as intended. Automatic transfer switch settings, sequencing, and actual timing need to be tuned for the loads being served, not just accepted as default.
Centralized UPS vs. Point-of-Load Protection
The episode also explores a practical design tradeoff that directly affects resiliency strategy: centralized UPS plants versus point-of-load UPS deployment.
Centralized UPS plants offer efficiencies and a more consolidated maintenance model. But they can also introduce single points of failure and create more complicated interactions with generator transfers. By contrast, point-of-load UPS units placed at racks or directly at critical devices can better isolate sensitive systems and often handle inrush and harmonics more effectively at the edge.
The downside, as discussed in the episode, is increased capital expense and distributed maintenance responsibility. The recommendation is pragmatic rather than ideological: identify the systems that must remain operational at all costs and give those systems dedicated, tested protection.
- Life safety and tenant-critical systems may justify more sophisticated transfer approaches.
- Edge devices and sensitive electronics may be better served with local UPS coverage.
- Mixed strategies can reduce risk better than one-size-fits-all resiliency designs.
What Facilities and IT Teams Should Do Differently
The operational guidance in this episode is especially clear. Rather than chasing vendor hype or overly theoretical design conversations, the discussion stays focused on actions teams can take now.
- Monitor meaningful signals: Do not stop at confirming power presence. Track waveform quality, harmonic content, and UPS input-output anomalies.
- Rehearse transfers: A transfer test should be treated as an operational rehearsal, with live observation of all critical systems and post-transfer validation steps.
- Require sequence documentation: Handover documents should include transfer sequence details and clear ownership responsibilities for vendors and facilities teams.
- Prioritize single points of failure: Maintain a ranked list of systems whose failure would most impact tenants, then protect those systems with local UPS units or isolation transformers where appropriate.
That emphasis on ownership is important. The episode repeatedly points out that resilience depends not just on equipment selection, but on who is accountable for transfer behavior, testing, and ongoing maintenance.
Simple Handover and Testing Steps
Another standout section of the episode is the focus on simple, realistic tests teams can run without specialized lab equipment.
- Schedule a staged transfer test during a low-risk window.
- Observe access control, elevator systems, critical HVAC, and IT edge devices during the event.
- Capture logs from UPS and ATS controllers.
- Confirm that affected controllers reboot cleanly and report back to central management.
- Deploy inexpensive power quality loggers for a week to detect harmonics and sags under normal operating conditions.
- Perform a cold transfer test at least annually to understand how equipment behaves during non-synchronized events.
These recommendations are notable because they turn a complex technical subject into repeatable operational practice. The message is that teams do not need to wait for a major retrofit to improve resilience. They can start by testing what they already have and documenting the results.
A 30-60-90 Day Action Plan
The episode closes with a practical timeline listeners can apply immediately.
- First 30 days: Request ATS and UPS transfer logs from the contractor and clarify who owns transfer sequencing in maintenance agreements.
- Days 30-60: Run a staged transfer rehearsal with observers covering all tenant-critical systems and review the post-transfer logs.
- Days 60-90: Deploy temporary power quality monitoring in known trouble areas and prioritize point-of-load protection for the top three tenant-impacting systems.
Throughout that process, teams are encouraged to document findings and fold them into capital planning. The larger theme is that power resilience should be measurable and repeatable, not assumed.
Final Takeaway
This episode makes a strong case that uptime is not just about having backup power. It is about how clean that power is, how transfers are managed, how sensitive systems behave during disturbances, and whether operations teams have rehearsed the real event before it happens at 2 a.m. For building owners, facilities teams, and IT leaders, the path forward is clear: monitor waveform quality, test transfers under observation, protect the most sensitive systems locally where needed, and make transfer ownership part of handover and maintenance from day one.
Why Backup Power Alone Does Not Guarantee Building Uptime
When building teams talk about resilience, the conversation often starts and ends with a simple question: will the generator come on when utility power fails? This episode of Built, Wired & Secured argues that the better question is far more operational: what happens to critical building systems during the transfer, and how do those systems behave when power quality is less than ideal?
The difference matters. A building can have power and still be operationally down. In the episode’s opening scenario, a storm interrupts the utility feed overnight. The generator starts, the automatic transfer switch changes sources, and on paper the backup sequence works. But a cluster of access controllers and elevator controllers reboots into fault states. Critical HVAC controllers stop responding. Tenants cannot badge in. Elevators go into restricted mode. No one would call that a successful continuity outcome, even though the building never went completely dark.
That is the central theme of the conversation: resilience should be measured by whether the building keeps functioning, not just whether electricity is technically present.
The Hidden Gap Between Electrical Design and Operational Reality
One of the most useful aspects of this episode is how clearly it frames the disconnect between installed infrastructure and day-to-day building operations. Power systems can be designed to meet code, pass commissioning, and still produce disruptive behavior once real-world loads and real-world transfer events come into play.
The discussion explains that many outages experienced by tenants are not total electrical failures. Instead, they are quality and transition problems. A building may ride through a utility event with enough power to keep lights on, yet still lose the systems that make the space usable and safe. Access control, life safety interfaces, point-of-sale systems, network edge equipment, and HVAC controls can all become unstable when waveforms are distorted or transfers are poorly managed.
For property teams and operators, that distinction changes the planning process. It means evaluating resiliency not just at the switchgear level, but at the controller, rack, and endpoint level where operational failure is actually felt.
How Harmonics Create Trouble Even When Voltage Looks Normal
A major cause discussed in the episode is harmonics. Modern buildings rely heavily on nonlinear loads, including LED lighting drivers, variable frequency drives, and server power supplies. These devices distort the electrical waveform in ways that standard voltage readings may not fully reveal.
The operational consequence is that systems can appear healthy while key components are under stress. Harmonics can overload neutrals, increase heat in UPS components, and contribute to instability that only shows up under transfer or surge conditions. That makes them particularly difficult to diagnose after the fact. Teams may see nuisance trips, intermittent faults, or unexplained controller resets without immediately recognizing that power quality is the deeper issue.
The important takeaway is that nominal voltage alone is not enough as a health indicator. If teams only monitor whether power is present, they can miss the conditions that actually cause sensitive systems to fail.
Why UPS Sizing Often Falls Short in Real Conditions
The episode also highlights a common planning error around UPS systems. Many UPS deployments are sized around steady-state runtime requirements, but that does not automatically mean they are ready for real operating conditions. Inrush current, harmonic heating, and actual load behavior during transfer events can push a UPS beyond what its sizing assumptions anticipated.
This is one of the more practical warnings in the discussion. A UPS may look correct on a submittal, but still trip under real load conditions if the design process did not account for startup behavior and waveform distortion. For owners and facilities teams, the lesson is straightforward: runtime calculations are necessary, but not sufficient. The system must be evaluated based on how the connected equipment behaves when power conditions are less than ideal.
Transfer Dynamics Matter More Than Most Teams Realize
The conversation’s breakdown of transfer timing is especially valuable because it translates a technical topic into operational risk. The episode compares soft transfer and hard transfer in plain language.
A soft transfer attempts to synchronize generator and utility sources before switching. That reduces abrupt shifts in voltage and frequency and generally makes the event less disruptive for sensitive systems. A hard transfer, by contrast, disconnects one source before connecting the other. While simpler and often less expensive, it can create voltage sags and phase angle jumps that some controllers interpret as faults.
The point is not that every building needs the most advanced and expensive transfer strategy. The point is that transfer method, ATS settings, and actual timing should be treated as system-level decisions with direct operational consequences. If those settings are not tuned to the loads they serve, the result can be nuisance trips and silent failures that emerge only during real transfer events.
The Slow Failures That Waste the Most Time
Another strength of this episode is its focus on how these problems actually show up in the field. They are often not dramatic. Instead of a clean failure that is easy to identify, teams see slow, flaky issues: breakers heating up, intermittent tripping, odd voltage behavior, or equipment that resets unpredictably. In some cases, sensitive devices may even corrupt firmware during transients.
Those are the failures that consume time, because troubleshooting stretches across multiple disciplines. Electrical contractors may see acceptable voltage at one moment. IT teams may see devices offline. Facilities teams may only know that tenants are frustrated and systems are unreliable. Without documentation, monitoring, and rehearsal, the root cause can remain unclear long enough to become a repeated operational problem.
Choosing Between Centralized and Distributed Resiliency
The episode also tackles the practical tradeoff between centralized UPS plants and point-of-load UPS protection. Centralized UPS systems offer efficiency and consolidated maintenance, but they also create single points of failure and can add complexity when combined with generator-backed transfer sequences.
Point-of-load UPS devices, installed at racks or directly at critical systems, can isolate risk more effectively and often handle sensitive electronics better during transfer events. The downside is greater capital cost and the burden of maintaining many smaller units instead of one centralized platform.
The most useful recommendation from the discussion is not to treat this as an all-or-nothing design choice. A mixed strategy is often the smarter path. Life safety and tenant-critical systems may warrant soft transfer strategies and higher levels of central planning, while edge devices and vulnerable controls may benefit from local UPS coverage. What matters is identifying which systems truly cannot afford disruption and protecting them accordingly.
What Facilities and IT Teams Should Start Doing Now
The operational advice in the episode is refreshingly direct. First, monitor meaningful signals. That means looking beyond a binary power-present status to waveform quality, harmonic content, and UPS input-output anomalies.
Second, rehearse transfers. A transfer test should not be treated as a paperwork exercise. It should be run like an operational event, with observers watching critical systems and validating post-transfer recovery. Access control, elevators, critical HVAC, and IT edge infrastructure should all be checked explicitly.
Third, require transfer sequence documentation at handover. Ownership matters. If no one clearly owns sequencing, testing, and follow-up, the building inherits risk that may not surface until the worst possible time.
Fourth, maintain a prioritized list of tenant-impacting single points of failure and protect them with local UPS or isolation strategies where needed.
Simple Testing That Creates Real Insight
The episode offers a practical testing framework that most teams can execute without specialized lab equipment. A staged transfer test during a low-risk period can reveal whether critical systems reboot cleanly. Logs from UPS and ATS controllers should be captured and reviewed. Inexpensive power quality loggers can be deployed for a week to identify harmonics and sags during normal operations. And a cold transfer test should be performed at least annually so teams understand how systems behave during non-synchronized events.
These recommendations matter because they move the conversation from theory to evidence. Rather than assuming the system will behave correctly, teams can observe what actually happens and make informed improvements.
A Practical 30-60-90 Day Plan
The episode closes with an action plan that is easy for owners and operators to adopt. In the first 30 days, request ATS and UPS transfer logs and confirm who owns transfer sequencing in maintenance agreements. In the next 30 days, schedule and observe a staged transfer rehearsal covering all tenant-critical systems. In the following 30 days, deploy temporary power quality monitoring in known trouble areas and prioritize point-of-load protection for the top three systems most likely to affect tenants.
Most importantly, document the results and feed them into capital planning. That turns resilience from an abstract goal into an operational program.
Final Perspective
This episode makes a practical and timely point: power strategy is not complete when equipment is installed. It is complete when building teams understand how systems behave during transfers, know which loads are most vulnerable, and can prove that critical operations recover the way they are supposed to. For owners, facilities leaders, and technology teams, that is the difference between having backup power on paper and delivering measurable uptime in the real world. If this topic is relevant to your properties or portfolios, this episode is worth a full listen for the testing ideas and operational questions alone.