23. Station Operations, IoT and Physical Data Infrastructure

A charging station's economic value arises from the service it provides in the physical world. Transferring energy to the vehicle, the driver paying for this service, keeping the equipment in working order and managing operating expenses are the core components of this value. The reliability of the digital investment model also depends on these activities being measured correctly and recorded consistently with one another.

eBattery's physical data infrastructure establishes this link between the charging site and the digital platform. Energy measurements from meters, socket operating statuses, charging sessions, payment transactions and maintenance records are linked under a common project identity. This way, the station performance presented to investors can be traced back to the service delivered on site.

In this structure, IoT enables data collection from physical devices and monitoring of device status. The charge management system manages station operations. Data verification and reconciliation layers check the consistency of records coming from different sources. The oracle and onchain record infrastructure supports sharing information that has passed the verification process with the digital investment system.

The core principle is to preserve the records on which every significant outcome, from physical activity to the financial report, is based. How much energy a station delivers, how much revenue it generates and what costs it is operated with are not treated as disconnected indicators. Each is part of a set of records that explain the same operating period and have a defined source and calculation method.

23.1 From Physical Charging Activity to Digital Record

When a driver arrives at a charging point, a fairly simple process begins from the user’s perspective: the vehicle is connected, the session is started, energy is transferred, and the transaction is completed. Behind this experience are many events that carry different meanings physically, technically, and financially.

Connecting the cable to the vehicle, authorizing the user, starting energy transfer and collecting payment are not the same event. For example, even if the user is authorized for payment, energy transfer may not start because communication with the vehicle cannot be established. Similarly, payment collection for a session whose energy transfer has been completed may be concluded later.

eBattery’s data model preserves these distinctions. Each stage is processed with its own status information and timestamp:

Operating stage Core record created What it means for operations
Connection Vehicle and socket connection status Establishing the physical connection
Authorization Sign-in permission and method information Checking authorization to use the service
Launch Session ID and starting measurement Recording the charging process
Energy transfer Energy, power and status measurements Measuring the service provided
Termination End reading and reason for termination The session closing technically
Pricing Tariff version and calculated fee Calculating the service consideration
Collection Payment, refund and settlement records Tracking the financial movement
Reporting Reconciliation result and relation to the period Preparing operating and investor reports

These records are linked to one another through the station e-ID and the relevant session ID. This way, it can be explained retroactively which sessions make up the amount of energy seen in a report, or which service a revenue record arose from.

Moving to a digital record does not mean that all data is sent directly to the blockchain. High-frequency device measurements, technical logs and personal information are kept in operational systems with controlled access. Verified summaries, report references and integrity proofs suited to the intended use are passed to the onchain layer.

This separation protects both operating performance and the meaning of the data. The safe operation of a charger is not made dependent on the confirmation of a transaction on the blockchain, and the records presented to investors are not produced independently of physical activity.

23.2 Meter, Socket and Charging Session Data

To understand a station correctly, it is necessary to know which information comes from which physical component. The energy meter at the site entrance, the charger's measurement system and the session record of a single socket answer different questions.

The meter at the site entrance may show the total energy the facility draws from the grid. Charging session metering, on the other hand, helps determine the amount of energy for the service provided to a specific vehicle. There may be a difference between these two values because of power conversion, auxiliary systems, standby consumption and measurement limits.

Rather than combining these measurements under a single “energy” heading, eBattery classifies them by their source.

Meter data, includes the measurement point, meter ID, energy direction, unit and time. Whether the measurement belongs to the station entrance, a specific device or a charging output is clearly defined.

Socket and charging output data, covers the connection type, usage status, power limit and fault information. The number of physical connections and the number of vehicles that can be served at the same time are kept separate. A device having two connections does not mean that two vehicles can always be charged at the device's full power at the same time.

Session data, brings together the start and end of the service, the energy measurements, the authorization reference and the reason for termination.

