Information on EIC - Energy Identification Code

1
2
3
4
A Common Identification System
For
The Energy Industry
5
6
7
The
Energy Identification Coding Scheme
EIC
8
Reference Manual
9
10
Version: 4
Release: 0
2006-05-15 EIC Reference Version 4 Release 0 Page:1 /32

11
REVISION HISTORY
Version Release Date Paragraphs Comments
1 0 2001-05-24 Initial publication
2 0 2002-06-20 Correction to remove the use of the
asterisk character (*) in the code
since the code could be used in a
filename.
2 1 2002-11-10 General revision to incorporate all
the facilities and requirements of an
issuing office.
2 2 2003-02-05 Suppress the use of the asterisk in
section 3.3 and clarify the use of
the hyphen character in Annex 1.
2 3 2003-06-30 General
Annex 4
3 0 2004-09-30 Section 1
Section 3
CORRECT PAGE
NUMBERING
Add correct XML document structure
for the transmission of EIC
codes in addition to providing more
descriptive information about the
information to be supplied to
ETSO.
UPDATE OF THE
INTRODUCTION SECTION
TO BEING IT INTO LINE
WITH THE CURRENT
SITUATION TO DEFINE THE
NEW TYPE CODE “W” FOR
UNITS
Annex 4
Annex 5
Annex 6
Specify more responsibilities for
the central issuing offices and additional
responsibilities for the local
issuing offices.
Modify the DTD to incorporate the
EIC responsible party and to provide
explanatory text
Explanation of the use of the EIC
parent
Explanation of the use of the EIC
responsible party
2006-05-15 EIC Reference Version 4 Release 0 Page:2 /32

Version Release Date Paragraphs Comments
4 0 2006-01-27 General revamping of the document
to incorporate the extension
of the coding system to the Energy
market, to permit the code to be
used locally as well as nationally
and to detail the use of the balance
group object type
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Copyright notice:
Copyright © ETSO 2002-2006. All Rights Reserved.
This document and translations of it may be copied and furnished to others, and
derivative works that comment on or otherwise explain it or assist in its implementation
may be prepared, copied, published and distributed, in whole or in part,
without restriction of any kind, provided that the above copyright notice and this
paragraph are included on all such copies and derivative works. However, this
document itself must not be modified in any way, by, for example, removing the
copyright notice or references to ETSO. It may be changed, however, as required
to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by
ETSO or its successors.
This document and the information contained herein is provided on an "as is" basis.
ETSO DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY
IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
www.edi.etso-net.org
2006-05-15 EIC Reference Version 4 Release 0 Page:3 /32

32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
Contents
1 INTRODUCTION............................................................................................ 6
2 GENERAL REQUIREMENTS FOR THE ADMINISTRATION OF EIC..... 7
3 ENERGY IDENTIFICATION CODING SCHEME - EIC ............................. 7
3.1 INTRODUCTION.................................................................................................. 7
3.2 ADMINISTRATIVE ORGANIZATION..................................................................... 8
3.3 THE ENERGY IDENTIFICATION CODE - EIC ....................................................... 8
3.3.1 Permitted characters ................................................................................ 8
3.3.2 Overall structure ...................................................................................... 8
3.3.3 Object types .............................................................................................. 9
3.4 EIC CODE VALIDATION.................................................................................... 10
3.5 ISSUING OFFICES.............................................................................................. 10
3.5.1 Central Issuing Office............................................................................. 10
3.5.2 Local Issuing Offices .............................................................................. 11
3.6 THE EIC CODE FOR NATIONAL AND INTERNATIONAL USE................................ 13
3.7 DEACTIVATION OF INTERNATIONAL EIC CODES.............................................. 13
3.8 LOCAL ISSUING OFFICE CREATION ................................................................... 14
3.9 SERVICES......................................................................................................... 14
3.10 MAINTENANCE AND ORGANISATION................................................................ 15
3.11 REGISTRATION COSTS ..................................................................................... 15
4 ETSO STEERING COMMITTEE POSITION.............................................. 17
ANNEX 1: THE EIC CHECK CHARACTER ALGORITHM ............................... 19
ANNEX 2: XML MESSAGE STRUCTURE FOR EIC CODE ALLOCATIONS. 23
ANNEX 2.1 DTD STRUCTURE ................................................................................ 23
ANNEX 2.2 THE MODEL OF THE APPROVED EIC IDENTIFICATION FILE .................. 24
ANNEX 2.3 ELEMENT DEFINITIONS ........................................................................ 25
ANNEX 2.4 BASIC GROUND RULES ......................................................................... 27
ANNEX 2.5 HOW TO VERIFY AN EIC CODE REQUEST. ............................................ 27
ANNEX 2.6 ETSO OUTPUT TO THE ISSUING OFFICES.............................................. 27
ANNEX 2.7 COMPLETING EIC INFORMATION FOR TRANSMISSION TO ETSO.......... 29
ANNEX 2.8 ETSO WEBSITE CONTENT.................................................................... 30
ANNEX 3 USE OF THE EIC PARENT.............................................................. 31
ANNEX 4 USE OF THE EIC RESPONSIBLE PARTY..................................... 32
2006-05-15 EIC Reference Version 4 Release 0 Page:4 /32

