2 Steering Committee February 2012 Report Agenda ► Monthly Updates ► Release Status Update ► Deployment Status Update ► Schedule Update ► Deployment Update ► Budget Status – Expenditures by Workstream ► Budget Status – Benefits ► Issues / Risks Summary ► Program Metrics ► Appendix ► Project Deployment Plan Progress ► Contingency Reconciliation ► SmartMeter TM Acronyms
3 Steering Committee February 2012 Report Release Status Update Challenges Actions/Status EACFunded BudgetITDScopeScheduleResourcesIssuesRisks IT Releases: January 31, 2012 Release 1 Release 2 Release 3 Overall ▪ IT continues to execute against the plan produced as output from the Reconstruct effort. HAN enablement and Peak Time Rebate roadmaps are in progress. Release 1 ▪ Provide model office, exception management for interval billing, and performance & scalability improvements. Release 2 ▪ Complete the integration of SmartMeter TM data to the existing outage systems. This includes using the meter “last gasps,” “restoration,” and meter ping capabilities. Added electric head-end system upgrade to scope of this release to enable Secure Port and firmware push. Remote Connect/Disconnect phase 2 (RCD) and performance and scalability improvements are also part of this release. Release 3 ▪ Improvements to meter data exception handling, NEMs deployment, scalability improvements for the data warehouse, and tracking of momentary outages. Overall ▪ Project stabilization work complete for all components except MV90 and NEMs. Release 1 ▪ Deployment of Release 1 on 7/29/11 with no issues. ▪ Project stabilization complete 9/1/11. Release 2 ▪ Deployment complete 9/30/11. ▪ Project stabilization complete 11/30/11. Release 3 ▪ Deployment of all in-scope functionality except MV90 completed by 11/30. ▪ Stabilization for all deployed components except NEMs is complete. ▪ Resolution for MV90, NEMs and FSU upgrade (March 2012) issues underway. ▪ Currently testing delivered MV90 MDM vendor fixes ▪ Preparing documentation for MV90 controlled deployment. ▪ Awaiting resolution proposal for NEM MDM issues from vendor (ETC 2/29).
4 Steering Committee February 2012 Report Deployment Status Update Actions/Status Challenges EAC2012 Forecast (2012 EOY / CPI) ScopeScheduleResourcesIssuesRisks Deployment: January 31, 2012 Endpoints (2012 YTD) * Gas Network (2012 YTD) Electric Network (2012 YTD) * 2012 Schedule and installation targets under review Endpoints ▪ Workflow slow down. ▪ Increased rate of ‘Unable-To-Completes’ due to non-standard meter installations in heavy urban areas and access refusals. ▪ Cost-per-install higher than planned due to resource mix. Electric Network ▪ Complete electric network deployment, initial design scope. ▪ Whether additional electric network is necessary is subject to ongoing review. Gas Network ▪ Complete gas network deployment, initial design scope. ▪ Whether additional gas network is necessary is subject to ongoing review. Endpoints ▪ Working with installation contractor to update 2012 deployment schedule. ▪ Working with installation contractor to routinely review UTCs and resolve them. ▪ T-300 team assigned to supplement Gas Meter Swivels and Exchanges in San Francisco and resolving 1S/2S electric exchanges. Electric Network ▪ Working with technology supplier and internal stakeholders to address network coverage in ‘hard-to-reach’ areas. Gas Network ▪ Network coverage issue to be resolved before the end of deployment.
5 Steering Committee February 2012 Report 2012 Legend Schedule Update Benefits Field Delivery Approved Milestone (delay) ‘Initial Design’ Network Deployed Meter Reading Reductions (ITD) As of 1/31/12 Forecasted Milestone (delay) Milestone MetBaseline Milestone Forecasted Milestone (early) Milestone TBD 590 Positions Captured 9.0M Meters/Modules in service Jun IT Release Deployment Release 2 Release 3 SM Operations Center Release 1 Apr May Oct Sep Aug Jul NovDec SMOC Phase 1.0 Deploy Remote Connect Disconnect Outage Identify & Scope Exception Management Improvements and NEMs deploy Exception Management Improvements and Momentary Outage Tracking Performance & Scalability Improvements Exception Management Improvements Electric ‘head-end’ system upgrade Feb Jan Mar 2011
6 Steering Committee February 2012 Report Deployment Update As of February 3, 2012 #s as of 02/3/12 2012 Targets under review
7 Steering Committee February 2012 Report 2012 Budget Status – Expenditures by Workstream Year-to-Date Variance Explanations: Unfavorable YTD capital variance ($0.7M) primarily due to timing of IT spend of -$1.1M (#5), offset by fewer meter/module installations of $0.6M (#3). Favorable YTD expense variance ($0.6M) due to timing associated with: 1) underruns in Customer of $0.3M (#10) and Business Operations/PMO of $0.2M (#7). *Revised based on final 2012 deployment schedule and timing. *
8 Steering Committee February 2012 Report 2012 Budget Status – Benefits
9 Steering Committee February 2012 Report Issues Summary Target Resolution Date IssueImpactStatus Summary Ongoing Increasing number of installations affected by access refusals. Increased costs, increase in unable to complete (UTC) back-log, customer change management. Pursuing operational improvements to increase efficiency of UTC resolution. Ongoing engagement with customers across multiple communication channels to enhance customer understanding of SmartMeter TM program and benefits. Customer option to temporarily delay SM upgrade being offered, pending CPUC decision on PG&E’s opt-out application.
10 Steering Committee February 2012 Report Risks Summary #Created OnIPScore Prev. Score RiskImpactStatus Summary Assoc. Issue 19/30/20115420 Increased forecast deployment costs and external resources requirement Key drivers: Delays in deployment, resource availability and installation complexity Increased installation costs and contract resources required to complete remaining installations effectively and timely Working with Sourcing and suppliers to complete contracting process. Pursuing other identified opportunities to offset additional installation costs and increase installation efficiency within ongoing operations. 34/4/20085315 Business processes enabled by new technology may not perform as intended. Key drivers: Increased data volume and validation, underlying business processes. Billing errors, customer complaints, inability to meet endpoint deployment goals. Continuing to monitor technology performance and identifying mitigations to resolve any identified technology performance issues. Meter transition process checks updated to include new integrated standards with supplier for validating network design, meter connectivity and read performance. Planning for Full Deployment/Interval Billing via functionality deployments and additional process capability initiatives through 2011 underway. 49/1/20115315 Network deployment and performance in ‘hard-to-reach’ areas can not be completed successfully. Key drivers: Network performance in ‘hard-to-reach’ areas and availability of alternate solutions. Deployment delays, resource planning and increased costs. Pursuing resolution of network coverage in ‘hard-to-reach’ areas with technology supplier, including potential alternate network solutions. Finalization of network design/equipment mix to complete network deployment in process with suppliers.
11 Steering Committee February 2012 Report Program Metrics #s as of 01/31/12 2012 Targets under review
12 Steering Committee February 2012 Report Project Deployment Plan Progress 2012 Targets under review
13 Steering Committee February 2012 Report Contingency Reconciliation
14 Steering Committee February 2012 Report SmartMeter TM Acronyms