Technical Balance Group Regulations

Transcription

1 Page 1 of 44 Technical Balance Group Regulations Technical Regulations relating to the Balance Group Contract

2 Page 2 of 44 Contents Preamble 5 1 Definitions 5 2 Scope of application 5 3 Principles of the balance group model General Description of the 3-balance group type model Comparison of balance group types 6 4 Trade types in schedule management General Internal trade External trade 8 5 Classification of schedule messages 9 6 Additions to the ESSIG 9 7 Version numbers in schedule messages 11 8 Times in schedule messages 12 9 Schedule difference rules Internal trade and external trade without allocation procedure External trade Nomination rules Day-Ahead procedure Day-Ahead procedure for external trade on the Switzerland-Germany, Switzerland-Austria, Switzerland-France borders and internal trade Overview of the Day-Ahead procedure Details of the Day-Ahead procedure Day-Ahead procedure for external trade at the Switzerland-Italy border Overview of the Day-Ahead procedure Details of the Day-Ahead procedure Intra-Day procedure Intra-Day procedure for external trade on the Switzerland-Germany, Switzerland- Austria, Switzerland-France borders and internal trade for Standard Balance Groups Overview of Intra-Day procedure for Standard Balance Groups Details of Intra-Day procedure for Standard Balance Groups Intra-Day procedure for external trade at the Switzerland-Italy border for Standard Balance Groups Overview of Intra-Day procedure Details of Intra-Day procedure 26

3 Page 3 of Intra-Day procedure for external trade on the Switzerland-Germany, Switzerland- Austria, Switzerland-France borders and internal trade for Control Balance Group and CH-15 Balance Groups Overview of Intra-Day procedure for Control Balance Groups and CH-15 Balance Groups Post Scheduling Adjustments Overview of post scheduling adjustments Details of post scheduling adjustment Status Request Maintenance of grid security in case of congestion Compliance with capacity rights Content and structure of individual documents Schedule Message TPS message header codes Schedule time series codes for an external trade Schedule time series codes for internal trade Acknowledgment Message (ACK) Reason Codes Message Level (ACK) Reason Codes Time Series Level (ACK) Reason Codes Time Interval Level (ACK) Anomaly Report Intermediate and Final Confirmation Report Reason Codes Message Level (CNF) Reason Codes Time Series Level (CNF) Reason Codes Time Interval Level (CNF) Status Request Naming conventions File names for schedule messages File names for acknowledgments File names for Status Request Submission of data General Submission time Data submission options Data submission via ftp Data protection and security Combination of standard and standby connection Suspension of schedule message management Energy data and imbalance data Trial run of schedule management 43

4 Page 4 of Supplementary provisions 44

