Integrated Corridor Management Systems Program Plan

1. Background

Traffic congestion is a serious and growing problem, particularly in major metropolitan areas. Much of the current congestion is concentrated in critical metropolitan corridors that link activity centers and carry high volumes of people and goods. Improving movement through these critical metropolitan corridors could yield significant benefits in terms of reduced travel time and delays and increased reliability and predictability of travel. The Integrated Corridor Management Systems (ICM) initiative is the only one of the nine Tier I Initiatives, started by the U.S. Department of Transportation's (USDOT) Intelligent Transportation Systems (ITS) program that directly addresses congestion.

The current state-of-the-practice is highly disaggregated. Freeway and arterial networks are often subject to unrestrained demands significantly greater than available capacity. Capacity is often reduced at bottleneck locations such as major interchanges and bridges. However, the ability to shift travel demands between networks and modes during traffic incidents, roadway work zone activity, adverse weather, or simply unusually large traffic demands is severely hampered by lack of information about current conditions (particularly on the arterial networks), and lack of standardized technical means for sharing that information. There is also a lack of institutional collaboration and coordination, and lack of integrated operational strategies and procedures that focus on maximizing the effectiveness of the entire corridor.

The state-of-the-practice is far from the state-of-the-art. ITS methods that are available to address corridor management are not widely deployed. To achieve effective corridor management, much work needs to be done on advancing the state-of-the-practice in institutional, operational, and technical integration.

2. Concept

Integrated Corridor Management is the coordination of individual network operations between parallel facilities that creates an interconnected system capable of cross network travel management. For the purposes of this initiative, a corridor is defined as a combination of discrete parallel surface transportation networks (e.g., freeway, arterial, transit networks) that link the same major origins and destinations. It is defined operationally rather than geographically or organizationally. The collection of networks and the collective impact of their operations will be the significant factors in determining the geographic and organizational boundaries in a corridor and will be affected by changes in network composition and operations.

The key to managing corridors effectively is achieving integration among the operations of different networks in the corridor. To date, efforts to reduce congestion have mainly focused on the optimization of individual networks. Each network is usually operated in isolation except for limited coordination at network junctions. This lack of coordinated operations between networks prevents effective use of a combination of these networks to address day-to-day congestion and congestion caused by work zones, incidents, weather, and special events. A coordinated effort between networks along a corridor can effectively manage the total capacity of a corridor in a way that will result in reduced congestion and increased trip reliability.

3. Program Vision

Metropolitan areas will realize significant improvements in the efficient movement of people and goods through aggressive and proactive integration and management of major transportation corridors. Integrated Corridor Management will result in a reduction in travel times, delays, fuel consumption, emissions, and incidents, and an increase in reliability and predictability of travel.

4. Program Goal

The goal of the Integrated Corridor Management Initiative is to provide the institutional guidance, operational capabilities, and ITS technology and technical methods needed for effective Integrated Corridor Management Systems.

5. Program PURPOSE

The initiative will demonstrate how operations strategies and ITS technologies can be used to efficiently and proactively manage the movement of people and goods in major transportation corridors through integration of the management of all the networks in a corridor. This initiative will develop a toolbox of operational policies, cross network operational strategies, integration requirements and methods, and analysis tools needed to implement effective Integrated Corridor Management Systems. A model deployment in a selected corridor will demonstrate how proven and emerging ITS technologies can be used to coordinate the operations between separate corridor networks to increase the effective use of the total capacity of the corridor.

6. Missing Integration

Deploying successful corridor management systems requires the understanding of institutional, operational and technical integration issues. It also requires the collaborative and coordinated efforts of multiple organizations in applying integrated operational strategies and technologies. Figure 1 shows the fundamental elements that need to be integrated for deploying corridor management systems.

Figure 1 High-Level Summary Diagram of the Program Plan

6.1 Institutional Integration

One of the chief obstacles to effective corridor management is the current institutional strategy and policy that allocates responsibility for corridor networks to different entities. The networks that serve a corridor are currently operated by separate jurisdictional entities. Typically, freeway networks are operated by a state transportation agency and enforcement is carried out by the state police. The arterial networks are operated by the various jurisdictions along the length of the corridor. Transportation management and enforcement duties at the arterial level are split between different jurisdictional units. Transit service in a corridor is typically provided by a regional authority, a jurisdictional-based entity, or some combination.

