Presentation is loading. Please wait.

Presentation is loading. Please wait.

Proposed AMIT SMT Methodology and Release Strategy March 9, 2010.

Similar presentations


Presentation on theme: "Proposed AMIT SMT Methodology and Release Strategy March 9, 2010."— Presentation transcript:

1 Proposed AMIT SMT Methodology and Release Strategy March 9, 2010

2 Objectives Review Proposed Enhancements to AMIT SMT Methodology Review proposal for Change Control Process for SMT Application Development Review proposal for Issue Escalation Process Review and Gain Consensus on Proposed AMIT Process Methodology and Next Steps

3 AGENDA Proposed Enhancements to AMIT SMT Methodology – Enhanced Methodology Overview – New Scope Phase and Scope Deliverables – Technical Design Phase New Deliverable Proposed Change Control Process – Change Control Process – Change Control Form Proposed Issue Escalation Process Proposed AMIT Methodology and Next Steps – Release 1 Functionality Matrix – Release 1 Business Process Flows – Release 1 Business Technical Flows – Release 2 Critical Success Factors – Future Business Requirements Review and Prioritization

4 SMART METER TEXAS Proposed Enhancements to Smart Meter Texas Methodology

5 Enhanced Methodology Overview Scope - AMIT 1.Functionality Matrix and Priorities 2.Business Functional Flows 3.Business Process Inventory 4.Release Critical Success Factors Business Analysis - AMIT 1.Business Requirements 2.Use Cases * Enhanced Deliverables in Red * Existing Deliverables in Black Functional Design – SMT Team 1.Requirements Traceability Matrix 2.Interfaces 3.Logical Data Model Technical Design – AMIT & SMT Team 1.Technical Requirements Definition and Flows 2.Technical Specifications 3.Physical Data Model Physical Design / Build / Test – SMT Team 1.Detail Code Design 2.Code – Unit Test 3.Data Base Design / Schemas UAT Test – SMT Team 1.Test Plan 2.Test Scripts User Interface Design – AMIT &SMT Team 1.Prototype OR 2.Mock Up COMMUNICATIONS 1.Market Notices 2.SMT Status meetings 3.AMIT meetings 1.Market Notices 2.SMT Status meetings 3.AMIT meetings

6 New Scope Phase and Scope Deliverables The Scope Phase Provides the Following: Defines Solution Purpose and Functionality Provides Foundation for Release Management and Change Control Provides Direction and Priorities for the Business Analysis phase and all Subsequent Phases Facilitates Consensus and Common Understanding Among Participants Defines Release Critical Success Factors Scope Business Analysis Functional DesignTechnical Design Physical Design / Build / Test UAT Test User Interface Design p COMMUNICATIONS

7 New Scope Phase and Scope Deliverables Functionality Matrix Example Deliverable: FunctionReleaseResidential Customer Non- Residential User Non-Residential Admin REP User REP Admin TDSP User TDSP Admin Portal Host Registration Register ResidentialR1x Register Non-Residential UserR1 (b) Register Non-Residential AdminR1 (a) Register REP UserR1 H Register REP AdminR1 (b) Register TDSP UserR1 H Register TDSP AdminR1 (b) Account Management LoginR1xXxxxxx Change PasswordR1xXxxxxx Reset PasswordR1xXxxxxx LogoffR1xXxxXxx Approve REP CompanyR1 H Approve New AccountR1 H H H Add New REP DUNsR1 H Approve New REP DUNsR1 H Alter Security for AccountR1 H H HX Mass Revoke REP (Mass Revoke any Company or DUNS) R1 x Update Company ProfileR1 H H H View Your Own Company ProfileR1 xxxxxxx Update Personal Account ProfileR1xxxxxxxx Setup ESIIDs Attach/Detach Single ESIIDR1x x Attach/Detach Multiple ESIIDsR1x x View ESIID AccessR1xxxxxxxx Remove for DisputeM1 Hx (a)limited to 1 Admin (b)unavailable H – Host enabled in the 3/15 Release R1R1

8 New Scope Phase and Scope Deliverables Business Functional Flow Example Deliverable:

9 New Scope Phase and Scope Deliverables Release Critical Success Factors Example Deliverable: Release Critical Success Factors for Smart Meter Texas Release 1 The solution must provide a common web portal The user online interface must be intuitive and easy to use by consumers The solution must provide a secure environment for confidentiality, user access and data transfer The solution must provide the information necessary in which the customer can make an informed decision regarding consumption The solution must be provide a common format to manage meter and In- Home Device functions The solution must be based on existing open industry standards The solution must be based on a common interoperable platform

10 Technical Design Phase New Deliverable Technical Requirements Definition and Flow: Typical information Portal access, Web service, FTP Push to REP, Pull from SMT Non-functional requirements

11 SMART METER TEXAS Proposed Change Control Process

12 Change Control Process AMIT or Market Participant Fills Out and Submits Change Control Detail Request to PUCT PUCT Assigns Change Control Number and Enters in Change Control Log AMIT Reviews Change Control Detail Requests at 1 st Monthly AMIT Market Change Control Meeting Archive Change Control Detail Request and Mark Change Control Log as Rejected AMIT Approve / Reject Approve Reject SMT Team Conducts Impact Analysis Including: Functions Impact, Time Estimate, and Cost Estimate AMIT Defines Priority and Potential Release for Change at 1st Monthly AMIT Market Change Control Meeting SMT Team Submits Impact Analysis Including the Time Estimate, and Cost Estimate to PUCT Review Change Control Detail Requests & Impact Analysis at the 2 nd Monthly AMIT Market Change Control Meeting Archive Change Control Detail Request and Mark Change Control Log as Rejected PUCT Approve / Reject Approve Reject Refine Priority and Define Release for Change During the 2 nd Monthly AMIT Market Change Control Meeting Acquire Signatures on Approved Change Control Form and Submit to SMT Team for Project Planning Poll Market to Identify if a Market Participant Wishes to Fund the Change Market Approve / Reject Reject Approve

13 Change Control Form – Detail Request from Market

14 Change Control Form – Impact Analysis

15 Change Control Form – Time and Cost Estimates

16 Change Control Form – Approve or Reject Sign Off

17 SMART METER TEXAS Proposed Issue Escalation Process

18 Proposed Issue / Requirements Clarification Escalation Process for Application Development SMT Team or AMIT Fills Out and Submits Issue or Clarification Description Form to PUCT Jenina Manages Issue or Clarification Documentation for Review at Next AMIT Meeting AMIT Reviews Issue and Selects / Refines Resolution Option SMT Team Develops Proposed Resolution Options with Impacts to Timeline and Cost AMIT Submits Resolution to SMT Team COMMUNICATIONS 1.Market Notices 2.SMT Status meetings 3.AMIT meetings 1.Market Notices 2.SMT Status meetings 3.AMIT meetings

19 SMART METER TEXAS Next Steps

20 Release 1 Functionality Matrix Release 1 Business Process Flows Release 1 Business Technical Flows Release 2 Critical Success Factors Future Business Requirements Review Proposed AMIT Methodology and Next Steps

21 Thank You For The Opportunity To Discuss SMART METER TEXAS


Download ppt "Proposed AMIT SMT Methodology and Release Strategy March 9, 2010."

Similar presentations


Ads by Google