december 10, 2008 tptf integrated schedule review nodal pmo

December 10, 2008TPTF

Integrated Schedule Review

Nodal PMO

2Integrated Schedule ReviewDecember 10, 2008 2

Agenda

1. Program Changes (Janet Ply)

2. Preliminary Nodal Integrated Master Schedule (Janet Ply)

3. Scope (Janet Ply)

4. Schedule Assumptions (Janet Ply)

5. Work Remaining by Project (Core PMs)

6. Integration Activities (Mike Bianco)

7. EDS Activities (Matt Mereness)

8. Key Program Milestones (Janet Ply)

9. Critical Path (Janet Ply)

10.Next Steps (Janet Ply)


Program Changes

• Reorganized the entire program to eliminate project silos; instill accountability; put the right people in the right roles; streamlined delivery

• Changed leadership: Ron Hinsley is the Executive Sponsor and the Executive Director; Janet Ply now leads the nodal Program Management Office (PMO)

• Projects were reorganized into core and supporting projects; core projects own end-to-end delivery

• Developed a Nodal Master Integrated Schedule; identified hundreds of project inter-dependencies that were previously unknown

• Developed comprehensive program controls that are used rigorously to manage work

• Increased executive involvement in anything that affects program scope

• Increased vendor oversight and vendor accountability; have put ERCOT staff onsite and have vendor staff onsite at ERCOT during critical times

• Staffing has been reviewed; 108 contractors have left the nodal program since June; 18 contractors have been converted to ERCOT employees

• Increased ERCOT home team involvement in several key areas


Restructured Projects

• Network Model Management System

– Linda Clarke leads this effort

– Established data quality teams for the RARF data collection from Market Participants and for “nodalizing” the zonal seed for the network model (Common Information Model (CIM))

• ERCOT Readiness and Transition

– Murray Nixon leads ERCOT readiness and transition (i.e. business process development)

• EDS

– Matt Mereness leads EDS and MP readiness metrics

• Enterprise Integration Services, Integration Testing

– Combined these projects, renamed to Systems Integration and moved under the PMO

– Mike Bianco leads this effort and comes from CAISO

– Consolidated the zonal and nodal integration testing teams into one, added structure

• COMS team

– Hope Parrish, ERCOT Manager, leads this team

– Justin Rasberry brought in to oversee Settlements and Billing and Commercial Systems Interfaces (CSI)

– Reorganized the Credit Management and Monitoring (CMM) team to accelerate progress


Results of Changes

• A high level of executive oversight and involvement

• The right people in nodal leadership positions

• Strong program controls and processes

• Vendor focus

• Team member accountability

• Sense of urgency to deliver the Nodal program on schedule

ERCOT now has


Preliminary Nodal Integrated Master Schedule

• In June, PMs replanned the nodal program across all project teams resulting in

– An improved understanding of the scope of the work required through go-live, now scheduled for Dec.1, 2010

– A comprehensive understanding of cross project dependencies for the nodal program

– A detailed integrated master schedule for the nodal program that is the single source of record for all nodal work to be performed (~5400 activities)

– Most importantly, a realistic schedule with a high degree of confidence that the nodal program can be delivered on schedule

• Integrated master schedule has undergone numerous reviews and audits

• ERCOT has been using this integrated schedule and supporting reports successfully to manage the program and project critical paths

• ERCOT needs to incorporate MP activities and feedback, scheduled for TPTF meeting on Tuesday, Dec. 16, before the schedule can be finalized


Scope

• Nodal program scope included in the integrated schedule

– Approved requirements and conceptual system design documents

– All NPRRs approved through Nov.17, 2008

• Additional scope to process to be included

– Remaining business process work

– Remaining requirements traceability work

– No impact to the program critical path for this work

• Note 1: No schedule contingency has been included in the integrated master schedule; any additional scope/effort that is required will go through the nodal change control process and impacts to the schedule and budget will be captured

• Note 2: Removing and/or clarifying scope that affects any of the nodal systems at this point does not necessarily decrease effort


Schedule Information


Schedule Assumptions