65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
Note concerning wording used in this document:
The force of the following words is modified by the requirement level of the document
in which they are used.
· MUST: This word, or the terms “REQUIRED” or “SHALL”, means that the
definition is an absolute requirement of the specification.
· MUST NOT: This phrase, or the phrase “SHALL NOT”, means that the definition
is an absolute prohibition of the specification.
· SHOULD: This word, or the adjective “RECOMMENDED”, means that there
may exist valid reasons in particular circumstances to ignore a particular item,
but the full implications must be understood and carefully weighed before
choosing a different course.
· SHOULD NOT: This phrase, or the phrase “NOT RECOMMENDED”, means
that there may exist valid reasons in particular circumstances when the particular
behaviour is acceptable or even useful, but the full implications should be understood
and the case carefully weighed before implementing any behaviour described
with this label.
· MAY: This word, or the adjective "OPTIONAL", mean that an item is truly optional.
One vendor may choose to include the item because a particular marketplace
requires it or because the vendor feels that it enhances the product while
another vendor may omit the same item. An implementation which does not include
a particular option MUST be prepared to interoperate with another implementation
which does include the option, though perhaps with reduced functionality.
In the same vein an implementation which does include a particular option
MUST be prepared to interoperate with another implementation which does not
include the option (except, of course, for the feature the option provides.)
2006-05-15 EIC Reference Version 4 Release 0 Page:5 /32

90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
1 Introduction
Electronic Data Interchange in the European Energy Market requires a common identification
scheme to be effective. Market Agents (Traders, producers, and qualified consumers)
have the possibility to act in different market areas and System Operators have
to exchange information amongst themselves concerning the market players in question.
In order to do this a reliable identification scheme is a necessity.
The primary but not exhaustive list of objects that need to be identified are:
A. Parties: System operators, traders, producers, big consumers, power exchanges,
grid operators, suppliers, agents, service providers, etc.
B. Areas: Local grids where measurement points are situated, market balance areas
consisting of a number of local grids control areas, balance groups, etc.
C. Measurement Points: Metering points, production units, consumers, cross border
connections, settlement or accounting points, Connection points, etc.
D. Resource objects: Resources that can either produce or consume energy.
The ETSO Task Force 14 "Electronic Data Interchange " investigated the use of identification
schemes in its member countries. The results of this study showed that most
countries were using national identification schemes that were unsuitable for use at a
European level.
The task force envisaged the possibility of making one of the national identification
schemes a European standard. However, the candidate schemes were deemed unsuitable
for widespread use as they did not provide the necessary guarantees to be a robust coding
scheme.
The task force also looked into the use of several international identification schemes
that could eventually be used for the energy market. The schemes in question, however,
contained specific constraints for their use that prevented their adoption at a European
level
In conclusion, TF14 considered that it would be better to establish a new energy identification
scheme that provides all the services that are required for the energy market.
TF14 therefore introduced an identification scheme, which provides an easy migration
path for existing national schemes, in a format that makes it suitable for general electronic
data interchange. This new Energy Identification Coding scheme - EIC - is described
in the rest of this paper.
The ETSO Steering Committee approved its initial implementation at their meeting on
14 May 2002.
2006-05-15 EIC Reference Version 4 Release 0 Page:6 /32

124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
2 General requirements for the administration of EIC
A successful identification scheme requires that the allocated codes are stable over time.
This implies that the significance of a code should always remain constant.
To achieve this the following principles shall be implemented:
1. Issued codes shall be globally unique. The basic principle is that only one code is
allocated per object identified (organisation, area, measurement point, resource
object, etc.).
2. Once a code is allocated to identify an entity, it shall stay unchanged until the organisation’s
status changes. Consequently, if the organisation merely changes its
name, its code shall not be modified.
3. Areas used in inter System Operator data interchange shall have codes allocated
centrally.
An identification scheme also requires a certain number of services. These services
should include, at least:
1. The correct allocation of codes
2. The management of the code lists (inquiry, deactivation and modification)
3. <strong>Information</strong> on the significance of codes
4. Contact details about the designated organisations
5. Communication parameters (e-mail, http, network address, etc…)
3 Energy Identification Coding scheme - EIC
3.1 Introduction
ETSO, through ETSO TF 14, has defined the coding system and the administrative organization
to manage and maintain them.
The coding scheme will be under the responsibility of ETSO. However, the overall assignment
and management of the codes will be carried out by Issuing Offices (ETSO
authorised organisations or associations) in compliance with an agreed basic set of
rules.
Such organisations will typically be national energy organisations or European energy
associations. On reception of the ETSO authorisation, they may assign codes to their
members and to other bodies or entities on a previously agreed basis.
The most important use of EIC is for party coding. With different market rules and practices
in the national markets today's use of EIC will vary slightly from country to country.
However the objective of EIC is to end up with a harmonised way of identifying
parties for data interchange in the Internal Energy Market. This process is carried out at
meetings with all the local issuing offices.
The ETSO vision for party identification is that an international party uses the same EIC
code in all markets for its wholesale activities. This is especially important for his en-
2006-05-15 EIC Reference Version 4 Release 0 Page:7 /32

