The Hidden Surge: How Power Quality Undermines Building Tech

Why power quality problems are easy to miss

This episode of Built, Wired & Secured focuses on a category of building technology issues that rarely look dramatic at first: power quality problems. Instead of a full outage or a blown breaker, the discussion centers on the quieter failures that create operational drag over time. A brief voltage sag, a fast transient, harmonic distortion, or a grounding issue can show up as intermittent badge reader resets, unexplained BAS controller reboots, drifting sensors, strange metering behavior, and shortened equipment life.

The episode opens with a practical example: a single brief voltage sag caused badge readers to reset intermittently for two days, leaving tenants locked out during morning deliveries. That framing sets the tone for the conversation. The point is not that every weird behavior in a building comes back to power quality, but that teams often spend too much time chasing symptoms before they consider it as a root cause.

Common power quality terms translated into real operational impact

Rather than staying abstract, the episode makes the core terms usable for facilities and operations teams:

• Voltage sag: a short drop in voltage, often tied to something like a motor start
• Transient: a very fast spike caused by switching events or lightning
• Harmonics: waveform distortion created by nonlinear loads
• Grounding faults: noisy or unstable reference conditions that can affect sensitive equipment

The practical takeaway is that each type of issue presents differently in the field. Teams may see controllers reboot randomly, access systems misbehave, temperature complaints rise, or data from sensors and metering start looking unreliable. In one example from the episode, HVAC controllers restarted around 4:30 a.m. for weeks. Maintenance initially chased thermostats, but the real cause was a nearby motor start sending transients down the line.

What teams can do before buying expensive equipment

A major theme in the episode is that useful detection does not have to start with a major capital purchase. The guests recommend beginning with the tools many teams already have or can deploy quickly at low cost.

• Review managed UPS and intelligent PDU logs for input voltage and event history
• Use portable clamp meters or handheld analyzers for spot checks during suspected events
• Install inexpensive waveform recorders at critical racks or control panels to establish a baseline
• Align timestamps across BAS, access control, UPS logs, and help desk tickets
• Observe the site during known problem windows instead of relying only on after-the-fact reports

That last point matters. If incidents cluster around certain hours, motor starts, or tenant activity, teams can often reproduce or at least correlate the pattern. The episode emphasizes that a controlled motor start test or simply being present in the mechanical room during a suspect period can reveal more than a rushed troubleshooting session later in the day.

Monitoring versus hardening: where quick fixes fit

The discussion also tackles a familiar tension in building operations: should a team invest first in monitoring, or go directly to hardening measures like UPS units, isolation transformers, or power conditioners?

The answer in the episode is nuanced. There are cases where immediate protection makes sense, especially for life safety systems, elevators, and critical server gear. A single UPS on a sensitive rack or isolating a panel can serve as a stopgap that reduces tenant pain and buys time. But the guests warn that protection without diagnosis can simply hide an upstream issue that continues to get worse.

The operating model they recommend is layered:

• Maintain and tighten existing infrastructure
• Monitor long enough to collect evidence
• Harden surgically where the data points

That approach helps teams avoid broad capital spending before they understand the real cause.

A short triage checklist teams can use this week

One of the most useful parts of the episode is the practical checklist for immediate action. The recommended first steps are straightforward:

• Correlate timestamps across BAS logs, access control, UPS event histories, and help desk tickets
• Take spot voltage readings at the affected panel and at the device input during suspected events
• Pull event history from PDUs or UPS units right away

If anomalies repeat, the next step is escalation to continuous monitoring or a power quality survey. The guests add several operational follow-ups as well:

• Inspect grounding and connection tightness during the next preventive maintenance round
• Schedule a controlled motor start test if large motors are suspected
• If tenant activity appears to correlate with the issue, ask about staggered starts while data is being collected

This is practical advice because it balances incident response with evidence gathering. It does not assume a blank-check budget, but it also does not treat recurring anomalies as random noise.

Two examples that show why evidence matters

The episode closes the loop with two short project examples. In the first, a high-rise owner wanted isolation transformers for an entire elevator bank after intermittent elevator control resets. Temporary waveform loggers were installed at the elevator panels and main feeders. The data showed harmonic spiking when a tenant's new data rack powered up. That shifted the solution from a large building-wide capital project to a targeted fix involving UPS and demand management in the tenant space.

