Within these pages, readers can find information related to the integration of data within ICM systems.
Born out of a USDOT pilot program in 2006, Integrated Corridor Management (ICM) is a methodology that transportation agencies have developed to address the movement of people, goods, and services through large metropolitan corridors with the integration of several parallel alternative travel modes – rail, bus, arterials, and freeways. The pilot program selected eight “Pioneer Sites” which developed aspects of ICM to model capabilities and explore challenges. Data integration is essential to the successful operation of an ICM, which involves sharing many different types and forms of data between multiple jurisdictions and agencies. Typical data sources for an ICM may include arterial, freeway real-time, and historical information from advanced traffic management systems (ATMS), regional traffic management systems, ramp metering plans, planned events, freeway incidents, CCTV imagery, message sign content, congestion, dynamic pricing, highway patrol data, and parking. Transit information may include incidents, AVL, schedule adherence, alarms, headways, and security.
As Pioneer Sites were being designed, refined, and implemented, there was significant work on the standardization of many typical sources of transportation datasets used in an ICM. However, system builders were still met with challenges as they integrated data. For example, according to an interview with a developer on the SANDAG ICM, the team utilized the Traffic Management Data Dictionary (TMDD) standards 1 but had to develop several customized add-ons that were not addressed by the standards. The Dallas ICM Demonstration Project on US-75 used center-to-center (C2C) and TMDD standards, but the C2C interface did not include lane by lane information, which required the development of a new interface. 2 This necessary customization strayed from the intent of standardization.
In some instances of the initial ICMs, the construct of the architecture and hubs for these new data had only been conceptualized. Coherence and coordination for updates of any regional ITS architecture in compliance with FHWA Rule 23 CFR 940.11 was common to all the pioneer sites. 3 In reference to the architecture, the ITS Data Distribution and ITS Data Warehouse are essential service packages.
By the time some of the pilots were underway, implementers articulated and described these architectures in greater detail only after they were built and refined. During implementation, unanticipated costs and complexities resulted from integrating the multitude and sheer quantity of data in these corridors. The C2C communications and required infrastructure, which utilized standards, ended up being less challenging than the data itself. However according to Integrated Corridor Management: Implementation Guide and Lessons Learned, there were different versions of C2C standards utilized in the pilot sites, which created system upgrades to address compatibility. 3 Successful data exchanges were established through institutional agreements and MOUs that were also in conformance with regional Transportation System Management and Operations (TSMO) plans.
- 1SANDAG. (2008). San Diego I-15 Integrated Corridor Management (ICM) System: Final I-15 ICM System Requirements. San Diego: San Diego Association of Governments. Retrieved June 4, 2020, from https://www.sandag.org/uploads/publicationid/publicationid_4472_23297.pdf
- 2Miller, K., Bouattoura, F., Macias, R., Poe, C., Le, M., & Plesko, T. (2015). Final report : Dallas Integrated Corridor Management (ICM) Demonstration Project. Washington, DC: U.S. Department of Transportation Intelligent Transportation Systems Joint Program Office. Retrieved June 4, 2020, from https://rosap.ntl.bts.gov/view/dot/3573
- 3 a b Blake, C., Hardesty, D., Hatcher, G., & Mercer, M. (2015). Integrated Corridor Management: Implementation Guide and Lessons Learned. Washington, DC: U.S. Department of Transportation Intelligent Transportation Systems Joint Program Office. Retrieved June 4, 2020, from https://connected-corridors.berkeley.edu/sites/default/files/fhwa_implementation_guide_v2.pdf