august 28, 2008 texas nodal program update special board of directors update ron hinsley

August 28, 2008Texas Nodal Program Update

Special Board of Directors Update

Ron Hinsley

2Texas Nodal Program UpdateAugust 28, 2008 2

Agenda

• Background • Newly Developed Delivery Approach• Work performed by projects to date• Work remaining (software releases) and why• Nodal program / project risks and issues• Options for Go-Live


Background

• Deep Background– Target date established before business requirements were

complete– Joint decision between the Market Participants (MPs) and ERCOT

to go with ‘Best of Breed’ nodal solution – Joint decision between the MPs and ERCOT to deploy Nodal

with a Common Information Model (CIM)

• More Recent Background– Program controls proved inadequate– Several vendor deliveries missed due to their internal delivery

issues and ERCOT staff missing requirement deadlines– To date, 112 Nodal Protocol Revision Requests (NPRRs) have

been approved by the Board, with minimal impact. Pending/future NPRRs could have an impact (details)


Newly Developed Delivery Approach

• The program structure has been revamped

– Developing a realistic integrated nodal program schedule that will be used for measuring progress and focusing on activities that affect the critical path

– Reorganized the projects into core and supporting activities, with core projects having accountability for all aspects of project delivery (details)

– Rebuilt the Project Management Office (PMO) with a structure and the skills needed to support Nodal size and complexities (details)

– Designed jointly-defined formal releases across nodal teams• Supporting document – Release Windows spreadsheet

– Plan for sufficient time to test in the lower environments (example)

– Improved vendor management

• Program structure will continue to evolve


Work Performed by Projects to Date


Details – Work Performed


• A large percentage of EMS and MMS development complete, some releases remain to be delivered

• FAT testing in progress

• Limited integration completed

• Limited integrated testing completed

• Limited EDS testing completed

Progress to date


• Data validation issues• CIM XML• No releases have completed FAT• Other systems have dependencies on

network model data from NMMS

NMMS

• These “downstream” systems depend on data and interfaces from “upstream” systems, such as NMMS, EMS, MMS

Settlements and Billing, MIS

Significant Work Remaining


Remaining Software Releases


How we developed the new sequence and durations

Project 1

Project 2

Project 3

EDS

Integration Test

Co

re a

nd

S

up

po

rtin

g

Pro

jec

ts (

FA

T)

FAT milestone put into time-boxed Integration releases

These will be integration tested and pushed to EDS

Project milestone

Indicates project milestones in a release

Cross project dependency

Legend


Release 2 – Market submissions and Results

• MMS provides SCED stability and compliance with V 1.12 of CIM

• All web services available less Disputes, Market Information, and Resources Parameters

• Ability to test Commercial Systems Integration (CSI)

EMS5.1.3

NMMS 4

MMS 4 P2

Siebel P3

CMM 3.1

CRR 2B

S&B 4CSI 5.3

11

10

26

19

EWS1.15

EWS1.15

21,22

EXT

EXT 21OS 2.0.10

CDR 3B28

MIS8OS_UI FP0

MMSUI

27 34

EWS1.15

25

35

31,36

31,36

IntegrationServices


Release 3 – 1st attempt at Bid to Bill process for DAM

• Ability to perform Bid to Bill through Settlements integration (for most Settlement charge types)

• MMS compliant with V 1.16 of CIM (closer to the final version)

• EMS – MMS integration for DAM, SCED and RUC provides ability to execute DAM and RUC with minimal data stubs

• CRR integrated to CMM and MMS

• All web services available less Market Information

EMS5.1.5

NMMS 5

MMS 4 P4

Siebel P4

CMM 3.1

CRR 2B

S&B 4CSI 5.4

11

10

6

13

26

19

14

7

9

16

15

EWS1.16

18

8

EWS1.16

17

20

21,22

EXT

EXT 21

32

33

OS 2.0.13

24

CDR 3C28

MIS9OS_UI FP0

MMSUI

27 34

EWS1.16

25

35

31,36

31,36

IntegrationServices


Release 4 – NMMS integration with EMS, Siebel etc