Freeway management entities, arterial management entities, and transit agencies in metropolitan areas have each implemented separate technology-based management systems that support their individual networks. Thus, each entity has its own management system that supports the distribution of responsibilities and control of the system within its network. In most cases, cross network management of different networks within a corridor is done manually. Although sometimes the entities themselves may want to collaborate, as is currently done by Houston's TransStar which co-locates the entities that control the various transportation networks, existing systems are typically not integrated such that the entities can distribute responsibilities and share control. Current management systems do not prohibit corridor management; however, the separate network-based systems do present institutional coordination challenges that need to be addressed.

This program will concentrate on how the integration of management systems can support the integrated operations of various organizations in a corridor. Different alternatives for shared operations management and the systems integration to support the operations management will be analyzed and documented. Guidance documents concerning the distribution of responsibilities and sharing of control between management systems to institutionally support integrated corridor operations will be developed and promulgated.

6.2 Operational Integration

Operationally, there is a lack of specific knowledge concerning how ITS technologies and strategies can be utilized to support effective coordinated corridor operations. Operational scenarios such as signal timing coordination in conjunction with ramp metering using NTCIP standards-conformant equipment need to be investigated. Other strategies that coordinate freeway, arterial, and transit operations need to be studied to identify what ITS technologies and strategies can be combined most effectively to improve corridor operations. Will the setting of a variable speed limit in conjunction with a ramp metering setting and signal timing plan on the adjacent arterials assist in mitigating the impact of a major corridor freeway incident? How will transit signal priority affect a signal/ramp meter pair? Where and how should coordinated managed lanes on freeways and arterials be implemented? How widely should HOT lanes be implemented to achieve the most efficient use of corridor capacity?

The limited state-of-the-practice concerning coordinated operations stems from a lack of detailed knowledge concerning operating strategies, and a lack of analytical capability to choose the best strategies for a particular corridor. The ITS technology and operational strategy building blocks for corridor management do exist. The results of coordinating these building blocks in a particular corridor need to be demonstrated and documented.

Operational integration is the foundation upon which institutional and technical integration must build. This program will identify and develop operational strategies by which individual ITS technologies such as ramp meters, advanced traffic control, variable speed signs, and parking notification can be operationally integrated at a corridor level. Analysis and evaluation tools will be developed to support strategy development and selection. Guidance will be provided to practitioners so that they can conduct a corridor resource and component inventory and use this information to identify what capabilities they have in a corridor and what capabilities are needed to implement various corridor operational approaches. Included in this area will be the development of specific corridor-based versions of FHWA Office of Operations' core programs such as the Traffic Incident Management Program. The analysis of corridor operational strategies will include the study of ITS supply and demand management practices and what can be done at the junctions of corridor networks. Junctions are the transfer points between networks, such as a freeway ramp.

6.3 Technical Integration

The third major obstacle to effective corridor capacity utilization is a lack of knowledge and capability concerning the technical integration of system operations at a corridor level. Arterial systems, freeway systems and transit systems have been deployed and are integrated within their individual networks; however, cross network coordination along a corridor has not been a priority. A lack of standards for sharing data and control has until recently been a major obstacle to effective technical integration.

The ITS standards and strategies needed for effective technical integration exist (or are in development and nearing completion), but have not been widely deployed. These ITS standards and strategies are key to effective operational and institutional integration. Without a means to effectively share data and control, operations cannot be integrated even if theinstitutional integration is robust.

In this area, the program will concentrate on the integration of systems, data, communications, and control at a corridor level. For example, ramp meters and adjacent traffic signals could be coordinated to adjust ramp meters and signals to facilitate demand. The linking of these systems will need to be location-specific and will require new integrated operations processing techniques and new data and communication interfaces. Generic system interfaces between corridor management components will be developed to support and advance implementation activities. Tools to assist in the identification and analysis of systems integration requirements will be developed.

7. Approach

This section describes the program approach. The objective of each program phase is given in the introduction section, followed by a discussion on the specific activities and deliverables for each phase in the remaining sections.

7.1 Introduction

Integrated Corridor Management will increase mobility and safety in major transportation corridors through institutional, operational and technical integration. It will result in reduced travel times, delays, fuel consumption, emissions, and incidents, and increased reliability and predictability of travel. This initiative will address institutional, operational and technical barriers to a successful corridor management.

This initiative will collaborate and coordinate with multiple organizations and program areas within the USDOT. A core team of DOT representatives will be formed to provide program management, technical guidance, and oversight throughout the program. The ICM core team will comprise:

• the ICM initiative team's Joint Program Office (JPO) Coordinator and Technical Lead, and
• partners from the Federal Highway Administration (FHWA) and Federal Transit Administration (FTA).

An advisory team will be formed with partners from federal agencies, including the Federal Highway Administration (FHWA) and Federal Transit Administration (FTA), and partners from the other related Tier I initiatives. The DOT ICM advisory team will provide input on the program approach.

