Understand SPDA risk management as a continuous process: assessment, treatment, design, implementation, inspection, change control, and protection review.
Check it out!
Risk SPDA risk management is the engineering approach used to keep lightning protection consistent with the actual condition of the installation over time. It is broader than risk assessment: it uses the results of the technical assessment to organize treatment, responsibilities, design, implementation, inspections, documentation, change control, and reassessments.
The distinction became especially important with ABNT NBR 5419-2:2026. The 2015 edition used the expression in the title of Part 2 “Risk management”; in 2026, Part 2 was renamed “Risk assessment”. The change helps separate the analytical core — calculation of R, RT, damage frequency F, and FT — from the broader process of managing decisions and protection measures.
In this article, “SPDA risk management” is treated as the continuous process that connects risk assessment to implementation and the protection lifecycle. For the calculation methodology of the current edition, see SPDA Risk Assessment — NBR 5419-2:2026.
Why Risk Management and Risk Assessment Should Be Separate Topics
Risk assessment essentially answers which risks need to be assessed and which measures are required to achieve tolerable limitsRisk management answers how those decisions will be implemented, maintained, verified, and reviewed when the installation changes.
| Risk assessment | Risk management |
| Delimited technical study | Continuous management process |
| Calculates R and, when applicable, F | Uses results to organize actions |
| Compares R × RT and F × FT | Defines responsibilities, priorities, and deadlines |
| Selects appropriate measures | Controls design, implementation, and effectiveness |
| Works with a known installation configuration | Controls changes that alter that configuration |
| Produces a technical decision | Keeps the decision technically valid over time |
The detailed treatment of SPDA risk assessment according to NBR 5419-2:2026 remains on its own URL. This avoids mixing search intent and allows each topic to be explored in depth without duplication.
From NBR 5419-2:2015 to NBR 5419-2:2026
The terminology of the two editions helps explain the difference in focus.
The 2015 edition was titled Lightning protection — Part 2: Risk management. The 2026 edition adopted Part 2: Risk assessment.
The current edition concentrates its main body on the analytical procedure. In addition to reorganizing risks, it formally introduces assessment of damage frequency F for internal systems. The former R2 was replaced by F, while R4 became informative and optional for economic assessment.
This does not make management irrelevant. On the contrary, an assessment only produces effective protection when its results are converted into actions, controlled during implementation, and reviewed when assumptions change.
The SPDA Risk-Management Cycle
A consistent process can be structured into seven interconnected stages.
1. Characterize the installation
Management starts with a reliable baseline. It is necessary to know which structure is being protected, how it is used, which lines are connected, which internal systems exist, and which protection measures are installed.
In existing facilities, this stage may require a field survey because historical drawings do not always represent accumulated expansions, replacements, and adaptations.
2. Perform the risk assessment
NBR 5419-2 risk assessment provides the objective basis for identifying relevant components, calculating R, comparing it with RT, and, where applicable, assessing F and FT.
Management should not arbitrarily alter the study results. Its role is to use those results traceably to define the treatment plan.
3. Select and prioritize measures
Measures should be selected according to the contribution of risk components and damage frequency. Depending on the scenario, the plan may include:
- external SPDA;
- equipotential bonding;
- grounding;
- measures against step and touch voltages;
- Class I SPDs;
- coordinated SPD system;
- LPZ;
- shielding and routing;
- isolating interfaces;
- protection of power and signal lines;
- specific measures for critical systems.
Priority should not be defined only by cost or ease of execution. The technical contribution of each measure and the consequence of delaying its implementation must be considered.
4. Design and specify
The assessment identifies the need; the design converts that need into an executable solution.
When the measure involves physical protection of the structure, the next step may be an SPDA Design. When the vulnerability lies in internal systems, it may require a Surge Protection Measures Design — MPS.
Management needs to ensure that assessment assumptions are transferred into the design. If the design uses data different from those used in the study, traceability is lost.
5. Implement and verify
The designed protection needs to be implemented according to the documentation and acceptance criteria. Field changes should be technically evaluated before being incorporated.
The mere existence of components does not demonstrate effectiveness. Air-termination, down conductors, grounding, equipotential bonding, SPDs, routing, and interfaces need to preserve the relationship established by the design.
6. Inspect and maintain
After implementation, risk continues to be managed through inspections and maintenance.
The objective is to verify whether:
- components remain intact;
- documentation remains consistent with field conditions;
- new installations have not created interference;
- protection measures remain present and functional;
- SPDs have not reached end of life;
- equipotential bonds remain intact;
- changes have not compromised separation distances, air-termination, or down conductors;
- internal systems remain protected according to the intended architecture.
7. Control changes and reassess
The cycle closes when the organization compares the current condition with the original assumptions.
Relevant changes may require a new assessment, design review, or new measures. Management needs to recognize these triggers before the protection becomes technically outdated.
Change Control: Where Many Systems Lose Technical Validity
An SPDA may have been correctly designed and installed and, years later, no longer adequately represent the installation because the building has changed.
Examples of changes that should enter the management process include:
- increase in area or height;
- new roof or metallic structure;
- photovoltaic installation;
- new antennas;
- rooftop HVAC equipment;
- new panels and power supplies;
- new substation, generator, or UPS;
- new metallic lines between buildings;
- deployment of video surveillance, telecommunications, automation, or instrumentation;
- change in use or occupancy;
- creation of hazardous areas;
- new mission-critical systems;
- changes to grounding or equipotential bonding;
- replacement of SPDs with different models;
- renovations that alter conductor routing or separation distance.
The point is not to treat every intervention as an automatic reason for a new design. The process should evaluate whether the change affects assumptions or protection measures.
Recording Risks, Assumptions, and Actions
Managing risk requires converting technical decisions into controllable information.
A tracking matrix may contain:
| Field | Purpose |
| Assumption | Records the condition used in the assessment |
| Information source | Defines where the data came from |
| Dominant risk/frequency | Identifies the factor governing the decision |
| Selected measure | Records the planned treatment |
| Design document | Links the decision to the executable solution |
| Responsible party | Defines who should execute or validate |
| Deadline | Controls implementation |
| Completion evidence | Demonstrates that the action was completed |
| Review trigger | Indicates when the assumption should be reassessed |
This structure is especially useful in industrial plants, campuses, hospitals, data centers, and multi-building facilities where protection evolves in stages.
Risk Management in Existing Installations
In brownfield environments, the first difficulty is often not the calculation, but the reliability of information.
Common findings include:
- design without As-Built documentation;
- SPDA modified without documentation review;
- expansions without an updated assessment;
- SPDs installed without a selection record;
- new signal lines not considered;
- modified grounding and equipotential bonding;
- inspection reports without historical consolidation;
- divergence between documents and field conditions.
In these situations, management should begin with survey and diagnosis, establishing a baseline before making upgrade decisions.
The service page for NBR 5419-2:2026 Risk Assessment can be used when the installation needs to review assumptions, recalculate R and F, or determine new measures.
Risk Management and Damage Frequency F
The introduction of damage frequency F expands what needs to be managed.
Previously, an organization could focus governance on the physical SPDA and the assessment of risks associated with losses. With the 2026 edition, internal systems may require specific management of availability and vulnerability.
This means maintaining control over:
- systems considered critical;
- more vulnerable equipment;
- associated power and signal lines;
- LPZ;
- SPDs and their replacements;
- coordination between stages;
- routing changes;
- shielding;
- isolating interfaces;
- failures and events recorded over time.
When F > FT, the management process should track implementation of the selected measures and ensure that the executed solution actually corresponds to the conditions used in the recalculation.
Critical Systems Require Stricter Governance
In critical systems, the consequence of a failure can extend beyond the individual piece of equipment.
Hospitals, data centers, water and wastewater systems, energy facilities, control centers, telecommunications, and industrial processes may depend on systems whose unavailability affects people, production, or essential services.
In these environments, management should treat lightning protection as part of infrastructure reliability management.
This involves integrating:
- risk assessment and damage frequency;
- SPDA and MPS design;
- asset management;
- electrical maintenance;
- change management;
- As-Built documentation;
- procedures after atmospheric events;
- extraordinary inspection when necessary;
- replacement and recommissioning criteria.
Relationship with SPDA, Grounding, MPS, and SPDs
Risk management should not create technical silos.
SPDA
The external SPDA addresses air-termination, down conductors, and grounding to intercept, conduct, and dissipate lightning current, as well as the interfaces required to prevent dangerous sparking.
Grounding and Equipotential Bonding
Continuity and equipotential bonds participate in current distribution and limiting potential differences. Changes to these networks can affect protection even if air-termination components remain unchanged.
MPS
Surge Protection Measures address effects on internal electrical and electronic systems through LPZs, equipotential bonding, shielding, routing, coordinated SPDs, and isolating interfaces.
SPDs
SPDs are assets subject to specification, coordination, installation, and maintenance. Their mere presence does not demonstrate that the MPS remains adequate.
Management should ensure that these disciplines remain integrated throughout the lifecycle.
Inspection as a Risk-Management Verification Mechanism
Inspection is the primary source of evidence about the actual condition of the system.
An SPDA Inspection can identify deterioration, documentation discrepancies, construction changes, interference, and maintenance issues.
For internal systems, the Inspection, Diagnosis, and Upgrading of SPDs and MPS verifies devices, backup protection, grounding, coordination, signal lines, LPZs, and other measures.
The results need to feed back into the management process. A report that identifies a nonconformity but does not generate an action, responsible party, and deadline does not close the management cycle.
Technical Documentation and Traceability
Document management is a structural part of risk management.
The following should be maintained consistently according to the installation scope:
- current risk assessment;
- assumption records;
- SPDA designs;
- MPS designs;
- grounding design;
- diagrams and drawings;
- ART records;
- As-Built documentation;
- inspection reports;
- maintenance records;
- history of replaced SPDs;
- change records;
- action plans;
- commissioning and acceptance documents.
Without traceability, the organization loses the ability to demonstrate why a given measure was adopted and whether the current condition still corresponds to the assessed scenario.
Risk Management in Design and Procurement
Management should also extend to contracting and procurement.
A design may specify a certain performance level and, during procurement, receive proposals with apparently equivalent solutions. Changes in materials, SPDs, SPDA components, cable routes, or equipotential-bonding strategies need to be assessed by technical impact, not only by price.
In significant projects, the Owner’s Engineering function can support:
- design review;
- technical bid evaluation;
- equivalency assessment;
- implementation oversight;
- deviation management;
- document control;
- inspections and testing;
- commissioning;
- As-Built updates.
This role closes the gap between the risk study and the protection actually delivered.
Useful Indicators for the Management Cycle
Management can be tracked using simple technical indicators, provided they are not confused with normative calculations.
Examples:
- percentage of critical actions completed;
- number of changes not yet reflected in the As-Built;
- number of SPDs with unknown condition;
- overdue inspections;
- critical systems without an updated F assessment;
- buildings with risk assessments predating relevant changes;
- recurring nonconformities;
- average time to close outstanding issues;
- percentage of technical documentation kept up to date.
These indicators support process management. They do not replace R, RT, F, or FT.
When to Commission a Risk-Management Review
A review is especially useful when an organization has multiple documents and interventions but cannot determine whether they all represent a single technical baseline.
Common indicators include:
- existing SPDA without a retrievable risk assessment;
- existing assessment without clear correspondence to the current design;
- multiple design revisions without a consolidated history;
- field changes without impact assessment;
- inspections with recurring findings;
- SPDs replaced without a design update;
- expansion of critical electronic systems;
- divergence among SPDA, grounding, and MPS;
- no responsible party assigned to close actions.
In these cases, the objective is not to produce another isolated report. It is to reconstruct the relationship among current condition → risk → measures → documents → actions → verification.
Common Errors in SPDA Risk Management
Treating the Assessment as a Final Document
The assessment is valid for specific assumptions and conditions. If the installation changes, the organization needs to assess the impact of the change.
Failing to Convert Recommendations into Actions
A technical report without a responsible party, priority, and deadline does not control risk.
Managing Only the External SPDA
Failures of internal systems, signal lines, SPDs, and MPS are also part of lightning protection.
Replacing Components without Assessing Equivalence
Changing components solely because of commercial availability can alter parameters established by the design.
Losing the As-Built
Without documentation of the installed condition, inspections and reassessments become dependent on field reconstruction.
Confusing a Management Indicator with a Normative Criterion
Administrative KPIs support governance but do not replace the assessment procedures of NBR 5419-2.
Final Considerations
SPDA risk management should be understood as the process that keeps protection technically coherent throughout the installation lifecycle. Risk assessment provides the initial decision; management converts that decision into design, implementation, verification, maintenance, and review.
The change in the title of Part 2 — from “Risk management” in 2015 to “Risk assessment” in 2026 — reinforces the value of separating the two intents. The current normative methodology deserves dedicated assessment content. Management, in turn, should address governance, change, traceability, and maintenance of measures over time.
This separation allows the two contents to complement each other: assess to decide; manage to keep the decision valid and the protection effective.
Technical References
[1] BRAZILIAN ASSOCIATION OF TECHNICAL STANDARDS. ABNT NBR 5419-2:2026 — Lightning protection — Part 2: Risk assessment. ABNT, 2026. Available at: https://www.abntcatalogo.com.br/.
[2] INTERNATIONAL ELECTROTECHNICAL COMMISSION. IEC 62305-2:2024 — Protection against lightning — Part 2: Risk management. IEC, 2024. Available at: https://webstore.iec.ch/en/publication/28137.
[3] A3A ENGENHARIA. Complete technical comparison between ABNT NBR 5419:2015 and ABNT NBR 5419:2026. 2026. Available at: https://a3aengenharia.com.br/conteudo/whitepapers/comparativo-tecnico-norma-nbr-5419/.
Frequently Asked Questions
It is the continuous process that uses risk assessment to define, implement, monitor, and review lightning-protection measures, integrating design, inspection, maintenance, documentation, and change control.
No. Risk assessment is the technical study that calculates and compares R, RT and, where applicable, F and FT. Management is broader and follows risk treatment and maintenance throughout the lifecycle.
The 2015 edition used the title Risk management; the 2026 edition was renamed Risk assessment. The change accompanies a methodological reorganization and more precisely defines the analytical role of Part 2.
When changes in use, construction, electrical installations, lines, critical systems, or protection measures may alter the assumptions and results of the existing assessment.
Yes. Inspection provides evidence about the actual condition of the system and can identify deterioration, changes, and discrepancies that require maintenance, upgrading, or reassessment.
Yes. Lightning protection includes interfaces with internal systems. Management should cover SPDA, grounding, equipotential bonding, MPS, SPDs, power lines, and signal lines where applicable.
Complementary Technical Materials
Related Solutions
Related Services
- NBR 5419-2:2026 Risk Assessment
- SPDA Design
- Surge Protection Measures (MPS) Design
- SPDA Inspection
- Inspection, Diagnosis, and Upgrading of SPDs and MPS
Main Content on the Topic
- SPDA Risk Assessment: NBR 5419-2:2026, R, F, and Protection Measures
- NBR 5419: SPDA, Risk Assessment, Grounding, SPDs, and Technical Documentation
- Complete Technical Comparison between ABNT NBR 5419:2015 and ABNT NBR 5419:2026