2

Task Force API Accounting Process ImplementationUsage of Accounting process for different topologiesV1.0, 14.09.2010

3

Use of T-, W-, Z- and local Code in the„Implementation Guide Accounting and Settlement Process”and consideration of special cases:- tie-line with three ends- coupling/ maintenance bus bar

4

1. Use of EIC-Codes and local Codes in MVD und EAR-Documents

2. Example of exchange of MVD und EAR

3. Special case: tie-lines with three ends

4. Special case : coupling/ maintenance bus bar

Content

5

1Use of EIC-Codes and local Codes in MVD und EAR-Documents

6

Process overview

The UCTE Accounting and Settlement pyramid

EAR doc

MVD doc USD doc

7

The UCTE Accounting and Settlement process: Provided documentsThe UCTE Accounting and Settlement process is based on the following documents

1. Measurement Value Document (MVD)

used for the verification of Accounting Point Relevant data on meter data level: message types SOMA and (SOVM: only for internal use, no data exchange with neighboring TS0)

Identification of Accounting Point Relevant data by official 10T-Code for tie-lines, (identification of optional additional meter data by locally assigned code or local Z-Code for meters)

2. Energy Account Report (EAR)

used for the matching of the Accounting Point data on accounting data level:message type SOAM for matching between TSO and SOVA for agreed values for exchange via Publication Framework

Identification of Accounting Point data by official 10Z-Code for accounting point

3. UCTE Settlement Report (USR)

used for the information of the UCTE Parties about the Settlement results:message types CBSR and CASR

Identification of Accounting Point data by official 10Z-Code for accounting point

8

Use of Meter Measurement data in MVD documentIdentified by an local Code for meters Identified by an EIC T Code

9

See IG Accounting: Page 19 -21, line 410 - 462,

especially line 460: use of MVD

Initial transmission Position 1 Position 2 Position 3 Position 4AccountingPointRelative data 100 101 N/A N/AMain Meter Measurement Data 100 N/A N/A 20Backup Meter Measurement Data N/A 101 N/A 105

Acknowledgement Positive ack Positive ack Negative ack Negative ack

Following transmission Position 1 Position 2 Position 3 Position 4AccountingPointRelative data 100 101 103 105Main Meter Measurement Data 100 N/A N/A 20Backup Meter Measurement Data N/A 101 N/A 105

Acknowledgement Positive ack Positive ack Positive ack Positive ack

Value 103 estimated

following SO agreement

Value 105 estimated

following SO agreement

Optional: Local Code for back-up

meter

Mandatory: 10-T-code best „composition“ of meter data

Optional: Local Code for main

meter

Local Codes in order to identify meters

10

Explanation to page 6

Accounting Point Relevant data shall (must) (mandatory) be exchanged in MVD (10T-Code). These are the meter data , that are necessary in order to calculate the Accounting point, hence accounting point relevant. If for example the meter data of both ends of a tie.line are used for the calculation of the accounting point (e.g. Accounting point is on middle of tie-line or on border point), the meter data of boths ends of the tie-line are accounting relevant data and have to be exchanged..

Each partner is sending in MVD the best “composition” (mandatory with 10-T-Code) of the available meter data from his station (Main meter, back-up meter) (see IG Accounting line ???). In normal cases the best collection of meter data is the pure main meter.

In addition to the best “composition” of meter data (mandatory with 10-T-Code) in the MVD the original data from main meter and back-up meter or tele-mesurement etc. (assigned with a local code in the MVD) can (optional) be exchanged in the MVD in order to make transparent, how the best “composition” of meter data was made.

11

Excerpt of IG Accounting

Excerpt of IG Accounting:

Line 429: In the UCTE process to establish the Accounting Point Relevant data the following rules for identification are to be used:

Line 431 · Accounting Point Relevant data are identified with an ENTSO-E assigned EIC "10T„-code.

Line 433 · Meter Measurement data are identified with a locally assigned code or an EIC "Z“-code issued by the Local Issuing Office.

12

Abstract MVD and EAR

MVD (for SOMA)

