CDOT Region 4 Intelligent Transportation Systems Strategic ...
CDOT Region 4 Intelligent Transportation Systems Strategic ...
CDOT Region 4 Intelligent Transportation Systems Strategic ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>CDOT</strong> <strong>Region</strong> 4<br />
<strong>Intelligent</strong><br />
<strong>Transportation</strong> <strong>Systems</strong><br />
<strong>Strategic</strong> Implementation<br />
Plan<br />
June 2011<br />
Colorado Department<br />
of <strong>Transportation</strong>
Acknowledgements<br />
Our thanks to the following persons who have contributed to the successful completion of this ITS <strong>Strategic</strong><br />
Plan:<br />
Roger Isaacson<br />
Broomfield Police<br />
Aaron Moss<br />
Colorado Department of <strong>Transportation</strong>-DTD<br />
William Johnson<br />
Colorado Department of <strong>Transportation</strong>-DTD<br />
Phyllis Snider<br />
Colorado Department of <strong>Transportation</strong>-DTD<br />
Dan Wells<br />
Colorado Department of <strong>Transportation</strong>-Permits<br />
Joe Olsen<br />
City of Fort Collins<br />
Eric Bracke<br />
City of Greeley<br />
Bill Hange<br />
City of Loveland<br />
Captain Paul Matzke<br />
Colorado State Patrol - 3A<br />
Major Kris Meredith<br />
Colorado State Patrol - 3A<br />
Captain Gaylon Griffin<br />
Colorado State Patrol - 3B<br />
Captain Rob Marone<br />
Colorado State Patrol - 3C<br />
Pat Castle<br />
Colorado State University<br />
Rick Santos<br />
Federal Highway Administration<br />
Marlys Sittner<br />
Transfort<br />
Joel Tower<br />
Fort Collins Police<br />
Brad Patterson<br />
GET<br />
Martina Wilkinson<br />
Larimer County<br />
John Manago<br />
Larimer County Sheriff's Office<br />
Marcy Abreo<br />
COLT<br />
Aaron Fodge<br />
North Front Range Metropolitan Planning Organization<br />
Hope Wright<br />
Department of Revenue - POE<br />
Jeff Anderson<br />
Department of Revenue - POE<br />
Rick Archer<br />
Department of Revenue - POE<br />
John Hannon<br />
Rocky Mountain National Park<br />
Larry Gamble<br />
Rocky Mountain National Park<br />
Trish Dickerson<br />
Town of Timnath<br />
TJ Dlubac<br />
Town of Timnath<br />
Abra Geissler<br />
Town of Timnath<br />
Scott Zurn<br />
Town of Estes Park<br />
Curtis Hall<br />
Weld County<br />
Ryan Rose<br />
University of Northern Colorado<br />
Mel Everhart<br />
Weld County<br />
Trent Bushner<br />
Yuma County<br />
Ken DiPinto<br />
Colorado Department of <strong>Transportation</strong>-ITS Branch<br />
Bruce Coltharp<br />
Colorado Department of <strong>Transportation</strong>-ITS Branch<br />
John Nelson<br />
Colorado Department of <strong>Transportation</strong>-ITS Branch<br />
Joe Tucker<br />
Colorado Department of <strong>Transportation</strong>-ITS Branch<br />
John Williams<br />
Colorado Department of <strong>Transportation</strong>-ITS Branch<br />
Larry Haas Colorado Department of <strong>Transportation</strong>-<strong>Region</strong> 4<br />
Ina Zisman Colorado Department of <strong>Transportation</strong>-<strong>Region</strong> 4<br />
Karen Schneiders Colorado Department of <strong>Transportation</strong>-<strong>Region</strong> 4<br />
Myron Hora Colorado Department of <strong>Transportation</strong>-<strong>Region</strong> 4<br />
Phillip Anderle Colorado Department of <strong>Transportation</strong>-<strong>Region</strong> 4<br />
Pawan Kharbanda<br />
Enroute<br />
Rich Follmer<br />
FHU<br />
Navin Nageli<br />
Navjoy<br />
Venkata Punati<br />
Navjoy
ACRONYMS AND ABBREVIATIONS<br />
ARRA…………………………………………………American Recovery and Reinvestment Act<br />
CCTM……….…………………………………………..City and County of Traffic Management<br />
CCTV..................................................................................................Closed Circuit Television<br />
<strong>CDOT</strong>…………………………………………………….Colorado Department of <strong>Transportation</strong><br />
CIP………………………………………………..………………..Capital Improvement Program<br />
CMAQ……………………………………………...………….Congestion Mitigation Air Quality<br />
CTMC………………………………...…………....Colorado <strong>Transportation</strong> Management Center<br />
CVO……………………………………………………………...Commercial Vehicle Operations<br />
DMS……………………………………………………….……...……….Dynamic Message Sign<br />
DMV…………………………………………………………………..Division of Motor Vehicles<br />
DRCOG……………………………………………......Denver <strong>Region</strong>al Council of Governments<br />
FHWA…………………………………………………………...Federal Highway Administration<br />
FLEX……………………………………………………………….Fort Collins Loveland Express<br />
FO………………………………………………………………………………………Fiber Optic<br />
FTA………………………………………………………………..Federal Transit Administration<br />
HAR……………………………………………………………………..Highway Advisory Radio<br />
HES…………………………………………………………...Hazard Elimination Safety Program<br />
HOT………………………………………………………………………….High Occupancy Toll<br />
HOV……………………………………………………………………..High Occupancy Vehicle<br />
IMP…………………………………………………………………….Incident Management Plan<br />
ISP………………………………………………………………….Information Services Provider<br />
ITS……………………………………………………………..<strong>Intelligent</strong> <strong>Transportation</strong> <strong>Systems</strong><br />
MPO………………………………………...………………..Metropolitan Planning Organization<br />
NFR MPO………………...……………..North Front Range Metropolitan Planning Organization
PNR..………………………………………………………………………………….Park-N-Ride<br />
RM…………………………………………………………………………………Ramp Metering<br />
RTMS………………………………………………………….Remote Traffic Microwave Sensor<br />
RWIS…………………………………………………….Road and Weather Information <strong>Systems</strong><br />
SEA………………………………………………………………...<strong>Systems</strong> Engineering Analysis<br />
SH………………………………………………………..………………………….State Highway<br />
SRTS……………………………………………............Colorado Safe Routes to School Program<br />
STP………………………………………………………….……...Statewide <strong>Transportation</strong> Plan<br />
TDM…………………………………………………………………Travel Demand Management<br />
TMC…………...…………………………………………...…………Traffic Management Center<br />
TOC……………………………………………………...……………….Traffic Operation Center<br />
TOD…………………………………………………………………………….…….Time-of-Day<br />
TPR…………………………………………………….………....<strong>Transportation</strong> Planning <strong>Region</strong><br />
TSSIP……………………………………………….Traffic Signal System Improvement Program<br />
TTI……………………………………………………………..…………..Travel Time Indicators<br />
TT DMS…………………………………………………….Travel Time Dynamic Message Sign<br />
VII………………………………………………………………Vehicle Infrastructure Integration
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
Table of Contents<br />
I. INTRODUCTION ................................................................................................................... 4<br />
A. Background ................................................................................................................................... 4<br />
B. Purpose and Description of Study Area ........................................................................................ 4<br />
C. ITS Stragtegic Implementaton Plan Process ................................................................................. 5<br />
D. Conformance with the National ITS Architecture ........................................................................ 5<br />
E. Turbo Architecture ........................................................................................................................ 6<br />
F. FHWA System Engineering Process ............................................................................................ 6<br />
G. Benefits of <strong>CDOT</strong> ITS Deployments ............................................................................................ 6<br />
II. PROCESS FOR DEVELOPING THE ITS IMPLEMENTATION PLAN ..................... 10<br />
A. Overview ..................................................................................................................................... 10<br />
B. Working Group ........................................................................................................................... 11<br />
C. Stakeholder Consultation ............................................................................................................ 12<br />
D. Planning Document Review ........................................................................................................ 13<br />
E. ITS Inventory .............................................................................................................................. 13<br />
F. Identification of <strong>Transportation</strong> Problems .................................................................................. 13<br />
G. Available ITS Solutions .............................................................................................................. 13<br />
H. Project Development ................................................................................................................... 13<br />
I. Interfaces with DRCOG ITS <strong>Strategic</strong> Plan ................................................................................ 14<br />
III. EXISTING ITS INVENTORY ............................................................................................ 15<br />
A. Review of Relevant Documents .................................................................................................. 15<br />
B. Existing ITS Traffic Inventory .................................................................................................... 15<br />
C. Existing Transit ITS Inventory ................................................................................................... 15<br />
D. Existing Inventory for Other Stakeholders ................................................................................. 15<br />
IV. TRANSPORTATION PROBLEMS IN STUDY AREA ................................................... 16<br />
A. Identification of <strong>Transportation</strong> Problems .................................................................................. 16<br />
B. <strong>Transportation</strong> Service Areas ...................................................................................................... 20<br />
C. <strong>Region</strong>al Ranking of <strong>Transportation</strong> Problems ........................................................................... 22<br />
D. Linking Problems to the Network ............................................................................................... 24<br />
V. ITS SOLUTIONS TO TRANSPORATION PROBLEMS ................................................ 25<br />
A. Available ITS Solutions to <strong>Transportation</strong> Problems ................................................................. 25<br />
B. Market Packages Analysis for the <strong>Region</strong> .................................................................................. 30<br />
C. Linking <strong>Transportation</strong> Problems to Market Packages ............................................................... 43<br />
D. Linking TSAs to Market Packages ............................................................................................. 43<br />
VI. ITS DEPLOYMENT STRATEGIES WITHIN THE REGION ....................................... 44<br />
A. Recommended ITS Strategies for the <strong>Region</strong> ............................................................................. 44<br />
B. Limitations for ITS Deployment ................................................................................................ 47<br />
C. Recommended ITS Deployment Timeframe .............................................................................. 48<br />
VII. ITS DEPLOYMENT COSTS .............................................................................................. 49<br />
A. ITS Deployment for Corridors .................................................................................................... 49<br />
B. ITS Deployment for Transit ........................................................................................................ 50<br />
C. ITS Deployment for <strong>Region</strong>al ..................................................................................................... 51<br />
I
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
D. Financial Summary .................................................................................................................... 51<br />
E. Project Sequencing ...................................................................................................................... 52<br />
VIII. CONCLUSION ..................................................................................................................... 53<br />
A. <strong>Region</strong>al ITS Project Funding Sources ....................................................................................... 53<br />
B. <strong>Region</strong> 4 ITS Project Funding Deficiencies................................................................................ 53<br />
C. Champion for ITS within the <strong>Region</strong> .......................................................................................... 54<br />
D. Next Steps ................................................................................................................................... 55<br />
List of Tables<br />
Table 1: <strong>Region</strong>al Problems Aligned to Applicable <strong>Transportation</strong> Service Areas ...................... 21<br />
Table 2: <strong>Region</strong>al Ranking of <strong>Transportation</strong> Problems ............................................................... 23<br />
Table 3: Available ITS Solutions to <strong>Transportation</strong> Problems ..................................................... 26<br />
Table 4: Applicable Market Packages within the <strong>Region</strong> ............................................................. 31<br />
Table 5: Needed ITS Investment Summary for <strong>Region</strong> 4 Corridor Projects ................................ 50<br />
Table 6: Needed ITS Investment Summary for <strong>Region</strong> 4 Transit Projects ................................... 50<br />
Table 7: Needed ITS Investment Summary for <strong>Region</strong> 4 <strong>Region</strong>al Projects ................................ 51<br />
Table 8: Summary of Needed ITS Investment for <strong>Region</strong> 4 ......................................................... 51<br />
Table 9: Funding Sources .............................................................................................................. 53<br />
List of Figures<br />
Figure 1: <strong>CDOT</strong> <strong>Region</strong> 4 and Planning <strong>Region</strong>s ........................................................................ 4<br />
Figure 2: <strong>CDOT</strong> <strong>Region</strong> 6 Ramp Metering Benefits (I-25 and C-470) ........................................ 7<br />
Figure 3: ITS <strong>Strategic</strong> Plan Development Process .................................................................... 10<br />
Figure 4: <strong>CDOT</strong> ITS Inventory within the <strong>Region</strong>…………………………………………….....<br />
List of Appendices<br />
Appendix A:<br />
Appendix B:<br />
Appendix C:<br />
Appendix D:<br />
Appendix E:<br />
Appendix F:<br />
Appendix G:<br />
Consolidated Existing Traffic Inventory (<strong>CDOT</strong> and Urban Stakeholders)<br />
Existing <strong>CDOT</strong> ITS Equipment by Corridor<br />
Consolidated Existing Inventory (Transit Stakeholders)<br />
Existing Inventory Other Stakeholders (Pull-out-Areas and Load Deficient Structures)<br />
<strong>Transportation</strong> Problems By Stakeholder Group (<strong>CDOT</strong> Stakeholders)<br />
Corridors & Priority of <strong>Transportation</strong> Problems<br />
<strong>Transportation</strong> Problems Linking Market Packages<br />
II
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
Appendix H:<br />
Appendix I:<br />
Appendix J:<br />
Appendix K:<br />
Appendix L:<br />
Appendix M:<br />
Appendix N:<br />
Appendix O:<br />
Appendix P:<br />
Linking <strong>Transportation</strong> Service Areas to Market Packages<br />
Pull-Out Area Priorities<br />
<strong>Region</strong> 4 ITS Deployment by Corridor<br />
Individual Corridor Priorities & ITS Deployment Discussion<br />
ITS Device Cost (2011 Dollars)<br />
ITS Deployments Cost by Time Frame and Device<br />
Corridor Deployment Sheets (Not included at time)<br />
<strong>Region</strong> 4 ITS Transit Deployments<br />
<strong>Region</strong> 4 ITS <strong>Region</strong>al Deployments<br />
III
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
I. INTRODUCTION<br />
A. Background<br />
<strong>Intelligent</strong> <strong>Transportation</strong> <strong>Systems</strong> are defined as the application of technology to address transportation<br />
problems and to assist in the management of the transportation network. Common ITS devices include<br />
Dynamic Message Signs (DMS) used to provide traveler information, Closed Circuit Television (CCTV)<br />
cameras used to monitor traffic conditions, electronic sensors used to monitor pavement and Road and<br />
Weather Information Service (RWIS) stations to monitor weather conditions, and traffic signal systems<br />
that are programmed to adapt their timing in response to traffic congestion.<br />
Within Colorado Department of <strong>Transportation</strong> (<strong>CDOT</strong>) <strong>Region</strong> 4 boundaries, <strong>CDOT</strong> and several<br />
agencies have invested significant resources in the deployment of <strong>Intelligent</strong> <strong>Transportation</strong> System (ITS)<br />
infrastructure. <strong>CDOT</strong> and local agencies intend to continue this ITS investment in the future given the<br />
mobility and safety benefits derived from actively managing the transportation system.<br />
Although ITS had its beginnings in urban areas, the falling cost and increased availability of proven<br />
transportation technologies has enabled ITS to be successfully deployed in rural areas and small cities that<br />
have recognized the operational, safety, and mobility benefits that ITS can provide.<br />
B. Purpose and Description of Study Area<br />
In early 2004, an ITS <strong>Strategic</strong> Plan and Architecture was completed that covered the geographical area<br />
of the North Front Range Metropolitan Planning Organization (NFR MPO) and Estes Park area.<br />
Due to the special requirements of ITS projects, which follow a process more typical of a technology<br />
project than a roadway project, the Colorado Department of <strong>Transportation</strong> (<strong>CDOT</strong>), in cooperation with<br />
the cities, towns and the NFR MPO in the <strong>Region</strong> have developed a <strong>Strategic</strong> Plan for the deployment of<br />
ITS in <strong>CDOT</strong> <strong>Region</strong> 4 over the next ten years. <strong>CDOT</strong> <strong>Region</strong> 4 covers the northeastern corner of<br />
Colorado comprising 9 counties including NFR MPO, Denver <strong>Region</strong>al Council of Governments<br />
(DRCOG), North Front Range and Upper Front Range <strong>Transportation</strong> Planning <strong>Region</strong>s (TPRs).<br />
Figure 1 shows the project area and the planning regions.<br />
Figure 1:<br />
<strong>CDOT</strong> <strong>Region</strong> 4 and Planning <strong>Region</strong>s<br />
4
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
The purpose of this project is to update and expand the previously developed ITS <strong>Strategic</strong> Plan and ITS<br />
Architecture to include all of the geographical area in <strong>Region</strong> 4. Specific tasks will include an assessment<br />
of how ITS can address critical transportation problems, an inventory of existing and planned ITS<br />
applications, generation of a ITS <strong>Strategic</strong> Implementation Plan and development of an ITS <strong>Region</strong>al<br />
Architecture. The <strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan (<strong>CDOT</strong> R4 ITS Plan) will provide<br />
a comprehensive document that details a vision and framework for the application of ITS to meet<br />
recognized transportation problems within the <strong>Region</strong>.<br />
The <strong>CDOT</strong> <strong>Region</strong> 4 ITS Plan shows how ITS applications will be implemented in a systematic and<br />
coordinated manner using a corridor approach. The <strong>CDOT</strong> R4 ITS Plan will also identify the funding<br />
needs, recommended deployment time frames and potential funding sources. The plan can be used by<br />
Staff in communicating ITS needswithin the <strong>Region</strong>.<br />
C. ITS Stragtegic Implementaton Plan Process<br />
Development of the ITS <strong>Strategic</strong> Implementation Plan in many ways followed a traditional planning<br />
process, including forming an ITS Working Group to guide its development, conducting a needs<br />
assessment, reviewing existing and planned ITS projects, and developing a prioritized ITS project list.<br />
However, on the technology side, the process also included a systems engineering analysis that identified<br />
opportunities and related requirements for systems integration, interagency cooperation, and<br />
communications infrastructure needs. These elements were factored into the development of the projects<br />
identified in the ITS <strong>Strategic</strong> Implementation Plan. From this point, the ITS <strong>Strategic</strong> Implementation<br />
Plan will provide input in the form of recommended ITS projects to the area’s existing formal planning<br />
process.<br />
D. Conformance with the National ITS Architecture<br />
In 1997, the Federal Highway Administration (FHWA) began preparing a National ITS Architecture and<br />
Standards in an effort to guide standardized development and deployment of ITS across America. The<br />
architecture established a framework to facilitate the regional deployment of ITS projects, while the<br />
standards help ensure the compatibility and maintainability of the deployed technologies.<br />
The <strong>Transportation</strong> Equity Act for the 21 st Century (TEA-21) requires all <strong>Intelligent</strong> <strong>Transportation</strong><br />
<strong>Systems</strong> (ITS) projects funded from the Highway Users Trust Fund (federal funds), be in conformance<br />
with the National ITS Architecture and appropriate standards. The Federal Highway Administration's<br />
(FHWA) “Final Rule” and the Federal Transit Administration's (FTA) “Policy” on National ITS<br />
Architecture became effective April 8, 2001 and is contained in Chapter 23 Part 940 of the Code of<br />
Federal Regulations (CFR).<br />
The purpose of the National ITS Architecture is to foster institutional agreement and technical integration<br />
for the implementation of ITS projects or groups of projects into regional ITS systems. The National ITS<br />
Architecture defines the ITS system components, key functions, organizations involved in developing an<br />
architecture, and the type of information to be shared between organizations and between parts of the<br />
system. Key elements of 23 CFR 940 that are of particular relevance to this project include:<br />
<br />
<br />
§ 940.5 that requires the National ITS Architecture be used to develop a local implementation, or<br />
a “regional ITS architecture”;<br />
§ 940.5.10 that requires that procedures and responsibilities for the maintenance of the regional<br />
ITS architecture be established; and,<br />
5
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
§ 940.5.11 that requires that all ITS projects be developed using a systems engineering analysis<br />
(an iterative process of design, testing, and evaluation).<br />
E. Turbo Architecture<br />
An Architecture database will be created using Turbo Architecture version 5.0 for <strong>CDOT</strong> <strong>Region</strong> 4 ITS<br />
Architecture. Turbo Architecture is a software tool that allows users to catalogue and organize regional<br />
and/or project architectures in a database format. The software also provides users with enhanced<br />
functionality in working with architecture stakeholders, elements, market packages, operational concepts,<br />
functional requirements, interfaces, standards and agreements. The software defines the architecture,<br />
relationships, interconnects between stakeholders and elements and gives the user the ability to access<br />
physical and logical diagrams at multiple levels. Use of the software will facilitate consistency, version<br />
control, maintenance and subsequent updating of the <strong>Region</strong>al Architecture. It will also be useful in<br />
obtaining and providing project Architecture related information as is required by, and in order to comply<br />
with, FHWA <strong>Systems</strong> Engineering Analysis.<br />
F. FHWA System Engineering Process<br />
In order to meet the requirements of 23 CFR Part 940 to receive federal funding, an ITS project must<br />
demonstrate that a systems engineering analysis was performed during the design of the project. The<br />
systems engineering analysis process includes the following seven elements that must be addressed to<br />
ensure a project conforms to the federal ITS requirements:<br />
1. Description of how project fits into the <strong>Region</strong>al ITS Architecture<br />
2. Roles and responsibilities of participating agencies<br />
3. Requirements definition<br />
4. Analysis of alternative system configurations and technology options<br />
5. Procurement options<br />
6. Applicable ITS standards and testing procedures<br />
7. Procedures and resources necessary for operations and management of the system<br />
<strong>CDOT</strong> has developed <strong>Systems</strong> Engineering Analysis (SEA) Guidelines that describe the method of<br />
demonstrating compliance with the federal ITS requirements. The requirement for SEA only applies to<br />
those ITS projects that have federal funding; however <strong>CDOT</strong> and DRCOG believe that there is value in<br />
requiring all ITS projects to use the SEA in order to ensure architectural consistency and integrity.<br />
Again, the Turbo Architecture databases will be very useful in obtaining and providing much of the<br />
project Architecture related information required in order to comply with the systems engineering<br />
analysis. FHWA or FTA may independently request additional documentation on the systems<br />
engineering analysis before federal funds are released for construction.<br />
G. Benefits of <strong>CDOT</strong> ITS Deployments<br />
The benefits of any single ITS device are often difficult to quantify individually, however the benefits<br />
become more quantifiable within the context of the application, i.e. (traveler information, Traffic<br />
Responsive Signal Control, traffic and incident management), as the many elements of the system are<br />
integrated. This integration empowers operators to positively impact current travel conditions, react<br />
quickly to incidents and congestion along corridors, assist in modifying travel plans based on current<br />
6
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
roadway conditions, and disseminate real-time traveler information. In general <strong>CDOT</strong>’s goal in<br />
deploying ITS technologies is to improve the productivity of the transportation system and to provide<br />
services that enhance and improve the mobility and safety of Colorado’s traveling public. The following<br />
are some examples that demonstrate the benefits of ITS locally and/or nationally.<br />
‣ Traffic Signal Timing and Traffic Responsive Operations - Through ITS system detection and fiber<br />
optic communication infrastructure traffic engineers are able to coordinate and maintain progression<br />
along adjacent signals of a corridor. This ITS infrastructure also allows for the collection of traffic data<br />
(speed, volume, and occupancy) empowering Traffic Responsive signal operations that adjust signal<br />
timing to existing conditions. Overall, the increased reliability in signal timing operations, due to ITS,<br />
allow for the most efficient utilization of the existing roadway. The benefits of signal timing are well<br />
documented and these include vehicle hours of travel, fuel consumption, time and fuel cost savings and<br />
reduction in total pollutant emissions.<br />
‣ Ramp Metering – Within <strong>CDOT</strong> <strong>Region</strong> 6, the benefits of ramp meters were documented by<br />
conducting before and after studies. For example, in December 2003, <strong>CDOT</strong> <strong>Region</strong> 6 implemented ramp<br />
metering on I-25 southbound between 104 th Avenue and 84 th Avenue and C-470 westbound between<br />
Bowles and Quincy Avenue. Initially the ramp meters were in operation during the morning peak period<br />
(6-8:30 a.m.). Prior to the implementation of these ramp meters, <strong>CDOT</strong> ITS Branch and <strong>CDOT</strong> <strong>Region</strong> 6<br />
conducted before conditions studies on the two corridors. After conditions studies were conducted during<br />
late January 2004. Figure 2 shows the benefits noted in the comparison of before and after conditions<br />
studies.<br />
Figure 2:<br />
<strong>CDOT</strong> <strong>Region</strong> 6 Ramp Metering Benefits (I-25 and C-470)<br />
A study conducted in Minneapolis Minnesota further reinforces the benefits of ramp meters. This study<br />
was conducted after public questioning of the use of ramp metering and a legislative mandate requiring<br />
MNDOT to study the effectiveness of ramp meters. MNDOT conducted the study by comparing before<br />
and after conditions for “with” and “without” ramp meters scenarios. The following findings resulted<br />
from the study:<br />
<br />
<br />
Traffic Volumes and Throughput: After the meters were turned off, there was an average nine<br />
percent traffic volume reduction on freeways and no significant traffic volume change on parallel<br />
arterials included in the study. Also, during peak traffic conditions, freeway mainline throughput<br />
declined by an average of 14 percent in the “without” meters conditions.<br />
Travel Time Reliability: Without ramp metering, freeway travel time is almost twice as<br />
unpredictable as with ramp metering. The ramp metering system produced an annual reduction of<br />
2.6 million hours of unexpected delay.<br />
7
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
<br />
Benefit/Cost Analysis: Ramp metering results in annual savings of approximately $40 million to<br />
the Twin Cities traveling public. The benefits of ramp metering outweigh the costs by a<br />
significant margin and result in a net benefit of $32 to $37 million per year.<br />
‣ Courtesy Patrol – In a study conducted for 2003 Mile High Courtesy Patrol (MHCP) operations, it<br />
was determined that MHCP assisted in over 6,000 incidents, based on CTMC Dispatch data. This<br />
amounted to a yearly estimated benefit of:<br />
<br />
<br />
Over 500,000 hours of vehicle delay averted<br />
Over $9 Million dollar savings from reduced delay<br />
‣ Dynamic Message Signs – In general, it is difficult to measure the stand-alone benefits of Dynamic<br />
Message Signs. However, the benefits regarding the use of DMS are very high when used in conjunction<br />
with other systems. These benefits include dissemination of real-time travel time and highway conditions<br />
information (incidents, events and other related corridor information), to which allow drivers to make<br />
informed decisions regarding selection of alternative routes as well as reducing driver related stress and<br />
the occurrence of secondary crashes.<br />
‣ Real-Time Travel Time Applications – <strong>CDOT</strong> currently utilizes Travel Time Applications along I-<br />
70 and I-25 corridors within <strong>CDOT</strong> <strong>Region</strong>s 1, 2 and 6. Through the use of real-time travel time<br />
applications, the dissemination of real time corridor performance (travel times, delay, congestion)<br />
empowers motorists with information that allows them to modify their travel routes and times. Travel time<br />
applications are envisioned for freeway corridors throughout Front Range. It is anticipated that for a<br />
typical freeway corridor (carrying approximately 100,000 vehicles/year) realizing a 3 minute weekly<br />
reduction in travel times, the resulting savings would be:<br />
<br />
<br />
Approximately 120,000 gallons/year in fuel consumption reduction<br />
Approximately 300,000 lbs/year in CO reductions<br />
‣ Traffic Management and Traffic Operation Centers (TMCs & TOCs)<br />
Through the use of <strong>Intelligent</strong> <strong>Transportation</strong> System (ITS) devices, TMCs and TOCs gather real time<br />
roadway condition information for decision making to improve overall traffic flow and aid in reducing<br />
congestion. By acting as a focal point for traffic information, the TMC and TOC permit engineers to more<br />
effectively use existing traffic management tools and provide a platform for the implementation of future<br />
technological advances in traffic management. The ability of local and regional TMCs and TOCs to<br />
communicate between each other is also key to regional cooperation, sharing of information and<br />
management of cross-jurisdictional congestion and incident management. The TMC and TOC are a tool<br />
for reducing congestion and managing incidents that directly benefits motorists.<br />
‣ Incident and Event Management Plans<br />
Incident and event management plans yield significant benefits through reduced vehicle delays and<br />
enhanced safety to motorists through the reduction of incident frequency, improved coordination,<br />
response and clearance times in response to incidents and large events. <strong>CDOT</strong> currently has coordinated<br />
Incident Management Operations ongoing at the Colorado Traffic Management Center (CTMC),<br />
Eisenhower-Johnson Memorial Tunnel (EJMT), Hanging Lakes Tunnel (HLT), and Colorado Springs<br />
Traffic Management Center (CSTMC) facilities. <strong>CDOT</strong> <strong>Region</strong> 4 Incident Management activities are<br />
coordinated as part of the CTMC operations. In Colorado, there are 18 Incident Management Plans<br />
including I-25 North and US-36 within <strong>CDOT</strong> <strong>Region</strong> 4. A study was conducted in Maryland in 2002 of the<br />
CHART Incident Management system. At the time of the study, CHART consisted of the following operational<br />
components: traffic monitoring, incident response, traffic management, and traveler information (i.e., live traffic<br />
8
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
cameras, real-time traffic maps, weather, and local traveler information). The results below highlight the findings of<br />
the study of incident response savings realized by CHART Highway Incident Management operations:<br />
Reduced delay by about 30 million vehicle hours and saved about 5 million gallons of fuel<br />
Contributed to a 28.6% reduction in the average incident duration<br />
Resulted in 377 fewer secondary incidents, as a result of primary incidents, in 2002<br />
The State of Georgia also conducted an evaluation of their NaviGAtor integrated ITS system. At the time<br />
of their study (1997-98) the ITS elements of NAVIGATOR included freeway management, incident<br />
management, multimodal traveler information, transit management, electronic toll collection, electronic<br />
fare payment, and traffic signal control, which constituted seven of the nine elements of the <strong>Intelligent</strong><br />
<strong>Transportation</strong> Infrastructure. Six sections of I-75 and I-85 where ITS technologies were fully<br />
implemented (including operators, incident detection system, courtesy patrol, and cameras) were analyzed<br />
for incident duration only. Using before and after data and very conservative assumptions, each section<br />
was evaluated to determine the reduction in the average incident duration since NAVIGATOR was<br />
deployed. The study documented the following findings.<br />
A 23-minute reduction in incident duration during 1997<br />
An estimated yearly cost savings of $44.6 million due to the above reduced delay time.<br />
It is expected that as <strong>CDOT</strong> continues the expansion and integration of ITS devices, incorporating new<br />
technologies and completing ITS Infrastructure coverage, the ITS Incident Management system will<br />
continue to yield similar if not greater results to the above documented studies.<br />
For further information of ITS related benefits please visit the following FHWA website;<br />
http://www.benefitcost.its.dot.gov<br />
9
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
II.<br />
PROCESS FOR DEVELOPING THE ITS IMPLEMENTATION PLAN<br />
This section describes the approach taken by the project team to develop the <strong>CDOT</strong> ITS <strong>Strategic</strong><br />
Implementation Plan.<br />
A. Overview<br />
Development of the ITS <strong>Strategic</strong> Plan followed the process illustrated in Figure 3. This process included<br />
extensive interaction with the regional stakeholders. Subsequent subsections describe each step of the<br />
process.<br />
Figure 3: ITS <strong>Strategic</strong> Implementation Plan Development Process<br />
10
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
B. Working Group<br />
An ITS working group was established as the body that provided feedback and oversaw development of<br />
the ITS <strong>Strategic</strong> Plan. Members of the working group were technical staff from numerous agencies that<br />
expressed interest in ITS implementation. The following member agencies were invited to participate:<br />
<br />
<br />
MPO/TPR<br />
North Front Range Metropolitan Planning<br />
Upper Front Range <strong>Transportation</strong> Planning<br />
<strong>Region</strong><br />
State<br />
<strong>CDOT</strong> <strong>Region</strong> 4<br />
<strong>CDOT</strong> Division of <strong>Transportation</strong><br />
Development<br />
<br />
<br />
<br />
<br />
<br />
Eastern Front Range <strong>Transportation</strong><br />
Planning <strong>Region</strong><br />
Denver <strong>Region</strong>al Council of<br />
Governments<br />
<strong>CDOT</strong> ITS Branch<br />
<strong>CDOT</strong> Permits<br />
CDOR POE<br />
<br />
<br />
<br />
<br />
<br />
Counties<br />
Boulder County<br />
Larimer County<br />
Logan County<br />
Morgan County<br />
Phillips County<br />
<br />
<br />
<br />
<br />
Sedgwick County<br />
Washington County<br />
Weld County<br />
Yuma County<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
Cities<br />
Akron<br />
Ault<br />
Berthoud<br />
Boulder<br />
Brush<br />
Dacono<br />
Eaton<br />
Eckley<br />
Erie<br />
Estes Park<br />
Evans<br />
Firestone<br />
Johnstown<br />
Julesburg<br />
Keensburg<br />
Kersey<br />
Lafayette<br />
La Salle<br />
Lochbuie<br />
Log Lane Village<br />
Longmont<br />
Louisville<br />
Loveland<br />
Lyons<br />
Mead<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
Fleming<br />
Fort Collins<br />
Fort Lupton<br />
Fort Morgan<br />
Fredrick<br />
Garden City<br />
Gilcrest<br />
Greeley<br />
Grover<br />
Haxtun<br />
Hillrose<br />
Holyoke<br />
Hudson<br />
New Raymer<br />
Otis<br />
Ovid<br />
Paoli<br />
Pierce<br />
Platteville<br />
Sedgwick<br />
Sterling<br />
Superior<br />
Timnath<br />
Ward<br />
Wiggins<br />
11
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
<br />
<br />
<br />
Merino<br />
Milliken<br />
Nederland<br />
<br />
<br />
<br />
Wellington<br />
Windsor<br />
Wray<br />
<br />
<br />
Transit<br />
Transfort<br />
The City of Loveland Transit<br />
<br />
<br />
Greeley Evans Transit<br />
<strong>Region</strong>al Transit District<br />
<br />
<br />
Law Enforcement/Emergency Management<br />
Colorado State Patrol<br />
Local Law Enforcement Agencies<br />
<br />
Poudre Valley Fire District<br />
<br />
<br />
<br />
<br />
<br />
<br />
Other Members<br />
Rocky Mountain National Park<br />
Division Of Local Affairs<br />
Colorado State University<br />
University Of Northern Colorado<br />
Northern Colorado Economic Development<br />
Corporation<br />
<strong>CDOT</strong> Division of Aeronautics<br />
<br />
<br />
<br />
<br />
Colorado Motor Carriers Association<br />
Federal Highway Administration<br />
United States Department of<br />
Agriculture Forest Services<br />
Northeast Colorado Association of<br />
Local Governments<br />
The working group was convened at critical project milestones to review information and provide<br />
direction. Meeting minutes and other documents resulting from these meetings were distributed to the<br />
group, and posted on the project website at COTrip.org.<br />
C. Stakeholder Consultation<br />
Seven stakeholder groups were established to provide assistance with their respective technical areas to<br />
identify transportation problems that could be addressed by ITS applications. Additionally, each<br />
stakeholder group provided an inventory of existing and immediately pending ITS implementations<br />
within their jurisdiction. Each member participated with the understanding that ITS planning integrates<br />
regional, local, modal and organizational requirements. The following shows the stakeholder groups and<br />
agencies that participated in each of the groups:<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<strong>CDOT</strong> – <strong>CDOT</strong> <strong>Region</strong> 4 (Traffic, Maintenance, Planning), <strong>CDOT</strong> ITS Branch and <strong>CDOT</strong> DTD<br />
Transit – Transfort, Greeley Evans Transit (GET) and City of Loveland Transit (COLT)<br />
Urban – Loveland, Fort Collins, Greeley and NFR MPO<br />
Rural – Local cities and counties in rural areas<br />
Law Enforcement – Colorado State Patrol, Police from Fort Collins, Broomfield, Loveland, Greeley<br />
and Larimer County Sherriff<br />
Commercial Vehicles – Department of Revenue - Port-of-Entries (POE) and <strong>CDOT</strong> Permits<br />
Technology – University of Northern Colorado, Colorado State University, Towns of Estes Park and<br />
Timnath and <strong>CDOT</strong> ITS Branch<br />
In addition to the above stakeholder groups, the project team met separately with Rocky Mountain<br />
National Park (RMNP) and the Town of Estes Park to discuss transportation issues in the area.<br />
12
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
D. Planning Document Review<br />
A review of existing planning documents in the <strong>Region</strong> was conducted in order to provide insight into the<br />
types of transportation problems and priorities already identified by the regional planning organizations,<br />
as well as to understand how the <strong>Region</strong> ITS <strong>Strategic</strong> Implementation Plan could complement these<br />
existing efforts. Following the document review, a summary of the key points of each document as it<br />
applies to ITS <strong>Strategic</strong> Implementation Plan was identified. Section 3 discusses the role of the ITS<br />
<strong>Strategic</strong> Implementation Plan in coordinating and integrating with other regional planning initiatives.<br />
E. ITS Inventory<br />
The ITS inventory was collected from stakeholders, including <strong>CDOT</strong> ITS, the City of Loveland, the City<br />
provided Fort Collins, the City of Greeley and local transit agencies. The inventory information provided<br />
the foundation of current conditions. The inventory includes existing ITS devices, key facilities and level<br />
and type of existing coordination between agencies. Section 3 discusses the current conditions.<br />
F. Identification of <strong>Transportation</strong> Problems<br />
Based on review of the planning documents, the ITS inventory review and the stakeholder meetings; the<br />
transportation problems were identified. These critical transportation problems are presented in Section 4.<br />
The priority of problems on the network is also identified in Section 4.<br />
G. Available ITS Solutions<br />
Discussion of potential solutions regarding these problems with the stakeholder groups centered on easy<br />
to understand applications and implementable ITS deployment applications. The information collected<br />
from stakeholder discussions was then translated into the Market Package terminology. Market Packages<br />
provide an accessible, deployment-oriented perspective to the National ITS Architecture. They are<br />
tailored to fit separately or in combination – real world transportation problems and needs.<br />
Table 4 contains a complete list of the Market Packages selected for the study area, including notes on<br />
their specific existing and future applicability to the region.<br />
H. Project Development<br />
The above steps resulted in the identification of ITS Deployments for corridors, transit and regional<br />
projects. Each ITS deployment on the list was then assigned a priority and a time frame for deployment<br />
(short, medium, or long-term). The deployments were presented to the Working Group, who provided<br />
feedback on proposed field device locations and the general description of each project and overall<br />
priority for deployment within the <strong>Region</strong>. The intent of this exercise was to provide perspective to the<br />
intensity of the need for, and feasibility of, each project.<br />
An overall vision for deployment was also developed in order to guide the prioritization process and<br />
systematic implementation of ITS in the <strong>Region</strong>.<br />
13
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
I. Interfaces with DRCOG ITS <strong>Strategic</strong> Plan<br />
The DRCOG ITS <strong>Strategic</strong> Plan overlays certain geographical areas of <strong>CDOT</strong> <strong>Region</strong> 4. The DRCOG<br />
ITS <strong>Strategic</strong> Plan was updated in December 2007. ITS deployments on the DRCOG geographical<br />
network that are common with <strong>Region</strong> 4 will remain unchanged to ensure consistency across the plans.<br />
The stakeholders from the following cities and counties are common to the DRCOG <strong>Region</strong> and <strong>CDOT</strong><br />
<strong>Region</strong> 4:<br />
Boulder County Boulder<br />
Dacono Erie<br />
Firestone Fredrick<br />
Lafayette Longmont<br />
Louisville Lyons<br />
Mead Nederland<br />
Superior<br />
14
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
III.<br />
EXISTING ITS INVENTORY<br />
A. Review of Relevant Documents<br />
This section will be inserted at a later time and stakeholders will have the opportunity to review.<br />
B. Existing ITS Traffic Inventory<br />
The bulk of the equipment within the study areas was deployed by, and is operated and maintained by the<br />
<strong>CDOT</strong> Colorado Traffic Management Center (CTMC) through the <strong>CDOT</strong> ITS Branch. <strong>CDOT</strong> CTMC<br />
monitors and operates 27 DMS, 14 CCTV and 19 Road Weather Information System (RWIS) within the<br />
study area. <strong>CDOT</strong> CTMC will continue as the main operator for similar ITS deployments along the<br />
freeway and state highways. CTMC uses the Colorado Traffic Management System/Colorado Traveler<br />
Information System (ATMS/ATIS) system to allow increased bi-directional information sharing for<br />
traffic, incidents, weather and camera images, as well as providing bi-directional control of local devices.<br />
<strong>CDOT</strong> DTD has 20 ATR’s within the <strong>Region</strong>.<br />
In addition, <strong>CDOT</strong> <strong>Region</strong> 4 operates and maintains a signal system. The <strong>Region</strong> has significant<br />
deployment of the MDSS.<br />
Loveland, Greeley and Fort Collins all operate and maintain separate signal systems. Fort Collins has<br />
incorporated this function into a traffic operations center that serves as the control point for all ITS<br />
elements in the City including CCTV cameras and weather stations. All three cities have some portion of<br />
their signal system on fiber optic communications. Fort Collins monitors and operates 42 CCTV and 7<br />
Road Weather Information System (RWIS), as well as 39 ATRs of both video and in-pavement sensors.<br />
Greeley monitors and operates 2 CCTV and 2 Road Weather Information System (RWIS) within their<br />
city limit plans are underway to add signals under fiber control and install additional weather stations and<br />
CCTV cameras. Loveland monitors and operates 7 CCTV, 4 RWIS and 20 ATR stations. Appendix A<br />
provided a consolidated existing traffic inventory for <strong>CDOT</strong> <strong>Region</strong> 4 and the Urban Stakeholders.<br />
Appendix B shows <strong>CDOT</strong> <strong>Region</strong> 4 existing ITS Deployment by corridor. Figure 4 shows the <strong>CDOT</strong><br />
ITS Inventory within the <strong>Region</strong> (figure not included at this time).<br />
C. Existing Transit ITS Inventory<br />
There are three transit agencies within <strong>Region</strong> 4; Transfort, COLT, and GET. Transfort has an annual<br />
ridership of 2 million riders, with 34 buses on 19 routes. All buses have AVL, and paratransit service is<br />
contracted out. COLT has an annual ridership of 155,000 with 11 buses on 3 routes, and manages their<br />
own paratransit system. GET has an annual ridership of 590,000 over 15 buses on 7 routes, and also<br />
manage their own paratransit system. Each agency has a central facility and uses maintenance scheduling<br />
software. Appendix C shows the Existing inventory for Transit Stakeholders.<br />
D. Existing Inventory for Other Stakeholders<br />
Appendix D shows existing pull-out areas and load deficient structures within the <strong>Region</strong>.<br />
15
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
IV.<br />
TRANSPORTATION PROBLEMS IN STUDY AREA<br />
Through working with the stakeholder groups, a comprehensive list of critical regional transportation<br />
problems were identified. Discussions focused on where the problems exist, the consequences associated<br />
with the problems and a regional ranking of each of the problems. Appendix E shows the transportation<br />
problems that were identified by each stakeholder group except for the technology group. Whose primary<br />
role was to provide advice on the state of technology and challenges ahead. The purpose of identifying<br />
these problems is to assist in the determination of applicable ITS solutions to be considered for inclusion<br />
in the ITS <strong>Strategic</strong> Plan.<br />
A. Identification of <strong>Transportation</strong> Problems<br />
Within the DRCOG <strong>Region</strong>, the concept of <strong>Transportation</strong> Service Areas (TSA) was introduced to<br />
provide a better understanding of ITS from a regional perspective and also assist in the development of<br />
the <strong>Region</strong>al ITS Architecture. In order to promote consistency and coordination across regions, the TSA<br />
concept has also been adopted for the <strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Plan.<br />
Although transportation problems were primarily grouped in to one TSA, some problems may overlap<br />
into others TSAs:<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<strong>Region</strong>al Traveler Information<br />
<strong>Region</strong>al Operations and Management<br />
<strong>Region</strong>al Traffic Incident Management<br />
<strong>Region</strong>al Transit Operations and Management<br />
Maintenance and Construction<br />
<strong>Region</strong>al Parking Management<br />
<strong>Region</strong>al Data Management<br />
<strong>Region</strong>al Emergency Management<br />
Commercial Vehicle Operations<br />
<strong>Region</strong>al Traveler Information<br />
<strong>Region</strong>al traveler information involves a wide range of data including: traffic conditions, travel times,<br />
incidents, construction, weather, transit operations, and alternative travel options. This data is then<br />
repackaged and disseminated to the public. For example, <strong>CDOT</strong>’s traveler information system consists of<br />
the 511 phone system and the CoTrip.org website. Other services to distribute this information (i.e.<br />
personalized e-mail or text messaging, mobile access, third party traveler information) are able to grow<br />
from this consolidated traveler information. The collection and dissemination of traveler information can<br />
assist travelers in making and modifying their travel decisions. This includes information regarding traffic<br />
conditions, incidents, construction, maintenance activities and weather.<br />
The following specific traveler information related transportation problems were identified:<br />
<br />
<br />
Not enough real-time information (traffic conditions, incidents & construction) provided to the<br />
travelers – This problem exists on interstates, state highways and regionally significant corridors.<br />
The inability to provide real-time information can lead to increased delays, traveler anxiety and<br />
negative impacts to regional travel particularly to the out-of-state/area drivers. This also impacts<br />
traffic operators and emergency management providers in their ability to quickly respond to<br />
incidents.<br />
Not enough real-time weather and pavement data – This problem exists on interstates, state<br />
highways and regionally significant corridors. Travelers are not being provided enough granular<br />
16
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
<br />
<br />
<br />
information regarding road and weather conditions. This also impacts maintenance personnel and<br />
emergency management providers and their ability to efficiently and effectively deploy resources<br />
to respond to bad weather conditions.<br />
Not much awareness of where existing real-time information is available- This is a regional<br />
problem. Travelers are generally unaware of information available is and are unable to take<br />
advantage of traveler information displayed on the <strong>CDOT</strong> web site. Also, traveler information is<br />
not being shared across institutional boundaries.<br />
No on-line trip planning services – This is a regional problem. Travelers are not being provided<br />
with one consolidated source for alternative modal options across the region such as; transit,<br />
carpool, vanpool, Park-N-Ride and bicycle. Transit ridership is being impacted as information is<br />
difficult to obtain and there is not a great demand for transit for inter-city travel. There also tends<br />
to increase costs for para transit services as normal bus operations do not meet the user needs.<br />
Not enough video surveillance to monitor traffic conditions, incidents and construction<br />
activities. This problem exists at freeway interchanges and highways that intersect with others,<br />
state highways and regionally significant corridors. Traffic operators are not able to monitor and<br />
verify traffic conditions. The inability to know current conditions also impacts safety.<br />
Additionally, there is decreased usage at Park-N-Rides due to lack of video surveillance and<br />
increased safety concerns.<br />
<strong>Region</strong>al Operations and Management<br />
<strong>Region</strong>al transportation management provides transportation monitoring and control functions<br />
coordinated across regional jurisdictions. For example, <strong>CDOT</strong>, Fort Collins, Greeley and Loveland<br />
operate signal systems to monitor and control signals. System monitoring and control functions provide<br />
operators the ability to respond to changing operational conditions, as needed. The following specific<br />
operations and management related problems were identified:<br />
<br />
<br />
<br />
<br />
<br />
<br />
Freeway/Arterial congestion – This problem exists on specific segments along interstates, state<br />
highways and regionally significant corridors where the traffic volume exceeds the roadway<br />
capacity. It increases delay, driver frustration and overall degradation of operations.<br />
Synchronization of signals and strategies beyond TOD plans – This problem exists on specific<br />
segments along state highways and regionally significant corridors where traffic signals are<br />
closely spaced (usually less than 1/4 mile from each other). Lack of proper synchronization<br />
causes unnecessary delay, increased emissions and increased safety concerns.<br />
Event traffic management – This problem exists in urban areas. Events tend to attract more<br />
traffic and can increase delays and safety concerns.<br />
Lack of communications infrastructure – This is a regional problem. The lack of backbone fiber<br />
infrastructure seriously affects the ability to deploy ITS devices, systems and networks. This<br />
affects the ability to easily share information between agencies for ITS applications and business<br />
functions.<br />
Tracking and data collection from maintenance vehicles – This is a regional problem.<br />
Maintenance vehicles are not being used as effectively as possible to supplement traveler<br />
information and road/weather conditions.<br />
Not enough reliable communication for signals – This problem exists on specific segments<br />
along state highways and regionally significant corridors where there is no reliable<br />
17
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
<br />
communications for traffic signals. This makes it difficult to troubleshoot signal problems<br />
remotely, increases maintenance cost and prevents the ability to synchronize signals.<br />
Security of key infrastructure – This problem exists on specific segments along interstates, state<br />
highways and regionally significant corridors. Security results in deterring vandalism at Park-N-<br />
Rides, on bridges and on ITS infrastructure, such as DMS.<br />
<strong>Region</strong>al Traffic Incident Management<br />
Severe and inclement weather, speeding, incidents and work zone management around construction and<br />
maintenance activities impact safety. The service area applies to two general groups: transportation<br />
operations and public safety. Using ITS devices, transportation operations would employ incident<br />
detection and verification and would disseminate traveler information regarding the incident. Public<br />
safety has primary responsibility for incident site management and incident clearance and would<br />
coordinate with transportation operations to support their activities and to promote safer operations. The<br />
following specific incident related transportation problems were identified:<br />
<br />
<br />
<br />
<br />
<br />
Weather (high winds, flooding and icing) – This problem exists on specific segments along<br />
interstates, state highways and regionally significant corridors. It impacts safety of traveling<br />
public, and it also disrupts traffic conditions.<br />
Improve highway-rail crossings – This problem exists at specific railroad crossings on state<br />
highways and regionally significant corridors. Some crossings lack protection gates, while other<br />
crossings on roadway directly parallel and due to their close proximity to the state highway, result<br />
in insufficient queue space. There is a disruption of traffic and increased localized safety and<br />
congestion concerns. Also, queue dissipation takes longer at these locations.<br />
Incidents – This problem exists on interstates, state highways and regionally significant corridors.<br />
It leads to disruption of traffic and secondary incidents. Also, there is a need to clear incidents to<br />
a safe zone location. Currently, this result in CSP resources inordinately tied up assisting vehicles<br />
clear the roadway.<br />
Road closures – This problem exists on specific segments along interstates, state highways and<br />
regionally significant corridors where the roadway needs to be closed due to bad weather<br />
conditions and/or incidents. It impacts safety and disrupts traffic.<br />
Speeding – The problem exists primarily along interstates during bad weather conditions. It<br />
impacts safety.<br />
<strong>Region</strong>al Transit Operations and Management<br />
Transit management provides monitoring and control functions for transit. The transit services needs to be<br />
integrated with other alternative modes to increase its competitiveness. Transit operations are intended to<br />
improve operational efficiency. For example, CAD/AVL system allows for monitoring of the transit for<br />
schedule adherence, etc. The following specific transit related transportation problems were identified:<br />
<br />
<br />
Not enough coordination and integration between alternative travel modes – This is a regional<br />
problem. Currently, there is no connectivity between and among the travel modes, e.g., transit,<br />
van pools and bicycle routes. Also, none of the existing Park-N-Rides have transit connectivity.<br />
All of this negatively impacts usage of these travel modes.<br />
No priority for transit vehicles at signals – This problem exists along certain transit routes on<br />
state highways and regionally significant corridors where there is traffic congestion. There is<br />
increased delay for buses that may affect schedule adherence.<br />
18
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
<br />
<br />
Not many regional bus routes – This problem exists between major urban areas within the<br />
<strong>Region</strong>. It can impact transit ridership and competitiveness.<br />
Lack of dedication outreach for transit to increase its competitiveness. This is a regional<br />
problem. This results in not enough public demand for transit.<br />
Maintenance and Construction<br />
The primary area in which ITS is related to maintenance and construction is for traveler information<br />
functions. Also, roadway maintenance is tied with weather data collection to support such activities as<br />
snow clearing operations and roadway striping. The following specific maintenance and construction<br />
related transportation problems were identified:<br />
<br />
Work zone – This problem exists on specific segments along interstates, state highways and<br />
regionally significant corridors where construction/maintenance activities are performed. This<br />
impacts the safety of the traveling public and construction/maintenance personnel.<br />
<strong>Region</strong>al Parking Management<br />
The parking management concept supports and provides parking information to the public and operators.<br />
The following specific parking management related transportation problems were identified:<br />
<br />
Parking management – This problem primarily exists in the Town of Estes Park due to its<br />
proximity to Rocky Mountain National Park (RMNP). It can lead to increased congestion, driver<br />
frustration and increased vehicle-pedestrian conflicts.<br />
<strong>Region</strong>al Data Management<br />
<strong>Region</strong>al Data Management involves the organization of transportation system performance data<br />
spanning across modal and jurisdictional boundaries. The data will be used by operators (for operational<br />
analysis and event planning), planners (for long-term planning) and researchers. Traffic operations,<br />
operations planning, and transportation planning rely on accurate and timely data. The data is used in<br />
evaluating system performance, determining priorities, calibrating models, developing and evaluating<br />
scenarios, timing signals, and managing events and incidents. Where data are old or nonexistent, the<br />
results of these activities may be compromised. Specific transportation problems related to data<br />
management are:<br />
<br />
<br />
<br />
Not enough historic traffic count (volume) data – This is a regional problem. Data are not at a<br />
centralized location. Also, there is not enough bike/pedestrian count data.<br />
Data sharing between agencies – This is a regional problem. There is not sharing of data<br />
between agencies in part due to lack of backbone communications infrastructure and data sharing<br />
mechanisms.<br />
Lack of performance monitoring data – This is a regional problem. Operational decisions are<br />
based on insufficient or incomplete information. It affects the ability to show demonstrable<br />
benefits for ITS.<br />
<strong>Region</strong>al Emergency Management<br />
ITS devices and systems may be used to support the protection of critical transportation infrastructure<br />
within the region. Note that ITS devices and systems are also critical transportation infrastructure that<br />
must remain available to support the public safety community in the event of a disaster.<br />
19
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
<br />
Access to MDSS and <strong>CDOT</strong> Traveler Information – The lack of availability of this information<br />
impacts local law enforcement agencies in the allocation of their resources in responding to bad<br />
weather conditions.<br />
Commercial Vehicle Operators<br />
ITS devices and systems may be deployed in this region to support both the Colorado State Patrol (CSP)<br />
and the Colorado Department of Revenue (CDOR) Port-of-Entry (POE) division interactions with<br />
commercial vehicle operations. CSP is responsible for the safety of commercial vehicle operations, which<br />
involves driver credential review, truck inspections, and HAZMAT routing and tracking. CDOR is<br />
responsible for commercial vehicle tax administration, assuring compliance with the State’s commercial<br />
vehicle size and weight laws. <strong>CDOT</strong> is responsible for issuing Extra-Legal and Longer Combination<br />
Vehicle permits and administering those programs. Coordination is ongoing among the primary agencies<br />
to improve and integrate the commercial vehicle operations.<br />
<br />
<br />
<br />
Access to MDSS and <strong>CDOT</strong> Traveler Information – The lack of availability of this information<br />
impacts the POE’s in their ability in providing timely information to commercial vehicles that<br />
pass through the facilities.<br />
Antiquated Business <strong>Systems</strong> – This problem specifically pertains to POE’s antiquated business<br />
system with silo databases that make it difficult to perform required functions effectively,<br />
efficiently and in a timely manner.<br />
Inadequate support infrastructure – This problem exists on interstates and state highways where<br />
there is not enough pullout areas to perform size and weight enforcement on commercial vehicles.<br />
There is also a lack of proper size and weight enforcement on load deficient bridges in the region.<br />
In addition to the above identified problems, there were additional problems identified that were more<br />
institutional in nature and are not tied to the TSAs. These problems pertain to coordination within and<br />
between local cities, counties, and law enforcement agencies, regional and state agencies. Specific<br />
transportation problems related to institutional are:<br />
<br />
<br />
Champion for ITS within the <strong>Region</strong> – This is a regional problem. The lack of formally<br />
identifying a champion for ITS within the <strong>Region</strong> results in individual agencies trying their best<br />
to promote ITS within their agency without a truly collaborative concerted approach.<br />
Lack of adequate funding – This problem affects all of stakeholders within the <strong>Region</strong>. This<br />
affects their ability to implement solutions, improve mobility and safety within the region and<br />
upgrade systems, facilities or roadways, etc.<br />
B. <strong>Transportation</strong> Service Areas<br />
Table 1 illustrates how the regional transportation problems align to the <strong>Transportation</strong> Service Areas.<br />
20
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
Table 1:<br />
<strong>Region</strong>al Problems Aligned to Applicable <strong>Transportation</strong> Service Areas<br />
<strong>Transportation</strong> Service Areas<br />
<strong>Region</strong>al <strong>Transportation</strong> Problems<br />
<strong>Region</strong>al Traveler Information<br />
<strong>Region</strong>al <strong>Transportation</strong><br />
<strong>Region</strong>al Traffic Incident<br />
Transit Operations and<br />
Maintenance and Construction<br />
<strong>Region</strong>al Parking Management<br />
<strong>Region</strong>al Data Management<br />
Emergency Management<br />
Commercial Vehicle Operations<br />
1 Not enough real-time information (traffic conditions,<br />
incidents & construction) provided to the travelers<br />
X X X X X X<br />
2 Not enough real-time weather and pavement data X X X X X X X<br />
3 Not much awareness of where existing real-time<br />
information is available<br />
4 No on-line trip planning services X<br />
5 Not enough video surveillance to monitor traffic<br />
conditions, incidents and construction activities.<br />
6 Freeway/Arterial congestion X X<br />
7 Synchronization of signals and strategies beyond<br />
TOD plans<br />
X X X X X X X X<br />
X X X X X<br />
8 Event traffic management X X X<br />
9 Lack of communications infrastructure X X X X X X<br />
10 Tracking and data collection from maintenance<br />
vehicles<br />
11 Not enough reliable communication for signals X<br />
12 Security of key infrastructure X<br />
13 Weather (high winds, flooding and icing) X X X X X<br />
14 Improve highway-rail crossing X<br />
15 Incidents X X X X X<br />
16 Management of road closures X X X X X<br />
17 Speeding X X<br />
18 Not enough coordination and integration between<br />
other travel modes<br />
X<br />
X<br />
X<br />
X<br />
21
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
<strong>Transportation</strong> Service Areas<br />
<strong>Region</strong>al <strong>Transportation</strong> Problems<br />
<strong>Region</strong>al Traveler Information<br />
<strong>Region</strong>al <strong>Transportation</strong><br />
<strong>Region</strong>al Traffic Incident<br />
Transit Operations and<br />
Maintenance and Construction<br />
<strong>Region</strong>al Parking Management<br />
<strong>Region</strong>al Data Management<br />
Emergency Management<br />
Commercial Vehicle Operations<br />
19 No priority for transit vehicles at signals X X<br />
20 Not many regional bus routes X<br />
21 Lack of dedication outreach for transit to increase its<br />
competitiveness<br />
22 Work zone management X X X<br />
23 Parking management X X X<br />
24 Not enough historic traffic count (volume) data X<br />
25 Data sharing between agencies X X X X X<br />
26 Lack of performance monitoring data X<br />
27 Access to MDSS and <strong>CDOT</strong> Traveler Information X X X<br />
28 Antiquated Business <strong>Systems</strong> X<br />
29 Inadequate support infrastructure X<br />
30 Champion for ITS within the <strong>Region</strong> X X X X X X X X X<br />
31 Lack of adequate funding X X X X X X X X X<br />
X<br />
C. <strong>Region</strong>al Ranking of <strong>Transportation</strong> Problems<br />
In working with the stakeholders the regional ranking of each of the problems were identified. The focus<br />
of the effort was to determine which problems were higher priorities from a regional perspective, not just<br />
within an agency. During discussions with some stakeholder groups, a numerical ranking of the problems<br />
was proposed. Other stakeholder groups preferred regional ranking that reflected high, medium and low<br />
priority. Generally, there was a greater degree of consensus between the stakeholders that the regional<br />
ranking should be reflected as high, medium and low priority instead of numerical ranking. Stakeholders<br />
believed this also avoided pitting problems against each other for higher ranking. Table 2 provides the<br />
<strong>Region</strong>al Ranking for each of the problems identified. It should be noted that some of the problems are<br />
not directly related to ITS and go beyond the scope of the project. However, they are included in this table<br />
22
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
to document their existence and acknowledge their importance and relationship to transportation service<br />
applications identified in the plan.<br />
Table 2:<br />
<strong>Region</strong>al Ranking of <strong>Transportation</strong> Problems<br />
Problem<br />
<strong>Region</strong>al <strong>Transportation</strong> Problems<br />
#<br />
1 Not enough real-time information (traffic conditions, incidents & construction)<br />
provided to the travelers<br />
<strong>Region</strong>al<br />
Ranking<br />
High Priority<br />
2 Not enough real-time weather and pavement data High Priority<br />
3 Not much awareness of where existing real-time information is available High Priority<br />
4 No on-line trip planning services High Priority<br />
5 Not enough video surveillance to monitor traffic conditions, incidents and<br />
construction activities.<br />
High Priority<br />
6 Freeway/Arterial congestion High Priority<br />
7 Synchronization of signals and strategies beyond TOD plans Low Priority<br />
8 Event traffic management Low Priority<br />
9 Lack of communications infrastructure High Priority<br />
10 Tracking and data collection from maintenance vehicles Low Priority<br />
11 Not enough reliable communication for signals Medium Priority<br />
12 Security of key infrastructure Low Priority<br />
13 Weather (high winds, flooding and icing) Medium Priority<br />
14 Improve highway-rail crossing Medium Priority<br />
15 Incidents High Priority<br />
16 Management of road closures Medium Priority<br />
17 Speeding Low Priority<br />
18 Not enough coordination and integration between other travel modes High Priority<br />
19 No priority for transit vehicles at signals Low Priority<br />
20 Not many regional bus routes Low Priority<br />
21 Lack of dedication outreach for transit to increase its competitiveness High Priority<br />
22 Work zone management Medium Priority<br />
23 Parking management High Priority<br />
24 Not enough historic traffic count (volume) data Low Priority<br />
25 Data sharing between agencies Low Priority<br />
26 Lack of performance monitoring data High Priority<br />
27 Access to MDSS and <strong>CDOT</strong> Traveler Information High Priority<br />
23
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
Problem<br />
#<br />
<strong>Region</strong>al <strong>Transportation</strong> Problems<br />
<strong>Region</strong>al<br />
Ranking<br />
28 Antiquated Business <strong>Systems</strong> 1 High Priority<br />
29 Inadequate support infrastructure 1 High Priority<br />
30 Champion for ITS within the <strong>Region</strong> High Priority<br />
31 Lack of adequate funding High Priority<br />
1<br />
The problem is not directly addressed by ITS transportation technology<br />
D. Linking Problems to the Network<br />
Working with <strong>CDOT</strong> and Urban Stakeholders, the transportation problems were linked to the<br />
geographical state highway network in <strong>CDOT</strong> <strong>Region</strong> 4. Obviously, certain transportation problems<br />
cannot link to the physical network and are not included in the analysis. Appendix F shows the priority of<br />
the problems on the geographical network of <strong>CDOT</strong> <strong>Region</strong> 4. The corridors include interstates, state<br />
highways and regionally significant corridors.<br />
24
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
V. ITS SOLUTIONS TO TRANSPORATION PROBLEMS<br />
In Section IV, transportation problems affecting the <strong>Region</strong> were identified. Discussion of potential<br />
solutions regarding these problems with the stakeholder groups centered on easy to understand<br />
applications and implementable ITS deployment applications. The information collected from stakeholder<br />
discussions was then translated into the market package terminology. Market Packages provide an<br />
accessible, deployment-oriented perspective to the National ITS Architecture. They are tailored to fit -<br />
separately or in combination - real world transportation problems and needs. Market Packages combine<br />
various ITS equipment that must work together to deliver a given transportation service, as well as the<br />
information that must flow between these elements and other important systems. In other words, they<br />
identify physical ITS elements that are required to implement a particular transportation service. They are<br />
independent of technology and do not recommend specific products. The following is a brief summary of<br />
discussion items:<br />
<br />
<br />
<br />
<br />
A – Discussion items available solutions to each of the transportation problem and the associated<br />
Market Packages.<br />
B – Market Package analysis including existing and future applications within the <strong>Region</strong>.<br />
C – Links between transportation problems and Market Packages.<br />
D – Links transportation problems and TSAs.<br />
A. Available ITS Solutions to <strong>Transportation</strong> Problems<br />
A wide range of ITS equipment and applications are available to implement solutions to specific<br />
problems. These solutions differ in cost, technology, extent of deployment required, etc. Table 3<br />
identifies potential ITS solutions based on existing and successful deployments within Colorado for<br />
similar transportation problems. Market Packages associated with the solutions and transportation<br />
problems are also identified.<br />
25
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
Table 3:<br />
Available ITS Solutions to <strong>Transportation</strong> Problems<br />
# Problem Solutions Market Packages<br />
1 Not enough realtime<br />
information<br />
(traffic conditions,<br />
incidents &<br />
construction)<br />
provided to the<br />
travelers<br />
2 Not enough realtime<br />
weather and<br />
pavement data<br />
Point devices (Radar, Solo, etc)<br />
P2P devices (Toll Tag indicators)<br />
CCTV<br />
HAR (non-<strong>CDOT</strong> use)<br />
Interface to CSP Dispatch and other law enforcement<br />
dispatch(s)<br />
CTMS Lite to CSP<br />
Courtesy Patrol<br />
COTrip website and any local agency websites<br />
GOV delivery<br />
511<br />
Weather stations<br />
Pavement sensors<br />
Expand MDSS System including AVL in-Vehicle<br />
reporting/Camera<br />
CCTV<br />
ATIS01-Broadcast Traveler Information<br />
ATIS02-Interactive Traveler Information<br />
ATMS01-Network Surveillance<br />
ATMS02- Probe Surveillance<br />
ATMS06-Traffic Information Dissemination<br />
ATMS08- Incident Management System<br />
MC08-Work Zone Management<br />
MC10-Maintenance and Construction Activity<br />
Coordination.<br />
ATIS01-Broadcast Traveler Information<br />
ATIS02-Interactive Traveler Information<br />
ATMS06-Traffic Information Dissemination<br />
MC03-Road Weather Data Collection<br />
MC04-Weather Information Processing and Distribution<br />
3 Not much<br />
awareness of<br />
where existing<br />
real-time<br />
information is<br />
available<br />
4 No on-line trip<br />
planning services<br />
5 Not enough video<br />
surveillance to<br />
monitor traffic<br />
conditions,<br />
incidents and<br />
construction<br />
Promoted COTrip website, 511 and GOV Delivers using<br />
existing dissemination devices (DMS, HAR)<br />
Static signs with COTrip and 511 information<br />
Rebranding smartrips.org to provide multi-modal options<br />
including transit, carpool, vanpool, PNR and bicycle<br />
CCTV<br />
ATIS01-Broadcast Traveler Information<br />
ATIS02-Interactive Traveler Information<br />
APTS07-Mulit-modal Coordination<br />
APTS09-Transit Traveler Information<br />
ATIS02-Interactive Traveler Information<br />
ATIS02-Interactive Traveler Information<br />
ATMS01-Network Surveillance<br />
ATMS08- Incident Management System<br />
MC03-Road Weather Data Collection<br />
MC08-Work zone Management<br />
26
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
# Problem Solutions Market Packages<br />
activities.<br />
6 Freeway/Arterial<br />
congestion<br />
7 Synchronization<br />
signals and<br />
strategies beyond<br />
TOD plans<br />
8 Event traffic<br />
management<br />
9 Lack of<br />
communications<br />
infrastructure<br />
10 Tracking and data<br />
collection from<br />
maintenance<br />
vehicles<br />
11 Not enough<br />
reliable<br />
communication<br />
for signals<br />
12 Security of key<br />
infrastructure<br />
13 Weather (high<br />
winds, flooding and<br />
icing)<br />
14 Improve highwayrail<br />
crossing<br />
Ramp meters (freeways)<br />
CCTV<br />
Signals under system control<br />
Traffic responsive<br />
Traffic adaptive<br />
Event timing plans<br />
CCTV<br />
DMS<br />
Affects all ITS deployment<br />
AVL<br />
Data Collection device<br />
Fiber interconnectivity<br />
CCTV at bridge or VMS structures affected by vandalism<br />
and at PNR’s<br />
Sensors and DMS (high winds and flooding)<br />
Automated anti-icing system with sensors and DMS<br />
Signals tied with railroad crossing to allow for quick queue<br />
clearance and advance warning<br />
ATIS01-Broadcast Traveler Information<br />
ATIS02-Interactive Traveler Information<br />
ATMS01-Network surveillance<br />
ATMS03-Surface Street Control<br />
ATMS04-Freeway Control<br />
ATMS03-Surface Street Control<br />
ATIS01-Broadcast Traveler Information<br />
ATIS02-Interactive Traveler Information<br />
ATMS01- Network Surveillance<br />
ATMS03-Surface Street Control<br />
ATMS08- Incident Management System<br />
All relevant market packages<br />
ATMS02- Probe Surveillance<br />
MC01-Maintenance and Construction Vehicle and<br />
Equipment Tracking<br />
MC03-Road Weather Data Collection.<br />
ATMS03-Surface Street Control<br />
EM05-<strong>Transportation</strong> Infrastructure Protection<br />
MC03-Road Weather Data Collection<br />
MC04-Weather Information Processing and Distribution<br />
MC05-Roadway Automated Treatment<br />
ATMS03-Surface Street Control<br />
ATMS13-Standard Railroad Grade Crossing; ATMS03-<br />
27
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
# Problem Solutions Market Packages<br />
15 Incident Interfaces to CSP and other law enforcement dispatches<br />
Courtesy patrol<br />
Update existing IMP from US-36 and I-25 and develop<br />
new IMP’s<br />
CCTV<br />
Incident detection algorithms using CTMS on freeways<br />
Surface Street Control<br />
ATIS01-Broadcast Traveler Information<br />
ATIS02-Interactive Traveler Information<br />
ATMS01-Network Surveillance<br />
ATMS08- Incident Management System<br />
EM04-Roadway Service Patrols<br />
16 Road closures Remote controlled gates or barriers with CCTV and DMS ATIS01-Broadcast Traveler Information<br />
ATIS02-Interactive Traveler Information<br />
ATMS21-Roadway Closure Management<br />
17 Speeding Advise lower speeds using VMS<br />
Speed radar and display equipment<br />
18 Not enough Integration through on-line trip planning services<br />
coordination and<br />
integration<br />
between other<br />
travel modes<br />
19 No priority for<br />
transit vehicles at<br />
signals<br />
20 Not many regional<br />
bus routes<br />
21 Lack of dedication<br />
outreach for transit<br />
to increase its<br />
competitiveness<br />
22 Work zone<br />
management<br />
23 Parking<br />
Management<br />
Green extension, red truncation, etc at all signals to allow<br />
quicker clearance of transit vehicles<br />
Increase transit competitiveness<br />
Integration of multi-modal options<br />
CCTV<br />
DMS<br />
HAR<br />
Parking lot conditions<br />
Promote multi-modal options<br />
ATMS19-Speed Monitoring<br />
APTS07-Multi-modal Coordination<br />
ATIS02-Interactive Traveler Information<br />
APTS09-Transit Signal Priority<br />
ATMS03-Surface Street Control<br />
APTS07-Multi-modal Coordination<br />
APTS07 - Multi-modal Coordination<br />
APTS08-Transit Traveler Information<br />
ATIS02-Interactive Traveler Information<br />
ATMS05-HOV Lane Management<br />
ATIS01-Broadcast Traveler Information<br />
ATIS02-Interactive Traveler Information<br />
MC08-Work Zone Management<br />
MC09-Work Zone Safety Monitoring<br />
MC10-Maintenance and Construction Activity<br />
Coordination<br />
ATIS01-Broadcast Traveler Information<br />
ATIS02-Interactive Traveler Information<br />
28
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
# Problem Solutions Market Packages<br />
24 Not enough<br />
historic traffic<br />
count (volume)<br />
data<br />
25 Data sharing<br />
between agencies<br />
26 Lack of<br />
performance<br />
monitoring data<br />
27 Access to MDSS<br />
and <strong>CDOT</strong><br />
Traveler<br />
Information<br />
28 Antiquated<br />
Business <strong>Systems</strong><br />
29 Inadequate<br />
support<br />
infrastructure<br />
30 Champion for ITS<br />
within the <strong>Region</strong><br />
31 Lack of adequate<br />
funding<br />
CCTV<br />
DMS<br />
Kiosks<br />
One consolidated source<br />
Expansion of CCTM application<br />
Reporting tools tied to databases<br />
Kiosks<br />
Access to CTMS lite<br />
Upgrade business systems<br />
Construct more pullouts<br />
Identify lead agency<br />
Public-Public and Public-Private partnerships<br />
ATMS01-Network Surveillance<br />
ATMS03-Surface Street Control<br />
ATMS16-Parking Facility Management<br />
ATMS17-<strong>Region</strong>al Parking Management<br />
AD1-ITS Data Mart<br />
AD2-ITS Data Warehouse<br />
AD3-ITS Virtual Data Warehouse<br />
AD1-ITS Data Mart<br />
AD2-ITS Data Warehouse<br />
AD3-ITS Virtual Data Warehouse<br />
ATIS02-Interactive Traveler Information<br />
APTS07-Mulit-modal Coordination<br />
AD3-ITS Virtual Data Warehouse<br />
ATIS02-Interactive Traveler Information<br />
CVO04-CV Administrative Process<br />
CVO07-Roadside CVO Safety<br />
CVO04-CV Administrative Process<br />
CVO07-Roadside CVO Safety<br />
Not applicable<br />
Not applicable<br />
29
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
B. Market Packages Analysis for the <strong>Region</strong><br />
Currently, there are 91 Market Packages included in the National ITS Architecture Version 6.1. Market<br />
Packages are categorized into nine subsystems based upon the type of transportation service provided:<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
Archived Data Management (AD): Store and retrieve transportation system information for future<br />
analysis.<br />
Advanced Public <strong>Transportation</strong> <strong>Systems</strong> (APTS): Manage transit operations and make transit use<br />
more convenient and safe.<br />
Advanced Traveler Information <strong>Systems</strong> (ATIS): Provide real-time information to travelers.<br />
Advanced Traffic Management <strong>Systems</strong> (ATMS): Manage operation of the roadway network.<br />
Advanced Vehicle Safety <strong>Systems</strong> (AVSS): Adds capability for improved safety to vehicles. These<br />
market packages are generally applicable to private-sector industry initiatives only.<br />
Commercial Vehicle Operations (CVO): Provides for the electronic monitoring of commercial<br />
vehicle safety assurance and regulation, and exchange of related information.<br />
Emergency Management (EM): Manage emergency response operations.<br />
Maintenance and Construction Management (MC): Manage maintenance and construction<br />
activities and operations.<br />
Table 4, Market Package Analysis, shows at Market Packages except got Market Packages associated<br />
with AVSS. The table provides a brief description and identifies existing and future <strong>Region</strong> 4<br />
applicability.<br />
30
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
Table 4:<br />
Applicable Market Packages within the <strong>Region</strong><br />
Market Brief Description <strong>Region</strong> 4 Application – Existing <strong>Region</strong> 4 Application – Future<br />
Package Name<br />
Archived Data (AD)<br />
AD1 ITS Data Mart Collect data for future<br />
analysis for one agency<br />
only<br />
CTMS collects travel time, speed,<br />
device logs, etc. Existing weather<br />
forecast and pavement condition<br />
As more real-time conditions data is collected and<br />
stored, performance measures reporting at an<br />
individual agency level would be enabled<br />
information in <strong>CDOT</strong> MDSS.<br />
Existing traffic count data at<br />
cities, counties and <strong>CDOT</strong> DTD.<br />
Transit ridership, vanpool/carpool<br />
usage, PNR usage at various<br />
agencies<br />
AD2 ITS Data Store data for multiple Does not exist<br />
All historical traffic counts available at <strong>CDOT</strong> DTD<br />
AD3<br />
Warehouse<br />
ITS Virtual Data<br />
Warehouse<br />
agencies<br />
Supports networked access<br />
to data archives for<br />
multiple agencies<br />
Advanced Public Transit <strong>Systems</strong> (APTS)<br />
APTS 01 Transit Vehicle<br />
Tracking<br />
Provide automatic vehicle<br />
location (AVL) to track<br />
APTS 02<br />
APTS 03<br />
Transit Fixed-<br />
Route<br />
Operations<br />
Demand<br />
Response<br />
Transit<br />
Operations<br />
transit vehicles<br />
Performs automatic driver<br />
assignment and<br />
monitoring, as well as<br />
vehicle routing and<br />
scheduling for fixed-route<br />
services<br />
Performs automatic driver<br />
assignment and<br />
monitoring as well as<br />
vehicle routing and<br />
scheduling for demand<br />
Does not exist<br />
Transfort and COLT have AVL.<br />
Planned AVL in Greeley<br />
Computer Aided Dispatch (CAD)<br />
and two-way communications<br />
exist<br />
Computer Aided Dispatch (CAD)<br />
and AVL exist; scheduling<br />
systems exist<br />
Historical performance “traffic conditions” data<br />
made available on CTMS on corridors that support<br />
“real-time” conditions through an on-line reporting<br />
tool<br />
None<br />
None<br />
None<br />
31
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
Market<br />
Package Name<br />
Brief Description <strong>Region</strong> 4 Application – Existing <strong>Region</strong> 4 Application – Future<br />
response transit services<br />
APTS 04<br />
Transit<br />
Passenger and<br />
Fare<br />
Management<br />
Allows for the<br />
management of passenger<br />
loading and fare payments<br />
on-board vehicles using<br />
electronic means<br />
APTS 05 Transit Security Provides for the physical<br />
security of transit<br />
passengers<br />
APTS 06<br />
APTS 07<br />
APTS 08<br />
APTS 09<br />
APTS 10<br />
Transit<br />
Maintenance<br />
Multi-modal<br />
Coordination<br />
Transit Traveler<br />
Information<br />
Transit Signal<br />
Priority<br />
Transit<br />
Passenger<br />
Counting<br />
Supports automatic<br />
maintenance scheduling<br />
and monitoring.<br />
Establishes two-way<br />
communications between<br />
multiple transit and traffic<br />
agencies and transit signal<br />
priority<br />
Provides customized or<br />
real-time transit<br />
Information<br />
Automated fare collection exists<br />
for Transfort and COLT.<br />
Magnetic strip exists for Transfort<br />
and allows use of smartcard for<br />
CSU students. Magnetic strip and<br />
smartcard planned for COLT<br />
Two-way communications and<br />
panic buttons exist; video<br />
monitoring in buses and transit<br />
center for Transfort; GET planning<br />
to install cameras on buses soon<br />
Maintenance systems exist.<br />
Transfort upgrading existing<br />
system<br />
Coordination between transit and<br />
traffic agencies exists regarding<br />
implementation of new routes and<br />
new stops. Fare collection<br />
coordination between COLT and<br />
Transfort. <strong>Region</strong>al route<br />
coordination on FLEX between<br />
Transfort, COLT and RTD<br />
Check with Estes Park on flow,<br />
they provide information. Static<br />
transit routes and schedules exist<br />
locally<br />
TSP exist at one location.<br />
Exists for COLT<br />
Possibly automated fare collection for GET<br />
None<br />
None<br />
Transit, vanpool/carpool, bicycle and PNR working<br />
together to promote multi-modal options. More<br />
coordination required if other regional bus routes<br />
are implemented<br />
Need for consolidated on-line trip planning services<br />
None<br />
Possibly for GET & Transfort<br />
32
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
Market Brief Description <strong>Region</strong> 4 Application – Existing <strong>Region</strong> 4 Application – Future<br />
Package Name<br />
Advanced Traveler Information <strong>Systems</strong> (ATIS)<br />
ATIS01 Broadcast<br />
Traveler<br />
Information<br />
ATIS02<br />
ATIS03<br />
ATIS04<br />
ATIS05<br />
Interactive<br />
Traveler<br />
Information<br />
Autonomous<br />
Route Guidance<br />
Dynamic Route<br />
Guidance<br />
ISP<br />
(Information<br />
Service<br />
Provider) Based<br />
Route Guidance<br />
Dissemination of<br />
information over a wide<br />
area through existing<br />
infrastructures and low<br />
cost user equipment<br />
Provides tailored<br />
information in response to<br />
a traveler request. Includes<br />
dynamic web pages and<br />
511 telephone information.<br />
In-vehicle or handheld<br />
electronic devices used to<br />
provide trip planning<br />
information and directions.<br />
Builds on Autonomous<br />
Route Guidance to factor<br />
in real-time conditions<br />
information. Again, this<br />
market package is<br />
generally more of a<br />
private-sector initiative.<br />
Trip planning and<br />
directions information that<br />
is provided by a service,<br />
and does not require a<br />
specific user device –<br />
Existing radio station (KEZ 1410)<br />
broadcasts weather and travel<br />
information in Estes Park.<br />
Existing <strong>CDOT</strong> faxes of road<br />
condition information. Existing<br />
Loveland HAR on 1610 AM,<br />
posts traffic information online<br />
and sends out weekly emails.<br />
Existing DMS provide<br />
information. <strong>CDOT</strong>’s Gov<br />
delivery system exists for email<br />
and text alerts<br />
<strong>CDOT</strong> COTrip web site, GOV<br />
delivery and 511 system exists<br />
This service is generally not<br />
provided by public sector<br />
agencies<br />
This service is generally not<br />
provided by public sector<br />
agencies<br />
This service is generally not<br />
provided by public sector<br />
agencies<br />
Possibly use agency website to show traffic<br />
conditions within the city. Provide traffic video<br />
images on city channel<br />
Possibly Estes Park city traveler information web site<br />
and kiosks. Kiosks at POE<br />
<strong>CDOT</strong> data available for use by private ISP’s<br />
<strong>CDOT</strong> data available for use by private ISP’s<br />
<strong>CDOT</strong> data available for use by private ISP’s<br />
33
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
ATIS06<br />
ATIS07<br />
ATIS08<br />
ATIS09<br />
ATIS10<br />
Market<br />
Package Name<br />
Integrated<br />
<strong>Transportation</strong><br />
Management/<br />
Route Guidance<br />
Yellow Pages<br />
and Reservation<br />
Dynamic<br />
Ridesharing<br />
In Vehicle<br />
Signing<br />
VII Traveler<br />
Information<br />
Brief Description <strong>Region</strong> 4 Application – Existing <strong>Region</strong> 4 Application – Future<br />
“Mapquest” web site<br />
would be an example.<br />
Ties in with route<br />
guidance systems to<br />
optimize traffic control<br />
strategies along<br />
anticipated vehicle routes.<br />
Provides “Yellow pages”<br />
business listings and the<br />
capacity to make<br />
reservations.<br />
Provides dynamic<br />
ridesharing/ride matching<br />
capability in real time.<br />
Some large companies<br />
provide this service.<br />
Supports distribution of<br />
information, such as travel<br />
advisories, to drivers<br />
through in-vehicle devices<br />
Distributes real-time<br />
information to vehicles via<br />
Vehicle Infrastructure<br />
Integration (VII)<br />
Advanced Traffic Management <strong>Systems</strong> (ATMS)<br />
ATMS01<br />
ATMS02<br />
Network<br />
Surveillance<br />
Probe<br />
Surveillance<br />
Collects information from<br />
field devices (detectors,<br />
CCTV, etc.) for<br />
monitoring of roadway<br />
conditions.<br />
Use toll transponder<br />
equipped vehicles,<br />
volunteers, buses,<br />
Does not exist<br />
This service is generally not<br />
provided by public sector<br />
agencies<br />
Static vanpool/carpool matching<br />
exists<br />
This service is generally not<br />
provided by public sector<br />
agencies<br />
This service is generally not<br />
provided by public sector<br />
agencies<br />
Cameras exist in Fort Collins,<br />
Greeley and Loveland, and at<br />
<strong>CDOT</strong> Park-n-Rides<br />
None available<br />
None<br />
Not applicable<br />
None<br />
<strong>CDOT</strong> data available for use by private ISP’s<br />
Not applicable<br />
More deployment needed to support real-time<br />
information<br />
Use of transponders anticipated Fort Collins South<br />
and Greeley South. Van and maintenance vehicles<br />
are an additional option<br />
34
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
ATMS03<br />
Market<br />
Package Name<br />
Surface Street<br />
Control<br />
Brief Description <strong>Region</strong> 4 Application – Existing <strong>Region</strong> 4 Application – Future<br />
anonymous cellular phone<br />
tracking or other<br />
technology to monitor<br />
traffic conditions<br />
Provide traffic signal<br />
control.<br />
ATMS04 Freeway Control Control of devices<br />
installed along freeways,<br />
including control of<br />
cameras and dynamic<br />
message signs.<br />
ATMS05<br />
ATMS06<br />
ATMS07<br />
ATMS08<br />
HOV Lane<br />
Management<br />
Traffic<br />
Information<br />
Dissemination<br />
<strong>Region</strong>al Traffic<br />
Control<br />
Incident<br />
Management<br />
System<br />
Manages HOV lanes by<br />
coordinating freeway ramp<br />
meters and connector<br />
signals with HOV lane<br />
usage signals<br />
Supports Dynamic<br />
Message Signs and<br />
Highway Advisory Radio<br />
Provides for the sharing of<br />
traffic information and<br />
control among traffic<br />
management centers to<br />
support a regional control<br />
strategy.<br />
Detects incidents and<br />
provides links between<br />
transportation and<br />
emergency management<br />
centers to exchange<br />
information<br />
TOD synchronization exists.<br />
Most urban area signals under<br />
system control. Traffic adaptive<br />
planned for 10 th Street in Greeley<br />
Traffic responsive control as needed, Upgrading to<br />
fiber communication as needed<br />
Ramp meters exist on US-36 Additional ramp meter deployment on I-25<br />
None<br />
HARS and DMS exist<br />
None<br />
Existing I-25 incident<br />
management plan<br />
Future HOV on I-25 at south end of study area<br />
More deployment needed<br />
Dependent on Fiber Connectivity<br />
Need US-85 IMP. Need for incident management<br />
and event planning at Larimer County Event Center<br />
and for Greeley Stampede. Congestion and routing<br />
an issue for special events in Fort Collins<br />
35
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
ATMS09<br />
ATMS10<br />
Market<br />
Package Name<br />
Traffic Forecast<br />
and Demand<br />
Management<br />
Electronic Toll<br />
Collection<br />
ATMS11 Emissions<br />
Monitoring and<br />
Management<br />
ATMS12<br />
ATMS13<br />
ATMS14<br />
ATMS15<br />
ATMS16<br />
Roadside<br />
weighting<br />
system control.<br />
Standard<br />
Railroad Grade<br />
Crossing<br />
Advanced<br />
Railroad Grade<br />
Crossing<br />
Railroad<br />
Operations<br />
Coordination<br />
Parking Facility<br />
Management<br />
Brief Description <strong>Region</strong> 4 Application – Existing <strong>Region</strong> 4 Application – Future<br />
Use of historical traffic<br />
data to predict future<br />
demand<br />
Use of electronic “tags” to<br />
collect tolls and process<br />
violations without<br />
requiring motorists to stop<br />
Monitors individual<br />
vehicle emissions and<br />
provides general air<br />
quality monitoring using<br />
distributed sensors to<br />
collect the data<br />
Manage lighting system<br />
along roadside<br />
Manages highway traffic<br />
at highway-rail<br />
intersections where rail<br />
operational speeds are less<br />
than 80 miles per hour<br />
Same as Standard, but for<br />
intersections with trains<br />
traveling in excess of 80<br />
miles per hour.<br />
Provides an information<br />
link between rail<br />
operations and traffic<br />
management centers and<br />
emergency dispatch.<br />
Provides monitoring and<br />
management of parking<br />
facilities<br />
None<br />
None<br />
Existing emissions check stations<br />
Not applicable<br />
Existing rail signal pre-emption in<br />
Fort Collins<br />
Not applicable<br />
None<br />
Parking exists at transit hub<br />
(visitor center) and Stanley<br />
satellite hub. More satellite hubs<br />
planned<br />
None<br />
None<br />
None<br />
Not applicable<br />
Possibly query clearance system<br />
Not applicable<br />
None<br />
Need for parking lot monitoring in downtown Estes<br />
Park and at Rocky Mountain State Park<br />
36
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
ATMS17<br />
ATMS18<br />
ATMS19<br />
ATMS20<br />
ATMS21<br />
Market<br />
Package Name<br />
<strong>Region</strong>al<br />
Parking<br />
Management<br />
Reversible Lane<br />
Management<br />
Speed<br />
Monitoring<br />
Drawbridge<br />
Management<br />
Roadway<br />
Closure<br />
Management<br />
Commercial Vehicle Operations<br />
CVO01<br />
CVO02<br />
CVO03<br />
Fleet<br />
Administration<br />
Freight<br />
Administration<br />
Electronic<br />
Clearance<br />
Brief Description <strong>Region</strong> 4 Application – Existing <strong>Region</strong> 4 Application – Future<br />
Supports coordination<br />
between parking facilities<br />
to enable regional parking<br />
management strategies<br />
Provides for the control of<br />
reversible lane facilities<br />
Monitors speeds of<br />
vehicles on roadways.<br />
DMS can then be used to<br />
post a safe speed reminder<br />
Drawbridge control<br />
systems – gates, warning<br />
lights, DMS, etc.<br />
Support for remotely<br />
controlled gates or barriers<br />
that close off roads in<br />
unsafe conditions, plus<br />
camera surveillance and<br />
traveler information<br />
Electronic routing of<br />
commercial vehicle fleets<br />
Electronic tracking of cargo<br />
movements from source to<br />
destination, including<br />
whether the shipment has<br />
been tampered with<br />
Provides for pre-registered<br />
commercial vehicles to pass<br />
through check stations<br />
without pulling over<br />
None<br />
Not applicable<br />
None<br />
Not applicable<br />
None<br />
Not applicable.<br />
Not applicable<br />
PrePass and Automatic Vehicle<br />
Identification equipment exists<br />
Possible future coordination in Estes Park between<br />
town, RMNP and <strong>CDOT</strong><br />
Not applicable<br />
Specific locations<br />
Not applicable.<br />
Specific locations<br />
Not applicable<br />
Not applicable<br />
None<br />
37
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
CVO04<br />
CVO05<br />
CVO06<br />
CVO07<br />
CVO08<br />
CVO09<br />
CVO10<br />
Market<br />
Package Name<br />
CV<br />
Administrative<br />
Processes<br />
International<br />
Border<br />
Electronic<br />
Clearance<br />
Weigh-In-<br />
Motion<br />
Roadside CVO<br />
Safety<br />
On-board CVO<br />
Safety<br />
CVO Fleet<br />
Maintenance<br />
HAZMAT<br />
Management<br />
Brief Description <strong>Region</strong> 4 Application – Existing <strong>Region</strong> 4 Application – Future<br />
Provides for electronic<br />
information sharing and<br />
automation of a number of<br />
commercial vehicle<br />
administration tasks, such<br />
as fee collection,<br />
credentialing, and tax filing<br />
Expands the Electronic<br />
Clearance market package<br />
to include border crossings<br />
Includes systems that allow<br />
commercial vehicles to be<br />
weighed by equipment<br />
installed on the roadside,<br />
allowing the vehicle to<br />
bypass traditional weigh<br />
stations<br />
Provides for automated<br />
roadside safety monitoring<br />
and reporting<br />
Provides for on-board<br />
commercial vehicle safety<br />
monitoring and reporting<br />
On-board monitoring and<br />
maintenance system.<br />
Integrates incident<br />
management capabilities<br />
with commercial vehicle<br />
tracking to assure effective<br />
treatment of HAZMAT<br />
material and incidents<br />
Separate databases at various<br />
agencies<br />
Not applicable<br />
WIM exists<br />
Limited pullout roadside check<br />
locations<br />
Generally a private sector<br />
initiative<br />
Generally a private sector<br />
initiative<br />
Not applicable<br />
Electronic sharing of information between agencies<br />
Not applicable<br />
None<br />
More pullout locations needed<br />
None<br />
None<br />
Not applicable<br />
38
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
CVO11<br />
CVO12<br />
CVO13<br />
Market<br />
Package Name<br />
Roadside<br />
HAZMAT<br />
Security<br />
Detection and<br />
Mitigation<br />
CV Driver<br />
Security<br />
Authentication<br />
Freight<br />
Assignment<br />
Tracking<br />
Emergency Management<br />
EM01<br />
EM02<br />
Emergency<br />
Response<br />
Emergency<br />
Routing<br />
Brief Description <strong>Region</strong> 4 Application – Existing <strong>Region</strong> 4 Application – Future<br />
Uses roadside equipment to<br />
detect HAZMAT cargo,<br />
then checks the vehicle’s<br />
credentials to ensure that<br />
the cargo and driver are<br />
properly authorized.<br />
Uses onboard security to<br />
detect unauthorized CV<br />
drivers, and if detected,<br />
disables the vehicle.<br />
Registration and tracking of<br />
the vehicle, cargo shipment,<br />
and driver.<br />
Provides computer-aided<br />
dispatch <strong>Systems</strong><br />
Automatic Vehicle<br />
Location and dynamic<br />
routing for emergency<br />
vehicles.<br />
EM03 Mayday Support Supports response to<br />
requests for help from invehicle<br />
or call-box type<br />
systems<br />
EM04<br />
Roadway<br />
Service Patrols<br />
Service trucks that respond<br />
to reports of disabled<br />
vehicles and help to clear<br />
Not applicable<br />
Generally a private sector<br />
initiative<br />
Not applicable<br />
Weld County emergency services<br />
dispatch and 911. Larimer County<br />
Sheriff dispatch. Fort Collins<br />
emergency department. Loveland<br />
emergency response. CSP<br />
dispatch<br />
Existing CAD for emergency<br />
vehicles in Estes Park. Trains<br />
block emergency vehicle access<br />
in La Salle. Existing signal preemption<br />
in Greeley, Loveland,<br />
and Fort Collins.<br />
Existing in-vehicle systems<br />
Not applicable<br />
None<br />
Not applicable<br />
None<br />
None<br />
None<br />
None On call tow services during bad weather for I-25<br />
39
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
EM05<br />
Market<br />
Package Name<br />
<strong>Transportation</strong><br />
Infrastructure<br />
Protection<br />
Brief Description <strong>Region</strong> 4 Application – Existing <strong>Region</strong> 4 Application – Future<br />
them, in order to reduce<br />
the impact on the traffic<br />
flow<br />
Uses surveillance cameras<br />
and sensors to monitor<br />
critical infrastructure such<br />
as bridges, tunnels, etc.<br />
EM06 Wide-Area Alert Facilitates the use of ITS<br />
driver information devices<br />
(such as DMS and HAR)<br />
to spread emergency alert<br />
Messages – example<br />
would be Amber Alerts<br />
EM07<br />
EM08<br />
EM09<br />
Early Warning<br />
System<br />
Disaster<br />
Response and<br />
Recovery<br />
Evacuation and<br />
Reentry<br />
Management<br />
Uses various types of<br />
sensors and monitors to<br />
facilitate early detection<br />
and warning of<br />
emergencies, including<br />
weather emergencies and<br />
terrorist attacks<br />
Supports the overall<br />
coordinated response to<br />
emergencies by<br />
transportation, emergency<br />
response, and maintenance<br />
personnel<br />
Supports coordination of<br />
evacuation plans by<br />
transportation and safety<br />
agencies as well as the<br />
subsequent return to the<br />
evacuation area<br />
None<br />
<strong>CDOT</strong> ITS currently places DMS<br />
messages on request of R4, State<br />
Patrol, and HQ. This includes<br />
Amber Alerts<br />
Stream level monitoring in<br />
Loveland, Fort Collins, and Estes<br />
Park. Some linked to emergency<br />
operations centers. Estes Park has<br />
a SCADA system with alarm<br />
capabilities. Existing stream<br />
monitoring on US 85, but not<br />
linked to any centers<br />
Existing emergency management<br />
plans<br />
Existing emergency management<br />
plans<br />
Monitoring bridges, Park-n-Rides and VMS against<br />
graffiti vandalism<br />
None<br />
None<br />
None<br />
None<br />
40
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
EM10<br />
Market<br />
Package Name<br />
Disaster<br />
Traveler<br />
Information<br />
Maintenance and Construction<br />
MC01 Maintenance<br />
and<br />
Construction<br />
Vehicle and<br />
Equipment<br />
Tracking<br />
MC02<br />
MC03<br />
MC04<br />
MC05<br />
MC06<br />
Maintenance<br />
and<br />
Construction<br />
Vehicle<br />
Maintenance<br />
Road Weather<br />
Data Collection<br />
Weather<br />
Information<br />
Processing and<br />
Distribution<br />
Roadway<br />
Automated<br />
Treatment<br />
Winter<br />
Maintenance<br />
Brief Description <strong>Region</strong> 4 Application – Existing <strong>Region</strong> 4 Application – Future<br />
Augments existing traveler<br />
information systems to<br />
provide emergency<br />
traveler information, such<br />
as evacuation routes, etc.,<br />
in the event of a disaster<br />
Tracks the location of<br />
maintenance and<br />
construction vehicles and<br />
other equipment<br />
On-board diagnostics that<br />
provide maintenance and<br />
repair information for<br />
snowplows, trucks, etc.<br />
Collection of weather and<br />
road conditions data using<br />
sensors installed near the<br />
roadway.<br />
Processing and<br />
dissemination of<br />
road/weather conditions<br />
information to travelers,<br />
maintenance workers, etc.<br />
Automated anti-icing<br />
systems for bridges and<br />
roadways<br />
Supports winter road<br />
maintenance including<br />
snowplow operations,<br />
roadway treatments (i.e.,<br />
Existing emergency management<br />
plans<br />
Data communications and GPS<br />
systems on <strong>CDOT</strong> snow plows<br />
exists<br />
None<br />
Weather stations in Fort Collins,<br />
Windsor, Loveland, Greeley, and<br />
<strong>CDOT</strong> R4<br />
<strong>CDOT</strong> MDSS system exists<br />
City of Fort Collins Timberline<br />
Bridge de-icing system<br />
Existing winter maintenance<br />
operations<br />
None<br />
More deployment anticipated<br />
None<br />
More deployment needed<br />
Expansion of MDSS<br />
Specific locations<br />
None<br />
41
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
MC07<br />
MC08<br />
MC09<br />
MC10<br />
MC11<br />
MC12<br />
Market<br />
Package Name<br />
Roadway<br />
Maintenance<br />
and<br />
Construction<br />
Work Zone<br />
Management<br />
Work Zone<br />
Safety<br />
Monitoring<br />
Maintenance<br />
and<br />
Construction<br />
Activity<br />
Coordination<br />
Environmental<br />
Probe<br />
Surveillance<br />
Infrastructure<br />
Monitoring<br />
Brief Description <strong>Region</strong> 4 Application – Existing <strong>Region</strong> 4 Application – Future<br />
salt spraying, etc.)<br />
Supports scheduled and<br />
unscheduled maintenance<br />
and construction of ITS<br />
and non-ITS equipment<br />
Enables construction delay<br />
and routing information to<br />
be provided en-route to<br />
drivers, and also facilitates<br />
providing this information<br />
to other agencies<br />
Intrusion Alarms” and<br />
other devices that warn if a<br />
vehicle is approaching a<br />
work zone at a high rate of<br />
speed or has entered the<br />
work zone. May also<br />
monitor movements of<br />
workers<br />
Coordination of<br />
maintenance and<br />
construction activities<br />
between various agencies<br />
for improved operations.<br />
Collects environmental<br />
data from on-board vehicle<br />
sensors<br />
Monitors infrastructure via<br />
both fixed and vehiclebased<br />
sensors<br />
Existing maintenance and<br />
construction operations<br />
None<br />
None<br />
Most agencies post scheduled<br />
road closures to web sites<br />
Not applicable<br />
Not applicable<br />
None<br />
As needed<br />
None<br />
Need consolidation of all sources<br />
Not applicable<br />
Not applicable<br />
42
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
C. Linking <strong>Transportation</strong> Problems to Market Packages<br />
Appendix G shows the Market Packages that are directly applicable to the transportation problems. The<br />
Market Package ensures technical integration and jurisdictional coordination when the solution is<br />
implemented. It should be noted that not all of the transportation problems correlate with a Market<br />
Package due to the specific nature of the problem. For example, POE Antiquated Business System and<br />
Silo databases do not lend themselves to allow for easily accessible and up-to-date information sharing.<br />
D. Linking TSAs to Market Packages<br />
Appendix H shows the relationship between <strong>Transportation</strong> Service Areas and applicable Market<br />
Packages. This analysis is useful in the development of the ITS Architecture.<br />
43
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
VI.<br />
ITS DEPLOYMENT STRATEGIES WITHIN THE REGION<br />
This section identifies the regional strategies regarding ITS deployment including specific<br />
recommendations concerning each ITS deployment.<br />
A. Recommended ITS Strategies for the <strong>Region</strong><br />
Strategy #1- Implement ITS Deployments that can Provide Benefits on Freeways, State Highways, US<br />
Highways and <strong>Region</strong>ally Significant Corridors<br />
These corridors carry the highest traffic volumes within the <strong>Region</strong> and these would receive the greatest<br />
benefits from ITS implementation, and be able demonstrate greater overall mobility and safety benefits. It<br />
should be noted that local agencies are not precluded from deploying ITS on their local street and<br />
roadways that serve local needs; however deployment should be considered in terms of technical<br />
integration and jurisdiction coordination with the regional ITS network. ITS deployments for Strategy #1<br />
include:<br />
<br />
Communication Infrastructure (Fiber Optic Cable & Network Equipment) – Implement<br />
communication coverage to corridors or corridor segments where no coverage exists, and to<br />
increase the connectivity, reliability and integration of all ITS devices.<br />
CTMC is migrating from a SONNET based fiber optic communications to an Ethernet based fiber<br />
optic communications to expand bandwidth capacity to support its ITS devices. Greeley is in the<br />
process of implementing an Ethernet based fiber optic communications within the City to support<br />
traffic signals, weather stations, CCTV and ATR. Ethernet based fiber optic communications is<br />
recommended for the urban area within the <strong>Region</strong>, which is defined by the following<br />
boundaries: SH-287 on the west, US-85 on the east, SH-7 on the south and SH-14 on the north.<br />
Cellular wireless communications has shown increased improvements in reliability and<br />
bandwidth and therefore is recommended for isolated ITS deployments in rural areas where it<br />
would be cost prohibitive to install fiber communications to support very few ITS devices.<br />
Regardless, <strong>CDOT</strong> and local agencies should take advantage of opportunities such as<br />
partnerships, new development, construction, etc. to install fiber optic communications along the<br />
corridors where possible.<br />
Traveler Information – It is recommended that traveler information be implemented on I-25<br />
corridor and on all corridors that have received the highest priorities for traveler information.<br />
Colorado <strong>Transportation</strong> Management Center (CTMC) & Urban Traffic<br />
Operation/Management Centers (TOC/TMC) – CTMC and the urban centers collect traffic<br />
conditions information based on overall operational and maintenance responsibility for the<br />
corridor. CTMC will continue to serve as the primary center for dissemination of statewide<br />
traveler information within the <strong>Region</strong> through the COTrip website, 511 and Gov Delivery<br />
system. The 511 automated phone systems has the capability to transfer to local 511 automated<br />
phone systems. The Gov Delivery system provides text and email alerts for incidents,<br />
maintenance and construction. Local agencies that collect traveler information on their corridors<br />
can disseminate the information on agency websites and coordinate with CTMC to display the<br />
information on the COTrip website.<br />
<br />
Incident Management Plan (IMP) – Improves coordination between agencies and identifies<br />
operational roles and responsibilities, protocols, and alternative routes when responding to<br />
incidents. IMP exists for I-25 and US-36 corridors. IMP is recommended for US-85 (Fort Lupton<br />
to Greeley). These plans should be updated on a regular basis to address changing conditions.<br />
44
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
<br />
<br />
<br />
<br />
<br />
<br />
Courtesy Patrol/Tow Vehicles – Assists law enforcement to utilize resources more effectively<br />
when incidents occur during severe weather conditions. On-call courtesy patrol is recommended<br />
along I-25 within the <strong>Region</strong>. The private tow vehicles would tow the impacted vehicle to a<br />
designated safe zone and be available to assist any other incidents.<br />
Traffic Responsive/Traffic Adaptive Control – Time-Of-Day (TOD) plans are sufficient to<br />
meet the needs of normal traffic conditions. These plans typically need to be updated every 3-5<br />
years. Traffic adaptive pilot project is being implemented in Greeley. The results will be used to<br />
determine other potential future installations within the <strong>Region</strong>. Corridors such as SH-119, SH-7<br />
West and SH-52 could benefit from implement of traffic responsive control i.e., pre-designed<br />
timing plans based on traffic condition thresholds to maximize corridor efficiency and responds<br />
to changing traffic conditions. Traffic responsive control would also apply for traffic signals<br />
along event and incident routes.<br />
Dynamic Message Signs – The signs provide real time traveler information to drivers on the<br />
corridors. In addition, they can be used to support CSP safety campaigns, promotion of COTrip,<br />
511 and alternative modal options. The signs are recommended at major decision points.<br />
Ramp Meters – Ramp meters exist on US-36. It is recommended that ramp meters be installed<br />
on I-25 from Loveland to Fort Collins based on the volumes and indicated levels of congestion.<br />
The installation of ramp meters will reduce the friction between freeway traffic and the traffic<br />
merging from the ramps and result in a more smoother operation. However, it should be noted<br />
that a ramp meter warrant study needs to be conducted before ramp meter can be deployed.<br />
Closed Circuit Television Cameras (CCTV) – Increase real-time observation coverage along<br />
corridors. CCTV is recommended at major signalized intersections or intersection of highways.<br />
The images from the CCTV should be made available on COTrip website,<br />
Weather Stations – Expand the deployment of weather and pavement sensors on corridors to<br />
assist maintenance personnel and provide information to travelling public. Given the<br />
geographical area and the significant impacts of weather conditions across the region, deployment<br />
of weather stations is recommended on each corridor.<br />
Strategy #2 - Increase transit ridership and demand by integration and coordination with alternative<br />
travel modes.<br />
Transit, van pool, car pool, bicycle and Park-N-Ride modal options should be integrated to increase usage<br />
of alternative modes of travel. ITS deployments for Strategy #2 include:<br />
<br />
<br />
<br />
Add Static Transit Route Information to Google – The site provides transit agencies a platform<br />
to post transit route information. Currently, there are over 400 agencies that provide transit<br />
information on the site. Within the <strong>Region</strong>, it is recommended that transit route information from<br />
all transit agencies be posted on the site. This is an interim solution until the on-line planning<br />
services website is developed.<br />
On-line Trip Planning Services Website – The ability to integrate travel mode options will<br />
assist in generating interest and increased usage. It is recommended that the smartrips.org<br />
website be rebranded and integrated to include transit, vanpool, carpool, bicycle and Park-N-<br />
Rides. The site is currently designed only for vanpool users. It does have transit routes and stops<br />
information.<br />
Automated Fare Collection System – It is recommended that automated fare collection systems<br />
be implemented for GET to increase transit usage and improve operational efficiency.<br />
Automated fare collection systems exist for Transfort and COLT.<br />
45
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
<br />
<br />
<br />
Transit Passenger Counting System - It is recommended that passenger count system be<br />
implemented for GET and Transfort. Automated system exists for COLT.<br />
Transit Services to Park-N-Ride Locations – It is recommended that transit services be<br />
provided to these locations as it would promote usage of transit and the Park-N-Ride lots.<br />
NextBus Application – It is recommended that real-time transit information be provided at<br />
transit centers, Park-N-Rides and key bus stops.<br />
Fare Collections Kiosks – Fare collection kiosks should be implemented after transit services<br />
and associated improvements at Park-N-Rides are completed. In addition, these kiosks should be<br />
implemented at transit centers.<br />
It should be noted that a study is planned to examine the feasibility of a regional transit agency. The study<br />
is anticipated to be completed by December 2012. The potential formation of a regional transit agency<br />
can have a significant impact on Transit ITS within the <strong>Region</strong>. Operationally, there will be existing<br />
systems for dispatch, maintenance, scheduling, etc. that are being used by transit agencies that may not be<br />
compatible with each other. Currently, these existing systems support transit ITS.<br />
Strategy #3- Implement and promote regional projects that increase cooperation and coordination within<br />
and between agencies<br />
ITS deployments for Strategy #3 include:<br />
<br />
<br />
<br />
<br />
Access to MDSS and Traffic Video for Agencies – It is recommended that local law<br />
enforcement, local transportation agencies and POE be provided access to the information. At<br />
POEs, traveler information kiosks should be installed to allow dissemination of information to<br />
commercial vehicle drivers.<br />
<strong>Region</strong>al Guidelines for Arterial Conditions Display and Sharing with <strong>CDOT</strong> – Fort Collins<br />
provides arterial condition information on the City website. As more agencies decide to provide<br />
arterial condition information, it is critical to display information consistently across the region so<br />
that the travelling public is not confused. Within the DRCOG area, <strong>Region</strong>al Guidelines are<br />
being developed for arterial condition information. It is recommended that the <strong>Region</strong> consider<br />
using the guidelines. It is important to achieve consistency across the region and the Front Range<br />
to display information on the COTrip website.<br />
Performance Monitoring for Corridors – There is a significant interest and value for<br />
performance measures reporting on corridor operations. The needs of performance measurements<br />
are better served if it is done parallel to ITS deployment for traveler information. As corridors are<br />
instrumented for traveler information, they will be integrated with CTMS. CTMC is currently<br />
considering a reporting tool that interfaces with the CTMS database to generate performance<br />
measures. Within the DRGOG area, agencies have identified several key performance measures<br />
and indices. For the <strong>CDOT</strong> <strong>Region</strong> 4, it is recommended that the <strong>Region</strong> consider using the<br />
measures. Similar to the regional guidelines for arterial conditions display, it is important to<br />
achieve consistency across the <strong>Region</strong> and Front Range.<br />
Traveler information for Estes Park/RMNP – It is recommended that interfaces with 511 and<br />
COTrip be developed to provide traveler information. This would include traffic condition<br />
information on US-34, US-36 and I-25 for outbound traffic leaving RMNP or Estes Park and<br />
parking availability information for the parking hub and satellites. RMNP should install cameras<br />
on Bear Lake Road to provide traffic and parking conditions information. Also, all of this<br />
information would be provided at the Estes Park Transit Hub (Town Visitor Center) via kiosk or a<br />
46
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
<br />
<br />
<br />
<br />
video wall. There is need to provide incident information on US-34 so that travelers entering<br />
Poudre Canyon have the opportunity to turnaround if the roadway ahead is closed.<br />
<strong>CDOT</strong> Maintenance Vehicles with AVL/Camera and In-Vehicle Interface Device – It is<br />
recommended that all <strong>CDOT</strong> maintenance vehicles be equipped with AVL/Camera and In-<br />
Vehicle interface device to allow maintenance personnel to report back on the work conditions.<br />
Expansion of MDSS System – The deployment of additional weather stations will provide more<br />
granular information. Additional routes will need to be added to MDSS and will require<br />
integration and revised forecast models. Also, given the demand for MDSS, additional users will<br />
need to be added to provide access to the information. This would require proper licensing and<br />
network management functions.<br />
Event Management Plans – It is recommended that Event Management plans be developed to<br />
meet the event traffic demands in Greeley and Larimer County. The plan would also include<br />
traffic responsive plans for impacted traffic signals to support event traffic.<br />
Expansion of CCTM Application for Traffic Agencies – Within the DRCOG area, <strong>CDOT</strong> has<br />
developed the CCTM application that allows users to access traffic data such as location of traffic<br />
signals, secure weather data and contract information for planned construction and maintenance<br />
projects. The performance measures will be accessible on the CCTM. It is recommended that the<br />
application be provided to <strong>CDOT</strong> <strong>Region</strong> 4 as more ITS deployment occurs. Again, this will also<br />
ensure consistency within Front Range.<br />
Expand CTMS Functionality for Maintenance and Construction Activity Information –<br />
This would allow local agencies the ability to add maintenance and construction activity<br />
information so that it is available on COTrip, 511 and Gov Delivery. Specific requirements need<br />
to be developed.<br />
<br />
Portable Monitoring System for Load Deficient Structures for Size and Weight<br />
Enforcement – This would implement the system at high priority locations within the <strong>Region</strong>.<br />
Specific requirements need to be developed.<br />
B. Limitations for ITS Deployment<br />
ITS deployments do not include or cover improvements to highway infrastructure and business functions.<br />
Such improvements should be addressed within the relevant planning efforts coordinated within the<br />
agency or regionally. The intent of this section is to ensure that these needs be formally recognized and<br />
any opportunities to implement the needs be considered.<br />
The following are a list of improvements that go beyond the scope of ITS technology:<br />
<br />
Park-N-Ride Improvements<br />
o PNR Upgrades to add more capacity at SH-402 and SH–60<br />
o PNR Upgrades to improve access at SH-492 and US-34<br />
o Need for New PNR Sites<br />
• On SH-287 between Loveland and Berthoud<br />
• On SH-287 between Fort Collins and Loveland – Transfort is building the South<br />
Transit Center, which will open in 2013. It will have 85 parking spaces.<br />
47
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
<br />
<br />
<br />
o Both at upgraded PNR sites and new sites, improvements to accommodate Transit<br />
services include:<br />
• Bus shelter<br />
• Bus turn around<br />
• Lighting<br />
Pull-Outs on Corridors for Size and Weight Enforcement – Appendix I provides information<br />
on the POE’s pull out areas priorities within the <strong>Region</strong>.<br />
Parking Facilities at Estes Park - The Town’s Transit Hub center (Town’s Visitor Center) is<br />
expected to be completed in summer of this year. The Center will have about 200 parking<br />
spaces. The Stanley Satellite hub on US-36 has 408 parking spaces and will be operational by<br />
June 2011. There is a need for a satellite hub along US-34. The Town intends on building more<br />
satellite Hubs to provide additional parking spaces and access to shuttle services.<br />
Increase Transit Levels of Service in Estes Park – Currently, transit shuttle busses operate<br />
between the end of June to Labor Day. It has over 19,000 users and buses run on 1-hour<br />
frequency. The current frequency is not sufficient to increase transit usage in the area.<br />
<strong>Region</strong>al Bus Routes – Within the <strong>Region</strong>, there is significant inter-city travel. However, there<br />
is only one regional bus route (FLEX). Serious consideration should be given to provide regional<br />
routes in order to increase transit competitiveness.<br />
Bicycle Routes to Transit Centers and PNRs – These routes would provide physical<br />
connectivity between modes and would increase usage of alternative modal options.<br />
Antiquated Business <strong>Systems</strong> – Many data sources used by the POE are maintained within<br />
separate silo databases. The data includes <strong>CDOT</strong> Permits, Department of Revenue (DOR)<br />
commercial vehicle taxes, Unified Carrier Registration (UCR), Division of Motor Vehicle<br />
(DMV) and Informix (POE business system). In order to easily share information between these<br />
databases would require understanding of business technology, security, etc. functions. More<br />
importantly, it would require significant coordination between these agencies and appropriate<br />
funding.<br />
C. Recommended ITS Deployment Timeframe<br />
The plan is fiscally unconstrained and following deployment time frames were recommended for<br />
implementation:<br />
Short Term – 0 to 3 years<br />
Medium Term – 4 to 6 years<br />
Long Term – 7 to 10 years<br />
These deployment timeframes are consistent with other <strong>CDOT</strong> <strong>Region</strong>’s implementation plans.<br />
It is a recognized that simply deploying devices does not itself improve the effectiveness or efficiency of<br />
the transportation system. Adequate transportation agency staffing must be provided to operate and<br />
maintain the system in order to most effectively take advantage of the transportation management tools.<br />
Additionally, system equipment maintenance and replacement are critical factors in the long-term<br />
serviceability of the ITS devices and infrastructure. Maintenance and replacement are well recognized<br />
requirements of all transportation investments. Maintenance of ITS devices is different from maintenance<br />
of a highway or a bridge. Typically, complete functionality is lost when the device fails rendering it<br />
unusable. Implicit in this Plan is an assurance by the stakeholders of sufficient staff and resources for<br />
management; operations, maintenance, and replacement of ITS devices and infrastructure to make them<br />
an effective investment.<br />
48
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
VII.<br />
ITS DEPLOYMENT COSTS<br />
For ease of understanding, ITS deployments are categorized in the following three priority areas:<br />
Corridors –Interstates, State Highways, US Highways and <strong>Region</strong>ally significant corridors.<br />
Transit – Transit and other alternative modes such as vanpools, carpools and bicycles.<br />
<strong>Region</strong>al – Deployments that cannot be tied to a corridor or transit agency and provide <strong>Region</strong>al<br />
benefits.<br />
A. ITS Deployment for Corridors<br />
The ITS deployment projects identified for each of the corridors in <strong>Region</strong> 4 is shown in Appendix J. For<br />
each corridor, the rationale for the ITS deployment is based on the information shown in Appendix K.<br />
Appendix J contains the following items for each corridor:<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
Corridor – Provides the name of the corridor with its limits and approximate mileage.<br />
Project – Identifies the projects to be implemented<br />
ITS Devices – Indicates the type of ITS device to be implemented<br />
Existing Devices – Provides the number of ITS devices existing on the corridor, by type of<br />
device. It indicates if an agency other than <strong>CDOT</strong> has an existing device<br />
Proposed Devices – Provides the number of ITS devices proposed for the corridor segment<br />
Proposed Location – Identifies the locations for the proposed ITS devices<br />
Unit Price – Provides the price for each unit of proposed ITS devices (Appendix L shows the<br />
device costs used for the Plan)<br />
Needed Investment – Identifies the needed investment (estimated construction costs) for <strong>CDOT</strong><br />
<strong>Region</strong> 4 ITS projects in 2011 dollars (estimates are not indexed). Needed investments also<br />
include estimated costs for network equipment necessary for system connectivity; however, they<br />
do not include operations and maintenance costs.<br />
Total Project Costs –Provides the total cost by project for the proposed number of ITS devices<br />
units in Million Dollars.<br />
Project Timeframe –Identifies the deployment priority as determined by the <strong>Region</strong>. For <strong>Region</strong> 4<br />
the following ITS deployment timeframe is used:<br />
o Short Term: 0 to 3 years<br />
o Medium Term: 4 to 6 years<br />
o Long Term: 7 to 10 years<br />
<br />
<br />
<strong>Transportation</strong> Problem Area (TPA) – Identifies the applicable <strong>Transportation</strong> Problem Areas<br />
addressed on the <strong>CDOT</strong> <strong>Region</strong> 4 corridors.<br />
<strong>Transportation</strong> Service Area (TSA) - Identifies the applicable <strong>Transportation</strong> Service Areas<br />
addressed on the <strong>CDOT</strong> <strong>Region</strong> 4 corridors.<br />
49
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
Appendix M shows total ITS device deployment costs by deployment time frame and device count or<br />
approximate corridor miles. It shows the magnitude of deployment for each ITS device deployment<br />
within the <strong>Region</strong>. Appendix N shows individual corridor sheets that contain the name of the corridor, its<br />
limits, approximate mileage, range of ADT counts along the corridor and a corridor map that identifies<br />
ITS deployment. The table for each corridor sheet provides the same information as shown on Appendix<br />
K, but specific for each corridor.<br />
ITS deployments have been identified on 64 corridors totaling $153.99 million dollars. These ITS<br />
deployments are proposed along approximately 1,900 center line miles. Table 5 shows the needed<br />
investment summary for corridor projects in <strong>Region</strong> 4.<br />
Table 5:<br />
Needed ITS Investment Summary for <strong>Region</strong> 4 Corridor Projects<br />
Corridor Projects<br />
Short Term Medium Term Long Term<br />
Total<br />
Number of Projects 150 42 125 317<br />
Needed Investment<br />
(In $Millions) $75.59 $38.46 $36.94 $153.99<br />
B. ITS Deployment for Transit<br />
Appendix O shows the ITS deployment for transit and contains the following items:<br />
<br />
<br />
<br />
<br />
Description – Provides the name of the project.<br />
ITS Deployment – Identifies the ITS application to be implemented.<br />
Total Project Costs – Provides the total cost by project for the proposed number of ITS<br />
devices in units of Million Dollars.<br />
<strong>Transportation</strong> Problem Area (TPA) – Identifies the applicable <strong>Transportation</strong> Problem<br />
Areas.<br />
<strong>Transportation</strong> Service Area (TSA) – Identifies the applicable <strong>Transportation</strong> Service<br />
Areas.<br />
ITS deployments have been identified for 9 transit projects in <strong>Region</strong> 4 that total $1.8 million dollars.<br />
Table 6 shows the needed investment summary for transit projects in <strong>Region</strong> 4.<br />
Table 6: Needed ITS Investment Summary for <strong>Region</strong> 4 Transit Projects<br />
Transit Projects<br />
Short Term Medium Term Long Term<br />
Total<br />
Number of Projects<br />
Needed Investment<br />
(In $Millions)<br />
2 3 2 9<br />
$0.20 $0.95 $0.65 $1.80<br />
50
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
C. ITS Deployment for <strong>Region</strong>al<br />
Appendix P shows the ITS deployment for <strong>Region</strong>al projects and it contains the following items:<br />
<br />
<br />
<br />
<br />
Description – Provides the name of the project.<br />
ITS Deployment – Identifies the ITS applications to be implemented.<br />
Total Project Costs – Provides the total cost by project for the proposed number of ITS<br />
devices in million dollar units.<br />
<strong>Transportation</strong> Problem Area (TPA) – Identifies the applicable <strong>Transportation</strong> Problem<br />
Areas.<br />
<strong>Transportation</strong> Service Area (TSA) – Identifies the applicable <strong>Transportation</strong> Service<br />
Areas.<br />
ITS deployments have been identified for 10 regional projects in <strong>Region</strong> 4 that total $2.18 million dollars.<br />
Table 7 shows the needed investment summary for regional projects in <strong>Region</strong> 4.<br />
Table 7:<br />
Needed ITS Investment Summary for <strong>Region</strong> 4 <strong>Region</strong>al Projects<br />
<strong>Region</strong>al Projects<br />
Short Term Medium Term Long Term<br />
Total<br />
Number of Projects 4 4 2 10 Projects<br />
Needed Investment<br />
(In $Millions) $0.53 $1.00 $0.65 $2.18<br />
D. Financial Summary<br />
<strong>CDOT</strong> <strong>Region</strong> 4 has currently identified a funding need for ITS projects at $157.97 million dollars. This<br />
amount is a needed investment cost that includes device costs, preliminary and construction engineering<br />
costs and system costs that include improvements for network and software integration. However, this<br />
estimate does not include operations or maintenance costs and is not indexed. Table 8 shows the overall<br />
summary of needed ITS investment for <strong>Region</strong> 4.<br />
Areas<br />
Table 8: Summary of Needed ITS Investment for <strong>Region</strong> 4<br />
Needed Investment (In Millions)<br />
Corridors Projects $153.99<br />
Transit Projects $1.8<br />
<strong>Region</strong>al Projects $2.18<br />
51
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
Areas<br />
Needed Investment (In Millions)<br />
Total (In $Millions) $157.97<br />
E. Project Sequencing<br />
The number one priority in the region continues to be the I-25 corridor and the installation of the fiber<br />
optic backbone. It would enable <strong>CDOT</strong> to install additional ITS deployment and implement the real-time<br />
travel time application along the corridor. It would allow lateral connectivity to Fort Collins and Loveland<br />
since both entities have fiber with close proximity to I-25, which would enable sharing of data and video.<br />
It would provide connectivity to the CSP facility at Harmony Road and the POE in Fort Collins. It would<br />
also allow communications to Park-N-Ride facilities to support future transit applications. The fiber<br />
backbone is essential to provide high-speed communications infrastructure to support and expand ITS<br />
applications and to fully integrate those applications within the <strong>Region</strong> into an ITS network.<br />
Weather plays a significant role within the <strong>Region</strong> as evidenced by transportation problems identified and<br />
the number of weather stations proposed to be deployed. MDSS is a very successful and efficient tool<br />
within <strong>CDOT</strong> <strong>Region</strong> 4. <strong>CDOT</strong> ITS Branch has design plans ready for 30 weather station locations in the<br />
<strong>Region</strong>. The MDSS system should be expanded to additional corridors to include integration of weather<br />
stations as they are displayed. Furthermore, all remaining <strong>CDOT</strong> maintenance vehicles should be<br />
equipped with AVL/camera and in-vehicle display system to allow for real-time reporting of road<br />
conditions within the MDSS system. Finally, MDSS information should be made available to law<br />
enforcement, POE and local transportation agencies.<br />
Parallel to the focus on weather related improvements, the <strong>Region</strong> should begin integrating transit with<br />
other alternative modes and work to develop an on-line trip planning services website. This would<br />
incorporate transit, vanpool, bicycle, Park-n-Rides and serve to enhance and improve travel within the<br />
<strong>Region</strong> and interconnectivity between alternative modes and vehicle travel.<br />
The <strong>Region</strong> should focus on deployments that build upon existing applications or generate quicker results<br />
with relatively less costs and effort. The <strong>Region</strong> currently has several areas ranging from good to high<br />
level of ITS applications including, DMS coverage on I-25, MDSS coverage and utilization, transit<br />
facility and systems and fiber within the urban areas. Future ITS deployment should seek opportunities to<br />
leverage on the existing ITS in the <strong>Region</strong> in order to maximize the utilization of ITS applications and<br />
interconnectivity of ITS system and benefit from a integrated ITS network.<br />
<strong>CDOT</strong> is currently working with Eaglenet to install fiber along I-25 as part of the Federal Broadband<br />
grant program. <strong>CDOT</strong> is very confident that the fiber will be installed through this partnership. Also, ITS<br />
devices such as CCTV, TTI, radar and network equipment to operate the fiber and devices will be<br />
installed.<br />
RMNP and Estes Park generate more than three million visitors each year. About 40% of those visitors<br />
live in the Front Range. Traveler information should be provided along US-36 and US-34 to facilitate<br />
travel into and out of RMNP and Estes Park. Additional ITS devices should be deployed to support<br />
traveler information so that travelers can make decisions at critical junctions on the routes. Also, RMNP<br />
and Estes Park shuttle bus and Park-n-Ride information should be displayed on the COTrip website and,<br />
where appropriate, on DMS on the roadway and incorporated into the 511 automated phone system.<br />
52
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
VIII.<br />
CONCLUSION<br />
Funding remains the foremost obstacle to implementation of ITS project in the region. <strong>CDOT</strong> <strong>Region</strong> 4<br />
has currently identified a funding need for ITS projects of $157.97 million dollars. This amount includes<br />
infrastructure devices, preliminary and construction engineering, construction and network/system cost.<br />
However, the estimate does not include operations or maintenance costs and it is not indexed.<br />
A. <strong>Region</strong>al ITS Project Funding Sources<br />
Funding of ITS Projects is possible through various funding sources. These sources include, but are not<br />
limited, to the following:<br />
Table 9:<br />
Funding Sources<br />
Category<br />
Funding Sources<br />
Corridor Deployment <strong>CDOT</strong> Congestion Relief Program – A state wide program<br />
aimed at reducing congestion<br />
Colorado Safe Routes to School Program (SRTS) – A<br />
program that improves safety for school routes<br />
Hazard Elimination Safety Program (HES) - A federal<br />
safety program that provides funds for safety<br />
improvements on all public roads and highways<br />
FASTER Legislation – Recently approved legislation<br />
establishing funding of surface transportation<br />
infrastructure<br />
Federal and State Grant monies<br />
Coordination with local governments and private<br />
development along corridors<br />
Congestion Mitigation Air Quality (CMAQ)<br />
Statewide <strong>Transportation</strong> Plan (STP)<br />
<strong>CDOT</strong> funds (ITS and <strong>Region</strong> 4)<br />
Local Capital Improvement Program (CIP) & General<br />
funds<br />
Transit Deployment CMAQ<br />
FTA Opportunities<br />
o 5307<br />
o 5316<br />
o 5310<br />
o 5309<br />
Local Match<br />
Advertisement Dollars<br />
Van Pool Dollars<br />
Faster legislation<br />
<strong>Region</strong>al Deployment Same as corridor funding sources and possibly transit funding<br />
sources<br />
B. <strong>Region</strong> 4 ITS Project Funding Deficiencies<br />
With a total funding need in excess of $150 million dollars in conjunction with given budget constraints<br />
and limited revenues for the foreseeable future, it is unrealistic to expect that all ITS projects will be able<br />
53
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
to be implemented within the timeframes identified in the Plan. The following strategies are<br />
recommended to overcome some of the deficiencies related to funding limitations:<br />
<br />
<br />
Include the ITS projects as part of any planning, design, and construction projects along corridors<br />
to maximize implementation and leverage the construction project funding - As corridor projects<br />
are being developed, there is an opportunity to implement ITS projects and realize cost saving<br />
synergies. For example, the inclusion of an ITS project within a corridor overlay project can result<br />
in potential cost savings of 15 to 50 percent. This is due to the typical overlay project requirements<br />
of lane closures, alternative routings, traffic control, and construction and project engineering cost<br />
requirements that often must be duplicated in many stand alone ITS projects.<br />
Look for synergies with other agencies or projects that allow for cost sharing opportunities - This<br />
would include projects with other departments within the agency or other agencies. For example,<br />
working with Police, Streets, Parks, Water, etc. divisions to determine needs for communications,<br />
video, weather information and other would allow for cost sharing opportunities regarding ITS<br />
investment. Also, other departments or agencies may assist with maintenance and operational<br />
functions.<br />
Sharing costs with private partners where development requires corridor improvements -<br />
Typically, private partners would include developers, telecommunications companies, cable<br />
companies and media. Improvements can possibly be included in exchange for access to right-ofway,<br />
waiving of permit fees on other partnering arrangements.<br />
<br />
<br />
Evaluating and touting the benefits of existing ITS applications to garner further ITS support - It<br />
is important to capture and demonstrate tangible and intangible benefits of ITS. The tangible benefits<br />
could include before/after studies and surveys. The intangible benefits could include anecdotal or<br />
specific case studies. It is also important to have non-transportation stakeholders tout the benefits of<br />
ITS.<br />
Selectively choosing ITS project deployments to ensure high benefit/cost ratios and/or build on<br />
existing deployment – This would include deployment of projects that have had a high success rate<br />
in other <strong>CDOT</strong> <strong>Region</strong>s or elsewhere. Additionally, it is important to build upon existing ITS<br />
deployments and applications that are successful.<br />
C. Champion for ITS within the <strong>Region</strong><br />
Within the <strong>Region</strong> two champions for ITS are identified.<br />
1. The <strong>CDOT</strong> <strong>Region</strong> 4 Traffic Operations Engineer has been identified as the champion for ITS. The<br />
anticipated role of the ITS Champion would include the following:<br />
<br />
<br />
<br />
<br />
<br />
Provide leadership and vision for ITS within the <strong>Region</strong><br />
Build strong relationships with other stakeholders including Law Enforcement agencies, POE,<br />
Towns and Cities.<br />
Establish an ITS working group committee and conduct committee meetings every six months to<br />
review plan status, priority and ITS Implementation.<br />
Ensure that ITS is systematically deployed in the <strong>Region</strong> in accordance with vision, priority and<br />
implementation identified in <strong>CDOT</strong> R4 ITS Plan.<br />
Promote successful ITS deployments with policy makers and management staff.<br />
54
<strong>CDOT</strong> <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan<br />
2. NFR MPOs TDM Planner has been identified as the champion for ITS for Transit, Van pools, Car<br />
pools and bicycle modes of travel.<br />
<br />
<br />
<br />
Co-ordinate and work closely with ITS champion for the <strong>Region</strong>.<br />
Establish an ad-hoc committee and conduct meetings every three months.<br />
Promote integration of alternative modes of travel and development of online trip planning<br />
services.<br />
D. Next Steps<br />
This <strong>Region</strong> 4 ITS <strong>Strategic</strong> Implementation Plan is a consolidation of all planned/desired ITS projects<br />
for <strong>CDOT</strong> <strong>Region</strong> 4. The objective of this plan is to provide a single resource that <strong>Region</strong> 4 stakeholders<br />
can utilize to effectively manage the implementation of the ITS Program in <strong>Region</strong> 4. This plan should<br />
be referenced not only during the planning, programming, design, and construction of ITS projects, but<br />
also during the planning stages of non-ITS related projects to leverage design and construction resources<br />
where possible.<br />
55