ESBI Workshop on OC October 9th-10th 2000

INTERNATIONAL DRAFTDRAFT

ESBI Workshop on OC October 9th-10th 2000

Presenters John Kennedy & Meadhbh Flynn


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


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


HTSO DSOTransmission Owner (PPC)

Suppliers CDGUs Non CDGUSmall Scale

Generators

Special Units

External System Operator

GC General Conditions b b b b b b b b r

CC Connection Conditions b b b r b b b b r

PC Planning Code b b b b b b b b r

OC1 Safety Co-ordination b b b b b b b b r

OC2 Information Exchange b b b r b b b b r

OC3 Metering Code b b b b b b b b bOC4 Demand Forecasts b b r b b r r b r

OC5 Demand Control b b r b r r r r r

OC6 System Services b b r b b >2MW r b r

OC7 Interconnector Management b b b b b r r b bOC8 Generator Maintenance Scheduling b b r b b r r b r

OC9 Transmission Maintenance Scheduling b r b r r r r r r

OC10 Monitoring, Testing and Investigation b b b b b >10MW b b r

OC11 Operational Testing b b b r b >2MW r b r

OC12 Emergency Control & Power System Restoration b b b r b >2MW r b r

OC13 Small Scale Generator Conditions b r r r r b b b r

SDC1 Generator Scheduling b b r b r r r b bSDC2 Generator Dispatch b b r b r r r b bSDC3 Special Scheduling Provisions b r r r r r r b r

Glossary b b b b b b b b b

Code


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


Hierarchy of documents

SafetyRules

UCTEStandards

GreekStandards

Standards

TransmissionPlanningCriteria

Reserve Policy

Policies

Operating CodeCompliance

Test

Power SystemRestorationProcedure

Procedures

Otherdocumentation

OperatingCode

Licences

Legislation

AncillaryServices

Agreements

PowerExchange

Code


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


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


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


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


CC Overall Structure

T ran sm iss ionS ys te m P e rfo rm a n ce

H T S OC C .8

T ra n sm iss ionC o m p ou nd

C C .4

P la n tD e s ig na tio ns

C C .5

G e ne ra ls ta n da rds

C C .6

C C 7 .1 -2E a rth in g ,L o ck in g ,

D e s ig n , C a b ling / w iring G rid C o nn e c te d Tra fos

C C 7 .3G e n era to rs

M in . p e rfom an ce sta n da rdsR e serve , R e a ctive po w e r, e tc.

S p e c if ics ta n da rds

C C .7

C C 1 0 .1 -8 C C 1 0 .9G e n era to rs

C C 10 .10D S O

C C 10 .11G C C

C C 1 0.1 -11U se r P ro te c tion

C C 10 .12Q u a lity

P ro tec tio n / Q u a lityC C .10

S ig n a ls

C C .12

P o w er S u pp lies

C C .13

S tan d ardsfo r Users ' Plant

M eter ingC C .9 a n d M ete ring

C o de

C o m m un icationC C .1 1 a n d O C .2

S afe tyC C .14 an d O C 11

C o m m iss ion ingC C .15

C O N N EC TIO N C O N D ITIO N S


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


Planning Code- Outline of application procedure

Complex Connection?

User applies to HTSO for connection

HTSO sends Connection Offer to User

HTSO requests more data from User

User sends Preliminary

Project Planning Data to HTSO

HTSO carries out further analyses

HTSO sends revised Connection Offer to User

User accepts offer?

User sends Committed Project Planning Data to HTSO within 60 days

HTSO and User signs Connection Agreement

Yes

HTSO publishes Forecast Statement and Use of System Tariffs

Yes

Connection Offer lapses if unaccepted

by User before Connection Offer

Expiry Date

No

No


Operating Codes (OC)


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


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


OC2- Overall structure

N o tif ica tionO C 2.1 .5

F o rmo f N o tif ica tion

O C 2.1 .6

R e cord ingO C 2.1 .7

T im in gO C 2.1 .8

O p e ra tio nsO C 2.1 .4 -8

N o tif ica tionO C 2.1 .9

F o rm o f N o tifica t ion

O C 2.1 .10

P ro v is iono f fu rth e r

In fo rm ationO C 2.1 .11

R e cord ingO C 2.1 .12

