Broadening Integrated Corridor Management Stakeholders (2020) / Chapter Skim
Currently Skimming:
Pages 36-42
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 36... ...
36 Identifying performance metrics of interest to corridor operators and stakeholder entities is key to initiating conversations for enhanced two-way data and information sharing. Which Performance Metrics Should We Use to Evaluate How Well Our ICM Project Meets Our Goals and Objectives?
|
From page 37... ...
Type of Performance Metric Performance Metric Category Examples Quality of Service Average Congestion Conditions Travel time; travel time index; total delay (vehicles, persons) ; delay per vehicle; spatial extent of congestion; temporal extent of congestion; density Reliability Buffer index; planning time index Throughput Throughput (vehicle, persons)
|
From page 38... ...
38 Broadening Integrated Corridor Management Stakeholders • Agencies and stakeholders may be more proactive and responsive about getting involved in ICM if they were positioned to receive significant benefits from the arrangement, and understood/ recognized those benefits. Which Performance Metrics Are Important to This Stakeholder Group?
|
From page 39... ...
Designate Performance Metrics & Data Sources 39 In addition to real-time transit-specific data, transit planners are also interested in metrics such as parking demand at transit facilities, frequencies and causal factors for incidents that cause transit delays (e.g., traffic attempting to cut into high-occupancy toll [HOT] lanes)
|
From page 40... ...
40 Broadening Integrated Corridor Management Stakeholders while en route to their destinations. As a result, non-motorized roadway users generally have poor situational awareness of the dynamic traffic conditions on roadways.
|
From page 41... ...
Transportation Data Desired by Freight Stakeholders Freight Data Desired by Transportation Agencies • Truck travel times • Travel time reliability • Incident information (e.g., any official alternate truck routes, location of the incident, time, duration, nature, expected clearance times, extent of current or predicted delays) • Planned events, such as anticipated lane and roadway closures for scheduled maintenance • Lane closure information (e.g., location, time, duration, nature, and expected delay impacts)
|
From page 42... ...
Transportation Data Desired by Incident Response Stakeholders Incident Response Data Desired by Transportation Agencies • Ingress/egress routes • Emergency vehicle travel times • Lane closures • Incident location (nearest postmile, direction) • Incident severity • Anticipated threats/hazards to incident responders • Personnel, vehicle, and equipment/supplies needed (e.g., towing and recovery, hazardous material spills, coroner, etc.)
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.