Integrated Corridor Management Initiative Dale Thompson Transportation Specialist Office of Operations R&D May 4, 2005

2 ITS Initiatives USDOT ITS program reoriented to focus on fewer, larger, higher-risk, high-payoff “major initiatives” Nine Major initiatives were approved by the Management Council Directly support USDOT’s goals of safety, mobility and global connectivity Integrated Corridor Management (ICM) is one of the major ITS initiatives started in 2004

3 Corridors Currently surface transportation systems are made up of several independent networks –Freeways, including managed lanes –Arterials –Bus Routes –Rail Transit Efforts to date to “reduce congestion” have focused on optimization of individual networks These adjacent network links overlay to form transportation corridors –Metropolitan areas contain several major corridors Corridors offer an opportunity to operate and optimize the entire corridor system as opposed to the individual networks

4 Integrated Corridor Management

5 Initial Definitions Corridor –A corridor is defined as a combination of discrete adjacent surface transportation networks (e.g., freeway, arterial, transit networks) that link the same major origins and destinations. Integrated Corridor Management (ICM) –Integrated corridor management is the coordination of individual network operations between adjacent facilities that creates an interconnected system capable of cross-network travel management.

6 Integrated Corridor Management Initiative Purpose –The initiative will demonstrate that ITS technologies can be used to efficiently and proactively manage the movement of people and goods in major transportation corridors by facilitating integration of the management of all the networks in a corridor. Goal –The goal of the Integrated Corridor Management Initiative is to provide the institutional guidance, operational capabilities, and ITS technical methods needed for effective Integrated Corridor Management Systems.

7 Integrated Corridor Management Initiative Vision –Improved mobility through integrated management of transportation assets – freeways, arterials, transit, managed lanes – in major transportation corridors in metropolitan areas Approach –Address Institutional, operational, and technical barriers to successful integrated corridor management –Demonstrate how mobility, safety and productivity can be increased in major corridors by Efficient, effective, proactive use of ITS technology Improved use of real-time data sharing Implementing demand management strategies

8 Missing Integration Institutional Integration –Lack of operational capability and technology that supports cross network distribution of responsibilities and sharing of control Operational Integration –Lack of integrated cross network operational strategies and analysis capabilities Technical Integration –Lack of cross network device-to-device data, communication, and procedure integration

9 ICM Program Plan

10 ICM Roadmap: Phase 1

11 Stakeholder Involvement Stakeholder Work Group –20 representatives Request For Information (RFI) –Gather information on corridor management activities –Study to identify needs –18 Responses Stakeholder Workshops –June 22 and 29 (one workshop, two locations) ITSA –Website –Conference Model Deployment Candidate Sites

12 Model Deployment Site Selection Approach Two-phased Approach: –Select candidate sites –Select model deployment site from candidate sites

13 Phase 1 – Foundational Research Team: Siemens ITS, TransCore, Dunn, SAIC, University of Virginia, Transystems, Howard / Stein-Hudson Major Activities –Program management & stakeholder meetings –Definitions, criteria for delineating a corridor, relationship to regional ITS –Generic Concept of Operations for ICMS –ICM system requirements –Document successful local integration efforts –Identify corridor types, operational approaches / strategies, analysis tools –Analyze associated operational, institutional, & technical integration issues –Develop ICM development feasibility report / briefing –Assist with MDI effort

14 Phase 1 Activities To Date Definitions –“corridor” –“integrated corridor management” Concepts for Delineating Corridor Boundaries Relationship Between Corridor & Regional Management Outline for Generic Concept of Operations Stakeholder Meetings Other Ongoing Activities –Review RFI responses, draft generic Con Ops, corridor types and strategies / operational approaches, simulation modeling

15 ICMS Concept of Operations “Concept of Operations” is Integral Part of Systems Engineering Process –High-level description of what the major system capabilities will be in ICM ICMS Con Ops a Formal Document Providing a User-Oriented Vision of ICM System –Can be understood by a wide variety of stakeholders (different operational & technical experience) –Engage stakeholders; soliciting input & feedback Generic ICMS Con Ops Will Serve as Template for Each MDI Candidate to Develop Their Corridor – Specific Con Ops

16 ICMS Concept of Operations Outline Based on FHWA Document “Developing and Using a Concept of Operations in Transportation Management Systems” –Overlap in content between sections 1 – Scope5 – Operational Needs 2 – References6 – System Overview 3 – User Oriented Operational Description 7 – Operational & Support Environment 4 – Relationship of ICMS to Regional ITS 8 – Operational Scenarios

17 Con Ops Operational Scenarios Normal operations (recurring congestion – Traffic and Transit) Scheduled events (special event / work zone) Evacuation Roadway, Transit, and Rail incidents Multiple simultaneous scenarios Others (as identified by stakeholders)

18 ICM Contacts and Information Mike Freitas, DOT JPO John Harding, FHWA Office of Operations Dale Thompson, FHWA Office of Operations R&D ICM Website: