The connection brings charger status, diagnostics, and charging sessions into the fleet and energy decisions that protect departure readiness.
Charger data connected
Status and diagnostics in context
Project scope defined
OCPP connections tested with selected charging-station models and firmware versions.
Defined OCPP 1.6J setup
OCPP 1.6J and the tested functions were validated for the defined project setup. Product and firmware scope follow the project configuration.
Tested via OCPP
Fenexity has tested the connection to Ekoenergetyka charging hardware. The applicable scope depends on the charging-station model, firmware, and required functions.
Charger status, 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 |
|---|---|---|
| Charging infrastructure | OCPP | Protocol profile, data points, and control functions are defined per project. |
| Telematics / OEM data | Project-specific | OEM APIs, telematics feeds, data points, and update intervals are connected per project scope. |
| Schedules / depot systems | Project-specific | 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 | 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. |
