At network scale, operations and maintenance stops being a chore list and becomes an operating model: monitoring and triage, scheduled condition rounds, fault response, spares, and the per-port records that tie them together. The network operator’s job is distinct from both the single-site owner’s and the installer’s — running all of it, every week, and proving it from the records.
Key Takeaways
- Network O&M is an operating model — monitoring, rounds, response, spares, records — not a longer checklist.
- Each function has a preventive side, a corrective side, and a record that proves it.
- In-house, contracted or hybrid is decided by your port count, spread and callout history — no outside ratio applies.
- Warranty defects are claimed on the manufacturer’s terms, not absorbed into the operations budget.
The Operating Model, Function by Function
| Function | Preventive side | Corrective side | The record that proves it |
|---|---|---|---|
| Monitoring and triage | Status and session data watched across all sites; the drifting unit spotted before it faults | Each alert decided on its evidence: remote action, scheduled visit, or urgent callout | The fault log per port, decision and outcome included |
| Scheduled condition rounds | Planned visits on a cycle set by your own fault history — the tasks are in the commercial maintenance checklist | Worn parts replaced before they fail in service | The visit record per unit: state, work done, items to watch |
| Fault response and repair | Spares held where the fault record says they will be needed | Repair under the response terms your own arrangements set | The callout log: fault, cause found, downtime hours per port |
| Configuration and firmware administration | Changes planned, proven on one unit, then rolled out | Recovery when an update misbehaves somewhere in the estate | The change record per unit: version and settings, before and after |
| Reporting | Uptime and utilisation reported on a fixed rhythm | Investigation where one site’s numbers break the pattern | The monthly per-port report |
Funded sites make reporting a compliance output: corridor stations under the U.S. NEVI programme must hold average annual uptime above 97% under 23 CFR Part 680 — a figure that has to fall out of the records, not be reconstructed at audit time.
In-House, Contracted, or Mixed
- In-house crews give direct control of response and records, and carry fixed staffing whether the fault rate is high or low.
- Contracted field services move field work to installers or service firms under written response terms the operator specifies and audits.
- A hybrid — own monitoring and triage, contracted hands for the visits — is the shape networks commonly grow into, because triage decides how much field work is bought.
Choose from your own numbers: port count, spread, callout history.
The Records Are the System — and the Warranty Is Not O&M
Every function above stands on one discipline: a per-port log, kept from commissioning — sessions, faults with causes, visits, parts fitted, downtime hours, configuration changes. Renewals are argued from it, host reports built from it, warranty claims evidenced by it. The boundary matters: a product defect is the manufacturer’s cost on the warranty’s written terms — EVDANCE’s standard warranty runs 3 years — while operating the site is the operator’s. Keep the claim file separate from the operations log, so a defect is claimed rather than absorbed into maintenance spend — the boundary discipline in the warranty and after-sales checklist.
Hardware That Reports Its State
The model runs on hardware that reports. The EV-AC03201T dual-connector AC station (two Type 2 connectors sharing up to 43 kW, OCPP 1.6J, RFID, IP54) and the EV-RHDC30K-L compact DC charger (22 kW DC, OCPP 1.6J, IP54) both state OCPP 1.6J, so on a paired platform faults surface as reports to triage centrally, not as driver complaints. EVDANCE, founded in 2011, offers no platform of its own — the pairing is the operator’s arrangement, confirmed per model in writing. Networks planning hardware around an O&M model can start via our commercial EV charging team, our reseller and distributor programme, or contact us.
Frequently Asked Questions
How many technicians does a charging network need?
No sourced ratio exists to copy. Staffing follows your port count, the spread of the sites and — most of all — your own callout record: a quiet estate needs fewer hands than a fault-prone one. Build the number from your first sites’ logs.
Is operations and maintenance the same as the manufacturer’s warranty?
No. The warranty covers product defects for its stated term — 3 years on EVDANCE hardware — on the manufacturer’s written terms. O&M is operating the installed network: monitoring, visits, response and wear. The day a fault could be either, the paperwork decides who pays.
What belongs in the per-port record?
Sessions and energy, faults with causes, visits and parts, downtime hours, configuration changes — one file per port from commissioning: evidence for renewals, host reporting, uptime duties and warranty claims.
Related Reading
- Commercial EV Charger Maintenance Checklist
- How Do Commercial EV Charging Stations Work?
- EV Charger Warranty and After-Sales Terms: A Distributor’s Checklist
- OCPP Explained: What Charge Point Operators Need From EV Charger Hardware
