Information Technology Update Aaron Smallwood Manager, IT Business & Customer Services

2 Data Extracts & Reports Recent Data Extracts & Reports Delays –Causes: Storage hardware failures –Failures delayed batch processing which in turn delayed reports and extracts Human errors –Data cleanup activities inadvertently caused incorrect data to be generated during the batch process, the remediation efforts required the backout and rerun of three operating days, much of which had to be performed manually –Permissions not granted properly during the March retail release, causing files to not be able to flow where they needed to for report generation –Resolution: Storage Hardware Failures –Project to replace aged hardware has been in progress since ’07 and is scheduled for implementation during the first weekend in May Human errors –Education and training

3 Recent Issues R-A – Delayed ESI_ID Service History and Usage Extracts –Due to a database rollback segment error, ESI ID service history and usage extract was delayed on February 19 th and February 20 th, 2008 and was posted on February 21 st, 2008 –Root Cause: Database size continues to grow due to the increasing volume of data, and maintenance activities failed due to space allocation –Fix: Additional space was allocated and extracts were rerun R-A – 867_03 Activity reports for 3/10 – 3/12 were delayed –Due to a permissions issue, some 867 usage files were not picked up via the automated process. Manual intervention was required to complete the usage processing which caused multiple reports to be created –Root Cause: Permissions issues following a hardware change during a Retail Release the previous weekend –Fix: Permissions were granted R-B – Mapping Status Reject Report for 3/10 – 3/12 was delayed –Due to failure to restart a retail process correctly following a hardware change during a Retail Release the previous weekend, the Mapping Status Reject Reports for 3/10 – 3/12 were delayed –Root Cause: Human Error –Fix: Education & Training M-A – Delays in Posting Several Reports & Extracts –Data cleanup activities inadvertently caused incorrect data to be generated during the batch process. Remediation efforts required the backout and rerun of three operating days, much of which had to be performed manually. Additionally, the data cleanup activities caused the database statistics to become stale off-cycle, which significantly increased batch processing time. Subsequent reports and extracts were delayed due to the delayed batch process –Root Cause: Inadvertently caused by data cleanup –Fix: Rerun statistics on the database

4 Recent Issues M-A – Delays in Posting Several Reports & Extracts (cont…) –Also relating to this market notice, a hardware failure hung the batch process requiring restart of the settlements and billing database and server –Root Cause: Hardware failure –Fix: PR70055 was initiated in November 2007 to replace these infrastructure components, expected completion is April 2008 W-A – Reposting of Settlements & Billing Extract –Settlements and billing extracts for March 9 th contained incomplete data –Root Cause: Missing data was due to an hour being skipped due to the Daylight Savings Time transition –Fix: Backout and rerun of that settlement date

5 Data Extracts & Reports SLA - Update Data Extracts & Reports SLA –Working with DEWG to formalize an SLA with COPS for Data Extracts & Reports Potential approval at May COPS meeting –Key points: Identified 27 ‘Priority 1’ extracts & reports to be included in SLA Reporting will be provided monthly to COPS and TAC, likely beginning in June and will include: –Timeliness (did it get there in time) –Completeness (was all the data there that was supposed to be) –Accuracy (was the data correct) –Application availability: TML Report Explorer Retail API (application programmatic interface)