Continuity Management Clause Samples

The Continuity Management clause establishes procedures and responsibilities to ensure that essential business operations can continue during and after disruptive events. Typically, this clause requires parties to develop, maintain, and periodically test business continuity and disaster recovery plans, covering scenarios such as natural disasters, cyberattacks, or other emergencies that could interrupt services. Its core practical function is to minimize operational downtime and mitigate risks associated with unexpected disruptions, thereby safeguarding both parties’ interests and ensuring service reliability.
Continuity Management. Infrastructure Manager, in consultation with Applicant, shall strive to ensure that the continuity of the service and agreement arising from the Capacity Agreement or Capacity Agreement are maintained.
View SourceView Similar (2)
Continuity Management. AWS Managed Services provides backups of Stacks using standard, existing AWS Backup functionality on a scheduled interval determined by the customer. Restore actions from specific snapshots can be performed by AWS Managed Services per customer RFC. Data changes that occur between snapshot intervals are the responsibility of the customer to backup. Customers may submit an RFC for backup/snapshot requests outside of scheduled intervals. In the case of Availability Zone (AZ) unavailability in a Region, with the customer’s permission, AWS Managed Services will restore the Managed Environment by recreating new Stack(s) based on templates and available EBS snapshots of impacted Stacks. 1 See “Supported AWS Services” section below for a list of supported AWS services. 2 Refer to the AWS Managed Services User Guide for details on which supported AWS services have logging and monitoring enabled.
View SourceView Similar (2)
Continuity Management. CMRI shall have an adequately tested continuity plan in place which identifies critical IT resources in case of a disaster within or around the geographic location of CMRI’s main IT source, allowing a return to functionality which complies with this Service Level Agreement within one (1) day.
View Source
Continuity Management. Retailer shall have an adequately tested continuity plan in place which identifies critical IT resources in case of a disaster within or around the geographic location of Retailer’s main IT source, allowing a return to functionality within twenty-four (24) hours. SPANTIK is committed to customer service. Retailers participating in the Marketplace Program will endeavor to meet the following service levels: (a) Retailer will maintain an On-Time Ship Standard of at least 99%. (b) Retailer will accurately ship the correct Product to the correct Customer at a rate of 99.5% of all Products shipped. (c) Retailer will maintain inventory to fulfill Customer Orders that result in a cancel rate (excluding Customer requested cancellations) of 1.5% or less; (d) Returns due to damaged or defective Products shall not exceed 3% of Sales Proceeds for Products sold on the SPANTIK Site. (e) Retailer shall limit emergency updates related to product information through any Partner Tool to a rate no greater than .03% of its entire SKU count in SPANTIK’s catalog per month; provided however, that SPANTIK makes no guarantee that all requests will be granted. SPANTIK will assess each emergency request on a case by case basis and make updates in situations SPANTIK deems critical. (f) Ninety-day Seller ratings shall, on average, remain above a seller rating of 90% positive. (g) The number of customer service escalations received through SPANTIK’s escalation guidelines, as set forth in Customer Service Escalations, shall not exceed 0.5% of Orders. (h) Retailer will within one (1) hour of receipt on a 24/7 basis, confirm every Order file received by SPANTIK. (i) Retailer will, within four (4) hours of receipt on a 24/7 basis, confirm every order line within every Order file received by SPANTIK. (j) Retailer will provide SPANTIK with electronic notice confirming shipment of each Product shipped and the corresponding shipment tracking information (if available) within four (4) hours of the Product/Order actually shipping so that SPANTIK may charge the Customer and allow the Customer to track shipment of Products.
View Source
Continuity Management. Supplier shall have an adequately tested continuity plan in place which identifies critical IT resources in case of a disaster within or around the geographic location of Supplier’s main IT source, allowing a return to functionality which complies with this Service Level Agreement within one (1) day.
View Source
Continuity Management. Seller shall have an adequately tested continuity plan in place which identifies critical IT resources in case of a disaster within or around the geographic location of Seller’s main IT source, allowing a return to functionality within twenty-four (24) hours. CONFIDENTIAL First Technology is committed to customer service. Sellers participating in the Marketplace Program will endeavor to meet the following service levels: 28.13.1. Seller will maintain an On-Time Ship Standard of at least 99%. 28.13.2. Seller will accurately ship the correct Product to the correct Customer at a rate of 99.5% of all Products shipped. 28.13.3. Seller will maintain inventory to fulfill Customer Orders that result in a cancel rate (excluding Customer requested cancellations) of 1.5% or less; 28.13.4. Returns due to damaged or defective Products shall not exceed 3% of Sales Proceeds for Products sold on the Makro Site. 28.13.5. Seller shall limit emergency updates related to product information through any Partner Tool to a rate no greater than .03% of its entire SKU count in First Technology’s catalog per month; provided however, that First Technology makes no guarantee that all requests will be granted. First Technology will assess each emergency request on a case by case basis and make updates in situations First Technology deems critical. 28.13.6. Ninety-day Seller ratings shall, on average, remain above a seller rating of 90% positive. 28.13.7. The number of customer service escalations received through First Technology’s escalation guidelines, as set forth in Annexure C, shall not exceed 0.5% of Orders. 28.13.8. Seller will within one (1) hour of receipt on a 24/7 basis, confirm every Order file received by First Technology. 28.13.9. Seller will, within four (4) hours of receipt on a 24/7 basis, confirm every order line within every Order file received by First Technology. 28.13.10. Seller will provide First Technology with electronic notice confirming shipment of each Product shipped and the corresponding shipment tracking information (if available) CONFIDENTIAL within four (4) hours of the Product/Order actually shipping so that First Technology may charge the Customer and allow the Customer to track shipment of Products. 28.13.11. Seller will send a refund request to First Technology through the data feed specified by First Technology within 24 hours of receiving a Customer refund or adjustment request, unless Seller has refused to accept a Product for return for any rea...
View Source
Continuity Management. In the event of a major catastrophe, or as a result of vis major as described in the MoA with the THE USERS, Service Levels may be affected. The THE USERS will assist SAHRA in arranging contingency plans regarding alternative processing and printing in accordance with the THE USERS's requirements.
View Source
Continuity Management. For the purpose of guaranteeing the Service Levels in case of disasters, <Supplier> must implement technical and organisational continuity measures. Any agreements on guaranteeing integrity/security also fall under Continuity management. Normal Attention phase Crisis phase Aftercare phase Normal SNO / SLA RTO (Recovery Time Objective ) SNO / SLA Normal business operations Normal Business operations Event Incident Disaster / Crisis Aftercare Event Emergency procedure Catch up with backlog Regular business process incident management As <Principal> manages the infrastructure itself, it has mostly taken technical continuity measures in case of a disaster. This limits the role of <Supplier> in this process, but is aimed at guaranteeing the services in case of any disasters. <Supplier> is responsible for advising <Principal> on developments in the Application components which impact the continuity of the Application components. PI Standard In case of a Disaster, a joint task force will be convened, at the location of<Principal>. This so-called "damage table" will start all necessary actions in order to repair the damage. This consultation may result in actions to be implemented by <Supplier> in a pro-active manner. Reports will be drawn up on the progress of these actions. <Supplier> will be present (physically or by telephone) at the crisis team/the “damage table” within 4 hours. Table 9 PI’s and standards for continuity management Chapter 4. Service Levels for Change management
View Source