The ICM initiative will identify, test, revise, and deploy appropriate technologies and techniques within the context of a Concept of Operations defined in partnership with a multimodal stakeholder working group. The initiative proposes a four-phase approach with two go/no-go decision points to achieve the intended program goals.

In the first phase, Foundational Research, a multimodal stakeholder working group will be formed, consisting of representatives from public and private sectors. The goal will be to assist the ICM core team in developing an understanding of the institutional, operational, and technical integration needs and issues of deploying an integrated corridor management system. The first ITS Management Council decision point for this initiative is at the end of this phase, when an assessment will be done to determine if sufficient integration issues have been identified that can be resolved.

In the second phase, Operations and Systems Development, alternative shared operations management schemes and cross network operations strategies will be developed. Analytical tools and methods will be modified or developed to enable the implementation and evaluation of integrated corridor management strategies. This phase also includes laboratory and limited field testing of component integration interfaces and component operations of an integrated corridor management system. The second ITS Management Council decision point is at the end of this phase. The results of this phase will be critical in determining if sufficient knowledge and resources have been identified and or developed to support an effective model deployment. Necessary standards to support the technical integration of corridor management data, communications, and control will be completed during Phase 2.

In the third phase, Model Deployment, the team will select candidate model deployment sites. Representatives from these sites will form the core of the stakeholder working group. The model deployment site will be chosen from the candidate sites. The model deployment will demonstrate the application of institutional, operational, and technical integration approaches in the field, and document implementation issues and operational benefits.

The final phase is Knowledge and Technology Transfer. Prior to the model deployment, technology transfer will be conducted to disseminate the knowledge gained from Phase 1 and Phase 2. The results of Phase 1 and Phase 2 will help candidate sites in developing their model deployment plans, and practitioners in implementing corridor management components. Towards the end of the model deployment effort, outreach activities will be conducted to provide guidance and transfer the tools and technologies needed to support successful integrated corridor management strategies.

Figure 2 shows a high-level summary diagram of the program plan.

7.2 Program Phases

The major activities, products, and expected outcome of each of the four program phases are discussed below. Figure 3 shows the road map for this initiative.

One of the key goals of this phase is to develop a Concept of Operations that has the support of the stakeholders. The Generic Concept of Operations will be used to define specific needs that will be addressed by this initiative. A contractor will be selected by the ICM core team to conduct the Phase 1 activities. Please see Figure 4 for a graphical illustration of the Phase 1 activities. Specific activities to be carried out under this phase include:

1.1 Establish and Engage Multimodal Stakeholder Working Group

A multimodal stakeholder working group consisting of approximately 15-20 members will be formed to provide the perspective of public sector operators and service providers. They will provide assistance to the ICM core team in providing feedback on the program plan and Generic Concept of Operations, identifying and assessing key knowledge gaps and requirements, and reviewing the planning and execution of outreach efforts. A series of meetings and workshops will be held to obtain input and direct participation in determining the direction of the program and context of program activities. Web-based collaboration will also be used to gather input.

The ICM core team will identify potential members from various associations and agencies, balancing modal representation, public and private sector, and bringing in the needed geographic representation. Membership will be solicited from TRB, APTA, AASHTO, ITE, ITS America, the Bus Rapid Transit Working Group, Freeway Operations Working Group, Arterial Operations Working Group, National Transit Institute, practitioners, researchers and experts from State DOTs, MPOs, 511 Policy Committee, and representatives from the private sector, such as equipment vendors and system integrators. After the first year, Candidate Model Deployment sites will be selected and representatives of those Candidate sites will form the core of the stakeholder working group for the subsequent phases.

Specific activities to be conducted by the stakeholder working group are: review of the draft program plan and the DOT's program approach, review of the Vision Statement including identification and refinement of definitions for a corridor and Integrated Corridor Management, and review of the products of the four program phases.

1.2 Develop Program Plan

The draft program plan describing the four-phased approach will be presented to the stakeholder working group at stakeholder meetings and workshops. Feedback will be solicited from stakeholders on the DOT's program approach. The program plan will be revised as necessary.

1.3 Develop Concept of Operations

The purpose of the Concept of Operations is to assist the ICM core team in building consensus among stakeholders on the goals, system components, functions, requirements, and capabilities of integrated corridor management. It will communicate overall stakeholder needs. This document will be a living document that will be used throughout the lifecycle of the ICM initiative.

Vision Statement

