Managing the maintenance of a lightning protection system on a single building is already a matter of rigor. So, when you have ten, twenty, or a hundred sites, the multi-site maintenance challenge means the question is no longer “will we manage it?”, but “how do we preserve operational efficiency?”.
A solid multi-site maintenance plan, a true facility maintenance plan for LPS, is a simple yet demanding blend: a common framework, clear priorities, then a realistic schedule, sustained over time. In March 2026, with strengthened QHSE requirements and sites often outsourced, you save time when everyone speaks the same language.
In this article, we lay out a practical method, tailored for maintenance managers, operators, facility managers and QHSE, with a schedule logic, priorities and tracking via CMMS.
Build a common foundation per site, before talking schedule
Before setting a single date, we need to agree on “what we maintain”. In the LPS (Lightning Protection System), we generally speak of lightning rods (including ESE where applicable), conductors, equipotential bonding, earthing systems, surge arresters, and associated control points.
The trap in multi-location facilities is heterogeneous asset inventory. One site calls equipment “TGBT Surge Arrester”, another “Panel SPD”, and the third doesn’t even have a label. As a result, we plan blind. We solve it by imposing standardized protocols with a unique, identical framework everywhere.
To set the foundations for inspection and what is expected according to compliance standards, we can rely on a clear guide like the complete LPS inspection method proposed by LPS France, then roll out the same logic across all sites.
Here are the elements we collect systematically, site by site, as part of structured asset management, so planning becomes “mechanical” rather than political:
- LPS scope (buildings, zones, extensions, roofs, antennas, canopies).
- Asset list and identification (unique ID, photos, location).
- History (last check, non-conformities, pending actions).
- Access constraints (hours, qualifications, concurrent work, permits).
- Documents (reports, plans, diagrams, studies, supporting documents).
At this stage, we also set simple Standard Operating Procedures: an asset without an owner is an asset without maintenance. So we assign a lead per site (site manager, local maintenance, contractor), and lock down validation circuits.
Once this foundation is laid through these standardized protocols, the schedule is no longer a “wish”, it becomes the logical consequence of a reliable framework for multi-site maintenance.
Define P1 to P4 priorities understandable by maintenance and QHSE
In a multi-site maintenance context with an LPS plan, priority is not “what screams loudest”. It’s a consistent, repeatable, and audit-defensible decision, at the heart of effective maintenance governance. We need a simple system, P1 to P4 for example, based on two axes everyone understands: impact (safety, downtime, compliance) and probability (exposure, condition, history). This framework specifically aims at downtime reduction by making trade-offs explicit.
We can draw inspiration from prioritization methods used in portfolio management, because they force trade-offs to be made explicit, like in this resource on project prioritization and decision criteria. The idea is not to overcomplicate, but to make choices clear.
We then formalize a short grid, usable in weekly meetings, and CMMS-compatible:
| Priority | When to use it | LPS examples (common) | Target timeframe |
|---|---|---|---|
| P1 | Reactive maintenance for immediate danger, major non-compliance, high risk | Broken earth connection, failed arrester, cut conductor | 24 to 72 h |
| P2 | Significant risk, proven degradation | Earth measurement out of target, degraded fastening, advanced corrosion | 7 to 30 days |
| P3 | Preventive maintenance for compliance maintenance | Periodic inspection, tightening, continuity checks | Current month to quarter |
| P4 | Opportunity, improvement, standardization | Labeling updates, test point additions, stock standardization | Quarter to semester |
If you’re torn between two priorities, decide with a question: “If it fails tomorrow, who bears the risk, and what’s the actual impact on operations?”
This prioritization becomes our “common language”. Only then do we plan, because we know what to defer, and above all what never to defer.
Build a sustainable multi-site schedule for multi-site maintenance, then bring it to life in CMMS software
A multi-site LPS schedule looks like a flight plan. You can draw it very neatly on a spreadsheet, but what matters is execution, field feedback, and continuous updates.
To build a robust maintenance scheduling calendar, we blend three families of work:
- mandatory or expected preventive maintenance (according to your internal frameworks and applicable standards),
- corrective work from discrepancies (P1 and P2 first),
- improvement actions (P3 and P4, when capacity allows).
We also gain realism by accounting for season and workload. Some sites have shutdown windows, others don’t. Multiple teams share the same contractors, which supports vendor consolidation. Roof work requires weather, access, permits, sometimes lifts. Planning means making trade-offs with good resource allocation.
On planning optimization, academic approaches highlight a useful point: you must manage dependencies and resources, not just dates. To go deeper, you can read this paper on maintenance schedule optimization (useful to structure thinking, even if you stay pragmatic day-to-day).
Here’s a simple sequence we apply well in multi-sites:
- We set non-negotiable appointments (preventive inspections, audits, client deadlines).
- We block monthly capacity for P1/P2 corrective work (otherwise everything falls apart).
- We group by geographic zones to cut travel and idle time.
- We smooth P3/P4 tasks over “light” weeks.
- We validate the schedule with operations, then publish a locked version (and a replanning rule).
Next, we avoid “ghost planning” by controlling through CMMS software, with work orders, statuses, attachments, and field evidence via mobile maintenance. On multi-site issues, experience feedback like these multi-site management best practices help frame standardization, even if you adapt it to lightning protection.
In our case, a dedicated platform like LPS Manager serves as the backbone for facility management software: site tracking, centralized document management, shareable reports, and also weather and lightning alerts with real-time data depending on activated features. For concrete feedback and demonstrations, you can follow the LPS France YouTube channel, useful for aligning internal teams and contractors on the same method. This approach opens the door to predictive maintenance via IoT sensors or a digital twin, with KPI tracking to measure equipment uptime.
Ultimately, a useful schedule isn’t “full”, it’s managed through a solid facility maintenance plan.
You recognize a good multi-site maintenance plan by two simple signs: P1s don’t drag on, and preventive inspections don’t get lost. If you implement a common framework, P1 to P4 prioritization, then a maintenance scheduling calendar managed in facility management software and CMMS software with centralized work orders, you regain control without adding burden. This boosts operational efficiency, downtime reduction and cost control in your multi-location facilities. The logical next step is to start with a pilot site for scaling maintenance, then roll out in waves with centralized management, keeping the same rules. And for you, which priority comes up most often, P1 or P2?
