QSE/RE Transmission Facilities Outage Coordination Workshop.

QSE/RE TransmissionFacilities Outage

CoordinationWorkshop

Protocol Disclaimer

This presentation provides a general overview of the Texas Nodal Market Implementation and is not intended to be a substitute for the ERCOT Nodal Protocols, as amended from time to time. If any conflict exists between this presentation and the ERCOT Nodal Protocols, the ERCOT Nodal Protocols shall control in all respects.

For more information, please visit:

http://ercot.com

2

Antitrust Admonition

ERCOT strictly prohibits market participants and their employees who

are participating in ERCOT activities from using their participation in

ERCOT activities as a forum for engaging in practices or

communications that violate antitrust laws. The ERCOT Board has

approved guidelines for Members of ERCOT Committees,

subcommittees and working groups to be reviewed and followed by

each market participant attending ERCOT meetings.

3

This course is intended for:

• QSEs and REs who

submit Resource Entity-Owned

Transmission Facility outages

• TSPs, ERCOT Outage Coordinators

and outage coordination support

personnel

Target Audience

4

Course Topics

The following topics will be discussed:

•NPRR 219 Requirements•Protocol Definitions•Resource Entity-owned Transmission Facility examples•Protocol Requirements for Transmission Facility Outages•Resource Entity-owned Transmission Facilities Outage process•Protocol Requirements for Adding & Removing Facilities•Resource Entity Adding Equipment scenario

5

Outage Scheduler Training Material

Training material pertaining to the Outage Scheduler may currently be found at:

http://nodal.ercot.com/training/index.html

http://nodal.ercot.com/readiness/markettrials/os/index.html

Web-based training modules are also available on the ERCOT Learning Management System

6

NPRR 219 Requirements


• In accordance with Nodal Protocol Revision 219 ERCOT will submit information into the Nodal Outage Scheduler for Resources who own Transmission Facilities and are unable to submit this information into the ERCOT Outage Scheduler.

• This workshop addresses the Protocol requirements and the process which ERCOT will implement for collecting information and performing this task upon Nodal go-live December 1, 2010.

8

RE requirement to designate a Responsible Entity

• Each Resource Entity is to submit a Notice of Change of Information (NCI) specifying who will responsible for submitting outages on their behalf (designating ERCOT or a TSP).

• If a RE designates a specific TSP, the NCI Contact Type block is completed with the TSP Single Point of Contact.

• When the RE designates a TSP, the RE is required to acknowledge to ERCOT either:• A signed letter from the TSPs Authorized representative or• An email from the TSP Authorized representative acknowledging

the TSPs obligation.

• If a RE confirms ERCOT as the Resource Transmission Facility

Outage Coordination point of contact, the contact block does not need to be completed.

9

Protocol Definitions


Outage

The condition of a Transmission Facility or Generation Resource that is:

• part of the ERCOT Transmission Grid• defined in the Network Operations Model• has been removed from its normal service• excludes the operations of Transmission Facilities associated with

the start-up and shutdown of Generation Resources.

11


Transmission Element

A physical Transmission Facility that is either an Electrical Bus, line, transformer, generator, Load, breaker, switch, capacitor, reactor, phase shifter, or other similar device that is part of the ERCOT Transmission Grid and defined in the ERCOT Network Operations Model.

Transmission Facilities

(1) Power lines, substations, and associated facilities, operated at 60 kV or above, including radial lines operated at or above 60 kV;

(2) Substation facilities on the high voltage side of the transformer, in a substation where power is transformed from a voltage higher than 60 kV to a voltage lower than 60 kV or is transformed from a voltage lower than 60 kV to a voltage higher than 60 kV

12

Resource Entity-Owned Transmission Facility

Discussion

Ownership vs. Operatorship

Ownership • Physical ownership of equipment. There can be more than one

owner.

• Owners may submit model change requests.

14

Ownership vs. Operatorship

Operatorship• The entity responsible for physical operation of the equipment.

There can be more than one operator.• Operators may also submit model change requests. • REs and PUNs must identify the connecting TSP in their RARFs.• Currently, only TSP Operators can submit Transmission Facility

