1 / 16

Retail SLA Proposed Changes

Retail SLA Proposed Changes. RMS/TDTWG August 2008 Trey Felton IT Account Manager. Apr – Jun 2008. Sample Data. For complete data set see: Retail SLA_Transaction Stats.xls. Weekend Transaction Volume during Outage Window Timeframes (1-year average vs 3-month average).

perdy
Download Presentation

Retail SLA Proposed Changes

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. Retail SLA Proposed Changes RMS/TDTWG August 2008 Trey Felton IT Account Manager

  2. Apr – Jun 2008

  3. Sample Data For complete data set see: Retail SLA_Transaction Stats.xls

  4. Weekend Transaction Volume during Outage Window Timeframes (1-year average vs 3-month average) Current Release Window Proposed Release Window

  5. Summary • SLA Proposed Changes • Add 6 hours to Week 1 • Currently 12 hours • Move 36-hr release window to Week 4 • Currently in Week 2—busiest week • Add a 12-hour outage window in Week 5s (Mar/May/Aug/Nov) • Not in current SLA • November will not be used for a release or week 5 outage • Rationale • 5-week Months become general outline for major releases (Mar/May/Aug/Dec) • Extra weekend gives additional outage window opportunity • Remaining months will be reserved for minor releases

  6. Additional Considerations • For 2009 • Move November Week 4 Outage to December Week 2 • To accommodate for Thanksgiving Holiday • Move May Release up 1 week (to Week 3) • To accommodate for Memorial Day • Analyze Quarterly Release concept • For 2010 • Reduce monthly minor release windows if possible

  7. TDTWG Recommendations • Limit Maintenance Window request to 15 hrs • Yes • Reduce Release Outage to 30 hrs • Cannot Support • Marketrak available 8am – Noon on Saturday • Researching, along with other data for MT Task Force • Have 1 weekend a month with zero outages • With our current systems, ERCOT cannot support • Targeted for 2010

  8. Proposed Release Calendar (2009)

  9. Proposed Maintenance/Release Windows for 2009 MAINTENANCE • 1st and 2ndSunday– 6:00am until 9:00pm Sunday (15 hours) • Option 2: Sunday– 9:00am until 12:00am Monday (15 hours) • 3rd and 5thSunday—8:00am until 8:00pm (12 hrs) • Option 2: Sunday—10:00am until 10:00pm (12 hrs) • RELEASE: 4th weekend– 12:00pm Saturday until 12:00am Monday (36 hours) • Option 2: 10:00am Saturday until 10:00pm Sunday (36 hours)

  10. Maintenance Outages (since Jan 1, 2008) ERCOT Proposed SLA (18 hours) TDTWG Proposed (15 hours) Current SLA (12 hours) Average = 9.8 hrs

  11. Releases (2007-2008) Current / Proposed SLA (36 hours) TDTWG Proposed (30 hours) Average = 26.5 hrs 37% took more than 36 hrs 50% took more than 30 hrs

  12. Marketrak

  13. Backup Slides

  14. Release Outage (apportioned time) Variations • June Release: Planned 11 hrs, Actual 24.8 hrs (Prod verification failure; rollback) • July Release: Planned 9 hrs, Actual 9 hrs • Average Release has been 24 hrs (since Jan 1, 2008)

  15. 2008 Net Service Availability 15 July, 2008 ERCOT Confidential

  16. Releases (2008) Current / Proposed SLA (36 hours) TDTWG Proposed (30 hours) Average = 24 hrs

More Related