The challenge
Operating an EV charging fleet inside a national transmission system operator means meeting two sets of requirements at once. On the operations side: real-time charging-session control, OCPP 1.6/2.0.1 compliance, billing accuracy down to the kWh, integration with corporate billing systems. On the governance side: full audit trails, no outbound dependencies on non-EU vendors, alignment with NIS2 supply-chain controls, and a stack that conforms to the operator's existing security posture.
The off-the-shelf OCPP charge-point management systems on the market in 2025 were built for fleet operators and retail chains, not for a TSO. They assumed cloud SaaS as the default deployment model, treated audit logging as an add-on, and had no native concept of AI-driven anomaly detection or session intelligence. Adapting them to a TSO's environment meant either heavily modifying a closed product or stitching together three different vendors.
Why NEXUS
NEXUS was designed from day one as an AI-native OCPP open platform. Three architectural commitments differentiate it from the existing market:
- OCPP 1.6 and 2.0.1 native, with the open extension surface. Every charge-point message is a first-class object in the platform, not a payload tunnelled through a cloud abstraction. The OCPP layer is the platform, not a feature wrapped on top of one.
- Built around an AI agent runtime. Wave Runtime — the same orchestration layer behind WaveOps and WaveFlow — is embedded inside NEXUS, available to every charging-session workflow. Anomaly detection, session-level reasoning, and natural-language operations queries are first-party features, not third-party integrations.
- Deployable inside the operator's perimeter. EU-hosted by default, no outbound calls to non-EU AI APIs, and no telemetry that leaves the customer's network. The same code that runs the public charge-point API runs the audit log.
What we deployed
At ELES, the NEXUS deployment covers the operator's internal charging fleet and the back-office systems behind it. The architecture has four layers:
- Charging-point connectivity. OCPP 1.6 and 2.0.1 endpoints, with native MQTT and WebSocket transports. Every connected charger registers, authenticates, and exchanges session messages through the NEXUS gateway.
- Session control + billing. Live tariff resolution, session metering, transaction reconciliation, invoicing-ready output. Every session is logged with full context (driver, vehicle, charge-point, tariff, kWh, duration, faults if any) into an audit-grade event store.
- AI agent layer. Wave Runtime runs operational agents on top of the session log: anomaly detection (sessions that look fraudulent, faulty, or outside SLA), natural-language operations queries ("show me all sessions over 90 kWh in the last week with reported faults"), and reporting automation.
- Integration to ELES back-office. Billing, asset management, identity (employee directory), incident workflow. Every NEXUS event surfaces into the operator's existing tooling without an intermediate cloud.
What was different about this deployment
Three things made this engagement structurally different from a typical SaaS rollout:
1. The same engineers wrote the code and installed it
ELES did not pay for a vendor and a separate systems integrator. The Wavenetic engineers who built NEXUS configured the deployment, ran the integration with ELES's existing systems, and remain the support contact today. There is no offshore handoff and no escalation tier between the customer and the people who wrote the runtime.
2. Audit trail by architecture
Audit logging in NEXUS is not a configurable feature — it's the storage substrate every other feature is built on. When ELES's compliance team asks who initiated a session, who authorised a tariff change, or what the AI agent recommended at 02:47 yesterday, the answer is in the same data store the operations dashboard reads from. There is no second pipeline, no after-the-fact log aggregation, and no event that can happen without leaving a record.
3. EU supply chain, end-to-end
ELES's supplier-risk frame requires that every component in the operational stack be traceable to an EU entity, with a clear governance and continuity story. NEXUS is built by Wavenetic in Slovenia, deployed within the EU, with an open OCPP layer and a runtime ELES's own engineers can inspect. The supply chain story matches the operator's framework without exception.
What's running today
NEXUS is live at ELES and used by operations staff daily. The platform handles live billing for active charging sessions, real-time session orchestration across the connected charge-point fleet, and routes operational events into ELES's existing back-office. Specific operational metrics are confidential to the operator and not published here.
Wavenetic is open to providing detailed operational metrics under NDA on request from qualified prospects. Contact us to discuss.
What's next
The ELES deployment is the reference architecture for what we now offer to other critical-infrastructure operators across the EU: a self-hosted, AI-native OCPP open platform that deploys inside the operator's perimeter, integrates with their existing billing and identity systems, and ships with the audit and compliance documentation already in the box.
If you operate national or regional EV-charging fleet inside a regulated environment — TSO, DSO, municipal operator, public-sector fleet — and the off-the-shelf cloud CPMS market doesn't fit your governance frame, we'd like to talk.