Accounting Point Relevant data are identified with an ENTSO-E assigned EIC "10T„-code. (Mandatory)

Meter Measurement data are identified with a locally assigned code or an EIC "Z„- code issued by the Local Issuing Office. (optional)

EAR (for SOAM)

Agreed Accounting Point data are identified with an ENTSO-E assigned official EIC "10Z„-code. (Mandatory)

13

2ExamplesMVD-/EAR-Document

14

Measurement Value Document (MVD)

TSO A TSO B

Accounting point: 10Z-DE-FR-000050

main, back-uplocal code

main, back-uplocal code

Main and/or back-up meter data with local Code from TSO A

Main and/or back-up meter data with local Code from TSO B

MandatoryAccounting relevant data in official T-Code „10T-DE-FR-00005A“ for tie-line

Accounting relevant data in official T-Code „10T-DE-FR-00005A“for tie-line

Tie-line10T-DE-FR-00005A

Optional

Available data Available data

SOMA in MVD

15

Energy Account Report (EAR)

TSO A TSO B

Accounting point: 10Z-DE-FR-000050

Accounting relevant data in official 10Z-Code „10Z-DE-FR-00005A“

Accounting relevant data in official 10Z-Code „10Z-DE-FR-00005A“

official 10Z-Code for accounting point

calculation of accounting point by means of the accounting relevant data from TSO A and TSO B

calculation of accounting point by means of the accounting relevant data from TSO A and TSO B

Available data after receiving SOMAfrom TSO B

SOAM in EAR

Available data after receiving SOMA from TSO A

Accounting point relevant data

Accounting point relevant data

16

Energy Account Report (EAR)

TSO A TSO B

main

National exception:

Accounting point:10Z-DE-DE-02701I

10T-DE-DE-02701S

TSO A TSO B

Back-uplocal Code

Remote reading

Accounting relevant data official 10Z-Code „10Z-DE-DE-02701I“

Accounting relevant data official 10Z-Code „10Z-DE-DE-02701I“

17

3Special case:Tie-line with 3 ends

18

Tie-line with 3 ends (1)(Sum of accounting point)

TSO A TSO B

Local CodeMeter C

10T-DE-DE-04710H

Local CodeMeter D

Accounting point 1

Accounting point 2

MVD:

the accounting relevant data is sum of meter C and D with official 10T-Code „10T-DE-DE-04710H“

optional meter data of meter C with local code optional meter data of meter D with local code

EAR: Accounting data is sum of meter C and D with official 10Z-Code „10Z-DE-DE-047107“

Note: only possible if both accounting point are at one TSO

19

Tie-line with 3 ends (2) (split into two lines)

TSO A TSO B

Local CodeMeter C

Line 1: 10T-DE-DE-04710H

Local CodeMeter DMVD:

accounting relevant data of point 1 with official 10T-Code „10T-DE-DE-04710H“ accounting relevant data of point 2 with offical 10T-Code „10T-DE-DE-04711F“

accounting data with official 10Z-Code „10Z-DE-DE-047107“ accounting data with offical 10Z-Code „10Z-DE-DE-047115“

Line 2: 10T-DE-DE-04711F

EAR:

Accounting point 1

Accounting point 2

Note: this is possible , if accounting point 1 is at TSO B and accounting

point 2 is at TSO C(!).

20

4Special case:Coupling / maintenance bus bar

21

TSO A TSO B10T-DE-DE-047092

SS1SS2

US

ZZ

z.B. „100“

„0“

„100“

Donau-WestCoupling

Accounting point

Coupling Donau-West

Import Export Import Export

0 0 0 200

0 100 0 0

0 0 0 200

Metering

Donau-West

Coupling/ maintenance bus bar (1)

22

Coupling/ maintenance bus bar (2)

TSO A TSO B

Accounting point

Coupling Donau-West

Import Export import Export

0 0 0 200

0 100 0 0

0 0 0 200

Donau-West

Import Export

0 200

0 100

0 200

Metering Accounting

10T-DE-DE-047092

Donau-West

Optional exchange of coupling data

in MVD with local Code

Accounting point relevant data in MVD with 10T Code.