requests in the Outage Scheduler

15

Protocol Requirements

Protocol 3.1.4.3 Reporting for Planned Outages and Maintenance Outages of Resource andTransmission Facilities

• Each Resource Entity and TSP shall submit information regarding proposed Planned Outages and Maintenance Outages of Transmission Facilities or Generation Resources under procedures adopted by ERCOT.

• The obligation to submit that information applies to each Resource

Entity that is responsible to operate or maintain a Generation Resource that is part of or that affects the ERCOT System.

• The obligation to submit that information applies to each TSP or

Resource Entity that is responsible to operate or maintain Transmission Facilities that are part of or affect the ERCOT System.

23

Protocol 3.1.5.1 ERCOT Evaluation of Planned Outage and Maintenance Outage of Transmission Facilities

• TSPs and Resource Entities shall request a Planned Outage or Maintenance Outage for their respective Transmission Facilities (i.e. Transmission Facilities owned by such Entities) that are part of the ERCOT Transmission Grid and defined in the Network Operations Model.

• For Resource Entities within a Private Use Network, this only

includes Transmission Facilities at the Point of Interconnection (POI).

24


• Specifically, such requests shall be made when a relevant Transmission Facility will be removed from its normal service.

• For TSP requests, the TSPs shall enter such requests in the Outage

Scheduler.

• For Resource Entity requests, ERCOT* shall enter such requests in the Outage Scheduler on behalf of the Resource Entity.

* or a designated TSP

25


• ERCOT’s obligation to enter outage requests for Resource Entities is valid only for the purposes of Transmission Facilities Outage Scheduler entry requirements prescribed by the ERCOT Protocols and Operating Guides.

• ERCOT’s obligations hereunder do not create any legal obligation or

responsibility related to any other legal obligations applicable to a Resource Entity.

• ERCOT’s obligation shall terminate upon the implementation of system changes that enable Resource Entities to perform this function.

26


• ERCOT is not deemed to have approved the Outage Schedule

associated with the Planned Outage or Maintenance Outage until ERCOT notifies the TSP or Resource Entity of its approval under procedures adopted by ERCOT.

• Once ERCOT posts a Resource Entity Transmission Facility Outage request on the MIS Secure Area, the Resource Entity shall review the submitted Outage for accuracy and request that ERCOT submit modifications if necessary.

27

Resource Entity-Owned Transmission Facility Outage

Process


• In accordance with Nodal Protocol Revision 219 ERCOT will submit information into the Nodal Outage Scheduler for Resources who own Transmission Facilities and are unable to submit this information into the ERCOT Outage Scheduler.

• The following process has been developed by ERCOT for collecting information and performing this task upon Nodal go-live December 1, 2010.

29

RE-Owned Transmission Facility Process

Each Resource Entity that owns Transmission Elements, that is part of the ERCOT Transmission Grid and defined in the Network Operations Model that has been removed from its normal service, excluding the operation of Transmission Facilities associated with the start-up and shutdown of Generation Resources, must submit Planned, Maintenance and Forced outage schedules for ERCOT approval.

Note: the following process does not apply to QSEs/REs with a designated TSP. The designated TSP shall be the responsible entity.

30

RE-Owned Transmission Facilities

• QSEs/REs must coordinate activities with ERCOT or a designated TSP who will enter outages for these facilities.

31


1. The Resource Entity shall coordinate Transmission Facility outage request with its designated single point of contact (QSE) in accordance with Nodal Protocol 3.1.4.1 Single Point of Contact.

32


2. The Resources Entity’s QSE shall submit outage information to ERCOT staff by email using the “Trans Planned-Maintenance Outage Request Form” or the “Transmission Forced Outage Request Form” depending on the type of outage being requested.

The “Trans Planned-Maintenance Outage Request Form” and the “Transmission Forced Outage Request Form” are available on ERCOT.com at http://www.ercot.com/gridinfo/transmission/index .

This information should be emailed to [email protected] .

33

Outage Request Forms on ERCOT.Com

34

QSE/RE Planned Outages for Resources