In the second example, a medical campus experienced repeated controller failures. Monitoring and commissioning checks led to corroded neutral connections and outside switchgear that required capital repair. Because the team had real data, they could prioritize the outage window and reduce patient impact during remediation.

Those cases reinforce the central lesson of the episode: collect enough evidence to separate localized, surgical fixes from true infrastructure-level problems.

Key lesson for owners, facilities teams, and IT leaders

The episode argues that power quality should be treated as part of operational resilience, not as an edge-case electrical concern. If tenant access, comfort, elevators, controls, or critical services are affected, the issue deserves escalation. If the impact is limited and localized, monitoring and maintenance may be the right near-term path. Either way, the response should match the consequence.

The final message is simple and useful: small, repeatable checks and clear communication beat reactive chaos. Preventive maintenance, targeted monitoring, and surgical capital work are not competing ideas. They work best together when teams stop guessing and start correlating what the building is already telling them.

Power quality is a building operations problem, not just an electrical one

When people think about power issues in a commercial building, they usually picture something obvious: a blackout, a tripped breaker, or a visible equipment failure. That is not what this episode is about. The conversation in The Hidden Surge: How Power Quality Undermines Building Tech focuses on the quieter, cumulative problems that degrade operations without announcing themselves clearly.

A brief voltage sag may not make headlines, but it can reset badge readers just enough to disrupt tenant access. A transient can cause a controller to reboot randomly. Harmonics can distort performance over time. Grounding faults can create unstable behavior that teams mistake for a device issue, a controls issue, or even a user complaint. The result is the same: operations teams spend time chasing symptoms while the real cause stays hidden.

That is why this episode matters for owners, facilities leaders, and IT teams. Modern buildings rely on tightly interconnected systems: access control, building automation, metering, HVAC controls, network racks, and tenant-facing services. When power quality degrades, those systems often fail in small, inconsistent ways. That inconsistency is exactly what makes the problem expensive.

What power quality problems look like in the real world

The episode translates technical language into practical consequences. A voltage sag is described as a short drop in voltage, often tied to events like motor starts. A transient is a very fast spike, such as one caused by switching or lightning. Harmonics distort the waveform because of nonlinear loads. Grounding faults create a noisy reference that sensitive equipment does not tolerate well.

Those definitions are useful, but the operational examples are what make them stick. The guests describe scenarios that sound familiar to anyone responsible for a building or distributed facility environment:

• Controllers rebooting without a clear pattern
• Sensors drifting or producing questionable readings
• Metering behaving strangely
• Badge readers or access systems resetting intermittently
• Tenants reporting comfort swings that maintenance cannot tie to a simple equipment fault

One example in the episode stands out: HVAC controllers were restarting around 4:30 a.m. for weeks, and maintenance initially chased thermostats because that was the symptom tenants felt. The real cause turned out to be a motor start in a nearby mechanical room sending transients down the line. That is an important lesson. The visible complaint is not always close to the electrical cause.

Why teams often miss the root cause

Power quality issues hide because they rarely present as a single obvious failure. Instead, they show up as intermittent behavior spread across systems that are owned by different teams. Facilities may see temperature complaints. Security may see badge reader resets. IT may see gear rebooting or UPS events. Help desk may log tickets that seem unrelated.

If nobody aligns those events by time and context, the organization never sees the pattern. Each team works its own incident queue, and the underlying issue remains invisible.

That is why the episode repeatedly comes back to correlation. If unexplained reboots, drifting sensors, or odd access events are happening at similar times of day, during equipment starts, or around specific tenant activity, power quality should move onto the checklist quickly. Not because it is always the answer, but because leaving it off the list prolongs guesswork.

You do not need a major budget to start detecting problems

One of the strongest parts of the episode is its practical stance on detection. The guests do not assume every building can justify a full power analyzer program on day one. Instead, they recommend using what is already available and adding targeted low-friction tools where needed.

The first layer is often already in place:

• Managed UPS units with event history
• Intelligent PDUs that log input voltage
• BAS logs
• Access control logs
• Help desk ticket timestamps

Those sources can already reveal a lot if teams pull and align them. Beyond that, portable clamp meters, handheld analyzers, and inexpensive waveform recorders can provide spot-check evidence or short baselines at critical racks and control panels.

The episode also highlights something simple but often overlooked: physically observing the site during problem hours. If incidents seem to occur when mechanical systems start up or when tenant equipment powers on, being present during those windows can expose a pattern faster than retrospective analysis alone. A controlled motor start test can be especially useful when large motors are suspected.

