lead from the front texas nodal 1 texas nodal eds 3 early delivery system plan tptf april 24, 2007

20
http://nodal.ercot.com 1 Lead from the front Texas Nodal Texas Nodal EDS 3 Early Delivery System Plan TPTF April 24, 2007

Upload: mae-harris

Post on 18-Jan-2018

216 views

Category:

Documents


0 download

DESCRIPTION

Lead from the front Texas Nodal 3 EDS 3 Plan - Background Presented EDS 3 Plan to TPTF on April 2 nd, 2007 Converted the presentation into the EDS 3 Plan on April 5 th, 2007 ERCOT internal review signoff April 19 th, 2007 Posted EDS 3 Plan for TPTF comment on April 19 th, 2007 –Comments expected by April 30, 2007 –Post redlined document and comment disposition by May 3, 2007 –Discussion and possible vote on May 7, 2007 TPTF on April 23 rd, 2007 requested a walk through of the plan

TRANSCRIPT

Page 1: Lead from the front Texas Nodal  1 Texas Nodal EDS 3 Early Delivery System Plan TPTF April 24, 2007

http://nodal.ercot.com 1Lead from the front

Texas Nodal

Texas Nodal EDS 3

Early Delivery System PlanTPTF

April 24, 2007

Page 2: Lead from the front Texas Nodal  1 Texas Nodal EDS 3 Early Delivery System Plan TPTF April 24, 2007

http://nodal.ercot.com 2Lead from the front

Texas Nodal

Agenda

Nodal Timelines• Nodal summary release schedule• EDS Release Philosophy

EDS 3 Plan• Objectives and Transition Plan requirements• Activities• Release and testing timelines• Market Participant Readiness

How can the TPTF continue to help in the effort?

Page 3: Lead from the front Texas Nodal  1 Texas Nodal EDS 3 Early Delivery System Plan TPTF April 24, 2007

http://nodal.ercot.com 3Lead from the front

Texas Nodal

EDS 3 Plan - Background

• Presented EDS 3 Plan to TPTF on April 2nd, 2007• Converted the presentation into the EDS 3 Plan on April 5th, 2007• ERCOT internal review signoff April 19th, 2007• Posted EDS 3 Plan for TPTF comment on April 19th, 2007

– Comments expected by April 30, 2007– Post redlined document and comment disposition by May 3, 2007– Discussion and possible vote on May 7, 2007

• TPTF on April 23rd, 2007 requested a walk through of the plan

Page 4: Lead from the front Texas Nodal  1 Texas Nodal EDS 3 Early Delivery System Plan TPTF April 24, 2007

http://nodal.ercot.com 4Lead from the front

Texas Nodal

ED

S 4

Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

Alarms Processing

FAT

EMS 2A

ED

S 1

ED

S 2

ED

S 3

FAT – Rel 3

EMS 2B EDW 1

FAT – Release 4

NMMS 1 NMMS 2 EIP 1

FAT – Release 5

REG 1 MMS 1EMS 2C

EIP 2 S&B 1 MIS 1EIP 3

EDW 2

FAT – Release 6EMS 3EDW 3

EIP 4

FAT – Release 7

EDW 4CRR 1CMM 1 EIP 5

FAT – Release 8MMS 2

S&B 2EDW 5 EIP 6

FAT – Release 9

MMS 2S&B 2OS

NMMS 3 EMS 4EDW 6 EIP 7

EMS 5 DIS

P2P Checkout

SE Verification

ITEST

RTM Go-Live

DAM Go-Live

EDS 2 Release 3: SE VerEMS- State Estimator & Tel Perf Stds,NSA, SPS/RAP, SCADA and DynRatings for Single ModelEDW– SE Statistics

EDS 2 Release 4: NM VerNMMS- Network Model, NOMCREMS- EMS /NMMS InterfaceEIP

EDS 3 Release 5: LMPsMMS– SCEDEMS- NSA, RLCCOMS- S&B (FIP, FOP,Ver Costs)- RegistrationEIPMISEDW

EDS 3 Release 6: LFC TestingEMS- LFCEIPEDW

EDS 3 Release 7: CRRCRRCOMS- CMMEIPEDW

EDS 4 Release 8: RT SettlementsMMS- RT Settlements InterfaceS&BEIP, EDWEDS 4 Release 9: DAM, RUCMMS- All Markets- OSEMS – Load Forecast, Out EvalNMMSS&BEIP, EDW

