Disaster Recovery Planning. MSI will have responsibility for coordinating the development, maintenance, testing and in the event of a disaster the implementation of Disaster Recovery Plans at an Application, DIR Customer and DIR level. Service Provider will be responsible for the development and modification of Disaster Recovery plans for the Services in coordination with DIR and DIR Customers. Such plans will be in compliance with Exhibit 16 and the Disaster Recovery Priority established for each DIR Customer Application. DIR and DIR Customers will approve Disaster Recovery plans and modifications to such plans. Service Provider’s responsibilities include:
1. Effectively manage and maintain the Disaster Recovery plans of DIR and DIR Customers, as they exist on the Effective Date.
2. To the extent that DIR and DIR Customers do not have a documented Disaster Recovery plan encompassing all Services, Service Provider will develop and implement a Disaster Recovery plan using Service Provider’s best practices and standards for companies of similar industry, size, and services. DIR or DIR Customers will approve any such Disaster Recovery plan developed by Service Provider and will provide support in creating the plan.
3. Maintain and continually enhance DIR’s and DIR Customers’ Disaster Recovery plans throughout the term of the Agreement, including enhancements required due to the introduction and use of new technologies (Equipment, Software, Applications, etc.), Resource Units, processes, business functions, locations, and priorities.
4. Integrate the Disaster Recovery plans related to the Services with any DIR Customer Business Continuity plans and activities of DIR.
5. Integrate the Disaster Recovery plans related to the Services with the plans of any Third Party Vendors and any activities of Third Party Vendors associated with Disaster Recovery planning or Disaster Recover response.
6. Document the manner, processes and procedures by which Service Provider will perform backups, provide Disaster Recovery services, and assist with Business Continuity.
7. Document DIR Customers priorities for Disaster Recovery and Business Continuity based on the priorities established by DIR.
8. Document the methods, processes and timeframes that allow DIR Customers to change priorities, as specified in Service Management Manual.
9. With DIR and DIR Customer’s input and approval, develop a process that will determine and modify the list of mission-critical Applications on a continual basis with annual re...
Disaster Recovery Planning. Supplier’s disaster recovery plans and activities in support of County shall be Approved by County in advance. Supplier’s responsibilities for disaster recovery planning related to the Services include the tasks, subtasks, and Deliverables set forth in Table 18 (Disaster Recovery Planning Responsibilities) below.
Disaster Recovery Planning. Is there a Business Continuity Plan available for the Data Center where Northeast Utilities will be connecting to your company?
Disaster Recovery Planning. Amdocs will provide Services for Disaster recovery planning in the areas of the equipment, processes, and mechanisms needed to ensure business continuity and to restore saved data and the Amdocs Systems in the event of a Disaster. Details of such Services are included in the Disaster Recovery Plan document (Schedule 12).
Disaster Recovery Planning. Disaster Recovery Plan (DRP) objectives for the Service under this Schedule are as follows: • Minimize the amount of time it takes to resume normal business operations in the event of a disaster. • Assess damage to the data center facilities and equipment, repair the damage if possible and activate the repaired data center, or bring alternative facilities online. • Manage the failover and recovery operation in an organized and effective manner. • Prepare departments and personnel to respond effectively in a disaster situation. To respond to the occurrence of a disaster in the most effective manner possible, the DRP has established hierarchal business teams that are responsible for the coordination and execution of the plans and procedures needed to fail over to, and back from another site. In addition, a Disaster Recovery Chairperson oversees all recovery operations and makes hot site fail-over decisions. He/she coordinates activities among the teams. The two teams are: the Business Recovery Team (BRT) and the Operations Recovery Team (ORT). The BRT is responsible for internal and external notification, coordination, and administrative support activities needed throughout the disaster recovery operation. The ORT is responsible for implementing and managing the movement of operations to the disaster recovery site, and for implementing and managing the recovery activities at the site of the disaster. FIS’s production operations for the Service are hosted in two different locations in the U.S. One is in Virginia and the other is in Colorado. FIS’s client operations for the Service are divided evenly between these two data centers. Half of the clients use Virginia as their primary data center and the other half use Colorado. Each data center functions as the D.R. location for the other data center. The database and files on disk are replicated from each data center to the other. In the event of a disaster at one of the data centers, all operations will be moved to the other data center. Each data center has enough capacity to host all of FIS’s ASP clients for the Service. ***** The implementation of recovery in Denver for the remaining non-production critical equipment is commenced at the direction of the Disaster Recovery Chairperson. The DRP contains a comprehensive list of the equipment and procedures for making the equipment operational. Accordingly, the DRP is reviewed annually and updated as necessary. Employees are made aware of any changes to the plan ...
Disaster Recovery Planning. Supplier’s Disaster Recovery plans and activities in support of Gap, shall be Approved by Gap in advance. Supplier’s responsibilities for Disaster Recovery planning related to the Services include (“Disaster Recovery Planning”):
(a) Managing and maintaining the Disaster Recovery plans of Gap, as they exist on the Initiation Date, as may be modified, amended or updated as set forth in the Agreement (“Gap’s Disaster Recovery Plans”).
(b) Maintaining and updating Gap’s Disaster Recovery Plans throughout the Term. Such updates may include Changes required due to the introduction and use of new technologies (e.g., Equipment and Software), Resource Units, processes, business functions, locations, and priorities.
(c) Integrating the Disaster Recovery plans related to the Services with Gap’s business continuity plans (provided that copies of such plans are provided by Gap to Supplier) in accordance with Section 5 (Change Management).
(d) Documenting the manner and procedures by which Supplier shall perform backups and provide Disaster Recovery Services.
(e) Documenting Gap’s priorities for Disaster Recovery backups based on the priorities established by Gap and communicated to Supplier and methods and timeframes that allow Gap to modify priorities.
(f) Maintaining a list of key personnel contacts and notification procedures for Gap, Supplier, and Third Party Vendor personnel.
(g) Providing * for Disaster Recovery plans, related communications and other activities that are Supplier’s responsibility.
(h) Gap retains the right to Approve all Supplier Disaster Recovery plans in support of Gap, and modifications to such plans.
(i) With respect to Gap’s critical Applications, Supplier’s Disaster Recovery responsibilities include Coordinating with Gap and Gap Third Party Vendors to:
(1) document new and maintaining/updating existing Gap procedures to support Disaster Recovery of critical Applications. * Certain information on this page has been omitted and filed separately with the Commission. Confidential treatment has been requested with respect to the omitted portions.
(2) document and providing a process that determines/modifies the list of *, subject to Gap’s Approval.
(3) Support Gap in critical Application Disaster Recovery testing on all * in accordance with the Procedures Manual.
(4) Retesting any unsuccessful critical Application annual Disaster Recovery test within * of the failure, not to exceed the annual test limit.
(j) Performing record retention (e.g., us...
Disaster Recovery Planning. 7.1 Duplicate final assembly Cell
Disaster Recovery Planning. Business Recovery ------------------------------------------------------------------------------------------------------------ Genuity GTEDS Service Description ------------------------------------------------------------------------------------------------------------ X C Develop Business Continuity Plans ------------------------------------------------------------------------------------------------------------ X C Maintain Business Continuity Plans ------------------------------------------------------------------------------------------------------------ X C Perform annual disaster rehearsals ------------------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------------------ Data Processing Recovery ------------------------------------------------------------------------------------------------------------ Genuity GTEDS Service Description ------------------------------------------------------------------------------------------------------------ X Maintain availability of like systems at designated recovery site ------------------------------------------------------------------------------------------------------------ C X Develop all SAP Disaster Recovery procedures ------------------------------------------------------------------------------------------------------------ C X Maintain all SAP Disaster Recovery procedures ------------------------------------------------------------------------------------------------------------ C X Perform annual disaster rehearsals ------------------------------------------------------------------------------------------------------------ C TM Recovery of Production system at recovery site ------------------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------------------ Appendix C - Definitions/Acronyms When used in this SLA, the terms listed below shall have the following meanings: Acceptance is defined as written notification from the receiving party's Manager indicating that the Deliverable has been evaluated and satisfies Acceptance criteria. Business continuity plans The planned sequence of events that allows for the recovery of business functions and processes. Critical IR - System is non-operational or has the potential to become non-operation...
Disaster Recovery Planning. Natural Disasters include, but are not limited to, earthquakes, tsunamis, volcano eruptions, etc. During a disaster activity, usage of the System is expected to be high. The following are areas of expected increase for operations:
6.1 Scheduling of personnel. During this time, the System Management Team will go on a higher level of total System monitoring, closely assessing the effected area for loading and service issues.
6.2 Activate Network Monitoring Office/System Service Center (NMO/SSC) to Higher Monitoring. The NMO/SSC will be notified of the disaster. They will be staffed with appropriate personnel to assist in monitoring and resolving issues throughout the emergency.
6.3 Other Support Personnel. Contract support personnel such as ProComm and North Slope will be activated to assist with issues, as necessary. Additionally, management and technical personnel from DOD/SOA DOA/Enterprise Technology Service (ETS)/SATS will be included in System management and restoration during the disaster.
Disaster Recovery Planning. Natural Disasters include, but are not limited to, earthquakes, tsunamis, volcano eruptions, etc. During a disaster use of the System is expected to be high. The following are areas of expected increase for operations:
5.1 Scheduling of personnel. During this time, the System Management Team will go on a higher level of total System monitoring, closely assessing the effected area for loading and service issues.
5.2 The Motorola™ Network Monitoring Office/System Service Center (NMO/SSC), at Schaumburg, Illinois, will be notified of the disaster and staffed with appropriate personnel to assist in monitoring and resolving issues throughout the emergency.
5.3 Other Support Personnel. Contract support personnel will be activated to assist with issues, as necessary. Additionally, management and technical personnel from DOD/SOA DOA/Enterprise Technology Service (ETS)/SATS will be included in System management and restoration during the disaster, which is outlined in the Catastrophic Natural Events (CNE) Plan.
