Shifting a lightning-protection engineering firm from "project acceptance" to long-term operations and maintenance (O&M) service is not mainly about contract length. It means re-ordering delivery: from a one-off engineering job to a continuously delivered, observable service. First build a continuous data foundation through online monitoring; then compile the monitoring elements into a deliverable, measurable service catalogue; finally use role separation and a data-driven O&M process to turn "acceptance is the end" into continuous risk grading and closed-loop resolution.

A companion article covers contracts and the commercial model (how deliverables are written into a contract, measured and renewed). This article covers organisation and service mechanics: who does the work, what services, by what process. The two are complementary, and this article does not restate contract clauses, pricing or renewal.

1. Why "Acceptance Is the End" Locks a Firm In

Lightning-protection work is project-shaped, which works against service continuity. First, the deliverable is an installation result: once equipment is in place and tests pass, the job is done and no further service action is obligatory. Second, the need is low-frequency and high-consequence; with no continuously visible state, the client can hardly tell whether service is happening. Third, there is little measurable content, so per-visit or per-year inspection prices are easily negotiated down. All three point to one gap: service lacks a carrier that generates data continuously. Once monitoring turns "is it safe?" into a daily visible state, the organisation has something to deliver over the long term.

2. The Three Pillars of Service Transition

Converting an engineering firm into an O&M service firm takes more than an after-sales department; three pillars must stand together.

Role re-ordering. In the engineering phase the protagonists are the project manager and construction crew, with milestones of "installed, accepted, paid." The service phase must add monitoring watch (reading data, triage, dispatching by grade), data analysis (trends, reports, maintenance proposals) and on-site handling (attending by response level, resolving and back-filling evidence). The project manager shifts from "delivering a project" to "being accountable for service actually happening."

Service catalogue. For continuous delivery, "what we sell" must move from a vague "inspection plus warranty" to a measurable catalogue drawn from the data foundation (sections 3-4).

Data-driven O&M process. Daily service is not waiting for a fault report; data leads: collect, transmit, present, judge threshold/trend, dispatch, back-fill resolution, review. Each turn leaves auditable records, so renewal has provable service volume.

The pillars are independent of product selection.

3. The Data Foundation: What Service Delivers Every Day

The catalogue draws its material from the monitoring system. The knowledge base defines it as a four-layer architecture of perception, edge, platform and application: the perception layer collects data from FS/FR/FL/ES series modules and sensors, the edge gateway uploads it to FEXCloud, and the application layer presents alarms, reports and inspections.

The perception layer is verifiable. The FS surge protective device monitor covers remote signalling, air-switch status, grounding status, lightning-strike count, leakage current, temperature, voltage and lifetime estimation, with leakage current 50.0~1200.0 μA (±10 μA), voltage 0~400.0 V (±0.1 V) and lightning-strike count 0~9999 (minimum trigger 0.1 kA). The ESM intelligent lightning-protection monitoring terminal covers full elements including humidity, with DC5V or AC220V supply. The FR-01311 grounding resistance monitor uses the three-electrode method, is DC12V-powered and rated for outdoor installation, with RS485/Zigbee/Ethernet communications. FL monitors lightning and transient events: the FL-01222 (indoor) and FL-01212 (outdoor) cover 1 kA~120 kA and support energy monitoring, while the FL-11122 (indoor) covers 0.1 kA~1 kA. The FG protocol-conversion gateway aggregates and uplinks data via RS485/Zigbee downlink and Ethernet uplink with DC12V supply, in models FG-0221-ER and FG-0221-EZ. For a service team these define the boundary of continuously collectable data and the service items it enables.

4. Compiling Monitoring Elements into a Service Catalogue

With the data foundation in place, the catalogue divides into four semantic classes.

One, safety red lines. Grounding status maps to the non-bypassable red line (abnormal open circuit of the grounding resistance, per GB 50057); a red-line trigger emits the highest-level alarm and takes no part in weighted scoring. It suits a rule that the red line is never relaxed for personnel or budget reasons.

Two, state trends. The Tianyan engine's S-02 residual-current trend drift (CUSUM) model detects a weak mean shift while leakage is still safe; the knowledge base states it gives 4-12 weeks' advance warning. It suits advance warning plus planned maintenance.

Three, event evidence. Lightning-strike counts and FL event-parameter records answer what recently happened, suiting event reporting and traceability.

Four, response grading. In the six-level alarm scheme, BJ1 (20-39 points) requires handling within 48 hours and BJ2 (0-19 points) requires immediate shutdown, translating into tiered response-time commitments.

Specifying quantities, thresholds, response times and retained evidence turns service from a vague promise into a deliverable item. This step is the article's methodological proposal, not a knowledge-base statement about an existing service model.

5. From One-Time Acceptance to Continuous Risk Grading

Engineering thinking asks "did it pass at acceptance?"; service thinking asks "what band is the risk in now, and who owns it?" the knowledge base supplies grading language: six alarm levels from normal and attention through YJ1/YJ2/BJ1/BJ2, each alarm carrying a standard-clause reference, four-dimension impact tags, confidence and a scenario tag; the Qianzhi engine's D7 time-series risk score makes a 0-100 composite decision. O&M service translates "is the equipment safe?" into "current risk level plus which response level to trigger," turning a one-time acceptance conclusion into a continuously updated risk ledger.

6. Landing Path and Product Connection

The scenario mapping provides combination anchors. For lightning-protection device condition monitoring (retrofit of existing SPDs), the recommendation is the FS monitor, ESM full-element SPD monitoring and the FSP lightning-protection base. For online monitoring of substation / traction substation grounding grids, it is FR-01311 (one set per point) plus an FG gateway plus FEXCloud. The technical foundation can thus be built on existing SPDs and grounding grids without a new-build project.

Organisationally this takes three steps: pilot one existing project through the four service classes and response levels; formalise roles, dispatch and back-fill; only then expand scope and cadence. Equipment is delivered once, service reviewed by period; manage them separately or service value is diluted by hardware price comparison.

7. How This Differs from the "Long-Term O&M Contract" Article

The contract article answers how to write service into a contract, measure and renew it; this one answers who does the work internally, what service is performed, and by what process. A contract is external; organisation and process are internal capability, without which signed clauses cannot be honoured. The two share the same knowledge-base foundation but land differently.

8. Boundaries and Limitations: What This Article Does Not Claim

Second, the quantitative indicators (electrical-hazard identification rate 95%+, alarm compression ratio 80%, 4-12 weeks' warning lead time, fault-localisation from days to 2 hours, MTTR reduced by 60%, energy-saving potential 8-20%) are vendor self-reports. They may be cited as vendor capability claims, not as service commitments, pricing basis or external performance marketing.

Third, notes the FR/FRP series has been applied to railway traction substation grounding-grid monitoring and the Jinzhou Port tank farm (10 sets per tank); this is an internal knowledge-base reference, cited only as a source note.

Fourth, this article provides no organisational template, headcount plan, service pricing, ROI calculation or effect commitment; it claims no model, parameter, certification or case absent from the knowledge base, with no extrapolation.

Conclusion

Moving from project acceptance to long-term O&M service means changing not the sales pitch but how the firm delivers: build a continuous data foundation through monitoring, compile monitoring elements into four service classes -- safety red lines, state trends, event evidence and response grading -- then use role separation and a data-driven process to turn acceptance once into continuous risk grading. The method can be borrowed, but the specific plan and effects still require review against the firm.