161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
ergy flows between the different national areas, as this will facilitate the validation of
these flows between the System Operators. Validation of cross border flows is a prerequisite
for the security of supply for the European energy networks.
For retail market data interchange a more detailed approach will generally be needed
and national subsidiaries of the international companies will need to be identified. In
this way an international group may end up with many party codes for its activities in
different parts of the market.
3.2 Administrative Organization
The administrative organization is composed of a two level structure:
Level 1: Central Issuing Office
The Central Issuing Office is under the direct responsibility of ETSO. Task
Force 14, on behalf of ETSO, will perform the functions of the Central Issuing
Office as long as the group remains in existence. When Task Force 14 terminates,
a common neutral body will be set up to continue these functions.
Level 2: Local Issuing Offices
The Local Issuing Offices act as agents of Central Issuing Office. Each country
or European association, which directly or indirectly is a part of the European internal
market for energy, can have a Local Issuing Office (EIC issuing office).
The Local Issuing Office can either be a separate legal body or a part of an existing
body. It must have an official entity with an active role in the energy market,
i.e. being a TSO, Market Operator or Association of energy related companies.
In order to qualify as a Local Issuing Office the applicant must apply to the
ETSO Secretary General.
3.3 The Energy Identification Code - EIC
The Energy Identification Coding scheme is based on fixed length alphanumeric codes.
The codes should be non-significant over and above the identification of the issuing
office and the nature of the object identified. The coding system provides additional
information describing the object in question.
3.3.1 Permitted characters
Permitted characters are numbers (0 to 9), capital letters (A to Z, English alphabet) and
the sign minus (-). To avoid confusion, the check character shall use numbers (0 to 9) or
the capital letters (A to Z).
3.3.2 Overall structure
The structure of the EIC may be broken down as follows:
A 2-character number identifying the issuing office assigned by ETSO
One Character identifying the object type that the code represents
2006-05-15 EIC Reference Version 4 Release 0 Page:8 /32

197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
12 digits, uppercase characters or minus signs allocated by the issuing office
in compliance with general and local rules to identify the object in question
(party, measurement point, area, etc.).
1 check character based on the 15 previous characters used to ensure the validity
of the code.
3.3.3 Object types
Currently four types of object have been identified in the coding scheme:
• Party (EIC object type X):
A party is only allowed to have one EIC code for a given entity within the European
internal energy market.
Each party should have the possibility to chose the code to their liking, be it characters
or numbers in respect to the coding rules.
A party will obtain a party code at one of the local issuing offices. However having
an EIC code is not sufficient to allow a party to participate in an energy market as
this is dependent on local market rules.
For international trading groups it is recommended to use a single unique EIC code
for identifying the party for cross border flows in all countries.
Examples: 10XDE-RWENET---W for the German TSO RWE and
10X1001A1001A361 for the Dutch TSO Tennet.
• Area (EIC object type Y) :
All areas involved in inter System Operator data interchange must be identified on a
central basis. In some countries metering points for a party are grouped together for
imbalance settlement and other purposes. These groups are called balance groups.
Such Balance groups are to be identified by an EIC Y-code.
Examples: 10YDK-BALANCE-WM for the western balance area in Denmark.
• Measurement point (EIC object type Z). A measurement point defines two
basic categories of measurement points:
1. Metering points: A point where energy products are measured.
2. Accounting or connection points : A point where the calculation
of the energy produced or consumed is carried out. It may
be a physical point situated at an extremity of a line; a virtual
point that is an agreed position between two connections or an
aggregation of physical or virtual points.
Example: 20Z123456789012E (national measurement point code)
• Resource object (EIC object type W):
2006-05-15 EIC Reference Version 4 Release 0 Page:9 /32

232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
Resource objects (resources that can either produce or consume energy) , such as
production units, industrial consumers, pumping stations, capacitor banks, synchronous
compensators, FACT devices, etc. need to be defined within the energy market.
Objects such as these will be identified with the W-code.
Other types of EIC code may be added with the agreement of ETSO.
3.4 EIC code validation
The identification code may be simply validated by applying a weighting to each of the
16 characters going from a weighting of 16 for the leftmost character to 1 for the rightmost
character (which is in itself the check character) and applying the formula
R= MOD(“weighted value”, 37) where to be valid R must equal 0.
(See Annex 1 for details)
3.5 Issuing offices
3.5.1 Central Issuing Office
The Central Issuing Office shall be responsible for providing the 2-character EIC code
that identifies the Local Issuing Offices.
It shall also be responsible for providing the 16-character EIC codes to any recognised
System Operator or area (used in inter-System Operator data interchange).
Areas used in inter-system Operator data interchange shall be named directly by the
Central Issuing Office.
Only System Operators, Market Operators and Imbalance Settlement Responsible organisations
may request new area EIC identification codes.
ETSO will maintain a list of all issuing offices and allocated EIC codes for international
use in a centralised database.
The Central Issuing Office may occasionally allocate EIC codes for parties not having a
Local Issuing Office. In this context, as in the case where it allocates System Operator
or area EIC codes, it shall respect the requirements that have been set forth for Local
Issuing Offices.
The central issuing office shall provide minimum checks to ensure that codes proposed
by the local issuing offices are not in conflict with codes already existing in the code list
or that the format of the codes do not infringe the rules for the allocation of codes. Explicitly,
the central issuing office shall ensure:
that the “EIC code” is unique within the central database,
that the “display name” is unique within the central database,
that a central database is maintained for each EIC code type,
that the “display name” respects the naming rules and only uses the permitted
characters,
that the “last request date” is modified with each EIC code evolution,
2006-05-15 EIC Reference Version 4 Release 0 Page:10 /32

