ERCOT and Utilicast Public Document www.utilicast.com February 17, 2009 Nodal Program Oversight Report 9 System Integration Assessment.

Slides:



Advertisements
Similar presentations
Module N° 4 – ICAO SSP framework
Advertisements

The Business Analyst and the SDLC
Program Management Office (PMO) Design
The Value of a Project Management Office Copyright: Kathy J. Lang, 2004.
Global Congress Global Leadership Vision for Project Management.
Global Business Blueprint Summary Presenters: Laurie Dempsey, CBP Lois McCluskey, eCP January 28, 2004.
Program Management Office “PMO”
1 LBNL Enterprise Computing (EC) January 2003 LBNL Enterprise Computing.
Managing the Information Technology Resource Jerry N. Luftman
1 April 2010 TX SET Timeline Project Conceptualization 11 weeks Market Requirements 12 weeks ERCOT Requirements 12 weeks Conceptual Design 6 weeks Detail.
Project Management Session 7
4. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the elements of project management and the responsibilities of a.
By Saurabh Sardesai October 2014.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Management Adrian Marshall.
Page 1 Program Management Office “PMO” Update Steve Wallace February 3, 2003.
Project Management Basics
Effective Programme Management
Development plan and quality plan for your Project
Planning. SDLC Planning Analysis Design Implementation.
Project Management and Scheduling
State of Kansas Statewide Financial Management System Pre-Implementation Project Steering Committee Meeting January 11, 2008.
Charting a course PROCESS.
18/21/20151 Instructor: Suprakash Datta (datta[at]cse.yorku.ca) ext Lectures: Tues (CB 122), 7–10 PM Office hours: Wed 3-5 pm (CSEB 3043), or by.
What is Business Analysis Planning & Monitoring?
Developing Enterprise Architecture
Project Management: Madness or Mayhem
Project Management Process Overview
Pre-Project Activities Text Chapters 5 and 6. Pre-Project Activities 1.Contract Review 2.Development Plan 3.Quality Plan.
Managing Projects using Oracle Project Management (PJT) & SPREADSHEETS Neeraj Garg Vice President, Client Services.
ERCOT and Utilicast Public Document ERCOT Board of Directors Meeting April 22, 2009 Nodal Program Oversight Report 10 – Infrastructure.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
April 9, 2009 Technical Advisory Committee Meeting Texas Nodal Program Implementation: Program Update Mike Cleary Sr. VP and Chief Technology Officer.
Strong9 Consulting Services, LLC 1 PMI - SVC I-80 Breakfast Roundtable Monthly Meeting Thursday, October 12, :00 am – 9:00 am.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
©Copyright OMRON Corporation All Rights Reserved A Step by Step Approach for Creating an Environment for Successful Projects IWFST2005 Nov. 8-10,
Market Implementation Board Presentation July – v1.1F 1 Texas Nodal Market Implementation ERCOT Board of Directors Meeting Program.
OPERATIONAL EXCELLENCE READINESS STAFFING STRATEGIES February 28, 2011.
Volvox Finance 2 How we will manage the Finance Angela Pettit – Contracts Officer.
Sherry Hicks VP, Global Implementation SafeGuard World International October 9, 2015.
A Strawman for Discussion by Dottie Stockstill & Greg Ramon Special ERCOT Board Meeting June 24, 2003.
Pre-Project Components
February 5, 2009 Technical Advisory Committee Meeting Texas Nodal Program Implementation: Program Update Trip Doggett.
Machine to Machine Interface Update 1 Machine to Machine Interface Update February 7th, 2007.
Reconfiguring Nodal Stakeholder Participation Presentation to the ERCOT Technical Advisory Committee Texas Nodal Transition Planning Task Force February.
BSBPMG501A Manage Application of Project Integrative Processes Manage Project Integrative Processes Unit Guide Diploma of Project Management Qualification.
Project Organization Chart Roles & Responsibilities Matrix Add Project Name.
Lead from the front Texas Nodal 1 Texas Nodal Market Implementation ERCOT Board Of Directors – August 15, 2006 TPTF Meeting August.
Stages of design  High level design  High level data structure  Architecture  Low level design-code design  Algorithms  Low level data structures.
Texas Nodal Program ERCOT Readiness Update TPTF June 23, 2008.
Long Term Move-In Move-Out Development Strategy August 19, 2002 DRAFT.
Project Management Overview U08784Software Project Management Rosemary Phillimore.
State of Georgia Release Management Training
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Project Management Processes for a Project
Project Management Why do projects fail? Technical Reasons
COMET Working Group Progress Report. Purpose of Report Provide Team Updates Potential Future Voting Items Draft Competitive Meter Ownership Timeline.
1 SCR756 – Enhancements to the MarkeTrak application –Fondly called - MarkeTrak Phase 3 –ERCOT CEO determined that SCR756 is not necessary prior to the.
Implementing Program Management Standards at Duke Energy.
Managing Multiple Projects Steve Westerman California Department of Motor Vehicles Steve Young Mathtech, Inc.
March 5, 2009 Technical Advisory Committee Meeting Texas Nodal Program Implementation: Program Update Trip Doggett.
Project Execution Methodology
Systems Analysis and Design in a Changing World, 4th Edition
2011 Prioritization Update to Market Subcommittees
Project Management Managing Project Execution
Project Management and Information Security
Description of Revision
{Project Name} Organizational Chart, Roles and Responsibilities
Presentation transcript:

ERCOT and Utilicast Public Document February 17, 2009 Nodal Program Oversight Report 9 System Integration Assessment

ERCOT and Utilicast Public Document2 Scope and Approach Scope The objective of Nodal Market Oversight Report Number 9 is to provide an independent assessment of the Nodal System Integration. Approach Current state of integration on the Nodal Program Integration scope and approach Integration project organization structure and resource plan Integration technical solution

ERCOT and Utilicast Public Document3 Nodal Program Components

ERCOT and Utilicast Public Document4 Findings Review AreaFindings Assess current state of integration on the Nodal Program The Nodal Program has made notable progress in:  Redefining the scope and objectives of the integration initiative consistent with requirements.  Developing and communicating a coordinated integration approach.  Assigning ownership and accountability for key integration deliverables.  Hiring knowledgeable and experienced personnel in key leadership roles. Integration testing is estimated at 5% complete. The tests completed to date are basic application connectivity tests. The business process based end- to-end testing has yet to be completed. Development of the technical data transfer solution EIP (Enterprise Integration Project - TIBCO data transfer solution) is estimated at 85%-90% complete. Some of the project teams have made progress in developing and testing the required application interfaces (EMS-MMS and COMS) and are therefore further ahead in integration. Review overall scope and approach of the Integration Project There were unrealistic expectations of the role, responsibilities and deliverables of the integration initiative. The formal components one would expect to find in an integration approach were poorly defined. Lack of communication on system specification changes has resulted in a high rate of system fixes and rework on the Enterprise Integration Project.

ERCOT and Utilicast Public Document5 Findings Continued Review AreaFindings Review Organization Structure and Resource Planning Limited leadership available on the integration team with knowledge of integrating complex solutions and understanding of nodal markets and electricity reliability. The integration resource plan was not well defined and seems excessive. Technical data transfer solution review The approach adopted for data transfer between applications has resulted in 3 separate technical solutions being developed.  TIBCO service orientated solution  Point-to-point data transfer  CSI TIBCO orchestration solution Based on our review, these solutions are consistent with program requirements. The specifications for volumes limits and package content managed by the external web services have not yet been fully defined. Consequently, there is a risk that transactions submitted by Market Participants may not be processed due to system constraints.

ERCOT and Utilicast Public Document6 Recommendations Because of the urgency of the Nodal Program and to expedite the management response, the Utilicast team communicated findings and made recommendations as they arose. Based on our findings we made the following recommendations and include the management response to date: RecommendationsManagement Response 1The application project teams should own and be accountable for developing and testing their application interfaces. The Nodal PMO has reassigned the ownership for interface development and testing to the application project teams. 2The scope of system integration testing (end-to- end testing) should be limited to confirming that the individual applications can operate as a single enterprise solution. The Nodal PMO is in the process of interviewing qualified candidates to lead this effort and develop the necessary test scripts. 3Clearly define and communicate the scope, objectives and expected deliverables of the core system integration components. The Nodal PMO has revised its approach for application interface testing and integration testing (end-to-end business scenario testing). This revised integration approach has been reviewed with the Project Managers, including the scope definition, roles and responsibilities of the Project Teams, and process for aligning approach with project schedules and budgets. 4Assign a qualified integration project lead.The ERCOT executives and the Nodal PMO have assigned a qualified project manager to this role. 5Appoint qualified leaders with clear ownership of clearly defined deliverables to the key system integration roles. ERCOT has posted the leadership positions and has received a number of responses. To date three offers have been extended successful candidates. The goal is to fill these positions with resources that have previous nodal market implementation or large- scale system integration experience.

ERCOT and Utilicast Public Document7 Recommendations Continued RecommendationsManagement Response 6Update project plans and budgets based on revised integration scope, objectives, roles and responsibilities. ERCOT will be revising their project plan and schedule to align with the revised integration testing approach. 7Define and implement (in conjunction with the market Participants) the specification for the volume and content of information transmitted over external web services. 8Build and configure a dedicated integration test environment. Project Manager has been assigned to this initiative. Currently in the planning phase with an expected delivery date of March Review access policies and IT controls for non-production environments. Project Manager assigned to recommendation 8 will also be responsible for reviewing access and control policies.