T im in gO C 2.1 .13

E v en tsO C 7.1 .4 ;

O C 2.1 .9 -13

N o tifica tio n ofE ven ts & E ven t R ep o rting

O C 2 .1

H T S OO C2.2.4.1

G e n era to rsO C2.2.4.2

G ridC o nn ec tedC u s to m e rs

O C2.2.4.3

D S O

O C2.2.4.4

C o n ta c t Lo ca tio nsO C 2.2 .4

C o m m u n ica tionF a c ilit ie sO C 2.2 .5

C o m m u n ica tionb e tw e en

H T S O & U serO C 2.2 .6

D a ta & N o ticesO C 2.2 .7

D a ta R e te n tionO C 2.2 .8

O p era tion a l C o m m un ica tion& D ata R e ten tion

O C 2 .2

O C 2 IN FO R M ATIO N EXC H AN G E

All Users

Generators

DSO

Grid Connected Customer

HTSO


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


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


OC4 Summary of information needed

Phase Programming Control Post ControlTime relative to Dispatch Dayfor which information required

Year ahead (Year +1) 2 weeks - 8 weeks ahead 2 days -12 days ahead 1 day ahead Day following dispatch day

Time for submitting information Week 22 of Year 0 10.00 each Tuesday 11.00 each Thursday 10.00 each day 08.00 each dayDSO

Demand at Supply points Hourly Hourly Hourly Hourly HourlyAnticpated demand control >10MW Hourly Hourly Hourly Hourly HourlyMW profiles for embeddedgeneration units > 10MW Daily Hourly Hourly Hourly HourlyMW profiles for embedded generation sites > 5MW Weekly Daily Daily Hourly HourlyMW profiles for criticalembedded generation sites >2MW Weekly Daily Daily Hourly Hourly

Suppliers:Demand at Supply points Hourly Hourly Hourly Hourly HourlyAnticpated demand control >10MW Hourly Hourly Hourly Hourly Hourly

Interconnector HourlyGenerators Hourly

Operational Planning


OC4 Information for Demand Forecast

Operational Planning PhaseUser Information

Post Control PhaseUser Information

HTSO conductsdemand forecasting

Historic Data

Userinformation

Transmission losses

System Events

Otherinformation

Programming PhaseUser Information

Control PhaseUser Information


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


OC5 Overall structure

Rota LoadShedding Plan

(If suffic ientnotice)

AlternativePlan

(If insufficientnotice)

ESBNG InstructedDem andControlOC5.4

Autom atic LowFrequency Dem and

DisconnectionOC5.5

Autom aticFrequancy

RestorationOC5.6

Autom atic LowVoltage Dem andDisconnection

OC5.7

Dem and Control


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


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


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


OC7 Summary of procedure

USER

HTSO

ATC determinationCalculate Total

Transfer Capabilityand TransmissionReliability Margin

before 16.00(in consultation with

relevant ExternalSystem Operator

Independent sectoraccess

Submit request forinterconnector access

before 11.00

Franchise sectoraccess

Remaining Capacitymay be used to

trading on behalf ofGreek franchise

market

ExternalSystem

Operator

Independentsector access

Process allpreviously

granted requestsfor

interconnectoraccess

D-2D-3 D-1

ATC postingPost TotalTransfer

Capability andTransmission

Reliability Marginon web before

17.00

Independentsector access

Respond torequest for

interconnectoraccess before

14.00

Independent sectortrading

Submit schedules forinterconnector trades to

HTSO before 10.00

Independent sectortrading

Process interconnectortrades received before

14.00

Independentsector trading

Prepareinterconnector

transferschedule

InterchangeScheduleManage

interchangeschedule so thatinterconnector

transfer scheduleis met ahead of

franchise markettrading

InterchangeSchedule

Co-ordinatewith External

SystemOperator insetting finalinterchange

schedule

SDC1 andSDC2

Schedulingand

dispatch

Userfollows

schedulingand

dispatchinstructions


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


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


OC8 Summary

C o m m itted O u ta ge P ro g ram m eY e a r 1

P ro vis io na l O u ta ge P ro g ram m eY e a rs 2 -3

In d ica tive O uta g e P rog ram m eY e a rs 4 -5

Generator Outage Program meYears 1-5


OC8- Procedure when HTSO requests change to COP

HTSO requests Generator to change COP

Amend COP COP not amended

Generator agrees Generator has reasonable case for declining request

HTSO accepts conditions

HTSO does not accept conditions

Generator agrees subject to conditions


OC8- Procedure when Generator requests change to COP

Amend COP

Cap

acity

ad

equ

acy

OK

No

amen

dmen

t to

G

ener

ator

's

prop

osal

HTSO evaluates effect on Capacity

Adequacy

Capacity adequacy not

OK

Generator prepares new proposal for change to COPGenerator requests change to COP

Generator takes forced

outage for unit

HTSO and Generator discuss modification

to Generators proposal

HTSO informs Generator

COP not amendedGenerator makes

change to Declaration of

Availability


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)


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 Programme Requirements to TO by the end August in MY.