269
270
271
272
273
274
275
276
that the “function” is present,
that all mandatory fields are present,
That “EIC parent” or “responsible party” codes, if assigned, exist in the central database.
If one of these codes is made inactive, it shall ensure that all “EIC parent” or “Responsible
party” codes are replaced accordingly.
The central Registry shall contain the list of all internationally recognised EIC codes
provided by the Local Issuing Offices.
The following basic information will be provided on the website:
EIC name
Display name
EIC parent
EAN code
VAT code
The official name assigned to the EIC code. For a Party code it
shall identify the name of the party. For an Area code it shall identify
the name of the area, etc.
A short name to be used for display on screen and verbal communication.
Within each category (Party, area, measurement point,
etc.) the Display name shall be unique per EIC code type. (it
should be noted that the unique identification of object is the EIC
code, the display name merely facilitates human communication)
In case of a subsidiary or a sub-area, the EIC code of the owner
The EAN code used by the party in markets using EAN instead of
EIC. This shall only be provided for EIC party codes.
The VAT code of the company. This code shall only be assigned
to EIC party codes.
277
278
279
280
281
282
283
284
285
286
287
288
289
290
Function
3.5.2 Local Issuing Offices
The functional use of the code, i.e. "Balance Responsible Party",
"International trader", "National balance group", "French retailer".
The Local Issuing Offices are authorised by ETSO to supply EIC codes to any recognised
energy organisation providing that they respect the minimum requirements set
forth in this document.
The principle behind delegating the allocation of codes to a Local Issuing Office is that
the office is more likely to know the company requesting a code. Typically, a Local
Issuing Office will be set up within a TSO, a power exchange, or an industry organisation.
A Local Issuing Office is responsible for the allocation and maintenance of the codes it
issues and it shall maintain a list of all issued codes and standard data about the object
identified by the code in its local database.
It must ensure that:
1. The allocated codes are stable over time. This implies that the significance of
a code should always remain constant,
2006-05-15 EIC Reference Version 4 Release 0 Page:11 /32

291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
For organisations: A code shall be allocated to identify an organisation
or a specific part of an organisation. Only one code may be assigned
to an entity. A code defines explicitly the entity. The entity
should be reflected in the text describing the company and it may be
indicated in the name. Consequently, if the entity merely changes its
name, its code will not be modified.
All allocated codes must respect the rules for establishing EIC codes
as described in this document.
It is the responsibility of each local issuing office to ensure that the codes under its responsibility
remain current and respect the rules laid down in this document. This means
that errors found by the central issuing office or local issuing office must be corrected.
A local issuing office must also ensure to the best of its ability that the parties given
codes will inform it of any changes in the registration.
Each local issuing office shall take all the measures possible to correct any anomaly
reported to it and shall ensure that the anomaly is rectified in the shortest possible delay.
2. The following minimum services are provided:
The verification in the central database under responsibility of the
Central Issuing Office that a code has not already been allocated for
the party in question. Only one EIC party code may be allocated to an
entity. If a code has already been allocated, the requestor of the code
shall be informed of the code in question.
The supply, to a request from an energy partner, of all the standard
details concerning a party
The supply to the central database under responsibility of the Central
Issuing Office of all allocated codes and the standard information.
This information shall be sent to the Central Issuing Office by the
local Issuing Office using either the standard XML mechanism or
the web based forms supplied to the Issuing Offices. The XML
document structure, is defined in Annex 2. The uploaded information
will be integrated into the central database once a week.
The management of the code lists (inquiry about a code, suspension
of a code and modification of company information concerning a
code). This includes ensuring that all TSOs within its area are informed
of any request for deactivation.
ETSO, or the Central Issuing Office on his behalf, will on a weekly basis publish and
maintain in its website database the information as received from the Local Issuing Offices.
It is the responsibility of each Issuing Office to ensure the correctness of the information
supplied.
2006-05-15 EIC Reference Version 4 Release 0 Page:12 /32

