A lightning protection system is engineered for the moment of the strike. But the people on your site, the crew on an exposed structure, the team running a hazardous process, the operator in an elevated cabin, need warning before that moment, not protection during it. The gap between an approaching storm and the first discharge is where injuries happen, and it is the gap a thunderstorm warning system is built to close.
A thunderstorm warning system detects the earliest measurable signs of a developing storm and turns them into advance warning: minutes of lead time in which a structured, pre-planned response can be carried out. Personnel are cleared from exposed areas. Hazardous operations are paused or brought to a safe state. Response teams are alerted. The outcome is not a device on a wall; it is a safety process with time built into it.
How Advance Warning Works
A thunderstorm does not begin with a strike. It begins with the electrification of the cloud, and that electrification produces a measurable electrostatic field at ground level well before any lightning occurs. Under IEC 62793, this electrostatic field is the first detectable phenomenon of a thunderstorm, present in the initial phase, before the first intra-cloud or cloud-to-ground discharge.
An electrostatic field sensor measures this build-up continuously. As the field strength crosses engineered thresholds, the system raises graduated alarms, giving operators warning of a developing hazard rather than confirmation of one that has already arrived. This is the essential distinction between an engineered warning system and a simple strike detector: a strike detector tells you lightning has occurred; a field-monitoring system tells you conditions are developing toward it, while there is still time to act.
What Operators Do With the Warning
Advance warning is only as valuable as the response it enables. IEC 62793 sets out the preventive actions a warning is intended to trigger, and in an operational setting these map directly to a site's safety procedures:
- Move personnel to a safe place, or hold them in one, clearing exposed roofs, yards, elevated structures and open ground.
- Stop or postpone hazardous activities, from fuelling and hot work to crane and lifting operations.
- Bring critical processes to a safe state, backing up systems and transferring to protected supplies where appropriate.
- Alert response and emergency teams so they are positioned before, not after, the storm arrives.
The specific response depends on the site. A warning system earns its value when it is engineered into an operator's existing procedures, so that an alarm produces a defined, rehearsed sequence of actions across the sectors we serve:
- Data Centres: safing of critical maintenance windows and outdoor works during high-field conditions.
- Energy & Renewables: clearing turbine and solar field crews from exposed work at height and in open terrain.
- Critical Infrastructure: protecting outdoor personnel and public-safety operations at transport, water and telecommunications sites.
- Oil & Gas: halting hazardous-area operations and hydrocarbon handling in the presence of an electrostatic hazard.
Why Engineering Makes the Difference
A thunderstorm warning system is not a plug-in gadget, and treating it as one undermines both its reliability and its standing under the standards. The performance of an electrostatic-field-based system depends on decisions that are engineering decisions, not installation steps.
Sensor siting matters: placed too close to an air terminal or a tall structure, the sensor reads a distorted field and its warnings lose meaning. Alarm thresholds must be tuned to the site's risk profile and the response times its procedures require. And the standard is explicit that these choices involve trade-offs. IEC 62793 defines the performance parameters that govern them, including the failure-to-warn ratio, which must be kept very low where human safety is involved; lead time, which matters most where preventive actions take time to activate; and the false-alarm ratio, which matters most where the cost of an unnecessary shutdown is high. Optimising for one affects the others. Setting them correctly for a given site is the engineering that turns a sensor into a dependable warning system.
Recognised Within the Risk Framework
For a decision-maker responsible for compliance and continuity, the most important point is this: a thunderstorm warning system is not a discretionary add-on. It is a protection measure recognised within the international lightning risk framework, with a quantifiable effect on risk to people.
IEC 62305-2:2024 recognises the thunderstorm warning system as a protection measure and accounts for the reduction in risk to persons when warnings and preventive actions are in place. There are cases the standard works through where structural protection alone is not enough. In IEC 62793's worked example of a crane, even a lightning protection system at the highest protection level does not reduce the safety risk to people near the structure to a tolerable level; the standard concludes that a warning system is required in addition to the protection system, specifically to protect people. The principle it illustrates is a general one: where the residual risk to people cannot be engineered out of the structure, warning and preventive action are how that risk is brought within tolerance.
IEC 62793 then sets the benchmark for how such a system must perform, its classification, detection and testing criteria, so that the warning capability credited in the risk assessment is a system that measurably delivers it. Together, the two standards let an operator treat thunderstorm warning as a documented, defensible part of a lightning risk assessment, not an unquantified extra.
A Managed Capability, Not a One-Off Install
A warning system commissioned once and left alone degrades in value the same way any protection system does. Thresholds drift out of step with a changing site. Alarm performance goes unverified. The standard itself recommends archiving and reviewing alarm-status data to confirm a system is performing as intended.
Aetheric treats warning as an ongoing capability. It sits naturally within the wider protection lifecycle:
- Lightning Resiliency Planning places warning within an enterprise-wide resilience strategy across multiple facilities and regions.
- Resiliency as a Service (RaaS) keeps the system monitored, maintained and performance-verified, with alarm data reviewed against the standard's efficiency criteria year after year.
The Technology Aetheric Integrates
The electric-field sensing system Aetheric integrates is the PREVISTORM TWS, an electrostatic field monitoring system designed and operating in accordance with IEC 62793. Aetheric selects, sites, configures and supports it as an engineered component within a complete warning solution, tuned to each site's risk profile, response procedures and compliance obligations. The value is not the sensor alone; it is the engineering that makes it a dependable part of your lightning protection strategy.
Frequently Asked Questions
How much advance warning does the system give?
Lead time depends on how a storm develops and how the system is configured for the site. Because the system detects the electrostatic field build-up that precedes the first strike, it can warn during the initial phase of a storm, before any lightning has occurred. Aetheric configures alarm thresholds to balance sufficient lead time against false-alarm rates for each site's specific response needs.
Does a warning system replace a lightning protection system?
No. The two address different parts of the risk. A protection system defends the structure at the moment of a strike; a warning system protects people and processes in the time before it. The standards treat them as complementary, and in some cases a warning system is required in addition to structural protection specifically to bring the risk to people within tolerable limits.
What standards apply?
Two in particular. IEC 62305-2:2024 recognises thunderstorm warning as a protection measure within the lightning risk assessment framework. IEC 62793 defines how a warning system must perform and be tested. Aetheric integrates systems against both, so warning capability sits inside your existing risk and compliance documentation.
Is it plug-and-play, or does it need engineering?
It needs engineering. Sensor siting, alarm thresholds and integration with your safety procedures all affect whether warnings are reliable and standards-defensible. A field sensor installed without this work can read a distorted field and produce warnings you cannot depend on. The engineering is what makes the system trustworthy.
How is the system maintained over time?
Through ongoing monitoring and periodic performance verification, ideally under a managed programme such as RaaS. The standard recommends reviewing alarm-status data to confirm the system continues to perform, and Aetheric builds that review into the way we support the capability.