Time to Repair. (TTR) SLA. TTR is the time to resolve an Outage Trouble Ticket for a Managed Device.
Time to Repair. (“TTR“). TTR is the time to resolve an Outage Trouble Ticket for a LAN Switch under management.
Time to Repair. 1. Any problem resulting in an corrective maintenance action shall previously classified according to Section 6.1.1,
Time to Repair a. POTS: If and as required by the Commission, out-of-service in excess of twenty-four (24) hours
Time to Repair. Node4 aims to respond, update and resolve Incidents in relation to the Collaboration service within the following times: Priority P1 P2 P3 P4 Seri vce Req uest Response / Acknowledg ement 30 Mins 1 Hour 2 Hours 4 Hours 12 Hou rs Commence ment 1 Hour 2 Hours 4 Hours N/A N/A Frequency of Updates 30 Mins 2 Hours 12 hours if Resolve / Target to Fix exceeded Resolve / Target to Fix 4 Hours 8 Hours 12 Hours 36 Hours 60 Hour s All priority 1 & 2 Incidents should be raised via the Service Desk then followed by a phone call. * Acknowledgement refers to an automated service which generates a response and alerts engineers of a service failure; or where there is dialogue between the client and the engineer.
Time to Repair. “TTR”) Objective.
Time to Repair. The following table defines the Service Levels that are available to RSPs for CGB services, for further information on applicable Service Levels, please refer to the CGB Product Specification documents. Service Levels will be measured against recorded Outages (see 6.0) on a monthly basis according to the terms set out in this Service Level Agreement. Service Credits are defined in the applicable section below. Reference Code Service Level Target Response Time Target Restoration Time Wholesale SLA QSLAB CGB Standard 1 Business Day 2 Business Days 90% in 2 Business Days of being notified - T2R1 and 98% within 5 Business Days after completion date committed - T2R2 QSLAE CGB Enhanced 8 business hours 1 Business Day QSLAP CGB Premier 4 hours 24 hours Service Timer Following CGB receiving an Outage notification from the RSP, the Service Timer will start once CGB has; acknowledged the Outage, assigned a priority level, completed initial diagnostic and activated communications. CGB will provide regular e-mail updates on the progress of restoration efforts and estimated restoration timescales, along with updates on our website service status information page. If an Outage is reported outside of working hours, the Service Timer will begin as the start of the next working day unless for a QSLAP 24 hour service. The Service Timer is stopped as soon as CGB confirm restoration to the RSP, or when the Outage is closed. The Service Timer will be paused if CGB needs to wait for information from the RSP. On occasion, CGB may need to make temporary repairs until a planned maintenance event can be scheduled. The Service Timer stops once a successful temporary repair has been made. Target Response Time CGB’s ‘time to respond’ is measured from the start of the Service Timer until the initial fault diagnosis has taken place and repair has commenced, this includes on-site attendance if required. CGB’s response time will be based on the relevant SLA in force with the RSP and prioritised by incident severity and the number of users affected. Target Restoration Time CGB’s ‘time to restore’ indicates the total time to service restoration, as measured from the start of our Service Timer until the restoration of service.
Time to Repair. Node4 aims to respond, update and resolve requests in relation to the N4EPMA services within the following times (In not specified on the Order Form then Gold is included for N4EPMA services): Priority P1 P2 P3 P4 Ser vic e Re qu est Response / Acknowledge ment 30 Mins 1 Hour 2 Hours 4 Hours 12 Ho urs Commencem ent 1 Hour 2 Hours 4 Hours N/A N/A Frequency of Updates 30 Mins 2 Hours 12 hours if Resolve / Target to Fix exceeded Resolve / Target to Fix 4 Hours 8 Hours 12 Hours 36 Hours 60 Hou rs All priority 1 & 2 Incidents should be raised via the Service Desk then followed by a phone call. * Acknowledgement refers to an automated service which generates a response and alerts engineers of a service failure; or where there is dialogue between the client and the engineer. Where Incident resolution involves third parties, or hardware replacement, then this is subject to the support contracts in place with those parties. *** Service Requests will be completed as per the table. This does not include Service Requests outside of the support contract, or Service Request implemented outside normal business hours these will be dealt with as chargeable projects.
Time to Repair. (“TTR”). TTR is the time to close an Outage Trouble Ticket for an IP PBX Platform.
Time to Repair. Interoute aims to resolve faults causing loss of Service within four (4) hours, provided access to the affected Customer Site, if required is available. Interoute will provide the Customer with progress updates every two (2) hours, unless otherwise agreed. • Where the fault arises from any Third Party Local Access, Interoute shall endeavour to manage the resolution of the fault by the Third Party Local Access provider as soon as reasonably practicable.