31 Aug - 30 Sept: HTSO and TO discuss any concerns


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.


OC9 Overview

C o m m itted T ran sm iss ion O uta g e S che d u leY e a r 1

P ro v isio n a l T ra nsm issio n O u ta ge S che d u leY e a rs 2

In d ica tive T ran sm iss io n O uta g e S che d u leY e a rs 3 -5

Transm ission Outage SchedlueYears 1-5


OC9 Outline procedure

TO SubmitsMaintenanceProgrammeRequirements

HTSO MonitorRequirements

HTSO studyrequirements Feasible

ScheduleAvailable

Produce firmschedule

HTSOPropose

Alternatives

ScheduleAdministrator

Yes

No

TO ReviewSchedule

TO agreesschedule

CloseAgreement

TO does notagree

schedule

TO RevisesRequirements

Agree

Disagree

Arbitration possible following first iteration

Next Page


OC9 Outline procedure

Previous

Page

HTSOProposealternatives

Presentalternatives to

TO

TO judgesalternativesare feasible

Agree andClose

TO judgeSalternatives

are infeasible

TO ProposesAlternatives

HTSOReceivesproposal

HTSOevaluatesproposal

Accept TOproposed

alternatives

TO proposedalternatives

not acceptable

HTSOPropose

AlternativesSuggest to

TO

TO Accept Close and end

TO proposealternatives

HTSO imposesolution

HTSOevaluatesProposal


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


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


OC11 Summary part 1 of 2

TESTPROPOSER

HTSO

OPERATIONALLYAFFECTED

USERS

RAE

OC11.6 Request Operational TestSubmit proposal to HTSO in line with OC2

OC11.7 Evaluaterequest for

operational testAdvise Operationally

Affected Users

OC11.7.2 Request for OperationalTest

Assess impact on system and users

OC 11.8 Approval forOperational TestReject or accept

Accept

OC11.5 Test required by User Draw up Test Proposal

OC11.4 Test requiredby HTSO

Draw up test proposal

OC11.7.2 Evaluate request foroperational testAssess impact

Reject


OC11 Summary Part 2 of 2

TESTPROPOSER

HTSO

OPERATIONALLYAFFECTED USERS

RAE

OC 11.8.3 Approvalfor Operational Test

Send proposeddispatch procedure

and schedule for testto test proposer and

operationally affectedusers

OC11.8.3.1Approval forOperational

TestAccept or reject

proposeddispatch

procedure &schedule for test

OC 11.8.3.3Approval forOperational

TestNotify

operationallyaffected users ofacceptance bytest proposer

OC11.8.3.1Approval forOperational

TestNotify HTSO

of acceptance

Accept

OC11.9Schedule

OperationalTest

Send offer toHTSO for test

in line withSDC1

OC11.10Dispatch

OperationalTest

Follow dispatchinstructions fortest ( SDC2)

OC11.10Dispatch

OperationalTest

Dispatchinstructions totest proposerfor test in line

with SDC2

OC11.11Test

ReportingSend toHTSO

OC11.10.3 DispatchOperational Test

Cancellation of test forsystem reasons by HTSO

OC 11.8.3.4Approval for

Operational TestAssess impact-

appeal to HTSO ifunacceptable

OC 11.8.3.4 Approval for OperationalTest

Assess if operationally affected usershave reasonable grounds for rejection of

proposed test

OC11.12 Approval forOperational Test

Appeal to RAE

OC11.12 Disputesresolution

Reject

No