5 Page 5 of 44 Preamble The following Technical Balance Group Regulations form an integral part of the Balance Group Contract between Swissgrid and the BGM. They describe the provisions governing the operational implementation of the Balance Group Contract and the management of schedule messages and balance group billing. The general requirements and procedures applicable to balance groups are contained in the General Balance Group Regulations, which likewise form an integral part of the Balance Group Contract. 1 Definitions The terms used in this Contract (including its annexes and forms, where applicable) are applied in accordance with the definitions in the Electricity Supply Act (StromVG), the Electricity Supply Ordinance (StromVV) and the Glossary for the Rules of the Swiss Electricity Market. The abovementioned glossary is published and available to view on the VSE website ( and the Swissgrid website ( 2 Scope of application These Technical Balance Group Regulations form an integral part of the Balance Group Contract. Supplemented by the General Balance Group Regulations, they describe requirements and procedures relating to the management of schedule messages, and in particular the form, content, registration times, and other deadlines, as well as technical requirements for the examination, coordination and confirmation of schedule messages. 3 Principles of the balance group model 3.1 General In Switzerland one control area exists: the Swiss control area A 3-balance group model is applied according to which a differentiation is made between standard balance groups, control balance groups and CH-15 balance groups Within the Swiss control area there are many balance groups (BG). Each Swiss feed-in and feed-out point (generation plants and end users) is assigned to a balance group. ASPs may access every Swiss inflow and outflow point of both their own and another balance group. Cross-control area trading with foreign countries and inter-balance group trading in Switzerland requires the conclusion of a balance group contract with Swissgrid. In addition to the balance group contract, balance groups with suppliers and purchasers (feed-in and feed-out) must also agree on regulations with the respective grid operators governing the exchange of measuring data. The Balance Group Manager (BGM) is responsible for the operation of a balance group.

6 Page 6 of Description of the 3-balance group type model There are three balance group types o o o Standard BG Reserve BG CH-15 BG Lead times for intraday scheduling separated according to type of balance group o Standard BG 45 min. o Reserve BG and CH-15 BG 15 min. The different types of balance groups are combined per BGM into one billing unit. The billing unit has the same EIC code as the standard BG. Only one balance group per type can be assigned to a billing unit in each case. Schedule messages are possible only between balance groups of the same type. Measuring points (power stations and end consumers) are assigned to the standard BG of the BGM. The imbalance energy is determined in aggregate for the billing unit. A standard BG is the criterion for opening a reserve BG or CH-15 BG. 3.3 Comparison of balance group types Each BG type must have its own schedule message. Capacity checks will be specifically used for cross border trades and will be carried out per border, direction and balance group. The transaction options of each type of balance group are represented in the following table: Temporal Regional BG type Day ahead Intra-day (45min lead time) Short notice (15min lead time) Post Scheduling (only CH internal) Internal trade External trade Standard BG Reserve BG CH15 BG allowed / - not allowed To set up a reserve balance group, proof that one of the following conditions is satisfied must be provided: proof of participation in an international reserve energy market. proof of participation in a national reserve energy market. proof of a reserve energy supply contract.

7 Page 7 of 44 4 Trade types in schedule management 4.1 General Two trade types are differentiated in the context of schedule management: a. Internal trade b. External trade Refer to Figure 1 below for a graphical overview of the two trade types. Ausland ÜBERTRAGUNGS - NETZ TSO 1 TSO 2 TSO n (Handel international) BG 1 BG 1 Schweiz Externer Geschäftsfall BG 1 Interner Geschäftsfall BG 4 BG 3 REGELZONE SCHWEIZ ÜBERTRAGUNGS - NETZ / VERTEILNETZ (Schweiz) BG 2 Figure 1: Balance Group Concept schematic representation 4.2 Internal trade All trading in and/or exchange of electricity between balance groups in Switzerland, including the processing of internal transactions for the supply of ancillary services to Swissgrid, is managed in the form of internal trade. All BGMs can exchange electricity with one another via their respective balance groups by means of schedule messages. The procedure comprises the following steps (see also Figure 2): The BGMs concerned coordinate all schedule messages with one another. Following this coordination, the BGMs must submit the schedule messages (TPS) to Swissgrid within the time period specified by Swissgrid. Swissgrid carries out the formal examination and the schedule coordination. If any discrepancies are revealed by the formal examination or the schedule coordination, the BGMs concerned are notified by Swissgrid about the rejection of the schedule message or schedule time series. The BGMs may correct incorrect schedule messages within the time period specified by Swissgrid.

8 Page 8 of 44 INTERNER GESCHÄFTSFALL: Energieaustausch zwischen BG Ausland REGELZONE 1 ÜNB REGELBLOCK ÜBERTRAGUNGS- NETZ (Handel international) Schweiz REGELZONE SCHWEIZ TPS swissgrid RB swissgrid ÜNB Legende: Stromaustausch FAHRPLAN MELDUNG: BG 1 BG 2 TPS Figure 2: Energy exchange between balance groups 4.3 External trade External trade usually involves the exchange of electricity between a balance group in Switzerland and a balance group in a control area adjoining the Swiss control area, whereby the balance group in Switzerland and the balance group in the adjoining control area are assigned to the same BGM (1:1 nomination). Alternatively, another procedure per border (e.g. 1:n nomination) can be published on the Swissgrid website ( or in the relevant auction rules. The procedure comprises the following steps (see also Figure 3): The BGM must submit to Swissgrid, and the BGM abroad to the TSO concerned, a schedule message (TPS) which corresponds to the counterpart schedule message within the specified time periods. Swissgrid carries out the formal examination of the schedule messages submitted to Swissgrid. A similar examination is carried out by the TSO in the neighbouring control area concerned. Schedule coordination is then carried out by Swissgrid jointly with the TSO (CAS/TPS). If any discrepancies are revealed by the formal examination or the schedule coordination, the BGM concerned is notified by Swissgrid about the rejection of the schedule message or schedule time series. The BGM may correct incorrect schedule messages within the specified time period. Swissgrid and the TSO concerned submit their schedule messages (CAX) to the responsible control block operators, which then coordinate these messages (CBS) at control block level.

9 Page 9 of 44 EXTERNER GESCHÄFTSFALL: Regelzonenüberschreitender Energieaustausch Ausland REGELZONE 1 BG TPS ÜNB CAX REGELBLOCK CBS CBS ÜBERTRAGUNGS- NETZ (Handel international) CAS CAS Schweiz REGELZONE SCHWEIZ swissgrid RB Legende: Stromaustausch BG TPS CAX swissgrid ÜNB FAHRPLAN- MELDUNG Figure 3: Energy exchange between control areas 5 Classification of schedule messages Schedule messages are classified as follows: «submitted» means that a schedule message has been submitted to Swissgrid in accordance with the DTD and ESS, and that it can be read into the balance group system. «accepted» means that a schedule message has been read into the balance group system following a formal examination. «rejected» means that a schedule message, or one or more schedule time series, has not been read into the balance group system following a formal examination. «balanced» means that a successful schedule coordination has been carried out for a schedule time series. The BGM receives an Intermediate Confirmation Report. «provisionally confirmed» means that a schedule message has been fully processed and complies with the rules. The BGM receives an Intermediate Confirmation Report. «confirmed» means that the schedule has been run. After the final message submission deadline, the BGM receives a Final Confirmation Report. 6 Additions to the ESSIG Schedule message submission and coordination is managed in Switzerland in accordance with the ENTSO- E ( ESS Implementation Guide (ESSIG). These Technical Balance Group Regulations are based on the ESSIG. The structure of the schedule messages is based on the rules described in Section 3.3 of ESSIG v2r3. The following supplementary, specific, or contrary provisions must be complied with in connection with the ESSIG rules referred to below: Rule 1: Rule 3: The BGM must submit all schedule messages in XML format in accordance with ESSIG v2r3. If a time series is rejected the entire message is not discarded in the Day Ahead and Intra Day process. In the Post Scheduling Adjustment Process the entire message is always discarded.

10 Page 10 of 44 Rule 10: Rule 11: Rule 12: Rule 14: A schedule time series always comprises the full calendar day. A schedule time unit comprises 15 minutes. Each schedule time series thus comprises 96 schedule time units, or 92 schedule time units at the start of summer time and 100 schedule time units at the end of summer time (refer also to Figure 4). The time interval covered by a schedule message must be identical to the time intervals of the schedule time series it contains. The start and end times of this interval are specified in UTC. Negative values are not allowed in schedule time series. The direction is not determined by a sign but by the following information: «Out Area», «In Area» and/or «Out Party», «In Party». The schedule time series are balance schedules. If a balance position includes both directions, a separate schedule time series is submitted for each direction. Only one of these two schedule time series can be not equal to zero in each schedule time unit. Values for a schedule time series are specified as mean power. The unit is always MW (code «MAW»). Up to three decimal digits are allowed. A period («.») is always used as the decimal separator. The decimal digits are not mandatory. Omitted decimal digits are assumed to be zero (100 MAW = MAW). Internal schedule time series takes account of the three decimal digits ( ). For external schedule time series different principles are valid: Germany: France: Italy: Austria: three decimal digits two decimal digits no decimal digits three decimal digits The following additional rule applies to all schedule messages: The sender of a schedule message specifies the version number. All acknowledgments (Acknowledgement Message, Anomaly Report, Intermediate Confirmation Report or Final Confirmation Report) must include the version number of the schedule message concerned. A schedule message should normally consist exclusively of schedule time series which contain a value not equal to zero in at least one schedule time unit (exception: schedule time series in accordance with ESSIG section 3.3, rule 3). Un-submitted schedule time series are interpreted as schedule time series with zero values. A schedule message may not contain any country-specific special characters. In the same way as for the EIC, «0» to «9», «A» to «Z», and «-» are valid characters as well as if necessary «a» to «z». Schedule message time units in schedule messages with the process types A01 or A02 (see section ) containing new or modified power values corresponding to a time period in the past are rejected in the formal examination. Schedules with the process type A13 in which external schedule time series have changed compared to the last CNF in the Intra Day process are completely rejected in the formal examination. Different values may be contained in the schedule messages for each schedule time unit. In the case of external schedule time series, the schedule management guidelines of the TSO responsible at the respective borders must be observed.

11 Page 11 of 44 7 Version numbers in schedule messages Version numbers must be specified in compliance with ESSIG section The allocation of version numbers starts again at 1 every day. They must be indicated in each schedule time series as well as in the message header of the schedule message (see also Example 1). Example 1: First submission of a schedule message Version number of the schedule message Schedule time series of the schedule message Version number of the schedule time series 1 Schedule time series 1 1 Schedule time series 2 1 Schedule time series 3 1 A schedule message must be rewritten and resubmitted each time its content changes. The version number of the schedule message («message version») must be incremented, and the changed schedule time series identified with this new version number (see also Examples 2 and 3). If this rule is not heeded, the schedule time series is interpreted as unchanged and not taken into account in the schedule coordination. Example 2: Second submission of the schedule message (schedule time series 2 changed) Version number of the schedule message Schedule time series of the schedule message Version number of the schedule time series 2 Schedule time series 1 1 Schedule time series 2 2 Schedule time series 3 1 Example 3: Third submission of the schedule message (schedule time series 1 and 3 changed) Version number of the schedule message Schedule time series of the schedule message Version number of the schedule time series 3 Schedule time series 1 3 Schedule time series 2 2 Schedule time series 3 3 If a schedule time series is added to the schedule message, the version number of the schedule message is incremented by 1 and the new schedule time series is identified with this version number.

12 Page 12 of 44 Example 4: Fourth submission of the schedule message (addition of a new schedule time series 4) Version number of the schedule message Schedule time series of the schedule message Version number of the schedule time series 4 Schedule time series 1 3 Schedule time series 2 2 Schedule time series 3 3 Schedule time series 4 4 If the unchanged schedule message needs to be processed again, the version numbers of the schedule message itself and all schedule time series must be incremented (see also Example 5). Example 5: Fifth submission of the schedule message (all schedule time series are unchanged but need to be read in again) Version number of the schedule message Schedule time series of the schedule message Version number of the schedule time series 5 Schedule time series 1 5 Schedule time series 2 5 Schedule time series 3 5 Schedule time series 4 5 When transferring from Day-Ahead to Intra-Day or from Intra-Day to the Post Scheduling Adjustment process the version numbers need to be incremented further. The message ID remains unchanged. The allocation of a version number is usually always the responsibility of the ESS participant writing the schedule message. 8 Times in schedule messages All times and dates given in the document are in local Swiss time (CET). All times in schedule messages must be specified in UTC. UTC deviates from local Swiss time (CET) by one hour in winter and two hours in summer (refer also to Figure 4). Times are specified as follows in the schedule messages: YYYY-MM-DDTHH:MMZ/YYYY-MM-DDTHH:MMZ in UTC YYYY: Year MM: DD: HH: MM: Month Day Hour Minute

13 Page 13 of 44 z.b :00 24:00 Uhr z.b :00 24:00 Uhr z.b :00 24:00 Uhr Winterzeit T23:00Z / T23:00Z 96 ¼-h-Werte Sommerzeit T22:00Z / T22:00Z 96 ¼-h-Werte Winterrzeit T23:00Z / T23:00Z 96 ¼-h-Werte Zeitumstellung Winter -> Sommerzeit T23:00Z / T22:00Z 92 ¼-h-Werte Zeitumstellung Sommer -> Winterzeit T22:00Z / T23:00Z 100 ¼-h-Werte Figure 4: Changeover to summer or winter time (times in CET) 9 Schedule difference rules The schedule difference rules are applied if at the settlement deadline schedule differences exist between the schedule time series of the BGM and the corresponding schedule time series or capacity rights are not adhered to. Special rules can be applied for special processes. The following cases are differentiated: 9.1 Internal trade and external trade without allocation procedure Day-Ahead If the schedule time units concerned have the same electricity delivery direction in both the schedule message and the counterpart schedule message, the lower of the two values in the schedule message and the counterpart schedule message is selected in the event of schedule differences between these schedule time units. If the electricity delivery direction is not the same in the schedule message and in the counterpart schedule message, the relevant schedule time series in the two schedule messages are set to zero in the schedule time units concerned. A missing schedule time series is considered as a time series with zero values. Notwithstanding the aforementioned provisions, in the case of a mismatch of schedule time units of the balance group of an energy exchange (or the involved shipping agent), the values of the schedule of the energy exchange (or the involved shipping agent) are selected. Intra-Day / Post Scheduling Adjustment process Irrespective of whether the electricity delivery direction in the schedule message and in the counterpart schedule message is the same or not, the schedule time series of the two schedule messages in the schedule time units concerned are set to the last successfully coordinated status. When a schedule message is submitted for the first time the last coordinated state is zero. In the case of the delivery of schedules by Swissgrid to the BGM as part of the processing of ancillary services, Swissgrid's values shall take precedence in the event of differences. Notwithstanding the above provisions, in the event of disagreement between the schedule time series of the balance group and the power exchange (or shipping agent) involved, the power exchange values (and those of the corresponding shipping agent) shall be used.

14 Page 14 of External trade At the respective Swiss borders the following rules apply: Italian border in the day-ahead export to Italy In the event of absence of the corresponding schedule time series, the minimum required capacity values are set. In the event of value differences, the minimum value is set, taking into account the minimum necessary capacity rights and the day right. If the schedule time series match but the capacity rights are disregarded, the minimum required capacity values are set. Italian border in the day-ahead import from Italy and in the intraday in both directions In the event of value discrepancies, the Terna values take precedence. French, German and Austrian border: In the day-ahead and intraday, the values of the neighbouring TSO take precedence in the event of mismatches. 10 Nomination rules The following nomination rules are valid for the nomination process at Swissgrid. If the nomination process is performed by the partner TSO (TransnetBW, Amprion, RTE, APG or Terna), the rules of the partner TSO should be used. Yearly / Monthly PTRs Border CH-DE Border CH-FR Border CH-AT Border CH-IT Nomination Platform Direction: IT->CH: Terna TransnetBW No nominations on Swissgrid Nomination Platform RTE No nominations on Swissgrid Nomination Platform APG No nominations on Swissgrid Nomination Platform Direction CH->IT: Swissgrid Nomination Platform ( d.ch/swissgrid/en/too ls/login-sns.html) Nomination Principle n.a. n.a. n.a. A:A or A:N Counterparty Notification n.a. n.a. n.a. Details can be found on the Swissgrid website ( e/experts/topics/cong estion_management/ch - it/auction_registration.html) Nomination Deadline n.a. n.a. n.a. D-1 08:30 Type of Nomination n.a. n.a. n.a. per Contract ID and direction

15 Page 15 of 44 Nomination Timeframe n.a. n.a. n.a. Format (see chapter ) Once the corresponding Contract ID is know n.a. n.a. n.a. Manual entry at the Swissgrid Nomination Platform Matching Rule n.a. n.a. n.a. In the case of mismatch in the direction CH->IT the Swissgrid nomination shall prevail Daily PTRs Nomination Nomination Principle Counterparty Notification Nomination Deadline Type of Nomination Nomination Timeframe Format (see chapter ) Matching Rule Border CH-DE Border CH-FR Border CH-AT Border CH-IT both TransnetBW, Amprion and Swissgrid both RTE and Swissgrid both APG and Swissgrid both Terna and Swissgrid A:A A:A A:A A:A or A:B n.a. n.a. n.a. Details can be found on the Swissgrid website ( e/experts/topics/cong estion_management/ch - it/auction_registration.html) D-1 14:30 D-1 14:30 D-1 14:30 D-1 14:30 total netted total netted total netted total netted from receipt of JAO capacity rights until D-1 14:30 ESS V2R3 (Business Type A06) Minimum value from receipt of JAO capacity rights until D-1 14:30 ESS V2R3 (Business Type A06) RTE s schedule prevails from receipt of JAO capacity rights until D-1 14:30 ESS V2R3 (Business Type A06) Minimum value from receipt of JAO capacity rights until D-1 14:30 ESS V2R3 (Business Type A03) In the case of mismatch in the direction CH->IT the minimum capacity rights shall prevail In the case of mismatch in the direction IT->CH the Terna values shall prevail

16 Page 16 of 44 Intraday PTRs Nomination Platform Nomination Principle Counterparty Notification Nomination Deadline Type of Nomination Nomination Timeframe Format (see chapter ) Matching Rule Border CH-DE Border CH-FR Border CH-AT Border CH-IT both TransnetBW, Amprion and Swissgrid Swissgrid both APG and Swissgrid both, Terna and Swissgrid A:A A:A A:A A:A n.a. n.a. n.a. n.a. 45min prior to delivery or 15min prior to delivery for Balancing Market (only possible with schedules from Control Balance Group) 45min prior to delivery CH->FR or 15min prior to delivery for Balancing Market (only possible with schedules from Control Balance Group) 45min prior to delivery ID1: D-1 17:30 ID2: D 12:30 total netted total netted total netted n.a. until 45min prior to delivery or 15min prior to delivery for Balancing Market (only possible with schedules from Control Balance Group) ESS V2R3 (Business Type A06) Acceptance of TransnetBW s and Amprion s nomination until 45min prior to delivery CH->FR or 15min prior to delivery for Balancing Market ESS V2R3 (Business Type A06) Acceptance of RTE s nomination until 45min prior to delivery ESS V2R3 (Business Type A06) Acceptance of APG s nomination ID1: D-1 17:00 to 17:30 ID2: D 12:00 to 12:30 ESS V2R3 (business type A03, capacity contract A05) In case of mismatch, nomination at Terna shall prevail

17 Page 17 of 44 Post Scheduling Nomination Plattform Nomination Principle BG-Typ Bilateral trades between BG s Swissgrid A:N Standard-BG, CH-15 BG Internal trades for the processing of ancillary services by Swissgrid Swissgrid A:B (A=Swissgrid) providing of ancillary services from ASP from the allied balance group: Control-BG providing of ancillary services from ASP from other balance groups Standard-BG Nomination Deadline D+1 17:00 1 Nomination until D+1 10:00 Nominationstyp Nomination Timeframe Format (see chapter ) Matching Rule total netted Matching D+1 17:00 total netted Ab D+1 00:00 bis D+1 17:00 Ab D+1 00:00 bis D+1 10:00 ESS V2R3 (Business Type A02) ESS V2R3 (Business Type A02) Last accepted values Swissgrid values shall prevail 2 11 Day-Ahead procedure 11.1 Day-Ahead procedure for external trade on the Switzerland-Germany, Switzerland- Austria, Switzerland-France borders and internal trade Overview of the Day-Ahead procedure Day-ahead schedules can be submitted up to one month in advance. Different rules may apply for crossborder schedule relationships with an allocation procedure. The respective auction rules take precedence over these Technical Balance Group Regulations. 1 workingday, see chapter 13 2 In Reference to the general balance group regulations, Swissgrid guarantees the correctness of the data

18 Page 18 of 44 The formal examination is carried out by Swissgrid as soon as the schedule message has been received. Schedule coordination in connection with the Day-Ahead procedure takes place on the day preceding the day on which the schedule message is executed. RZ-Fahrplanabstimmung RB-Fahrplanabstimmung FP-Abwicklung gemäss Intra-Day 24:00 14:30 Anmeldeschluss 14:45 Anmeldeschluss für CAS 15:30 Einigungsschluss 16:30 Fahrplanzeitreihen Day-Ahead eingestellt Figure 5: Day-Ahead procedure (times given in CET) The submission deadline specified by Swissgrid for schedule messages for the following day D is D Schedule coordination between Swissgrid and the neighbouring TSOs commences at If Swissgrid establishes discrepancies in the schedule message, it notifies the BGM. From D until the settlement deadline (D-1 15:30), the BGMs whose schedule messages do not correspond to the counterpart schedule messages are given time to rectify such discrepancies. The BGMs concerned may correct incorrect schedule time series with a new schedule message. If they do not succeed in rectifying the discrepancies within the specified time period, Swissgrid applies the schedule difference rules at D-1 15:30. Coordination between the affected control blocks also takes place from D-1 15:30. When coordination at control block level is completed at approximately D-1 16:30, a check is carried out for congestion. Congestion measures can be ordered by Swissgrid if necessary Details of the Day-Ahead procedure Zeit BG swissgrid RB CH ÜNB BG TPS ACK TPS D-1, 14:30 Anmeldeschluss TPS D-1, 15:30 D-1, 16:30 CAS ACK CAS CAS ACK CAS INT CNF TPS CAX ACK CAX Einigungsschluss TPS Anmeldeschluss CAX Start Intra-Day D, 23:45 Ende Intra-Day D+1, 00:00 Start Post Scheduling Adjustments Figure 6: Day-Ahead procedure (external trade)

19 Page 19 of 44 Figure 6 shows the steps necessary for successful coordination in the Day-Ahead procedure (without discrepancies or corrective measures). Day preceding the day on which the schedule message is executed (D-1): Until D-1 14:30: Submission of schedule messages for the following day to Swissgrid by the BGM. An Acknowledgment Message is sent by Swissgrid to the BGM each time a schedule message is received. D-1 14:30: Deadline for the submission of schedule messages to Swissgrid by the BGM. Day-Ahead Schedule Messages (process type A01) submitted after 14:30 are rejected if they contain new schedule time series. Schedule differences may be corrected, however. New schedule time series can only be submitted in the context of Intra-Day schedule messages (process type A02). From this time on, the processing of a status request for the relevant time series will be possible. From D-1 14:30: Start of schedule coordination in the Swiss control area and between Swissgrid and the TSOs in the neighbouring control areas. In the event of schedule differences, an Anomaly Report is sent to the BGM concerned. Schedule differences can be corrected by submitting a new Day-Ahead schedule message (process type A01). Coordinated schedule time series can no longer be changed in the Day-Ahead process. D 15:30 Settlement deadline: From this point in time onwards, Day-Ahead schedule messages for correcting schedule differences can no longer be submitted by the BGM. At the settlement deadline, all successfully coordinated day-ahead schedule messages are classified as «balanced». If schedule differences still exist, they are corrected according to the schedule difference rules. Any Day-Ahead schedule messages (process type A01) for the next day which are received after 15:30 are rejected. Management of such messages is, however, always possible in the form of Intra-Day schedule messages as part of the Intra-Day procedure From D-1 15:30: After the settlement deadline and the possible application of the schedule difference rules, Intermediate Confirmation Reports are sent to the BGM. This means that the Day-Ahead schedule message is classified as «provisionally confirmed». Coordination is subsequently carried out at control block level. Intra-Day schedule messages for the next day (D) are read in during this phase but not processed further From D-1 16:30: The control block operators carry out a grid security analysis on the basis of the provisionally confirmed Day-Ahead schedule messages. If congestion is detected, operational congestion management measures are initiated (e.g. Redispatch).

20 Page 20 of Day-Ahead procedure for external trade at the Switzerland-Italy border Overview of the Day-Ahead procedure Day-ahead schedules can be submitted up to one month in advance. The formal examination is carried out by Swissgrid as soon as the schedule message is received. Schedule coordination in connection with the Day-Ahead procedure takes place on the day preceding the day on which the schedule message is executed. FP-Abwicklung gemäss Intra-Day 24:00 14:45 Anmeldeschluss für CAS 15:15 RZ-Fahrplanabstimmung 14:30 Anmeldeschluss RB-Fahrplanabstimmung Einigungsschluss 16:30 Fahrplanzeitreihen Day-Ahead eingestellt Figure 7: Day-Ahead procedure on the Switzerland-Italy border (times given in CET) The submission deadline specified by Swissgrid for schedule messages for the following day D is D-1 14:30. From D-1 14:30 schedule coordination between Swissgrid and Terna applies. To the extent that no capacity rights for the BGM's schedule nomination are present, the BGM receives formal confirmation of the time series, subject to examination of the capacity rights (reason code B06). Upon input of the capacity rights, a second ACK shall be issued for the schedule. For violations of capacity rights determined by the capacity check, these shall be returned to the BGM with a corresponding ACK (reason code A27, the reason text shall differentiate between exceeded and unmet capacity rights). If Swissgrid establishes discrepancies in the schedule messages to Terna and Swissgrid, it notifies the BGM. From D-1 14:30 until the settlement deadline (D-1 15:15), the BGMs whose schedule messages do not correspond to the counterpart schedule messages are given time to rectify such discrepancies. The BGMs concerned may correct incorrect schedule time series with a new schedule message. If they do not succeed in rectifying the discrepancies within the specified time period, Swissgrid applies the schedule difference rules at D-1 15:15. Coordination between the affected control blocks also takes place from D-1 15:45. When coordination at control block level is completed at approximately D-1 16:30, a check is carried out for congestion. Congestion measures can be ordered by Swissgrid if necessary. The auction rules for the Swiss-Italy border take precedence over these Technical Balance Group Regulations.

21 Page 21 of Details of the Day-Ahead procedure Zeit BG swissgrid RB CH ÜNB BG TPS ACK TPS D-1, 14:30 Anmeldeschluss TPS D-1, 15:15 D-1, 16:30 CAS ACK CAS CAS ACK CAS INT CNF TPS CAX ACK CAX Einigungsschluss TPS Anmeldeschluss CAX Start Intra-Day D, 23:45 Ende Intra-Day D+1, 00:00 Start Post Scheduling Adjustments Figure 8: Day-Ahead procedure (external trade) Figure 8 shows the steps necessary for successful coordination in the Day-Ahead procedure (without discrepancies or corrective measures). Day preceding the day on which the schedule message is executed (D-1): Until D-1 14:30: Submission of schedule messages for the next day to Swissgrid by the BGM. An Acknowledgment Message is sent by Swissgrid to the BGM each time a schedule message is received. D-1 14:30: Submission deadline for schedule messages submitted to Swissgrid by the BGM. Day- Ahead Schedule Messages (process type A01) submitted after 14:30 are rejected if they contain new schedule time series. Schedule differences may be corrected, however. From this time on, the processing of a status request for the relevant time series will be possible. From D-1 14:30: Start of schedule coordination between Swissgrid and Terna. In the event of schedule differences, an Anomaly Report is sent to the BGM concerned. Schedule differences can be corrected by submitting a new Day-Ahead schedule message (process type A01). Coordinated schedule time series can no longer be changed in the Day-Ahead process. D-1 15:15: Settlement deadline: From this point in time onwards, Day-Ahead schedule messages for correcting schedule differences can no longer be submitted by the BGM. At the settlement deadline, all successfully coordinated day-ahead schedule messages are classified as «balanced». If schedule differences still exist, they are corrected according to the schedule difference rules.

22 Page 22 of 44 From D-1 15:15: After the settlement deadline and the possible application of the schedule difference rules, Intermediate Confirmation Reports are sent to the BGM. This means that the Day-Ahead schedule message is classified as «provisionally confirmed». From D-1 16:30: The control block operators carry out a grid security analysis on the basis of the provisionally confirmed Day-Ahead schedule messages. If congestion is detected, operational congestion management measures are initiated (e.g. Redispatch). 12 Intra-Day procedure 12.1 Intra-Day procedure for external trade on the Switzerland-Germany, Switzerland- Austria, Switzerland-France borders and internal trade for Standard Balance Groups Overview of Intra-Day procedure for Standard Balance Groups 0 Uhr RZ/RB Fahrplanabstimmung 16:30 D-1 Beginn Fahrplan- Abstimmung Z-45min Anmelde-/ Einigungsschluss Z-30min Fahrplanzeitreihen Intra-Day eingestellt Z jede volle Viertelstunde von 00:00 bis 23:45 Figure 9: Intra-Day procedure Schedule messages for the next day which are submitted after D-1 15:30 and schedule messages for the current day are managed using the Intra-Day procedure The submission deadline for schedule messages submitted to Swissgrid using the Intra-Day procedure is 45 minutes prior to the time (Z) at which a modification or a resubmission is supposed to become effective. This time (Z) can be any full 15-minute period. Any schedule messages received after that time (Z-45) are rejected In addition to the modified or new schedule time series, Intra-Day schedule messages always contain all schedule time series relating to the current day which have already been submitted They cover the whole day (D 0.00 to 24.00) Intra-Day schedule messages are submitted with process type A02, the same message ID as Day-Ahead and sequential versioning. Schedule coordination takes account of all schedule time series from the time (Z) until the end of the day and is confirmed with an Intermediate Confirmation Report. An Anomaly Report is sent to any BGM whose schedule message contains schedule differences. If schedule differences still exist after the settlement deadline, the schedule difference rules are applied A congestion check is performed by Swissgrid after each schedule coordination. Congestion measures can be ordered by Swissgrid if necessary.

23 Page 23 of Details of Intra-Day procedure for Standard Balance Groups Zeit TPS ACK TPS BG swissgrid RB CH ÜNB BG z 45 Min z 30 Min CAS ACK CAS CAS ACK CAS INT CNF TPS CAX ACK CAX Anmeldeschluss TPS Einigungsschluss TPS Anmeldeschluss CAX z = 23:45 Ende Intra-Day Fahrplanabstimmung Figure 10: Intra-Day procedure (external trade) Figure 10 shows the steps necessary for successful coordination in the Intra-Day procedure (without discrepancies or corrective measures). Day preceding the day on which the schedule message is executed (D-1): Until D-1 15:30: Intra-Day schedule messages submitted before D-1 15:30 (process type A02) are rejected by means of a negative acknowledgement (Reason Code A02, Date must be today/tomorrow for Process type A02). From D-1 15:30: No Intra-Day schedule messages for the following day are processed for the duration of the Day-Ahead schedule coordination between Swissgrid and the TSOs in the neighbouring control areas. If such schedule messages are received, they are read into the balance group system but not processed until schedule coordination is complete. From D-1 16:30: Until Z-45: Start of Intra-Day schedule coordination for the following day. The procedure described below is repeated every full quarter of an hour up until the latest time at which an Intra-Day schedule message can be successfully submitted (16:30 (D-1) to 23:00 (D)). Intra-Day schedule messages submitted by the BGM must be received by Swissgrid no later than 45 minutes before the time at which the schedule message is to be executed. The submission deadline for a new or modified Intra-Day schedule message which is supposed to become effective at 00:00 (D) is therefore 23:15 (D-1). The submission phase is followed by the schedule coordination phase. Once schedule coordination is complete, the coordination results are sent to the BGM (Anomaly Report, Intermediate Confirmation Report). The Anomaly Report notifies the BGM concerned of any schedule differences. The BGM may submit a new schedule message up to the submission deadline for the purpose of correcting schedule differences.

24 Page 24 of 44 Z-45 Submission deadline and settlement deadline for intra-day schedule messages. From Z-45 Start of schedule coordination for all remaining schedule time units in the current day starting at the time (Z). Following schedule coordination, an Intermediate Confirmation Report is sent to the BGM. The Anomaly Report is used by Swissgrid to notify the BGM concerned of any schedule differences. As a result of this report, the schedule message submitted by the BGM is either rejected or adapted according to the schedule difference rules. The BGM is given an opportunity to submit a suitably corrected schedule message before the next change time. Z-30 Completion of schedule coordination for the time (T). D 23:00 Latest possible submission deadline and settlement deadline for Intra-Day schedule messages relating to the current day (for the 15-minute period from D 23:45 to 24:00). Additional anomaly check: 15 minutes after receipt of a schedule message a check is made to see if the counterpart schedule is in place. An anomaly report is sent to the submitter of the schedule and the relevant counterpart if necessary. Z-65 Check to see if the counterpart schedule has been received and possible dispatch of an anomaly report to the submitter of the schedule and also to the missing counterpart if necessary. Z-45 Check to see if the counterpart schedule has been received and possible dispatch of an anomaly report to the submitter of the schedule and also to the missing counterpart if necessary Intra-Day procedure for external trade at the Switzerland-Italy border for Standard Balance Groups Overview of Intra-Day procedure At the Switzerland-Italy border free capacity is allocated by JAO in two Intra-Day capacity allocations (the first on Day D-1 between 15:40-15:55 -> XBID1, and the second on Day D between 10:25-10:40 -> XBID2) based on explicit auctions with a marginal price. For more information on how to register and the respective Intra-Day auction rules, please visit The following diagrams illustrate the process schematically:

25 Page 25 of 44 Figure 11: Intra-Day procedure Switzerland-Italy (D-1 process) Figure 12: Intra-Day procedure Switzerland-Italy (D process) In which MI 2-4 refer to Mercato Infragiornaliero 2-4 in Italy

26 Page 26 of Details of Intra-Day procedure Intra-Day schedule messages are submitted to Swissgrid and to Terna. Schedule messages for the next day submitted to Terna and to Swissgrid after 16:30 and schedule messages for the current day are managed via the Intra-Day procedure. The deadline for submitting schedule messages in the Intra-Day procedure is the first Intra-Day auction at 17:30 D-1 (0:00-24:00) and the second Intra-Day auction at 12:30 on Day D (16:00-24:00). Afterwards Swissgrid and Terna perform a 30 minutes Correction Cycle. In case of a mismatch the nomination at Terna prevails. Submissions to Terna must be made in accordance with the provisions of the currently applicable Italian Dispatching Contract Intra-Day procedure for external trade on the Switzerland-Germany, Switzerland- Austria, Switzerland-France borders and internal trade for Control Balance Group and CH-15 Balance Groups Overview of Intra-Day procedure for Control Balance Groups and CH-15 Balance Groups External Trades are only possible for Control Balance Groups. 0 Uhr Control area comparison Z-15min Schedule deadline Z-5min Short-term schedules set Z Every ¼ hour Figure 13: Intra-Day procedure In principle, intra-day schedule messages are subject to the same rules as standard balance groups, apart from the fact that the schedules have to be delivered to Swissgrid only 15 minutes before the message deadline instead of at least 45 minutes. Detailed information can be found in the separate Documents Control balance group subcontract and CH- 15 balance group subcontract, available on the Swissgrid website ( The defined deadlines for the schedules of the control and CH-15 balance groups can in the case of redispatch set by Swissgrid to 30 minutes. The relevant balance groups will be informed immediately by Swissgrid (prior to the redispatch).

27 Page 27 of Post Scheduling Adjustments 0 Uhr 24:00 D Ende Intra Day 00:00 D+1 Beginn Post Scheduling Adjustment laufend Abstimmung eintreffender Fahrpläne 17:00 D+x Ende Post Scheduling Adjustment am nächsten Arbeitstag Figure 14: Post Scheduling Adjustments 13.1 Overview of post scheduling adjustments Internal schedules can be changed or re-registered up to 17:00 on the working day following the schedule day. Swissgrid publishes applicable holidays on its website, with exact definitions of the working days (D+x) and hence the post scheduling settlement deadline. Changes and re-registrations of schedules on the following working day take place with the process type A13 (post scheduling adjustment), with the same message ID as Day-Ahead and Intra-Day and sequential versioning. In addition to the changed and new internal time series, subsequent changes to the schedule always contain each of the time series already submitted for the balance group in Day-Ahead and Intra-Day. They cover the entire schedule day (00:00 24:00) and all internal and external time series. The values of the external time series must correspond to the last coordinated version in the Day-Ahead and/or Intra-Day process, otherwise the entire message will be rejected with Reason Code A02 «Message fully rejected. All the positions for the schedule days (previous day and preceding weekend and/or holidays) are continually coordinated. BGMs receive an anomaly on their schedule message if at the schedule deadline schedule differences exist between the schedule time series of the BGM and the corresponding schedule time series. Time series with discrepancies are rejected immediately if the settlement deadline is reached. The difference rules in chapter 9 apply.

28 Page 28 of 44 Submission procedure for post scheduling adjustment Messages can be submitted at any time after the end of the schedule day prior to the Post Scheduling Adjustment submission deadline and are formally examined immediately (ACK). They are coordinated as soon as the counterpart schedule is received. The BGM receives an ICNF Report and additionally an Anomaly Report in the case of value differences Details of post scheduling adjustment Zeit BG swissgrid BG D+1, 00:00 Start Post Scheduling Adjustments D+x, TPS ACK TPS INT CNF TPS F-CNF TPS Ende Post Scheduling Adjustments Final Confirmation Report Figure 15: Post scheduling adjustment (internal trade) Figure 15 shows the steps required for successful coordination in the post scheduling procedure (without discrepancies or corrective measures). Until 24:00 D: Messages submitted with the process type A13 before the end of the schedule day D are rejected. Coordination does not take place. From 00:00 D+1: Start of Post Scheduling Adjustment schedule check. Messages submitted with the process type A13 after the end of the schedule day D are accepted, formally examined and an ACK is sent. Until 17:00 D+x As soon as a comparison with the counterparty is possible, the entire position of the day is coordinated and the corresponding results dispatched (Intermediate Confirmation Report or Anomaly Report). The intermediate confirmation is used to supply information about the status of the schedule message to the BGM. The anomaly reports are used by Swissgrid to inform the BGMs concerned in the event of schedule differences. In the Post Scheduling Adjustment process the entire schedule message is always either accepted or rejected. The BGMs can re-submit the corrected changes. Post Scheduling Adjustment schedule changes by the BGM must be received before the submission deadline on the first working day after the schedule day D. 17:00 D+x Submission and settlement deadline for Post Scheduling Adjustment schedule changes from the BGM to Swissgrid (TPS).

29 Page 29 of 44 After 17:00 D+x Other anomalies: From 00:00 D+1 If schedule differences exist after the submission deadline, the schedule difference rules apply. Swissgrid sends a Final Confirmation to the BGMs (on working days). The BGMs are thus informed about their executed, billing-related schedule time series. 15 minutes after receipt of a schedule message a check is made to see if the counterpart schedule is in place. An anomaly report is sent to the submitter of the schedule and also to the missing counterpart if necessary. 14 Status Request In the processing of the status request are two roles involved: - an active role, which sends the status request (BGM) - an passive role, which receives the status request and answers (Swissgrid) Swissgrid is always in the passive role and answers the status requests from the BGM. Every BGM can send a status request. The status request will be answered as fast as possible, taking into consideration the priority of the processing of TPS. BGR (active role) Swissgrid (passiv role) Formally correct? Yes No Send negative ACK No - content correct AND - TPS available AND - first Matching done AND - request before deadline Yes Send CNF / ANO Figure 16: schema of status request