Data group Example areas Purpose of use
Identity Station e-ID, device, EVSE, socket and meter identity Linking the measurement to the correct physical source
Energy Start and end meter readings, kWh transferred Calculating the service quantity
Electrical status Power, current, voltage Performance and technical status monitoring
Session Start, end, pause and reason for ending User experience and operations analysis
Device status Ready, in use, faulty or offline Producing Map and operational statuses
Commercial context Tariff version, pricing and payment reference Matching the service with financial records
Data quality Source, time received, verification and completeness status Assessing whether the record is usable

Here, the distinction between power and energy is especially important. kW, the power level at a given moment; kWhrefers to the amount of energy transferred over a given period. The device’s nameplate power is not treated as power that is sustained throughout a session.

Information such as the vehicle's battery level is used only when vehicle and device communication supports it. A value that cannot be accessed is not filled in with an estimate and presented as an actual measurement.

In projects where the hardware supports it, signed meter data is also included in the record chain. The Open Charge Alliance's related implementation work describes the method for carrying signed measurements between the charging station and the management system. Such a signature helps verify the origin and integrity of the measurement record; it does not, on its own, guarantee the accuracy of the physical metering system.

23.3 OCPP and the Charging Management System

In eBattery's station communication architecture, OCPP is the core protocol approach between charging devices and the central charging management system.

OCPP supports managing chargers from different manufacturers through a common communication standard. Developed by the Open Charge Alliance, the protocol provides a common structure for device status, transaction management, remote control and other functions supported by the relevant version. While OCPP 2.0.1 includes advanced features in device management, transaction tracking and security, OCPP 2.1 brings additional capabilities related to bidirectional energy transfer and distributed energy resources.

eBattery's technical approach for new stations, a management architecture that provides controlled compatibility across versions with hardware verified for OCPP 2.0.1 and later capabilities as its basis. OCPP 2.1 features are assessed in line with project requirements and hardware support. The choice of version relies on functions verified in the field, in addition to the protocol name written on the device.

When existing OCPP 1.6 devices need to be integrated, separate protocol adapters and acceptance tests are used. OCPP 1.6 and 2.0.1 are not directly compatible versions; records coming from different versions must be converted into a common data model.

The Charging Station Management System (CSMS) is the operational center of this communication. Its main tasks are as follows:

  • Managing how devices are connected to the system and authorized.

  • Tracking socket and session statuses.

  • Carrying out remote start, stop and configuration operations.

  • Receiving energy measurements and linking them to the relevant session.

  • Applying power limits and load management policies.

  • Monitoring fault, connection and maintenance events.

  • Recording authorized software and configuration changes.

Sending a command and its being carried out in the field are tracked as separate states. For example, a "start charging" request being accepted does not by itself show that energy transfer has started. The app confirms the actual state of the operation through subsequent events coming from the device.

OCPP certification is also assessed together with its scope. In the OCA's certification structure, core functions are separate from profiles such as advanced security and smart charging. For this reason, during procurement it is checked which product, software version and functions the certificate covers.

The CSMS, the payment system and the blockchain layer are connected, but each carries a different responsibility. The CSMS manages physical charging operations; the payment infrastructure handles collection; and the oracle and onchain layers make sure the relevant records are shared with the investment system.

23.4 IoT Gateways and Connectivity Infrastructure

A station site does not consist only of the charger. Depending on the project’s structure, there may also be incoming meters, energy management equipment, environmental sensors, network devices and local control components. The IoT connectivity architecture enables these components to communicate reliably.

A charger that supports OCPP can connect directly to the CSMS with a suitable network connection. It is not mandatory to route each device's communication through an additional gateway. A gateway is used particularly to connect auxiliary meters or equipment with a different industrial interface to the shared data infrastructure.

eBattery's connectivity approach has three levels:

Site connection: Covers communication between chargers, meters and local control components. Depending on equipment support, Ethernet, serial communication or suitable industrial protocols are used.

