ESBI Workshop on OC October 9th-10th 2000

1. ESBI Workshop on OC October 9th-10th 2000 Presenters John Kennedy & Meadhbh Flynn

2. ESBI Workshop on OC October 2000 Agenda for the next two days Using the User Guide to Grid Code we will make presentations covering • General Conditions • Connection Conditions • Planning Conditions and Planning Code Appendix • Operating Codes 1-13 • Special Dispatch Codes1-3 and Appendix • Glossary

3. ESBI Workshop on OC October 2000 The Format of the Presentations • Users Guide • Construct Flowchart of actions and events • “Breakout Groups” - to discuss issues and make changes • Use of flipcharts to capture unanswered questions and suggested changes • Role play of events to achieve better understanding • Plenty of time for Questions and Answers • A short post-workshop report will issue to tie-up outstanding issues

5. Purpose of Operating Code • Fundamentally a technical document containing the Rules governing the Operation, Maintenance, and development of the Transmission System • Gives Users an understanding of the Rules and provides for equitable treatment for all. • It refers to documents that are not part of the Operating Code e.g. transmission planning criteria, operating policies, interconnection • It does not address commercial issues - penalties -violations -failure of services • These are dealt with in other agreements

6. Hierarchy of documents

7. Precedence of Definitions • Importance of common understanding • Hence a Glossary is included • If a Term is Defined in the Operating Code it will take precedence over the definition in the Glossary

8. Governance • The Operating Code is a “living” document - it is subject to changes • Approved by RAE -brings it into being • Modifications, Updates, Derogation requests, will be approved by REA - keeping it alive

9. General Conditions • Makes provision for rules of a more general nature making a cohesive document allowing the operation of the transmission System for the benefit of all • Requirement of HTSO to establish and maintain the OCRP • Allows derogation rather than changes to design specifications • General Conditions requires users to comply with the”letter & spirit” of the code and provides HTSO with its rights • HTSO will act reasonably - “Prudent Utility Practice” It should be noted that if there a conflict between Operating Code and any other agreement the provisions of the Operating Code will prevail • If parts of the Operating Code unlawful/invalid the validity of all remaining provisions will not be affected

10. Connection Conditions • To protect plant certain minimum criteria are met - technical - design - operational • These are defined in Connection Conditions • This is to allow stable, secure operation of the transmission system • Compliance required from all users • Performance of the transmission system at the connection point to enable new users to design their equipment • For existing plant derogation will be through REA

11. CC Overall Structure

12. Planning Code • Planning code is necessary to allow development of the transmission system - demand growth - new connection - development of existing facilities • Planning code allows HTSO/User interaction covers - performance impacts on either side - information requirements of HTSO to allow it plan according to criteria and standards - Prepare Forecast statement

13. User accepts offer? Complex Connection? Planning Code- Outline of application procedure HTSO publishes Forecast Statement and Use of System Tariffs User applies to HTSO for connection HTSO sends Connection Offer to User User sends Preliminary Project Planning Data to HTSO Yes HTSO carries out further analyses HTSO requests more data from User No HTSO sends revised Connection Offer to User Connection Offer lapses if unaccepted by User before Connection Offer Expiry Date No Yes HTSO and User signs Connection Agreement User sends Committed Project Planning Data to HTSO within 60 days

14. Operating Codes (OC)

15. OC1 Safety Co-Ordination • “Safety First” and so it is with the Operating Code OC1 • Establishes the requirement of HMSO (or agents) as well as users ( or agents) to operate in accordance with approved Safety Rules. It is assumed that PPC’s will apply to everyone • Other rules allowable if complying with all national/international and legal requirements • Applies to interconnected systems

16. OC2 Information Exchange • This Code deals with - notification of event and event reporting - operational communication an data retention • Pre-connection communication is covered under Connection Conditions

17. All Users Generators DSO Grid Connected Customer HTSO OC2- Overall structure

18. OC3 Metering Code • For settlement purposes imported and exported MWh and MVArh are measured at defined points • OC3 specifies the minimum technical, design and operational criteria for metering and data collection • The Settlement System provides for payments due • Metering is provided by HTSO and DSO and will be registered in an appropriate system

