Electronic Outage Reporting Proof Of Concept Report July 8, 2002

Electronic Outage Reporting & the Spirit of SB7 b Must allow the CR to take the call & send data electronically to the TDSP b Should allow for status information to be passed to the customer at the time of the call to the CR b Should allow for near real time delivery of the data to the TDSP

Electronic Outage Reporting Recommendation

Common Standard

Assumptions as originally presented to RMS, 10/01: 4 All Electronic Outage transactions will be driven by an ESI ID. 4 CR’s will need to develop a process for handling customers who call the wrong CR. 4 The TDSP will reject Outage transactions: If the TDSP is not the owner of the ESI ID.If the TDSP is not the owner of the ESI ID. If the data received is invalid, unreadable, or the record is corrupted.If the data received is invalid, unreadable, or the record is corrupted.

Assumptions as originally presented to RMS, 10/01: 4 Telecommunication connections to the TDSP will be the financial responsibility of the CR. 4 Communication Type, Carrier, and Size will be a bilateral agreement between the CR and TDSP. 4 Data elements & requirements were established by previous workshops & Texas SET

Assumptions as originally presented to RMS, 10/01 : 4 The Transmit/Receive process will be fast enough to provide status information to the customer during the phone call. 4 The CR will send an Electronic Outage transaction to the TDSP for every valid customer contact received. 4 The TDSP will issue one completion transaction per ESI ID.

Benefits Realized? 4Near real time response 4Delivers status information *Reduction of repeat callers 4Provides timely & accurate information to TDSP - Reliability will not be negatively impacted. 4Time stamps available at all points of the process. 4Data capture mechanisms when system unavailable

Benefits Realized? 4Separate platforms insure that service order and invoicing processes can continue on EDI during high volume outage events 4Separate platform eliminates stress on EDI platform during high volume outage situations 4Scalable 4Volume & stress tests models available

Goals and Expectations Realized? 4Work plan that details major milestones, timelines and success criteria will be developed and published 4Proof of Concept participants will report monthly to RMS 4Status information to be passed to the CR at the time of the customer’s call 4Near real time delivery of the data to the TDSP 4Existing data requirements developed in previous Outage Workshops and Texas SET will be utilized 4Stress and Volume test will be conducted - Results approved by Texas Test Plan Team 4Contingency plans between the entities will be developed

Goals and Expectations Realized? *The proof of concept would not exceed a 6 month period of time *Provide documentation of the development and implementation time to RMS *Metrics and statistics will be collected and published *Lessons learned will be documented and reported *When the success criteria has been met, a recommendation will be provided to RMS for approval as the new standard.

Recommend as next step: b Open ‘Electronic Outage Reporting’ Meeting to coincide with next RMS meeting Deliver and present promised documentationDeliver and present promised documentation Answer QuestionsAnswer Questions Develop a time line for moving forwardDevelop a time line for moving forward –Ask for RMS approval –Update Protocols –Create Texas SET Implementation Guide –Integrate into Texas Test Plans –Present completion report to RMS