Time to Restore. The mean time to restore from time of identification of any unplanned generalized service outage or Service Incident Severity Levels 1, 2, 3 and 4 is six hours.
Time to Restore. Genuity will use commercially reasonable efforts to keep the Time to Restore (TTR) under four hours (95% of the time) as measured over a one month period. TTR is not a parameter that is directly measured for SLA crediting, however TTR by its very nature is a factor in the computation of the overall Average Network Availability
Time to Restore. The SLA Credit/Remedy for Time to Restore (TTR) is accounted for in the Circuit Availability SLA set forth in 2.4.5. TTR is not a parameter that is directly measured for SLA crediting. TTR shall be the cumulative amount of time (minutes/hours) between the opening of a trouble ticket by Genuity and the closeout process set forth in the Service Schedule and its' attachments.
Time to Restore. Etellect target Time to Restore for the server is 5 hours or less for 98% of qualifying Faults.
Time to Restore. (“TTR”) AND MEAN TIME TO RESTORE (“MTTR”) OBJECTIVES
7.1. GTT will commit to a MTTR for Service Outage(s) affecting a descrete Service. The MTTR commitment is determined by the access technology for each GTT provided Access Circuit providing the Service. Should MTTR exceed this objective during any given month, GTT shall credit the Client a service credit equal to ten percent (10%) of one month’s MRR for the affected Service, in addition to any credits under Section 6, with a maximum of one MTTR credit per Client Site. Access Technology MTTR
7.2. In the event of CPE failure and where replacement is required, GTT will commit to a time-to-restore of next business day unless a different TTR is expressly specified in the relevant SOF. Replacement CPE, provided by GTT, will be shipped for next business day delivery so long as (i) the trouble is isolated to the GTT provided and managed equipment, and (ii) the root cause of the failure is determined by GTT by 1 PM local time to the Client Site on the same day. GTT may request client to install replacement CPE shipped to Client’s Site by GTT (in accordance with installation instructions provided by GTT). Once GTT has confirmed installation of CPE at Client’s Site, GTT will complete remote configuration and testing of replacement CPE.
7.3. GTT will commit to an additional MTTR service level inclusive of CPE repair. Should MTTR fall below the objectives below during a given month, GTT shall credit the Client a service credit equal to ten percent (10%) of the MRR for the affected Service, with a maximum of one credit per day per Client Site. In the event of CPE failure, MTTR for Service shall apply as follows:
Time to Restore. Average 160 GB 1 hr 35 min Full Database
Time to Restore. Etellect’s target for Time to Restore for the Service is 10 hours or less for 98% of qualifying faults.
Time to Restore. General Comments: This metric measures trouble duration intervals. Mean Time to Repair: (MTTR) For Network Trouble reports, the average duration time from trouble receipt to trouble clearance. Includes Disposition Codes 03 (Drop Wire), 04 (Cable) and 05 (Central Office).
Time to Restore. If the Time to Restore Service Level is not achieved for a Severity Level 1 Incident, then Customer will be entitled to receive a credit equal to €100 for each full Business Hour of delay, up to a maximum of €1,000 per month and per Incident, subject to the limitation on total credits due for all unachieved Service Levels specified in Clause 1.3 (Conditions and Exclusions) of this Service Level Agreement document.
Time to Restore. Jelly Digital will give customer a status update within 1 hour from receipt of trouble ticket for T-1, Fiber, EoC and Wireless service. Jelly Digital is committed to restoring these services within four (4) hours and DSL/DS-0 services within eight (8) hours. The “time to restore” begins on the the date and time customer reports the service outage and ends upon the time Customer’s service is able to once again transmit and receive voice and Internet data. Customer must open a trouble ticket with Jelly Digital’s Customer Support when Customer believes a service outage has occurred in order to have the network unavailability eligible for consideration for a service credit. Customer must initiate a trouble ticket by voice contact. Upon notification from Customer, Jelly Digital will open a trouble ticket, test the affected service and attempt to isolate the problem. Jelly Digital’s records and data will be the sole basis for all service credit calculations and determinations. Customer will not be entitled to any service credits for service unavailability unless Customer has opened a trouble ticket and requested the service credit within one (1) week of the service unavailability. Service Level Agreement
