Common use of Service Level Definitions Clause in Contracts

Service Level Definitions. Service level definitions should be documented for the proposed solution, and should meet the CPS operational requirements of 99.99% application uptime, and a data recovery point objective (RPO) of 2 hours (maximum data loss), and a recovery time objective (RTO) time of 8 hours, when a Severity-1 event (up to a disaster) is declared. Severity levels for incidents management must be classified before go-live, and be able to be integrated with how CPS supports applications and services. Incident management for cyber security and service impacting events need to be documented and approved by CPS.

Service Level Definitions. Service level definitions should must be documented for the proposed solution, and should meet the CPS operational requirements of 99.99% application uptime, and a data recovery point objective (RPO) of 2 two (2) hours (maximum data loss), and a recovery time objective (RTO) time of 8 hours, when a Severity-1 event (up to a disaster) is declared. Severity levels for incidents management must be classified before go-live, and be able to be integrated with how CPS supports applications and services. Incident management for cyber security and service service-impacting events need to must be documented and approved by CPS.

Service Level Definitions. Service level definitions should be documented for the proposed solution, and should shall meet the CPS operational requirements of 99.99% application uptime, and a data recovery point objective (“RPO”) of 2 hours (maximum data loss), and a recovery time objective (RTO) time of 8 hours, when a Severity-1 event (up to a disaster) is declared. Severity levels for incidents management must shall be classified before go-live, and be able to be integrated with how CPS supports applications and services. Incident management for cyber security cybersecurity and service service- impacting events need needs to be documented and approved by CPS.

Service Level Definitions. Service level definitions should be documented for the proposed solution, and should meet the CPS operational requirements of 99.99% application IT service uptime, and have a data recovery point objective (RPO) of 2 hours (maximum data loss), and a recovery time objective (RTO) time of 8 hours, when a Severity-1 event happens (up to a disaster) is declared. Severity levels for incidents incident management must be classified before go-live, and be able to be integrated with how CPS supports applications and services. Incident management for cyber security and service impacting events need to be documented and approved by CPS.