• No new software vendor releases will be required past what is already planned (remaining scheduled releases will be covered in each individual project)

• Preserved the EDS durations as defined in the handbooks• Market participant activities that were placed on hold are not

restarted until the NMMS/EMS/MMS5 systems are on a synchronized model (schema and data set)

• Market participants will continue to participate in ongoing nodal EDS activities


Work Remaining – NMMS

Release Description FAT/Testing Complete

NMMS 5 • Production Model to support business processes• Auto Model Scheduler integration• MIS posting folder structure• Historical models and historical NOMCR tracking• PTC screens to support PMCR linkage• Canned reports (8)

Dec 19 08

NMMS 6 • Project Tracking Coordinator screens and functionality for Model Coordinator screens

• Outage clarification• Name service redesign• As Built report

Mar 17 09

NMMS 7 • Auto Model Scheduler validation May 04 09

JUN JUL AUG SEP OCT NOV DEC JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC

2008 2009 2010

NMMS Remaining Releases


Work Remaining - Model

Dec.10: Synchronized Model (v1.21 schema and data set)

Jan. 8: Validated Model (v1.21 schema and data set)

Mar. 9: Validated Model with Final RARF data (v1.21 schema and data set)

Achieve Production Quality Metric of 98%

Resolve Data Validation & Downstream Errors in Model v1.21

RARF Activities

Model Validation Activities

Validate v1.21 with Final RARF data Mar 9

Jan 8

Dec 10Zonal Seed “Nodalization

& Validation”

Dec 31

SEP OCT NOV DEC JAN FEB MAR

2008 2009


Work Remaining – EMS

Release Description FAT Complete

5.1.6 • Habitat 5.6 security patch re-test Dec 15 08

5.1.8 • Habitat 5.7 security patch and upgrade from beta to the release version Dec 24 08

6.1.x • (2) NPRR 97: Section 8 Reports• (2) NPRR102: Publication of Load Resources on MIS• (2) System Implementation Guides (SIGs) implementation

(0003/0022, 0006, 0011, 0020)

Jan 23 09

6.1.x • (1) CIM importer w/ synchronized model (v1.21 schema and data set)• (1) SIGs implementation (0002, 0008) • (1) IDA 46 Net (EPS) Metering

Feb 12 09

(1) AREVA Development(2) ERCOT Development


2008 2009 2010

EMS Remaining Releases



MMS4 P6 • CIM importer additions (based on model prior to synchronization (v1.20 schema and data set))

• NPRR113 (partial)• SIG rounding paper (partial)• Bug fixes

Jan 13 09

(patch testing)

MMS4 P7 • CIM importer additions (based on synchronized model (v1.21 schema and data set))

• Bug fixes

Feb 20 09 (patch testing)

MMS5 • Last scheduled release of functionality; pre-FAT will use the Jan. 8, 2009 NMMS-delivered validated model (v1.21 schema and data set); delivery to ERCOT targeted for Apr.15, 2009; FAT will use the Mar. 9, 2009 NMMS-delivered validated model with final RARF data (v1.21 schema and data set)

• CIM XML import processing and end-to-end testing • Remaining NPRRs and change items approved and to vendor by Dec. 21,

2008 (e.g., NPRR113, SIG rounding paper, NPRR154)• Bug fixes• Two patches to address defects scheduled during MMS5 FAT; additional

patches are scheduled to address integration and EDS defects but are not considered part of MMS FAT

Aug 21 09

(FAT)

Work Remaining – MMS


2008 2009 2010

MMS Remaining Releases



MMS MM UI • Market Manager FAT 1 – Bids and Offers, Resource-Specific Submissions, Schedules and Self-Arranged Ancillary Services

Feb 10 09

MMS MM UI • Market Manager FAT 2 – Trades, Awards, Notices and Verbal Dispatch Instructions

Apr 10 09

Work Remaining – MMS UI


2008 2009 2010

MMS MM UI Remaining Releases


Work Remaining – Outage Scheduler


2.1.0.0 • Patch installation and test Jan 09 09


2008 2009 2010

Outage Scheduler Remaining Releases


