Overview
Mobi.E is the Portuguese entity responsible for supervising the entire public charging infrastructure in Portugal. This means that any charge station that is installed in Portugal for public access, needs to be integrated in Mobi.E network. This is the regulatory framework in Portugal until 31/December/2026, which means it is possible some parties will be moving away from this model before that deadline.
Although the eMobility ecosystem of MobiE is enabled by roaming protocol OCPI 2.2, there are substantial customizations that are built on top of the protocol, in order to fulfil country specific regulations, such as:
- Location object contains additional fields.
- All CDRs from Mobi.E network (happening in a charger in Mobi.E) are generated by Mobi.E, regardless of the role of the operator, and in which back-end it runs its business.
- CDRs contain several additional fields for billing purposes - Mobi.E extensions.
- Cost structure of CPO and eMSP costs, when compared to the norm in other EU countries, is that electric energy costs from the charge sessions is borne by the eMSPs, even though the electricity contract may be in the name of the CPO operator.
For full details, check Mobi.E rules and regulations.
In this article we will delve into how does it look for an operator in GreenFlux backend, acting in Portugal Mobi.E network (charge sessions the public domain) as CPO and/or EMSP operator, which means that there are three possible scenarios for this Use Case:
- Scenario 1: Operator acts only as CPO
- Scenario 2: Operator acts only as EMSP
- Scenario 3: Operator acts as both CPO and EMSP
GreenFlux supports all of the 3 scenarios above.
Configuration & Setup
CPO Role
Hereunder represented the typical structure of the operator's charging infrastructure belonging to Mobi.E ecosystem (public chargers in Portugal) when these chargers are handled through GreenFlux backend.
- For the locations, we are representing here the Location Mobi.E ID. In GreenFlux system, the unique identifier of a location will still be its external ID, which is represented by a GUID (36 digits - Global Unique Identifier)
In order for a charge station to work within Mobi.E network, there are certain aspects that MUST be met:
- When commissioning a location and charger the first time from scratch in GreenFlux backend, the procedure for doing so must be followed and fully completed
For detailed step by step check link
Be aware there are several exceptions that must be present when commissioning a location and charge station. Please follow the procedures from
Tariff management - wholesale costs
This is currently handled by CSM. You should provide inputs to CSM to create the tariffs according to an agreed template.
CSM takes the following steps:
- Creates the tariffs and billing rules in the system, in the corresponding CPO-n (see above)
- Defines the applicable VAT rates for each tariff
- After 1 and 2, the tariffs are good to be used by the CPO.
EMSP Role
Hereunder represented the typical structure of B2C and B2B customers from EDP, in what concerns token management.
In order for a token to work within Mobi.E network, there are certain aspects that MUST be met:
- Token needs to have roaming flag enabled to work – so that token updates are shared with Mobi.E
- Driver needs to be assigned a (valid) Energy Contract. Presently, this is achieved:
- You need to define the correct energy contract to each driver in the energy contract property (e.g. CT_4KBRPNH0BFEV7LB7DMB9AB3KLE)
- Token auth-id needs to be compliant with EMA ID syntax. Check Add a Token to know how to generate it.
- Token chipId needs to be created in decimal format
Above is only represented the setup on GreenFlux domain.
Tariff Management – Retail costs:
As introduced in the overview section, retail costs in Mobi.E network is where the energy needs to be billed to the drivers. Furthermore, there are a set of additional (Portuguese regulation specific) fees that apply, which GreenFlux platform does not support. For this reason, our system does not model the real retail costs.
Instead, the platform configurations simply passthrough the wholesale costs, which means that retail will be the same as wholesale costs. It is then up to the operator who will pick these costs and compute the real retail costs on top of it, and then invoice their drivers.
Configuration checklist - Operator as EMSP only (in GreenFlux platform)
In order to have this use case running smoothly, the following elements should be verified:
- The token from this session belongs to the operator and is hosted in GreenFlux platform. Charge station may or not belong to the operator, but it is not hosted in GreenFlux platform (when both token and charge station are hosted in GreenFlux platform, then check the checklist below.
- Token needs to:
- Have chip Id in decimal format
- Auth-id needs to follow EMA ID syntax (check what this means in the Details Tab table, here)
- Token needs to have roaming flag enabled
- Driver needs to be assigned a (valid) Energy Contract.
Configuration checklist - Operator as CPO only (in GreenFlux platform)
In order to have this use case running smoothly, the following elements should be verified:
- The location and charger must belong to a CPO with Mobi.E exclusive hub
- The location MUST have been created at first with Publish = True, otherwise the Mobi.E Location ID will start with 'MOBI' prefix!! (which shouldn't be used by the operator)
- The following 2 fields must be properly filled in in the location:
- MobiE voltage
- MobiE CPE
- The location restricted access flag MUST be set to False
- The location 'External ID' field must be filled in
- The charge station ID must be the same as the location 'External ID'
- The charger's tariff prefix must start by a prefix as aligned with your CSM and the tariff must have a VAT rate assigned to it
Configuration checklist - Operator as both CPO and EMSP (in GreenFlux platform)
In order to have this use case running smoothly, both the elements in CPO and eMSP should be verified.