Chargers generate a great many events and only a small proportion warrant human attention. Automation that creates a ticket per fault event produces a queue nobody can work, and the response is to stop reading it.
The valuable automation is the filtering, not the ticket creation.
Most reported faults need no action
A vehicle that stopped drawing, a session ended by the driver, a brief communication interruption that recovered, a connector unplugged mid-session. All appear as events and none requires anyone to do anything.
Suppressing these is the first and highest-value step. A queue containing only actionable items gets worked; one containing everything gets ignored.
Wait before raising
Many conditions clear themselves within minutes. Raising immediately produces tickets that are already resolved when someone opens them, which erodes confidence in the system.
A delay before raising, with automatic cancellation if the condition clears, removes a large proportion of the noise at almost no cost in response time.
Group by cause, not by event
A site losing connectivity generates a fault from every charger. Those are one incident, not many, and creating a ticket per unit obscures the actual problem.
Correlation by site, by time window and by fault type turns a flood into a single actionable item with a known scope.
Enrich at creation
A ticket carrying this needs no investigation before dispatch. One carrying only a code requires someone to gather it, which is the work automation was supposed to remove.
- The specific charger, connector and site.
- The standard fault code and any vendor-specific detail.
- Firmware version and recent update history.
- Recent session and status history for that unit.
- Whether the same fault has occurred here before, and when.
Route by what it will take to fix
Faults that a remote reset will likely clear should be attempted remotely before anyone is dispatched. Faults requiring a part should carry the part. Faults that are vehicle-side should not become tickets at all.
Routing on that basis, rather than on severity alone, is what reduces unnecessary site visits, which is where the cost is.
Close with a cause
A ticket closed as resolved without a recorded root cause guarantees the fault recurs and is investigated again. Requiring a cause at closure, from a defined list rather than free text, builds the data that makes patterns visible.
Without it, a network learns nothing from its own faults, which is the most common failure of charging operations at scale.