How to Check SPD Status Indicators in a Panel
A surge-protective device is the only component in a panel whose job is to sacrifice itself, and it does so silently: a panel whose SPDs died in last month's storm looks identical to a protected one, right up until the next surge arrives with nothing in its way. That is why SPDs carry status indicators, and why walking a site's panels and actually reading them is a maintenance task rather than a formality. This page covers what the indicators are telling you, how to check the different SPD types found across power and signal circuits, and how to get SPD status out of the panel and into the monitoring system where it belongs.
Check SPD Status Indicators in one line: To check SPD status indicators, walk every protected panel and read each device's indication - typically a colored window, flag, or LED whose healthy and failed states are defined on the device's own label or datasheet - and treat any failed, ambiguous, or dark indication as an unprotected circuit to be corrected. Check every layer, not just the service entrance: distribution and branch SPDs, the DC side, and the signal-line and antenna protectors on instrument and communication circuits. Replacement of modules and any work inside an energized panel follow the site's electrical safety program and qualified-person rules, and where devices offer a status contact, wiring it to the RTU turns the silent failure into an alarm.
Why SPD Status Has to Be Checked at All
The dominant SPD technology in panels is the metal-oxide varistor, and its life story explains the whole procedure: each surge it clamps degrades it slightly, and a large event or an accumulation of small ones drives it toward a failing state. To keep a degraded MOV from ending as a fire, SPDs incorporate thermal disconnects that take the worn component safely out of circuit - which means the device's normal end of life leaves the circuit quietly unprotected while power flows on undisturbed. Nothing downstream misbehaves; no breaker trips; the only witness is the indicator. Devices evaluated to UL 1449, the safety standard for SPDs, are designed to fail in this safe-but-silent way, which is precisely why the standard-equipped indicator exists and why somebody has to look at it.
The consequence for remote and lightning-prone sites is a simple asymmetry: the storm that kills the SPD is the same storm that proves the site needed one, and the second storm finds the site bare. A status check that happens only at annual PM leaves months of exposure, which is the argument - developed below - for wiring status contacts into telemetry wherever the hardware offers them.
Walking the Panels: What to Inspect
The inspection itself is a reading exercise with one rule: the device's own label or datasheet defines what healthy looks like, because conventions genuinely differ between manufacturers - a green window, an extinguished flag, an illuminated LED can each mean healthy on one product line and failed on another. Read each indicator against its legend, not against habit. Cover the full protection chain: the service-entrance or main-panel SPD, distribution and branch-panel devices, DIN-rail protectors on the DC supplies, and the signal-line protectors that guard instrument loops, network runs, and radio or antenna feeds - the small devices that die most often at communication sites and are checked least. Many industrial SPDs are built as a base with a pluggable cartridge, where the indicator reports the cartridge's state and a failed module swaps without rewiring; note which pattern each panel carries.
Record as you go: device, location, indication, and date, alongside the install date where it is known. A visual check also catches what indicators cannot say - discoloration, cracked housings, and loose or lengthened lead dress that degrades the protection's performance regardless of module health. Anything found failed means the circuit behind it has been running unprotected for an unknown interval; the module gets replaced like-for-like per the manufacturer, the event gets correlated with recent storms in the site log, and repeated failures at one location are escalated as a finding about the installation - grounding, lead length, device rating - for the electrical engineer rather than treated as bad luck. All physical work in the panels, including cartridge swaps where the manufacturer permits them energized, is governed by the site electrical safety program and its qualified-person rules.
Getting SPD Status Out of the Panel and Into SCADA
The upgrade that changes the economics of all of the above is the status contact. Many panel and DIN-rail SPDs provide a dry changeover contact that follows the device's health, exactly so the silent failure can become an alarm: wired to a digital input on the RTU or PLC, the contact reports the moment a module sacrifices itself, with a timestamp that usually lands inside the storm that caused it. At unmanned sites this converts the inspection interval from months to minutes; a platform such as Merobix carrying SPD-status points alongside power and communication health gives the operator the pattern - which sites, which storms, how often - that individual walkdowns never assemble.
Two verification habits complete the setup. First, prove each status circuit end to end at commissioning, operating the contact by the means the manufacturer provides - removing a pluggable module is the common method - and confirming the alarm arrives with the right label; an SPD alarm wired to a spare input nobody mapped is the silent failure reborn one layer up. Second, keep the human walkdown in the program at a reduced tempo, because the contact reports module state, not installation quality, and spares on the shelf remain the difference between an alarm and a fix. The common mistakes are all omissions: checking the big service-entrance SPD and ignoring the signal-line protectors, assuming a dark indicator means healthy when the legend says the opposite, replacing modules repeatedly without asking why one location eats them, and leaving the status contacts unwired at exactly the unmanned sites that need them most.
Frequently Asked Questions
How does a surge-protective device fail?
The common power-panel SPD is built on metal-oxide varistors, which degrade a little with every surge they clamp. When a varistor approaches its end, the device's internal thermal disconnect removes it from circuit safely - devices evaluated to UL 1449 are designed for exactly this behavior - so the typical failure leaves power flowing normally and the circuit silently unprotected. The status indicator, and the optional remote contact, exist because this failure mode produces no other symptom.
Should SPD status contacts be wired into SCADA?
Wherever the device offers one and the site has telemetry, yes - it is among the cheapest alarms in the panel. The contact turns a failure that would wait silently for the next inspection into a timestamped event, usually arriving during the very storm that caused it, and at unmanned sites it is effectively the only timely way to know protection has been lost. Prove the circuit end to end at commissioning, since an unmapped alarm input recreates the silent failure it was meant to eliminate.
How often should SPD indicators be checked manually?
Sites with status contacts in telemetry use the walkdown as a periodic audit of installation quality - lead dress, grounding, housings - at whatever interval the site's maintenance program sets, with an added check after significant lightning activity. Sites without remote status depend entirely on the walkdown, which argues for a short interval in storm season and for prioritizing the retrofit of status contacts at any site nobody visits often.
Automation services
Need help turning this into a working system?
Merobix integrates SCADA, programs Allen-Bradley and Siemens PLCs, and designs and fabricates industrial control panels.
Meeting requests are reviewed before confirmation.