Submittal Timelines for Resource Planned Outages

If QSE submits outage request…

ERCOT will approve or reject…

1-2 days prior Within 8 business hours of receipt*

3-8 days priorBefore 1800 hours, two days prior to start of proposed Outage

8+ days priorMust accept, but may discuss reliability and scheduling impacts to minimize hazards/costs

* Eight Hour Business Rule Applies

TSP/Transmission Facilities Planned Outages

Submittal Timelines for Planned Outages

If TSP submits outage request…

ERCOT will approve or reject…

91+ days* 75 days*

46–90 days* 30 days*

9–45 days* 4 days*

4–8 days* No later than 1800 hours 3 days*

3 days* No later than 1800 hours 2 days*

*Prior to Planned Start Date/Time

QSE & TSP Maintenance Outages

• Initiated manually to remove equipment from service to perform work on components

• Required to prevent a potential forced outage

• Could be postponed briefly

• Cannot be postponed until next planned outage

OutageLevels

Equipment must be removed from service…

1 Within 24 hours

2 Within 2 – 7 days

3 Within 8 – 30 days.

QSE Communication

If Maintenance Outage occurs:• QSE must update Current Operating Plans • Verbal communication with ERCOT may be necessary

Maintenance Outage

Planned and Maintenance Submittal Form

39

Replicates TSP Planned and Maintenance Outage Scheduler submittal format

QSE & TSP Forced Outages

• Initiated by protective relay (or manually)

• In response to equipment that could lead to a potential event, or poses threat to people, equipment, or public safety

Notification Requirements ERCOT Action

• Verbally communicate outage immediately.

• Submit into Outage Scheduler as soon as practicable.

• QSEs must update COP.

• Default Accept status automatically assigned when submitted.

Forced Outage Request Form

41

Replicates TSP Forced Outage Scheduler submittal format


3. The QSE shall confirm receipt[1] and review the Outage request by calling ERCOT Outage Coordination at (512) 248-6842 during normal business hours and calling the ERCOT Shift Engineer at (512) 248-6354 during non-business hours.

Phone Confirmation for Forced and Level 1 Maintenance Outage schedules is required.

[1] All emails of the “Resource Transmission Outage Request forms” should be verified by a phone call from the QSE to ERCOT.

42


4. ERCOT staff[2] shall enter such requests in the Outage Scheduler on behalf of the Resource Entity as submitted by the QSE.

[2] ERCOT shall act as the responsible Entity that will manage Outage Scheduler entries for Transmission Elements owned by the Resource.

This excludes entries of Resources since the Resource Entities QSE has sufficient roles and permission to submit outages for Resources that is acts as the designated point of contact for and can submit the Resource outages into the ERCOT outage scheduler.

ERCOT’s obligations in regard to submitting Transmission Outages for the Resources Entity and QSE shall terminate upon the implementation of Outage Scheduler system changes and protocol changes that enable Resource Entity QSEs to enter Outages of Transmission Facilities in the Outage Scheduler.

43


5. The Resource Entity shall:• Monitor the outage information on the ERCOT MIS• Ensure that the correct information was entered by ERCOT • Monitor the progression status and identify if the schedule is

“Approved” or “Rejected”.

https://mis.ercot.com/pps/tibco/mis/Pages/Grid+Information/Transmission

Digital Certificate is required

44

Market Information System – Accessing Outage Information

45


46


47

Market Information System – Accessing Outages

48

Updated files are loaded just after the top of each hour.

QSE/RE needs to validate entries submitted into the Outage Scheduler during the previous hour

(following format also applies to Proposed and Rejected Outages)


49

MIS – Proposed Outages in .csv format

Contains all outages in “Received at ERCOT” (RatE) or Study mode.May use Find, Filters and Data Sorts, etc. to locate outages

50

MIS – Proposed Outages in .csv format

Displays outages in “Received at ERCOT” (RatE) or Study mode.May use Find, Filters and Data Sorts, etc. to locate outages

51


52


53

Updated files are loaded just after the top of each hour.