A Vision Statement will be developed giving an overview of the Integrated Corridor Management future concept. It will be presented to the stakeholders at the first stakeholder meeting. The meeting will provide a venue for stakeholders to offer feedback on the document, including the definition of a corridor, the definition of Integrated Corridor Management, and DOT's version of an Operations Scenario that illustrates what Integrated Corridor Management will be.

Detailed Generic Integrated Corridor Management (ICM) Concept of Operations

A detailed Generic Concept of Operations for Integrated Corridor Management will be developed. Information such as the ICM Vision Statement, an ICM Concept of Operations guidance outline, sample Concepts of Operation documents, the program plan, and initial definitions for corridor and Integrated Corridor Management will be used as a basis for the development. The Generic Integrated Corridor Management Concept of Operations will identify institutional, operational, and technical aspects of Integrated Corridor Management. It will communicate overall ICM needs and provide the basis for development of individual site-specific ICM Concepts of Operations. This document will be a living document that will be used throughout the lifecycle of the ICM initiative.

The final Generic ICM Concept of Operations document will be provided to the developers selected for model deployment, and shall be used as the starting point for developing site-specific ICM Concept of Operations for model deployment. Note that the Generic ICM Concept of Operations is intended to address a wide range of capabilities and functions, and facilitate discussion of the relative importance of different alternative capabilities and functions. It is intended to help stakeholder discussions about defining the corridor management problem and prioritizing solutions. Not every stakeholder or capability discussed in this Generic Concept of Operations should necessarily be included in the specific Concept of Operations for the model deployment.

Develop Alternative Definitions

Alternative definitions for corridor and Integrated Corridor Management will be developed to support the selection of agreed upon definitions. The definitions will be presented to the stakeholders at meetings and workshops to support selection and refinement. The definitions will be refined per stakeholder comments until definitions for corridor and Integrated Corridor Management are selected.

Develop Criteria for Delineating a Corridor

Criteria and a prototype procedure for delineating a corridor will be developed. This will include identifying what constitutes a corridor, the approach for identifying the boundaries of a corridor and the corresponding issues. Stakeholders will be asked to participate in the development of the criteria and delineation procedure.

Corridor Management vs. Regional Management

The purpose of this activity is to investigate and identify relationships between Corridor Management and Regional Management, and to understand how the two may be interrelated and may be operated together for optimal performance.

The goals and objectives of Corridor Management and Regional Management will be identified. Similarities, differences and linkages between the two will be identified with respect to implementation of various operational approaches and operational strategies including operations service programs such as Traffic Incident Management, Work Zone Management, Special Events Management, and Freight Management.

Corridor Management Institutional Strategies and Administration

Generic institutional strategies for corridor management for different corridor characteristics will be identified and analyzed. The stakeholders, including the decision makers, the operators of the system, and the corresponding participating organizations will be identified.

Administrative processes and requirements, including operational policies, procedures and constraints will be analyzed and documented.

Corridor Management Program Planning and Funding

Administrative challenges associated with planning deployment of corridor management systems will be identified. Alternative investment scenarios that will facilitate concept deployment and contribute to improved operations will be identified.

1.4 Document Successful Local Integration Efforts

Successful and promising current corridor management efforts will be identified to gather further information on best practices, needs and gaps in the state-of-the-practice.

A report will be prepared that will document the site visits and describe the corridor management improvements for each of the selected sites. The report will also include the RFI responses, the site selection process, the implementers involved, a description of the integration efforts in the current systems, the institutional, operational, and technical issues that were and were not addressed, lessons learned, and the stakeholder needs.

1.5 Identify Corridor Types and Operational Approaches

The purpose of this task is to gain an understanding of how to begin the process of determining what Integrated Corridor Management can be applied to various corridors in relation to generic corridor characteristics. Corridor types and operational approaches that practitioners can use to analyze their specific corridors and identify needs and possible ICM approaches to pursue will be developed.

Develop Operational Approaches

Operational approaches will be developed for each of the corridor types that would support effective ICM. Development of the operational approaches will include: (i) identifying operational strategies, including supply and demand strategies, which make up each operational approach; (ii) identifying for each network the cross network junctions, operational strategies, integration issues, and needs; and (iii) identifying combinations of ITS technologies, and devices needed to support the implementation of the approach.

A report documenting the corridor types and the corresponding operational approaches will support the development of the Phase 1 Development Feasibility report. The information will assist in identifying cross network integration issues that need to be addressed in Phase 2 of the program and developing alternate operational approaches for different corridor types.

1.6 Identify Operational Strategies and Analysis Tools

This activity serves to identify existing operational strategies for corridor management, and analysis tools that help assess the impacts of these operational strategies.

Identify Analysis Tools for Operational Strategies