329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
3.5.2.1 Creation of national EIC codes
Local Issuing Offices may assign EIC codes to local entities for national purposes that
generally do not have an international interest. In this case the EIC code assigned shall
not be submitted to the Central Issuing Office for publication in the central database. It
must be remembered that a party that only participates in the local market may at some
later date wish to participate in the international market. All the Local Issuing Office
has to do in such a case is to transmit the EIC code information to the Central Issuing
Office.
Display names in the Central database are required to be unique. This uniqueness check
also applies to locally assigned codes. In order to ensure that a locally assigned EIC
code has a display name that is guaranteed to be unique it is recommended to incorporate
the two character international country code of the country in question in the display
name. For example a local EIC code assigned in Switzerland could have a display
name such as “CH-NAME”.
When a locally assigned EIC code is given international status, the Local Issuing Office
may modify the Display name accordingly but it must ensure that the Display name is
unique within the Central database.
3.6 The EIC code for national and international use
The EIC in its basic construction is universally unique whether the code is used nationally
or internationally. However, there are some constraints put on codes that are identified
for use internationally in order to ensure the harmonious use of the code throughout
Europe. These constraints are identified in the paragraphs dealing with the Local Issuing
Office responsibilities and organisation.
International codes must be uploaded to the Central database to enable all Issuing Offices
and market participants to benefit of their use.
In order to obtain a code a market participant must contact a Local Issuing Office to
request the allocation of an EIC for his use within the market. At this time he should
also indicate whether the code is intended for national use, for international use or for
use both nationally and internationally. The Local Issuing Office, after validating the
market participants request then allocates the EIC and informs the market participant of
its allocation. If the code is intended for use internationally, the Local Issuing Office
then provides the information about the code to the Central Issuing Office for publication
for international use.
3.7 Deactivation of international EIC codes
Before an international EIC code may be deactivated, the Issuing Office in question
shall send a deactivation request to the Central Issuing Office. The Central Issuing Office
then informs the Local Issuing Offices of the deactivation requests.
The request remains open for a period of two months prior to its deactivation.
If, during that time a request is made to the Central Issuing Office for it not to be deactivated,
all Local Issuing Offices will be informed that the request in question is no
longer valid and that the code will not be deactivated.
2006-05-15 EIC Reference Version 4 Release 0 Page:13 /32

370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
If, after the two month period, no objections have been received, the code will be deactivated
by the Central Issuing Office.
The Central Issuing Office will send a deactivation list to the local issuing offices with
each revision of the EIC code list.
An EIC code for a new entity cannot make use of a deactivated code.
3.8 Local issuing office creation
To qualify as a Local Issuing Office the applicant must issue a written and officially
signed application to the ETSO Secretary General containing:
The name and address of the legal body requesting Issuing Office status;
<strong>Information</strong> indicating that the legal body has a position in the marketplace that
makes it acceptable for it to issue EIC codes.
The ETSO Secretary General will supply the successful applicant by post with a certificate
acknowledging his Local Issuing Office status. The present issuing office application
form can be found in section 6.
3.9 Services
All authorised issuing offices will have to provide the services approved by ETSO (refer
to chapter 2).
For the initial implementation a web page shall be developed to provide the necessary
services including the download of the list of EIC assigned codes in compliance with
the ETSO XML schema. At a later stage more advanced data interchange can be introduced
to automate the transmission of general information and of communications parameters
to the participating parties.
The services must also include information about the unique EAN code for the parties
that are active in TSO areas using the EAN coding scheme.
Each Local Issuing Office might also require that their participants send a copy of their
application request in the appropriate format.
Each Local Issuing Office shall send all codes to be used internationally to the Central
Issuing Office containing the standard information about the objects and their allocated
EIC codes. This information shall be sent to the Central Issuing Office by the local Issuing
Office using either the standard XML message or the web based form on the supplied
to the Issuing Offices.
(Annex 2 describes the DTD of the XML message structure for EIC Code allocation)
All local issuing offices shall send update for all modifications to object information
provided by the parties.
2006-05-15 EIC Reference Version 4 Release 0 Page:14 /32

404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
3.10 Maintenance and organisation
Any coding scheme needs a body to maintain it to ensure that it satisfies market requirements.
For the moment ETSO Task Force 14 will maintain the code’s structural
definition as long as the group remains in existence.
ETSO will provide a central database containing all the approved EIC codes provided
by the issuing offices. All new information provided by the issuing offices will be integrated
into the database within the week after reception.
All issuing offices will be invited to participate in the maintenance process.
Any proposed changes to the coding scheme must have the consensus of all participating
bodies.
When Task Force 14 terminates a common neutral body will be set up to continue this
maintenance.
3.11 Registration Costs
ETSO Task force 14 (office number 10) will issue the needed common codes at no cost.
Local issuing offices may install a cost based fee depending on their market requirements.
This fee shall not exceed the local EAN fee for similar codes.
2006-05-15 EIC Reference Version 4 Release 0 Page:15 /32

420
PAGE INTENTIONALY LEFT BLANK
2006-05-15 EIC Reference Version 4 Release 0 Page:16 /32