ITEST

ITEST

LegendIntegration TestingProject FAT Activities

Settlements Statements

Upload Bids

Test Settlements

Outages DAM, RUC, SASMFull Nodal Functionality

24*7 Operation 168 Hr Test

NOMCR Chk out Network Model Verification

Rel 1

Rel 2

EDS 1 Release 1:EMS Vanilla

EDS 1 Release 2:ICCP Upgrade

Rel 3

FAT

EDS

FAT

ITEST

EDS

FAT

ITEST

EDS

SCED TestingRegUpload Offers

Rel 4

Rel 5

Rel 7

Rel 6

6 month LMP Posting

CRR Data Validation Trial Ops of CRR

LFC Comms Testing

ITEST

EDS

FAT

FAT

EDS

ITEST

ED

S 4 Go-Live

Activities

EDS 1 EDS 2 EDS 3 EDS 4

MP Interface Spec

Start of EDS activities

FAT milestones

EDS Preparatory Milestones

Rel 8Rel 9

LFC Testing

ReadinessDeclaration

Readiness Declarations

Texas Nodal Program Summary Release Schedule High Level Version 2.0

Page 5: Lead from the front Texas Nodal  1 Texas Nodal EDS 3 Early Delivery System Plan TPTF April 24, 2007

http://nodal.ercot.com 5Lead from the front

Texas Nodal

Release Overview

• EDS 1 Release 1 – Alarm Processing

• EDS 1 Release 2 – Point-to-Point Checkout

• EDS 2 Release 3 – State Estimator & Network Security Analysis

• EDS 2 Release 4 – Network Model Validation

• EDS 3 Release 5 – SCED execution and Reasonable LMP’s

• EDS 3 Release 6 – Load Frequency Control

• EDS 3 Release 7 – Settlement Statements, CRR Allocation & Auction

• EDS 4 Release 8 – RT Settlements (no Shadow Settlements)

• EDS 4 Release 9 – DAM, RUC, SASM, Full Settlements, EDW Extracts

Page 6: Lead from the front Texas Nodal  1 Texas Nodal EDS 3 Early Delivery System Plan TPTF April 24, 2007

http://nodal.ercot.com 6Lead from the front

Texas Nodal

http://nodal.ercot.com 26Lead from the front

Texas Nodal

Quality and application maturity

Software Maturity / Stability / Time

Qua

lity

Early DropNew

software versions

New software version

Final version

Trend

http://nodal.ercot.com 26Lead from the front

Texas Nodal

Quality and application maturity

Software Maturity / Stability / Time

Qua

lity

Early DropNew

software versions

New software version

Final version

Trend

We are working to “start early” EDS to encourage earlier MP involvement – quality and support expectations must be managed appropriately• During the ERCOT quality control process,

“early” software versions will be used for EDS testing that have not completed ERCOT's full quality control cycle

• EDS Software versions will have known defects and additional defects discovered during EDS that will be incorporated into the internal release management schedule for prioritization and correction.

• Potential for periods of reduced service level due to unexpected circumstances such as server failures.

• These systems will be available to the market for testing the processes required to run SCED, LFC and CRR

• The EDS environment will be upgraded incrementally with new functionality coordinated with the internal release management schedule. Market Participants will be notified in advance of system upgrades and new functionality.

• System availability, quality of LMPs and other data and support responses will improve over time but may not likely meet production standards at the initial start

http://nodal.ercot.com 2Lead from the front

Texas Nodal

Release Quality Gates ensure quality of the early EDS activities

Integration 1 Integration 2

Security & Performance

End To End Testing

EDS Input and Data Validation EDS Release Testing

Registration EMS(RLC, TCM)

Projects perform FAT testing...

…followed by Application Integration

completion...

…followed by ERCOT Internal Quality Control

process...

MMS(SCED)

NMMS

Integration Testing

Testing to ensure application is stable, secure and meets system performance requirements

Testing of application integration and data flows between systems

Testing of business functionality across systems to support EDS

Build 1 Build 2

Early Delivery of Stand Alone Systems will be available for

Data Validation

EDS Interface Testing

External Facing Machine to Machine

Interface Stubs

Market Testing with all Participants

EarlyDrop 1

QC TestingRelease

EarlyDrop 2

Integrated Release

Page 7: Lead from the front Texas Nodal  1 Texas Nodal EDS 3 Early Delivery System Plan TPTF April 24, 2007

