1 / 18

Emerging Issues

Emerging Issues. Enterprise Data Warehouse (EDW). Enterprise Data Warehouse (EDW) Overview. Agenda Architecture Overview Project Plan Overview LodeStar Extract Transition. Enterprise Data Warehouse (EDW) Overview.

bunyard
Download Presentation

Emerging Issues

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Emerging Issues

  2. Enterprise Data Warehouse(EDW)

  3. Enterprise Data Warehouse (EDW) Overview • Agenda • Architecture Overview • Project Plan Overview • LodeStar Extract Transition

  4. Enterprise Data Warehouse (EDW) Overview • The EDW consists of three major architectural components, all optimally designed for stability, security and recoverability. • Replicated Source System (RSS) • Captures insert, update, and delete activity in the source system • Maintains a ‘mirror’ of the source system – does not store historical data • Significantly reduces impact on the source system • Provides near real-time reporting

  5. Enterprise Data Warehouse (EDW) Overview • Operational Data Store (ODS) • Provides ‘As Of’ querying by recording when a record was inserted or updated/deleted in the source system • Enables record versioning via Point-in-Time Selectivity (PITS) • Records intra-day history by loading all record activity from the RSS • Provides an optimized extracting and reporting environment

  6. Enterprise Data Warehouse (EDW) Overview • Data Warehouse (DW) • Integrates data from multiple source systems • Organizes data by business subject area • Relates data across subject areas • Facilitates effective and efficient reporting solutions for MP support

  7. EAI ODS SEIBEL ODS Siebel ODS SEIBEL ODS EMMS ODS LODESTAR ODS EDW Project: 2004 Deliverables PR-40042: Enterprise Data Warehouse PMO and IT PM Director: R Connell PM: A Esenkova EDW Application Foundation 3 8 EMMS Reports Ray Chase EDW Delivery Manager Business Intelligence Foundation 01: EMMS RSS (Q3) Lead: R Chase 5 02: Data Delivery Module (Q2) Lead: J Messer 2 6 L* Batch Extracts Data Delivery Module 03: EDW Application Foundation (Q3) Lead: R Chase 7 04: LodeStar ODS Transition (Q3) Lead: A Sooley 4 05: BI Foundation (Q4) Lead: C Ryan L* RSS EMMS RSS 1 06: LodeStar Extracts (Q4) Lead: J Messer LODESTAR EMMS 07: EMMS ODS (Q4) Lead: A Sooley Settlement & Billing Load Generation Outage Solution Generation Congestion Energy Schedule Ancillary Service Resource Plan Balancing Energy ESIID RID 08: EMMS Reports (Q4) Lead: P Ohlendorf

  8. Extract Transition: Data Archive to EDW • Approach • Solid collaboration with business users on requirements gathering • Input from market participants to confirm requirements and recommendations for technical implementation • Formation of IT and business team for validation • Simulation of MP loading process to inform technical guidelines • Thorough documentation for MP processing and client services support

  9. Extract Transition: Data Archive to EDW • Methodology • Logic auditing automated • Posting process auditing with meta data capture (i.e., what records went out to which MPs in a specific extract) • Full recovery built into the logic and processing – enabled through EDW architecture • Designed with reusable foundation for extracting and reporting

  10. Thank You

  11. Program Area Teams(PAT) Overview

  12. Program Area Teams Overview • Program Area Teams (PATs) • The overall goal of the PAT internal organization is to support needs from the ERCOT Market and ERCOT internally related to areas of operation within ERCOT systems. • Specific objectives: • Reduce the number of changes/release to ERCOT systems • Provide a means to affectively managing the change requests received from the market and internal ERCOT • Support Operational Area goals • Support Project Management goals • Support IT goals • Support Program Management goals

  13. Program Area Teams “PAT” Composition ERCOT Strategic Review Team Representatives from PATs Business IT Sponsor Sponsor STRATEGIC TEAM BUS PMO IT • Strategic focus • 3m-3yr outlook Program Lead Vendor Lead CONTINUOUS ANALYSIS & REQUIREMENTS TEAM BUS Lead PMOIT Lead Market Rules, Vendor, Arch Lead Business Lead Release Lead IT Lead RELEASE TEAM BUS PM - PMO IT • Project and Release Focus

  14. Program Area Teams Strategic Review Team (All Strategic Team Members) Systems Operations Market Operations IT Operations Corporate Operations Strategic Team Strategic Team Strategic Team Strategic Team Continuous Analysis and Requirement Team Continuous Analysis and Requirement Team Continuous Analysis and Requirement Team Continuous Analysis and Requirement Team Release Team Release Team Release Team Release Team

  15. PAT Responsibilities Responsibilities Communications Strategic Review Team • Monitor requests: PUC, Market, Internal, PRRs • Prioritize cross-functional issues / projects • Coordinate X-functional efforts, schedules, $’s • Board • Officers Program Area • Prioritize program issues/impacts/projects • Develop program goals • Monitor program performance • Prog Review • Market Subcom • Cont Req Team Strategic Team BUS PMO IT • Manage project requests • Coordinate requirements • Detailed impacts • Monitor protocol updates • Recommend priorities • Strategic Team • Release Core Continuous Analysis & Requirements Team BUS PMO IT • Coordinate project teams • Assess CRs for release projects • Cont Req Team • Front-line Mgrs Release Team BUS PMO IT

  16. PAT Deliverables & Meetings Deliverables Meetings Strategic Review Team • Program area recommendations • Program Updates / Major Committees • Programs, Rules and Allocation • Program Review (monthly as part of Executive Meeting) Program Area • Yearly goals & performance metrics • Manage 3-year Program Plan • Roadmap / Release schedule • Program Review • (Attend Board, Subcommittees, • Program Review ) Strategic Team BUS PMO IT • Program Updates • Project Requests • Impact Analysis (cost-benefit-resource) • Requirements Specification • High-level Design • Project Charter • Tollgate • Project Placement, Scheduling and Update Meeting in Conjunction with Tollgate Meeting Continuous Analysis & Requirements Team BUS PMO IT • Release Updates • Cash Flow • Closure Signoff • Release/Project Kickoff • Project Team mtgs • Peer Review • Lessons Learned Release Team BUS PMO IT

  17. Apps Areas Program Area Teams and Focus Areas Systems Operations POS MOS MMS WMS ROS Market Operations Data Agg Load Profiling Metering Statements/Billing Registration ESI ID MIMO / TX SET WMS (new CMS or SBS) RMS IT Operations Data Warehouse Web Systems Trans Systems Hardware Network / SAN PRS TAC Corporate Operations Legal Finance HR Facilities Planning Strategy PRS TAC BOD Subcommittees & Communications

  18. Thank You

More Related