| System Requirement Specification for the I-394 Integrated Corridor Management System (ICMS) in Minneapolis, Minnesota |
The stakeholder agencies that operate transportation systems along the I-394 Corridor on the west side of the Twin Cities Metropolitan Area (TCMA) have decided to implement and operate an Integrated Corridor Management (ICM) approach throughout the corridor. The I-394 corridor in Minneapolis, Minnesota is one of the eight ICM Pioneer Sites. Together, the stakeholder agencies have defined a set of User Needs that must be met within the corridor. This System Requirement Specification (SRS) defines the requirements for the Minneapolis I-394 Corridor Integrated Corridor Management System (ICMS). These requirements describe 'what' the ICMS will do to fulfill its role as part of the overall I-394 Integrated Corridor Management approach. |
Transportation professionals in the field involved in, or approaching, the requirements phase of the ICM lifecycle can use this document to help them define their System Requirement Specification (SRS) for their ICMS. |
Transportation infrastructure engineers, managers and operators interested to optimize their multimodal transportation networks through ICM. |
| High-Level Requirements for the US-75 Integrated Corridor in Dallas, Texas |
This document is intended as a listing and discussion of the high-level Requirements for the US-75 Integrated Corridor Management System (ICMS) in Dallas, Texas. This corridor is one of the eight ICM Pioneer Sites. This document describes what the Integrated Corridor Management (ICM) system is to do (the functional requirements), how well it is to perform (the performance requirements), and under what conditions (non-functional and performance requirements). This document sets the technical scope of the system to be built. It is the basis for verifying the system and sub-systems when delivered via the Verification Plan. The purpose of the US-75 ICMS is to implement a multi-modal operations decision support tool enabled by real-time data and live video pertaining to the operation of freeways, arterials, tollways, and public transit. The US-75 ICMS will be a multi-agency, de-centralized operation which will utilize a set of regional systems to integrate the operations of the corridor. |
Transportation professionals in the field involved in, or approaching, the requirements phase of the ICM lifecycle can use this document to help them define their System Requirement Specification (SRS) for their ICMS. |
Transportation infrastructure engineers, managers and operators interested to optimize their multimodal transportation networks through ICM. |
| System Requirement Specification for the I-270 Integrated Corridor Management System (ICMS) in Montgomery County, Maryland |
This document presents a revised System Requirements Specification (SyRS) for an Integrated Corridor Management (ICM) System along the Interstate-270 Corridor in Montgomery County, Maryland. This corridor is one of the eight ICM Pioneer Sites. It provides a description of the planned ICM System and delineated high-level and detailed requirements for the system. The I-270 ICMS will focus on traveler and operations management decision support by emphasizing corridor transportation systems management, traveler information dissemination, and systems evaluation by leveraging, and improving upon, current data collection, fusion capabilities, and corridor transportation system integration. |
Transportation professionals in the field involved in, or approaching, the requirements phase of the ICM lifecycle can use this document to help them define their System Requirement Specification (SRS) for their ICMS. |
Transportation infrastructure engineers, managers and operators interested to optimize their multimodal transportation networks through ICM. |
| System Requirement Specification for the IH-10 Integrated Corridor Management System (ICMS) in San Antonio, Texas |
This document captures the requirements of the San Antonio ICM System (ICMS) on the IH-10 Corridor. Requirements are primarily concerned with capturing "what" the system will accomplish as opposed to "how." The document is a valuable and essential component of the system engineering process as part of the ICM project to improve quality and efficiency in implementing the ICM corridor in the San Antonio region. The document captures the system functionality to communicate the information to stakeholders and vendors that would implement the ICMS. Through revisions, the Requirements Specification Document has provided a mechanism for obtaining feedback and refining the system functions. |
Transportation professionals in the field involved in, or approaching, the requirements phase of the ICM lifecycle can use this document to help them define their System Requirement Specification (SRS) for their ICMS. |
Transportation infrastructure engineers, managers and operators interested to optimize their multimodal transportation networks through ICM. |
| System Requirement Specification for the I-15 Integrated Corridor Management System (ICMS) in San Diego, California |
This document presents a System Requirements Specification for an Integrated Corridor Management System (ICMS) in the I-15 Corridor in San Diego, California. The ICMS will consist of two major subsystems: the existing Intermodal Transportation Management Subsystem and a new, as-yet-undeveloped subsystem to be known as the Decision Support Subsystem. In addition, the ICMS will include organic functions such as Collect and Process Data, Access/Store Historical Data, System Management, and Lifecycle Support. Several existing and planned regional systems will be connected with the ICMS – some of these will be upgrades to Intermodal Transportation Management System (IMTMS), some will be new systems. Section 2 provides an overview description of the I-15 ICMS , which includes the ICMS Context, ICMS Description, ICMS User Characteristics, System Constraints and Assumptions, and Dependencies. Section 3 includes a requirements framework, definitions of the I-15 ICMS components and key terms, action verb description, user needs developed in the I-15 Concept of Operations, an overview “mind map” of the IMCS requirements, and an indexed listing of the system requirements organized according to the ICMS's 17 functional areas. Appendix A provides Definitions, Acronyms, and Abbreviations Appendix B provides Requirements Management Metadata (for future requirements management activity). Appendix C includes U.S. Department of Transportation Comments on the Draft System Requirements Specification for the San Diego ICM Pioneer Site with SANDAG Responses. |
Transportation professionals in the field involved in, or approaching, the requirements phase of the ICM lifecycle can use this document to help them define their System Requirement Specification (SRS) for their ICMS. |
Transportation infrastructure engineers, managers and operators interested to optimize their multimodal transportation networks through ICM. |
| Develop Alternative Definitions for Corridor and Integrated Corridor Management (ICM) |
Discusses key attributes that were identified for possible inclusion in definitions used for the ICM initiative. It also presents final versions of these definitions, incorporating comments by FHWA and the ICM stakeholders. |
Transportation professionals in the field involved in some stage of the ICM lifecycle can use this document to help them define their ICM corridor, its boundaries, scope and reach. It offers various stakeholder and historical perspectives of how to define a corridor. |
Transportation infrastructure managers and operators |