http://nodal.ercot.com 7Lead from the front

Texas Nodal

Early SCED Release Timeline

Objectives • Enable MPs (limited) to upload

offers to SCED (API or UI)• Scripted testing with limited

QSEs• Enable MPs to review LMPs • Obtain feedback on user

experience• Test MP ability to submit offers

through API into SCED

System Needs MMS• SCED• SCED UI (As Is)• LMP Output (CSV)EIP• Three Part Offer• Offer Acceptance• Error notification*Data / Stubs • Registration (QSE, Resources)• EMS (Telemetry Simulator,

Resource Limit Calculator, Shift Factors, Constraints)

• SCED Input data Creation / Submission Tool

Testing Tools• Defect tracking &

communication process / tool

* Interface may be delivered in next phase

Objectives (Incremental)• Test MP ability to utilize API’s

- Output Schedules- COP- Inc/Dec Offers

System Needs MMS• No ChangeMIS• Portal with all portlets configured

(Minimal data / linkable apps)EIP• Output Schedule• COP• Inc/Dec Offer*Data / Stubs• No ChangeTesting Tools• No Change

* Interface may be delivered in next phase

Objectives (Incremental)• Execute SCED utilizing Real-

Time ICCP data• All MPs to participate together• Publish LMPs and Base points

via MIS

System Needs MMS• SCED UI UpgradeEMS• SE, Transmission Constraint

Manager, Resource Limit Calculator

S&B• FIP, FOP, Heat Rate CurvesNMMS• Network ModelMIS• Data and linkable apps

incorporated as availableEDW• LMP Reports (MIR)EIP• EMS-to-MMS• MMS-to-EMS• NMMS-to-MMS• REG-to-MMS• S&B-to-MMS• PLATT-to-MMS Data / Stubs• No ChangeTesting Tools• No Change

Objectives (Incremental)• Publish all SCED reporting per

Nodal Transition Plan

System Needs MMS• Hub & Load Zone Price

CalculationsMIS• Full System• SCED Reporting (Graphical)EIP• MMS-to-MISData / Stubs• No ChangeTesting Tools• No ChangeInfrastructure• No Change

Objectives (Incremental)• Stable & quality SCED • Begin publishing of LMPs for 6

months as required by Nodal Transition Plan

System Needs MMS• Bug fix onlyMIS• Bug fix onlyEMS• Bug fix onlyEIP• Bug fix onlyNMMS• Bug fix onlyMIS• Bug fix onlyEDW• Bug fix onlyData / Stubs• No ChangeTesting Tools• No ChangeInfrastructure• No Change

Support levels:

The quality, system availability and support levels during early stages may not match production standards. ERCOT will ramp up to 8*5 support for SCED operations by Jan 08

July Aug Sep Oct Nov Dec Jan2007 2008

Page 8: Lead from the front Texas Nodal  1 Texas Nodal EDS 3 Early Delivery System Plan TPTF April 24, 2007

http://nodal.ercot.com 8Lead from the front

Texas Nodal

Early LFC Release Timeline

Objectives • Test the process for AS qualification of Generator and Load resources• Issue draft report to QSE and ERCOT and evaluate process making

adjustments as necessary• Software and communications testing• Calculation of ACE & comparison with existing control system• Validate EMS• Ability of QSE to receive Regulation Signal• QSE internal system / processing validation

System Needs EMS1• ICCP• Generation Subsystems

• Resource Qualification Testing Tool• LFC

MMS1• SCEDEIP• None?Data / Stubs • None?Testing Tools• Ancillary Service Qualification Testing Tool• Tool to provide base points to LFC• Defect tracking & communication process / tool

Infrastructure• Temporary Hardware – OK

Objectives (Incremental)• Evaluate each generator and load resource• Verify data requirements for LFC, for each QSE qualified to provide either Reg- Up, Reg-Down or

Response Reserve Services• Compare Area Control Error on EDS environment and existing control systems for seven days• Verify each QSEs ability to provide Regulation Control and Dispatch Instructions for Manual Response

Reserve Deployment Dispatch

System Needs EMS• Bug fix onlyMMS• Bug fix onlyMIS• Bug fix onlyEMS• Bug fix onlyEIP• Bug fix onlyNMMS• Bug fix onlyMIS• Bug fix onlyEDW• Bug fix onlyData / Stubs• No ChangeTesting Tools• No ChangeInfrastructure• No Change

