Recovery Time Objective Clause Samples

The Recovery Time Objective (RTO) clause defines the maximum acceptable amount of time that a system, application, or process can be unavailable after a disruption before normal operations must be restored. In practice, this clause sets a specific timeframe—such as four hours or one business day—within which services must be recovered following an outage or disaster. By establishing clear expectations for recovery speed, the RTO clause helps organizations plan for business continuity and ensures that both parties understand the urgency and requirements for resuming critical operations after an interruption.
POPULAR SAMPLE Copied 19 times
Recovery Time Objective. The recovery time objectives in the following table have been established following discussions with ▇▇▇▇▇ ▇▇▇▇▇▇ and ▇▇▇ ▇▇▇▇▇▇▇▇. RTO refers to the period following a disaster that Council can survive without a service before in starts to cause major business interruption. Service Requested RTO ievable RTO Comments Authority – Payment Processing 2 Days 1 Day Manual receipting option available Authority – Payroll / Fleet 2 Days 1 Day Have the option to replay the last banking if required Purchasing 2 Days 1 Day Rates 2 Days 1 Day Applications 2 Days 1 Day Now more dependant on the State Government portal BIS 1 Week 1 Day Credit Card process 2 days Banks to provide, all credit card facilities are in Council Offices only. Email 1 Day 1 Day Mapping (Intramaps) 1 Week 1 Day Mapping (Mapinfo) 1 Week 1 Day Content Manager 1 Day 1 Day Reflect 1 Day 1 Day Software and data is synced to the cloud. Phones 1 Day 1 Day File Systems 1 Day 1 Day DR Management (Recover Software) Able to access as required Web Casting (Blue Jeans) 1 Week Alternate site available (E.g. Jerilderie or Darlington Point) Inter-site Wireless 2 Days Alternate options required Internet Access 2 Days Remote Desktop 1 Week 1 Day RDPlus 2 Days 1 Day Sewer Alarms Building Security 1 Week
View Source
Recovery Time Objective. Recovery Time Objective (“RTO”) is Loopio UK’s objective for the maximum period of time between Loopio UK’s decision to activate the disaster recovery processes to failover the Services to a secondary site due to a declared disaster and the point at which our customers may resume production operations at a secondary site. If the decision to failover is made during the period in which an upgrade is in process, the RTO extends to include the time required to complete the upgrade. The RTO is 24 hours.
View Source
Recovery Time Objective. System Recovery Time Objective
View SourceView Similar (2)
Recovery Time Objective. In the event of a system failure requiring a complete rebuild of the myday platform onto Microsoft Azure, either in the same or different region, the Recovery Time Objective is 8 hours EXCLUDING Sync Data which would need to be resynced to myday from the on-premises sync server.
View Source
Recovery Time Objective. The following table sets out (i) the Supplier’s monthly RTO (depending on which Cloud Managed Service Offering the Client has selected) and (ii) the Service Credits which apply if the Supplier fails to meet the relevant RTO: Cloud Managed Service Offering Monthly recovery time objective Service credit* Starter or Business 4 hours 60% of relevant monthly Cloud Fees Business Plus 2 hours 60% of relevant monthly Cloud Fees Enterprise 30 minutes 60% of relevant monthly Cloud Fees * If Service Credits for Monthly RTO apply, they will represent the Client’s exclusive right to Service Credits for the applicable month, irrespective of the Supplier’s Monthly Uptime performance or any related Service Credits. For the avoidance of doubt, the Supplier’s total liability for Service Credits in relation to Cloud Services in any month will not exceed the Cloud Fees for that month.
View Source
Recovery Time Objective is the duration of time within which a service, business process or application must be restored after an outage to avoid unacceptable consequences associated with a break in continuity of business
View Source
Recovery Time Objective. The Recovery Time Objective (RTO) is the targeted duration of time and a service level within which a business process must be restored after a disaster (or disruption) in order to avoid unacceptable consequences associated with a break in business continuity. The commitment for the RTO for the Kinetic Platform is 4 hours.
View Source
Recovery Time Objective. Services will have a maximum allowable outage of two (2) consecutive hours within each month of Service under the term of Agreement. i) Where the outage is more than two (2) total hours within one (1) month of Service under the term of the Agreement, excluding non-emergency maintenance, Citizens shall be due a Service Credit in the amount of one (1%) percent of the monthly services fees. Company Name (“Vendor”): Agreement Name/Number (“Agreement”): Primary Vendor Contact Name: Telephone: Email: Citizens is subject to Florida public records laws, including Chapter 119, Florida Statutes. As a part of providing public access to Citizens’ records, Citizens makes its contracts available on Citizens’ external website located at ▇▇▇.▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/▇▇▇▇▇▇▇▇▇. This Addendum is incorporated into the Agreement in order to address Citizens’ public posting of the Agreement and its disclosure to third parties. If Vendor asserts that any portion of the Agreement is exempt from disclosure under Florida public records laws, (the “Redacted Information”), such as information that Vendor considers a protected “trade secret” per Section 815.045, Florida Statutes, then Vendor must select the corresponding declaration below and provide the following to ▇▇▇▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇@▇▇▇▇▇▇▇▇▇▇▇.▇▇▇: (1) A copy of the Agreement in PDF format with the Redacted Information removed (the “Redacted Agreement”); and, (2) A dated statement on Vendor’s letterhead in PDF format clearly identifying the legal basis for Vendor’s redaction of the Redacted Information (the “Redaction Justification”).
View Source

Related to Recovery Time Objective

  • PERFORMANCE OBJECTIVES 4.1 The Performance Plan (Annexure A) sets out- 4.1.1 the performance objectives and targets that must be met by the Employee; and 4.1.2 the time frames within which those performance objectives and targets must be met. 4.2 The performance objectives and targets reflected in Annexure A are set by the Employer in consultation with the Employee and based on the Integrated Development Plan, Service Delivery and Budget Implementation Plan (SDBIP) and the Budget of the Employer, and shall include key objectives; key performance indicators; target dates and weightings. 4.2.1 The key objectives describe the main tasks that need to be done. 4.2.2 The key performance indicators provide the details of the evidence that must be provided to show that a key objective has been achieved. 4.2.3 The target dates describe the timeframe in which the work must be achieved. 4.2.4 The weightings show the relative importance of the key objectives to each other. 4.3 The Employee’s performance will, in addition, be measured in terms of contributions to the goals and strategies set out in the Employer’s Integrated Development Plan.

  • Goals & Objectives The purpose of this Agreement is to ensure that the proper elements and commitments are in place to provide consistent IT service support and delivery to the Customer by the Service Provider. The goal of this Agreement is to obtain mutual agreement for IT service provision between the Service Provider(s) and Customer(s). The objectives of this Agreement are to: • Provide clear reference to service ownership, accountability, roles and/or responsibilities. • Present a clear, concise and measurable description of service provision to the customer. • Match perceptions of expected service provision with actual service support & delivery.

  • Performance Targets Threshold, target and maximum performance levels for each performance measure of the performance period are contained in Appendix B.