Measurement, interpretation, and expert analysis of power quality events — and the harder question that follows: whether the event actually caused the damage attributed to it.
Most power quality engagements are not really about characterizing the disturbance. Modern meters do that well. They are about attribution — whether a documented event caused the failure being claimed, and whether responsibility sits with the utility, the facility, a neighboring customer, or the equipment itself.
That question is answered with waveform records, equipment withstand capability, and physical failure evidence together. An event that coincides in time with a failure is a starting point, not a conclusion; a voltage sag well within a device's ride-through capability did not damage it, whatever the timestamps suggest.
Where monitoring is needed, PEFG specifies the instrumentation and monitoring points, then interprets the results — which is normally where these engagements succeed or fail. Power quality monitoring produces very large volumes of data, most of it irrelevant to the question, and a monitor placed at the wrong point answers a question nobody asked.
Existing records are often more valuable than new monitoring: utility meter and relay event captures, drive and UPS fault logs, and facility monitoring data frequently already contain the event, and they have the considerable advantage of being contemporaneous rather than recreated after the dispute began.
PEFG publishes free power system calculators at powerengcalc.com, including voltage drop, motor starting, and transformer thermal life. Those are for engineering estimation; a power quality investigation requires measurement and analysis of the actual system.
A plant records a 62% voltage sag lasting 4.5 cycles. Two hours later a drive fails. The claim asserts the sag destroyed the drive.
Detection is the easy half; the monitor already did it. Attribution is the dispute. A 62% sag for 4.5 cycles sits in a specific region of the ITI curve and of SEMI F47, and equipment meeting either is expected to ride it through. If the drive was specified to ride through it and did not, the more probable explanation is that the drive did not meet its own specification — which is a product claim against the manufacturer, not a service claim against the utility.
The two-hour gap is the other problem. Electrical damage from a sag is essentially immediate: undervoltage trip, DC bus collapse, or component failure occurs during or within cycles of the event. A failure two hours later is more consistent with a thermal or mechanical progression that was already underway, and a teardown will usually say which. Establishing that the sag occurred and establishing that the sag caused the damage are entirely different evidentiary burdens, and only the second one decides the case.
Where the suspect event is a voltage sag caused by starting a large motor rather than by a utility fault, the motor starting calculator at PowerEngCalc estimates the depth and duration of the resulting sag from the machine and source data, which is often enough to confirm or eliminate the on-site theory before a monitor is ever installed. The voltage drop calculator covers the steady-state case where the complaint is chronic low voltage rather than a discrete event.
Questions that come up before a retention decision, answered by the engineer who would do the work.
Sometimes, and the honest answer in many matters is no. Proving causation requires three things to line up: a recorded event of sufficient severity, an equipment immunity specification the event actually exceeded, and a physical failure mode consistent with that specific electrical stress. Where all three align, the opinion is strong. Where the event is inside the ITI or SEMI F47 ride-through envelope, or the failure mode indicates a thermal or mechanical progression rather than an electrical transient, the attribution fails — and it is better to know that before an expert designation than after.
IEEE 519 allocates it in two directions. The customer is responsible for limiting the harmonic current injected into the utility system, with limits scaled by the ratio of short-circuit capacity to load current. The utility is responsible for maintaining voltage distortion at the point of common coupling within limits, given customers who meet their current limits. Most harmonic disputes turn on measurement location and on whether the load actually present matches the load the allocation was based on. Both are answerable from data if the monitoring was set up correctly.
IEEE 1159 defines them, and the distinction matters because the damage mechanisms differ. A sag is a short-duration reduction in RMS voltage, typically 10 to 90 percent of nominal for half a cycle to a minute — the most common cause of production loss and the least likely cause of physical damage. An interruption is a complete loss of voltage. A transient is a sub-cycle event, either impulsive such as a lightning surge or oscillatory such as a capacitor switching event. Loose use of the word 'surge' to describe all four is the most common source of confusion in power quality claims.
No. A monitor records what happened at the monitor's location; it says nothing on its own about where the disturbance originated. Sags recorded at a customer facility are frequently caused by on-site events — large motor starting, an internal fault, capacitor switching, or a downstream breaker operation — and the recorded waveform often distinguishes an upstream from a downstream source. Determining direction requires the waveform capture and the facility configuration, not the summary event table.
Recorder buffers vary from days to a few months depending on configuration and trigger frequency, and utility event records follow their own retention schedules that are typically not long. Preserve the raw waveform captures rather than the summary report, along with the monitor's configuration and calibration records, and request the utility's feeder event history in writing early. Summary reports discard the waveform detail that makes attribution possible, so a case built on a summary table alone is usually a case that cannot be finished.
Attribution is the hard part. Correlation in time is not causation, and the waveform usually settles it either way.