Jan Feb Mar Apr May Jun Jul

2008

Support levels:

The quality, system availability and support levels during early stages may not match production standards. ERCOT will ramp up to 8*5 support for SCED operations by Jan 08

Page 9: Lead from the front Texas Nodal  1 Texas Nodal EDS 3 Early Delivery System Plan TPTF April 24, 2007

http://nodal.ercot.com 9Lead from the front

Texas Nodal

Early CRR Release Timeline

Objectives • Registration of QSEs as

CRR Account Holders• Validate MP CRR Digital

Certificate rights• Enable AH to upload Bids• Validate AH bids

System Needs CRR• CRR• CRR UI (As Is)Data / Stubs • Registration (Account

Holders)• CMM• Network Model, Settlement

Point Prices, etc

Testing Tools• Defect tracking &

communication process / toolInfrastructure• EDS 3 Environment

Objectives (Incremental)• Conduct mock CRR auction• Validate allocation

methodology• Issue test PCRRs and CRRs

to MPs• Mock CRR Invoices

System Needs CRR• CRR mock auction results

(CSV/XML)EIP – CRR interfaces with• NMMS• Registration• CMM

Data / Stubs• NoneTesting Tools• No ChangeInfrastructure• No Change

Objectives (Incremental)• Conduct monthly and multi month CRR auctions• Stable & Quality CRR• Conduct bilateral trading• View CRRs

System Needs CRR• Bug fixes• CRR ReportsEDW• CRR ExtractsData / Stubs• NoneTesting Tools• No ChangeInfrastructure• No Change

Jan Feb Mar Apr May Jun Jul2008

Support levels:

The quality, system availability and support levels during early stages may not match production standards. ERCOT will ramp up to 8*5 support for SCED operations by Jan 08

Page 10: Lead from the front Texas Nodal  1 Texas Nodal EDS 3 Early Delivery System Plan TPTF April 24, 2007

http://nodal.ercot.com 10Lead from the front

Texas Nodal

What should QSE’s have in place?

Release 5 - SCED• Personnel have attended Nodal Training Courses• Provided new and updated Registration data to ERCOT• QSE ability to create and submit offer curves to ERCOT • QSE Interactions with Interface Testing

– Obtained digital certificates – Connectivity and ID Authentication – Offer submissions capability demonstrated

• QSE ability to receive Base Points and other data• Market Participant operators available 8 to 5

Release 6 - LFC• QSE EMS Nodal system changes complete to support LFC • QSE Ancillary Service Qualification complete

Release 7 - CRR• CRR Digital Certificate access requested• CRR Account Holder:  Completed Registration with ERCOT and Application

Process • CRR Account Test Credit Limit established

Page 11: Lead from the front Texas Nodal  1 Texas Nodal EDS 3 Early Delivery System Plan TPTF April 24, 2007

http://nodal.ercot.com 11Lead from the front

Texas Nodal

Web Service Implementation Timeline

Objectives • The following Web Services

should be available by June 30th, 2007

Web Services – EIP

• Three Part Offer• Incremental/Decremental

Offers• Congestion Revenue Rights• Current Operating Plan• Energy-Only Offer• Output Schedule• Bid Set Acceptance• Bid Set Errors• Get mRID• System Status

Jun Jul Aug Sept Oct Nov Dec

Objectives • The following Web Services

should be available by July 30th, 2007

Web Services – EIP

• Forecasted Load• Market Totals• Market LMPs and SPPs• Binding Constraints• Active Contingencies in

SCED• Voltage Profiles• Shift Factors• Proxy Curves• Mitigated Curves

Objectives • The following Web Services

should be available by August 30th, 2007

Web Services – EIP

• Energy Bid• PTP Obligation• Self Schedule• Real-Time System Load• Total Regulation• Load Ratio Share• Load Distribution Factors• Unit Availability• Startup and Shutdown

Instructions• CRR Awards

Objectives • The following Web Services

should be available by September 30th, 2007

Web Services – EIP

• Self Arranged Ancillary Services

• Ancillary Service Offers• Ancillary Service Trades• Capacity Trade• DC Tie Schedule• Energy Trade• Get Award Set• Market MCPCs• Ancillary Service Schedule

Obligations• Customer Load Profile• PTP Obligation Awards

Objectives • The following Web Services

should be available by October 30th, 2007

Web Services – EIP

• Dynamic Ratings• Competitive Constraints• Aggregated Ancillary Service