• NMMS integration with EMS, Registration, Outage Scheduler provides for a consistent dataset flowing between applications

• Alerts and notices integrated with each of the applications such as MMS and EMS

• Settlements Integration for DAM and RTM

EMS5.1.6

NMMS 6

MMS 4 P5

Siebel P4

CMM 4.1

CRR 2B

S&B 4CSI 6.5

1 11

10

6

13

26

19

12

14

4

7

9

16

15

EWS1.17

18

8

EWS1.17

17

20

5

21,22

EXT

EXT 21

30

32

33

OS 2.0.13

23

24

CDR 428

MIS10OS_UI FP3

MMSUI

27 34

EWS1.17

25

3

35

31,36

31,36

IntegrationServices


Release 5 – Integrated CIM

• Ability to perform end-to-end CIM business process testing (all systems using the same data set)

• Enables re-start of EDS activities for Day-Ahead Market, RUC and Settlements

• Enables performance of 2, 8 and 48 hour LFC tests

EMS5.1.6

NMMS 7

MMS 5 (Prelim)

Siebel P4

CMM 4.3

CRR 2B

S&B 4CSI 7.2

1 11

10

2

6

13

26

19

12

14

4

7

9

16

15

EWS1.18

18

8

EWS1.18

17

20

5

21,22

EXT

EXT 21

30

32

33

OS 2.0.13

23

24

CDR 4A28

MIS11OS_UI FP3

MMSUI

27 34

EWS1.18

25

3

35

31,36

31,36

IntegrationServices


Release 6 – Integrated Nodal system

• Final MMS version, enables testing of final versions of interfaces and External Web Services

• All system-to-system integration deployed

• Web Service chunking enabled (splits MP submissions of large files into smaller ones)

EMS5.1.6

NMMS 7

MMS 5 (Final)

Siebel P4

CMM 4.3

CRR 2B

S&B 4CSI 7.2

1 11

10

2

6

13

26

19

12

14

4

7

9

16

15

EWS1.19

18

8

EWS1.19

17

20

5

21,22

EXT

EXT 21

30

32

33

OS 2.0.13

23

24

CDR 3C28

MIS11OS_UI FP3

MMSUI

27 34

EWS1.19

25

3

35

31,36

31,36

IntegrationServices


Release 7 – Patches and bug fixes

• After Integration Release 6, majority of the effort will be involved in fixing outstanding defects in preparation for the 168-Hour Test

• Other activities include Performance testing, Security testing and fail-over testing

EMS5.1.6

NMMS 7

MMS 5 (Final)

Siebel P4

CMM 4.3

CRR 2B

S&B 4CSI 7.2

1 11

10

2

6

13

26

19

12

14

4

7

9

16

15

EWS1.19

18

8

EWS1.19

17

20

5

21,22

EXT

EXT 21

30

32

33

OS 2.0.13

23

24

CDR 3C28

MIS11OS_UI FP3

MMSUI

27 34

EWS1.19

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


Remaining Software Releases – NMMS

• NMMS 5 – required for SEM Go-Live– Production model business processes and workflow support– Auto model scheduler– MIS posting folder structure– Historical models and NOMCR tracking– PTC screens to support PMCR linkage to NOMCR– Reports

• NMMS 6 – required for SEM Go-Live– Project Tracking Coordinator (PTC) functionality and screens for Model

Coordinator– Outage Clarifications– Name Service– As Built Report

• NMMS 7 – not required for SEM Go-Live– Auto Model Scheduler Data Validation (supports Outage Scheduler and Outage

Evaluation)


Remaining Software Releases – EMS

• EMS 5.1.5 – Outage Evaluation (OE) – Testing at ERCOT (Post-FAT bug fix phase)– Voltage Support (VSS) – Testing at ERCOT (Post FAT bug fix phase)– Alerts and Notification along with the MMS-EMS Interface– Bug fixes

• EMS future drop – EMS Habitat upgrade– EMS CIM Importer – still testing at AREVA– Bug fixes

• Other drops– Changes related to SIG papers – in analysis, Private Use Network paper reviewed