Depending on the submittal time and the Planned Start of the Outage, itmay be several hours or days before Approval or Rejection is posted

MIS – Approved & Accepted Outages in .csv format

Displays all active and future Outages.May use Find, Filters and Data Sorts, etc. to locate outages

54


55

56

MIS – Rejected Outages in .csv format

Lists Rejected outages May use Find, Filters and Data Sorts, etc. to locate outages


6. If the Resource Entity identifies an error has been made:• Resource Entity shall resubmit the correct outage information to

their QSE • QSE shall resubmit the “Trans Planned-Maintenance Outage

Request Form” or the “Transmission Forced Outage Request Form” to ERCOT

• The Outage ID should be included on the resubmittal

57


6. (Continued):• QSE will confirm receipt and review the Outage modifications with

ERCOT Outage Coordination by calling (512) 248-6842 during normal business hours and calling the ERCOT Shift Engineer at (512) 248-6354 during non-business hours.

• Phone Confirmation for Forced and Level 1 Maintenance Outage schedules is required.

58


7. If circumstances prevent adherence to these timetables:

• ERCOT shall discuss the request status and reason for the delay of the approval with the requesting QSE

• ERCOT will make reasonable attempts to mitigate the effect of the delay on the Resource Entity.

59


8. If the outage is to be “Rejected”:

• ERCOT staff will contact the QSE by phone and/or email. • ERCOT staff will work with the Resource Entity via their QSE for a

solution. • If no solution can be reached, the ERCOT staff will notify the QSE by

phone and by email that the outage was “Rejected” • The message shall identify the contingency and the overloaded

element, other known issues and solutions.

60


9. For Planned and Maintenance Outages, if the outage is “Approved” and the outage starts:

• QSE will continue to email ERCOT updated forms to capture the “Actual Start” and “Actual End” times of the Outage.

• New Planned End times must be submitted before the previously approved Planned End.

• Phone confirmation is required for New Planned End submittals.• The Outage ID should be included on the updated forms. • The ERCOT staff will enter all of the updates into the Outage

Scheduler.

61

Planned and Maintenance Submittal Form

62

Replicates TSP Planned and Maintenance Outage Scheduler submittal format


9. (Continued) For Forced Outages

• QSE will continue to email ERCOT updated forms to capture the “Actual End” times of the Forced Outage.

• New Planned End times must be submitted before the previously accepted Planned End.

• Phone confirmation is required for New Planned End submittals.• The Outage ID should be included on the updated forms. • The ERCOT staff will enter all of the updates into the Outage

Scheduler.

63

Forced Outage Request Form

64

Replicates TSP Forced Outage Scheduler submittal format


10. If an outage cannot be performed during the approved time frame:

• Resource Entity will submit an updated form to their QSE who will provide this information to ERCOT.

• The Outage ID should be included on the resubmittal • ERCOT will enter the information into the Outage Scheduler. • Resource Entity should monitor ERCOT’s entries to ensure the

correct data has been entered by ERCOT.

65


10. (Continued)• If corrections are required then the Resource Entity should resubmit

the correct outage information to their QSE and the QSE shall resubmit the correction and confirm receipt

• QSE will review the Outage modifications by calling ERCOT Outage Coordination at (512) 248-6842 during normal business hours and calling the ERCOT Shift Engineer at (512) 248-6354 during non-business hours.

• Phone Confirmation for Forced and Level 1 Maintenance Outage schedules is required.

66

Adding or RemovingTransmission Facilities

Protocol Section 3.3.2.1

3.3.2.1 Information to Be Provided to ERCOT

• The energization or removal of a Transmission Facility or Generation Resource in the Network Operations Model requires an entry into the Outage Scheduler by a TSP or Resource Entity.

• The Resource Entity shall make entries in the Outage Scheduler for Outages of new or relocated Generation Resources.

• ERCOT * shall submit entries into the Outage Scheduler on behalf of the Resource Entity, for any energization or removal of Transmission Facilities owned by the Resource Entity.

* or the designated TSP

69

3.3.2.1 Information to Be Provided to ERCOT