Offer Curves• Ancillary Service System

Plan• Pending Trade• Energy Offer Awards• Energy Only Offer Awards• Energy Bid Awards• Ancillary Service Awards• Outage Creation

Objectives • The following Web Services

should be available by November 30th, 2007

Web Services – EIP

• Total Ancillary Service Offers

• Total DAM Energy• Derated CRRs• Notices and Alerts• Outage Notifications• Alert Acknowledgement• Outage Query• Outage Cancellation

2007

Page 12: Lead from the front Texas Nodal  1 Texas Nodal EDS 3 Early Delivery System Plan TPTF April 24, 2007

http://nodal.ercot.com 12Lead from the front

Texas Nodal

Next StepsEDS 3 Transition Plan Details

1. Develop a method for Market Participants to create and provide individual Resource offer curves to SCED

2. Identify MIS reporting requirements – “posting LMPs and other data available on the EDS…” if required in NP 6.3.2

3. Define LMP posting requirements – “at least six months”

– What is needed & How much Analysis Requirements -----

4. Define details of Load Frequency Control Testing

5. Create a CRR detailed test plan describing each step of trial allocation & auction

6. Define PCR / CRR allocation process for testing

7. Finalization and signoff of Entry / Exit criteria

8. Other items as needed

Page 13: Lead from the front Texas Nodal  1 Texas Nodal EDS 3 Early Delivery System Plan TPTF April 24, 2007

http://nodal.ercot.com 13Lead from the front

Texas Nodal

EDS 3 Transition Plan Details Development

Step 1 – Meet with Nodal project teams, ERCOT business owners and MP volunteers to define and document a recommended approach

Step 2 – Send 1-2 page recommended approach to TPTF for review

Step 3 – Discuss the recommended approach at TPTF for feedback and consensus

Step 4 – TPTF approval

Step 5 – Document recommended approach into the EDS3 Detailed Plan

Page 14: Lead from the front Texas Nodal  1 Texas Nodal EDS 3 Early Delivery System Plan TPTF April 24, 2007

http://nodal.ercot.com 14Lead from the front

Texas Nodal

Transition Plan Details – Draft Development & Approval Schedule

Transition Plan Requirement TPTF Volunteer Presentation to TPTF

Approval by TPTF

Develop a method for Market Participants to create and provide individual Resource offer curves to SCED

May 21, 2007 June 11, 2007

Identify MIS reporting requirements – “posting LMPs and other data available on the EDS…” if required in NP 6.3.2

May 21, 2007 June 11, 2007

Define LMP posting requirements – what does “at least six months” mean?

May 21, 2007 June 11, 2007

Define a method for Load Frequency Control Testing, including the plan for settlement of nodal testing periods (if required)

May 21, 2007 June 11, 2007

Create a CRR detailed test plan describing each step of trial allocation & auction

May 21, 2007 June 11, 2007

Define PCR / CRR allocation process for testing May 21, 2007 June 11, 2007

Draft of Entry / Exit criteria May 21, 2007 June 11, 2007

We are seeking volunteers to work with ERCOT personnel for resolution of these issues.

Page 15: Lead from the front Texas Nodal  1 Texas Nodal EDS 3 Early Delivery System Plan TPTF April 24, 2007

http://nodal.ercot.com 15Lead from the front

Texas Nodal

EDS 4 Preview

Page 16: Lead from the front Texas Nodal  1 Texas Nodal EDS 3 Early Delivery System Plan TPTF April 24, 2007

http://nodal.ercot.com 16Lead from the front

Texas Nodal

Release Overview

• EDS 1 Release 1 – Alarm Processing

• EDS 1 Release 2 – Point-to-Point Checkout

• EDS 2 Release 3 – State Estimator & Network Security Analysis

• EDS 2 Release 4 – Network Model Validation

• EDS 3 Release 5 – SCED execution and Reasonable LMPs

• EDS 3 Release 6 – Load Frequency Control

• EDS 3 Release 7 – Settlement Statements, CRR Allocation & Auction

• EDS 4 Release 8 – RT Settlements (no Shadow Settlements)

• EDS 4 Release 9 – DAM, RUC, SASM, Full Settlements, EDW Extracts

Page 17: Lead from the front Texas Nodal  1 Texas Nodal EDS 3 Early Delivery System Plan TPTF April 24, 2007

http://nodal.ercot.com 17Lead from the front

Texas Nodal