by TPTF subgroup last week– Remaining interfaces (e.g., reports, replication) in progress– Bug fixes


Remaining Software Releases – MMS

• MMS 4, Patch 4 – Partial implementation of NPRR 102 – Bug fixes

• MMS 4, Patch 5 – Code changes based on consumption of latest CIM XML test file– Bug fixes for Settlements integration– Final patch scheduled for MMS4; delivery added to ensure progress is made while waiting for

validated and synchronized CIM XML file from NMMS

• MMS5 is the last scheduled release of functionality, target delivery to ERCOT is TBD; triggered off an NMMS-delivered validated and synchronized CIM XML file ready for consumption by downstream systems

– CIM XML import processing and end-to-end testing – Bug fixes– Remaining NPRR as approved (e.g., NPRR102, NPRR113), SIG paper changes (e.g.,

rounding) and software implementation changes based on testing (e.g., performance improvements, startup cost eligibility, SASM constraint modeling)

• Additional monthly patch releases are planned to fix any defects that are identified during subsequent testing efforts


Remaining Software Releases – CRR

• Enhancement patch (internal to software)

• Additional patches, as needed, to address defects originating from iTest


Remaining Software Releases – COMS

• Settlements and Billing Core Development

– DAM

– RTM

– Invoices

– Statements

– Data Aggregation

– Combine Cycles Unit

– Flow Gates

– Batch Scheduling

– Reports

• Commercial Systems Integration

– Integration to MMS, NMMS, EMS, S&B, CMM, CRR

– Bill Determinant Calculations

• Registration & Disputes

– Market Participant Account Management

– Settlement Dispute Management GUI – Settlement Dispute API

– Integration to MMS, NMMS, EMS, S&B, CMM, CRR


Risks and Issues


Nodal Program / Project Issues and Risks

• Staffing risk• Reliance on vendor deliverables• Resolving data integrity issues• Integration• Rework due to clarification of requirements • Traceability to Protocols• Zonal project resource conflicts• Stakeholder relations


Options for Go-Live


Go-Live Options that could Impact Go-Live Date

• Separate Day-Ahead and Real-Time Markets– Considered, would lengthen schedule

• Implement a CIM XML file work-around– Under review

• Start EDS earlier– Considered, would lengthen schedule

• Shorten EDS testing effort (on critical path)– Under review


Supporting Materials


Count of NPRRs By Type

Baseline Reason Count Sum Cost Sum

Baseline1 Corrections to Protocol Language - No Impact 11 0

Baseline1 Corrections to Protocol Language - Impact Absorbed 7 0

Baseline1 Corrections to Protocol Language – Incremental Impact 11 $1,800k-$3,500k

Baseline1 Scope Reduction 2 0

Baseline1 Synchronization with Zonal PRRs 11 $200k-$500k

Baseline1 Enhancements Deemed Essential 1 43 $1,000k-$2,000k $3,000k-$6,000k

Baseline2 Corrections to Protocol Language - No Impact 6 0

Baseline2 Corrections to Protocol Language - Impact Absorbed 4 0

Baseline2 Corrections to Protocol Language – Incremental Impact 10 $1,000k-$1,300k

Baseline2 PUCT Requirements 4 $800k-$1,200k

Baseline2 Synchronization with Zonal PRRs 3 27 $200k-$500k $2,000k- $3,000k

Post-Baseline2 Corrections to Protocol Language - No Impact 17 0

Post-Baseline2 Corrections to Protocol Language - Impact Absorbed 11 0

Post-Baseline2 Corrections to Protocol Language – Incremental Impact 3 $100k-$250k

Post-Baseline2 PUCT Requirements 2 $100k-$300k

Post-Baseline2 Scope Reduction 1 0

Post-Baseline2 Synchronization with Zonal PRRs 7 0

Post-Baseline2 Enhancements Deemed Essential 1 <$50k

Post-Baseline2 TBD (in progress NPRRs) 24 66 $2,900k-$3,600k $3,100k-$4,200k

N/A Rejected or Withdrawn NPRRs 13 13 0 0

Total 149 Total Cost $8,100k-$13,200k


