Write an EVSE procurement spec that correctly requires OCPP 2.0.1 certification
domain: ev-charging.ocpp-certification · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Require OCA (Open Charge Alliance) OCPP 2.0.1 certification from an accredited independent test lab (DEKRA, DNV, KSGA, Korea Testing Certification Institute, or Korea Testing Laboratory) rather than accepting a self-declared "OCPP 2.0.1-compatible" claim
Note the Dec 2025 simplified OCPP 2.0.1 Certification Program made Reservations, Local List Management, Advanced Device Management, and Advanced User Interface optional add-ons to the Core profile — specify which optional profiles the project actually needs
For DC fast chargers with Plug & Charge ambitions, additionally require ISO 15118 profile certification, since that is tracked separately from base OCPP 2.0.1 certification
Cross-check NEVI's federal minimum (OCPP 1.6J or higher) against the project's own OCPP 2.0.1 requirement — a 2.0.1 spec exceeds, and is compatible with, the federal floor
Known gotchas
NEVI's own regulatory floor is OCPP 1.6J, not 2.0.1 — don't assume federal funding requires 2.0.1; exceeding the floor is a site-host choice
A vendor's marketing claim of "OCPP 2.0.1 support" is not the same as OCA certification — ask for the certificate or lab report
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?