Show Notes
Why power quality deserves more attention
This episode of Built, Wired & Secured focuses on a problem that rarely gets the same attention as a full outage but often causes more confusing day-to-day disruption: power quality. Instead of dramatic blackouts, the discussion centers on voltage sags, transients, harmonics, and grounding faults that quietly undermine building systems over time.
The episode opens with a practical example: a brief voltage sag causing badge readers to reset intermittently for two days. There were no blown breakers and no major outage event, yet tenants were locked out during morning deliveries. That framing makes the core point clear: small electrical disturbances can create very real operational problems when they affect access control, HVAC controls, metering, and other building technologies.
Common power quality issues explained in operational terms
The conversation breaks down several power quality terms into plain language:
- Voltage sag: a short drop in voltage, often tied to events like motor starts.
- Transient: a very fast spike caused by switching events or lightning activity.
- Harmonics: waveform distortion created by nonlinear electrical loads.
- Grounding faults: noisy or unstable electrical references that create erratic system behavior.
Rather than staying theoretical, the episode connects each issue back to what operations teams actually see in the field: controllers rebooting unexpectedly, sensors drifting, and metering data acting strangely. One example described HVAC controllers restarting at 4:30 a.m. for weeks while maintenance teams chased thermostat issues, only to discover that motor starts in a nearby mechanical room were sending transients down the line.
What teams can do before buying expensive tools
A major theme in the episode is that teams do not need to begin with a large capital purchase. Instead, the guests recommend low-friction detection steps that use tools and logs many facilities and IT teams already have.
- Start with intelligent PDUs and managed UPS units that log input voltage and event history.
- Use portable clamp meters or handheld analyzers for spot checks during suspected events.
- Place inexpensive waveform recorders at critical racks or control panels to establish a baseline.
- Align timestamps across BAS, access control, UPS histories, and help desk tickets.
- Observe the site during problem hours to correlate equipment starts, tenant activity, and anomalies.
The episode stresses that useful insight often comes from correlation, not from buying the most sophisticated analyzer first. If an incident happens at the same time every morning, or when large motors start, or when a tenant powers up equipment, that pattern can point teams toward the real issue faster than guesswork.
Monitoring versus hardening
The discussion also explores the tradeoff between monitoring the problem and trying to harden systems immediately. The guests describe quick fixes such as installing a UPS on a sensitive rack or isolating a panel as legitimate stopgaps, especially when tenant experience or critical services are already being affected.
At the same time, they warn that protection without diagnostics can hide a bigger upstream issue. A UPS may calm complaints in the short term, but it can also mask wiring problems, utility issues, or broader electrical instability that will continue to worsen if nobody measures them.
The practical guidance is a layered response:
- Maintain and tighten what can be addressed during normal operations.
- Monitor long enough to collect reliable evidence.
- Protect high-impact systems immediately when necessary.
- Harden surgically after data shows where the real problem lives.
A short triage checklist for this week
The episode offers a simple triage process that teams can start using right away:
- Correlate timestamps across BAS logs, access control systems, UPS events, and help desk tickets.
- Take spot voltage readings at the affected panel and at the device input during suspected event windows.
- Pull event history from PDUs and UPS units immediately after symptoms appear.
- Inspect connection tightness and grounding during the next preventive maintenance round.
- Schedule a controlled motor start test if large motors are suspected.
- If tenant behavior lines up with incidents, discuss staggered equipment starts while data is collected.
If anomalies continue, the recommendation is to escalate to a short monitoring campaign, including roughly two weeks of waveform logging at the problem point, before jumping to major capital fixes.
Two field examples that changed the outcome
One of the strongest parts of the episode is the contrast between two real-world examples.
In a high-rise with intermittent elevator control resets, the owner initially wanted isolation transformers for the full elevator bank. Temporary waveform logging at elevator panels and main feeders showed that harmonic spikes were appearing when a tenant’s new data rack powered up. Because the issue was isolated to tenant activity, the fix became targeted UPS deployment and demand management in the tenant space, avoiding a far more expensive building-wide solution.
In the second example, a medical campus was experiencing repeated controller failures. Monitoring and commissioning checks traced the issue to corroded neutral connections and outside switchgear that required capital repair. The difference was that the team had evidence, allowing them to prioritize the outage window and reduce patient impact during the repair.
The business value of treating power quality as an operational issue
The larger takeaway is that power quality is not just an electrical engineering concern. It directly affects tenant experience, maintenance efficiency, service reliability, and capital planning. Teams that treat unexplained resets, drifting sensors, and strange access events as isolated device failures can spend weeks replacing the wrong components. Teams that correlate logs, test during suspect hours, and monitor strategically can identify the true source faster and spend money more effectively.
The episode closes with a clear framework: protect what has high consequence, monitor what is uncertain, and avoid full-scale capital work until the evidence supports it. That approach helps facilities, operations, and IT leaders reduce disruption without overreacting or overspending.
The hidden infrastructure problem behind flaky building systems
When building technology fails, most teams look first for a visible outage, a failed device, or a software issue. That makes sense. A blown breaker, a dead controller, or a network interruption is easy to spot and easy to explain. Power quality problems are different. They sit in the background, often for weeks, quietly degrading performance until the symptoms start spreading across systems.
That is the focus of this episode of Built, Wired & Secured: how power quality issues such as voltage sags, transients, harmonics, and grounding faults undermine building operations in ways that are easy to misdiagnose.
The episode starts with a simple but memorable example. A brief voltage sag causes badge readers to reset intermittently for two days. There is no major outage. No breakers trip. Nothing dramatic shows up at first glance. But tenants cannot get into their suites during morning deliveries. What looks like a minor electrical event turns into a real operational problem with tenant impact, support load, and lost confidence.
That framing matters because it reflects how these issues usually appear in the real world. They do not arrive as neat electrical theory. They show up as confusing behavior at the system level.
How power quality problems actually appear in operations
One of the most useful parts of the conversation is the way it translates technical terms into operational consequences.
A voltage sag is described as a short drop in voltage, often caused by something like a motor start. A transient is a very fast spike associated with switching events or lightning. Harmonics distort the waveform because of nonlinear electrical loads. Grounding faults create a noisy reference point that can make equipment unstable.
For operations teams, that means something more practical:
- Controllers reboot for no obvious reason.
- Sensors begin drifting out of expected range.
- Metering behaves inconsistently.
- Access control acts intermittently.
- Tenant comfort complaints increase even though thermostats seem fine.
The episode gives a strong example of this disconnect. HVAC controllers were restarting at 4:30 a.m. for weeks. Tenants complained about temperature swings. Maintenance spent time chasing thermostat issues. The real problem turned out to be motor starts in a nearby mechanical room sending transients down the line.
That is the danger of hidden surge and power quality issues. The symptom appears at the edge, but the cause lives somewhere upstream. If teams only troubleshoot the device that is misbehaving, they can lose a lot of time and money without fixing the root problem.
Why teams should put power quality on the checklist early
The episode makes a strong case for adding power quality to the standard checklist whenever a team sees unexplained reboots, drifting sensors, strange BAS behavior, or intermittent control issues. Not because power quality is always the answer, but because it is often ignored for too long.
That matters in commercial real estate and mixed-use environments where multiple systems share infrastructure and where tenant actions can affect building operations in indirect ways. A new rack powering up in one space, a large motor starting in another, or a grounding issue that only surfaces during specific load conditions can all create symptoms far away from the source.
What makes this practical is the recommendation not to begin with a big purchase. The guests repeatedly emphasize low-friction detection before major capital decisions.
What you can do before buying a full analyzer
Many teams assume that meaningful power quality work begins with specialized instrumentation and a large budget. The episode pushes back on that assumption. In many cases, the first step is making better use of data you already have.
That includes:
- Managed UPS event histories
- Intelligent PDU voltage logs
- BAS logs
- Access control timestamps
- Help desk ticket timing
Simply aligning those timestamps can reveal patterns that would otherwise stay hidden. If badge reader resets, BAS alarms, and UPS events all cluster during the same morning window, that is useful evidence. If incidents line up with a tenant’s startup routine or a scheduled mechanical sequence, that changes the troubleshooting path immediately.
The episode also recommends portable clamp meters, handheld analyzers, and inexpensive waveform recorders at critical racks or control panels. These tools provide spot checks and baseline visibility without forcing a full building-wide study on day one.
Another practical point is direct observation. Watching the site during suspect hours, sitting in the mechanical room during equipment startup, or running a controlled motor start test can expose patterns that logs alone may not fully explain.
Monitoring versus hardening is not an either-or decision
One of the most balanced parts of the discussion is the tradeoff between monitoring and hardening. Some teams want to measure first. Others want a quick fix because tenants are already feeling the impact. The episode argues that both instincts can be valid if they are applied in the right order and with the right scope.
A quick stopgap might mean putting a UPS on a sensitive rack or isolating a problem panel. That can reduce immediate disruption and buy time. But it should not become a substitute for diagnosis. If a UPS is only masking a larger utility, wiring, or grounding issue, the underlying risk is still there.
The recommendation is a layered response:
- Protect high-consequence systems immediately when needed.
- Inspect and maintain connections, grounding, and panel conditions.
- Monitor upstream to gather evidence.
- Make capital decisions only after the data points to the real source.
That approach matters because it keeps teams from swinging between two expensive extremes: doing nothing until the issue gets worse, or overbuilding the fix before they understand the problem.
A practical triage checklist for facilities and IT teams
The episode offers a short checklist that leaders can put into use right away.
First, correlate timestamps across BAS, access control, UPS logs, and help desk tickets. Second, take spot voltage readings at the affected panel and at the device input during the suspected event window. Third, pull event histories from PDUs and UPS units as soon as symptoms appear.
From there, add a grounding and connection inspection to the next preventive maintenance cycle. If large motors are suspected, schedule a controlled motor start test. If tenant behavior appears to correlate with the issue, communicate temporary procedures such as staggered starts while the team collects evidence.
If the anomalies continue, move to a short monitoring campaign. The specific recommendation in the episode is roughly two weeks of waveform logging at the problem point. That creates enough evidence to understand repeat patterns without committing prematurely to a full-scale capital project.
Why field data changes spending decisions
The two closing examples show why this disciplined approach matters.
In one high-rise, intermittent elevator control resets led the owner to consider isolation transformers across the entire elevator bank. Temporary waveform logging revealed that harmonic spikes appeared when a tenant’s new data rack powered up. Instead of a much larger building-side project, the fix became targeted UPS protection and demand management in the tenant space.
In another case, a medical campus experienced repeated controller failures. Monitoring and commissioning checks led the team to corroded neutral connections and outside switchgear that did require capital repair. The key difference was not whether capital was necessary. It was that the team had evidence, so they could prioritize the outage window and minimize patient impact.
That is the real value of monitoring. It does not always prevent capital work. It makes sure capital work is directed where it belongs.
Treat power quality as part of resilience, not a specialty issue
The biggest takeaway from the episode is that power quality should be treated as part of operational resilience. It affects tenant experience, equipment life, maintenance efficiency, and the reliability of building systems that people depend on every day.
When teams ignore it, they often end up replacing edge devices, chasing false causes, or making rushed capital decisions. When they treat it as an actionable part of operations, they can align logs, run targeted tests, protect critical systems, and harden only where the evidence supports it.
The closing advice is simple and useful: ask what breaks if this goes down. If the answer is tenants or critical services, escalate quickly. If the impact is local and limited, monitor and maintain while you gather evidence. Match the response to the consequence.
If your team is dealing with unexplained resets, drifting sensors, inconsistent access events, or recurring building-system oddities, this episode offers a practical framework for what to do next. Listen to the full conversation for the triage steps, field examples, and guidance on choosing between monitoring, maintenance, and surgical capital fixes.