August 25, 2008 TPTF Nodal Status Report: Projects Status Updates Adam Martinez.

August 25, 2008TPTF

Nodal Status Report:Projects Status Updates

Adam Martinez

2Nodal Status Report - Projects UpdatesAugust 25, 2008 2

Agenda

• NMMS• EMS• MMS• CRR• COMS• EIP (Integration) • INT (Testing)


NMMS Project Update


Project Update – NMMS

Software Releases

• Finishing NMMS 4 FAT

• Supporting AREVA On-Site Work

• Working with Siemens to Create Data Validation Rules

• Working with EDS to determine System Planning Market Participants’ training and market trial activities


Project Update – NMMS (cont.) Functionality SEM Description

Oct

ober

200

8 Re

leas

e

Production Model Business Processes & Workflow Support

Supports model building and maintaining data dates Creates approved jobs for consumption by EMS

Auto Model Scheduler User interface to schedule reoccurring model builds Supports creation of incremental models

MIS Posting Folder Structure Supports posting models to ERCOT MIS Establishes market participant-specific notifications

Historical Models & NOMCR Tracking

Supports “what-if” capability to create models based on past NOMCRs

PTC Screens to Support PMCR linkage to NOMCR

Associates NOMCRs & PMCRs to “pull-out” PMCR when NOMCR is applied

Reports Canned reports including Device Report, Change Request Statistics, TSP Model Support, etc)

Dec

embe

r 20

08 R

elea

se PTC Functionality & Screens for Model Coordinator

Create queries to manage workflow (i.e., determine active NOMCRs, number of days until active)

Outage Clarifications Supports outage information needed for CRR and planning models

Name Service Validation and translation to ERCOT RDF Ids (unique identifiers in CIM files for new equipment) for TSP NOMCRs that included TSP Ids

As Built Report Additions to support identification of “failed” outage Supports profiles for downstream systems (EMS and MMS)

TBD

Auto Model Scheduler Validation Validation of models created by Auto Model Scheduler

Remaining NMMS Functionality


EMS Project Update


Project Update – EMS

Recent FAT Completion and Release to ITEST• Transient Stability/Voltage Stability Analysis Tools (TSAT/VSAT)

EMS has completed all EMS functionality testing and released the functionality to I-Test/EDS except:

• Currently in FAT testing (rescheduled completion to the end of this week)

– Outage Evaluation (OE) – Testing at ERCOT (Post-FAT bug fix phase)• Two high severity SPRs remain open. Expect fixes and retest this week.

Once fixed, exit FAT

– Voltage Support (VSS) – Testing at ERCOT (Post FAT bug fix phase)• One high SPR is being fixed and once tested, then exit FAT

– Alerts and Notification, MMS-EMS Interface and Alarm Display – Testing at ERCOT (Post FAT bug fix phase)

– Defect fixes (over 70 being tested, over 90% acceptance level)


Project Update – EMS (cont.)

• In progress or planned– EMS CIM Importer – testing at ERCOT

• Iterating with NMMS to get fidelity in the data model to complete validation and run the EMS applications

• AREVA technical resources on site at ERCOT starting Aug. 18

• CIM XML has been consumed and all seven Habitat databases have been produced. Validation success is improving as the fidelity of the data improves

– Changes related to SIG papers – in analysis, Private Use Network paper being reviewed by TPTF this week

– Remaining interfaces (e.g., reports, replication) and defects are planned or in progress


MMS Project Update


Project Update – MMS

• MMS (ABB) Software Releases– MMS4 includes baseline 0, 1 & 2 software (e.g., DAM, RUC, SASM, CCT,

SCED)• Patch 2 is scheduled to complete all SPR retesting on 22Aug08

– First FAT to use a CIM XML test data set; data for all MMS-required extensions is not included in this CIM XML test data set

– As reported at the May 23 TPTF meeting, two previously deferred items that the TPTF requested be delivered to ERCOT by ABB prior to go-live were added back to the MMS schedule and planned for delivery to ERCOT by ABB on June 30. Both items were delivered on time and are currently being tested in MMS4 patch 2 FAT

» Item #1: Dynamically scheduled resource incremental and decremental energy offer curves updates

» Item #2: Co-optimizing energy and AS for self-committed resources in DAMNOTE: there was a TPTF subgroup that defined the new requirements; the TPTF approved 2 of the 3 proposed requirements for delivery

NOTE: The two S&B info only calcs and the resource parameter API were originally deferred but have been delivered by ABB and tested by the MMS team. There is still EIP work to complete the resource parameter API.

– Loading of MMS4 patch 2 into iTest complete


Project Update – MMS (cont.)

• MMS (ABB) Software Releases• Patch 3 delivered by ABB on 25Jul08

– uses same CIM XML test data set as patch 2– loaded into MMS DEV starting on 28Jul08– MMS DEV smoke testing completed 15Aug08– incrementally loading patch 3 into MMS FAT with a target completion of