19. OC 4 Demand Forecasting • Demand forecasting will be required over different time scales - Operational Planning - Programming - Control - Post Control • Exact HTSO responsibilities yet to be determined • Anyway will require typical profiles from DSO for defined categories of day type. HTSO will define these day types • Unnecessary duplication can be avoided by using information delivered under SD1 for centrally dispatched and embedded generation • Pumped storage generation treated as negative generation • Possible agreements required with external TSOs

20. OC4 Summary of information needed

21. OC4 Information for Demand Forecast Post Control Phase Operational Planning Phase User Information User Information Transmission losses System Events Historic Data HTSO conducts demand forecasting User Other information information Programming Phase Control Phase User Information User Information

22. OC5 Demand Control • Operator must feel comfortable with methods employed in Demand Control - Empowered to act • The operator should have extensive knowledge of control methods and act quickly in emergencies and if necessary break the rules if needed • Mainly DSO will act on behalf TSO - contact between suppliers and customers will need to reflect the necessity of demand control • There may be tariff arrangement that allow for a higher risk of disconnection • Exemptions - need arrangements in place

23. OC5 Overall structure

24. OC5 Demand Control Provision will be made for - Customer Demand reduction instructed by HTSO - Automatic low frequency demand disconnection - Automatic low voltage demand reduction - Automatic Demand Restoration

25. OC6 System Services • System services for network control and operation now more formalised (payments and measurements) • HTSO will manage these services and will specify what services will be provided and by whom • Generator licences must have a requirement to provide certain services on reasonable terms • Services include - Frequency control Voltage control Network control Operating Margin and Power System Restoration

26. OC7 Interconector Management • Interconnector management is part of prudent system control • OC 7 facilitates secure trading with neighbouring utilities • Trading planned over three day time frame requiring posting of Available Transmission Capacity (ATC) and then allowing Independent and Franchise sectors access • Reserve sharing and restoration services should be covered by bilateral agreements

27. OC7 Summary of procedure

28. OC8 Generator Maintenance Scheduling • The role of HTSO not clear yet in the new environment - will still have to produce a Transmission outage Programme - maintain capacity adequacy - ensure system security - Areas of special constraints - produce timely information to market participants

29. OC8 Generator Maintenance Scheduling • Schedule time frames 1- 5 years - Indicative Outage Programme (4 -5 years) - Provisional Outage Programme (2 - 3 years) - Committed Outage Programme (year 1) • HTSO approves outages from a security point of view • Obligation on Generators to move outages • Need to develop mechanisms for dispute resolution

30. OC8 Summary

31. OC8- Procedure when HTSO requests change to COP HTSO requests Generator to change COP Generator agrees subject to conditions Generator has reasonable case for declining request Generator agrees HTSO accepts conditions HTSO does not accept conditions Amend COP COP not amended

32. OC8- Procedure when Generator requests change to COP Generator prepares new proposal for change to COP Generator requests change to COP Capacity adequacy not OK HTSO and Generator discuss modification to Generators proposal HTSO evaluates effect on Capacity Adequacy HTSO informs Generator No amendment to Generator's proposal Capacity adequacy OK Generator takes forced outage for unit Generator makes change to Declaration of Availability COP not amended Amend COP

33. OC9 Transmission Maintenance Scheduling • Maintenance year runs from July 1st- June 30th • Schedule time frames 1- 5 years - Indicative Transmission Outage Schedule (3 -5 years) - Provisional Transmission Outage Schedule (year 2) - Committed Transmission Outage Schedule (year 1)

