How quickly do you know a charger is down?

Inside a minute. Liveness is judged by the messages actually arriving from the unit, not by a stored online flag, because a flag can lag a silent drop by a long way. One charger elsewhere read as online for forty-one days after its last real message. That is the failure this design exists to prevent.

What is predictive oversight?

The platform watches for repeat fault codes, failed sessions, a unit stuck in a faulted state and a charger that has gone quiet, and surfaces one heading for trouble before it goes down, so a visit happens on your schedule rather than the charger’s.

Do I need to check the dashboard every day?

No. Anything that needs you is pushed to you as an alert, scoped to what you are responsible for. The dashboard is for when you want to look, not something you have to patrol.

Run the site

Day to day.

What to look at, what the statuses actually mean, and what you are safely allowed to ignore. On a good week this page takes you two minutes a day.

The two minute routine

Open Overview, Dashboard. Read the Anomalies card. Anything red is today.
The alerts panel on Overview is the Anomalies card. Red marks a critical problem, here a charger offline for 2 days and 3 hours; amber marks a warning, here 7 OCPP errors in the last hour. View opens the charger. Sample screen with test data.
Glance at chargers offline. One that has been quiet more than an hour wants a look.
That is it. Everything else will find you.

The morning check, in one question

Do it yourself

Open Overview, Dashboard and read the Anomalies card.

Or just ask EVII™

Anything I need to deal with this morning?

How did the network do yesterday?

Which chargers have been offline more than an hour?

What the statuses mean

Status is reported per connector, not per charger, so a dual-port unit can be busy on one side and available on the other.

Stations, Chargers list for a test Operator: 8 chargers registered, with an Add Charger button, a search box and a Status filter button. The table lists the sample chargers TEST-TWR-01, TEST-TWR-02, TEST-LFT-01, TEST-LFT-02, TEST-INN-01, TEST-INN-02, TEST-DEPOT-01 and TEST-DEPOT-02, all Sample Charger Co. SC-7 on OCPP 1.6, with a colored dot for each connector, an Online or Offline badge, the 30-day start timeouts and the last heartbeat time. TEST-LFT-02 is Offline, its timeouts column reads Offline, no contact 2d, and its last heartbeat is two days earlier. — On Stations, Chargers each connector has its own dot, so one charger can show two states at once. Sample screen with test data.

Available. Idle and ready. Nothing to do.
Preparing. A cable is in but the session has not started. Normal for a few seconds. Stuck here usually means the driver has not started the session, or started it before plugging in.
Charging. Power is flowing. Nothing to do.
Suspended. Connected but not drawing. Usually the car, not the charger. A full battery or a car on its own schedule looks exactly like this.
Finishing. The session has ended and the cable is still in. Idle fees, if you set any, apply here.
Faulted. The unit is reporting a problem itself. Go to the fault playbook.
Unavailable. Somebody, possibly you, took it out of service deliberately.
Offline. The unit has stopped talking to the network. This is the one that matters most, because it is the state a charger fails into silently.

Suspended is usually not your problem

A car that has finished charging, or one obeying its own departure schedule, sits suspended for hours. It is the most common thing an operator worries about unnecessarily. If the driver is not complaining, nothing is wrong.

Live sessions

Every session running across everything you can see, updating as it goes: energy delivered, cost accruing, how long it has been going.

Watch or interrogate what is running

Do it yourself

Sessions, Active tab.
Click a session for its detail and its charger.

Or just ask EVII™

What is charging right now?

How much energy has the depot delivered today?

What happened in the session at Balboa around 6:14 last night?

Every OCPP message a charger has ever sent or received is stored and searchable. When a driver disputes a session, that record is the answer rather than a theory.

Sessions, Active tab, for a test Operator: 1 active, with an Export CSV button. The table has one live session with a pulsing Active badge: started 48 minutes earlier, 5.74 kWh delivered so far, 7.1 kW power, 48 minutes, no RFID tag, a running total of $1.61 and no payment yet. Clicking the row opens the session. — Sessions, Active tab: the running session’s energy so far, power, duration and running total. Click the row to open the session. Sample screen with test data.

A session that strands, because the network dropped or a unit rebooted, closes itself and bills the last meter reading we received. You do not have to find it, and the driver is never charged for anything after that reading.

Alerts

Alerts escalate on a schedule, so something nobody acknowledged does not sit unread forever. They are scoped to what you actually hold: a manager responsible for three buildings gets three buildings, not the network. That sounds obvious and it is unusual, and it is the reason alerts here are worth reading rather than worth muting.

Change who hears about what

Do it yourself

Settings, then notifications.
Set the channels and the escalation schedule for your account.

Or just ask EVII™

Stop emailing me about sessions, keep the offline alerts.

Who gets alerted when a charger at Plymouth goes down?

The rule behind every message we send

We tell people things they can act on and we do not tell them things they cannot. A host whose charger went offline can power-cycle it, so they hear. A host whose guest had a card declined cannot do anything about it, so they do not. If you are getting a notification you can do nothing with, tell us, because that is a bug in the rule rather than a preference.