421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
4 ETSO Steering Committee position
The ETSO Steering committee recommends the use of EIC and EAN schemes and published
the following recommendation in this respect on the 24 th of May 2002 1 :
"To facilitate electronic data interchange in the open Internal Electricity Market the
ETSO Steering Committee recommends the use of the EAN identification code or the
ETSO Identification Code – EIC – for parties and balance areas in countries which
need a new coding scheme.
The EIC is specified by Task Force 14 "Electronic Data Interchange between Market
Participants".
Task force 14 together with the ETSO Secretary General will assist countries in the
contractual implementation of registration offices for the EIC. ETSO strongly recommends
that any issuing fee is based only on the actual costs.
Task Force 14 will provide the initial registration agency codes for all current ETSO
members and will provide the EIC codes for balance areas and a list of all permitted
coding schemes to be used within the ETSO Scheduling System (ESS).
As long as Task Force 14 is active they will maintain the definition of the EIC. After
that ETSO will ensure that a common neutral body is set up to maintain the code structure
according to user needs.
The actual coding scheme used for data interchange between TSOs will have to be
agreed on a bilateral basis."
Within the national context it is suggested that an existing identification scheme as well
as the new coding scheme (EIC or EAN) may be used during a transition period. It is
recommended that this transition period be as short as is reasonably possible in order to
avoid the extended use of multiple identification schemes.
It should be noted that the ETSO –electronic business standards (ESS, ESP, ERRP,
ECAN, etc..), which is also developed by Task Force 14, will be able to cater for multiple
coding schemes, i.e. the EIC, the EAN or national schemes. All TSO IT systems
should be able to cater for these different coding schemes.
1 Since the Steering Committee of 2002 it has been agreed to evolve the name to Energy Identification
Code.
2006-05-15 EIC Reference Version 4 Release 0 Page:17 /32

449
PAGE INTENTIONALY LEFT BLANK
2006-05-15 EIC Reference Version 4 Release 0 Page:18 /32

450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
Annex 1: The EIC Check Character algorithm
Introduction
This document outlines the algorithm for verifying the accuracy and validity of the Energy
Identification Code. The Energy Identification Code is encoded with a "Check
Character". A check character is a character added to the end of the code that validates
the authenticity of the code. A simple algorithm is applied to the other digits or letters of
the code which yields the check character. By running the algorithm, and comparing the
check character you obtain with the check character encoded in the Energy Identification
Code, it is possible to verify that the complete identification code has been correctly
read and that they make a valid combination. Possible uses for this information:
When a user has keyed in an identification code (or scanned it) and you want
to validate it before sending it out in a schedule, for example.
When issuing codes.
Calculation of the check character, General algorithm for all codes
Step 1:
The first 15 characters of the code are individualised as follows
1 1 X R W E N E T 1 2 3 4 5 -
2006-05-15 EIC Reference Version 4 Release 0 Page:19 /32

466
467
468
Step 2:
Where alphabetic characters are present, they are replaced by a numeric value as extracted
from the following table:
CODE 0 1 2 3 4 5 6 7 8 9
VALUE 0 1 2 3 4 5 6 7 8 9
469
CODE A B C D E F G H I J K L M N O P Q R
VALUE 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
470
CODE S T U V W X Y Z -
VALUE 28 29 30 31 32 33 34 35 36
471
as follows :
1 1 33 27 32 14 23 14 29 1 2 3 4 5 36
472
473
474
Step 3:
Then, the positions are again weighted, beginning with the greatest value to the left and
ending with a one at the far right.
1 1 33 27 32 14 23 14 29 1 2 3 4 5 36
475
16 15 14 13 12 11 10 9 8 7 6 5 4 3 2
476
Step 4:
1 1 33 27 32 14 23 14 29 1 2 3 4 5 36
477
16 15 14 13 12 11 10 9 8 7 6 5 4 3 2
478
Each digit is multiplied by its position weight
16 15 462 351 384 154 230 126 232 7 12 15 16 15 72
479
Step 5:
16 15 462 351 384 154 230 126 232 7 12 15 16 15 72
480
The products are then summed to give a total value: 2107
2006-05-15 EIC Reference Version 4 Release 0 Page:20 /32

481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
Step 6:
Apply a modulo 37 (which corresponds to the total number of characters available) to
the value 2107 with the formula (36 – MOD((2107-1),37))
The result is 2 that, since it is inferior to 10, the check character for the code is the same.
Had it been superior to 9 it would have to be converted to a letter using the same
mechanism as in Step 2.Thus the code is: 11XRWENET12345-2.
If the check character generated is the “-“ character (result of the calculation
equal to 36), one of the characters in the proposed code shall be changed in order
to obtain a result which does not give a value of 36.
Strengths
Like any consecutive weighting system, this scheme detects 100% of all single digit
errors and all transposition errors. Thus the system would detect that the code
10Z317973010277Q was incorrect.
The proposed algorithm is very beneficial insofar as it enables the use of the alphabet
that significantly expands the potential limit of numbers available for use.
2006-05-15 EIC Reference Version 4 Release 0 Page:21 /32

496
PAGE INTENTIONALY LEFT BLANK
2006-05-15 EIC Reference Version 4 Release 0 Page:22 /32

