Time to Repair Sample Clauses

Time to Repair. (“TTR“). TTR is the time to resolve an Outage Trouble Ticket for a LAN Switch under management.

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. 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 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. 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. 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 Incidents in relation to the Collaboration service within the following times: 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.

Time to Repair. “TTR”) Objective. 3.1.1 The TTR Objective applies only to “Hard Outages”. Slow service or other service degradation is not considered a Hard Outage. There are no applicable credits for this objective. Unprotected 7 Hours Protected Access 6 Hours Protected Dual Path 2 Hours

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.

Time to Repair. (TTR) (M-S)

Time to Repair i. Class Networks aims to resolve faults causing loss of Service within four (4) business hours in a standard working day, provided access to the affected Customer Site, if required, is available. Class Networks will provide the Customer with progress updates every two (2) hours, unless otherwise agreed. ii. Where the fault arises from any Third Party, Class Networks shall endeavour to manage the resolution of the fault with the Third Party as soon as reasonably practicable. 1 More than 51% of users unable to work as a result of a problem or incident with the “Customer IT system” documented in section 7.1 30 mins 4 hours 2 A User is prevented from working; Normally there will be a temporary 'work around' for this problem. 1 hour 1 day 3 Problems of a 'non urgent' nature, where the effect on the User is not significantly impacting work. Also Requests such as new users, changesto email distribution groups, printer settings etc. 1 hour 3 days 4 These would be routine request to the Service Desk (like purchase of new equipment which has been budgeted for) or Change Requests 1 day 1 Week 5 Projects. The scheduling and project plan foreach individual project would be agreed with the client. 1 day Agreed at time

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 b. HICAP: Percentage of Repairs Not Completed within two (2) hours c. SUBRATE: Percentage of Repairs Not Completed within three and one-half (3½) hours 2. Percentage of Initial Trouble Reports 3. Percentage of Code 4 Troubles