Sessions
Every charging session is displayed in “Sessions”. Detailed information is shown to track errors or test functionality.
Authorization
This table displays all relevant authorization requests, and has various sub-items.
Tabs “AuthorizeStart” and “AuthorizeStop” show every authorization that has been requested via either RFID or Plug & Charge
On the other hand, tabs “AuthorizeRemoteStart” and “AuthorizeRemoteStop” display every authorization that has been initialised remotely (such as an authorization by the helpdesk).
The next tab is “ChargeDetailRecord”. A Charge Detail Record (CDR) is sent to the HBS after every charging session. It contains information about the charging session (such as the timestamps defining the beginning and end of the charging session, the Provider ID and the Operator ID).
The last Tab is "GetChargeDetailRecord". Here you can see an overview of all CDRs.
Authentication Data
“Authentication Data” displays for EMPs the authentication data they have pushed to the HBS, while the CPO sees the authentication data downloaded from the system.
EVSE Data & Status
“EVSE Data & Status” displays the EVSE data and the status of the charging station. The CPO pushes this information while an EMP partner can pull it from the HBS.
EVSE data is static. It contains information such as address, geo coordinates and charging station name. The EVSE status is dynamic, meaning the data is updated with every event, such as a charging process. Whenever a charging session is started, the status switches to “occupied”, when the session is stopped, it switches back to “available”.
Reservation
In this table you can see Reservation Requests.
Mobile Authorization
Registered in “Mobile Authorization” is every charging request that has been sent via app. There are three sub-tabs. The Tab “MobileRemoteStart” for every start of a charging session and “MobileRemoteStop” for every stop of a charging session.
The last tab is “MobileAuthorizeStart” for every authorization request.
Please note that the options “AuthorizeRemoteStart” and “AuthorizeRemoteStop” from “Authorization” - section is not the same as “MobileRemoteStart” and “MobileRemoteStop” from the "Mobile Authorization”-section.