Hub connection: Provides the station site’s access to central systems. Fixed internet and cellular connections are assessed according to the site’s coverage conditions and the criticality of the service.

Local continuity: Ensures that safe power limits, required records and permitted operating functions are maintained on site when the connection to the center is lost.

Redundancy design does not treat two connections that could be affected by the same outage as independent. Common points of failure for lines that rely on the same modem, the same power source or the same operator infrastructure are assessed separately.

Charging devices, management interfaces and, where available, guest internet access are kept in separate network segments. Instead of controlling devices through management screens exposed to the internet, authorized and logged access methods are the basis.

Local limits take priority in power management. The safe operating behavior to apply when the cloud connection is lost, so that the site’s connection capacity is not exceeded, is defined in advance. Electrical protection systems and emergency stop functions are not made dependent on a remote server or an oracle service.

23.5 Device Identity and Secure Communication

To know which station a piece of data comes from, a station name appearing in a message is not enough. The identity and authority of the device connected to the system, and the physical project it belongs to, must be verified.

eBattery, manages the permanent project ID and the physical device ID separately. The station e-ID represents the continuity of the economic and operational project. The device serial number, certificate and hardware record identify the physical equipment serving in that project between specific dates.

When a new device is commissioned, the following information is linked:

  • Manufacturer, model and serial number.

  • Hardware and software version.

  • The e-ID of the station it is linked to.

  • The communication endpoint it is authorized for.

  • Device identity information and certificate status.

  • Installation, acceptance and commissioning records.

The security approach for new installations is based on encrypted communication in which the identity of both the device and the server is verified. Separate credentials are used for each device; using a shared administrator password or a shared private key across the entire fleet is not accepted.

Cryptographic keys are protected in secure storage components supported by the hardware. Certificate validity, renewal and revocation processes are monitored centrally. If a device is suspected of being compromised or tampered with without authorization, the relevant credentials can be disabled; because the communication of other stations is not tied to the same credential, the scope of the incident is limited.

Security is not applied only when a connection is established. The source and integrity of software updates are verified, changes are tested on a limited group of devices, and an appropriate rollback procedure is prepared. Remote maintenance permissions are limited per task; additional approval and transaction logging are used for critical operations.

Digitally verifying a device does not mean that all measurements within it are physically correct. For this reason, the device identity check works together with meter verification, site inspection and data consistency checks.

23.6 Data Collection, Time Alignment and Unique Record Management

For data from different devices to be assessed together, a common order of time and records is needed. The start of a charging session, a meter reading and a payment result may arise in different systems; these records may also reach the center in a different order from the one in which they occurred.

The eBattery data model separates at least three pieces of time information:

Time information Description
Event time When the transaction took place on the device or in the source system
Time received When the record reached the central infrastructure
Processing time When the record passes the verification and related calculation stage

A common time reference is used in technical records; the relevant local time zone is applied separately for user screens and financial periods. Deviations in device clocks are monitored. Records whose time is not reliable are not treated with the same verification status as normal records.

A single event being delivered twice should not create two separate economic transactions. For this reason, each record is deduplicated using fields such as source device, session ID, protocol event reference or sequence information. Differences between versions and manufacturers are preserved when converting to the common record model.

The aim here is, instead of assuming that each message will arrive only once in the communication network, is to ensure that the result is applied only once even if the same message arrives again. When the same end record arrives again, the energy amount is not added twice; when the same payment notification is processed again, no second charge or second revenue record is created.

Data is handled in three layers:

Source record: Preserves the original content received from the device or an external system, along with the context in which it arrived.

Regulated record: Units, identities and event types converted into a shared model.

Verified output: The result that has passed the checks required for reporting, charging or onchain sharing.

When an incorrect match is corrected, the old record is not silently replaced. The reason for the correction, the authorized person who made it and the link to the new version are kept. This makes it possible to explain why reporting results change over time.

