P2 Policy 2: Scheduling and Accounting [C]

Transcription

1 P2 Policy 2: Scheduling and Accounting [C] Chapters A. Scheduling B. Online Observation C. Accounting and settlement of UNINTENTIONAL DEVIATIONS Introduction To operate a large power system like the one of UCTE and to create the suitable conditions for commercial electricity trade it is necessary to schedule in advance the power to be exchanged at the interconnection borders between the system operators. During daily operation, the schedules are followed by means of the LOAD-FREQUENCY CONTROL installed in each CONTROL AREA / CONTROL BLOCK. Notwithstanding LOAD- FREQUENCY CONTROL, UNINTENTIONAL DEVIATIONS invariably occur in energy exchanges. For this reason, it is necessary to co-ordinate the SCHEDULE nomination between the system operators, to observe in real-time UNINTENTIONAL DEVIATIONS and to co-ordinate ACCOUNTING and computation of the COMPENSATION PROGRAMS to balance UNINTENTIONAL DEVIATIONS. Note: All terms that are formatted in CAPITILISED letters can be found in the glossary of terms. This document and other chapters of the UCTE Operation Handbook as well as excerpts from it may not be published, redistributed or modified in any technical means or used for any other purpose outside of UCTE without written permission in advance.

2 A. Scheduling of Power Exchange P2 2 [UCTE Operation Handbook Appendix 1 Chapter A: Scheduling of Power Exchange, 2009] Introduction Due to ongoing market liberalisation throughout Europe the commercial cross border electricity trading of market parties gets more important than it was years ago. To meet the following demands it is necessary to co-ordinate and standardize the process of scheduling between system operators. This not only supports but even enhances the commercial cross border exchange of electricity as desired by the European Community. Within this scope the UCTE Operational Handbook Policy 2 Chapter A Scheduling of Power Exchange describes in a general approach how to run this process within the complete UCTE hierarchy (see Appendix, Figure 2). This document describes the scheduling process only for normal operational conditions for emergency operation see UCTE OH Pol.5 Chapter A G2. In the Implementation Guide for the ESS (ETSO Scheduling System) in the UCTE processes the receiver of schedules from market parties is identified as the TRANSMISSION SYSTEM OPERATOR. As in most cases this role is carried out by the CONTROL AREA (System) OPERATORS, this version of the Policy 2 does not distinguish between these two roles. Definitions A-D1. The nomination process of Market Parties to related CONTROL AREAS. Market Parties are responsible for the transmission of their cross border schedule nominations to the responsible CONTROL AREA Operator considering the local market rules and special requirements valid for a certain border (e.g. regarding MTFS). A-D2. Matching. Matching is the comparison of corresponding values of an EXCHANGE PROGRAM dedicated to the same border. A successful matching must have for a given direction and for all time intervals the same value for the same time interval. Mismatch is the result of a matching process where the value and/or the direction is not the same on both sides of the border. A-D3. Exchange program. An EXCHANGE PROGRAM generally means a set of values transmitted horizontally to a counterpart or vertically to an upper level within the UCTE to enable cross border matching. Depending on the UCTE Pyramid level of exchange or transmission the EXCHANGE PROGRAM can have a different quality and therefore a different naming e.g. CAS, CAX, CBS, CCT (see P2-A-D4 to D7). A-D4. CONTROL AREA SCHEDULE (CAS). The exchanged data for matching purposes

3 P2 3 between CONTROL AREAS is the Control Area Schedule documenting the cross border exchange per registered market party nominating schedules for a defined process (Day Ahead, Intra Day etc.) and border. This data set contains as much detail as possible considering the cross border nominations of parties. The contents must be bilaterally agreed and enable an effective and successful matching. (see P2-A-S5.2) The CAS is an exchange between two CONTROL AREAS. A-D5. CONTROL AREA EXCHANGE (CAX). The exchanged data to be transmitted from the CONTROL AREA to its CONTROL BLOCK is the Control Area Exchange and enables the matching between CONTROL BLOCKS. The CAX is made up of the matched values of the CAS but must contain only the aggregated and netted values of all nominations per Control Area border and therefore states the total bilateral exchange per border. If bilaterally agreed between CONTROL AREA and CONTROL BLOCK the CAX may contain not netted values. If a CONTROL AREA has several borders the CAX contains the values related to each border. The schedule of the related CONTROL AREA for the UCTE compensation of UNINTENTIONAL DEVIATION is included. A-D6. CONTROL BLOCK SCHEDULE - bilateral (CBSb). On a bilateral base the CONTROL BLOCK SCHEDULE CBSb is exchanged and used for the matching between CONTROL BLOCKS. It is assembled out of the aggregated values (CAX quality) of the affected CONTROL AREAS for every time interval for the common CONTROL BLOCK border. CONTROL BLOCK SCHEDULE - multilateral (CBSm). On a multilateral base the CBSm is transmitted from the CONTROL BLOCK to the CO-ORDINATION CENTRE and enables the matching between the CO-ORDINATION CENTRES. In this case it is assembled out of the aggregated and matched values (CAX quality) of all affected CONTROL AREAS at all CONTROL BLOCK borders. The schedule of the related CONTROL BLOCK for the UCTE compensation of UNINTENTIONAL DEVIATION is included in the CBSm message.. A-D7. CO-ORDINATION CENTRE Total Exchange (CCT). The exchanged data for matching purposes between CO-ORDINATION CENTRES is the CO-ORDINATION CENTRE Total Exchange. The CCT is assembled out of the values of the related multilateral CBSm. It contains the EXCHANGE PROGRAMS between CONTROL AREAS located at the CC-border and the COMPENSATION PROGRAM for UNINTENTIONAL DEVIATIONS of the CO-ORDINATION CENTRE.