• Once ERCOT posts a Resource Entity Transmission Facility Outage request on the MIS Secure Area, the Resource Entity shall review the submitted Outage for accuracy of information and request that ERCOT submit modifications if necessary.

• If any changes in system topology or telemetry are expected, then the TSP or Resource Entity shall notify ERCOT in accordance with the schedule in Section 3.3.1, ERCOT Approval of New or Relocated Facilities.

70

3.3.1 ERCOT Approval of New or Relocated Facilities

Before energizing and placing into service any new or relocated facility connected to the ERCOT Transmission Grid, a TSP, QSE, or Resource Entity shall enter appropriate information in the Outage Scheduler and coordinate with, and receive written notice of approval from, ERCOT.

71

Outage Scheduling Requirements

As per Protocol section 3.3.1, Planned Outages must be input by TSPs and QSEs to the ERCOT Outage Scheduler to account for gaps between:

• Model-ready and field-energization dates for equipment additions, upgrades, relocations, etc.

• Field-retirement and model-retirement dates for equipment being retired or permanently removed.

72

3.10.1 Time Line for Network Operations Model Changes

(3) TSPs and Resource Entities shall submit Network Operations Model updates at least three months prior to the physical equipment change. ERCOT shall update the Network Operations Model according to the following table:

73

74

Deadline to Submit Information to ERCOT

Model Complete and Available for Test

Updated Network Operations Model Testing Complete

Update Network Operations Model Production Environment

Target Physical Equipment In-Service Month

Jan 1 Feb 15 March 15 April 1 Month of April

Feb 1 March 15 April 15 May 1 Month of May

March 1 April 15 May 15 June 1 Month of June

April 1 May 15 June 15 July 1 Month of July

May 1 June 15 July 15 August 1 Month of August

June 1 July 15 August 15 September 1 Month of September

July 1 August 15 September 15 October 1 Month of October

August 1 September 15 October 15 November 1 Month of November

September 1 October 15 November 15 December 1 Month of December

October 1 November 15 December 15 January 1 Month of January (the next year)

November 1 December 15 January 15 February 1 Month of February (the next year)

December 1 January 15 February 15 March 1 Month of March (the next year)

Both are used to submit network model change requests

NOMCR vs. RARF

75

RARF to NOMCR Conversion

• REs must provide adequate cushion to account for validation and conversion to NOMCR by ERCOT

• RE may be asked to revise and resubmit if model validation fails after successful conversion to NOMCR

• May become an Interim Update if model submittal deadline has passed.

• REs must still observe Protocol 3.14.1.1 Notification of Suspension of Operations when removing a Resource from operation.

76

Resource Entity addinga Combustion Turbine

Scenario

RE Adding a new Combustion Turbine

B4 B5 B6

B1 B2 B3

TSP Owned

CD02

SD01

Resource RARF Submittal

L01 L02 L03

L04

S010 S020 S030

S040

C200

S100

CT02

ST01

XT02

XT01

MT02

MT01

CD03

C300 CT03

MT03

New Combustion Turbine Train

78

RE adding a Combustion Turbine to an existing facility

A RE plans to add a new combustion turbine CT03 to an existing facility

Planned energization date for CD03 and MT03 is Friday, April 15th at 1400 hours

New CT03 will synchronize to the grid for start-up testing on Wednesday, April 20th at 0800

80

In advance of Equipment Energization

Market Participants ERCOT

At least 4+ months Establish in-service/energization date for new equipment

Check Model Change Schedule to establish:

Minimum RARF submittal date - required at least 3 months prior to in-service month. Recommend submitting 3+ weeks prior to 1st of month deadline to allow for conversion to NOMCR, corrections, revisions, etc.Desired Model Ready Date – recommend selecting a model load date at least 2 model loads prior to energization for schedule flexibility and to facilitate the Approval to Energize process.

At least 90+ days Submit RARF using the minimum submittal and Model Ready dates determined above

7 days after NOMCR creation New equipment will be added to the Outage Scheduler Equipment Names list

91+ down to 46 days in advance of the equipment energization date

Submit Outage Requests.