497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
Annex 2: XML message structure for EIC code allocations.
Annex 2.1 DTD Structure
The structure reflects the issuing office approved code submission document for the
transmission of approved codes to the Central site.
2006-05-15 EIC Reference Version 4 Release 0 Page:23 /32

561
Annex 2.2
The Model of the approved EIC identification file
562
2006-05-15 EIC Reference Version 4 Release 0 Page:24 /32

563
Annex 2.3 Element definitions
Data Element
Size
EicCode
16 characters fixed
length
Status
EicType
LastRequestDate
EanCode
VatCode
OfficeCode
Comments
This element must have a valid check
character
1 character The following coded values are permitted:
C = Creation
U = Update (The information about a
code is to be modified. In this context the
previous XML entry is entirely replaced
by the current entry.)
D = Make inactive (The information concerning
this code is marked “inactive”. It
is not possible to reallocate the same
code).
Two codes exist for the complete file:
A = Active, the code is active and valid
I = Inactive, the code is inactive and must
not be reissued.
The one character type
of the EIC Code
A date in the format :
yyyy-mm-dd
Fixed length 13 numeric
characters
Variable length 14 alpha-numeric
characters
The EIC type may be :
W = Resource Object identification
Y = area identification
X = party identification
Z = measurement point identification
The last request date represents the date
of the addition, last modification or deletion
to the code. This date shall be modified
each time an EIC code is modified or
made inactive.
The EAN code, if present, must consist of
13 numeric characters. The EAN code
shall only be provided for EIC “X” codes.
The VAT code generally consists of the 2
character country code followed by a
variable length code of 12 alpha-numeric
characters. All blanks, or presentation
separators should be stripped from the
code. The VAT code shall only be provided
for EIC “X” codes.
2 characters The central issuing office may only assign
this code. The element shall always
be blank for Local Issuing Office trans-
2006-05-15 EIC Reference Version 4 Release 0 Page:25 /32

EicParent
EicResponsibleParty
EicName
DisplayName
AddressLine1,
AddressLine2,
AddressLine3
PostalCode
City
CountryCode
ContactPerson
Telephone
Fax
EMail
Function
16 character fixed
length
16 character fixed
length
70 characters variable
length alpha-numeric
16 character variable
length alpha-numeric
field
Each address line is
variable length 70 alpha-numeric
characters
Variable length 10 alpha-numeric
characters
Variable length 35 alpha-numeric
characters
2 uppercase alphabetic
characters
Variable length 70 alpha-numeric
characters
Variable length 35 numeric
characters
Variable length 35 numeric
characters
Variable length 70 alpha-numeric
characters
Variable length 700
alphanumeric characters
missions..
This code is a valid EIC code that must
exist in the code list. It represents the root
identification of a series of dependant
EIC codes.
This code is a valid EIC code that must
exist in the code list. It represents the
party that is responsible for a domain (for
example, a TSO is responsible for a balance
area).
The name of the party, area or measurement
point. Special language specific
characters should be avoided if standard
Latin characters can be used.
The permitted letters are the uppercase
characters “A” to “Z”, the minus sign “-“,
the plus sign “+”, the underscore sign “_”
or the numeric values “0” to “9”. Each
Display name assigned must be unique
within each EIC code category (“W”,
“X”, “Y”, “Z”, etc.)
The 2 character code shall respect ISO
3166 2 character code identifications
2006-05-15 EIC Reference Version 4 Release 0 Page:26 /32

564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
Annex 2.4 Basic ground rules
1. The character “&” should be avoided wherever possible. This character is used
as an escape character by XML processors. If such a character is required then
the string “&amp;” should be used.
2. All file extensions should be “.xml”.
3. The file character set content shall always be “UTF-8”.
4. The same Display Name is not allowed for different EIC codes of the same type.
Annex 2.5 How to verify an EIC code request.
1. Interrogate approved EIC code list with display name to verify if it already
exists.
2. Interrogate with EAN code to verify duplicate EIC code creations.
3. Interrogate with all known VAT codes to verify duplicate EIC code creations.
4. If duplicate codes then request justification for duplicate code.
5. If duplicate display names for different entities then change display
nameETSO output to the Issuing offices
After every update of the list of EIC codes ETSO will provide a file that will contain the
following:
eic-approved-codes.dtd – the DTD document structure.eic-approved-codes.xsd –
the Schema document structureeic-approved-codes.xsl – a transformation tool
enabling the list of all EIC codes in the code list.
eic-approved-codes.xml – the XML file in compliance with the DTD of all approved
EIC codeseic-approved-codes-xsd.xml – the XML file in compliance
with the Schema of all approved EIC codes
Deactivated.htm – the list of EIC codes that are planned for deactivation at a
given date.
2006-05-15 EIC Reference Version 4 Release 0 Page:27 /32

590
591
592
593
594
595
Figure 1
eic-approved-code-interrogation-v2.htm – an Interrogation tool of the XML file
enabling an interrogation by EIC, EAN, VAT, Parent EIC or EIC Responsible
Party(see
figure
2)
596
597
Figure
2006-05-15 EIC Reference Version 4 Release 0 Page:28 /32

