Operator Manual

You own the chargers.
Here is how you
run them.

Everything an operator can do on the EV Initiative network, written so you never have to ask us how. Every job on every page appears twice: the way you click through it, and the sentence that makes EVII™ do it for you.

What you own, what we run

You own the chargers. That does not change, and it is the reason the rest of this works the way it does. Stop paying us and you keep the hardware, keep your data, and take both wherever you like.

What we run is the operation. Drivers arrive, sessions start, cards get charged, money lands in your bank, a charger goes quiet and somebody notices inside a minute. None of that should need a person on your staff, and none of it does.

The one number

$8 per charger per month. A dual-port unit is one charger, so it is still $8. Load management is $4 per managed charger where your service needs it. You keep 85% of session revenue. Hosts pay no per-session fee, no setup fee and no term.

Everything else in this manual is detail underneath that sentence.

Which kind of operator you are

The console shows you what your role allows, so two people reading this manual will not see the same screens. Find yourself below and start there. Each one is a complete walkthrough of that job and nothing else.

Roles decide what you can do. Scoping decides where. A regional manager and a building admin can hold the same role and see entirely different networks. Nobody can grant a role or a scope above the one they hold, and that is enforced on every request rather than by hiding a menu.

Everyone, whatever their role, needs two more things: a bank account connected through Stripe before any money can move, and the app on their phone so an offline charger reaches them before a resident does.

Two ways to do everything

Every task in this manual is written twice, side by side. On the left is the click path, for when you want to see it happen. On the right is what to say to EVII™ instead.

For example: find out what is broken right now
Do it yourself
  1. Open Overview, Dashboard.
  2. Read the Anomalies card. Anything red needs you today.
  3. Click through to the charger for the detail and the message history.
Or just ask EVII™
What is offline right now?
Anything I should worry about at Balboa this morning?

She answers inside your own permissions and nobody else’s. She cannot see another operator’s network, and she cannot give herself or you any access you do not already hold.

The Anomalies card from the Overview dashboard for a test Operator, with a count badge of 2. The first row has a red dot: TEST-LFT-02, Sample Lofts (sample data), Offline for 2d 3h. The second row has an amber dot: TEST-INN-02, Sample Inn (sample data), 7 OCPP errors in last hour. Each row has a View button that opens the charger.
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.
The EVII assistant, opened as a side panel in the admin console by a test Operator. A Recent row at the top repeats the last question. After the greeting, the operator asked: What is offline right now? EVII answers that 7 of the 8 chargers are online, that the offline one is at Sample Lofts (sample data), where 1 of 2 chargers is online so the site shows as partial, that every other site is fully online, and to open Chargers to see which unit it is and when it last checked in. Tool tags above the answer read get_scoped_charger_status and get_scoped_location_status, and a Network status ring reads 88 percent online, chargers 7/8, faulted 1. The message box at the bottom reads Ask EVII about your network, with a note that EVII only sees your own scoped data. The answer is a canned sample reply.
The same question asked of EVII™ in the console. She answers from your own scoped data: how many chargers are online, and which site has the one that is not. Chargers then shows which unit it is. Sample screen with test data.

Anything that changes something, she proposes first and waits for you to confirm. Anything that only reads, she just answers. That split is in the code rather than in her instructions, which is why it holds.

Where everything is