BUI • Base user interface testing – Group, Opportunity, Recurring Outages Feb 05 09

OS FP 1 • OS Feature Pack 1 – Warnings, Summary Enhancements Mar 24 09

OS FP 2 • OS Feature Pack 2 – Copy/Print/Export, Client Side Validations Apr 30 09

Outage Scheduler

Outage Scheduler User Interface


Work Remaining – CRR


Patch • Reported severity 1 and 2 defects fixed Dec 12 08

Enhancement • Software upgrade – jBoss 4.3– Java (recommending 1.7)

Aug 31 09


2008 2009 2010

CRR Remaining Releases



REG/DISP • REG4/DISP2: Migration to production – stage in current production environment

Dec 06 08

REG/DISP • COMS REG5/DISP3: Refactoring and Disputes API – i-Test complete

Feb 17 09

CSI5.5 • Commercial Systems Integration with S&B Jan 23 09

CSI6.3 • Commercial Systems Integration with CMM Jan 23 09

CSI7.0 • Commercial Systems Integration refactoring - S&B/CMM Long Day/Short Day

Apr 17 09

CMM4.1 • External reports/custom management Mar 31 09

CMM4.2 • Internal reports/defect fixes Apr 24 09

CMM4.3 • Upgrade 5.0/defect fixes May 22 09

FTGUI • Internal Financial Transfer Graphical User Interface May 19 09

Work Remaining – COMS


2008 2009 2010

COMS Remaining Releases


Integration Activities


Outline of Discussion

• Breadth of Integration Work• What’s Remaining?• Integrated Releases• Integrated Release 4 Activities• Integrated Release 5 Activities• Operational Readiness Activities


Breadth of the Systems Integration Effort

December 10, 2008

• 120 servers in the integrated test environment

• 16 nodal systems and shared services

• 36 integration interfaces

• 344 functional data flows

• End-to-end business scenarios EMS

NMMS

MMS

REG

CMM

CRR

S&B

1 11

10

2

6

13

26

19

12

14

4

7

9

16

15

EWS

18

8

EWS

29

EWS

17

20

5

21,22

EXT

EXT 21

30

32

33

OS

23

24

CDR28

MIS & UIs forOS, MMS

27 34

EWS

25

3

35

31,36

31,36

IntegrationServices

# Interface Description

1 NMMS -> EMS Network models

2 NMMS -> MMS Network models and contingencies

3 NMMS -> S&B Resource parameters and assignments

4 NMMS -> CRR Network Model

5 REG -> NMMS MP & Resource details

6 REG -> MMS MP & Resource details

7 REG <-> CMM Credit limits & Creditworthiness Status

8 REG<-> S&B MP & Resource details, Calendar

9 REG -> CRR MP & Resource details

10 MMS -> EMS Base points and LMP

11 EMS -> MMS Dynamic ratings, losses and constraints

12 S&B -> MMS Heat rates, verifiable O&M


13 CMM -> MMS Credit limits

14 S&B -> CMM Invoices, statements & determinants

15 CRR -> MMS CRR ownership

16 CMM -> CRR Credit limits, Bilateral trades

17 S&B -> CRR Invoices, statements & payment

18 EMS -> S&B Schedules, operations, BDs

19 MMS -> S&B Trades, awards, schedules, BDs

20 CRR -> S&B CRR settlements, BDs

21 EXT -> MMS S&B Platts FIP, FOP

22 S&B <-> EXT Banks financial wire transfers

23 OS <-> NMMS Outage data and network model data

24 OS <-> EMS Outage data and network model data


25 OS <-> EWS Outage Scheduler Web Services

26 MMS <-> EWS Bids, offers, trades, schedules and LMP

27 EMS -> CDR EMS data for Current Day Reports

28 MMS -> CDR MMS data for Current Day Reports

29 REG <-> EWS Disputes

30 EMS -> NMMS Operational data for model

31 EXT -> EMS WGR information

32 MMS -> CMM Bid, RTM and DAM market data

33 CRR -> CMM CRR inventory, bilateral trades

34 CDR <-> EWS Market information services