34. OC9 Transmission Maintenance Scheduling • First Business Day of July, TO gives HTSO: • the CMPR for Maintenance Year 1 (MY+1) • the PMPR for Year MY+2 • the IMPR for MY+3 to MY+5. • the start date and time and the duration of each Outage. • TO should avoid a situation arising in which the TO is obliged to schedule an Outage at short notice • In rolling over the Transmission Outage Programme Requirements from one year to the next TO shall not be constrained in making any submission by any previous IMPR. • 1 July - 31 August of MY, HTSO does security analysis of MY+1 to MY+5 in light of proposed Outages and other relevant matters including Outages of Generation Units, Interconnection and load growth. • HTSO will highlight any concerns with the Transmission Outage ProgrammeRequirements to TO by the end August in MY. • 31 Aug - 30 Sept: HTSO and TO discuss any concerns

35. OC9 Transmission Maintenance Scheduling • The HTSO shall issue to TO a Transmission Outage Schedule for Maintenance Year MY+1 to Maintenance Year MY+5 by the fifth (5th) Business Day of November in Maintenance Year MY, comprising • the Committed Transmission Outage Schedule (CTOS) for Maintenance Year MY+1 • the Provisional Outage Schedule (POS) for Maintenance Year MY+2 • the Indicative Outage Schedules (IOS) for Maintenance Years MY+3 to MY+5.

36. OC9 Overview

37. OC9 Outline procedure

38. OC9 Outline procedure

39. OC10 Monitoring Testing and Investigating • For HTSO to discharge its duties for safe secure and economic operation there is a need to carry out monitoring testing and Investigation of User’s Plant • HTSO is to ensure compliance with Operating Code and needs to establish agreed procedures separate from the Operating Code • OC10 does not apply to Operational testing but check that users are within their design, operating and connection requirements • Methods to deal with disputes are required

40. OC11 Operational Testing • Covers responsibilities and procedures to arrange and carry out Operational Tests - these test can affect HTSO and Users • Central co-ordination required since there will be implications foe security quality continuity and economic operation • Tests required by HTSO or Users - Requesting - Evaluation - Approval - Scheduling - Dispatching - Reporting - Disputes

41. OC11 Summary part 1 of 2

42. OC11 Summary Part 2 of 2

43. OC12 Emergency Control and Power System Restoration • OC12 is to ensure that after a partial or total system collapse normal supply is restored to all customers quickly and safely • Generator licences include a provision to offer black start capability to HTSO ( this can be tested under OC10) • Various proposed System Alerts are presented • An up to date Power System Restoration Plan is Required

44. OC12 Emergency Control and Power System Restoration

45. OC13 Small Scale Generator Conditions • Small scale generation is defined by HTSO as less than 5MW for a single site • Some sections of Operating Code do not apply • Some important codes still apply like OC8 Operational Planning. Here the HTSO needs information like seasonal load factors and running patterns. • OC13 deals with • Outage Scheduling - Changes to the Committed programme - information to be notified • Network control

46. Scheduling and Dispatch Codes SDC Codes

47. SDC1 Generation Scheduling • HTSO obligation to to schedule and dispatch generation • HTSO requires accurate and timely information relating to generation and supply • SDC1 specifies procedures for issuing a generation schedule for a trading day and Demand forecast • Thus generator receive an indicative dispatch for the following day and thus be available for operation • HTSO maintains an operating margin desired flows on interconnections

48. SDC1 Generation Scheduling • General Requirements - Demand Forecast - Declarations by Generators - Daily Nominations - Communication of Declarations - Communication of Daily Nominations - ATC for interconnections - Production of Generation Schedule (GS) - Procedure in absence of a daily nomination

49. SDC1 Generation Scheduling SDC1.4 The HTSO publishes demand forecast for next dispatch day by 11.00 SDC1.5-1.6 SDC1.8 Generators Exporting send Purchasers Declarations send and Daily Nominations Offers for next for next Dispatch Day by 12.00 Dispatch Day by 12.00. SDC1.10 The HTSO issues SDC1.10 The HTSO produces provisional running orders and schedule between 13.00 and publishes forecast system 16.00 for next dispatch day marginal price for each dispatch hour of next dispatch day

50. SDC2 Generation Dispatching • HTSO licence obligation to dispatch generation to meet demand • A structured process is required • SDC2 details the process to be used by HTSO decides the generation dispatch using the generation scheduled provided • HTSO procedure for communicating dispatch instructions - some details will depend on Market protocols