Research Archive

Systems Engineering Management Plan

In this phase ICM stakeholders will identify the tasks that must be performed; estimate and assign needed resources; define task dependencies; identify task completion criteria; and develop the progress/performance measurement plan.

Title Abstract How to Use Useful to Date 
Generic ICM Concept of Operations This is a high-level Concept of Operations (Con Ops) for a "generic" 15 mile-corridor, consisting of freeway, arterial, bus and rail networks, and serving a central business district. The document's primary purpose is to provide an example of an ICM Con Ops that can be used by agency and network owners as the basis for developing their own corridor-specific and real-world Concept of Operations. Transportation professionals in the field seeking to implement ICM can use this document to develop their own concepts of operation for ICM. It can also help transportation professionals at all levels (Federal, State and local) understand all of the elements involved in ICM. It is intended to help practitioners flexibly design their own custom, tailored concept of operations based on their corridor's unique conditions and requirements.
  • All information about the generic corridor herein is purely fictional, fabricated based on the Project Team's collective experience, to provide a basis for describing the ICM operational concepts herein. The CONOPS for a real corridor will have more information.
  • The actual situation for most real-world corridors will undoubtedly be different from this generic corridor in terms of network types and other corridor characteristics, stakeholders, institutional and technical environments and the ICM concept and operational capabilities as discussed herein. Accordingly, users should tailor the information and/or sections within each chapter of this Generic CONOPS to develop their site-specific ICM CONOPS to meet any and all of their unique corridor conditions.
  • The generic corridor and the associated CONOPS does not attempt to be all-inclusive with respect to the types of networks that might be included within a corridor, the ICM stakeholders, and the operational approaches and strategies to be deployed.
Transportation agency and/or network owners

Transportation professionals at all levels (Federal, State and local)
Systems Engineering Management Plan - Dallas Integrated Corridor Management (ICM) Demonstration Project This Systems Engineering Management Plan is designed to assist the Dallas ICM Team by defining a procedural framework for management and control of the systems engineering components provided in the US-75 ICM Demonstration Project contract. It is a living document and will be reviewed at least twice in each year of the contract and updated as appropriate. Transportation professionals in the field seeking to implement ICM can use this document as a guide to develop their own Systems Engineering Management Plan for ICM. Transportation professionals interested to learn more about how to structure and manage an ICM project. 12/10
Integrated Corridor Management: Implementation Guide and Lessons Learned The purpose of this ICM Implementation Guide is to provide information to ICM “early adopters” on how to plan, develop, deploy, operate, and maintain an ICM system (ICMS). The Guide describes the phases in the ICMS life cycle and the associated deliverables for each phase, focusing on how the ICM Pioneer Sites addressed each phase. The guide also discusses typical issues (lessons learned) that arose during the U.S. DOT’s research initiative. Transportation professionals who will be involved in some stage of the ICM lifecycle can use this document to gain a high-level overview of the process steps needed to develop, implement and operate an ICM system. It can also help transportation professionals at all levels (Federal, State and local) who are generally interested to learn more about what ICM is and how to implement it. Transportation project managers who wish to implement an ICMS in their region 2/15