35 N ->MIS Multiple information services

36 OS EMS <-> EXT AWS Truewind


Integrated Release Milestones

December 10, 2008


2008 2009 2010

Integrated Release 1




Integrated Release 1 and 2 are complete Integrated Release 3 is in progress

To date, Integration Testing is approximately 4% complete4% complete


5%

50%

(Test/Build/Validation)

2%

100%

0%

IR 445%

IR 33%

IR 22%

IR 550%(Interface Testing)

(Interface + Functional Testing)

(Functional Integration Testing)

(Business Scenario Testing)

% of Systems Integration Work Effort by Integrated Release

Technology and Data Integration Functional Integration/Business Scenarios Market Integration


Integrated Release Timeline


2008 2009 2010






(Test/Build/Validation)

(Interface Testing)

(Interface + Functional Testing)

(Functional Integration Testing)

(Business Scenario Testing)

MMS4 P6, NMMS5, EMS CIM Importer v1.21, CSI 5.5/6.3, MIS10, Int Interfaces

MMS4 P7, CMM 3.3/4.1, CRR4, S&B RF1, Int interfaces

MMS UI, EMS, NMMS6, OS 2.1, OS UI FP1, CSI 7.0, CDR 4.0, Int Interfaces

NMMS7, CMM 4.2/4.3, OS UI FP2, Int Interfaces

MMS5 Prelim, FT P1 Lodestar, EMS Final, MIS11, Int interfaces

MMS5 Final, interface updates

Defect fixes

Defect fixes

Defect fixes

Operational Readiness (Application Security)

Operational Readiness (Performance and Monitoring)

Operational Readiness (Local and Data Center Fail-Over)= Software release migration to i-Test


Integrated Release 4 Activities

December 10, 2008

Continue technical interface and data integration (Jan. - Mar. 2009)

• Continue testing of MMS input and output interfaces

• Continue building integrated data sets

• Continue MMS to Settlements and Billing integration for the day-ahead market

• Begin operational readiness security testing

Begin functional integration testing and operational readiness (Apr. - July 2009)

• Perform NMMS, EMS and MMS functional integration testing on validated model (v1.21 schema and data set)

• Complete OS, OS and MMS UI integration testing

• Demonstrate functional integration and data flow for– CRR to Settlements

– MMS to Settlements for RUC and real-time market

– EMS to MMS for DAM and RUC

– Credit Management

• Begin operational readiness performance testing


2008 2009 2010

Integrated Release 4 (Functional Integration Testing)


Integrated Release 5 Activities

December 10, 2008

Continue functional integration testing (July - Sept. 2009)

• Continue system-to-system functional integration for DAM

• Continue work on integrated data set required for business scenario testing

• Test for first time all completed nodal systems

Begin business scenario testing (Oct. 2009 - Feb 2010)

• Regression test functional data flows where required

• Conduct bid-to-bill business scenario testing

– Run end-to-end system data flow for DAM, RT, SASM, RUC, CRR

• Validate end-to-end performance of nodal market timeline

• Complete operational readiness testing

• Complete system and data readiness to move to EDS


2008 2009 2010

Integrated Release 5 (Business Process Testing)


Operational Readiness Activities

December 10, 2008

• Performance Testing

– System processing, system-to-system data flow, end-to-end business scenarios

• Security

– Application-level compliance and vulnerability, access control (authentication and authorization)

• Monitoring

– Infrastructure and server health

– Application availability, performance and business-level events

• Fail-over

– Localized and data center (geographic) fail-over

• Daylight Savings Testing

– Long day/Short day


2008 2009 2010

Operational Readiness


EDS Activities


Outline of Discussion

• Revisit why EDS4 DAM/RUC/Settlements testing stopped• Lessons Learned from EDS in 2007/2008• Current EDS Delivery Challenges• Details of 2009 Market Activities• Monthly view of 2010 Market Activities


Revisit why EDS4 DAM/RUC/Settlements testing stopped

• Behind schedule in delivering a validated model with final RARF data• Significant workarounds put in place but did not solve the integrity

