EV CPO · Case study

EV CPO — NEVI uptime & OCPP fleet.

Two scenarios from a regional CPO running 47 NEVI-funded sites — a quarterly uptime packet that drafts itself, and four chargers that recovered without a truck.

A regional CPO operating 47 NEVI-funded DC fast-charge sites across three states. NEVI Title 23 requires 97% per-port uptime measured the way drivers experience it — not the way vendor RMS counts. Two scenarios: one compliance, one incident.

Read the scenarios
day 12federal NEVI submission — not day 32
47 secto upstream fault correlation
11 mintotal operator time — no truck dispatched
Operator scenarios

How this plays out in the field.

01

97.4% per port. Drafted live.

NEVI · Q2 reporting window opens · 47 sites · 188 ports
01
NEVI · Q2 reporting window opens · 47 sites · 188 ports

Reporting window opens. Analyst opens ObservOne.

NEVI Q2 reporting window opens. Historically the CPO’s compliance analyst has been hand-stitching per-port numbers across vendor RMS exports, payment-rail logs and CSMS session-ledger data — a 2-3 week exercise per quarter. ObservOne has been running the NEVI methodology continuously since install.

02
Compliance pillar · NEVI Title 23 · per-port methodology · sealed

Every excluded minute classified and attributed.

ObservOne correlated OCPP heartbeats, StatusNotifications, MeterValues and payment-rail authorizations continuously. Every minute each port was unable to deliver a session is classified: vendor fault, payment-rail timeout, network drop, utility event, scheduled maintenance — hash-chained and attributed.

03
NEVI Q2 packet · sealed · submitted day 12 of reporting window

Day 12. Federal funds released on time.

The quarterly federal report goes in on day 12 of the reporting window. The analyst spent 90 minutes reviewing, not two weeks assembling. Three vendors whose RMS numbers disagreed with the measured uptime now have specific per-port divergence evidence — a vendor-management conversation with leverage.

day 12
of the reporting window
Federal NEVI submission, not day 32. Federal funds released on time.
188
ports continuously measured
Per-port NEVI methodology applied across 47 sites — not vendor RMS heartbeat count.
NEVI Title 23OCPP 2.0.1OCA conformance
02

Four chargers, one substation, zero trucks.

PHX-EV-04 · 4 chargers · OCPP disconnect · within 28s of each other
01
PHX-EV-04 · 4 chargers · OCPP disconnect · within 28s of each other

Four chargers drop. Vendor RMS pages on-call.

Four chargers drop OCPP heartbeat within 28 seconds of each other. Vendor RMS pages on-call. Standard playbook: dispatch a tech to assess. Phoenix in July — the tech cannot be on site for 90 minutes. Two in-flight sessions are mid-delivery.

02
correlation engine · utility substation event · 14:08:11 confirmed

Upstream event confirmed in 47 seconds.

ObservOne checks upstream telemetry: site main panel, utility feed, adjacent sites on the same substation. The OCPP drop event window matches a utility-side substation switching event at 14:08:11 — confirmed against the public utility outage feed in 47 seconds. Expected recovery: ~6 minutes. In-flight sessions completing against cached energy readings.

03
NEVI · excluded minutes · upstream cause attached · no dispatch

No truck. Back online in 11 minutes total.

Dispatch suppressed. By 14:14:30 all four chargers are back online. In-flight sessions post final MeterValues. The 6-minute customer-facing outage is attributed to upstream utility in the NEVI exclusion stream with the cause attached. Total operator time: 11 minutes of supervised auto-recovery.

47 sec
to upstream correlation
From OCPP disconnect to confirmed utility substation switching event.
11 min
total operator time
No truck dispatched. In-flight sessions completed against cached energy readings.
NEVI Title 23OCPP 1.6
Further reading
EV / NEVI compliance5 min readMay 2026

How NEVI counts uptime — and why your RMS doesn’t agree

Vendor RMS measures the charger’s opinion of itself. NEVI measures whether a driver could pull up and complete a session. These are not the same number — and the gap is structural.

Read →
SLA & compliance evidence5 min readMay 2026

Carrier SLA disputes: why evidence wins and screenshots lose

Screenshots from vendor RMS lose SLA disputes. Hash-chained, Ed25519-signed event streams win them. Why the gap between testimony and evidence is wider than most operators realize.

Read →
Hands on

Reproduce this scenario
in our sandbox.

30 minutes with a solutions engineer. We'll preload a tenant with anonymised sites matching your topology. NDA-friendly.

Book a demo All use cases