In following the systems engineering approach and tailoring it to the needs of the project, the Connected Corridors team developed the following timeline to map the project's tasks:
Click image to enlarge
As the timeline illustrates, many of the tasks overlap or occur simultaneously. Some are relatively brief, while others continue throughout the life of the project. There is also considerable and ongoing interplay among the tasks. For example:
- Project Management touches every task in the project, as does Outreach and Communications with stakeholders, whose input and engagement are integral to moving the project forward.
- System design, development, integration, and deployment tasks are interdependent and proceed in parallel.
- System Evaluation begins with the design phase and continues for the rest of the project, to monitor and critically assess whether the objectives and user needs are being met.
Note: The timeline may be updated periodically in the course of the project.
The following table describes each task. A detailed breakdown of the specific activities and milestones for each task can be found in the Appendix to the Project Management Plan.
Project Initiation & Management
|General project management activities, such as staffing, budgeting, contracting issues|
|Outreach & Communications|
Engagement of corridor stakeholders, coordination of activities among stakeholders, release of information to the public, etc.
|Preliminary Concept Exploration & User Needs||Evaluation of current corridor operations (travel demand, observed speeds and travel times, status of detectors, etc.); identification of high-level user needs; and identification of operational gaps|
|Corridor Preparation||Activities to ensure that the monitoring and control systems currently in place along the corridor are operating adequately; management of equipment upgrade requests prior to ICM system deployment|
|Analysis, Modeling, and Simulation (AMS)||Use of analytical and simulation tools to evaluate the potential improvements that may be provided by various candidate strategies|
|Systems Engineering Management Plan (SEMP)||Identification of systems engineering activities that will guide the development of the proposed ICM system|
|Concept of Operations||Development of the concept of operations for the I-210 Pilot ICM system|
|System Requirements||Development of system requirements for the I-210 Pilot ICM system|
|Organizational Design||Identification of organizational changes that may be implemented to enhance corridor-based operations|
|Technical Design||Design of system architecture and technical components of the proposed I-210 Pilot ICM system|
|Component Development||Development of technical components of the I-210 Pilot ICM system|
|System Integration||Integration of developed technical components into a coherent integrated corridor-based traffic management system|
|Institutional Design and Operations||Design and implementation of institutional procedures and practices needed to operate the ICM system|
|System Deployment||Field deployment of the developed ICM system|
|Training||Training of operators and administrators of the proposed ICM system|
|Validation and Acceptance||Validation of the deployed ICM system and acceptance by corridor stakeholders|
|System Operations||Operations of the deployed ICM system|
|System Evaluation||Evaluation of the benefits provided by the deployed ICM system|
|Migration to Production||Transition of system operations from pilot system to standard production system|
|Lessons Learned||Identification and documentation of lessons learned and best practices|