Mean Time To Respond. Repair (MTTR) The Contractor shall respond to Troubles and Outages (defined in footnote 2 of the following table), and repair such problems, in accordance with the standards contained in the following table. The Contractors responsibility to respond/repair exists, when there is a Trouble or Outage, without regard to whether or not the Contractor was at fault in causing such Trouble or Outage. These services shall, for the Types of Trouble listed below, and without regard to the time of day or day of week (including holidays), be performed in accordance with the Response Times and Restoral Times contained in the following table. It should be noted that the numbers in the two columns should not be added together; the time in the Restoral Time column includes any time that the Contractor takes to respond to a Trouble or Outage. “Response Time” begins to be counted at the time that an Authorized User notifies the Contractor of a Trouble or Outage, or the Contractors network management organization determines that such a Trouble or Outage exists on its own. Response Time concludes when the appropriate staff of the Contractor commences performance of remedial services, either in person or (if a Trouble is capable of being remedied remotely) remotely. In no case is acknowledgment of receipt of notification of a Trouble by the Contractors service organizations or the simple generation of a trouble ticket to be construed or defined as a “response.”
Mean Time To Respond. “Mean Time to Respond” is the average time required for Crown Castle to begin troubleshooting a reported failure. The Mean Time to Respond objective is two (2) hours from Crown Castle’s receipt of notice of such failure.
Mean Time To Respond. “Mean Time to Respond” is the average time required for Company to begin troubleshooting a reported failure. The Mean Time to Respond objective is two (2) hours from Company’s receipt of notice of such failure.
Mean Time To Respond. Mean Time to Respond (MTTR) is defined as the monthly average of the time taken between when a trouble ticket is opened by EPB Fiber Optics and when EPB Fiber Optics responds acknowledging receipt of the trouble ticket. MTTR is calculated by dividing EPB Fiber Optics’ total response time by the total number of trouble tickets in a calendar month.
Mean Time To Respond. The length of time between End User opening a Trouble Ticket and End User receiving acknowledgement of the Trouble Ticket; this time is calculated as an average of all response time for the End User’s Trouble Tickets in the preceding calendar month.
Mean Time To Respond. Monthly average of the time taken for VTSL to initially respond via phone or email to a service impacting Trouble Ticket logged by a customer.
Mean Time To Respond. The Mean Time to Respond to a Trouble Ticket varies according to the Trouble Ticket’s priority: Severity Level Time To Respond Severity 1 6 Hours Severity 2 1 Business Day Severity 3 2 Business Days
Mean Time To Respond. A. Global Crossing will meet a Mean Time to Respond commitment of [***] per trouble report on a 7 x 24 basis at all locations. The start time (alarm generation or trouble ticket creation) and response end-time (when Exodus is contacted) will be added to every trouble ticket.
Mean Time To Respond. Monthly average of the time taken for PBX-Change to initially respond via phone to a service impacting Trouble Ticket logged by a customer.
Mean Time To Respond. Crosswind guarantees a Mean Time to Respond of thirty (30) minutes or less for Trouble Tickets classified as Priority 1.