For each identified operational strategy, this activity serves to: (i) identify modeling and analysis tools that support or evaluate the operational strategy; (ii) conduct a gap analysis of current modeling and analysis tools.

A report documenting the cross network operational strategies and analysis tools will be finalized. It will assist in identifying specific modeling and analysis tools that need to be developed in Phase 2 of the program. It will identify gaps in the current practice and ITS technologies that need to be addressed in Phase 2 to support the application of corridor management operational approaches and strategies. Findings from this activity will support the development of the Phase 1 Development Feasibility report.

1.7 Derive Requirements

The purpose of this activity is to derive the applicable requirements for Integrated Corridor Management. The derivation of these requirements will be done in coordination with the development of the Generic ICM Concept of Operations and be a part of that document.

Identify System-Level Components and Interfaces

System-level components will be identified for the proposed Integrated Corridor Management (ICM) system in the Generic ICM Concept of Operations document. System interfaces will be identified for data sharing and communication between system components.

Derive System Requirements

Requirements that meet the needs of stakeholders will be derived for the proposed system. The requirements document will: (i) identify the purpose and scope of them proposed system; (ii) modes of operation; (iii) system capabilities, conditions and constraints for various modes of operation; (iv) system-level components and system interfaces; (v) system performance measures (performance requirements); (vi) system interface requirements to facilitate integrated operational strategies, including device-to-device integrated operations.

The requirements document will assist in the model deployment effort in Phase 3 of the program.

1.8 Develop "Integrated Corridor Management Systems Development Feasibility: Issues and Opportunities" Report

The objectives of this activity are to conduct a feasibility analysis, develop a briefing that presents the preliminary results, and produce a technical report that supports a go/no go decision. The briefing and report will summarize the activities of the Phase 1 Foundational Research Studies and make a recommendation on the feasibility of the ICM development and continuation of the initiative. If the recommendation is for continuation of the initiative, this activity also serves to summarize the Phase 1 findings and make recommendations for the remaining program activities.

A feasibility analysis that addresses cost/benefit issues and current technology capabilities will be conducted. The report will address if the identified integration issues represent the stakeholder needs and if sufficient integration issues have been identified that can be resolved with the allocated program resources. The analysis will identify and make recommendations for Phase 2 activities, such as corridor management system integration needs, corridor delineation methodology, analysis tool modification, ITS technology development, testing, and standards application, and for the entire program.

A briefing will be developed that will assist the ICM team present the preliminary findings from Phase 1 ICM Development Feasibility Analysis. The briefing will include the key institutional, operational and technical integration issues that need to be addressed. It will address if these issues are workable within the allocated program resources.

The ICM Development Feasibility report will be developed that summarizes the results of the feasibility analysis and the integration issues identified as part of the analysis and via the other Phase 1 Foundational Research studies. The report will include the institutional, operational and technical integration barriers, gaps and requirements identified in the previous activities.

Products:

Key products of Phase 1 will be:

• Program Plan
• Vision Statement
• Generic ICM Concept of Operations
• Final Report on Local Corridor Management Efforts
• Final Report on Corridor Types and Corresponding Operational Approaches
• Final Report on Operational Strategies and Analysis Tools
• Briefing on Integrated Corridor Management Systems Development Feasibility: Issues and Opportunities
• Integrated Corridor Management Systems Development Feasibility: Issues and Opportunities Report

Outcome: Decision Point #1 Deployment Feasibility - The decision to continue with initiative will be made by the ITS Management Council based on the recommendations made in the Integrated Corridor Management Systems Development Feasibility: Issues and Opportunities briefing and report.

Phase 2: Operations and Systems Development

The goal of this phase is to complete the operations and systems development and application needed to have an effective model deployment, including limited tests of specific interfaces, tools, and operational strategies, based on the recommendations made in the "Integrated Corridor Management Systems Development Feasibility: Issues and Opportunities" report (Section 1.8). Figure 5 shows a graphical representation of Phase 2 activities. Specific activities to be carried out under this phase include:

2.1 Develop Alternative Shared Operations Management Schemes

The purpose of this activity is to build on existing practices identified in Section 1.5 "Identify Corridor Types and Operational Approaches" of Phase 1 to develop alternative approaches for institutions to distribute responsibilities and share control between the networks in a corridor. The objective here is to facilitate integrated operations of the different network management systems in a corridor.

Develop Operational Performance Goals

Low, medium and high operational performance goals will be identified for each corridor type identified in Section 1.5. The work done in Phase 1, particularly the activities listed in Sections 1.4 and 1.5 will serve as input to this activity.

Develop Operations Management Schemes