Count of NPRRs By Type - Legend

Corrections to Protocol Language - No Impact Changes with no system impacts

Corrections to Protocol Language - Impact Absorbed Changes with minimal system impacts

Corrections to Protocol Language – Incremental Impact Changes with incremental project costs noted on the Impact Analysis

PUCT Requirements PUCT elements added since the May 2006 protocol baseline

Scope Reduction Changes resulting in reduced effort for the Nodal project

Synchronization with Zonal PRRs Changes that kept the Nodal protocols in sync with PRRs that apply to both the current protocols and the Nodal protocols

Enhancements Deemed Essential Changes not technically required but deemed essential for Go-Live

TBD (in progress NPRRs) Changes currently in the stakeholder process

Back to presentation


Functional Organization: Nodal Delivery

Program Mgmt Office

Janet Ply

Executive Sponsor

Ron Hinsley

A Core Project

Core PM

Integration

Supporting PM

MIS Portal

Supporting PM

Current Day Reports

Supporting PM

Enterprise Data Whse

Supporting PM

Integration Testing

Supporting PM

Executive Program Director

Ron Hinsley

Business Owners

Managers

Transition Executives

Division VPs

• Serve as the authoritative point of contact for nodal readiness and transition efforts for each affected ERCOT division/area

• Secure the appropriate participation of staff for their organization to meet schedule

• Facilitate ERCOT’s Readiness Declaration of progress for the departments within their organization

• Own business requirements for nodal systems

• Own responsibility for maintaining nodal systems after EDS

• Develop internal procedures for operating in the nodal market

• Directs the day-to-day activities of the nodal projects

• Serves as an escalation point for core and supporting project issues

• Administers program controls (see PMO organization)

• Serves as an escalation point for PMO

• Acts as liaison with Executive Team, TAC and Board

• Accountable for end-to-end delivery of core nodal system

• Accountable for core project schedule and budget

• Directs day-to-day activities of the supporting projects that interface with their project

• Manages vendor relationships

• Provides resources to the core projects as needed

• Directs activities that are not shared across core projects (i.e. MIS My Page, documentation)

Business Owners

Directors

CORE PROJECTS

SUPPORTING PROJECTS

These are the core nodal systems and include: NMMS, EMS, MMS, CRR, Commercial Systems and EDS

• Hold business owners accountable for appropriate involvements with nodal projects



Program Management Office

Program Management Office

Janet Ply

• Tracks status of data availability and quality across program

• Determines impacts across the program when data is not available or of sufficient quality

• Resolves architectural issues

• Facilitates integration of nodal systems with existing ERCOT architecture

• RUP • Project mgmt/ MS

Project• Estimation• Risk mgmt• Process training• Develops,

implements & communicates training effectiveness measures

• Ensures requirements are documented at the right level and traceable

• Ensures program level traceability to protocols and other binding documents

• Program scope change management

• PMO liaison to the Change Control Board

Program Schedule

John BlumJD Mullikin

Data Quality / Mgmt

Kenneth Ragsdale

Resource and Contract Mgmt

Dawn Moldenhour

Architecture

Shawn Catoe

Program Administration

Requirements Mgmt

Betty Luedke

Process Standardization

TBD

• Develops and maintains standard project plans and overall integrated schedules

• Analyzes schedules to identify critical path(s), trends, resource constraints, potential problem areas

• Develops project controls and supporting processes

• Identifies, documents, assesses & communicates project & program level risks

• Develops mitigation strategies with PMs

• Works with PMs & schedulers to assess program & project level impacts

• Works with PMs & PMO to develop a resource management plan

• Reports SOW status for contractors

• Determines appropriate staffing levels within projects

• Identifies areas for staffing optimization within projects

• Reviews existing contracts for nodal vendors to identify areas for optimization

Risk / Issue Mgmt

Brett Economides

• Develops nodal presentations & communications to ensure consistent messaging across the program

• Clarifies points of confusion within the program

• Improves meeting effectiveness

Communications

Adam Martinez



Number of weeks of test vs. Number of weeks of defect management

0.0

5.0

10.0

15.0

