Http://nodal.ercot.com 1 Market Trials Outage Scheduling Weekly Update June 25, 2010.

http://nodal.ercot.com 1

Market TrialsOutage Scheduling

Weekly Update

June 25, 2010


Antitrust Admonition

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 the 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. If you have not received a copy of these Guidelines, copies are available at the Client Relations desk. Please remember your ongoing obligation to comply with all applicable laws, including the antitrust laws.

DISCLAIMER

All presentations and materials submitted by Market Participants or any other Entity to ERCOT staff for this meeting are received and posted with the acknowledgement that the information will be considered public in accordance with the ERCOT Websites Content Management Operating Procedure.


Agenda

• Anti-trust Admonition

• Environment Report– Planned / unplanned outages – CIM Load– Known Issues

• Standing Reports and Updates– General reminders / updates

• Outage Scheduler Transition to Go-Live

• Question and Answers / General Discussion

ERCOT asks that Market Participants log into the WebEx session using their company name and then their name. This will allow ERCOT to take roll-call offline

Market Trials 2010 Roadmap



Day-to-day operations summary: Planned / Unplanned Outages of EDS / CIM Load

• Planned Outages– 06/25/2010 5:00 P.M. – 10:00 P.M.

• Hardware site failover and application patch deployments are being planned during this period and will affect availability of following application services:

– OS UI

– OS

– EWS

• Unplanned Outages– No unplanned outages to report

• Target CIM Load dates for the month of June / July– 7/01/2010 – start on 2 week load schedule– 7/16/2010


General reminders / updates

• ERCOT has developed a user guide along with a web-based user interface training module to introduce the user interface and provide ongoing reference material for end users of the application.

• The introductory sessions are targeted at personnel from TSPs, QSEs and Resource Entities and are intended to:

– Review ERCOT market rules related to outage coordination– Describe roles and responsibilities for ERCOT and market participants– Introduce the use and design of the Outage Scheduler– Demonstrate the basic functions of the Outage Scheduler– Describe the interfaces between the outage scheduler and other Nodal Market applications.

• TSPs and QSEs are encouraged to send personnel that will either submit or maintain outage information on the Outage Scheduler as well as those that may need to generate reports on outages.

• The location and schedules of the remaining courses are shown below:

Date Time City Address

28-Jun-10 09:00 to 15:00 Dallas, TX

Oncor Energy Plaza1601 Bryan St.

Dallas, TX 75201

15-Jul-10 09:00 to 15:00Houston,

TX

CenterPoint EnergyEnergy Control and Data Center

16303 Tomball ParkwayHouston, TX 77065


General reminders / updates

• Reminder: ERCOT will be opening a window of optional Outage Scheduling testing

– Testing will open on 7/1/2010 and close on 7/9/2010

– During this period Outages will be de-coupled from the DAM to allow MPs flexibility to test varying scenarios

– MPs should contact ERCOT in advance to coordinate approvals or other scenarios

• ERCOT will presented the Outage Scheduler Transition Plan at NATF last week (6/23/2010)URL: http://www.ercot.com/calendar/2010/06/20100623-NATF


Environment Report: Known Issues

• Known issues posted to the readiness center at: http://nodal.ercot.com/readiness/markettrials/os/index.html

• New / Closed Issues: Next Slide


Environment Report: Known Issues – Newly Opened

Issue Description Work Around/Comments

On a Forced Extension the user is able to enter a New Planned End that is the same as the Planned End. This should draw an Error.

When the user enters the New Planned end on a Forced Outage it should be greater than the Planned End. The system is allowing the the New Planned End to be the same date/time at the Planned End. The New Planned End should always be greater than the Planned End. ERCOT is looking into this issue.

ERCOT is looking into this issue.Workaround: don't copy a ROO.ERCOT is looking into this issue.User is getting an error message. They should then look at the request and see that the required date/times are missing.

You can't work with a new TOO when is had an existing TOO that was canceled if any part of the 90 days overlaps.

If the user submits a TOO. An outage is submmitted on the Designated Resource from the TOO. The TOO is then canceled by the user. The user submits another TOO on the same piece of equipment. The New TOO will not be able to be approved by ERCOT until the Opportunity Window from the first TOO has passed. ERCOT is looking into this issue.

ERCOT is looking into this issue.Workaround: don't copy a TOO.

from the OS UI, TOO - Need to trigger the cancel pick list in ENYS

The user can't cancel a TOO once the designated resource has been submitted and the TOO Status is ENYS.

This is fix and is working its way up through the testing environments.ERCOT is looking into this issue.Workaround: The user can add a note when the outage is created and once it proceeds to Stage 2.

Load Resources are missing from the Equipment list Load Resources are missing from the Equipment list ERCOT is looking into this issue.

ERCOT is looking into this issue.Workaround: The user will need to highlight the Requestiong Company to limit the filtered information.

Copy outage for QSE ROO in each stage isn't displaying the correct fields

Then the user copies an ROO type outage, the resulting display should default to a Planned Outage.

Client side validation is not being displayed for missing date fields on Group TOO.

In the OS UI on a Group TOO, when the user is entering the Earliest/Planned Start Latest and leaves one of the date fields blank, the error message is "Displays Authentication failure. Please contact the ERCOT Help