Planned Start will always be 0000 hours on the Model Ready DatePlanned End will be the desired energization date and timeApplies to Resource and Transmission Facility submittals

7 days prior Begin the Approval to Energize pre-check

On the Model Ready date Prior to 0030 HoursSubmit actual Start for new equipment just loaded into the Network Operations Model

At 0000 HoursLoad updated Network Operations Model

On the Equipment Energization date

Contact ERCOT Real Time Shift Supervisor for final Approval to Energize.After equipment is energizedSubmit Actual End times

NMMS OS Timeline for Adding Resource Facilities - Sequence of Events

81

Network Operations Model Change Schedule on ERCOT.Com

82

Network Operations Model Change Schedule on ERCOT.Com

MIS – Accessing Network Operations Model Change Schedule

To be added:Network Operations Model Change Schedule

83

84

Network Operations Model Change Schedule

85

For the Red-flagged months:

Equipment being energized on the 1st and/or 2nd day of these months must meet the submittal deadline for the previous week.

86

Sample Model-ready dates from the posted Network Operations Model

Change Schedule

In-Service Month

ModelDeadline

Market Validation

Final Tests

Scheduled Loads

Supplemental Loads

APR Jan 1 Feb 15 Mar 15 Apr 1

Apr 6

Apr 12

Apr 20

MAY Feb 1 Mar 15 Apr 15 May 2

May 9

May 16

May 23

April 15th

4/6/2011

Model-ready dates only (includes Supplemental database loads) from the Nodal DB Column

Important Note: NOMCR Energization Date = a Model-ready Date!

Outage Submission Timeline

New equipment names will be available in Outage Scheduler equipment list 7 days after NOMCR submittal

Outage requests submitted…*

ERCOT will approve or reject…*

91+ days 75 days

46–90 days 30 days

*Prior to Planned Start Date/Time

88


B4 B5 B6

B1 B2 B3

TSP Owned

CD02

SD01

Normal Energization – 2 Steps

L01 L02 L03

L04

S010 S020 S030

S040

C200

S100

CT02

ST01

XT02

XT01

MT02

MT01

CD03

C300 CT03

MT03

Step 1 Step 2

89


B4 B5 B6

B1 B2 B3

TSP Owned

CD02

SD01

L01 L02 L03

L04

S010 S020 S030

S040

C200

S100

CT02

ST01

XT02

XT01

MT02

MT01

CD03

C300 CT03

MT03

Transmission Facilities Resource

90

Energization Date for New CD03 & MT03

Jan Mar Apr MayFeb12 21 28

ModelLoad

ModelLoad

ModelLoadModel

Load

ModelLoad

156

Outages for CD03 & MT03

Outages inthe Outage

Scheduler Outage for C300

7

RARF to NOMCR•Model-ready date for CD03, MT03 , C300 & CT03

ModelLoad

Startup date for CT03

Outage for CT03QSE

T Fac

20


92

Interval begins at 00:00 hours on the Model-ready date and ends at 23:59 on the day prior to the next model-ready date.

For example: Using the April 6th Model-ready date – the interval begins at 00:00 hours on April 6th and ends at 23:59 on April 11th (one minute prior to the next Model-ready date)

Requestor Equipment Outage SchedulerPlanned Start

Outage SchedulerPlanned End

T Fac CD03 April 06 00:00

T Fac MT03 April 06 00:00

T Fac C300 April 06 00:00

QSE CT03 April 06 00:00

CD03

C300 CT03

MT03

April 15th April 20th

Model-readyApril 6th at 00:00

Planned EnergizationDates



T Fac CD03 April 06 00:00 April 15 14:00

T Fac MT03 April 06 00:00 April 15 14:00

T Fac C300 April 06 00:00

QSE CT03 April 06 00:00

CD03

C300 CT03

MT03





T Fac CD03 April 06 00:00 April 15 14:00

T Fac MT03 April 06 00:00 April 15 14:00

T Fac C300 April 06 00:00 April 20 08:00

QSE CT03 April 06 00:00 April 20 08:00

CD03

C300 CT03

MT03



Desired Energization Date & Time