EDS 4 Objectives

Execution of DAM, RUC, SASM5.4.6(1) Verify convergence of QSE provided bids and offers and expand testing to allow Market Participants to submit energy-only offers and bids for any settlement point on the ERCOT Transmission Grid 5.4.6(2) Verify that DAM can co-optimize energy and ancillary service procurement5.4.6(3) Execution of the DAM shall continue for 7 consecutive days5.4.7(1) Verify proper RUC commitment of available off-line resources5.4.14 Conduct SASM coordinated testing

Settlements and Data Extracts5.4.6(4) Verify RT Operations, DAM, and SASM settlement statements5.4.7(4) Verify RUC settlement statements

Outage Scheduler 5.4.1(2h) Verify for proper operation the functions of the Outage Scheduler 5.4.1(2i) Verify that ERCOT operators are able to determine if the Outage of a Transmission Facility had been scheduled in the Outage Scheduler or is a Forced Outage

Emergency Electric Curtailment Plan5.4.16 Conduct tests for the proper operation of the system under EECP conditions

Performance and Compliance Measurement5.4.12 Provide sample performance and compliance reports to the Market Participants for review and comment

168 Hr Test5.4.9 ERCOT shall develop real time dispatch market readiness criteria that will include a systems stability test. The systems stability test generally will require the real time systems performing SCADA, Network Security Analysis, Transmission Constraint Management, SCED, RUC and LFC to operate without significant error for at least 168 continuous hours

Daylight Savings Time5.4.15 ERCOT shall develop procedures and conduct the tests for the proper transition of systems to and from daylight savings time

Data Center - Site fail over and system fault tolerance Test

Page 18: Lead from the front Texas Nodal  1 Texas Nodal EDS 3 Early Delivery System Plan TPTF April 24, 2007

http://nodal.ercot.com 18Lead from the front

Texas Nodal

EDS 4 – DAM, RUC, SASM, Settlements Testing Approach

Phase Activities Incremental System / Features / Artifacts

Upload Bids • Create and upload offers for Physical Resources• Create and upload bids for Load • Create and upload offers for physical offline resources for testing RUC• Validate DAM, RUC, SASM input data• QSE Energy-Only Offers submittals and bids for any settlement point on

the ERCOT transmission grid• QSE Bilateral Trade submittals

• DAM, RUC and SASM• DAM External Input Interfaces available • External User Interface updates available• Initial EDS 4 MP Handbook complete

Perform Outages

• Test Outage Scheduler• Synchronize use of the Outage Scheduler for transmission elements and

resource outages

• Outage Scheduler• Outage Evaluation

Integrated DAM & RUCTest Settlements

• Download and verify real-time settlements statements • Test the operation of DAM to procure Ancillary Services• Update offers for SASM• Test transition of systems to and from DST

• Real Time Settlements• Shadow Settlements

24 x 7 Operation

• 7 day trial Operation of DAM• Review the test settlement statements for errors and provide feedback• Download and verify full settlements statements & extracts

• Training Complete • 24* 7 support during EDS• Final EDS 4 MP Handbook• Site redundancy for environments

168 Hour Test • Participate in 168 hour test• Perform systems stability test for real time systems – SCADA, NSA,

TCM, SCED, RUC and LFC• Generate Settlements statements using dispatches and LMPs from

SCED and actual meter data• Review Settlements statements for each operating day and provide

feedback

• Final Nodal Configuration

Page 19: Lead from the front Texas Nodal  1 Texas Nodal EDS 3 Early Delivery System Plan TPTF April 24, 2007

http://nodal.ercot.com 19Lead from the front

Texas Nodal

What should QSE’s have in place?

Release 8 – Energy-Only Offers and Outage Scheduler• Personnel have attended recommended Nodal Training Courses and

reviewed associated reading materials• Provided new and updated Registration data to ERCOT• QSE ability to create energy-only offers and bids for any settlement

point on the ERCOT gridRelease 9 – DAM, RUC, SASM, Settlements• QSE ability to create and submit bid curves, offer curves and trades to

ERCOT • Designate resources providing ancillary services• Attest for ancillary services qualification of resources• Complete registration and qualification process • Market Participant operators available 24 x 7

Page 20: Lead from the front Texas Nodal  1 Texas Nodal EDS 3 Early Delivery System Plan TPTF April 24, 2007

http://nodal.ercot.com 20Lead from the front

Texas Nodal

Questions

Questions?