100 likes | 119 Views
This document provides an overview of the ERCOT EDW Project, including reporting requirements, project scope, dependencies, and the project team organization. It also discusses current work in progress and invites questions.
E N D
EDW Updateto TPTFNovember 27, 2007Janet Ply, PhDEIS Nodal EDW Project Manager http://nodal.ercot.com 1
Topics • ERCOT Reporting Requirements • EDW Scope • Dependencies • EDW Project Team Organization • Current work in progress • Questions http://nodal.ercot.com 2
ERCOT Reporting Requirements Notifications Extracts EDW Protocols Nodal/Zonal Nodal Data Services Master List Business/Market Reqts Market Guides Reports Real Time Reports Replication Data Marts Alerts Lodestar Parsing Reqts Source System Reports DMT Market Documentation http://nodal.ercot.com 3
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 http://nodal.ercot.com 4
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 http://nodal.ercot.com 5
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) http://nodal.ercot.com 6
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 http://nodal.ercot.com 7
EDW Project Team TPTF MIS Adam Martinez PMO NDSML Jane Cates Delivery Assurance PM Janet Ply Project Controller. Becky Brecht Technical Architect Bob Blackard Documentation Amy Apodaca EDW EIS COMS Sr. Data Modeler Tom Kornegay CRR, CMM, OS, NMMS, Parsing S. Krishnaswamy ITEST Rao Kondapalli Siebel, L* Chandra Ramireddy DBA Architect B. Hanley Ops Reqts Isabel Flores COMS Reqts J Ashbaugh EMS, PI, MMS John Messer B. Groenewald Developer Mo Nasim Developer Durga Viswanatha Developer Durga Viswanatha Developer Mo Nasim PI Lodestar Extracts Linc Zhu Replication S. Mahableshwarker DW Analyst (OPEN) DW Analyst (OPEN) Developer Durga Viswanatha Siebel EMS Extracts Gary Schulte DB Developer Jai Kanuri DB Developer (Open) DW Analyst Len Sweatman MMS Extracts/Rpts Chandra Ramireddy Extracts Gary Schulte ETL John Michael CRR Extracts/Rpts S. Krishnaswamy Extracts Linc Zhu DB Developer (Open) CMM Sr. Data Modeler (OPEN) NMMS Developer Durga Viswanatha DW Analyst (OPEN) ETL John Michael Section 8 Cognos Reports (OPEN) Outage Sched http://nodal.ercot.com 8
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 http://nodal.ercot.com 9
Questions? http://nodal.ercot.com 10