problems • DAM results were not meaningful due to data issues • MP involvement declined over time when DAM results were not valid• ERCOT system integration components were not in place


Lessons Learned from EDS in 2007/2008

• ERCOT Benefits

– Visibility of market generated bids/offers and submission structures

– More production-like testing of Web Services & Market rules

– Earlier feedback from Market Participants

• Market Benefits

– Exercised interfaces with ERCOT

– Better understanding of how the technology and rules are implemented

– Opportunity for end-users to put hands on the systems

– Opportunity to receive and analyze data from ERCOT to load into MP systems

• ERCOT Challenges

– MP integration was prioritized over internal integration

– Throw-away development of work-arounds to overcome system limitations

– Project SMEs were pulled to support EDS issues


All QSEs re-qualify submissions (API and UI)MPIM Production Digital Certificates issuedMPs ensure access and submission of data to EDS4

EDS and Market Activities 2009

EDS 2 Release 3Telemetry and SE

JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC JAN

2009

Focused Input Testing (Telemetry and State Estimator)

EDS 2 Release 4NOMCR

EDS 3 Release 6 LFC Testing Preparation

EDS 4 Release 8.3Verifiable Costs

EDS 4 Release 9.1Market Submission Testing

Registration

Training on NOMCR with NMMS6 and Business Rule Validation

SEM Go-Live Milestone

TSP Verification of Model

Begin open-loop test activity with QSEs

Submission of Verifiable Costs for Resources

Resource Transmission equipment registration

EDS 3 Release 5 SCED Real-Time Market Required SCED submissions


EDS and Market Activities 2009

Test windows for market systems prior to EDS4 commencement

- ERCOT and MPs will develop a test plan and schedule for aligning systems in 2009 and begin voluntary periodic windows of market testing

- Plan to release next generation of MMS and web services in Q2 2009

- Plan to execute day-ahead, adjustment, and real-time market on a periodic schedule. (e.g. run DAM multiple days and then pause testing (4-6 weeks) to analyze results and prepare for next test sequence)

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

Submission testing for

current MMS User Interfaces & Web

Services

* MPs compliant with appropriate Web Services and MMS4.x

Develop Test Plan with MPs

Periodic execution of markets:Day Ahead, Adjustment, Real-Time*

Possible sequence


EDS 2010 Timeline

View handout “EDS Project Schedule” for details


Feb 2010 – Resume EDS on integrated systems

EDS activities• Execute SCED with the objective of publishing LMPs for 6 months• Publish SCED reports (RT LMPs etc)

• Test communication of DAM inputs and outputs• Execute DAM 2 days per week with Market Data • Post AS Obligation, QSE Load Ratio Share, AS plan• Issue DAM Awards and Notifications (Awarded AS, Awarded Energy bid etc)• Publish DAM hourly reports (DAM LMPs, DAM MCPC etc)

• Conduct mock CRR annual auction• Publish CRR auction results

• Outage Scheduler open to MPs for submissions • Perform Outage Evaluation testing• Publish Outage Scheduler reports (Approved outages, rejected etc)

• Publish Available Credit Limit on MIS• Seek TPTF approval for test Network Model to be used for Settlements testing


Mar 2010 – Execute DAM and RUC, publish Settlements for DAM and conduct CRR auction

EDS activities• Continue execution of SCED for publishing LMPs for 6 months and publish reports• Continue execution of DAM 2 days per week with Market Data, issue notifications and publish results

• Conduct 2 hour LFC test with CIM

• Execute HRUC and DRUC 2 days per week with Market Data • Publish RUC results

– Committed and decommitted units– Active binding transmission constraints used in RUC

• Publish Settlement Statements, Invoices and Extracts for DAM– DAM Settlement and Resettlement Statement – CRR Balancing Account Invoices – DAM Invoice– CARD Invoices– DAM Resettlement Invoice– DAM Late Fee Invoices – DAM Consolidated Operating Day Extracts– DAM Market Operating Day Extracts– Public Reference Data Extract– Settlement Input Data Extract

• Conduct OS Performance test

• Publish test CRR annual auction results• Conduct Integrated CRR monthly auction


