1 / 28

Evaluation of the “COMET” Incident Response Program

Evaluation of the “COMET” Incident Response Program. June 16, 2004 Dr. Robert Bertini Michael Rose. Oregon Department of Transportation. Presentation Outline. Research Objectives Freeway Management in Portland What are Incidents? What is Incident Response?

Download Presentation

Evaluation of the “COMET” Incident Response Program

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Evaluation of the “COMET” Incident Response Program • June 16, 2004 • Dr. Robert Bertini • Michael Rose Oregon Department of Transportation

  2. Presentation Outline • Research Objectives • Freeway Management in Portland • What are Incidents? • What is Incident Response? • Incident Response in Portland • Incident Data for the Region • Estimation and Costs of Incident Delay • Conclusions

  3. Research Objectives Demonstrate the use and display of archived data from multiple sources as a tool for evaluation and monitoring of freeway operations. Evaluate the effectiveness of the “COMET” incident response program in Portland, Oregon Develop tools to facilitate efficient deployment of resources and programs in other places

  4. Transportation System Management In the Portland metro area ODOT currently operates an extensive advanced traffic management system from the TMOC including: • 75 CCTV cameras • 18 variable message signs • 118 ramp meters • 436 inductive loop detectors • Digital archives of incident logs • AVL Archives of COMET movements • An extensive fiber optic communications system

  5. Traveler Information Variable Message Signs Traffic Reports www.tripcheck.com Traffic Cameras

  6. What are Incidents? • Crashes, breakdowns and other random events on our highways • They contribute to more than half of the delay on our highways • Lead to major road closures increase drivers’ exposure to hazardous conditions • Cause secondary crashes • Divert maintenance resources and reduce overall productivity

  7. What is Incident Response? • A proactive strategy for dealing with incidents • Roving response vehicles • CCTV network of traffic cameras • An operations center monitoring the cameras • Communications network linking the vehicles and the operations center

  8. Benefits of Incident Response • IR programs are the eyes and ears of highway system • They are proven strategy for reducing duration of incidents. They reduce delay, fuel consumption, accident exposure, air pollution and environmental impacts • Decrease emergency vehicle response times • Reduce secondary crashes • Improve safety for emergency and highway maintenance personnel • Improve relations between the driving public and the local transportation agency

  9. d Tow Truck Arrived Tow Truck Called Incident Effects Cleared Call Receive IR Arrived Incident Cleared Verified Incident Occurs Cumulative Vehicles Actual Recovery Incident Duration Capacity Flow Capacity Flow Demand Flow Total Delay Incident Flow Response Detection Clearance Time Time Typical Delay Curve Reducing incident duration by ½ reduces incident delay by ¾.

  10. Incident Response in Portland • The incident response program, known as “COMET”, began service in March 1997, and now covers the Portland metropolitan area nearly 24 hours a day with 11 specially equipped incident response vehicles.

  11. Incident Response in Portland • The vehicles are equipped with: • Variable message sign • Basic traffic control equipment • Gasoline and automotive fluids • Basic automotive tools • Communications system • Automatic Vehicle Location system

  12. Patrol Region

  13. Data Sources • Incident Database • Automated Vehicle Location • Automatic Traffic Recorders • Inductive Loop Detectors • Archived Weather Data

  14. Removal of 49,286 duplicate records 3 week sample for delay estimation 660 incidents 21,708 incidents 6,334 Incidents on I-5 860 Crashes on I-5 11,078 Stalls 3,188 Crashes 2001 Incident Data 70,976 incident records

  15. Low Medium High Incident Frequency Map

  16. Incident Types Lane Blocking Incidents N=21,728 N=18,920 2001 Incidents

  17. 2001 Incident Location N=13,464

  18. Crashes & Stalls Account for 65% of incidents in the region

  19. Crashes by Time of Day and Day of Week • Day of Week • Fridays had the highest crash frequency in 2001 Time of Day The highest crash frequency was during the evening peak

  20. Incidents by Month

  21. Rainy Days and Crashes

  22. Ongoing Incidents 1 Day

  23. Sunday Monday Tuesday Wednesday Thursday Friday Saturday IR Vehicles Weekday IR Vehicles Weekend Ongoing Incidents - One Year

  24. Filtering 164 delay causing incidents 3 Week Incident Delay Estimation 3 week sample for delay estimation 660 incidents • Manually matched incidents to ATRs • Determined the capacity reduction using incident data and tables from the Highway Capacity Manual • Average flow data for the specific hour of the incident were drawn from the 2001 ATR database. • The result was 112,000 vehicle hours of delay caused by incidents during the 3 week period • Estimated cost of additional fuel • consumption due to delay $150,000 • Estimated cost of lost time due to delay $2,800,000 • Total Estimated cost of delay for 3 weeks $2,950,000

  25. Estimation of Annual Incident Delay 2001-Extrapolated from 3 week sample- • If each incident were to increase in • duration by an average of 1 minute • the annual cost of delay increases by: $1,400,000 • The cost to operate COMET for one • year is about $750,000 • Estimated vehicle hours of delay: 1,940,000 hours • Estimated cost of additional fuel • consumption due to delay: $2,500,000. • Estimated cost of lost time due to delay: $48,500,000. • Total Estimated cost of incident delay: $51,000,000. For COMET to be cost effective the duration of each incident needs to be reduced by an average of 32 seconds.

  26. Efficiency Curve

  27. Conclusions • Comet is clearly beneficial. The responders only need to reduce the duration of each incident by just a few minutes to have a positive effect on the flow of traffic. • It is impossible to measure and assign a dollar value to the numerous other environmental and public relations benefits of the program. • Archived data is a rich and useful source of information. • Ongoing improvements to database entry and dispatching need to be made as traffic volumes and patterns change.

  28. Thank You • U.S. Department of Transportation • Transportation Northwest (TransNow) • Oregon Department of Transportation • Portland State University Department of Civil & Environmental Engineering • Dennis Mitchell, Jack Marchant, Richard Santa Ana and Eric Anderson of ODOT • Barnie Jones, Rob Edgar, Galen McGill and Edward Anderson at ODOT for their support Dr. Robert Bertini: bertini@pdx.edu Michael Rose: mwrose@pdx.edu The full report is available online at: http://www.its.pdx.edu/opbenefits.html

More Related