Lead from the front Texas Nodal 1 EDW Update to TPTF November 27, 2007 Janet Ply, PhD EIS Nodal EDW Project Manager
Lead from the front Texas Nodal 2 Topics ERCOT Reporting Requirements EDW Scope Dependencies EDW Project Team Organization Current work in progress Questions
Lead from the front Texas Nodal 3 ERCOT Reporting Requirements Protocols Nodal/Zonal Market Guides Nodal Data Services Master List Business/ Market Reqts EDW Real Time Reports Notifications Alerts Market Documentation Extracts Replication Source System Reports Data Marts Reports Lodestar Parsing Reqts DMT
Lead from the front Texas Nodal 4 ERCOT Business Users Work with Market Participants to gather requirements Document requirements using templates for extracts and reports Prioritize requirements Work with EDW team to define EDW scope
Lead from the front Texas Nodal 5 Current EDW Scope Derived from NDSML v4.7 COMS: –NODAL: Reports: 3 Extracts: 6 Complexity is based on batch –Zonal/Nodal Modify: Reports: 0 Extracts: 6 –Web services project for ad hoc queries Modify 7 of 15 queries –Zonal will retire: retirement strategy after settlement billing is complete (after go live) –Replication of Lodestar, Siebel source systems
Lead from the front Texas Nodal 6 Current EDW Scope Derived from NDSML v4.7 Operations: (Estimates) –EMS/PI: Replication by EDW Reports: 65 (includes 33 in Section 8) Extracts: 11 –MMS: Replication by EDW Reports: 17 Extracts: 3 –Outage Scheduler: Replication by EDW Reports: 2 Extracts: 0 –CMM: Replication by EDW and MIR archival by EIS –CRR: Replication by EDW and MIR archival by EIS –NMMS: No EDW scope (MIR archival by EIS)
Lead from the front Texas Nodal 7 Schedule Dependencies for EDW COMS –Finalized data flow and batch schedule from Lodestar –Waiting on those who are testing Lodestar settlement –Requirements completion by Feb 25, 2008 Operations –All requirements from OPS complete by Feb 1, 2008 –EMS: dependent on stable EMS feed from Nodal data source –CMM: infrastructure issues currently being investigated; replication requirements due by December 15, 2007 –NMMS: No EDW dependencies –CRR: Replication requirements by December 3, 2007 –MMS: Waiting on replication requirements from Technical Architect – no commitment to a date –PI: dependent on stable PI feed from Nodal data source and ETL implementation –Outage Scheduler: FAT completion by January 21, 2008
Lead from the front Texas Nodal 8 EDW Project Team NDSML Jane Cates COMS Reqts J Ashbaugh PI EMS MMS CRR CMM PM Janet Ply EMS, PI, MMS John Messer Siebel, L* Chandra Ramireddy CRR, CMM, OS, NMMS, Parsing S. Krishnaswamy DBA Architect B. Hanley Technical Architect Bob Blackard ITEST Rao Kondapalli Developer Durga Viswanatha Developer Mo Nasim ETL John Michael Project Controller. Becky Brecht Documentation Amy Apodaca B. Groenewald DW Analyst Len Sweatman Ops Reqts Isabel Flores Section 8 EDW EIS COMS Sr. Data Modeler Tom Kornegay DW Analyst (OPEN) Replication S. Mahableshwarker NMMS DB Developer (Open) Lodestar Siebel DB Developer (Open) Extracts Linc Zhu Sr. Data Modeler (OPEN) Delivery Assurance PMO TPTF MIS Adam Martinez Outage Sched DW Analyst (OPEN) Cognos Reports (OPEN) Developer Durga Viswanatha Developer Durga Viswanatha DW Analyst (OPEN) Developer Mo Nasim Extracts Linc Zhu Extracts Gary Schulte Extracts/Rpts Chandra Ramireddy Extracts/Rpts S. Krishnaswamy Extracts Gary Schulte DB Developer Jai Kanuri Developer Durga Viswanatha ETL John Michael
Lead from the front Texas Nodal 9 Other Scalability concerns are addressed by the Enterprise Architecture team Data Dictionary items are included in the User Guides Data frequency is determined by the business, based on input from MPs as well as protocols
Lead from the front Texas Nodal 10 Questions?