Available, but broken
The CMS still shows Available, while sessions fail to start or deliver almost no energy.
Asset intelligence
EV charger fault analytics that catch what chargers never log
A charger can show Available while no driver can charge. Iris R-One reads status, telemetry and session behaviour together to find Logged and Derived faults, and the cause behind them, across multi-OEM networks.
Available is not the same as usable.
Drivers often find the fault before the operator does.
Every OEM speaks differently
Error codes vary by manufacturer, so the same failure looks different across the network.
The same fault, again
Without root cause, a repaired charger fails the same way a week later.
Three fault types. This page covers the first two.
LoggedIn the CMS
Faults the charger logs and sends over OCPP.
e.g. Faulted, Unavailable, OEM error codeDerivedR-One
Faults R-One works out from status, telemetry and session behaviour when the charger logs nothing.
e.g. Shows Available but sessions never start, minimum-energy sessions, repeated interruptionsPredictedR-One
Forward-looking risk from trends and history, with the prescribed fix attached.
e.g. Contactor degradation flagged up to 3 weeks aheadExplore predictive and prescriptive maintenanceFrom raw charger data to a clear cause.
A network raises more alerts than a crew can clear. R-One ranks them by business impact, so effort goes to the assets that protect the most revenue.
Fault analytics in the web app
Business impact prioritisation
A risk matrix weighs alert criticality against the average energy a charger delivers. A serious fault on a busy charger ranks above the same fault on a quiet one, so ops starts where the loss is largest.
Multi-OEM normalisation
Vendor error codes mapped to common fault categories across 35+ manufacturers.
Derived fault detection
Non-starter sessions, minimum energy and minimum duration sessions, frequent offline or faulted states, and communication gaps.
Root cause and repeat faults
Faults classified by cause, with repeat and batch defects surfaced across the network.
True uptime and downtime
Downtime from status, heartbeat gaps and communication silence past a set threshold, per charger and connector.
Fault to work order
Any fault becomes a reactive job with its context attached.
Detect, classify, act.
Collect
Status, telemetry, sessions and OCPP messages from every charger.
Normalise
OEM error codes are mapped to common categories.
Detect
Logged faults are captured, and Derived faults are identified from behaviour.
Classify
Root cause and repeat patterns are identified for each fault.
Prioritise
Alerts are ranked by business impact, so the most valuable assets come first.
Act
A work order or remote action is raised from the fault.
In the mobile app
The fault context reaches the site.
Technicians see a charger's active alerts and OCPP logs in R-Vision, and findings and fixes recorded on site attach to the fault.
- Active alerts and recent status history on the phone
- Remote actions to troubleshoot before replacing parts
- Findings recorded on site close the loop on root cause
R-Vision is part of the mobile app. It gives the field team asset technical and operational data, plus remote actions to troubleshoot chargers.
Connected to the lifecycle.
Faults become reactive work in maintenance. Fault history feeds predictive and prescriptive maintenance.
- 01Feeds thisSet up assets
Inventory management
The record everything else depends on.Explore - 02Set up assets
Installation management
One controlled path from site readiness to go-live.Explore - 03Fed by thisMaintain assets
Maintenance management
Fix what broke and service what is due, on one work engine.Explore - 04You are hereAsset intelligence
Fault analytics
Understand what is failing now, and why. - 05Fed by thisAsset intelligence
Predictive and prescriptive maintenance
Know what will fail, weeks before it does, and what to do about it.Explore
Operators
Operators running Iris R-One
Frequently asked questions
A fault the charger never logs. R-One works it out from status, telemetry and session behaviour, for example a charger that reports Available while sessions never start or deliver almost no energy.
A fault the charger reports itself over OCPP, such as a Faulted or Unavailable status or an OEM error code.
By business impact. Each alert is placed on a risk matrix that weighs alert criticality against the average energy the charger delivers, so a serious fault on a busy charger is addressed before the same fault on a quiet one. Operations teams spend crew time where it protects the most revenue.
Yes. OEM-specific error codes are normalised into common fault categories, so faults compare across a multi-OEM network.
From Faulted, Unavailable and Offline states, plus heartbeat gaps and communication silence beyond a set threshold, per charger and connector.
R-One records true uptime per charger and connector and keeps an evidence trail for every fault and repair, ready for regulator and client reporting.
See R-One on a live network.
Share the size and make-up of the charging network, and the walkthrough will show what R-One surfaces on it. Demos run about 40 minutes.
Offices