598
2
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
Figure 3Each Issuing Office will have a complete copy of the approved EIC codes. This
includes all the information relative to the address and contact information. Such detailed
information will not be provided on the website. It is up to each Issuing Office to
correctly manage this information.
Annex 2.7 Completing EIC information for transmission to ETSO
The “Allocate an EIC code” function can be used to prepare an XML document containing
the approved EIC code information for transmission to the Central registry.
The form is as shown in figure 3. A number of zones are considered mandatory and
have been indicated by an asterisk in red. When the send key is hit, the information captured
on the form will be verified for coherence.
The following information is verified:
1. The length of each element.
2. The display name contains alphanumeric characters or a hyphen (“-“). Any
lower case letters will automatically be converted to uppercase.
3. All the mandatory elements are filled with information (EIC Name, Display
name, Address line 1, City, Postal code, Country (selected from the drop down
menu), contact name, E-Mail, Original request date, EIC code and Transaction
Type (selected from a drop down menu).
4. The check character provided for the EIC code.
5. The check character provided for the EAN code, if one is provided.
2006-05-15 EIC Reference Version 4 Release 0 Page:29 /32

620
621
622
623
624
625
626
627
628
629
630
631
632
633
Annex 2.8 ETSO website content
The ETSO website will be updated with a subset of the approved code list and will contain
the following information:
• EIC code
• EIC type
• EAN code
• VAT code
• EIC Parent
• EIC Responsible party
• Update Status
• EIC name
• Display name
• Function
• Office code
2006-05-15 EIC Reference Version 4 Release 0 Page:30 /32

634
Annex 3
Use of the EIC parent
Use of the EIC parent
99XIRE-BRP-P-1-N
99XIRE-BRP-E-A-E
99XIRE-BRP-E-B-B 99XIRE-BRP-E-C-8 99XIRE-BRP-E-D-5
99XIRE-BRP-C-A-O
99XIRE-BRP-C-B-L
99XIRE-BRP-CCA-9
99XIRE-BRP-CCB-6
EIC CODE
99XIRE-BRP-P-1-N
99XIRE-BRP-E-A-E
99XIRE-BRP-E-B-B
99XIRE-BRP-E-C-8
99XIRE-BRP-E-D-5
99XIRE-BRP-C-A-O
99XIRE-BRP-C-B-L
99XIRE-BRP-CCA-9
99XIRE-BRP-CCB-6
Display name
BRP-PARENT
BRP-CHILD-A
BRP-CHILD-B
BRP-CHILD-C
BRP-CHILD-D
BRP-GRD-CHILD-A
BRP-GRD-CHILD-B
BRP-GGD-CHILD-A
BRP-GGD-CHILD-B
EIC Parent
99XIRE-BRP-P-1-N
99XIRE-BRP-P-1-N
99XIRE-BRP-P-1-N
99XIRE-BRP-P-1-N
99XIRE-BRP-E-A-E
99XIRE-BRP-E-A-E
99XIRE-BRP-C-B-L
99XIRE-BRP-C-B-L
635
636
Figure 4
Task Force 14
2006-05-15 EIC Reference Version 4 Release 0 Page:31 /32

637
Annex 4
Use of the EIC Responsible party
Use of EIC Responsible Party
99YCB-IRELAND--P
EIC-RP-9
EIC-RP-1
EIC-RP-6
99YIR-GROUP1---4
99YIR-GROUP-2--2 99YIR-GROUP3---V 99YIR-GROUP4---Q
638
639
EIC-RP-4 EIC-RP-5
99YIR-SUB-GR11-E 99YIR-SUB-GR12-B
EIC-RP-2
EIC CODE
99YIR-GROUP1---4
99YIR-SUB-GR11-E
99YIR-SUB-GR12-B
99YIR-GROUP-2--2
99YIR-GROUP3---V
99YIR-GROUP4---Q
99YIR-SUB-GR41-2
99YIR-SUB-SGR41S
99YCB-IRELAND--P
EIC-RP-3
Display name EIC Parent
BG-IR-1
99YCB-IRELAND--P
BG-IR SUBGRP1-1 99YIR-GROUP1---4
BG-IR SUBGRP1-2 99YIR-GROUP1---4
BG-IR-2
99YCB-IRELAND--P
BG-IR-3
99YCB-IRELAND--P
BG-IR-4
99YCB-IRELAND--P
BG-IR SUBGRP4-1 99YIR-GROUP4---Q
BG-IR SUBSUB41-199YIR-SUB-GR41-2
CB-IRELAND
Figure 5
99YIR-SUB-GR41-2
EIC-RP-7
99YIR-SUB-SGR41S
EIC-RP-8
EIC Responsible party
99XIRE-EIC-RP-1A
99XIRE-EIC-RP-28
99XIRE-EIC-RP-36
99XIRE-EIC-RP-44
99XIRE-EIC-RP-52
99XIRE-EIC-RP-60
99XIRE-EIC-RP-7Z
99XIRE-EIC-RP-8X
99XIRE-EIC-RP-9V
Task Force 14
2006-05-15 EIC Reference Version 4 Release 0 Page:32 /32