20.0

25.0

30.0

EMS 2C EMS 3A EMS 3B EMS 3C EMS 4.1 EMS 4.2

test time in weeks all defect management in weeks

The longer the test duration, the shorter the defect management time(when number of weeks in test increases defect management time decreases)



Work Performed by Projects to Date

Detailed Information


• Developed EMS exporter for extracting zonal data to initially seed the nodal network model as a starting point for data population

• Released functionality to enable ERCOT Transmission Service Providers (TSPs) to enter descriptions of Network Operations Model Change Requests (NOMCRs), with the following components:

– Information Model Manager – database to support operational network models, dataset management service that is capable of producing time based operations models, and services that import/export models in CIM XML/RDF bulk formats

– Project Tracker and Coordinator – allows user to describe construction projects or any changes to the network model parameters, and to perform some validation of submitted projects

– Topology Processor – converts operations models to planning models– Planning Model On Demand – capabilities to manage multiple planning projects and to produce

and manage multiple time-based planning models

• Completed NMMS training for TSPs on steps to complete a NOMCR

• Completed development of the four core Network Model Group business procedures needed to support business workflows after Single Entry Model Go-Live

– Generate, Post, and Distribute Models & Files, Conduct NOMCR Validation, Respond to Model Changes & Interim Updates, Maintain Network Model

• Although functionality has been delivered, NMMS has not yet successfully passed FAT

Work Performed by Projects to Date – NMMS



• Released the base EMS system which facilitates the data exchange between ERCOT and MPs, monitoring of generation, load frequency control, assessment of the network security of the ERCOT system through applications such as:

– SCADA (in EDS)• ICCP interface, Local calculations, Alarming, ERCOT Control Rooms interface to the

EMS Applications– Dynamic Ratings (in EDS)

• Temperature dependent limits (better use of existing facilities)– Forced Outage Detection (in EDS)

• Extends alarming beyond SCADA (detects and alarms on discrepancies between SCADA, Current Operating Plan and Outage Schedules)

– Generation Functions (in EDS)• Load Frequency Control, energy deployment, Ancillary Service performance

monitoring, Resource qualification testing, Resource Limit Calculator– Load Forecasting (in EDS)

• Seven-Day hourly, past pattern and weather based– Wind Power Forecasting (in EDS)

• Short-Term Wind Power Forecast (expected power for 2 days), Wind-Powered Generation Resource Production Potential (80% probability, for 2 days), Long-Term Wind Power Forecast (provided by resources)

Work Performed by Projects to Date – EMS



Work Performed by Projects to Date – EMS

• Released the base EMS system (continued)– State Estimator (in EDS)

• Real-Time estimate of the true and complete state of the system; identify real-time violations, inconsistencies between different measurements, and critical locations for measurements; Study version for debugging

– Network Security and Stability Analysis (in EDS)• Real-Time Contingency thermal overload analysis; Voltage and Transient stability

analysis (completed FAT); Transmission Congestion management; • Backup scheme when State Estimator fails to provide solution for extended time;• Determination of look-ahead limits for use in market functions

– Voltage Support Requirements Specification (in FAT)• Finds a suggested voltage profile to correct Real-Time voltage problems

– Outage Evaluation (in FAT)• Multi-hour, multi-model reliability analysis to determine if requested outages can be

approved– Interfaces to downstream applications

• MMS (most in EDS, some in FAT), EDW (most in EDS, some future work), All Wind Service (in EDS), External Load Forecast (in EDS), Weather Service (in EDS), Settlement & Billing (in EDS)

• Alarms and Notification to market participants (in FAT)– Supply Data to Reporting functions

• Telemetry standards; congestion reports; SE performance monitoring– Data Model Import (in process)

• Import and processing of CIM models needed for security assessment, generation control and outage evaluation Back to presentation


Work Performed by Projects to Date – MMS

• Delivered four releases through MMS4 that includes baseline 0, 1 & 2 functions in support of Day-Ahead (DAM), adjustment, and operating period markets

– Continuing work on MMS Processes & Procedures to support these markets

• Testing and all testing-related documentation through initial release of MMS4 FAT is completed

