EV Charger Monitoring: 6 RFP Must Haves for Fleet & Facilities
Remote monitoring for EV chargers means capturing live status, meter and fault data from every charge point so you can spot and fix problems before a driver finds a dead screen. The main payoff is fewer site visits and faster recovery, backed by standards such as OCPP 2.0.1 and obligations under the Public Charge Point Regulations 2023.
TL;DR:
Chargers that support OCPP 2.0.1 and Device Model variables enable preemptive diagnostics and remote fault management, reducing site visits.
Monitoring systems should update status within 30 seconds, supporting compliance and ensuring timely fault detection in both public and private sites.
Edge gateways are especially vital at complex sites, aggregating local electrical data to reduce bandwidth and latency in fault reporting.
Establishing clear ownership and response procedures is crucial, as monitoring alone does not shorten repair times without a defined maintenance process.
Role-based access control and comprehensive logging of remote actions are necessary to maintain security and support compliance for growing fleets.
Table of Contents
What remote monitoring means for commercial charging operators
Remote monitoring, often shortened to RMS in supplier literature, is the software layer that collects status, session and fault data from every connector on your estate and puts it in front of the people who need to act on it. For a commercial operator, it replaces guesswork with a live record: which bays are charging, which have faulted, and which have gone quiet without an obvious cause.
The use cases vary by site type, but the underlying need is the same: visibility without a windscreen tour.
Fleet depots use monitoring to confirm every vehicle will be ready for its shift, often overnight when no staff are on site.
Workplace charging relies on it to manage shared bays fairly and spot chargers that have silently dropped offline.
Destination and public sites use it to protect revenue and meet regulatory reporting duties.
Multi-site estates use a single dashboard to compare performance across locations rather than relying on separate local reports.
Beyond fault-finding, the same data supports compliance evidence, protects card and RFID revenue from silent failures, and gives drivers a more reliable experience, which matters as much for staff retention as for public reputation.
Why remote monitoring matters to your bottom line
A charger nobody is watching tends to stay broken longer than it should. Remote monitoring shortens that gap by letting your team or your maintenance partner issue a remote reset or diagnostic command before dispatching an engineer, which cuts both the mean time to recovery and the number of unnecessary site visits.
It also produces the evidence trail that reliability reporting and asset planning both depend on.
Remote reset and remote command capability resolves many faults without a van ever leaving the depot.
Historical performance data supports the reliability reporting that public charge point operators must produce.
Condition-based maintenance, built from meter and fault trends, lets you replace parts before they fail rather than after.
Taken together, these benefits turn monitoring from a nice-to-have dashboard into the record that justifies your maintenance spend and defends your uptime figures when a client or regulator asks for proof.
How remote monitoring works in practice
A workable monitoring system for a commercial site is built in four layers, and it is worth understanding each one before you specify a platform. The first is charger telemetry: the connector status, meter readings and fault codes generated at the hardware itself. The second is the site gateway or network connection, which aggregates local signals and carries them off site, often over 4G or a wired connection where the depot already has one.
The third layer is the OCPP or equivalent message broker, which receives standardised messages from every charger and converts them into events your platform can act on. The fourth is the dashboard and data layer, where alerts, analytics and workflows actually reach a human. This four-layer structure, described in AWS’s work on cloud-based charging monitoring, is now the common pattern across mature deployments, and academic reviews of intelligent monitoring architectures reach a similar conclusion: combine edge processing for low-latency anomaly detection with cloud services for estate-wide analytics.
Edge gateways matter most at larger or electrically complex sites, where they can talk to low-voltage cabinets over PLC or Modbus and aggregate that data locally before sending only the meaningful events upstream, reducing both bandwidth and latency. At the message level, a handful of OCPP events carry most of the operational value: StatusNotification for connector state changes, MeterValues for energy and billing data, FirmwareStatusNotification for update progress, and TriggerMessage for forcing a charger to report its current state on demand. A platform that surfaces these promptly, rather than batching them for later, is the difference between knowing about a fault in minutes and finding out from an angry driver.
Standards and features worth specifying
Not every charger and platform combination delivers the same monitoring depth, and the protocol version is the first thing to check. OCPP 2.0.1 introduces a Device Model that supports inventory reporting, configurable monitoring thresholds and richer error states than its predecessor, which makes pre-emptive replacement and remote diagnostics genuinely practical rather than theoretical. The caveat is backward compatibility: a mixed estate running OCPP 1.6 alongside 2.0.1 chargers will not get Device Model features from the older units, so specify the version per asset rather than assuming estate-wide parity.
When you are drafting requirements, work through these in order:
Confirm OCPP version and which Device Model variables each charger actually exposes.
Require meter values granular enough to support both billing and load management decisions.
Specify security requirements: TLS-encrypted connections, signed firmware updates and retained audit logs for every remote action.
Insist on remote command support, including reboot, reset and diagnostics file upload, so faults can be triaged without a visit.
Analysis of OCPP versions makes the point plainly: OCPP compatibility is not a binary checkbox, and treating it as one leaves gaps in exactly the monitoring granularity you are paying for.
Pro Tip: Ask suppliers to demonstrate a live remote reset on a test charger during procurement, not just describe it in a data sheet.
Metrics that actually tell you the platform is working
Monitoring is only as good as the freshness of the data behind it. Under the Public Charge Point Regulations 2023, public charge point status must update within 30 seconds of a change, and reference data such as connector type and pricing must be published in machine-readable form. That 30-second threshold is a useful benchmark even for private fleet and workplace sites that fall outside the regulation’s scope.
The same regulations set a high average reliability benchmark for rapid chargers on the public network. They also require a staffed 24/7 helpline, which gives operators a concrete target to measure their own uptime against (gov.uk).
Beyond raw uptime, track mean time to acknowledge an alert, mean time to restore service, event latency between a fault occurring and it reaching your dashboard, session duration and bay occupancy. Data completeness matters too: a platform that drops events during network blips will understate downtime and overstate reliability, so ask how gaps are logged and backfilled, not just how averages are calculated.
Bringing site energy into the same picture
A charger fault is not always a charger problem. Correlating charge point alerts with upstream electrical assets, such as low-voltage cabinets, breakers and site meters, shortens diagnosis and avoids replacing hardware that was never faulty in the first place. The AWS and Iberdrola-BP Pulse EVBrain implementation extended exactly this kind of monitoring down to low-voltage cabinet level, processing large volumes of protocol messages daily to classify incidents automatically.
Architecturally, this means edge gateways should be able to read PLC or Modbus signals from site electrical infrastructure and decide what is worth sending to the cloud, rather than flooding the platform with raw telemetry. For sites with solar PV or battery storage, this integration also explains charging behaviour that would otherwise look like a fault: curtailment during low generation, reduced import capacity, or scheduled charging delays tied to grid export limits. Without that context, a perfectly healthy charger can look broken simply because the energy system around it changed.
Turning alerts into repairs that actually happen
An alert that nobody owns is just noise. Before you go live, decide who acknowledges alerts, who has authority to issue a remote reset, and what the escalation path looks like when a remote fix does not work. Spares strategy matters here too: knowing which parts fail most often, drawn from your own fault history, shortens the time between an on-site visit being necessary and it being resolved.
Define ownership for each alert type, including who can action a remote command without waiting for sign-off.
Procure SLA terms covering acknowledgement time, remote-recovery targets and on-site response windows separately, since they measure different things.
Build a spares strategy from your own fault-pattern data rather than a generic parts list.
Review your maintenance approach regularly as your estate and fault history grow.
The evidence on this is blunt. Transport & Environment’s 2025 UK analysis found that only around a fifth of a sample of 500 broken charge points were repaired within 24 hours, and 40% within a week. Monitoring tells you something is wrong; only a defined process gets it fixed quickly.
What to put in your tender or procurement specification
A monitoring platform is only as useful as the requirements you write into the contract. Use this as a starting checklist when drafting an RFP.
State the required OCPP version and the specific Device Model variables each charger must expose.
Define firmware update modes, including whether updates are signed, and the security profile in use.
Set a minimum data update frequency and require publication of reference data through a public API where relevant.
Require remote diagnostic and control capability, including reboot, reset and diagnostics file upload.
Mandate an archive of raw protocol messages and a full incident audit trail, not just summarised reports.
Include maintenance response terms, reporting cadence and the exact method used to calculate reliability figures.
Pro Tip: Ask suppliers to show you a real incident report, start to finish, so you can see whether their audit trail actually supports the reliability numbers they quote.
Our fleet depot guidance covers how these requirements translate into a depot-specific specification document.
Practical lessons from deployment
Experience across workplace, fleet and public sites consistently shows the same pattern: the chargers that fail quietly, not dramatically, cause the most disruption, because nobody notices until a driver reports it. Monitoring that flags a drifting meter reading or an intermittent connector fault early allows condition-based maintenance instead of reactive callouts.
Combining managed monitoring software with structured maintenance contracts and grant support so that detection and repair sit under one process rather than two separate suppliers pointing at each other can help keep downtime low across an estate.
Data privacy considerations and compliance implications
Monitoring systems handle more personal and commercially sensitive data than operators sometimes expect: driver identifiers tied to RFID cards or payment apps, vehicle charging patterns, site energy use and, for workplace schemes, employee usage records. Treat this as personal data under data protection law wherever it can be linked to an individual, which means minimising what you collect, stating clearly why you collect it and setting a retention period you can actually justify.
Access control matters as much as collection. Diagnostic and billing data should be visible only to the roles that need it, and every remote command or configuration change should be logged against the user who issued it, both for security and for dispute resolution if a driver queries a charge.
Compliance obligations also extend to how pricing and availability data is published. The Public Charge Point Regulations 2023 require reference data, including price in pence per kWh, to be published in machine-readable form, which means your platform’s data pipeline is not purely internal: it feeds a public-facing compliance obligation. Treat your monitoring platform’s data retention and access policy as part of your wider compliance posture, not an afterthought bolted on after the system is live.
Real-world examples of monitoring in action
The clearest demonstration of what good monitoring architecture achieves comes from the AWS and Iberdrola-BP Pulse EVBrain project, which processed hundreds of thousands of OCPP messages a day, classified incidents automatically and, where historical data showed a reboot reliably fixed a specific error pattern, triggered a remote reset and closed the incident without human intervention. That kind of automated detection-to-remediation loop depends entirely on retaining raw protocol messages, timestamps and severity metadata rather than discarding them after a summary report is generated.
The challenges are just as instructive as the successes. Monitoring alone does not guarantee fast repairs, as the Transport & Environment repair-time findings referenced earlier show starkly: alerts without a defined maintenance process simply accumulate as a backlog. Estates that paired monitoring with a clear escalation path and spares strategy saw faults close faster, while those that treated monitoring as a dashboard to glance at occasionally saw little improvement in actual uptime. The lesson for a commercial or fleet manager is not to choose between software and process, but to procure both together.
Where remote monitoring is heading next
The direction of travel in monitoring architecture is towards more processing happening at the edge rather than waiting for a round trip to the cloud. Research into intelligent monitoring systems points to a three-tier model combining IoT sensors, edge computing and cloud services, which allows anomaly detection to happen in near real time at the charger itself while the cloud layer handles estate-wide analytics and long-term pattern recognition.
Expect automated remediation to expand beyond simple resets, following the pattern already demonstrated in cloud-based platforms that classify incidents and trigger corrective commands without waiting for a human to read an alert. As OCPP adoption matures, the Device Model introduced in version 2.0.1 is likely to become the baseline expectation in procurement rather than a premium feature, since it enables the granular threshold alerts and inventory reporting that condition-based maintenance depends on.
Energy integration is also set to deepen. As more sites add solar PV and battery storage, monitoring platforms that already correlate charger faults with low-voltage cabinet data are well placed to extend that correlation to live grid import and export conditions, giving operators a single view of both charging reliability and site energy performance rather than two disconnected systems.
Managing who sees and controls what
As your estate grows, so does the number of people who need some form of access to your monitoring platform: facility staff checking daily status, maintenance contractors issuing remote resets, finance teams pulling billing reports, and site hosts who only need visibility over their own location. Role-based access control is the mechanism that keeps this manageable, and it should be a specification requirement, not an assumption.
At minimum, define separate roles for read-only status viewing, remote command authority, billing and reporting access, and full administrative control including user management itself. Every remote action, particularly resets, configuration changes and firmware updates, should be logged against the individual who triggered it, which protects you in any dispute and gives you an audit trail that supports the compliance reporting discussed earlier. For multi-site operators, access should also be scoped by location, so a depot manager at one site cannot inadvertently issue a command to a charger three sites away.
Prioritising your monitoring investment
Start with the bays carrying the highest demand, your fleet depot chargers and your busiest workplace bays, since that is where downtime costs the most. Build incident response before expanding the architecture to cover solar PV or battery storage. The recurring costs to budget for are software licensing, site gateways and the maintenance SLA that turns alerts into fixed chargers, not just the initial hardware spend.
— Swift Charging
Getting your monitoring and maintenance set up properly
We bring managed charging software, structured maintenance plans and fleet depot expertise together so monitoring and repair sit under one process instead of being split across suppliers who blame each other when something breaks. Where you qualify, we also support applications for available EV charging grants to reduce your installation costs.
Our Basic, Standard and Fully Managed maintenance plans match monitoring depth to how critical each site is.
Fleet EV Charging Solutions cover depot-specific design, software and maintenance in one package.
Workplace EV Charging Solutions bring the same managed monitoring approach to shared office and site bays.
Getting started typically runs from a site survey through specification to managed monitoring and maintenance going live. If you are ready to scope your estate, our fleet charging team can walk through what a tailored setup looks like for your sites.
FAQ
What app can I use to monitor EV charging stations?
Most commercial charging suppliers provide a dedicated management platform or app tied to their hardware and back-office software, rather than a single universal app covering all brands. The right choice depends on your charger manufacturer and the OCPP version it supports, since platform features vary with what the hardware can report.
What does remote monitoring do?
Remote monitoring collects live status, meter and fault data from each charger and presents it on a dashboard, so operators can spot problems, issue remote resets and track performance without visiting the site. It also generates the historical data needed for reliability reporting and maintenance planning.
Which cars will be V2G ready soon?
Vehicle-to-grid readiness depends on both the vehicle’s onboard hardware and the charger supporting the relevant bidirectional protocol, and manufacturer plans in this area change frequently. Rather than naming specific models, check directly with vehicle manufacturers for their current V2G compatibility roadmap before specifying infrastructure around it.
How do I stop unauthorised use of my EV charger?
RFID access control, PIN codes or app-based authentication are the standard methods for restricting who can start a charging session, and most commercial charger management platforms support one or more of these. Combining this with remote monitoring also lets you spot and respond to attempted unauthorised use in real time.
Sources
Recommended