General principle of identifiers for e-mobility
Pursuant to Decree No. 2017-26 of 12 January 2017 on charging infrastructures for electric vehicles and the Order of 12 January 2017 specifying the provisions concerning identifiers for e-mobility service roaming, AFIREV is empowered to determine and award the identifiers for operating units with “FR” country code, as well as to define the methods of composition, allocation and management of identifiers according to the standards in use at European level.
AFIREV applies the principles of European association eMI3 in its document «eMI3 standard V1 Part 2 » which can be found here : http://emi3group.com/documents-links/ or in the “documents publiés” in the bibliothèque.
Identifiers (ID) created by every e-mobility service provider for each contract with a customer, or by every contractor owner of a charging infrastructure for every charging point and every charging station pool are based on a prefix specific to each operator or owner and issued by AFIREV. AFIREV, being the single entity able to deliver such prefix with “FR” country code, take care of their unicity so that the ID created by operators on their basis are unique in France and in Europe.
Consequently, contractor owner or operators have to request such prefix at AFIREV. They may request several IDs for the sake of the organization of their operations, each of them corresponding to a specific operational unit. For example, an operational unit for a range of customers or services of an e-mobility service provider, or a set of charging station pools for a contractor owner. Each operational unit must be operated by a single operator.
Each prefix issued for an owner or operator is called an operational unit identifier.
See the definition of terms used.
I. Format of operational unit identifiers
I. a) Format of operational unit identifier for a charging infrastructure
| String | Value | Remark |
|---|---|---|
| 2 characters for country code. | Two upper case letters «FR» | |
| Characters identifying the operational unit | 3 upper case letters or digits. | Letters A to Z or digits 0 to 9. |
Example: FRAAA
I. b) Format of operational unit identifier for a set of e-mobility service contracts
| String | Value | Remark |
|---|---|---|
| 2 characters for country code. | Two upper case letters «FR» | |
| Characters identifying the operational unit | 3 upper case letters or digits. | Letters A to Z or digits 0 to 9. |
Example: FRB12
N.B.: An operational unit identifier has no semantics so that changing the operator who uses it do not compel to change this identifier.
II. Format of identifiers
II. a) Format of identifier for a charging station pool
| String | Value | Remark |
|---|---|---|
| operational unit identifier | As defined in I. a) | |
| possible separator | « * » | ASCII code 42, optional |
| Prefix specific to the object | Upper case character «P» | P for pool |
| Characters to identify the pool, chosen by the operator | 1 to 30 upper case letters or digits, plus possible separator « * ». | Letters A to Z (except O and I) or digits 0 to 9, and possibly code ASCII 42. Warning : do not write a separator immediately after the character “P”. See also some complementary prescriptions in the applicable rules. |
Each identifier includes a total of at least seven characters, not including separators: five characters for the operational unit prefix, one character for the object type, and one character to identify the object ; or not more than thirty seven characters.
A star character (“*”) may be used at the here above indicated positions, to separate blocs when showing the identifier, for its easier visual reading and spelling. It has no IT significance and should not be included in data exchange.
Example: FR123P456AB789 or FR*123*P456*AB789
II. b) Format of identifier for a charging point
| String | Value | Remark |
|---|---|---|
| operational unit identifier | As defined in I. a) | |
| possible separator | « * » | ASCII code 42, optional |
| Prefix specific to the object | Upper case character «E» | E for EVSE (Electric Vehicle Supply Equipment) |
| Characters to identify the pool, chosen by the operator | 1 to 30 upper case letters or digits, plus possible separator « * ». | Letters A to Z (except O and I) or digits 0 to 9, and possibly code ASCII 42. Warning : do not write a separator immediately after the character “E”. See also some complementary prescriptions in the applicable rules. |
Each identifier includes a total of at least seven characters, not including separators: five characters for the operational unit prefix, one character for the object type, and one character to identify the object; or not more than thirty seven characters.
A star character (“*”) may be used at the here above indicated positions, to separate blocs when showing the identifier, for its easier visual reading and spelling. It has no IT significance and should not be included in data exchange.
Example : FR123ESAINTAVOLD01 or FR*123*ESAINT*AVOLD01
II. c) Format of identifier for an e-mobility service contract.
| String | Value | Remark |
|---|---|---|
| operational unit identifier | As defined in I. b) | |
| possible separator | « – » | ASCII code 45, optional |
| Prefix specific to the object | Upper case character «C» | C for contract |
| Characters to identify the contract, chosen by the operator | 8 upper case letters or digits. | Letters A to Z (except O and I) or digits 0 to 9. |
| possible separator | « – » | ASCII code 45, optional. Warning : do not write a separator immediately after the character “C”. |
| Control character | 1 character alpha or digit, optional but recommended to avoid reading or writing error. | Checksum error calculated |
Example : FR8AACA2B3C4D4 or FR8AACA2B3C4D4B or FR-8AA-CA2B3C4D4-B
Each identifier includes a total of fourteen characters, fifteen including control character.
In case of writing an identifier (on a card, a charging point etc.), it is advisable to avoid risk of confusion when reading and for that purpose not to use capital letters O and I.
A hyphen (“-“) may be used at the here above indicated positions, to separate blocs when showing the identifier, for its easier visual reading and spelling. It has no IT significance and should not be included in data exchange.
A description of implementation of checksum can be found at http://www.ochp.eu/id-validator/