What is MOBI.E?
MOBI.E is a state-owned company operating as an EGME (Electric Mobility Network Managing Entity) in Portugal. As a charging station operator in Portugal, you need to activate the MOBI.E interface.
You can find more details about MOBI.E on their official website.
Step-by-step instructions to use the MOBI.E interface
1) Enabling the interface
In the first step, the interface must be approved by us so that it appears in your be.ENERGISED instance in the "Roaming" tab. Please contact your direct contact person in this regard.
2) MOBI.E Charge Point Identifier
To use the MOBI.E interface, you need so-called "Charge Point Identifiers" for your charging stations. Contact MOBI.E in this regard, you will receive the identifiers from them.
3) Activating the interface per charging station in be.ENERGISED
In the next step, you have to activate the MOBI.E interface at each charging station located in Portugal.
To do this, go to Infrastructure/Charging stations/Station list in be.ENERGISED and go to the charging station data sheet of the respective charging station. Go to the "Roaming" tab and select "MOBI.E".
To unlock the interface, the MOBI.E identifier of the charging station must be entered. You can then activate MOBI.E.
Other comments (questions and answers)
Q: Where is the data stored?
A: The data is generally stored in be.ENERGISED.
Q: What exactly is the MOBI.E Identifier used for?
A: The MOBI.E Identifier is used for the communication with MOBI.E, so that MOBI.E can distinguish the charging stations. The identifier is included in all messages to MOBI.E so that they know on their side which charging station it is.
Q: How is the data forwarded to MOBI.E?
A: In general, there is an OCPP flow, meaning we forward data according to OCPP 1.5 SOAP. The following messages are forwarded:
- Responses to RemoteStart, RemoteStop
Q: It seems that BootNotifications are not transmitted to MOBI.E. What can be done?
A: The BootNotification that be.ENERGISED receives from a charging station is independent of the BootNotification that be.ENERGISED sends to MOBI.E. Therefore, the BootNotification that be.ENERGISED receives is not forwarded to Mobi.E.
The BootNotification that be.ENERGISED sends to MOBI.E is used to "register" the charging station with MOBI.E.
However, there is the possibility to manually trigger the BootNotifications of all relevant charging stations via the button "Send EVSE information to MOBI.E". You can find this item in be.ENERGISED under Roaming/MOBI.E/Settings. The BootNotifications will then be forwarded to MOBI.E at a certain time on that day.
Q: How can the data be exported?
A: OCPP data in general can be exported manually in be.ENERGISED.
Q: What data is returned by MOBI.E?
A: MOBI.E delivers the data to an sFTP server, be.ENERGISED imports the data from there via a job that runs regularly (once per day).
The data contains the actual EMP of the charging process and a reference to the specific session (SessionID). This data must be provided because the actual EMP cannot be included in the OCPP data.
Then the charging session is updated with the data provided by MOBI.E in be.ENERGISED.
Until then, the charging session is set as invalid in the be.ENERGISED plausibility monitor to not start the billing process until all required data is available.
Q: How fast is the data transferred from MOBI.E to be.ENERGISED?
A: This depends on MOBI.E. As soon as the required data is available, be.ENERGISED will query and update it once a day.
Q: What form of validation takes place on the part of MOBI.E?
A: We have no information regarding validation at MOBI.E. On our side, charging processes are marked as "INVALID" until the CDRs have been assigned to an actual EMP. Furthermore, all checks of the plausibility monitor can be applied.
Version: 2022-11-24 07:15:40 UTC