Incident Classification Matrix Clause Samples
The Incident Classification Matrix clause establishes a structured framework for categorizing incidents based on their severity, impact, or urgency. Typically, this matrix assigns incidents to different levels or categories, such as minor, moderate, or critical, often with corresponding response protocols or escalation procedures. By providing clear criteria for classification, the clause ensures that incidents are consistently assessed and managed according to their seriousness, which helps organizations prioritize resources and respond appropriately to various situations.
Incident Classification Matrix. 7.4.1. The Incident classification matrix set out below outlines the description, resolution and scheduled updates frequencies for the associated Incident priorities. Priority Description Target Resolution OUTSOURCE TELECOM Response Time High Total loss of Service resulting from a single event. User has total loss of Service / product or degraded beyond usable limits. Degraded Service. E.
Incident Classification Matrix. The Incident classification matrix set out below outlines the description, resolution and scheduled updates frequencies for the associated Incident priorities.
Incident Classification Matrix. 8.5.1 The Incident classification matrix set out below outlines the description, resolution and scheduled updates frequencies for the associated Incident priorities.
g. Errors, packet loss to router interface, Inability to transmit/receive where Business operations are severely impacted. 5 hours- Ethernet# 7 hours for 0ther services**# ½ hour followed by updates each hour Medium Partial loss of Service or degradation of Service, resulting from one event. Partial loss where Service is intermittent or slow throughput. Dribbling errors; packet loss less than 25%; slow throughput; 24 hours 4 hours Low Service Enhancement* that requires a change to the existing Service and/or TALKTECH Network components that will facilitate Service. (*Service Enhancements exclude speed upgrades which are considered on a case-by-case basis and the TALKTECH shall endeavour to resolve such requests within 10 Business Days) Service requests or changes etc 3 Business Days - ** Other services are Etherway Copper, Superfast GEA,EFM. # time for resolution is extended to 15 hours if it is the result of a Fibre break.
8.5.2 The Client understands and accepts that it may be necessary to extend the timescales in the Incident classification matrix above due to the complexity of the Incident or where TALKTECH is dependent on a third party for resolution of the Incident. In such circumstances, TALKTECH shall use reasonable endeavours to eliminate or reduce the impact of the Incident on the Service by provision of a workaround, with permanent correction to follow.
Incident Classification Matrix. 7.4.1. The Incident classification matrix set out below outlines the description, resolution and scheduled updates frequencies for the associated Incident priorities. Priority Description Target Resolution ES SYSTEMS LTD Response Time High Total loss of Service resulting from a single event. User has total loss of Service / product or degraded beyond usable limits. Degraded Service. E.g. Errors, packet loss to router interface, Inability to transmit/receive where Business operations are severely impacted. 4 hours (Fibre) 5 Hours (GEA) 7 Hours (EoFTTC) 7 Hours (EFM) 1 hour followed by updates each hour Medium Partial loss of Service or degradation of Service, resulting from one event. Partial loss where Service is intermittent or slow throughput. 24 hours 6 hours Dribbling errors; packet loss less than 25%; slow throughput; Low Service Enhancement* that requires a change to the existing Service and/or ES SYSTEMS LTD Network components that will facilitate Service. (*Service Enhancements exclude speed upgrades which are considered on a case-by-case basis and the ES SYSTEMS LTD shall endeavour to resolve within 5 Business Days) Service requests or changes etc 3 Business Days -
7.4.2. The Client understands and accepts that it may be necessary to extend the timescales in the Incident classification matrix above due to the complexity of the Incident or where ES SYSTEMS LTD is dependent on a third party for resolution of the Incident. In such circumstances, ES SYSTEMS LTD shall use reasonable endeavours to eliminate or reduce the impact of the Incident on the Service by provision of a workaround, with permanent correction to follow.
Incident Classification Matrix. 8.5.1 The Incident classification matrix set out below outlines the description, resolution, and scheduled update frequencies for the associated Incident priorities.
8.5.2 The User understands and accepts that it may be necessary to extend the timescales in the Incident classification matrix due to the complexity of the Incident or where GIACOM is dependent on a third party for resolution of the Incident. In such circumstances, GIACOM shall use reasonable endeavours to eliminate or reduce the impact of the Incident on the Service by provision of a workaround, with permanent correction to follow.
Incident Classification Matrix. 8.5.1 The Incident classification matrix set out below outlines the description, resolution and scheduled updates frequencies for the associated Incident priorities. SLA: All faults will be validated when reported and subsequently classified as below: • Priority 1 - Total loss of service (hard down or no transmission of signal in one or both directions) • Priority 2 – Service is available, but either reduced functionality or degradation is creating significant business impact for the End User • Priority 3 - Service is available, but either reduced functionality or degradation is being experienced by the End User without any significant business impact for the End User For Priority 1 faults we will resolve the fault within 6 Clock Hours (as defined below) from a validated fault. Clock Hours are defined as the time between the Start Time and Stop Time, excluding Parked Time, where: • Start Time means the time a fault has been validated and categorised as a Priority 1 fault