Information TechnologyService Availability Metrics

March 2008

Recent MarkeTrak Degradation Issues

• MarkeTrak users have experienced delayed system response and slow application performance – Degradations are tracked and described in the incident log

• Initial analysis indicated database contention was the root of the problem. After increasing system resources, the database problem was resolved but slow application response continued– Assigned additional resources to the database (3/2)– Planned to implement a database change (3/30) – cancelled

• Increased volume of 814_20 transactions for station ID’s is not affecting transaction processing, although it may play a small role in MarkeTrak application performance problems– Initially, increased transactional volume was thought to be a factor

causing slow MarkeTrak performance, but further analysis shows this is not the case

– Volume is reflected on the graph on the following slide

Recent MarkeTrak Degradation Issues

MarkeTrak Activity – October ’07 to present

Recent MarkeTrak Degradation Issues

• Other areas examined during the troubleshooting process:– Network

• Underutilized – no issues found– Security

• No issues found– Server resources

• CPU is underutilized • DISK/SAN is underutilized• HTTP sessions – MarkeTrak becomes unresponsive around 200 sessions

– ODBC settings• Updated to latest version of the driver in February 2008

• Having ruled out other potential causes – the probable cause is the application itself – a version upgrade is needed

– The version upgrade was initially scheduled for the January ’08 release, the release did not pass testing due to bugs. Rescheduled for March ’08 release

– The next version of code also had bugs, and did not pass testing and was pulled from the March ’08 release

– The latest version of code will be released into testing within the next few days, if all goes well it will be promoted to production in the May ’08 release

2008 Net Service Availability

3

99.00%

98.00%

97.00%

94.00%

95.00%

96.00%

93.00%

92.00%

100.0%

2008 Net Service Availability Through February 29th, 2008

Transaction Processing TML MarkeTrak Frequency ControlRealtime Balancing

Market

99.84% 99.90%99.36% 99.830%99.998%

Wholesale Total

100%

Transaction Processing SLA Target 99.9%

TML Availability Target99%

MarkeTrak Availability Target – 98%

Retail & Wholesale Operations System Operations

February 2008 Net Service Availability

4

February 2008 Net Service Availability

99.00%

98.00%

97.00%

94.00%

95.00%

96.00%

93.00%

92.00%

100.0%

Transaction Processing TML MarkeTrak Frequency ControlRealtime Balancing

Market

99.67% 99.87%100% 99.928%99.995%

Wholesale Total

100%

Transaction Processing SLA Target 99.9%

TML Availability Target99%

MarkeTrak Availability Target – 98%

Retail & Wholesale Operations System Operations

Retail Transaction Processing Availability Summary

5

Retail Transaction Processing Availability

99.50%

99.00%

98.50%

97.00%

97.50%

98.00%

96.50%

96.00%

100.0%

February 2008 Retail Transaction Processing Availability Summary

Target – 99.9%

February 2008 Transaction Processing Availability – 99.67%

2/6 – ERCOT was able to receive, but not send transactions due to an application port being inadvertently closed – 131 min

TML Availability Summary

6

February 2008 TML Availability Summary

TML Availability

99.50%

99.00%

98.50%

97.00%

97.50%

98.00%

96.50%

96.00%

100.0%

Target – 99%

Feb 2008 TML Availability – 100.00%

MarkeTrak Availability Summary

7

MarkeTrak Availability

99.50%

99.00%

98.50%

97.00%

97.50%

98.00%

96.50%

96.00%

100.0%

February 2008 MarkeTrak Availability Summary

Target – 98%

February 2008 MarkeTrak Availability – 99.87%

2/19 – Application froze due to security software issues – 20 min