April 2010 – Execute DAM 5 days per week, publish RTM Settlement statements and conduct LFC tests

EDS activities• Continue execution of SCED for publishing LMPs for 6 months and publish reports

• Publish mock Integrated CRR auction results

• Conduct 8 hour LFC test with CIM

• Execute DAM and DRUC 5 days per week, issue notifications and publish results• Execute HRUC 4 days per week• Begin SASM execution• Issue SASM notifications

– Awarded AS offers• Publish SASM reports

– SASM MCPC – Total Ancillary Service procured – Aggregated Ancillary Service Offer

• Publish Settlement Statements, Invoices and Extracts for RTM and DAM– RTM Initial, Final, True-up and Resettlement Statement– RTM Initial, Final, True-up and Resettlement Invoice– RTM Consolidated Operating Day Extract (RTM CODE)– RTM Market Operating Day Extract (RTM MODE)– Public Reference Data Extract (PRDE)– Settlement Input Data Extract

• Begin testing of Disputes submission process through UI and API


May 2010 – Test full market timeline for 7 days and settle market

EDS activities

• Continue execution of SCED for publishing LMPs for 6 months and publish reports

• LFC test analysis and reporting of results to Market Participants

• Continue execution of DAM and DRUC 5 days per week, issue notifications and publish results

• Continue execution of HRUC 4 days per week

• Continue SASM execution

• Continue publishing of DAM and RTM Settlement Statements, Invoices and extracts

• Execute full Market timeline for 7 seven days

• Produce Settlement statements for the full market timeline

• One day dual entry of Outages into Zonal and Nodal systems


June 2010 – Conduct 48 hour LFC test and conduct integrated CIM business process testing

EDS activities

• Publish RT and DAM settlements for Full market timeline

• Execute 48 hour LFC test

• Execute EECP test


• Continue execution of DAM and DRUC 5 days per week



• Conduct CIM business process testing

• 7*24 support of Nodal systems

• Validate EDW Compliance Data Access


July 2010 – Verify LMP quality and conduct DAM/RUC/SCED performance test

EDS activities


• Complete posting of LMPs for 6 months

• Continue execution of DAM and DRUC 5 days per week



• Execute DAM/RUC/SCED performance test

• Conduct DST Test with Market Participants

• Begin verification of MIS compliance with Requirements

• Conduct fail-over test(s)


August 2010 – 48 Hour full market timeline test and preparation for 168-Hour test

EDS activities

• Continue DAM/RUC/SCED performance tests

• Execute DST test

• Execute 48 hours of full market timeline without Sev 1 or Sev 2 errors

• Complete verification of MIS compliance to Requirements

• Complete execution of Fail-over tests

• Complete verification of Dispute Process

• 7 day forecast validations/retraining

• Conduct test monthly CRR auction for 168-Hour test

• Align for 168-Hour Test

• Qualification - QSE declaration of intent to participate in Nodal


Sept 2010 – Completion of 168-Hour test and the Go-Live Period

• Upon successful completion of the 168-Hour test, the Texas Nodal Go-Live Procedure

will come into effect.

• Activities include• Start of Go-Live Period

• Readiness declarations by ERCOT and Market Participants

• First binding monthly CRR auction

• Go-Live Sequence

• First binding SASM

• Nodal Go-Live

• First binding DAM


EDS & Cut-over Plans

• EDS 1 Approach: TPTF approved Feb 2008 as being completed - http://nodal.ercot.com/docs/pd/eds/eds1/eds1/eds_1_approach_v2_0.doc

• EDS 2 Approach: TPTF Approved May 2007 -http://nodal.ercot.com/docs/pd/eds/eds2/eds2/EDS_2_Approach_v1_00.doc• EDS 3 approach: TPTF approved June 2007 -

http://nodal.ercot.com/docs/pd/eds/eds3/eds3dp/EDS_3_Approach_v1.0_061107.doc– SCED Handbook v4: TPTF Approved Feb 2008 -

http://nodal.ercot.com/docs/pd/eds/eds3/scedhdbk/eds_3_sced_mp_handbook_v4_0.doc– LFC Handbook v2: TPTF approved April 2008 -

