Integration risk is one of the biggest blockers in depot electrification. Fenexity makes supported standards, repeatable project integrations, and customer-specific integration paths visible before procurement asks.
OCPP-first charger connection
OCPP diagnostics and fault context
Status labels prevent overpromising
OCPP chargers, diagnostics, local controllers, CSMS interfaces, charger-state changes, and fault context.
Schedules, blocks, dispatch plans, vehicle state of charge, telematics, and OEM APIs.
Meters, grid limits, tariffs, PV, batteries, EMS, and reporting exports.
| Category | Status | Current public scope |
|---|---|---|
| OCPP chargers | Supported | OCPP 1.6, OCPP 2.0.1, and OCPP 2.1 for charger connection, status, diagnostics, fault context, and operational alarm handling. |
| Telematics / OEM data | Project-specific integration | OEM APIs, telematics feeds, data points, and update intervals are connected per project scope. |
| Schedules / depot systems | Project-specific integration | Schedule, block, dispatch, and depot-system data are connected per project; VDV standards are especially relevant in bus operations. |
| Meters / EMS / PV / battery | Project-specific integration | Meters, external EMS platforms, PV, and battery systems are connected according to available signals and control responsibilities. |
| Reporting exports | Supported / project-specific | CSV and API exports are supported. BI exports and ESG formats are defined per target system, data model, and reporting method. |
