Electronic Outage Reporting Proof Of Concept Report

1. Electronic Outage ReportingProof Of ConceptReport July 8, 2002

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

3. Electronic Outage ReportingRecommendation

4. Common Standard

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

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

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

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

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

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

11. 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.

12. Recommend as next step: • Open ‘Electronic Outage Reporting’ Meeting to coincide with next RMS meeting • Deliver and present promised documentation • Answer Questions • Develop 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