Understanding the Data Model
Eve Control organizes your charging infrastructure around a set of core entities. Understanding how they relate to each other is key to managing your setup effectively.
Core Entities
1 Organisation
The top-level container. Every user, charger, location, token, and token group belongs to one or multiple organisations. Organisations are fully isolated from each other — you cannot see or manage another organisation’s data unless access is explicitly granted on entity level.
2 Charging Station
A physical Alfen EV charger connected to Eve Control via OCPP. Each charger is identified by its serial number (e.g. ACE0497739). Chargers can be assigned to locations and have tokens linked to them for charging access.
3 Location
A physical site (parking garage, office, housing complex) where one or more chargers are installed. Locations have a name, address, and other details. Token groups are linked to locations to grant access to all chargers at that site.
4 Local Token
Represents a charge card (RFID tag). Each token has a Hidden ID (the chip UID), a Visual ID (printed on the card), and a description. Tokens can be valid or invalid, and blocked or unblocked.
5 Local Token Group
A collection of tokens that share the same charging access. Instead of granting each token individual access, you place tokens in a group and link the group to locations. Token groups can be enabled or disabled.
How They Connect
Entities are linked through many-to-many relationships:
- A charger can be assigned to one or more locations
- A location can have multiple chargers and multiple token groups
- A token group can be linked to multiple locations and contain multiple tokens
- A token can belong to multiple token groups and have direct access to specific chargers