Charge Station Deployment State – EV Portal

The term ''state'' is used in the EV Portal to classify what deployment stage a charger is in. We classify these in three ways:

Stock: The charge station is in stock but not yet in the field (this charger could be at a warehouse).

Production: This charger is active and deployed in the field.

Deprecated: This charger is no longer in use.

Data exchange towards roaming (e.g. OCPI) and Charge Assist app/API, if applicable

State is set to 'Stock':

💡

Common Use Case is when CPOs want to test a couple of scenarios (e.g. non-roaming and roaming session) while the charger is still in warehouse, prior to transporting it to the field for installation

No data (location, EVSE, CDRs) is shared with roaming partners.

But CDRs are still processed, in the sense that they are mapped in GreenFlux platform and allowed even with roaming cards

State is set to 'Production':

the locations, charge stations and EVSE data is shared with roaming partners with actual status (available, charging).

CDR's are also shared with roaming partners.

State is set to 'Deprecated':

💡

This is used to flag that a charger is no longer installed and reached end of life.

The EVSE's are shared with roaming partners with the status 'Removed', which means those parties should no longer display these EVSEs in their apps.

CDRs are no longer shared with roaming partners, but

sessions are still allowed and CDRs are still processed in the system.

⚠️

When the state is set to either Stock or Deprecated state, since we do not share the CDRs with roaming partners, it is plausible that the eMSP will not accept to pay for a CDR they are not aware of. For this reason, and on the scope of our GreenFlux managed roaming service, we won't be crediting the CPOs for these sessions, since we are not reselling it to the eMSPs (we don't share the CDR with them). CPOs should ensure the correct states are associated with its infrastructure.

Checklist to share charging information with app and/or roaming partners

Let’s divide this in 2 use cases:

Visibility towards roaming users (drivers from eMSPs):

The suitable roaming configurations must be in place → this is handled by GFX staff (e.g. CSM) in order to ensure that your charger’s CPO is configured to the adequate roaming channels

The Location is set to Publish = True; CPO can update this as neeeded through EV Portal* or platform API

The charger’s state = Production; CPO can update this as needed through EV Portal* or platform API.

ℹ️

*Permission Levels required: only EV Portal users with permissions to update or create chargers will be able to edit/create these fields

⛔

INTERNAL to GFX only: For further and more in depth details on the working principles of this feature: Additional technical details on sharing CDR, related with Charge Station State