zevOS

01Operations

When a spreadsheet stops working: running a charging NOC

Somewhere between fifty and two hundred connectors, informal operations stops scaling. What replaces it, and in what order.

FOzevOS Field Operations · Customer operations
22 April 2025 · 2 min read

At twenty connectors, one person knows every charger by name and operations is a group chat. At two hundred, that same arrangement is why faults sit unnoticed for four days. The transition is predictable and most operators go through it late, after a bad month rather than before one.

The three things that break first

  1. 01Detection. Nobody notices a charger is down until a driver complains, which means your detection latency is set by your traffic, and quiet sites go dark for weeks.
  2. 02Ownership. A fault is seen by three people, each assuming one of the others is handling it.
  3. 03Memory. The same charger fails the same way for the fourth time and nobody realises, because the previous three fixes live in three different conversations.

What to put in place, in order

This sequence solves the three above with the least process added. Do not skip ahead — a ticketing system without detection just gives you an empty queue.

StepWhat it isSolves
1. AlertingCharger offline, faulted, or zero sessions in N daysDetection
2. A queueEvery alert becomes a ticket with one ownerOwnership
3. Outcome codesEach ticket closes with a cause and a resolutionMemory
4. A daily reviewFifteen minutes on what is open and what is repeatingEverything else

Staffing it honestly

A charging NOC is not a twenty-four-hour room until you are considerably larger than most Indian operators currently are. What it is, at two hundred connectors, is one person whose actual job is the queue — not a field technician who also watches the dashboard, and not a founder checking it between meetings.

The moment that role exists, the metrics start moving, because someone is finally accountable for them. Before it exists, no amount of tooling helps.

Four numbers on one screen

Connectors serviceable right now. Faults open, by age. Dispatches this month against last. Sessions failed, as a share of attempted. Everything else is diagnostic detail that belongs one click away — those four are the state of the network.

scaleprocessfield

Get the next one by email

One email a month. Operations notes, unit economics and policy changes that affect your tariff.