After many smart lightning protection projects are completed, the platform does indeed have plenty of data: device online status, SPD status, leakage current, temperature, grounding resistance, lightning strike count, lightning current peak values, alarm records, and trend curves.
But when customers open the platform, what they really care about is not each number itself, but: Is my site safe? Where are the anomalies? How serious are they? Why did they happen? Do we need to handle them right away? Who will handle them? Have they been handled? Will they recur next month?
Therefore, a smart lightning protection platform cannot be just a data display system; it should become a risk interpretation and O&M decision system. The platform should organize lightning current, SPD, grounding, leakage current, temperature, device online status, alarms, work orders, and reports into a risk management view that customers can understand, act on, and trace.
1. The Platform Must First Answer the Five Questions Customers Care About Most
First, is it safe right now? When customers open the platform, the first thing they should see is not complex parameters but overall status, risk level, number of anomalies, important alarms, offline devices, and pending work orders. The platform homepage should be like a lightning protection health overview.
Second, where is the risk? The platform must have point-level and area-level capabilities, telling customers which distribution cabinet has an abnormal SPD, which grounding point has rising grounding resistance, which site has had a lightning current event, which lightning protection box is offline, and which area has recurring alarms.
Third, how serious is the risk? Not all alarms are the same. A short device offline can be at notice level, an abnormal SPD remote signal at general level, a continuously rising SPD leakage current should enter the important level, and a grounding change after a severe lightning strike may be at the emergency level. More alarms do not mean a stronger platform; the value lies in making important risks visible first.
Fourth, why did the alarm occur? When customers see an alarm, they should not only see SPD abnormal, grounding abnormal, or device offline; they should also see the trigger cause: continuously rising leakage current, temperature exceeding a threshold, sudden status change after a lightning strike, a rising grounding resistance trend, a device offline beyond the set time, or multiple anomalies in the same area.
Fifth, has it been handled? Every alarm must eventually enter closure. The platform should show whether it has been confirmed, whether a work order was dispatched, who is responsible, whether the site was visited, whether equipment was replaced, whether it returned to normal, and whether it was archived. Otherwise the platform only finds problems but does not manage them.
2. How Should the Platform Homepage Be Designed?
The homepage should not be filled with curves; it should first help customers quickly form an overall judgment. The first layer of the homepage is overall health status, including system health score, risk level, online rate, number of abnormal points, and number of pending work orders. At a glance, customers can tell the state of the entire lightning protection system.
The second layer is key risk alerts, including emergency alarms, important alarms, anomalies after lightning strikes, grounding changes, SPD degradation, and device offline timeout. The point is not to list all alarms but to let customers see first the problems that should be handled first.
The third layer is a site or area map. Parks, data centers, wind farms, PV plants, communication base stations, oil and gas storage tank farms, highways, and railway lines all need a map or hierarchical structure to locate risks. The map is not decoration; it is used to pin risks down to on-site points.
The homepage should also show today's events and recent trends, such as today's lightning current events, today's SPD alarms, today's grounding anomalies, 7-day risk trends, and 30-day alarm changes. Finally, the homepage should show pending tasks and work order status, directly connecting to long-term O&M services.
3. The Alarm Page Cannot Just Show a Red Indicator
A common problem with many platforms is that alarms are too simple, only showing device abnormal, SPD fault, grounding abnormal, or communication interrupted. Customers often do not know what to do after seeing them. The alarm page should be upgraded from a red-light indicator to a handling entry point.
A truly valuable alarm should at least include the alarm point, alarm level, trigger cause, related data, recommended action, responsible person, handling deadline, and history. For example, an SPD alarm should not just show a fault; it should explain whether it is a remote-signal disconnection, rising leakage current, abnormal temperature, or a status change after a lightning strike.
Alarms should also support correlation analysis. For example, when a lightning current event, SPD status change, grounding resistance change, and device communication anomaly occur at the same time, the risk level of the event is clearly higher than a single device offline. The platform should recognize the risk chain instead of displaying each alarm in isolation.
Alarms should ideally come with handling recommendations, such as checking the SPD module status on site, rechecking grounding connection points, checking backup protection status, checking whether devices in the same area have simultaneous anomalies, and carrying out a special recheck after thunderstorms. In this way, the platform is more like an O&M assistant than an alarm siren.
4. What Should Be Viewed on the Trends Page?
For SPD trends, focus on leakage current trends, temperature trends, operation count, degradation trends, and lifetime status. The risk of an arrester usually does not appear suddenly; in many cases, leakage current rises gradually, temperature stays high, and lifetime declines after repeated impacts. The trends page should help customers see this process.
For grounding trends, focus on long-term changes in grounding resistance, seasonal variations, sudden changes after thunderstorms, multi-point comparison, and anomaly recovery. A grounding system is not permanently reliable just because it passed one inspection; soil, corrosion, construction, and lightning strikes all change grounding status.
For lightning current event trends, focus on strike time, peak value, polarity, frequency, waveform, multiple impacts, and distribution across key areas. This helps customers judge which areas are struck frequently, which points need stronger protection, and which events need special rechecks after thunderstorms.
Alarm trends and work order trends serve managers. The platform should show changes in alarm counts, high-frequency alarm devices, recurring alarm points, overdue work orders, recovery ratio, and average response time. The purpose of trend analysis is not to draw curves but to judge whether risk is improving or worsening.
5. What Should Event Archives Record?
A smart lightning protection platform should build an archive for every important event, especially lightning strikes, severe surges, SPD anomalies, grounding changes, equipment damage, and post-storm rechecks. Without archives, the platform can only prove that an alarm once occurred; with archives, the platform can form an event evidence chain.
An event archive should include event number, time of occurrence, location, event type, peak or status value, related devices, related alarms, handling process, handling result, recheck records, photos or attachments, and final conclusion.
For customers, event archives support accident review, responsibility determination, annual assessment, reporting to management, and follow-up rectification. For service providers, event archives prove service quality and accumulate long-term data assets.
6. How Does the Platform Support Long-Term Services?
A smart lightning protection platform must support long-term services, not just demonstrate at project acceptance. The platform should be able to generate monthly lightning protection health reports, quarterly trend analysis reports, post-storm special recheck reports, annual risk assessment reports, rectification recommendation lists, and equipment replacement recommendations.
Reports should not simply export data tables; they should answer the questions customers really care about: which points have rising risk, which systems are stable over the long term, which SPDs need replacement, which grounding points need recheck, which alarms recur, which work orders were handled promptly, and what should be done in the next phase.
This follows the logic of smart lightning protection services: the platform is the entry point for long-term services, data is the basis of service, reports are the deliverables customers can perceive, and work order closure is the evidence that risks were actually handled.
7. How Does FEXLINK Understand the Smart Lightning Protection Platform?
FEXLINK believes that a smart lightning protection platform is not a display screen after equipment goes online, but the entry point through which lightning protection data enters the customer's safety management process. The value of the platform lies not in how much data it has, but in whether customers can read status from the data, judge risk, drive handling, and accumulate reports.
What FEXLINK cares about is: whether status can be understood at a glance, whether risks are automatically graded, whether events are traceable, whether trends can be explained, whether work orders can be closed, and whether reports can be delivered continuously.
This can be summarized as three shifts: from data display to risk interpretation; from alarm accumulation to graded handling; and from a platform page to an entry point for long-term services.
Conclusion: Customers Need Risk Information That Is Understandable and Actionable
What a smart lightning protection platform should really show customers is not more and more parameters, nor more complex and professional curves, but risk information that customers can understand and act on.
Customers need to know: where is normal, where is abnormal, what is most urgent, why it is abnormal, who is handling it, what the result is, and what to do next. Only when the platform can answer these questions does smart lightning protection data truly change from device data into management value.