4 P2 4 Co-ordination Centre (CC) Control Block (CB) UCTE-South UCTE-North CB N CC S CC N CBSm CBSm CBSm CBSb CBN N CAX CAX CAX CAX CCT Co-ordination Centre (CC) CBSb Control Block (CB) CBN N Scope of UCTE OH P2 Control Area (CA) CA CAS CA CAS CAS CA CA CAS Control Area (CA) MPS MPS MPS MPS Market Parties M Deal M Deal M M Deal Deal M Market Parties Legend: MPS Market Party Schedule CAX Control Area Exchange CBSm Control Block Schedule multilateral CAS CBSb CCT Control Area Schedule Control Block Schedule bilateral Control Center Total Figure 1: Information exchange for the scheduling process in the UCTE Pyramid A-D8. Gate-Closure Time (GCT). Gate Closure time is a specified time providing a deadline for submission of schedules by market parties or a deadline for submission of Exchange-Programs for UCTE matching purposes. The GCT is related to the timestamp of reception. A-D9. Cut-Off Time (COT). Cut-off time is a specified time providing a deadline, after Gate- Closure, for corrections by market parties of submitted, but mismatching schedules. If the mismatch can not be solved until Cut-Off Time, agreed rules between affected CONTROL AREAS must allow adjustments for successful matching. In some cases Cut-Off Time can be equal to Gate-Closure Time. A-D10. Time Interval. Time interval is a time resolution used in accordance to MTFS ( Multi Time Frame System ). A-D11. Definition of D, D-1, D-2, D+1. D : The day when the nominated Market Party Schedules and the exchange programs are set into force. The day D is based on CET respectively CEST D-2: two days ahead (before) D D-1 : the day ahead (before) D D+1: the day after D