Monitoring first or hardening first?

This is the budget question many owners and operators face. When a system is causing pain now, there is pressure to implement a visible fix fast. A UPS on a sensitive rack, a panel isolation step, a power conditioner, or an isolation transformer can sound like decisive action.

The episode does not reject those options. In fact, it makes clear that some systems deserve immediate protection, especially life safety systems, elevators, and critical server gear. If the consequence of failure is high, waiting too long for perfect diagnosis can create unnecessary risk.

But the guests are equally clear about the downside of skipping diagnostics. A stopgap can calm the symptom while masking a deeper upstream issue in wiring, grounding, utility feed behavior, or shared building infrastructure. That can turn a manageable issue into a more expensive one later.

The recommended approach is layered and disciplined:

• Start with maintenance and basic inspections
• Monitor long enough to gather evidence
• Harden selectively where the data points

That sequencing matters. It helps teams avoid broad capital spending driven by anxiety instead of proof.

A practical triage checklist for this week

The episode offers a short, actionable checklist that building and IT teams can use right away:

• Correlate timestamps across BAS logs, access control, UPS events, and help desk tickets
• Take spot voltage readings at the affected panel and at the device input during suspect periods
• Pull event history from PDUs and UPS units immediately after incidents
• Add grounding and connection checks to the next preventive maintenance round
• Schedule a controlled motor start test if large motors may be involved
• If tenant activity correlates with the problem, discuss temporary staggered starts while data is collected

If the anomalies keep repeating, the next step is not blind replacement. It is a short continuous monitoring campaign or a formal power quality survey focused on the problem point.

That is the discipline this episode promotes: observe, correlate, verify, then intervene.

When data saves money and when capital is unavoidable

The episode includes two examples that show why this approach works. In the first, a high-rise experienced intermittent elevator control resets. The owner wanted isolation transformers for the full elevator bank. Instead of moving straight to a large capital project, the team installed temporary waveform loggers at the elevator panels and main feeders. The logs showed harmonic spiking when a tenant's new data rack powered up. That shifted the solution to the tenant side, where targeted UPS and demand management solved the issue for far less money.

In the second example, a medical campus had repeated controller failures. Monitoring and commissioning checks led to corroded neutral connections and outside switchgear problems that did require capital repair. But because the team had evidence, they could prioritize the outage window and reduce impact on patient operations.

The contrast is the real lesson. Data does not always prove that the cheap fix is enough. Sometimes it confirms that capital work is necessary. Either way, it improves decision quality.

What this means for building resilience

For commercial real estate operators, facilities teams, and IT leaders, the larger message is strategic. Building resilience is not only about uptime during major outages. It is also about reducing the small, repeated disruptions that erode tenant experience, create maintenance churn, and shorten equipment life.

Power quality belongs in that resilience conversation because so many modern building systems are sensitive to subtle electrical instability. If badge readers reset, BAS controllers reboot, sensors drift, or metering looks unreliable, teams should stop treating those as isolated quirks.

They should ask a more useful question: is the building giving us a power quality signal that we are not yet measuring clearly?

This episode argues for a balanced response. Protect critical systems quickly when the consequence justifies it. Use maintenance to eliminate basic issues like loose connections and grounding problems. Run targeted monitoring long enough to collect evidence. Then spend capital surgically rather than broadly.

That approach serves both operations and budgets. It reduces unnecessary replacements, limits tenant disruption, and helps owners make more defensible investment decisions.

Final takeaway

The best operational environments are often the least visible to occupants. People badge in, systems stay online, temperatures remain stable, and nobody thinks about what had to go right behind the scenes. That does not happen by accident. It happens because teams pay attention to weak signals before they become visible failures.

That is the real value of this episode. It reframes power quality from an abstract electrical topic into an operational discipline. Small, repeatable checks. Better log correlation. Clearer communication. Targeted monitoring. Focused hardening. Those are the moves that turn a hidden source of instability into something measurable and manageable.

If your building teams are dealing with unexplained resets, drifting sensors, flaky controls, or tenant complaints that do not line up cleanly with obvious failures, this episode is worth a listen. It offers a practical framework for deciding what to inspect, what to monitor, and where to spend next without guessing first.

Listen to the full episode for the complete discussion and the field-tested checklist that can help your team start troubleshooting power quality issues with more confidence this week.