Projects

The Regional ITS Architecture provides a starting point for project definition. It provides an overall framework that shows how anticipated projects will integrate with each other and with existing systems. This page lists all the ITS projects that have been mapped to the regional ITS architecture.

ProjectStatusTimeframeDescription
1.1. - Regional ITS Information Sharing InitiativePlannedShort termProvide real-time data sharing and monitoring along with ability to construct, reference and report archived and historical dats
1.2 - Regional Multi-Modal Traveler Information System and Journey PlannerPlannedShort-medium termImplement a regional multi-modal traveler information system and journey planner which integrates Missouri and Illinois road and transit information from state, county, local and transit agencies
2.0.1 - Metrolink AVL integration with bus AVLPlannedShort termEnable tracking and coordination of bus and rail schedules and estimation of travel times
2.0.2 - Regional Emergency Alert and Evacuation InitiativePlannedEarly-short termProvides wide-area warning of hazmat / chemical incidents and manage evacuations
2.0.3 - Dynamic Ridesharing InitiativePlannedMedium termEnable online applications which match travelers within a particular corridor and desiring a particular travel time frame
2.1.1 - Integrated ATMS Enhancement (IDOT)PlannedShort termUpgrade current freeway management system to provide integrated real-time information and control for freeways and arterials serving the corridor. .
2.1.2 - Arterial Adaptive Signal Control in E St Louis / Route 3 subareaPlannedShort termUprade traffic signals to adaptive control in Route 3 corridor near I-70/I-55 junction, E St Louis. Includes updated central adaptive signal platform and expanded detection supporting 23 CFR 511 requirements.
2.1.3 - Transfer Connection Protection - IL and downtown MetroLink (ICM Corridor 1)PlannedShort termEnable bus services to coordinate arrival / departure with rail arrival to improve connections.
2.1.4- Transit Signal Priority (ICM Corridor 1)PlannedMedium termIdentify 4 key corridors in City of St Louis
2.1.5 - Parking and travel time real-time information system - Illnois Stations (ICM Corridor 1)PlannedMedium termProvide real-tme parking and train departure information, compare current road and rail travel times (requires AVL data from train) - estimated 8 signs, 4 lots with access sensors for parking counts.
2.1.6 - Bridge Emergency Monitoring and Coordination (ICM Corridor 1)PlannedMedium to long termProvides emergency security monitoring and detection and alerts to regional traffic and police where needed. Includes additional CCTV and physical structure detection technologies
2.1.7 - Queue and Hazard Warning Management (ICM Corridor 1)PlannedLong termAdvance information on back of queue location due to congestion and accidents, includes 1/2 mile to 1 mile DMS spacings. Locate on all approaches to bridge complex, estimated 5 miles inbound and outbound from bridges (I-70, I-64-IL, I-55). Estimated 40 queue warning signs
2.1.8 - ICM Data Hub: Gateway Corridor (ICM Corridor 1)PlannedLong termCollect freeway, arterial traffic data and relevant transit location and travel time data in the corridor for archiving / analysis
2.1.9 - Gateway Corridor Decision Support (ICM Corridor 1)PlannedLong termModeling and simulation using live and archived data to provide adjustments to ramp metering, signal timing, and other operational strategies
2.2.1 - I-64 Ramp Metering (ICM Corridor 2)PlannedShort termManage entrance ramp traffic flow at 15 locations
2.2.2 - Transfer Connection Protection at east-west MetroLink stations (ICM Corridor 2)PlannedShort termEnable bus services to coordinate arrival / departure with rail arrival to improve connections.
2.2.3 - Traffic Signal Interconnection - Clayton Rd - University City (ICM Corridor 2)PlannedMedium termCoordinate signal timings based on real-time traffic, between MoDOT, St Louis County and local signals using common interfaces
2.2.4 - Traffic Signal Interconnection - city corridors (ICM Corridor 2)PlannedMedium termCoordinate signal timings based on real-time traffic, between MoDOT and St Louis City using common interfaces
2.2.5, 2.3.3, 2.4.4 and 2.5.2- Parking and travel time information system (ICM Corridors 2, 3 and 4 plus future transit station in Corridor 5 for BRT)PlannedShort termProvide real-tme parking and train departure information, compare current road and rail travel times (requires AVL data from train)
2.2.6, 2.3.4, 2.4.5, and 2.5.3 - Queue amd Hazard Warning Management (ICM Corridor 2, 3, 4 and 5)PlannedLong termAdvance information on back of queue location due to congestion and accidents, includes 1/2 mile to 1 mile small DMS spacings. (see corrdor locations below)
2.2.7 - ICM Data Hub: I-64 Corridor (ICM Corridor 2)PlannedLong termCollect freeway, arterial traffic data and relevant transit location / travel time data for archiving / analysis
2.2.8 - I-64 Corridor Decision Support (ICM Corridor 2)PlannedLong termModeling and simulation using live and archived data to provide adjustments to ramp metering, signal timing, and other operational strategies
2.3.1 - Transfer Connection Protection at North Hanley MetroLink station (ICM Corridor 3)PlannedShort termEnable bus services to coordinate arrival / departure with rail arrival to improve connections.
2.3.2, 2.4.3, amd 2.5.1 - Traffic Signal Interconnection - Mid-North, Central and Northwest St Louis CountiesPlannedShort termCoordinate signal timings based on real-time traffic, between MoDOT and St Louis County using common interfaces
2.3.5 amd 2.4.6 - ICM Data Hubs: I-170 Corridor (ICM Corridor 3) and I-270/Lindbergh Corridor (ICM Corridor 4)PlannedLong termCollect freeway, arterial traffic data and relevant transit location / travel time data for archiving / analysis
2.3.6 and 2.4.7 - Decision Support (ICM Corridors 3 and 4)PlannedLong termModeling and simulation using live and archived data to provide adjustments to ramp metering, signal timing, and other operational strategies
2.4.1 - Transfer Connection Protection - Shrewsbury Station (ICM Corridor 4)PlannedShort termEnable bus services to coordinate arrival / departure with rail arrival to improve connections.
2.4.2 - Tunnel Emergency Monitoring and Coordination -Lindbergh Blvd (ICM Corridor 4)PlannedShort termProvides emergency security monitoring and detection and alerts to regional traffic and police where needed. Includes additional CCTV and physical structure detection technologies
2.5.4: ICM Data Hub: NW Corridor / GGL (ICM Corridor 5)PlannedLong termCollect freeway, arterial traffic data and relevant transit location / travel time data for archiving / analysis
2.5.5 - Northwest Corridor Decision Support (ICM Corridor 5)PlannedLong TermModeling and simulation using live and archived data to provide adjustments to ramp metering, signal timing, and other operational strategies
3.1.1 - MoDOT: Enhance CCTVPlannedMedium termImprovement of video quality
3.1.2 - MoDOT: Expand Bluetooth ReadersPlannedMedium termImprove Travel Time Accuracy
3.1.3 - MoDOT: Add Static Destination DMS (travel time)PlannedLong termSupport expanded travel time info for multiple destinations
3.1.4 - MoDOT: Enhance Freeway and Arterial DMS (full matrix color)PlannedLong termExpand level and quality of information provided, supporting MUTCD-type messaging displays
3.1.5 - MoDOT: Expand Adaptive Control - ArterialsPlannedLong termReduce arterial congestion through improved real-time responsive operations
3.2.1 - IDOT: Update website to show live video and arterial dataPlannedShort termExpand functionality and coverage for IDOT website
3.2.2 - IDOT: Arterial Adaptive Signal Control - Phase II (region outside Route 3 / E St Louis)PlannedShort termUprade traffic signals to adaptive control. Uses Phase 1 (ICM Tier 2 project) updated central adaptive signal platform and expanded detection supporting 23 CFR 511 requirements.
3.2.3 - IDOT: Expand CCTVPlannedMedium termAdd 20 camera locations
3.2.4 - IDOT: Expand Traffic Detection to support 23 CFR 511 requirementsPlannedMedium termStandard detection as well as Bluetooth readers to provide speed and travel time data
3.2.5 - IDOT: Expand DMS (full-size)PlannedLong termNine new signs on Route 3 and other arterials approaching bridge complex plus upgrade existing 11 signs
3.3.1 - Metro: Integrate electronic payment across regionPlannedShort termCreate standardized payment for transit services across region
3.3.2 - Metro: Implementation of on-board Wifi (rail)PlannedShort termSupport traveler info, emergency data communications, customer convenience - includes router cost and 5-year wireless lease
3.3.3 - Metro: Implementation of on-board Wifi (bus)PlannedMedium termSupport traveler info, emergency data communications, customer convenience - includes router cost and 5-year wireless lease
3.4.1 - City of St Louis: TOC co-location with police operationsPlannedEarly startShared CCTV / control center, improved coordination
3.4.2 - City of St. Louis - Signal System UpgradePlannedShort termUpdate current platform
3.4.3 - City of St Louis: Signal Controller UpgradesPlannedShort termUpgrade remaining pretimed controllers to TS2 compliance and support of actuated and adaptive control
3.4.4 - CIty of St. Louis - Upgrade intersections to full actuationPlannedMedium termExpand detection at signalized intersections
3.4.5 - City of St Louis - CCTV ExpansionPlannedMedium termAdditional CCTV locations (intersections)
3.4.6 - City of St Louis - Fiber expansionPlannedMedium termEnables remaining isolated intersections / future camera locations to be connected via wireline network within city
3.4.7 - City of St Louis: Adaptive control in downtown St LouisPlannedMedium termImplementation of adaptive control strategies in downtown ST Louis, will involve installing additional detection as well as an adaptive control algorithm in coordination with the proposed upgraded signal system platform.
3.5.1, 3.5.2, 3.5.3, 3.5.7 - St Charles County: Expansion of surveillance and traffic data collectionPlannedEarly start to short term3.5.1 - PTZ cameras additional deployment 3.5.2 - Travel time detector deployment 3.5.3 - Count station deployment 3.5.7 - Probe data expansion
3.5.10 - St Charles County: Integrate state, county and Metro sensors to support expanded expanded TT DMSPlannedMedium termAdd detection,  other modifications. Create integrated system to provide traffic and transit information to St Charles county traveler, leveraging MoDOT and Metro data as well as ST Charles County data
3.5.14 - St Charles County: Weather data sharing with MoDOTPlannedMedium termRequires depoyment of 3.5.5 (RWIS). Provides sharing of MoDOT and County RWIS data to better track and respond to weather conditions.
3.5.4 and 3.5.11- St Charles County: Travel time DMS on key county arterialsPlannedEarly start3.5.4 - Initial deployment (Early start) 3.5.11 - Expanded deployment (Short term)
3.5.5 - St Charles County: Deployment of Weather StationsPlannedEarly startIncrease weather station coverage
3.5.6 - St Charles County: Emergency signal pre-emption deploymentPlannedShort termImplementation of signal pre-emption at critical interesections utilizing wireless vehicle to infrastructure communications.
3.5.8, 3.5.12, 3.5.13 - St Charles County fiber expansion projects (enables other activities)PlannedMedium termProject 3.5.8 consists of Phase III fiber expansion (48 strand). Project 3.5.12 includes a future fiber expansion (48 strand). Project 3.5.13 includes a future fiber expansion involving 12 strand fiber.
3.5.9 - St Charles County - Adaptive signal system upgradePlannedMedium termAdd detection and other enhancements to support adaptive operations at selected GGL intersections.
3.6.33 - St Louis County: Roadside weather monitoring pilotPlannedLong termImplement initial RWIS locations in County.
3.6.n: General Project Architecture for St Louis County ITS projectsPlannedShort to long termInclude fiber, CCTV, controller upgrades, detection systems. Multiple locations, ranging from short term ot long term implementatioins.