Use the process monitor effectively with this overview. This article describe different sections of the process monitor. You will also find related articles if you wish to know more about each topic.
Authorization view allows you to access the data stored related to your charging sessions. You will find all relevant authorization requests.
Authorization requests sent via RFID card or Plug&Charge
Use the tabs “AuthorizeStart” and “AuthorizeStop” to display every authorization that has been requested via either RFID card or Plug & Charge.
You can check if the request has been Authorized or Not Authorized by the EMP.
Authorization requests sent via app or helpdesk
Tabs “AuthorizeRemoteStart” and “AuthorizeRemoteStop” display every authorization that has been initialised remotely (such as an authorization by EMP app).
Display the Charge Detail Records (CDR) that have been sent to the HBS after every charging session.
Consumption in kWh, Session Start and Session End are details that can be found here. Also it’s possible to check if the CDR was succesfully stored in HBS and forwarded to the EMP.
Export the CDRs as CSV or Excel format. Please note that there is a 1000 row limit for exports. You may need to filter it into smaller chunks (e.g. by week). You will find more information here.
CDRs requested via API
"GetChargeDetailRecord" request allows EMPs to download CDRs that have been sent to Hubject by partner CPOs. These requests are shown in this tab.
Offline EMPs can upload the authentication data to the HBS sending a PushAuthenticationData request. These transactions will be displayed in this view.
Click on filters to display specific requests. For example, you can use ActionType filter to display only fullLoad requests.
"Number of Records" field indicates the amount of authentication data records uploaded to the HBS.
Check the status to know if the data was uploaded correctly. You will find the codes description in our OICP documentation.
EVSE Data & Status
This section display the static information and the status of the charging stations. The CPO upload this information while an EMP partner can receive it from the HBS.
As CPO you can display EvseDataPush and EvseStatusPush requests. This view will allow you to check if the requests were sent succesfully from your backend.
If an EvseID that doesn’t belong to a sub-partner or the status of a charging station not included in your EvseData is sent in the requests, an error will be displayed here.
EVSE Data is also known as POI Data. If you want to know more about how you can improve the quality of your EVSE Data click here.
As EMP you can display EvseDataPull and EvseStatusPull requests. The status of these requests can be also checked in this section.
Download the payloads by clicking on the download icons in the last column of the table.
Transactions to request a reservation of a charging point and the end of a reservation are displayed here.
See more information about in our OICP documentation.
Every charging session is displayed in “Sessions”. Detailed information is shown to track errors or test functionality.
Use the tab dedicated to each type of request (e.g. AuthorizeRemoteStart) to check the details of a charging session instead of this view.