Incident Classification. The Service Provider must classify and respond to support calls by the underlying problem’s effect on a Subscribing Entity. In this regard, the Service Provider may classify the underlying problem as critical, urgent, or routine. The guidelines for determining the severity of a problem and the appropriate classification of and response to it are described below. The Service Provider must designate a problem as “critical” if the Service is functionally inoperable, the problem prevents the Service or a major component or function of it from being used in production mode or there is significant potential for data integrity problems. This classification assumes there is no existing patch for the problem. The Service Provider must classify a problem as “urgent” if the underlying problem significantly degrades the performance of the Service or a major function or component of it or materially restricts a Subscribing Entity’s use of the Service in a production mode. A problem also will be considered urgent if a commonly used feature often generates application errors, causes the Service to freeze, locks up the computer on which the Service is running, or otherwise routinely does not work as intended. Classification of a problem as urgent rather than critical assumes that an affected Subscribing Entity still can conduct business with the Service and response times are consistent with the needs of the Subscribing Entity for that type of Service. As with the critical classification, the urgent classification assumes there is no existing patch or acceptable workaround procedure for the problem. Finally, the Service Provider may classify a support call as “routine” if the underlying problem is a question on end use or configuration of the Service. It also may be classified as routine when the problem does not materially restrict a Subscribing Entity’s use of the Service in its production environment, such as when a feature or combination of features generates minor or rare errors. Also, if any problem that otherwise should be classified as critical or urgent can be solved either by a known workaround or an existing patch that does not materially interfere with a Subscribing Entity’s use of the Service, the problem may be treated as routine. The Service Provider must apply the above classifications in good faith to each call for support, and the Service Provider must give due consideration to any request by a Subscribing Entity to reclassify a problem, taking into acco...
Incident Classification. 5.1 Incidents shall be classified as follows:
Incident Classification. In the event of a Service outage, failure or other degradation, BT shall assign a severity level in accordance with the table below (for the avoidance of doubt, BT shall only pay Service Credits on actual Incidents - see paragraph 3.1 above): Incident severity Nature of Incident Severity 1 * Severity 2 * Severity 3 * For the avoidance of doubt, Severity Levels in the above table have no relationship to the Severity Levels applicable to the Existing Services.
Incident Classification. 5.1 Incidents shall be classified as follows: Classification Description Response Time / Update time Target Resolution Time Severity 1 An incident is categorized as Severity level 1 when the following conditions are satisfied: Condition 1: Unavailability of one or more online services provided by Equifax, affecting multiple customers or partners during service hours Condition 2: A logical security breach whose severity could impact adherence to regulatory requirements 30 minutes 4 hours Severity 2 Major inconvenience, some users affected. Example: All or some users experiencing slow responses or errors 1 hour 24 hours Severity 3 Minor Incident, no impact on service. Example: A single user affected, business functionality still maintained 24 hours 3 days Severity 4 Minor impact, information only 7 days 28 days
Incident Classification. (a) Interactive will determine the severity of any reported Incident based upon the Customer’s impact assessment, having regard to the urgency and impact factors in Table A and Table B. Interactive will then allocate a severity level in accordance with Table C.
Incident Classification. All incident reports must be made to ne Digital by an Authorized Contact. ne Digital will work with Customer and will assign the appropriate priority level to any such reported incident. ne Digital may reclassify incidents based on the current impact on the System and business operations.
Incident Classification. The Incident Classifications used for Services: High: An Downtime that prevents use; the performance and/or Services related to (the platform, application or its part belonging to) the Service have been disturbed to an unusable state, the application, its part or process has stopped, the Services are so unstable that no normal activities can be performed. If the Incident concerns users who are central to the Client or if the Incident concerns passengers, the Incident is classified as high. Medium: The Incident significantly hinders the usability of the Service, the hardware, application, Modification or platform are repeatedly unstable or do not respond normally to service requests. Low: The Incident occurs only on occasion and does not hinder use in a significant manner, the Incident concerns special services that are used rarely and/or it can be circumvented. Other situations that do not hinder the Client’s normal activities.
Incident Classification. A2.2.1 Following the registration phase, Mi Support will classify the case according to Item C.2.5.2: Incident Severity Matrix and calculate minimum response time according to Item C.2.5.3: Response Time Matrix.
Incident Classification. For all requests which relates to incidents, Supplier will use a classification and escalation method. Supplier understands and expects that there may be cases in which the severity of the incident is not known at the time of request. Once Supplier receives such request, it will make a determination as to the severity level of the problem and respond accordingly. Should the Supplier’s Project Manager and Customer's Project Manager disagree on the severity of the incident, the incident shall be classified as Level 3: Incident Classification & Escalation Table Priority Level 4 3 2 1 Severity Level Work-Around Available Error Critical System Failure Software is functioning with work-arounds. Incident may be prioritized as a Modification to be included into a future release. Any other uncategorized issues or questions. Software has minor functionality which is unavailable or impaired. No mutually agreed upon work-around is available. Software has important functionality or core component which is unavailable or severely impaired. No Application feature is currently functioning. Application is completely unavailable or severely impaired.
Incident Classification. Vendor and Subscriber will together classify each incident reported by Subscriber (each, an “Incident”), based on the Incident Classification Table below and on information provided by Subscriber. Description Incident Classification Incident Classification Description Catastrophic Incident (Severity Level 1) The Service is unusable, unavailable for a significant number of Subscriber users, or there is an imminent risk of the loss of Subscriber Data or the occurrence of a Security Incident. Critical Incident (Severity Level 2) The Service is materially degraded or otherwise causes results that are more detrimental to Subscriber or its systems than a Severity Level 3 Incident. Serious Incident (Severity Level 3) The Service experiences a significant malfunction, which materially impacts a portion of the functionality or the population of Subscriber users. Important Incident (Severity Level 4) The Service experiences a non-critical malfunction, which does not materially impact the functionality of the Service. Non-Critical Incident (Severity Level 5) The Service does not provide functionality or perform in a way that meets Subscriber’s new needs or Subscriber’s needs for information about the Service.
