The design changed again. So did the risk.
Built for a design that keeps moving
A revision, not a rebuild
The structure model is carried forward, so a design change means editing the inputs that moved and re-running. The project keeps a revision list with a number, a date and a note on what changed. When someone asks what changed between issue B and issue C, the list answers.
A result services can act on
Each figure shows the working and the clause behind it, so a services engineer sees what drives the risk, not only the verdict. Under IEC 62305-2:2024 the engine goes further and resolves risk down to each zone, so the team sees which zone needs SPD coordination.
Disciplines on one record
Electrical, services and project management work in the same project with roles scoped per person, so nobody is emailing a spreadsheet version around and nobody works from a superseded copy.
What each standard tells the design team
You pick the standard the client or authority names when you start each assessment. The assessment then follows that standard's own method from the first input to the report.
Results per zone, national rules per site
The combined risk R and, separately, the frequency of damage F, resolved down to each zone of the structure, with the national departures of the site's jurisdiction applied. A what-if on the LPS class or SPD coordination shows its effect before the design is issued. Zones and jurisdiction profiles are IEC features.
Each connected service counted
Surge protection and bonding flagged
The least protection search (C.3.4.2) never offers an LPS without surge protection at the point of entry where a service comes in (4.1, 4.2.1(b)). Wherever an LPS is in play, the result reminds you to bond metallic services such as gas and water pipes at the point of entry (3.6.2(c)).
Three buildings, two design issues, one record
Take a common case. A design firm carries a mixed-use scheme of three buildings through several design issues, and the client names IEC 62305-2:2024. The scheme is an illustration, not a customer.
- One project, three sites. Each building is a site in the same project with its own assessment, so the electrical lead and the services engineers work from one record.
- Assess at the first issue. Model each building, its zones and its incoming services. Each result opens to the clause behind it, and under IEC the risk is resolved down to each zone.
- The design moves. At the next issue the plant room moves to the roof of one building. You edit the inputs that changed and re-run that building only; the earlier revision stays readable.
- Test the option. Propose a higher LPS class or SPD coordination for the zone that now fails and compare it with the risks as they stand, before the drawings are issued.
- Track the scheme. The project view shows which buildings are assessed, in review or still draft, so nobody issues a drawing against a stale result.
- Issue per building. Each building gets its own report when it reaches sign-off.
What the design team gets out of it
A report per building
A full PDF and a short version for each building at sign-off, with your logo and firm name (full white label on Enterprise). See a sample IEC 62305-2 report.
A comparison for each option
The risks with a proposed protection beside the risks as they stand, ready for a design review before anyone commits to it.
A project status view
Every building's state on one page, refreshed from the newest revision, with the activity log behind it showing who changed what.
One project, every building, no stale copy
A campus or a phased development is one project holding many sites, each assessed on its own. The project rollup refreshes from the newest revision, so the lead sees which buildings are assessed, which are in review and which have not caught up with the latest design.
- See at a glance which sites are assessed, in review or still draft.
- Hand a site between disciplines without re-entering the structure model.
- Take the calculation trace into a design review and answer where a value came from.
- Propose a protection upgrade and show its risks beside the risks as they stand, before anyone commits to it.
- Issue a report per building when each one reaches sign-off, with your logo and firm name (full white label on Enterprise).
- On an IEC 62305-2:2024 assessment, apply the national rules of the jurisdiction the site sits in.
Coordinating SPDs between the zones of an IEC design? Read lightning protection zones, or see how NFPA 780 Annex L and AS 1768:2021 work.
Questions design teams ask
What happens to the lightning risk assessment when the design changes?
Can several disciplines work on the same project?
How does Lumex™ handle a campus or a phased development?
Does Lumex™ lay out the lightning protection system?
Can we show the effect of a design option before issuing it?
Get started today