Based on the assessment done in Section 1.5 on existing operational approaches for managing a corridor, alternative schemes that facilitate the sharing of control and responsibilities between participating corridor organizations will be developed for each corridor type. For example, to deploy a corridor management system integrating ramp meters and adaptive signal control on adjacent arterials, alternative approaches will be developed that define junctions between the responsible agencies to allow the sharing of control. Different alternatives for management schemes that satisfy the low, medium and high operational performance goals will be identified and or developed for each corridor type and analyzed. The alternate approaches will address the cross network integration issues and needs identified in Section 1.5.

A report documenting these operational management schemes will assist in developing a guidance document in Phase 4 for deploying integrated corridor management systems.

2.2 Develop Cross Network Operational Strategies and Analysis Tools Modifications

The purpose of this activity is to develop operational strategies for integrated corridor management, and develop or modify modeling and analysis tools identified in Section 1.6 to help assess the impacts of the operational strategies. This activity is a continuation of the activities conducted under Section 1.6.

Develop Cross Network Operational Strategies

For each corridor type, previously identified in Section 1.5, cross network strategies by which individual ITS technologies can be operationally integrated at a corridor level will be developed. The focus will be to develop operational strategies that afford the capability of proactively controlling the networks in a corridor as a system, and influencing travel demand. This will contribute to a reduction in congestion and an increase in trip reliability.

Develop Analysis Tools for Operational Strategies

Modeling and analysis tools identified in the gap analysis in Section 1.6 will be developed or modified to assist in the analysis and development of cross network operational strategies. These tools will also help practitioners in evaluating alternative operational strategies and selecting appropriate strategies that meet their specific corridor needs.

During the field test it may be determined that there is a need for refining or developing modeling techniques, which may be carried out under this activity. Existing research and development efforts may also be leveraged. For example, a transit signal priority field test may require the enhancement or development of signal control strategies and technologies. These may be developed and tested under this initiative based on the needs assessment previously conducted by the FTA and the ITS JPO.

The operational strategies and the modeling and analysis tools developed or enhanced under this initiative will be available for use throughout this program and will be made available to practitioners.

2.3 Develop System Interfaces and Integrated Operations Processes

This activity involves developing system interfaces and integration processes needed to support the deployment of cross network operational strategies by integrating ITS technologies, including device-to-device integration. This activity will include analysis of appropriate standards to address the interfaces.

Develop Interfaces and Requirements Tool

A system analysis tool will be developed that will identify the necessary interfaces, processes and system requirements to allow integrated operations of the system components.

2.4 Laboratory and Limited Field Testing of Component Integration Interfaces and Operations

The proof of concept tests will deploy integrated systems and services, but on a smaller scale than that envisioned for a fully integrated corridor management system. The purpose of this activity is to identify any limitations or issues with the integrated operations of system components in proof-of-concept tests prior to a fully integrated deployment in the field. These tests, depending on schedule will, support the model deployment and/or other independent deployments over time.

Prioritize and Select Proof-of-Concept Tests

The ICM core team, with assistance from the stakeholder working group will prioritize and select the tests that need to be conducted in the laboratory and or in the field, as proof of concept for deploying integrated systems. Criteria for selection will include: (i) the ease and speed with which these tests can be executed; (ii) the stakeholder needs identified in the Concept of Operations document in Section 1.3; and (iii) findings from the Pre-Model Deployment Workshop that will be conducted in Phase 3.

Conduct Field Tests of Component Integration Interfaces and Operations

Field tests will be conducted to test the integrated operations of system components of a corridor management system on a limited scale. Some of these system components may already be operational in the field. The field tests will demonstrate if integrating the operations of these system components is feasible and effective. ITS standards will be selected for the field tests and applied.

The laboratory and field tests will demonstrate the effectiveness of ITS technologies, standards, and strategies that may be included in a full model deployment effort. The ITS standards selected and used for the tests may be revised at the end of this activity. The laboratory implementation procedures, the field tests, limitations and problems identified while conducting the tests and the applicable ITS standards will be documented.

The Concept of Operations document may be revised at the end of this activity based on the findings from these tests.

2.5 Develop "Integrated Corridor Management Systems: Model Deployment Feasibility Analysis" Report

The objective of this activity is to develop a report to support a go/no-go decision. The ICM core team will present Phase 2 findings to the ITS Management Council and make a recommendation on the continuation of this program.

The report will document if sufficient knowledge and technological capabilities have been developed or identified to support an effective model deployment effort. The report will include an inventory of the products developed or modified in Phase 2, including the operations management schemes, cross network operational strategies, analysis and modeling tools, and ITS standards needed to have a successful integration of corridor management systems. It will document the lessons learned from the laboratory and field tests.