OS UI Custom Filter - TSP only- Operating Company is not defaulting to the Certificate Company.

When the TSP user uses the Custom Filter to look for only their outages, the "Requesting Company" should default to the Company that is logged in.

You can copy a TOO with dates from any state with dates (reject etc), and it will submit it directly to

If the user copies a TOO that has Planned Start and End Dates the system also copies the dates. When the TOO

Can't add a note in stage 1 of a TOO

Once the TOO has been submitted in Stage 1, the user can't add notes. This would be before the TOO has had a match with a designated resource outage.


Environment Report: Known Issues – Closed

Issue DescriptionOn the details page, the Reviewer Notes are not formatted and are wrapping around the page

New reviewer notes are being added to the end of the previous note.

Copy outage: button is missing when an outage has a status of rejected.

If an outage has been Rejected by ERCOT, the Copy outage button is missing.

Does not handle the new error message and the Max_record change from EIP

If there are more than ~300 outages that should be displayed, the summary page or Warnings page are blank.

Max_record - needs to be added to the EIP definition and limit the records to jboss so it does not time out.

There is a limit to the number of outages the OS can return before the request times out.

Copy: Recurring should only display when the request type is PlannedWhen an outage other that a Planned outage is copied, the Recurring button may be displayed.

Operating Company Pick List- should display the company Name and not the short name

Pick list to create outages and to query back outages will require that the TSP know the ERCOT assigned MP short names.

Related Equipment Not working

When the user picks a line or transformer to be outages, and click the "View" button, the related equipment information is not returning.

Opportunity outage is not complete Opportunity outage is not working as expected.

OS Reports: Advanced Transmission Outage Schedule Statistics NP3-406 report requirements specifications are incomplete Due to NOGR 25 the requirements specifications are incompleteOS Reports: Advanced Resource Outage Schedule Statistics NP3-407 report requirements specifications are incomplete Due to NOGR 25 the requirements specifications are incompleteOS Reports Planned vs. Actual Transmission Outage Monthly Statistics (NP3-537 ER) - Update cover sheet Update the cover sheet to include the formula. OS Reports Planned vs. Actual Resource Outage Monthly Statistics (NP3-539 ER) - Update cover sheet Update the cover sheet to include the formula. OS Reports Planned vs. Actual Resource Outage Annual Statistics (NP3-540 ER) - Update cover sheet Update the cover sheet to include the formula.

25 June 2010

• Outage Scheduler with Zonal Outage Import

• Delete all Outages and run Zonal to Nodal Transfer Tool Monday, 8/14.

• Available for review and submissions Monday afternoon, 8/14.

• List of Outages not transferred can be provided upon request.

• Due to sensitive nature of Resource Outages, they will not be transferred by the Transfer tool.

• If a TSP does not want their zonal outages transferred --- inform ERCOT --- and ERCOT will not transfer them.

Outage Scheduler Transition Timeline (slide one of two)

25 June 2010

• TSPs and QSEs are requested to enter remaining outages not imported by the start of the 168 hour test (August 31, 2010).

• TSPs and QSEs should also begin entering outages effective December and beyond to support Go-Live.

• Outages starting and ending in October and/or November are optional to maintain.

• TSPs and QSEs required to certify Outages in the Nodal Outage Scheduler by 9/17 for all Outages December and beyond.

• First production pull of OS data 10/2 for first CRR Auction.

• TSPs are responsible to ensure that the outages in the Nodal Outage Scheduler are correct

Timeline (continued)

ERCOT OS Readiness – Nodal Metric EMO3

• Nodal Metric EMO3, criteria #1 – “A test of the Outage Management Process is completed”

• Integration between Outage Scheduler and Outage Evaluation has been tested successfully throughout Market Trials.

• Outage Coordinators able to approve outages in Outage Evaluation and send data back to the Outage Scheduler.

25 June 2010

25 June 2010

• Nodal Metric EMO3, criteria #2 – “An approved Outage Minimization Plan is implemented”

• Guideline requests TSPs to limit the submission of outages starting after November 21, 2010 and ending before January 4, 2010

• ERCOT recommends removing criteria #2 because Outage Coordinators have sufficient authority to approve/reject outages without a Outage Minimization Guideline.

ERCOT OS Readiness – Nodal Metric EMO3

Outage Scheduler Protocol Timeline

• ERCOT proposes that Section 3.1 “Outage Coordination” of the Nodal Protocols will become binding on November 1st, 2010 (for outages in December and beyond).

• Allows 30 days necessary for Outage Coordination to review and approve outages that will be effective post Go-Live.

• Based on the November 1st, 2010 binding date:

• Two Market Notices to be sent notifying the Market of the 11/1 effective date of Section 3.1

• 30 days out

• 10 day out

• BOD Approval in September

• TAC Approval in July or August

• NATF Review in June and/or July

25 June 2010


Q&A

Q&A / Open Forum

Http://nodal.ercot.com 1 Market Trials Outage Scheduling Weekly Update June 25, 2010.

Documents

Transcript of Http://nodal.ercot.com 1 Market Trials Outage Scheduling Weekly Update June 25, 2010.