Related to Continuity Management

  • Workload Management 11.1 The parties to this Agreement acknowledge that Employees and management have a responsibility to maintain a balanced workload and recognise the adverse effects that excessive workloads may have on Employee/s and the quality of resident/client care. 11.2 To ensure that Employee concerns involving excessive workloads are effectively dealt with by Management the following procedures should be applied: (a) Step 1: In the first instance, Employee/s should discuss the issue with their immediate supervisor and, where appropriate, explore solutions. (b) Step 2: If a solution cannot be identified and implemented, the matter should be referred to an appropriate senior manager for further discussion. (c) Step 3: If a solution still cannot be identified and implemented, the matter should be referred to the Facility Manager for further discussion. (d) Step 4: The outcome of the discussions at each level and any proposed solutions should be recorded in writing and fed back to the effected Employees. 11.3 Workload management must be an agenda item at staff meetings on at least a quarterly basis. Items in relation to workloads must be recorded in the minutes of the staff meeting, as well as actions to be taken to resolve the workloads issue/s. Resolution of workload issues should be based on the following criteria including but not limited to: (a) Clinical assessment of residents’ needs; (b) The demand of the environment such as facility layout; (c) Statutory obligation, (including, but not limited to, work health and safety legislation); (d) The requirements of nurse regulatory legislation; (e) Reasonable workloads (such as roster arrangements); (f) Accreditation standards; and (g) Budgetary considerations. 11.4 If the issue is still unresolved, the Employee/s may advance the matter through clause 9 Dispute Resolution Procedure. Arbitration of workload management issues may only occur by agreement of the Employer and the Employee representative, which may include the union/s.

  • Quality Management Grantee will: 1. comply with quality management requirements as directed by the System Agency. 2. develop and implement a Quality Management Plan (QMP) that conforms with 25 TAC § 448.504 and make the QMP available to System Agency upon request. The QMP must be developed no later than the end of the first quarter of the Contract term. 3. update and revise the QMP each biennium or sooner, if necessary. ▇▇▇▇▇▇▇’s governing body will review and approve the initial QMP, within the first quarter of the Contract term, and each updated and revised QMP thereafter. The QMP must describe ▇▇▇▇▇▇▇’s methods to measure, assess, and improve - i. Implementation of evidence-based practices, programs and research-based approaches to service delivery; ii. Client/participant satisfaction with the services provided by ▇▇▇▇▇▇▇; iii. Service capacity and access to services; iv. Client/participant continuum of care; and v. Accuracy of data reported to the state. 4. participate in continuous quality improvement (CQI) activities as defined and scheduled by the state including, but not limited to data verification, performing self-reviews; submitting self-review results and supporting documentation for the state’s desk reviews; and participating in the state’s onsite or desk reviews. 5. submit plan of improvement or corrective action plan and supporting documentation as requested by System Agency. 6. participate in and actively pursue CQI activities that support performance and outcomes improvement. 7. respond to consultation recommendations by System Agency, which may include, but are not limited to the following: i. Staff training; ii. Self-monitoring activities guided by System Agency, including use of quality management tools to self-identify compliance issues; and iii. Monitoring of performance reports in the System Agency electronic clinical management system.

  • Access Management The Engineer shall coordinate and evaluate access management within the project limits in accordance with the latest State Access Management Manual or as directed by the State.

  • Security Management The Contractor shall comply with the requirements of the DOD 5200.1-M and the DD Form 254. Security of the Contractor’s electronic media shall be in accordance with the above documents. Effective Program Security shall require the Contractor to address Information Security and Operations Security enabled by the Security Classification Guides. The Contractor’s facility must be able to handle and store material up to the Classification Level as referenced in Attachment J-01, DD Form 254.

  • Continuity Each of the provisions of this Agreement will be binding upon and inure to the benefit and detriment of the Parties and the successors and assigns of the Parties.