At the end of Phase 2, the ICM core team will ask the ITS Management Council to make a decision on the feasibility of moving forward with the initiative to the deployment phase. The decision will be made based on the findings and recommendations presented in the final report.

Products: Major products of Phase 2 will be:

• Final Report on Alternative Shared Operations Management Schemes
• Final Report on Cross Network Operational Strategies and Analysis Tools
• Final Report on Laboratory and Field Tests
• Integrated Corridor Management Systems: Model Deployment Report
• System Interfaces and Requirements Tool

Outcome: Decision Point #2 - At the end of Phase 2, the ICM core team will ask the ITS Management Council to make a decision based on the Integrated Corridor Management Systems: Model Deployment Feasibility Analysis document to continue on to the model deployment phase.

Phase 3: Model Deployment

3.1 Define A Preliminary Integrated Corridor Management Model Deployment

The model deployment effort will be defined jointly with the candidate sites (Please see Section 3.4). The Preliminary Model Deployment will be used to start the discussion between the DOT and the candidate sites on what the actual model deployment needs to accomplish and what it needs to demonstrate.

A preliminary description of the model deployment will be developed based on the Generic Concept of Operations produced in Phase 1 (Section 1.3) and the ICM Development Feasibility Report (Section 1.8). The preliminary description will include the goals, objectives, scope of the effort, and the functions and features of the system. It will be presented at the pre-model deployment workshop (Section 3.2).

The ICM core team will then work with the candidate sites to revise the description of the model deployment effort, including the system components that need to be integrated, and their functions and features.

3.2 Pre-Model Deployment Workshop

A workshop will be held to make state and local agencies aware of the opportunity of having a model deployment effort in their corridors, and to encourage them to become candidate sites for model deployment (Section 3.3). The workshop will provide information on the goals and objectives of the Integrated Corridor Management Systems program, and the potential role that agencies could have in supporting advancements in Integrated Corridor Management. The workshop will explain the necessary procedures and requirements for becoming a candidate model deployment site or the model deployment site. Materials needed for the pre-model deployment workshop, including the Integrated Corridor Management Systems Primer will be developed in Section 4.1.

3.3 Model Deployment Candidate Sites Selection

Multiple candidate sites will be selected that have the potential of becoming a model deployment site.

Model Deployment Candidate Sites Solicitation

A solicitation for state and local agencies to become candidate sites for model deployment will be issued.

3.4 Candidate Sites Working Group

The ICM core team will invite representatives from the candidate sites to form the core of the stakeholder working group. This group will play a key role in the model deployment effort, as each of their sites has the potential of being chosen for model deployment. The ICM core team will work with the candidate sites to jointly develop the goals, objectives, and specific requirements of the model deployment. The candidate sites will work with the ICM core team to identify specific institutional, operational, and technical issues of each corridor.

3.5 Model Deployment Implementation

The purpose of the model deployment will be to apply ITS institutional, operational, and technical integration techniques to implement an Integrated Corridor Management System in a real-world setting. The site selected will provide a stage to demonstrate the implementation and operation of an integrated corridor management system, and to support an evaluation of the operational benefits.

The ICM core team will select the model deployment site from the candidate sites. Selection will be dependent on the site-specific requirements, and the technical and institutional capabilities that meet the needs of the proposed model deployment.

Model Deployment Implementation

The chosen site will modify the site-specific Concept of Operations as necessary. The operational strategies and tools testedin Phase 2 may be used for the model deployment. Appropriate standards will be selected for the model deployment effort to allow data sharing and communication between the model components. The ITS standards selected and used for the deployment effort may be revised at the end of this activity.

Model Deployment Operation

The selected ITS standards will be applied and the model deployment effort will conducted based on the site-specific Concept of Operations. The model deployment will demonstrate if integrating all components of the corridor management system is feasible and effective in meeting the goals of the deployment effort.

A report will be finalized documenting the model deployment implementation effort, including: the site-specific Concept of Operations and requirements, the approach, the operational management schemes and operational strategies, ITS standards and the lessons learned.

3.6 Model Deployment Evaluation

The purpose of this activity to evaluate the effectiveness of the model deployment effort in satisfying the goals of the ICM program and the model deployment effort.

Model Deployment Evaluation Procurement

The model deployment will be evaluated by an independent contractor. An RFP will be issued by the ICM core team to conduct the evaluation and document the evaluation results.

• The Model Deployment Experience: Implementation and Operation
• Integrated Corridor Management Systems: Model Deployment Evaluation

Outcome: This phase will have demonstrated the deployment of a successful integrated corridor management system.