5 P2 5 A-D12. Subsection A Scheduling. The subsection A Scheduling covers the following cross border schedules types: A-D12.1. Market Party Schedules (MPS) two types: A-D Commercial schedules. Transactions between registered market parties based on commercial trades or contracts. A-D TSO related schedules. Transactions towards a TSO and between TSOs to ensure a safe operation. In this context the TSOs act in some cases as Market Parties nominating commercial schedules. (For exceptions see P2-A-S20. A-D12.2. Programs for the compensation of UNINTENTIONAL DEVIATIONS. As the result of the UCTE settlement process, a program for the compensation of UNITENTIONAL DEVIATION is generated for each UCTE CONTROL AREA, CONTROL BLOCK and CO-ORDINATION CENTRE. These programs have to be matched within the scheduling process. Due to the nature of these programs they are nominated and matched in a different manner. The COMPENSATION PROGRAMS must be nominated from the CONTROL AREA to the CONTROL BLOCK and in a next step from the CONTROL BLOCK to the CO-ORDINATION CENTRE. The resulting COMPENSATION PROGRAMS must then be exchanged between the CO-ORDINATION CENTRES. As part of the Day-Ahead nomination process the CONTROL AREA COMPENSATION PROGRAMS are to be validated by the related CONTROL BLOCK OPERATOR. The CONTROL BLOCK ones are to be validated by the related CO-ORDINATION CENTRE Operator.

6 Standards P2 6 A-S1. Exchange program. The EXCHANGE PROGRAMS must match before setting them into force (see P2-A-D3). A-S2. Sum of Control and EXCHANGE PROGRAMS. The sum of the CONTROL PROGRAMS and sum of EXCHANGE PROGRAMS of all CONTROL AREAS for each time unit of a synchronous area must be at any time equal to zero. The responsibility for this is located at the CO-ORDINATION CENTRES who can ensure this by cooperation with the CONTROL BLOCKS. A-S3. Treatment of DC-links. A DC-link crossing the border of the UCTE synchronous zone between two CONTROL AREAS must be treated as a GENERATION or CONSUMPTION unit. A DC-link within the UCTE synchronous zone between two CONTROL AREAS is considered in the UCTE scheduling process like an AC interconnection. A-S4. General Agreements between UCTE System Operators who are affected by cross border scheduling. For performing a proper matching process and especially for cases of troubleshooting the UCTE bodies (Control Areas, Control Blocks and CO-ORDINATION CENTRES) have to document common agreed rules e.g. A-S4.1. A-S4.2. Agreed MTFS and number of digits Solution for mismatches (see Guidelines) A-S4.3. Troubleshooting in case of problems with data exchange and matching process. (see P2-A-G2 & P2-A-G3 & P2-A-G4) A-S5. General Agreements between neighbouring CONTROL AREAS. For automatic matching neighbouring CONTROL AREAS have to document their agreement for common rules for their border. Rules relevant for Market Parties must be published or communicated towards the parties in question. This document has to contain: A-S5.1. Identification Code used - either EIC or GS1 (former EAN) A-S5.2. Agreement on the contents and granularity of the exchanged CAS (e.g. MTFS, resolution) in order to allow a sufficient matching A-S5.3. Agreed timing for processes (e.g. exchange of programs, matching, day ahead and intra day process, Gate Closure, Cut-Off Time ) A-S5.4. Rules to solve mismatches at Cut-Off Time A-S5.5. Responsibilities (e.g. matching, CAPACITY check) Neighbouring CONTROL AREAS shall implement and run their matching process according to the Implementation Guide for the ESS (ETSO Scheduling System) in the UCTE processes.

7 P2 7 A-S6. Framework for an international Coding Scheme. For the electronic exchange of documents referring to the UCTE scheduling process a common identification of the involved UCTE bodies (Control Areas, Control Blocks and CO-ORDINATION CENTRES) on all levels in accordance with EIC (Energy Identification Code) must be used. This implies that each body within the UCTE organisation must be identified as a party (EIC-X-code) and depending on the role being played different area (EIC- Y-code) and role codes (e.g. CONTROL AREA, CONTROL BLOCK, CO- ORDINATION CENTRE). The registration or change of an EIC code must be coordinated together with the responsible UCTE and ETSO bodies. For this, every party is responsible for informing all other involved parties. The valid list of codes is published at the ETSO site. A-S7. Electronic Data Exchange. For Electronic Data Exchange for scheduling between Control Areas, Control Blocks and CO-ORDINATION CENTRES electronic highway must be used. If the Electronic Highway is disturbed, an electronic back-up must be available such as: ftp-dial in via ISDN-line or via internet. If electronic communication is generally disturbed, fax or phone can be used as last back-up. It is in the responsibility of all UCTE system operators to operate their IT processes, including the communication, in an acceptable performance. A-S8. Electronic Data Exchange Format. The Electronic Data Exchange Format for scheduling has to be agreed among the operators. A-S9. Identification of Market Parties in the nomination of MPS. For the identification of market parties, either EIC or GS1 (former EAN ) must be applied. Cross border nominations of Market Party Schedules (MPS) must be based on an Out Area / In Area and Out Party / In Party sense and identical on both sides of the border. A-S10. Time Interval. The following time intervals are allowed: t i = ¼h, ½h or 1h. The time interval for EXCHANGE PROGRAMS must be agreed bilaterally between adjacent operators in accordance to MTFS. As a general rule, two neighbouring operators have to choose the larger time frame for their bilateral EXCHANGE PROGRAMS (see P2-A-S4.1). A-S11. Value Resolution. The value of power in EXCHANGE PROGRAMS will be given as a number of MW. The number of decimal digits must be mutually agreed. (see P2- A-S4.1) A-S12. Availability. The UCTE scheduling process must be available every day from 00:00 to 24:00 CET respectively CEST. A-S13. Data exchange and matching of EXCHANGE PROGRAMS between CONTROL AREAS (Day Ahead, Intra Day, Modifications).

8 P2 8 A-S13.1. Data to be exchanged between CONTROL AREAS. The CONTROL AREA OPERATORS must assemble and exchange a Control Area Schedule. The CONTROL AREA OPERATOR must transmit his Control Area Schedule immediately but latest see timetable 1 and timetable 2. This transmission must also take place in the case of any other modifications (e.g. curtailment of Market Party Schedules etc.) (see also P2-A-S17.1. & P2- A-S22.1 & P2-A-S24) A-S13.2. Matching between CONTROL AREAS. The CONTROL AREA OPERATORS have to match and agree on the Control Area Schedule (CAS). After matching and by consideration of local market rules the Control Area operators must inform their market parties in question according to the ESS reports. This information is independent from the related CONTROL BLOCK information. A-S14. Data exchange and matching of EXCHANGE PROGRAMS between CONTROL BLOCKS (Day Ahead, Intra Day, Modifications). A-S14.1. Data transmission from CONTROL AREA to CONTROL BLOCK. After successful CAS matching the CONTROL AREA OPERATORS have to assemble and transmit a CONTROL AREA Exchange (CAX) to their corresponding CONTROL BLOCK OPERATOR. A-S14.2. Data to be exchanged between CONTROL BLOCKS. After receiving the CAX from a CONTROL AREA the CONTROL BLOCK OPERATOR must assemble and exchange a bilateral CONTROL BLOCK SCHEDULE considering the affected border. A-S14.3. Matching between CONTROL BLOCKS. The CONTROL BLOCK OPERATORS have to match and agree on the bilateral CONTROL BLOCK SCHEDULE (CBSb). A-S15. Matching of EXCHANGE PROGRAMS between CO-ORDINATION CENTRES (Day Ahead, Intra Day, Modifications). A-S15.1. Data transmission CONTROL BLOCK to CO-ORDINATION CENTRE. After successful matching of bilateral CBS the CONTROL BLOCK OPERATORS have to assemble and transmit a multilateral Control Block Schedule (CBSm) to their corresponding CO-ORDINATION CENTRE. A-S15.2. Data to be exchanged between CO-ORDINATION CENTRES. After receiving a multilateral CBS from a CONTROL BLOCK the CO-ORDINATION CENTRE Operator must assemble and exchange a CO-ORDINATION CENTRE Total Exchange (CCT) considering the common border. A-S15.3. Matching between CO-ORDINATION CENTRES. The CO-

9 P2 9 ORDINATION CENTRE Operators have to match and agree on all values contained in the CO-ORDINATION CENTRE Total Exchange (CCT). A-S16. Confirmation of matched EXCHANGE PROGRAMS. A-S16.1. CO-ORDINATION CENTRE confirmation to CONTROL BLOCKS. Immediately after successful matching the CO-ORDINATION CENTRES have to confirm the matched EXCHANGE PROGRAMS to the CONTROL BLOCK OPERATORS electronically by a confirmation report. A-S16.2. CONTROL BLOCK confirmation to CONTROL AREAS. After receipt of the CO-ORDINATION CENTRE confirmation, the confirmation of the CONTROL BLOCK matching has to be confirmed immediately by the CONTROL BLOCK OPERATORS to the CONTROL AREA OPERATORS electronically by a confirmation report. A-S17. Timing for Day-ahead matching between CONTROL AREAS (D-1 for D). A-S17.1. Transmission of EXCHANGE PROGRAM (CAS) to affected neighbouring CONTROL AREA has to be completed latest 15 min. after local market Gate Closure. A-S17.2. CONTROL AREA matching closure. The CONTROL AREA matching has to be completed by the CONTROL AREA OPERATORS till (D-1), 15min after the Cut-Off Time bilaterally agreed between concerned CONTROL AREAS. A-S18. Timing for Day-ahead matching between CONTROL BLOCKS (D-1 for D). For a sufficient processing of the UCTE scheduling and all later processes (e.g. DACF) on all levels, the following deadlines must be considered. A-S18.1. Transmission of EXCHANGE PROGRAM (CAX) from CONTROL AREA to CONTROL BLOCK. Every day (D-1) latest until 15:45 the CONTROL AREA OPERATOR has to submit the matched bilateral EXCHANGE PROGRAMS per border (CAX) concerning all of his borders to his corresponding CONTROL BLOCK OPERATOR. A-S18.2. Exchange of EXCHANGE PROGRAM (CBSb) between CONTROL BLOCKS. The CONTROL BLOCK OPERATOR has to submit the EXCHANGE PROGRAM (CBSb) to his affected neighbouring CONTROL BLOCK latest until (D-1) 16:00. A-S18.3. CONTROL BLOCK matching closure. The CONTROL BLOCK matching has to be completed by the CONTROL BLOCK OPERATOR until (D-1), 16:15.

10 P2 10 A-S19. Timing for Day-ahead CO-ORDINATION CENTRE matching (D-1 for D). A-S19.1. Transmission of EXCHANGE PROGRAM (CBSm) from CONTROL BLOCK to CO-ORDINATION CENTRE. Every day (D-1) latest until 16:30 the CONTROL BLOCK OPERATOR has to submit the bilaterally matched EXCHANGE PROGRAMS (CBSm) per CONTROL BLOCK border to his corresponding CO-ORDINATION CENTRE. A-S19.2. Exchange of EXCHANGE PROGRAM (CCT) between CO-ORDINATION CENTRES. Every day (D-1) latest until 16:45 the CO-ORDINATION CENTRE operators have to submit the EXCHANGE PROGRAM (CCT) to his corresponding CO-ORDINATION CENTRE. A-S19.3. CO-ORDINATION CENTRE matching closure. The CO-ORDINATION CENTRE matching has to be completed by the CO-ORDINATION CENTRE operator until (D-1), 17:00. Process- Time [hh:mm] Time [min] for D-1 process Deadline 15:45 Transmission of CAX to affected CB assemble & send CBSb to affected CB 15 16:00 Transmission of CBSb to affected CB matching of CBSb 15 16:15 Matching Closure CB<=>CB assemble & send CBSm to affected CC 15 16:30 Transmission of CBSm to affected CC assemble & send CCT to affected CC 15 16:45 Transmission of CCT to affected CC matching of CCT 15 17:00 Matching Closure CC<=>CC assemble & send CNF CC to affected CB 5 17:05 Transmission of Confirmation CC==> CB assemble & send CNF CB to affected CA 5 17:10 Transmission of Confirmation (CNF) CB to CA CA receives and regards CNF 5 17:15 Control Area has received the CNF CA receives and regards CNF 5 Timetable 1: Day-ahead deadlines for UCTE Scheduling Process

11 P2 11 A-S20. Intra Day scheduling process for commercial Schedules. After the end of the day ahead nomination process in most markets modifications or additional values in the Schedules can be nominated by the market parties (Intra Day scheduling). Due to different local market rules the Intra Day process for cross border scheduling must follow a set of rules which must be bilaterally agreed between the neighbouring Control Areas. These rules must be published or communicated towards the market parties in question. Beside this the affected CONTROL AREAS have to agree on a common Intra Day process being able to run a successful matching and data transmission in time towards other UCTE bodies. The timing of the Intra Day process must allow the responsible UCTE bodies on a higher level to perform a successful matching. The following Intra Day timetable outlines the UCTE scheduling process over all UCTE levels and is based on a Gate Closure Time (GCT) of at least 45min (before setting the schedule into force) for commercial schedules or TSO related schedules. (see P2-A-S, Timetable 2). Exception: Special TSO related schedules may have a GCT shorter than 45min e.g. MEAS (Mutual Emergency Assistant Service) or for SATCR (Schedule Activated Tertiary Control Reserve) but due to the necessity of a different UCTE process, they are not described here. A-S21. Timing for Intra Day matching between CONTROL AREAS. A-S21.1. Transmission of EXCHANGE PROGRAMS (CAS) to affected neighbouring CONTROL AREA has to be completed latest 40 min. before setting the schedule into force. A-S21.2. CONTROL AREA matching closure. The CONTROL AREA matching has to be completed by the CONTROL AREA OPERATORS latest 32min before setting the schedule into force. A-S22. Timing for Intra day matching between CONTROL BLOCKS. A-S22.1. Transmission of EXCHANGE PROGRAM (CAX) from CONTROL AREA to CONTROL BLOCK. The CONTROL AREA OPERATOR has to submit the matched EXCHANGE PROGRAMS per border (CAX) concerning all of his borders to his corresponding CONTROL BLOCK OPERATOR latest 29min before setting the schedule into force. A-S22.2. Exchange of EXCHANGE PROGRAM (CBSb) between CONTROL BLOCKS. The CONTROL BLOCK OPERATOR has to submit the EXCHANGE PROGRAM (CBSb) to his affected neighbouring CONTROL BLOCK latest 26min before setting the schedule into force. A-S22.3. CONTROL BLOCK matching closure. The CONTROL BLOCK

12 P2 12 matching has to be completed by the CONTROL BLOCK OPERATOR latest 24min before setting the schedule into force. A-S23. Timing for Intra day matching between CO-ORDINATION CENTRES. A-S23.1. Transmission of EXCHANGE PROGRAM (CBSm) from CONTROL BLOCK to CO-ORDINATION CENTRE. The CONTROL BLOCK OPERATOR has to submit the matched EXCHANGE PROGRAMS per border (CAX resolution) concerning all of his borders to his corresponding CO- ORDINATION CENTRE operator latest 21min before setting the schedule into force. A-S23.2. Exchange of EXCHANGE PROGRAM (CCT) between CO-ORDINATION CENTRES. The CO-ORDINATION CENTRE operator has to submit the EXCHANGE PROGRAM (CCT) to his corresponding CO-ORDINATION CENTRE latest 18min before setting the schedule into force. A-S23.3. CO-ORDINATION CENTRE matching closure. The CO-ORDINATION CENTRE matching has to be completed by the CO-ORDINATION CENTRE operator latest 16min before setting the schedule into force.

13 Time [min] before executing schedule Deadline Time [min] for process 45 GCT Nomination MPS ==> CA assemble & send CAS to affected CA 5 40 Transmission of CAS to affected CA matching of CAS 8 32 Matching Closure CA<=>CA * assemble & send CAX to affected CB 3 29 Transmission of CAX to affected CB assemble & send CBSb to affected CB 3 26 Transmission of CBSb to affected CB matching of CBSb 2 24 Matching Closure CB<=>CB assemble & send CBSm to affected CC 3 21 Transmission of CBSm to affected CC assemble & send CCT to affected CC 3 18 Transmission of CCT to affected CC matching of CCT 2 16 Matching Closure CC<=>CC assemble & send CNF CC to affected CB 3 13 Transmission of Confirmation CC==> CB assemble & send CNF CB to affected CA 3 10 Transmission of Confirmation (CNF) CB to CA CA receives and regards CNF 5 5 Begin ramping of LFC P EXECUTION OF SCHEDULE MPS=Market Party Schedule GCT= Gate-Closure Time Timetable 2: Intra Day Deadlines for UCTE Scheduling Process * send confirmation to market party after successful matching (see P2-A-S13.2)

14 P2 14 A-S24. TSO driven Modification of EXCHANGE PROGRAMS. Outside the normal market processes, modifications in the UCTE scheduling process can be applied due to agreed security rules (e.g. curtailment of schedules) or other measures. This leads to a TSO driven modification of former matched values of EXCHANGE PROGRAMS. In such a case, the timetable above is not applied because of an emergency situation. A-S25. Final schedules for the accounting of UNINTENTIONAL DEVIATION. After D the responsible System Operator has to transmit the final matched schedules to his UCTE Settlement Responsible. A-S26. Troubleshooting. A-S26.1. Data exchange. Generally for the day ahead and intra day scheduling process the UCTE body having trouble with the transmission of exchange data to his affected counterpart must apply all available backup solutions as soon as possible. (see P2-A-S7) If the exchange can not be managed in time, the affected UCTE body should apply pre-agreed rules. A-S26.2. Matching. Generally for day ahead and intra day matching process all UCTE bodies having trouble with the matching process must apply preagreed rules. (see P2-A-G2 to P2-A-G4and P2-A-S5.4) After successful matching Control Area Operators inform their market parties according to ESS (see P2-A-S13.2). A later modification of these confirmed schedules by the CONTROL AREA Operator because of mismatches on higher UCTE levels is not possible any more. Therefore mismatches on a higher UCTE level must be settled in an agreed other manner. A-S27. Confirmation of matched EXCHANGE PROGRAMS (for Day Ahead and Intra Day). A-S27.1. Confirmations by CO-ORDINATION CENTRES see P2-A-S16.1 A-S for the Day Ahead process latest 5min after successful matching by CO-ORDINATION CENTRES A-S during Intra Day: at latest 13min before setting the matched Schedules into force

15 P2 15 A-S27.2. Confirmation by CONTROL BLOCK see P2-A-S16.2 The CONTROL BLOCK has to confirm the matched EXCHANGE PROGRAMS to the CONTROL AREA OPERATORS by a confirmation report latest 3min after receiving the Confirmation from related CO-ORDINATION CENTRE. A-S28. Supervision of CAPACITY limits. A-S28.1. Checking nominated schedules against allocated CAPACITY. CONTROL AREA OPERATOR must check at any time if the nominated schedule of a market party does not exceed the corresponding allocated CAPACITY limits. In case of limit violation agreed auction rules must be applied. (For more detailed information please refer to UCTE OH Pol.4, Chapter B) A-S28.2. Checking EXCHANGE PROGRAMS against CAPACITY limits. CONTROL AREA and CONTROL BLOCK OPERATORS must check at any time if the totally market-nominated values of the EXCHANGE PROGRAMS do not exceed bilaterally agreed NTC limits. If a CONTROL BLOCK OPERATOR discovers a capacity limit violation the affected CONTROL AREA OPERATORS must be informed. A-S29. Responsibility for the publication of cross border exchange schedules. The CO-ORDINATION CENTRES are responsible for the transmission and publication of matched cross border exchanges on Vulcanus. This requires all time AVAILABILITY of Vulcanus. A-S29.1. Day ahead publication of matched cross border exchanges on Vulcanus. Latest 30min after completing the day ahead (D-1) matching of the CO-ORDINATION CENTRES (see P2-A-S16.1) and before processing intra day Schedules the CO-ORDINATION CENTRE Operators have to transmit the EXCHANGE PROGRAMS for the day ahead process to Vulcanus. The CO-ORDINATION CENTRE Operators must check if the values of the EXCHANGE PROGRAMS of all CONTROL AREAS are considered and that all sum up to zero (not if due to rounding deviations). A-S29.2. Intra Day publication of matched cross border exchanges on Vulcanus. Immediately after completing each intra day matching of the CO- ORDINATION CENTRES the CO-ORDINATION CENTRE Operators have to transmit the EXCHANGE PROGRAMS for intra day process to Vulcanus. (see P2-A-S27.1) The CO-ORDINATION CENTRE Operators must check if the values of the EXCHANGE PROGRAMS of all concerned CONTROL AREAS are considered and that all sum up to zero (not if due to rounding deviations).

16 P2 16 Guidelines A-G1. Data exchange between market parties and CONTROL AREAS. For data exchange, the processes defined in the ETSO ESS are recommended. A-G2. Operation in Case of Mismatches. On all operational levels of the UCTE Pyramid matching takes place to ensure correct EXCHANGE PROGRAMS at all time. In case of mismatches the following procedures should be applied. A-G2.1. Mismatches on CONTROL AREA level. Mismatches on CONTROL AREA level should be solved according to ESS and based on bilaterally agreed rules. (see P2-A-S5.4) The market parties have to be informed about a mismatch according to ESS. A-G2.2. Mismatches on CONTROL BLOCK level. A-G Identification of mismatch: Identification of mismatched time interval (s) and of affected CONTROL AREA border by matching process is based on the EXCHANGE PROGRAM (CBSb) A-G Mismatch correction: The CONTROL BLOCK OPERATOR informs the affected CONTROL AREA OPERATOR. The CONTROL AREA OPERATOR solves the mismatch regarding rules bilaterally agreed with his corresponding CONTROL AREA. The affected CONTROL AREA OPERATOR informs the affected CONTROL BLOCK OPERATOR about the agreed solution. A-G2.3. Mismatches on CO-ORDINATION CENTRE level. A-G Identification of mismatch: Identification of mismatched time interval (s) and the affected CONTROL AREA border is achieved by matching the EXCHANGE PROGRAM (CCT). A-G Mismatch correction: The CO-ORDINATION CENTRE Operator informs the affected CONTROL BLOCK OPERATOR. The CONTROL BLOCK OPERATOR solves the mismatch. The affected CONTROL BLOCK OPERATOR informs the affected CO-ORDINATION CENTRE Operator about the agreed solution. A-G3. Correction of remaining mismatches at Cut-Off Time for day ahead (D-1) In the case that the nominated schedules are not corrected by the market participants, that means that they have a mismatch at Cut-Off Time (D-1), then bilaterally pre-agreed rules are applied. The following rules are possible examples for borders without congestions which can be applied:

17 P2 17 A-G3.1. Where no previously confirmed schedule is available and the nominated Schedule does not have the same delivery direction, the CONTROL AREA OPERATOR sets the schedule to zero. A-G3.2. Where no previously confirmed schedule is available and the nominated schedule has the same delivery direction, the CONTROL AREA OPERATOR sets the schedule to the lower absolute value. A-G4. Correction of remaining mismatches at Cut-Off Time for Intra Day (D) In the case that the nominated Schedules are not corrected by the market participants, that means that they have a mismatch at Cut-Off Time (Intra Day), then bilaterally pre-agreed rules are applied. The following rules are possible examples which can be applied: A-G4.1. In case of no congestion on the boarder and if the EXCHANGE SCHEDULE does not have the same value on both sides of the border, the EXCHANGE SCHEDULE (if any) previously matched and confirmed will stay valid. If no previously matched schedule is available the schedule is set to zero. A-G4.2. In case of congestion on the boarder and if the EXCHANGE SCHEDULE does not have the same value on both sides of the border, the EXCHANGE SCHEDULE is set to the previously reserved capacity.

18 B. Online Observation P2 18 Introduction The task of online observation is performed during the system operation phase. In order to prevent systematic faults in the context of LOAD-FREQUENCY-CONTROL (see Policy 1) it is essential to check the UCTE-wide consistency of the input variables for online operation used by the single parties involved. This comprises the control deviation used as an input value for LOAD-FREQUENCY-CONTROL as well as the real-time observation of bordercrossing exchange power flows and EXCHANGE PROGRAMS among all CONTROL AREAS / CONTROL BLOCKS of UCTE (see Appendix, Figure 2 Hierarchical Levels of UCTE Co-ordination ). Definitions B-D1. Control Program. The CONTROL PROGRAM is the matched set of all EXCHANGE PROGRAMS related to a defined area (e.g. CONTROL AREA, CONTROL BLOCK) and the program for the compensation of UNINTENTIONAL DEVIATION. B-D2. Power Deviation. In this context the meaning is Power Control Error see P1

19 Standards P2 19 B-S1. Accuracy, Transmission of measurements and Power Deviations. (see P1) B-S2. Control Programs. The sum of Control Programs of each UCTE level (e.g. CONTROL AREA level, CONTROL BLOCK level) of a synchronous area must be equal to zero at any time. B-S3. Power deviation. B-S3.1. The sum of Power Deviations of all CONTROL AREAS of a CONTROL BLOCK must be equal to the Power Deviation of the CONTROL BLOCK concerned (taking account of the measurement s range of accuracy). B-S3.2. The sum of Power Deviations of all CONTROL BLOCKS in the area of a CO-ORDINATION CENTRE must be equal to the Power Deviation calculated with respect to the external border of the CO-ORDINATION CENTRE concerned (taking account of the measurement s range of accuracy). B-S3.3. The sum of Power Deviations of all CONTROL BLOCKS of a synchronous area must be equal to zero at any time. (See also glossary) B-S4. Physical Exchange. B-S4.1. The sum of physical exchanges of all CONTROL AREAS of a CONTROL BLOCK must be equal to the physical exchange of the CONTROL BLOCK concerned (taking account of the measurement s range of accuracy) B-S4.2. The sum of physical exchanges of all CONTROL BLOCKS in the area of a CO-ORDINATION CENTRE must be equal to the physical exchange with respect to the external border of the CO-ORDINATION CENTRE concerned (taking account of the measurement s range of accuracy). B-S4.3. The sum of the measurements of the physical exchange of all CONTROL BLOCKS of a synchronous area is equal to zero at any time (taking account of the measurement s range of accuracy). B-S5. Perturbation of measurement equipment. B-S5.1. The operator of the relevant CONTROL AREA has to inform the neighbouring CONTROL AREA OPERATOR and the corresponding operator of the CONTROL BLOCK on any perturbation in the measurement equipment with regard to the physical exchange crossing the border with the neighbouring CONTROL AREA. B-S5.2. The operator of the relevant CONTROL BLOCK has to inform the neighbouring CONTROL BLOCK OPERATOR and the corresponding CO- ORDINATION CENTRE about any perturbation in the measurement

20 P2 20 equipment with regard to the physical exchange crossing the border with the neighbouring CONTROL BLOCK. B-S6. Measures in case of discrepancies. B-S6.1. Detection of abnormal operation. The observation of UNINTENTIONAL DEVIATIONS by the CONTROL BLOCK (see Glossary: Observation of Unintentional Deviations ) allows to identify and to correct as soon as possible abnormal operating and accounting situations (e.g.: abnormal values of TIE-LINE tele-measurements (TMs), misunderstanding in setting the exchange program of a CONTROL AREA, etc.). The CONTROL BLOCK OPERATOR has to contact the responsible UCTE body as soon as possible in order to make corrective measures and to step back to normal operation. B-S6.2. Transmitted and calculated Power Deviation differs B-S If the transmitted Power Deviation of a CONTROL AREA differs from the Power Deviation calculated by the CONTROL BLOCK, the operator of the relevant CONTROL BLOCK has to contact immediately the corresponding operators of the CONTROL AREAS in order to solve the problem. B-S If the transmitted Power Deviation of a CONTROL BLOCK differs from the Power Deviation calculated by the CO-ORDINATION CENTRE, the operator of the relevant CO-ORDINATION CENTRE has to contact immediately the corresponding operator of the relevant CONTROL BLOCK in order to solve the problem. B-S6.3. Power Deviations do not sum up B-S In case that the sum of the Power Deviations of the CONTROL AREAS in a CONTROL BLOCK is not equal to the Power Deviation of the CONTROL BLOCK, the operator of the relevant CONTROL BLOCK shall immediately contact the corresponding operators of the CONTROL AREAS in order to solve the problem. B-S In case that the sum of the Power Deviations of the CONTROL BLOCKS in the area of a CO-ORDINATION CENTRE is not equal to the Power Deviation calculated with respect to the external border of the CO- ORDINATION CENTRE concerned, the CO-ORDINATION CENTRE shall immediately contact the corresponding operators of the CONTROL BLOCKS in order to solve the problem.

21 P2 21 B-S6.4. Control Programs do not sum up B-S In case that the sum of the control programs of the CONTROL AREAS in a CONTROL BLOCK is not equal to CONTROL PROGRAM of the CONTROL BLOCK, the operator of the relevant CONTROL BLOCK shall immediately inform the corresponding operators of the CONTROL AREAS. B-S In case that the sum of the control programs of all CONTROL BLOCKS in the synchronous area is not equal to zero, the responsible CO- ORDINATION CENTRE shall immediately inform the corresponding operators of the CONTROL BLOCKS. Guidelines B-G1. Acquisition of TIE-LINE METERING. The CONTROL BLOCK OPERATORS shall acquire the METERING data of the TIE-LINEs to adjacent CONTROL BLOCKS to record the energy in the time-frame used for power exchanges. B-G2. Exchange of metered data. The CO-ORDINATION CENTRE shall be provided with data of total hourly Scheduled exchanges for each CONTROL BLOCK and real-time active power Telemeasurements of each TIE-LINE crossing the border of the CO- ORDINATION CENTRE area.

22 P2 22 C. Accounting and Settlement of UNINTENTIONAL DEVIATIONS Introduction The task of accounting of UNINTENTIONAL DEVIATIONS is performed "after the fact", e.g. at the next working day following the system operation. It comprises the validation of meter measurement data, followed by the derivation and matching of accounting data, before the settlement of the account of UNINTENTIONAL DEVIATIONS of each CONTROL AREA / CONTROL BLOCK / CO-ORDINATION CENTRE with reference to a recording period is carried out. The compensation of UNINTENTIONAL DEVIATIONS is performed by using a program of compensation "in kind" within the compensation period - as an import / export of the corresponding amount of energy per tariff period, that was accumulated in the recording period. The compensation of UNINTENTIONAL DEVIATION is a duty towards the community of the UCTE TSO and is in the responsibility of the UCTE body responsible for LOAD-FREQUENCY-CONTROL. The COMPENSATION PROGRAMS of all CONTROL BLOCKS respectively all CONTROL AREAS within UCTE must sum up to zero. All times mentioned in this document are related to CET respectively CEST (see also Appendix, Figure 2 Hierarchical Levels of UCTE Co-ordination )..

23 P2 23 Definitions C-D1. Accounting Process. The Accounting Process is the validation of the metered data (usually located at an interconnecting TIE-LINE of a TSO) and of the resulting accounting data. The daily accounting process is usually performed on the first working day after energy delivery. It starts with the initial exchange of metered data between neighbouring TSO, continues with the establishment of the accounting data, and the transmission of the resulting data up to the top of the UCTE pyramid and finishes with the exchange of the accounting data between the Co-ordination Centres top of the UCTE pyramid. The weekly accounting process is identical to the daily process with the exception that it ends at the deadline for the weekly accounting process. The purpose of the daily accounting is to provide a validated set of accounting data to the UCTE bodies in order to calculate every day the actual state of the account of unintentional deviation. The UCTE accounting and process is based on the UCTE pyramid. UCTE-South Coordination Centre (CC) CCVA CC CC UCTE-North CBVA Control Block (CB) CB CB CB CAVA Control Area (CA) CA CA CA CA SOVA TSO Accounting level TSO TSO SOAM TSO TSO TSO TSO Meter data level TSO TSO SOVM TSO SOMA TSO TSO TSO Legend: SOMA SOVM SOAM System Operator Meter Alignment System Operator Validated Measurements System Operator Accounting data Matching SOVA CAVA CBVA CCVA System Operator Validated Accounting data Control Area Validated Accounting data Control Block Validated Accounting data Coordination Centre Validated Accounting data Figure 1: Accounting Process flow: From the bottom to top of the UCTE Pyramid

24 P2 24 C-D2. Settlement Process: A distinction must be drawn between daily and weekly settlement. The daily settlement starts after the daily accounting process. It is the calculation of the UNINTENTIONAL DEVIATION and the update of the state of the account per UCTE body. It is finalised by the transmission of the settlement report on all levels of the UCTE pyramid. The weekly settlement process is identical to the daily one. It covers the correction of daily settlement (if any) and the calculation of the program for compensation of unintentional deviations on the state of the final account at the end of the recording period. The settlement process goes from the top of the UCTE pyramid to its bottom. The basis for the settlement process are the market schedules and the physical energy flow on the lowest level of UCTE pyramid, the TSO level. UCTE-South Coordination Centre (CC) CC CC UCTE-North Control Block (CB) CB CB CB Control Area (CA) CA CA CA CA Figure 2: Settlement Process flow: From top to bottom of UCTE Pyramid C-D3. UNINTENTIONAL DEVIATION (UD). The UNINTENTIONAL DEVIATION is calculated ex post as the sum of the TIE-LINE flows (ET) minus the sum of VIRTUAL TIE-LINE flows (EVT) minus the sum of all market party Schedules (ES) - excluding schedules for the compensation of UNINTENTIONAL DEVIATION - of an defined area during a given CET respectively CEST time period (see P2-C-S5.1.2) C-D4. Physical Energy Exchanges (ET and EVT). C-D4.1. TIE-LINE Flows ET. The sum of the TIE-LINE flows on a border between two TSO / CONTROL AREAS / CONTROL BLOCKS / CO- ORDINATION CENTRES. C-D4.2. VIRTUAL TIE-LINE Flows EVT. VIRTUAL TIE-LINES are used to consider generators physically located in another CONTROL AREA in real time without schedule. The sum of the VIRTUAL TIE-LINE flows (EVT)

25 P2 25 between two TSO / CONTROL AREAS / CONTROL BLOCKS / CO- ORDINATION CENTRES is included in ET and must be considered as below: The physical energy exchange (ET) between CA1 and CA2 is measured by M1+ M2 and includes the physical flow of the generator measured by M3. To isolate the schedule based flow between the CA the measurement M3 has to be subtracted for LFC and for accounting: ET EVT = M1+ M2 M3 Real tie-lines (ET) CA 1 M1 CA 2 LFC ~ M3 Virtual tie-line (EVT) M2 LFC Transmission of measure M3 to LFCs Figure 3: The consideration of VIRTUAL TIE-LINE C-D5. Meter Measurement Data. The physical energy exchange is registered per TIE- LINE, by meter devices installed at substations, which are located at the end of the TIE-LINE. There is at least one main meter device and up to n back up meter devices per TIE-LINE. C-D6. Accounting Point. C-D6.1. The accounting point is the agreed energy delivery point between two TSOs. The accounting value may be equal to a physical metered data or calculated by using meters on both sides. The algorithm for this calculation and the applied rounding rules are agreed between adjacent TSOs. There must be only a single accounting point per TIE-LINE. C-D6.2. In case of a VIRTUAL TIE-LINE the accounting point is normaly located at the generator. In some special cases power flows of the TSOs are based on values which are agreed between the involved TSOs and considered as an accounting value. C-D7. Accounting Data. Accounting Data is the result of an agreement between two TSOs on relevant accounting data and is derived from validated metered data. This can be a one to one copy of the meter measurement data (located at the

26 P2 26 Accounting Point) or a calculation using a given bilaterally agreed formula and one or more meter measurement data. (e.g. In order to consider line losses). Accounting data is considered as a value per TIE-LINE. C-D8. Tariff Period. The Tariff period is the time interval (e.g. season, holiday, working day, etc.) fixed by UCTE agreement during which UNINTENTIONAL DEVIATIONS are attributed the same value for offsetting by compensation in kind (see P2-C- S5.2). The accumulation of UNINTENTIONAL DEVIATIONS within the recording period is performed separately for each tariff period. The tariff periods consist of NT, HT, HHT, HHT1 and HHT2 and distinguish summer and winter period. For the definition of the tariff periods the related calendar day must be taken into account (see P2-C-S1.3 and Figure 5). A tariff period consists up to several hours of a day. C-D9. Working day. The Working Day is the calendar day except Saturday, Sunday and 4 holidays: Christmas 25 th December, New Year, Easter Monday and Ascension. C-D10. Recording period. Recording Period is the time period for which accounting data and schedules are recorded for the UCTE settlement process. Normally the recording period starts on Monday 00:00 and ends on Sunday 24:00 based on CET respectively CEST. C-D11. Compensation Period. Compensation Period is the time period, related to the recording period, during which the CONTROL AREA is applying the program for Compensation of UNINTENTIONAL DEVIATION. Generally the compensation period starts on Thursday 00:00 CET respectively CEST and ends on Wednesday 24:00 CET respectively CEST.

27 Standards P2 27 C-S1. General Process Overview. C-S1.1. Workflow for the accounting- and settlement process. The accounting data goes from the bottom to the top (TSO >CA>CB>CC) The UNINTENTIONAL DEVIATION as well as the related COMPENSATION PROGRAMS are calculated and are sent from top to bottom (CC>CB>CA) CO-ORDINATION CENTRE (CC), CONTROL BLOCK (CB) and CONTROL AREA (CA) are responsible to split down the account of UNINTENTIONAL DEVIATION which finally results in COMPENSATION PROGRAMS for CONTROL BLOCK and CONTROL AREA. Each level has to ensure that there is no difference (or rounding difference) induced by the splitting. Rounding differences have to be taken by the UCTE body responsible for the corresponding UCTE pyramid level. (see P2-C-D1. & P2-C-D2. and see A2 Figure11) A small amount of energy which cannot be compensated, e.g. due to rounding, remains on the account of UNINTENTIONAL DEVIATIONS. C-S1.2. Recording Period, Compensation Period The accounting process is based on the recording period m. The compensation of UNINTENTIONAL DEVIATIONS is performed in kind within the compensation period m as an import / export of the corresponding amount of energy per tariff period, that was accumulated in the recording period. Figure 4 gives an overview to this procedure. The standard recording period is defined to comprise 7 days (one week), from Monday, 0:00 to Sunday 24:00 whereas the standard compensation period is defined to comprise 7 days (one week), from Thursday, 0:00 to Wednesday 24:00 of the week following the recording period. Recording Period m Recording Period (m+1) Recording Period (m+2) 0:00 24:00 0:00 24:00 0:00 Fr Sa Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su 0:00 24:00 0:00 24:00 0:00 Fr Sa Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Compensation Period m Mo Tu Mo Tu Mo Tu Final Accounting m Figure 4: Recording Period, Compensation Period

28 P2 28 C-S1.3. Tariff Period. The valid tariff periods of UCTE are indicated below HHT Winter* HT Winter* NT Winter* HHT 1 Summer** HHT 2 Summer** HT Summer** NT Summer** Monday - Saturday Sunday / Holiday Monday - Saturday Sunday / Holiday Monday - Saturday Sunday / Holiday Monday - Friday Saturdaye Sunday / Holiday Monday - Friday Saturdaye Sunday / Holiday Monday - Friday Saturdaye Sunday / Holiday Monday - Friday Saturdaye Sunday / Holiday *: The Winter: black bars present ; the Holidays: tariff hours in consideration und of the season, the day and the tariff. **: NT: Summer: Low tariff, HT: - High ; tariff, Holidays: HHT: Peak Easter tariffs Monday and Ascension * Winter: ** Summer: Holidays: , , Ascension and Easter Monday depending on calendar Figure 5: UCTE Tariff Periods C-S1.4. Consideration of time shift CET - CEST C-S For the day having a duration period of 23h, it is agreed upon that the period 02:00 to 03:00 is cancelled. Thus, the tariff on this day will be applied using the tariffs for the period 00:00 to 02:00 and 03:00 to 24:00 as listed in the table. C-S For the day having a duration period of 25h, it is agreed upon that the period 02:00 to 03:00 will be considered having a two hours duration for the calculation. Thus, the tariff on this day will be applied using the tariffs for the period 00:00 to 03:00, additional 02:00 to 03:00 and 03:00 to 24:00 as shown in figure 5. C-S1.5. Changes of standard recording and compensation In case of bank holidays or the change of tariff seasons exceptions to the standard recording and compensation periods may occur. The CO- ORDINATION CENTRES agree on exceptions to the definition of the recording period / compensation period. Starting with the CO-ORDINATION CENTRES, each UCTE level informs the level below 4 weeks before the start of the recording period. The following rules have to be taken into account: A recording period must last at minimum 4 days

29 P2 29 A compensation period must last at minimum 4 days The compensation period has to start always with a delay of at least three days after the end of the corresponding recording period. C-S1.6. Further local exceptions In case of unavailability of an accounting office, e.g. national bank holidays or system maintenance, the office in question must inform the upper UCTE level at least 4 weeks before. C-S2. General rules C-S2.1. Accounting and Settlement Period The daily accounting and settlement is done for the day D (see P2-A-D11) on the next working day. (see P2-C-D9.) The weekly accounting and settlement is done for the recording period. C-S2.2. Time Frame The time frame for Accounting of UNINTENTIONAL DEVIATIONS has to correspond with the time frame of the EXCHANGE PROGRAM (1h, ½ h, ¼ h); this time frame applies to the frames for ET, EVT, UD and the program for the Compensation of UNINTENTIONAL DEVIATIONS. The time frame must be the same on a common border between two areas. C-S2.3. Rounding rules Generally the data exchanged is in MWh. If all CONTROL AREAS in a CONTROL BLOCK agree, a mathematical rounding in kwh can be performed. The program for compensation of UNINTENTIONAL DEVIATION of a CONTROL BLOCK must be in full MW only. By default the program for the Compensation of UNINTENTIONAL DEVIATIONS for a CONTROL AREA should be in MW but if all CONTROL AREAS in a CONTROL BLOCK agree, the program for the Compensation of UNINTENTIONAL DEVIATIONS may be in kw. The remaining amount of energy in kwh stays on the account of UNINTENTIONAL DEVIATIONS. C-S2.4. Electronic Data Exchange Electronic data exchange for accounting and settlement is required using e- mail via EH. If the via EH is disturbed, an electronic back-up must be agreed such as via internet or ftp-dial in via ISDN-line. If electronic communication is generally disturbed, fax or phone must be used as last back-up.