January 17, 2007 Texas Test Plan Team Meeting Lessons Learned Flight 1006

Texas Test Plan TeamJanuary 17, 2007 Service Provider Comments Details ERCOT NAESB services were down at the start of flight on day 1. This is several flights in a row that ERCOT NAESB service has been nonfunctional on day 1. MP had incorrect port listed under the NAESB/EDM Specifications. This created significant delays in diagnosing connectivity problems while conducting CON51. Contacts listed on the TW are not being used. Instead, pre-made distribution lists are used that do not include new testing contacts. Issues experienced with out-of-order transactions for STK07.

Texas Test Plan TeamJanuary 17, 2007 Service Provider Comments Details SCR33 script – if a problem with the script or ACH payment, it would be best practice to have the CRs attempt to diagnose and resend payment early in the flight. –If the TDSP requests payment information & the CR doesn’t send the payments until the end of flight, it makes it difficult for the TDSP. –In one situation, the refund was made and the checklist was updated, but no was sent with notification of the refund. –In another situation, the refund was marked as sent, no was sent, and the payment was never sent.

Texas Test Plan TeamJanuary 17, 2007 Service Provider Comments Details Transactions must be wrapped in order to enter the translator and generate a 997 reject. (specific to random testing – file was too corrupt to even enter SP system. Follow protocols. When envelope is wrong, can’t respond to 997) Random Testing Guidelines not followed as more than two errors were sent regarding ANSI X12 to one CR.

Texas Test Plan TeamJanuary 17, 2007 TDSP Comments Details No TDSP comments received

Texas Test Plan TeamJanuary 17, 2007 ERCOT Comments Details Flight Test Checkpoint dates must be met to have testing transactions (and Flight) run smoothly.

Texas Test Plan TeamJanuary 17, 2007 Recommendations to Lessons Learned Issue –MP had incorrect port listed under the NAESB/EDM Specifications. This created significant delays in diagnosing connectivity problems while conducting CON51. Possible Resolution –Urge entities to review their TWs and make sure they are correct. Verify against your systems, if necessary. If someone points out a problem, then be sure to go back and fix it.

Texas Test Plan TeamJanuary 17, 2007 Recommendations to Lessons Learned Issue –Contacts listed on the TW and/or the Contacts tab of the RTW are not being used. Instead, pre-made distribution lists are used that do not include new testing contacts. Possible Resolution –At the beginning of each Flight, review the contacts on your personal distribution lists and make sure they are up-to-date and correct.

Texas Test Plan TeamJanuary 17, 2007 Recommendations to Lessons Learned Issue –SCR33 script – if a problem with the script or ACH payment, it would be best practice to have the CRs attempt to diagnose and resend payment early in the flight. Possible Resolution –Possibly have TDSPs require EFT forms for SCR33. Make change to CON52 script to spell out what the TDSPs will need to make refunds for SCR33.

Texas Test Plan TeamJanuary 17, 2007 Recommendations to Lessons Learned Issue –Specific to Random Testing: Transactions must be wrapped in order to enter the translator and generate a 997 Reject. The file was too corrupt to even enter the Service Provider’s system. When the envelope is wrong, the entity can not respond to the 997. Possible Resolution –Follow Texas SET Guidelines.

Texas Test Plan TeamJanuary 17, 2007 Recommendations to Lessons Learned Issue –General issues experienced during a normal flight. How to communicate those ‘lessons’ to new testing parties? Possible Resolution –Address on the Flight Kick-Off Conference call asking if anyone is new to testing? If so, obtain contact information and address independently. Have Retail Account Manager review what’s expected.