29Aug08 for loading and smoke testing• Patch 4 scheduled for delivery into MMS DEV in late August

– will use same CIM XML test data set as patch 2 & 3– focused mainly on outstanding defects

• Patch 5 has been added to allow ABB to continue developing & testing on the most recent version of the CIM schema and corresponding CIM XML test data file that ERCOT can provide

– tentatively scheduled for delivery into MMS DEV in late September– patch contents will be agreed to with ABB by 29Aug08; targeting S&B

defects, interface updates and additional workflow development & testing with the most recent CIM schema & data set

– CIM XML test data set version will be determined based on availability and accuracy of CIM XML test data sets received from NMMS; currently working with NMMS to move to v1.20


Project Update – MMS (cont.)

• MMS (ABB) Software Releases– MMS5 is the last scheduled MMS software release

• This release will be comprised of the following:– CIM XML import processing and testing end-to-end (defined in last bullet in this section)

– Bug fixes identified to ABB during testing– Remaining work on NPRRs (e.g., NPRR113, NPRR131)– Remaining SIG paper work (e.g., rounding, combined cycle – primary/alternate

handling)– Remaining software implementation changes based on testing (e.g.,

performance improvements, startup cost eligibility, SASM constraint modeling)• Trigger start for MMS5 is a CIM schema and CIM XML data file validated and

synchronized for consumption by EMS and MMS • Once the trigger is available, the following tasks will take place:

– ABB final review and refactoring of all workflows using the complete CIM schema & CIM XML file

– ABB completion of software updates for SIG papers, post baseline 2 NPRRs, performance and production readiness tasks, and outstanding defects

– Pre-FAT in Santa Clara– Release preparation & delivery to ERCOT– Loading and smoke testing in MMS DEV & MMS FAT– Final regression testing of MMS system in FAT

• MMS Processes & Procedures (DAM, RUC, Adjustment Period and Real-time)– MMS & MOS team members are leading the development of these documents – Reviews with the TPTF are scheduled for August, September and October meetings


CRR Project Update


Project Update – CRR

• Reviewed draft requirements for CRR Network Model One Line diagram with EMS project team to discuss optimizing development efforts.

• Planning final FAT stage with Nexant and CRR SMEs to test revised propagation of CRR Account Holder name changes within the CRR application.


COMS Project Update


Project Update – COMS

• Settlements/Data Agg/CSI – Product Testing at ERCOT – Development

• S&B/Data Agg: Completed over 97% of nodal coding and functionally verified– Outstanding code (to date): – Data Agg: Core rewrite complete. Validating with recent Product release

(issue below)– Internal/External Source Reports for Data Agg, Settlements, and CODIA

• CSI: Completed over 70% of Lodestar Bill Determinants and Tested– Outstanding code (to date): RUC and complex bill determinants

– Testing• Continue to test core system with upstream system changes• Continue to optimize batch cycles

– Major issues• Product Memory mgmt issue caused some Lodestar deliver delays.

Received a fix release on 08/13/2008 that is under test. Impact: Additional regression testing time added to the schedule.

• Need synchronous dataset from market systems (NMMS/EMS/MMS/CRR) running in an integrated environment before market level validation can begin (required for post Shadow Settlement Extracts)


• Registration and Disputes – Migrating to Integration Test – Registration 4 Release scheduled to begin integration test September 2, 2008

– Registration 4 Release includes:• Siebel changes for nodal (defect fixes)• Siebel to Lodestar interface (upgrade/change from zonal)• Lodestar to Siebel Settlement Calendar Look Up• Disputes API

– Major Issue• Potential for rework once integrated with other systems. Mitigation strategy to allow for

additional time in iTest for contingency. Impact: Release 4 now targeted to implement in December 2008 (zonal)

• Credit Monitoring and Management – FAT Testing – Build 3.1 (Vendor developed interfaces) in FAT 80% Complete

– Build 3.2 (Settlement and Billing / Commercial System Integrated Releases) in development targeting October 2008 delivery to FAT

– Major Issues• Finalization of detailed analysis and designs or changes from upstream systems has

potential to cause schedule delay. Mitigation strategy to finalize requirements by September and build in contingency time for rework.

Project Update - COMS (cont.)


Integration (EIP) Project Update


Integration highlights

• Replanning & Rework– Nearing completion of resynchronizing rework and final designs to accommodate

new delivery dates from end-point systems– No new scope changes; CDR services, Alerts & Notices were the last areas to add

to scope• External interfaces

– External Interface Specification v1.16 has finished review; comments have been addressed and the Sandbox services consistent with 1.16 were deployed on Aug. 21

– Web Service Usage shows reduced traffic a handful of new MPs connecting and improving successful submission rates

– Refresher Developer Workshop for Sep. 3

• Interfaces Status – Minor changes to interface status from last period;

• One new design for REG -> S&B• No new construction completions• Two deployments to Test; CDR adapter & CSI (MMS -> S&B)

