Proposed AMIT SMT Methodology and Release Strategy

March 9, 2010

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

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

SMART METERTEXAS

Proposed Enhancements to Smart Meter Texas Methodology

Enhanced Methodology Overview

Scope - AMIT1.Functionality Matrix and Priorities2.Business Functional Flows3.Business Process Inventory4.Release Critical Success Factors

Business Analysis - AMIT1.Business Requirements2.Use Cases

* Enhanced Deliverables in Red* Existing Deliverables in Black

Functional Design – SMT Team1.Requirements Traceability Matrix2.Interfaces3.Logical Data Model

Technical Design – AMIT & SMT Team1.Technical Requirements Definition and Flows2.Technical Specifications3.Physical Data Model

Physical Design / Build / Test – SMT Team

1.Detail Code Design2.Code – Unit Test3.Data Base Design / Schemas

UAT Test – SMT Team1.Test Plan2.Test Scripts

User Interface Design – AMIT &SMT Team

1.Prototype OR2.Mock Up

COMMUNICATIONS

COMMUNICATIONS

1. Market Email Notices

2. SMT Status meetings

3. AMIT meetings

1. Market Email Notices

2. SMT Status meetings

3. AMIT meetings

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 Design Technical Design

Physical Design / Build / Test

UAT Test

User Interface Design p

COMMUNICATIONS

COMMUNICATIONS

New Scope Phase and Scope Deliverables

Functionality Matrix Example Deliverable:Function Release Residential

CustomerNon-

Residential User

Non-Residential Admin

REP User

REP Admin

TDSP User

TDSP Admin

Portal Host

Registration Register Residential R1 x Register Non-Residential User R1 (b) Register Non-Residential Admin R1 (a) Register REP User R1 H Register REP Admin R1 (b) Register TDSP User R1 H Register TDSP Admin R1 (b) Account Management Login R1 x X x x x x x Change Password R1 x X x x x x x Reset Password R1 x X x x x x x Logoff R1 x X x x X x x Approve REP Company R1 H Approve New Account R1 H H H Add New REP DUNs R1 H Approve New REP DUNs R1 H Alter Security for Account R1 H H H XMass Revoke REP (Mass Revoke any Company or DUNS)

R1 x

Update Company Profile R1 H H H View Your Own Company Profile R1 x x x x x x xUpdate Personal Account Profile R1 x x x x x x x xSetup ESIIDs Attach/Detach Single ESIID R1 x x Attach/Detach Multiple ESIIDs R1 x x View ESIID Access R1 x x x x x x x xRemove for Dispute M1 H x

(a) limited to 1 Admin(b) unavailable

H – Host enabled in the 3/15 Release

R1

New Scope Phase and Scope Deliverables

Business Functional Flow Example Deliverable:

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

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

SMART METERTEXAS

Proposed Change Control Process

Change Control Process

AMIT or Market Participant Fills Out and Submits Change

ControlDetail Request to

PUCT

PUCT Assigns Change Control

Number and Enters in Change

Control Log

AMIT Reviews Change Control Detail Requests

at 1st Monthly AMIT Market Change Control

Meeting

Archive Change Control Detail

Request and Mark Change Control Log as Rejected

AMIT Approv

e / 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 2nd

Monthly AMIT Market Change Control

Meeting

Archive Change Control Detail

Request and Mark Change Control Log as Rejected

PUCT Approv

e / Reject

Approve

Reject

Refine Priority and Define Release for

Change During the 2nd 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 Approv

e / RejectReject

Approve

Change Control Form – Detail Request from Market

Change Control Form – Impact Analysis

Change Control Form – Time and Cost Estimates

Change Control Form – Approve or Reject Sign Off

SMART METERTEXAS

Proposed Issue Escalation Process

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

COMMUNICATIONS

1. Market Email Notices

2. SMT Status meetings

3. AMIT meetings

1. Market Email Notices

2. SMT Status meetings

3. AMIT meetings

SMART METERTEXAS

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

Proposed AMIT Methodology and Next Steps

Thank You For The Opportunity To Discuss

SMART METERTEXAS