1 / 8

TX SET V4.0 Lessons Learned

TX SET V4.0 Lessons Learned. Areas That Went Well - Test plan was clearly defined - Project timeline was defined - Training sessions on TX SET V4.0 changes - Flight testing covered the majority of new functionality - Overall successful implementation of the project.

carnell
Download Presentation

TX SET V4.0 Lessons Learned

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TX SET V4.0Lessons Learned

  2. Areas That Went Well • - Test plan was clearly defined • - Project timeline was defined • - Training sessions on TX SET V4.0 changes • - Flight testing covered the majority of new functionality • - Overall successful implementation of the project Texas SET

  3. Areas Needing Improvement • - Change controls should be more clearly defined • - PUC rulemaking should be more timely; affected the requirements and change controls • - Requirements should show the entities affected (Ex. CR, TDSP, ERCOT) Texas SET

  4. Areas Needing Improvement cont. • - Need for determining and documenting what constitutes postponing the PROD release and using the contingency dates in the initial stages of the project • - More market participation in general, especially from CRs during requirements development Texas SET

  5. Suggestions • - Deadline for change controls • - If changes are needed to a change control, close it and create a new change control in order to avoid confusion of having different versions • - Market-wide participation needed at meetings; meeting attendees need to focus more on discussion topics instead of personal work in order to prevent readdressing the issues later on • - Adding regression scripts to flight testing as needed Texas SET

  6. Suggestions cont. • - Documentation of when a TX SET release contingency dates will be utilized • - Additional market conference call on the Monday following PROD implementation • - Upgrade of ERCOT CERT environment in order to test more functionality (Ex. MIS functionality) • - TX SET release schedule in order to better forecast budget and resources Texas SET

  7. Suggestions cont. • - Distribute meeting notes from previous month 1 week prior to next meeting for review • - Adhere to a “no earlier than” PROD go live date/time • - All functionality should be available if contingency dates are used • - Balance the transaction load during flight testing better; too front loaded during Flight 0312 • - 2 flight tests during a TX SET release year Texas SET

  8. Suggestions cont. • - Utilizing the Texas SET WG instead of MCT to avoid confusion • - MPs need to follow the implementation schedule (transaction submittal deadline) Texas SET

More Related