Phase 4: Knowledge and Technology Transfer

In this phase, knowledge and technology transfer activities will be conducted to provide guidance and tools needed for widespread effective deployment of integrated corridor management systems. Specific activities to be carried out under this phase include (graphically illustrated in Figure 7):

4.1 Pre-Model Deployment Knowledge and Technology Transfer

The Integrated Corridor Management Systems Primer will be developed on integrated corridor management systems that provides information on the goals and objectives of the program and the institutional, operational and technical integration issues. Knowledge gained from Phase 1 and Phase 2, including the ITS standards, modeling and analysis tools, and operational approaches and strategies, will be disseminated to support candidate sites in developing site-specific requirements, and to support independent implementers. It should be noted that Phase 1 and Phase 2 products will have value independent of the subsequent model deployment effort.

4.2 Develop Integrated Corridor Management Knowledge and Technology Transfer Materials

Outreach materials will be developed to provide guidance on implementing integrated corridor management systems. Outreach materials will include brochures, guidance document, training courses, workshop materials, etc.

Develop Technology Transfer Materials for ICM Institutional Integration Approaches

Based on the knowledge gained from Phases 1 to 3, a training module will be developed on institutional integration issues and approaches needed to integrate management systems across corridor networks.

Develop Technology Transfer Materials for ICM Operational Integration Approaches

A training module will be developed on operational integration issues, and cross network operational approaches and strategies.

Develop Technology Transfer Materials for ICM Technical Integration Approaches

A technical integration training module will be developed that will identify technical integration issues, the modeling and analysis tools needed to assess the impacts of corridor management systems, the applicable ITS standards, combinations of ITS technologies, devices, and strategies that are compatible and feasible, and combinations of ITS technologies, devices, and strategies that may not be compatible or feasible.

Develop Integrated Corridor Management Implementation Guidance Document

Specific guidance on implementing corridor management systems will be developed. The document will address the institutional, operational, and technological gaps in the integration of corridor management operations. The document will provide guidance on how to select relevant management schemes, operational approaches, operational strategies, ITS standards and analysis tools for integrating corridor management systems.

4.3 Integrated Corridor Management Knowledge and Technology Transfer

Outreach will be conducted to provide guidance and the necessary tools and strategies to the community for integrating corridor management operations. The outreach will include knowledge and technology to support the implementation of corridor integration through integrated management systems, integrated operational strategies, cross network analysis capabilities, cross network systems, application of ITS standards, and training.

Corridor Management Conference

A post model deployment and evaluation conference will be held to share the model deployment experience, including the approach, the lessons learned, and the results of the deployment effort and the evaluation process. Brochures and other outreach materials promoting corridor management will be distributed.

Technology Transfer of ICM Institutional, Operational, and Technical Integration Approaches and Analysis Tools

The various institutional strategies identified or developed for integrating cross network operations in a corridor, the operational approaches and strategies necessary for integrated operations of a corridor, the modeling and analysis tools developed or modified under this initiative to analyze the operational strategies, and the ITS standards revised under this initiative will be freely disseminated.

Technology transfer will take place through training courses, peer-to-peer training, seminars, mobile workshops, brochures, guidance document, etc. Technology transfer materials developed in Section 4.2 may be tailored to address the needs of an agency interested in integrating corridor operations.

• Integrated Corridor Management Systems Primer
• Integrated Corridor Management Systems Implementation Guidance Document
• Institutional Integration Training Module
• Operational Integration Training Module
• Technical Integration Training Module
• ICM Training Courses

Outcome: This phase will result in an increased awareness among decision makers, system operators, and practitioners, of the benefits and issues of deploying an integrated corridor management system. It will provide practitioners with the knowledge, guidance, standards and analysis tools necessary to integrate corridor management systems successfully.

8. Projected Outcomes

This initiative will have demonstrated through a successful model deployment effort how mobility and safety can be increased in major transportation corridors by:

• successfully integrating ITS technologies efficiently and proactively,
• Improving use of real-time data sharing across all networks within the corridor, and
• optimizing the corridor as a system instead of a collection of individual networks.

It will have demonstrated the effective use of existing capacity within a corridor, leading to reduced congestion and more reliable travel times. It will promote the widespread use of integrated corridor management tools and strategies.

Figure 3 Integrated Corridor Management Road Map

Figure 4 Integrated Corridor Management Roadmap for Phase 1

Figure 5 Integrated Corridor Management Roadmap for Phase 2

Figure 6 Integrated Corridor Management Roadmap for Phase 3

Figure 7 Integrated Corridor Management Roadmap for Phase 4