Incident duration Sample Clauses

Incident duration. All Incidents recorded by the monitoring system will be reconciled against the corresponding Service Ticket raised by the Service Desk. The exact Incident duration will be calculated as the elapsed time between the Service Ticket being opened and the time when service is restored.
Incident duration. All Incidents recorded by the Node4 monitoring system will be reconciled against the corresponding Service Ticket raised by the Service Desk. The exact Incident duration will be calculated as the elapsed time between the Service Ticket being opened Service Desk and the time when Service is restored.
Incident duration. In 2009 WITS data, four timestamps are recorded for a typical incident: notification time (when the incident was notified to the IR team), arrival time (when the IR team arrived at the incident site), lane open time (when all lanes became open to traffic), and clear time (when the incident had been cleared and full departure capacity of the roadway section became available). Note that the actual start time of an incident might be some time before the incident is notified; however, unless the person involved in the incident could provide accurate information, there is uncertainty to determine when the incident actually started. Fortunately, due to the widely-used wireless communication, notification time is a good estimate of the actual start time of an incident, which is considered as the “start time” of an incident in 2009 WITS data (WSDOT, 2008). Correspondingly, the incident duration consists of three typical intervals: arrival (the interval between the notification and arrival times), clearance (the interval between arrival and all lanes open times), and recovery (the interval between all lanes open and clear). The arrival interval depends on and reflects the ability of the IR teams to respond to an incident. The clearance interval measures the performance of the IR teams to clear an incident with the 90- minute goal (WSDOT, 2008). The recovery interval reflects the time for the traffic to operate at full departure capacity from the incident impact. As mentioned in Section 3.1.1, following WSDOT’s convention the period from the notification time to the clear time (labeled as Clearance Time in WITS data) of an incident is referred as the duration of the incident. All of the 2009 incident records in WITS were classified by month, with the incident duration shown in Table 4-8. The three months with the highest average incident durations were January, March, and May. Meanwhile, April, July, and ▇▇▇▇ had the shortest average incident durations. On average, incidents last longer in winter than in summer. Mean 14.7 13.2 14.2 12.4 13.8 12.5 12.4 13.6 12.7 13.6 13.7 13.6 Clearance Time SD 27.0 21.7 28.3 23.9 32.7 22.9 20.9 25.9 21.3 23.8 22.8 27.7 Median 7 7 7 6 7 6 6 6 6 6 7 6 Max 407 360 570 866 1,020 567 377 505 370 402 300 542 Mean Winter Quarter 14 Spring Quarter 12.9 Summer Quarter 12.9 Autumn Quarter 13.6 Clearance Time SD 25.93 26.69 22.76 24.93 Max 570 1,020 505 542 Mean Total 13.3 Clearance Time SD 25.09 Median 6 Max 1,020 While there were fewer incid...
Incident duration. All Incidents recorded will be reconciled against the corresponding ticket raised by the Client Contact Center. The exact Incident duration will be calculated as the elapsed time between the Incident being reported to the Client Contact Center and the time when Service is restored.

Related to Incident duration

  • Pact Duration The provisions of this Pact shall come into effect from the date of signing of this Pact by the both parties. It expires for the Contractor 12 months after the last payment under the respective contract, and for all other Bidders 6 months after the contract has been awarded. If any claim is made / lodged by either party during this time, the same shall be binding and continue to be valid despite the lapse of this pact as specified above, unless it is discharged/determined by the Chairperson of the Principal.

  • Agreement Duration The term of the Agreement shall begin and end on the dates indicated in the Standard Grant Agreement, unless extended or terminated earlier in accordance with the applicable terms and conditions. The Grantee shall be eligible for reimbursement for work performed on or after the date of execution through the expiration date of this Agreement, unless otherwise specified in Attachment 2, Special Terms and Conditions. However, work performed prior to the execution of this Agreement may be reimbursable or used for match purposes if permitted by the Special Terms and Conditions.

  • Effective Date; Duration This Agreement shall become effective when signed by both parties and approved by the City’s legal counsel. Unless sooner terminated, this Agreement shall expire on June 30, 2019. Termination or expiration shall not extinguish or prejudice the City’s right to enforce this Agreement with respect to any default or defect in performance that has not been cured.

  • Contract Duration This contract shall commence with the date this contract was entered into and shall expire on August 31, 2022. No new projects may be assigned on or after the expiration date, but all projects assigned prior to the expiration date will be allowed to continue to completion with all the terms and conditions of this contract herein set forth remaining in full force and effect. The term of this contract may be extended in writing by the Commissioner.

  • Particular Methods of Procurement of Consultants’ Services 1. Quality- and Cost-based Selection. Except as otherwise provided in paragraph 2 below, consultants’ services shall be procured under contracts awarded on the basis of Quality and Cost-based Selection.