23.7 Data Protection During Connection Interruptions

A loss of internet connection is not the same as a loss of the station's electrical connection. A station can keep operating locally while unable to communicate with the central system; when power is cut, the device's operation may also be affected.

eBattery's outage design treats these situations separately. On compatible devices and field components, critical session records are stored in persistent local memory. When the connection returns, pending records are resent, with confirmation that the central system has accepted them.

Local logging capacity is sized by taking into account expected session density and outage duration. Memory usage is monitored; the behavior to apply when there is a risk of losing records is defined in advance. Controlled methods are used, such as generating a warning, prioritizing critical records or limiting acceptance of new sessions, instead of silently deleting data.

Offline operation and offline payment authorization are separate things. A device being able to keep a session record does not mean every user can receive payment approval without a connection. Whether a new session can be opened is determined by the local authorization policy, the payment method, hardware support and the terms of the relevant project.

The basic approach during an outage is as follows:

Status Operating approach Data approach
Loss of connection to the central system Local safety and permitted operation policy applies Events are stored locally
Payment service being unreachable Acceptance of new sessions is managed according to the payment policy Authorization and capture status are kept separate
Power outage The device enters a safe state The last persisted records are preserved, gaps are flagged
Blockchain or oracle access issue The physical operation is run independently Verified records to be published are held
Connection restored Device and session states are reassessed Pending events are processed with deduplication

This distinction should also be visible on the map. The last “available” status of a station that has not been heard from for a long time is not shown as current information. Data freshness is taken into account and, where appropriate, connection uncertainty is indicated.

Records that arrive late are attributed to the period in which they occurred. If the period has been closed, the relevant correction process is run; past revenue or energy totals are not rewritten without explanation.

23.8 Reconciliation of Energy Measurements and Payment Records

For station revenue to be reported reliably, the energy record and the payment record must explain the same service. However, there is no direct equality between these two records that holds in every case.

A session in which energy was transferred may fall under a free campaign. A pre-authorization taken for payment may not be a final charge. Part of the amount charged may be refunded later. Taxes and payment service deductions may also make the gross charge differ from the amount the operator can use.

eBattery carries out reconciliation at four levels:

1. Technical alignment

The session’s start and end readings, interim readings, and device statuses are assessed together. Events such as a change of measurement unit, a meter reset, or a device replacement are checked.

2. Tariff reconciliation

The service fee must be recalculable using the tariff version in effect for the session and the applicable fee components. Where present, energy, time, idle or session fees are shown separately.

3. Payment reconciliation

The calculated fee is compared with authorization, final capture, refund, dispute and payment provider settlement records.

4. Project and period reconciliation

Verified revenues are linked to the relevant station project and operating period. Energy supply, rent, maintenance and other operating expenses are linked to separate source documents.

For example, if a session’s verified start reading is 10,240.0 kWh and its end reading is 10,268.4 kWh, and both measurements are from the same meter and within a valid measurement limit, the session energy is calculated as 28.4 kWh. This amount is used in calculating the relevant tariff. If the amount reported by the payment system differs, the reason for the difference is investigated; the measurement is not changed to match the payment amount.

Likewise, the energy entering the site is compared with the energy distributed to sessions. Auxiliary consumption, conversion losses and meter time intervals are taken into account. Unexplained differences are put under review as possible missing data, measurement problems or physical faults.

The IoT system measures the amount of service; distributable net profit is calculated by assessing verified operating and financial records together. Rent, tax, insurance or maintenance expenses cannot be learned from a socket sensor. These expenses are included in the data chain with documents, approvals and payment references.

The reports that form the basis of monthly profit distribution go through the relevant reconciliation and period-close checks. Unresolved differences are not hidden; their effects and the accounting entries to be applied are managed in a traceable way.

23.9 Maintenance, Fault and Uptime Tracking

A station’s quality cannot be measured only by whether it appears connected to the system. A device connected to the internet may not be able to deliver energy. Another device whose communication has been lost may still be serving locally.