• Delivered and received approval for all requirements and conceptual design documentation through baseline 2 and any other approved changes (e.g., co-optimizing energy & AS for self-committed resources in DAM changes)

• Continuing work on functional & detailed design specifications, as changes are needed

• Continuing work on additional documentation that includes:– Test plans, test cases, test scripts, test results, traceability matrix for MMS4 patches

and MMS5– DAM, RUC, adjustment period & real-time process documentation development in

progress– DAM, RUC, adjustment period & real-time procedure documents development in

progress

• Evaluated and planning for inclusion (into MMS5) of all post-baseline 2 NPRRs approved by the board or deemed essential for go-live by TPTF (seven total as of Aug. 25, 2008) Back to presentation


Work Performed by Projects to Date – CRR

• Delivered a fully tested CRR system that meets the functionality and performance measures in accordance with approved requirements by using manually uploaded production files

• Resolved all defects found during Pre-FAT and FAT testing cycles

• Delivered a CRR process that is fully traceable and compliant with the respective Protocols as well as other official published defining documents

• Full Non Opt-In Entity (NOIE) participation in EDS testing of Allocation Markets



• Planning and Documentation– Completed Market Requirements and Conceptual Design documentation and received

approval from TPTF– Created Detailed Designs (Living Documents)– Created Test Plans, Cases, and Scripts (over 11,000 testing artifacts)

• Development– Completed Lodestar core development; targeted to deploy with Lodestar 4.7 Upgrade

in September 2008– Completed core development of batch cycle for DAM, RTM, and CRR– Completed and deployed builds for Commercial Systems Integration to support EMS,

SASM, CRR, DAM, GUI, and 70% of all billing determinants– Completed and deployed three Registration releases to ERCOT production (zonal)

that includes TML screens, Siebel screens, Metadata, and EIS changes– Deployed base CMM product, critical calculations build, and build 3.1 (critical

interfaces)

• Testing– Completed testing of all MMS patches from ABB (up to MMS4 patch 2) in support of

market based solution for settlements– Continuing testing of Siebel Phase 4 – Completed framework testing of shadow settlements extracts

Work Performed by Projects to Date – COMS



Work Performed by Projects to Date – EIP

• Simple, reliable and secure Market Participant interaction with ERCOT– Delivered interfaces for and supported all EDS testing activities since August 07– Nodal Web Services have been used 250,000 times since March 2008 by 315

different Market Participant identities – Supported Market Participants’ efforts to develop their side of the Nodal services

including workshops, Google, samples, sandbox and regular meetings

• Automated and controlled internal interfaces for all Nodal systems– Provided the interfaces that enable ERCOT’s new MMS and OS user interfaces– Designed 35 of the total 36 interfaces required for Nodal– Constructed 30 of the total 36 interfaces required for Nodal– Deployed 19 of the total 36 interfaces required for Nodal to iTest or equivalent

• Established a service oriented architecture platform for future enhancements

– New common services and design pattern library that ensure interfaces are reliable, controlled, simple to extend and maintain

– Comprehensive TIBCO-based infrastructure and description of all services and interfaces to improve and simplify maintenance and extension



Work Performed by Projects to Date – CDR

• Reporting Engine– Schedules and creates reports based on time from the source systems (MMS and

EMS) and inserts them into the ERCOT common data storage known as the Market Information Repository (MIR)

• Direct Posting to MIR – Inserts the file to the MIR database directly without using any brokers or middleware

thereby significantly decreasing the time to insert files, especially large ones

• Reports and Extracts – 38 complete, 8 pending completion– Outage Scheduler (4 of 4 complete); Day Ahead Market (7 of 7 complete)– Reliability Unit Commitment (3 of 3 complete)– Security-Constrained Economic Dispatch (3 of 3 complete)– Load/Demand Forecasts (6 of 6 complete); State Estimator (2 of 5 complete)– System Adequacy – PUCT (1 of 1 complete)– Distribution Factors (1 of 1 complete); Ancillary Services (4 of 5 complete)– Locational Marginal Prices and Settlement Point Prices (2 of 2 complete)– System Data (3 of 6 complete); QSE specific data (1 of 2 complete)– Weather Data (1 of 1 complete)



