Issue Severity Level Definitions Sample Clauses
The Issue Severity Level Definitions clause establishes a standardized system for categorizing the seriousness of issues or incidents that may arise during the execution of an agreement. It typically assigns levels such as 'critical,' 'major,' or 'minor' to different types of problems, often based on their impact on operations or service delivery. By clearly defining these levels, the clause ensures that all parties have a shared understanding of issue priorities, which facilitates appropriate and timely responses and helps prevent disputes over the significance of reported problems.
Issue Severity Level Definitions. (i) P1: Mission Critical. Critical issue affecting all users of the Customer Site, including system unavailability and data integrity issues with no workaround available.
(ii) P2: Urgent. Essential services are significantly degraded and/or impacting significant aspects of the Customer Site. The issue is persistent and affects many users and/or major functionality. No reasonable workaround available.
(iii) P3: Important. Services are noticeably impaired, but most business operations continue as normal. Some but not all users are affected. Short-term workaround is available, but not scalable.
(iv) P4: Minor. The support request consists of "how to" questions, enhancement requests, or documentation questions. This may include routine technical issues, information requested on application capabilities, navigation, installation or configuration, or a bug affecting a small proportion of users on the Customer Site.
Issue Severity Level Definitions. Severity level indicates the relative impact of an issue on Client systems or business processes that are related only to Usherwood’s technology and provided products. ▇▇▇▇▇▇▇▇▇ uses the following severity level definitions to classify all support requests:
o A mission critical supported product or service is down, and no workaround is immediately available. o The supported production system is down or unavailable. o A crucial supported component is not functioning, resulting in the halt of all operations and critical business impact.
Issue Severity Level Definitions. ● Severity Level 0 (Service Unavailability): Customer experiences complete loss of Service, meeting the definition of “unavailable” in Section 5.1 below. ● Severity Level 1 (Severe Issues): Customer experiences a severe defect or configuration issue with the Service that materially impacts Customer’s business in a negative way (excluding Service failures that qualify as Severity Level 0). ● Severity Level 2 (Delayed Performance): Customer experiences transactional and operational slowness in the Service (excluding Service issues that qualify as Severity Level 0 or 1). ● Severity Level 3 (Routine Requests): Routine Service support requests relating to issues that don’t qualify as Severity Level 0, 1 or 2.
Issue Severity Level Definitions. Severity Level 0 (Service Unavailability): Customer experiences complete loss of Service, meeting the definition of “Unavailable” in Section III-B-1 below. Severity Level 2 (Delayed Performance): Customer experiences transactional and operational slowness in the Service (excluding Service issues that qualify as Severity Level 0 or 1).
Issue Severity Level Definitions. P1: Mission Critical. Critical issue affecting all users of the Customer Site, including system unavailability and data integrity issues with no workaround available P2: Urgent. Essential services are significantly degraded and/or impacting significant aspects of the Customer Site. The issue is persistent and affects many users and/or major functionality. No reasonable workaround available. P3: Important. Services are noticeably impaired, but most business operations continue as normal. Some but not all users are affected. Short-term workaround is available, but not scalable.