http://nodal.ercot.com/docs/pd/eds/eds3/lfchandbook/eds_3_lfc_testing_market_participant_handbook_v2_0.doc– CRR Handbook v2: TPTF approved Jan 2008 -

http://nodal.ercot.com/docs/pd/eds/eds3/crrhandbook/eds_crr_testing_mp_handbook_v2_0.doc• EDS 4 Approach: TPTF approved Dec 2007 - http://nodal.ercot.com/docs/pd/eds/eds4/eds4app/eds_4_approach_v1_0.doc

– COMS Handbook: TPTF Approved Feb 2008 - http://nodal.ercot.com/docs/pd/eds/eds4/eds4coms/eds_coms_mp_handbook_v1.0.doc

– DAM/RUC Handbook v2: TPTF Approved March 2008 - http://nodal.ercot.com/docs/pd/eds/eds4/eds4damrucsasm/eds4_dam_ruc_sasm_mp_handbook_v2_0.doc

– Outage Scheduler Handbook: TPTF Approved March 2008 - http://nodal.ercot.com/docs/pd/eds/eds4/eds4os/eds_outage_scheduler_mp_handbook_v1_0.doc

– Day-light Savings Test Plan: TPTF Approved July 2008 - http://nodal.ercot.com/docs/pd/eds/eds4/dsttp/eds_dst_test_plan_v1_0.doc

– EECP Test Plan: TPTF Approved May 2008 - http://nodal.ercot.com/docs/pd/eds/eds4/eotp/eds_emergency_operations_test_plan_v1_0.doc

• 168 Hr Test procedure: TAC Approved July 2008 http://nodal.ercot.com/docs/pd/eds/eds4/168htp/texas_nodal_market_168_hour_test_procedure_v1_0.doc

• Single Entry Model Go-Live Procedure: TAC Approved Aug 2008 - http://nodal.ercot.com/docs/pd/eds/eds2/semglp/tnm_sem_go_live_procedure_v1_0.doc

• Texas Nodal Market Go-Live Procedure: TAC Approved Jun 2008 - http://nodal.ercot.com/docs/pd/eds/eds4/glp/texas_nodal_market_go_live_procedure_v1_0.doc

• TCR to CRR Transition Plan: TAC Approved Nov 2007 http://nodal.ercot.com/readiness/golive/kd/crr_tcr_to_crr_transition_plan_v1_0.doc


Key Program Milestones through Go-Live

• View handouts:– Nodal Program Timeline 2009– Nodal Program Timeline 2010


Critical Path

• Program critical path is the following

– NMMS through Jan. 8, 2009 when the validated model (v1.21 schema and data set) is delivered for consumption by downstream systems (e.g. MMS, EMS, and CRR)

– MMS5 is critical path from Jan. 9, 2009 – Aug. 24, 2009

– Integrated Release 5 is critical path from Aug. 24, 2009 – Feb. 8, 2010

– EDS is critical path from Feb. 9, 2010 – Dec. 1, 2010

• View handout: Nodal Program Critical Path


Next Steps


Next Steps

Review Activity Date

Present schedule to TPTF for initial review (today’s Webex meeting) Dec. 10, 2008

Gather initial TPTF feedback Dec. 16, 2008

Present revised schedule to TPTF for additional reviews and incorporate feedback January 2009

Present to TAC and incorporate feedback February 2009

Present to Special Nodal Program Committee and incorporate feedback February 2009

Present to Board of Directors and incorporate feedback February 2009

Present to PUCT TBD

• Please submit schedule comments/questions to [email protected]• Initial comments can also be shared during a planned schedule discussion at next week’s TPTF meeting• Documents provided to TPTF

– Nodal Critical Path– Nodal Program Timelines– EDS Project Timeline– Status Reports

• Proposed Review Schedule

december 10, 2008 tptf integrated schedule review nodal pmo

Documents

nodal work

nodal programa

program changesreorganized

entire program

realistic schedule

hasintegrated schedule

project teams

ercot staff