1 / 11

ERCOT Release Bucket Proposal - Mitigating Impact and Early Delivery

This document provides an overview of the ERCOT Release Bucket Proposal, including project status, planning phase, next steps, and recommended task force items. It outlines the proposed release buckets to mitigate impact during Nodal Code Freeze and ensure early delivery of requirements.

smithrachel
Download Presentation

ERCOT Release Bucket Proposal - Mitigating Impact and Early Delivery

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. PR70007 – MarkeTrak Ph2 ERCOT MarkeTrak Task Force January 24, 2008

  2. Overview • Project Status - Planning • Next Steps • ERCOT Release Bucket Proposal

  3. PR70007_01 Project StatusERCOT

  4. Project Phases and Deliverables

  5. Planning Phase Status

  6. Next Steps

  7. Next Steps/ Recommended Task Force Items

  8. Release Bucket Proposal

  9. Execution Phases Example – ERCOT ERCOT would like to propose the following release buckets in order to mitigate impact with Nodal Code Freeze (03-06 and 09-12 Siebel lock down) and provide early delivery of some requirements while working on delivery of more complex requirements. The actual release dates will be confirmed in early March. MarkeTrak Phase Breakdown Criteria (see Release_Proposal.xls) Release I (5 Weeks Development) -MT GUI and minimal API Release 2 (19 weeks Development) -IAG Workflows -DEVLSE Automation -New Adapter/Interfaces Release 3 (4 weeks Development) -API (Complex changes) -New Workflow fields -Integration changes Release 4 (16 weeks Development) -New Workflows -Integration changes -Bulk Insert templates -Reporting/TML

  10. “DRAFT” Execution Example Timeline 4th Qtr 2007 1st Qtr 2008 2nd Qtr 2008 3rd Qtr 2008 4th Qtr 2008 1st Qtr 2009 Timeline DRAFT Execution Schedule **Dates will be confirmed in early March (contingent on Nodal) Planning 06/2008 Release 1 Release 1 07/2008: Release 2 Release 2 08/2008: Release 3/ Release 2 Contingency Release 3 11/2008: Release 4 Release 4 02/2009 Release 5 Release 5 (Contingency Date Due to Nodal and Stabilization)

  11. Questions

More Related