1 / 5

Enhancing Disaster Recovery Capabilities: ERCOT Workshop Follow-up

Explore improving timelines and efficiencies in ERCOT's disaster recovery procedures discussed in the workshop. Address considerations such as system readiness, recovery objectives, data centers capability, and cost implications for achieving faster recovery times. Evaluate the feasibility of MarkeTrak operating independently and assess communication requirements for COPMG. Plan for potential site failover and prioritize restoration of retail services.

bettinas
Download Presentation

Enhancing Disaster Recovery Capabilities: ERCOT Workshop Follow-up

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. RMS ERCOT Disaster Recovery Workshop Follow-up ERCOT September 9, 2014

  2. Disaster Recovery Workshop ERCOT Follow-ups • Requirement: reduce the timeline from "event" to first notice giving "market awareness" to an ERCOT system issue.   What can ERCOT do to meet this requirement? • Work with COPS/CSWG on evaluating where COPMG may need similar communication requirements as RMS • Can MarkeTrak operate “standalone” without ERCOT’s registration system? • MarkeTrak functionality is largely “standalone” at this time • A change request has been submitted to include all functionality • What does it take to meet 12 hour recovery time objective? (event to systems ready) • What does it take to meet 6 hour recovery time objective? (event to systems ready)

  3. Retail/Commercial Systems – DR Capability • Capable of operating out of two data centers • Capable of a 5 minute data loss Recovery Point Objective (RPO) • Recovery Time Objective (RTO) • Moving ERCOT’s operations between data centers • ERCOT has historically committed to a 24 hour RTO of all Retail/Commercial systems • After a review of the current DR plan and processes, ERCOT will commit to a 12 hour RTO • Assumptions: • ERCOT’s alternate, or passive, data center is fully functional • The 12 hour RTO window starts with ERCOT’s first detection of an issue or incident that may require moving to the alternate data center • ERCOT may execute 1 planned site failover in the fall/winter of 2014

  4. Retail/Commercial Systems – DR Capability • Recovery Priority • Retail Services will normally be restored, or failed over, in a parallel fashion • Should prioritization be necessary, the following order will be followed

  5. Retail/Commercial Systems – DR Capability • 6 hour RTO would require additional costs • ERCOT would need to undertake a formal initiative to determine the scope of necessary changes/costs

More Related