Work Performed by Projects to Date – EDW

• Infrastructure and software are in place for data replication to store Real-time Nodal information for EMS, MMS, CMM, CRR, Lodestar

• Energy Management System data marts are built to support future reporting requirements

• All State Estimator reports and data extracts completed in iTest using Nodal data, allowing MPs and ERCOT to track convergence and violations that occur during State Estimator execution

• All Telemetry reports are completed in iTest using Nodal data, allowing MPs and ERCOT to identify equipment failures and communications issues

• XSDs and DDLs for State Estimator and Telemetry reports posted for MP use

• All Shadow Settlement extracts currently in iTest; DDLs and XSDs posted for MP use

• All COMS Non-Shadow settlement extracts under development



Work Performed by Projects to Date – MIS

• Deployed Portal framework and supporting infrastructure to EDS

• Designed, created and deployed 16 Landing Pages containing approximately 40 portlets

• Deployed the following reports and extracts to EDS– 11 sample Settlement Statement and Invoices – 36 CDR Reports, 4 MMS Reports, 9 EDW Reports and Extracts, 3 CMM

Reports, and 6 COMS Reports and Extracts

• Deployed links to launch CRR, MMS and OS UI applications to EDS

• Implemented Simple Search functionality

• Deployed LMP Contour Map dashboard to iTest

• Implemented Protocol ViewBack to presentation


Work Performed by Projects to Date – Infrastructure

• Infrastructure Process Changes– Completed operational procedures for a fundamental technology change of Unix

platforms and Oracle platforms– Implemented a release management process capable of supporting a 500%

increase in releases– Implemented an SLA for the EDS systems which will become the Nodal SLA

• Infrastructure deployments and upgrades– Licensed all database and supporting software– Implemented the Market Participant Identity Management (MPIM) solution

currently in production– Revised the architecture of the monitoring tools to support the high availability

needs of Nodal– Deployed most infrastructure components required expected to be needed to

support the new market prior to performance tests– Consolidated 91 Unix servers to 4 to support both the Zonal and Nodal markets– Upgraded the architecture of the data warehouse to support the availability and

throughput requirements of the new market– Implemented a virtualized development environment to maximize data center

capacity– Completed all possible data center power conservation activities



Work Performed by Projects to Date – INT

• Testing Infrastructure / Tools– Documented overall Nodal Test Strategy and Procedures– Purchased and implemented a central defect tracking tool and process across

the program– Purchased and Implemented test automation tools for integration, performance,

and regression testing– Partially completed Integration Test Environment (supported by INF)

• Test Planning– Documented test plans for CRR, Siebel, and CMM functional testing– Developed approximately 600 test cases– Developed approximately 18,000 test scripts– Created automated testing suites for approximately 60 integration adapters– Created automated testing scripts to support functional regression testing of MIS,

CRR, CMM, CDR, and EIP systems – Created test data generation tools to facilitate early testing of software

• Test Execution in FAT– Executed approximately 18,000 test scripts



Work Performed by Projects to Date – EDS

• Test Planning– Developed and gained approval on EDS 1, 2, 3, & 4 Test Plans– Developed and gained approval on 168Hr Test & Go-Live Procedures

• Test Execution– Supported all MPs through initial connectivity and use of all Nodal systems

(MMS, CRR, Outage Scheduler, NMMS)– Completed Real-time system connectivity (ICCP)– 10 months of generating LMPs (SCED)– 13 Day-Ahead Markets, 2 SASMs, 6 DRUC and 2 HRUCs– 2 Monthly and 1 annual CRR Auction– 2Hr Total System LFC Test, including 5 open preparatory tests

• Market Support– Hosted ~100 test status calls & 10 face-face workshops– Answered ~6000 emails


august 28, 2008 texas nodal program update special board of directors update ron hinsley

Documents

mistexas nodal program

livetexas nodal program

datetexas nodal program

nodal size

whynodal program project

settlements integration

core projects

fatother systems