Model-readyDate @ 00:00

RE-Owned Transmission Facility outage request

RE submitted outage on the new Combustion Turbine

98

Model-readyDate @ 00:00

Desired Energization Date & Time

Must enter Zero’s for Off-line status

Energization Date for New CD03 & MT03

Jan Mar Apr MayFeb12 21 28

ModelLoad

ModelLoad

ModelLoadModel

Load

ModelLoad

156

Outages for CD03 & MT03

Outages inthe Outage

Scheduler Outage for C300

A2E

7

RARF to NOMCR•Model-ready date for CD03, MT03 , C300 & CT03

ModelLoad

Startup date for CT03

Outage for CT03QSE

T Fac

20


Approval to Energize process begins 7 days prior to

transmission facilities energization

Approval to Energize

NMMS/OS Coordination

Approval to Energize Process

What is Approval to Energize?

Last step to ensure all aspects of equipment have been accurately and consistently incorporated into all ERCOT Network Models

•Outages•Ratings•Characteristics•Connectivity•Telemetry mapping

Required prior to energization for:

• Newly installed, removed or relocated facilities

• Upgraded or revised ratings

Slide 102


ERCOT requires at least 7 calendar days prior to energization to complete the process and confirm that equipment is accurately modeled.


Beginning 7 days prior to the Energization Date, ERCOT Operations:

•Follows a check list of actions

•Approves or rejects request

Approval to Energize ProcessERCOT Check List for Approval

Modeled and observable in SCADA

Modeled in State Estimator

Outages properly modeled

Energization simulated in Power Flow study case

Confirmed there are no unresolved security issues

Ascertained that model recognizes new equipment

Market Participant contacted to convey tentative approval

Slide 104


Reasons for Rejection

Requested Element not modeled correctly

Requested Element supposed to be but not in SCADA

Unresolved security issues related to Energization of

Requested Element

Requested Equipment not in State Estimator

Note: ERCOT will contact the requestor to discuss

reasons for rejection.


Energization of new equipment in the production environment must be preceded by the following two conditions:

• The new equipment must be in the production model prior to energization

• Planned Outages with end times corresponding to the energization of the new equipment must be in the Outage Scheduler

106

Approval to Energize Process Pre-Check

On a daily basis, ERCOT Operations will:

• Check the Outage Scheduler for new equipment being energized in 7 days.

• Perform tests on new equipment in the current production model.

107

Approval to Energize Process Pre-CheckOn a daily basis (Continued)• If no problems are anticipated, ERCOT will email the Market Participant

stating that the Approval to Energize is expected to occur on the requested energization date.

• If problems are found, the Market Participant will be notified by email with the details of the problem and a statement that the Approval to Energize could be delayed if the issues are not fixed prior to the requested energization date.

Email

108

Approval to Energize Process Pre-Check

If the equipment to be energized is not in the current production model:

• Market Participant will receive a notice that the equipment is not in the current model and that approval may be delayed.

• Market Participant is required to call ERCOT Operations and provide details as to when the equipment is expected to be loaded in the model.

• With appropriate communications, the energization date will not be delayed.

Phone Call

109


NOTE: If changes in the field energization date are

anticipated, Market Participants should contact ERCOT

Operations with the updated information by phone.

Phone Call

110


On the day of energization:

•Market Participant contacts the ERCOT Shift Supervisor by telephone

• Requests permission to energize equipment

Phone Call

Model & Outage Submission Timeline Recommendations• Outages can span multiple Model Load dates

(recommend two model-ready dates prior to energization or following de-energization)

• Submit outages 91+ to 46 days in advance.

112

FieldEnergization orDe-energization Dates

Jan Mar Apr MayFeb

919 26

ModelLoad

ModelLoad

ModelLoad

153

NOMCR Model-ready Date

7

Outages in theOutage Scheduler91+ to 46 days in

advance

NOMCR Model-ready Date

ModelLoadDec

15 Days

A2E

QSE/RE Transmission Facilities Outage Coordination Workshop.

Documents

Transcript of QSE/RE Transmission Facilities Outage Coordination Workshop.