• Diagram Key– Green/solid means that design, code or deployment is in maintenance and subject to rework– Red/dashed means design, code or deployment is incomplete

• Interface Rework– Green/solid means no expected rework because the final system or final system component has been integrated– Red/dashed means expect rework because final system is not available and interfaces may change


Design metric – 97%

Nodal has 10 major end-point systems, 36 Interfaces, 57 major integration components and around 400 Information Flows

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


Construction metric – 85%

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


27 34

EWS

25

3

35

31,36

31,36

IntegrationServices








































Remaining work

OS <-> EMS being constructed by EMS teamNMMS -> MMS CCT is incompleteS&B -> Reg for disputes calendarNew disputes API in construction


Deployed to Testing metric – 50%

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


27 34

EWS

25

3

35

31,36

31,36

IntegrationServices









































Rework – 5% 1 component is final

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


27 34

EWS

25

3

35

31,36

31,36

IntegrationServices









































Web Service UsageUpdate to Aug 15, 2008


Additional Detail on Web Service Usage

• During the health check in May, the statement was made that the strategy is working externally. More information was requested to illustrate whether the market was exercising all of the services and therefore business processes

– The detail verifies the statements made at the time that most transactions were COP and TPO

• The following results provide counts of success and failure for all transactions

– First chart indicates volume of successfully & unsuccessfully invoked services

– 2nd & 3rd charts show the most frequent successful and unsuccessful processes.

– Y scale is logarithmic, X scale shows all transaction types for two graphs


Transactions volumes – 227k hits by 315 entities at 91% overall success rate

T – successful invoked transactionsF – unsuccessfully invoked transactionsThere were 605 hits on July 4th

Success rate improved to 98% over last two weeks. Fewer new entities in the last 2 weeksVolumes have decreased over the last few weeks compared to when the EDS tests were running

Transaction volumes

0

5000

10000

15000

20000

25000

12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

Week #

Fre

qu

ency

F

T


30 most frequent correctly invoked processes

Top 30 Successful Process

1

10

100

1000

10000

100000

getB

idSet

crea

teTPO

crea

teCOP

getA

wardS

et

crea

teOS

getO

utageS

et

crea

teEne

rgyB

id

crea

teSAAS

crea

teW

indF

oreca

st

crea

teASOffe

r

crea

teOutag

e

MPOne

UNK

crea

teEOO

getM

CPCs

crea

tePTP

crea

teET

getLM

Ps

crea

teAST

crea

teCT

crea

teIN

CDEC

crea

teCRR

getA

SObliga

tions

crea

teSS

getS

PPs

getS

yste

mSta

tus

getM

arke

tTot

als

getU

nitAva

ilabil

ities

getA

ggre

gate

dASOfferC

urve

s

getC

ompe

titive

Constr

aints

getA

SSyste

mPlan

Transaction

Fre

qu

ency


30 most frequent incorrectly invoked processes

Top 30 Failed Process

1

10

100

1000

10000

100000

getB

idSet

crea

teCOP

crea

teOutag

e

getS

PPs

getLM

Ps

crea

teTPO

getT

otalA

SOffe

rs

crea

teASOffe

r

getO

utageS

et

crea

teUNK

getA

wardS

et

crea

teEOO

getT

otalE

nerg

y

crea

teEne

rgyB

id

getM

CPCs

getA

SSyste

mPlan

getA

ggre

gate

dASOfferC

urve

sge

t

crea

teAST

crea

teOS

crea

tePTP

crea

teSAAS

getLo

adFor

ecast

getR

epor

ts

getA

SObliga

tions

getM

arke

tTot

als

getB

inding

Const

raint

s

crea

teET

crea

teCRR

getS

tartu

pShu

tdow

nIns

tructi

ons

Transaction

Fre

qu

ency


Integration Testing (INT) Project Update


Project Update – INT

Integration Release Planning / Nodal Integrated Schedule– Working with Project Managers to understand software deployments for system

to system Integration Testing– Detailing Integration Release Windows “Buckets” to align interface and software

compatibility for Integration Testing– Working with the EDS team to align dates with delivered functionality– Estimating time for Performance, Security, and End to End testing– Supporting Program efforts for definition and collection of datasets to support

Integration Testing

Functionality, Reports, and Extracts Testing– Input and output data validation of CMM integration tables; including regression

testing of Credit Calculations– Settlement Extracts, data warehouse (EDW) replication and reports testing– Current Day Reports testing– MIS Portal testing

Integration Testing– Installing and testing of latest software released for Integration testing

• EMS5 Internal Interfaces to the Market and Settlements systems • MMS4 system installed and running for External Web Services and

downstream interface testing• Updated External Web Services code to support MMS4 (EIS1.15)


Questions?

August 25, 2008 TPTF Nodal Status Report: Projects Status Updates Adam Martinez.

Documents

Transcript of August 25, 2008 TPTF Nodal Status Report: Projects Status Updates Adam Martinez.