For this reason, eBattery tracks communication status, technical availability and actual service success as separate indicators.

Indicator Question it answers
Contact accessibility Can current data be obtained from the device?
Technical availability Is the relevant outlet able to provide a charging service?
Service access Can the driver access the point during the stated opening hours?
Session start success Do valid start attempts turn into energy transfer?
Session completion status For what reasons do started transactions end?
Power performance Is the power offered compatible with the vehicle and site conditions?
Response and repair time How much time passes from detecting the problem to the service coming back?

Uptime ratios indicate at what level the measurement is made. One of four outlets at a station being faulty is not reported as the same result as the whole station being completely out of service. At the same time, the fact that only one outlet is working does not make the loss on the other outlets invisible.

In the calculations, the service calendar, planned maintenance and unknown-status periods are clearly separated. Where planned maintenance is excluded from a given indicator, this method is stated; the report may not be changed merely to show higher availability.

Maintenance management is tracked from detection of the incident to its verified closure:

  • Identifying a fault or performance degradation.

  • Assessing impact and safety priority.

  • Remote diagnosis and appropriate intervention.

  • Directing the field team if necessary.

  • Processing parts, labor and warranty records.

  • Post-repair check and testing.

  • Confirmation that service has been restored.

A work order is not closed on the assumption that the device has recovered. The relevant measurements and, where necessary, a test session confirm the result of the intervention.

Maintenance records also give meaning to investor reports. Whether a drop in energy sales comes from lower demand, a faulty outlet or a site access problem can be explained through these records. For the use of renewal and major maintenance reserves too, it is tracked which equipment and which need the expense corresponds to.

23.10 Device Renewal and Station Relocation Records

eBattery’s project identity is not tied to the serial number of a particular charger. Physical equipment may be renewed over time; capacity may be increased, or, within the project terms, the station may be moved to another location. Identity continuity is maintained so that economic rights and operating history can be tracked correctly through these changes.

When a device is replaced, the record of the old equipment is not deleted. The decommissioning date, its last valid measurements, the status of open sessions, and the reason for replacement are recorded. The new device is defined under the same project with its own serial number, meter ID, security information, and acceptance tests.

Especially when meters are replaced, the old and new readings are not simply subtracted from each other. Each meter is evaluated within its own valid operating period; total project energy is built by combining verified period records.

The device replacement file covers the following elements:

  • Reason for the change and technical assessment.

  • Decommissioning details of the old device.

  • Technical specifications and connectivity structure of the new device.

  • Purchase, warranty and installation documents.

  • Tests performed and the time of return to service.

  • The cost of the change and its source of funding.

  • Effect on capacity, service quality and operating expenses.

Relocating a station is a broader change. It may mean a new location, different access conditions, an energy connection, a rental structure and user demand. For this reason, it is not considered complete simply by changing the coordinates on the map.

During relocation, the technical and commercial suitability of the new site is assessed and the necessary permits and contracts are checked. A historical link is established between the last activity at the old location and the first activity at the new one. Downtime, relocation expenses and recommissioning results are included in the project record.

The continuation of a project identity does not allow a different economic project to be presented under the same identity without disclosure. Changes affecting investor rights or the project’s core terms are carried out under the contractual authority and approval procedures disclosed in advance. Relocation or renewal does not by itself result in new investment units being issued or existing rights being reduced.

Warranty replacement, recycling or regulation-compliant disposal of decommissioned equipment is also recorded. Fees and expenses arising from these operations are linked to the project accounts.

In this way, the station's digital history covers all device generations after the initial installation, maintenance periods and location changes. In addition to seeing the equipment running today, the investor can also follow which investments the project is sustained with and how its operating capacity has been maintained over time.

Search eBattery

Search for a feature, guide or topic.

Starting pointsFinding a charging station →Sample RWA project →Guides and news →