OC 11.8.4Approval

forOperational

TestReject Test& notify Test

ProposerYes

Reject(from Fig 13)

OC 11.8.4 Approval forOperational Test

Amend proposal or appeal to RAE

App

eal t

o R

AE

Amend

OC 11.8.3.3Approval for

Operational TestDiscuss alternative

with HTSO

Reject

OC11.10.3 DispatchOperational Test

Discuss revised Test with TestProposer

Accept(from Fig 13)


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


OC12 Emergency Control and Power System Restoration

A m b er R ed B lue

S ys te m A le rtsO C 1 2 .4

P o w e r S ys temR e s tora tion

O C 1 2 .5

D e -e ne rg isa tiono f U se r's P la n t

b y H T S OO C 1 2 .6

E m erg en cy C on trol& Po w er S ys tem

R esto rationO C 12


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


Scheduling and Dispatch Codes

SDC Codes


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



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



SDC1.4

The HTSO publishesdemand forecast for next

dispatch day by 11.00

SDC1.5-1.6Generators

sendDeclarations

and DailyOffers for nextDispatch Day by 12.00

SDC1.8Exporting

Purchaserssend

Nominationsfor next

Dispatch Dayby 12.00.

SDC1.10

The HTSO producesschedule between 13.00 and16.00 for next dispatch day

SDC1.10

The HTSO issuesprovisional running orders and

publishes forecast systemmarginal price for each dispatch

hour of next dispatch day


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


SDC2 Summary

The HTSO forecasts Demand, sets reserve level and agrees ATC on interconnectors with External System Operators. HTSO issues dispatch instructions up to real time

The HTSO issues dispatch instructions up to real time

Accepted by

Gen?

Inform HTSO-must be for safety or

emergency reasons

Yes

No

Synchronising, desynchronising

times

Active Power Dispatch

System Alerts

Instruction in line with

operating characteristics? Inform HTSO

No

Revise

instruction

Reactive Power

Dispatch

System Emergency Conditions

Operating Mode

Dispatch


SDC2 Dispatch Instructions: Synchronise/ desynchronise

Yes

Synchronising , desynchronising times

Can synchronise within 10 mins.

instructed time?

Synchronise

Effective redeclaration

Can synchronise between 10 mins.

& 4 hrs. instructed time?

Issue redeclaration Yes

No

No


SDC2 Dispatch Instructions: Active power, reactive power and operating mode dispatch

Active Power Dispatch

Achieve dispatch level within allowable tolerance

consistent with Declarations

Inform HTSO without delay if problem arises

Reactive Power Dispatch Operating Mode Dispatch

Change operating mode consistent with Declarations


SDC2 Dispatch Instructions: Emergency

Emergency Instruction

Instruction may be outside Declared characteristics. Generator must comply

except for safety reasons

Inform HTSO without delay if problem arises


SDC3 Special Scheduling Provisions

SDC3 is to describe procedures to be adhered to by Users in defined special cases. – Congestion relief– Irrigation constraints– Minimum demand provisions– Renewable generation– Indigenous generation units– Hydro dispatch groups

Process for issuing instructions pursuant to SDC3 shall be in accordance with the provisions of SDC1 and SDC2.

Provisions of SDC3 do not supersede the provisions in SDC1 and SDC2.


SDC3 Irrigation Constraints

Unconditional must-run output for each dispatch hour

Availability for each dispatch hour

Generator givesnotice of constraintsby 10.00 day ahead

of dispatch day and specify::

IRRIGATIONCONSTRAINTS

Maximum and minimum available energy for dispatch day

Schedule and dispatch - SDC1 & SDC2


SDC3 Hydro Dispatch Groups

Unconditional must-run output for each dispatch hour

Availability for each dispatch hour

Generator givesnotice of constraintsby 10.00 day ahead

of dispatch day and specify::

HYDRO DISPATCH GROUPCONSTRAINTS

Maximum and minimum available energy for dispatch day

Schedule and dispatch - SDC1 & SDC2

Generator must meet certain constraints to qualify as Hydro Dispatch Group


THE END

Thank you from Meadhbh & John

Date post:	12-Jan-2016
Category:	Documents
Upload:	taffy
View:	25 times
Download:	0 times

ESBI Workshop on OC October 9th-10th 2000

Documents