System Requirement Specification for the I-394 Integrated Corridor Management System (ICMS)in Minneapolis, Minnesota
You will need the Adobe Reader to view the PDFs on this page.
PDF (3.4 MB)
March 31, 2008
FHWA-JPO-08-042
EDL Number 14422
Submitted to:
U.S. Department of Transportation
Federal Highway Administration
Federal Transit Administration
Research and Innovative Technology Administration
TABLE OF CONTENTS
Notice and Quality Assurance Statement
Technical Report Documentation Page
- Introduction and Document Overview
- General System Description
- System Content
- ICMS Business Model
- ICMS System Capabilities
- ICMS Data Hub
- ICMS Enhancements to the Mn/DOT Traffic Operations System
- ICMS Enhancements to the Mn/DOT Arterial Signals Group
- ICMS Enhancements to the Metro Transit Control Center System
- ICMS Enhancements to the SouthWest Transit Center
- ICMS Enhancements to the Plymouth Metrolink Dispatch
- ICMS Enhancements to the A,B,C Garages
- ICMS Enhancements to the Minnesota State Patrol Emergency Management
- ICMS Enhancements to the Hennepin County Emergency Management
- ICMS Enhancements to the City of Minneapolis Emergency Management
- ICMS Enhancements to the City of Minneapolis Arterial Signal Control
- ICMS Enhancements to the Hennepin County Arterial Signal Control
- System Modes and States
- Major System Conditions
- Major System Constraints
- User Characteristics
- Assumptions and Dependencies
- Operational Scenarios
- Performance Measures
- ICMS System of System Level Requirements
- ICMS Individual System Requirements
- ICMS Data Hub System Requirements
- ICMS Enhancements to Metro Transit Control Center (ICMS-MTCC) Functional Requirements
- ICMS Enhancements to Mn/DOT Traffic Operations (ICMS-Traffic Operations) Functional Requirements
- ICMS Enhancements to the A, B, and C (ICMS-ABC) Garage System Requirements.
- ICMS Enhancements to Mn/DOT Arterial Signals Group (ICMS-Mn/DOT-ASG) Functional Requirements
- ICMS Enhancements to Hennepin County Arterial Signals Group (ICMS-HENN-ASG) Functional Requirements
- ICMS Enhancements to City of Minneapolis Arterial Signals Group (ICMS-COM-ASG) Functional Requirements
- ICMS Enhancements to Minnesota State Patrol (ICMS-MSP-EMS) Functional Requirements
- ICMS Enhancements to City of Minneapolis Emergency Management System (ICMS-COM-EMS) Functional Requirements
- ICMS Enhancements to Hennepin County Emergency Management System (ICMS-HENN-EMS) Functional Requirements
- ICMS Enhancements to SouthWest Transit Dispatch Center (ICMS-SWT System)
- ICMS Enhancements to Plymouth Metrolink Transit Dispatch Center (ICMS-PM System)
- Hardware Requirements
- I-394 ICMS Interface Requirements
- Documentation and Training Requirements
- Definitions, Acronyms and Abbreviations
- References
TABLES
- Table 1: Summary of Corridor Problems and Needs
- Table 2: Existing Field Devices and Control Systems within the ICM Corridor and Ownership/Maintenance of the Systems
- Table 3: Future Enhancements to Existing Systems and Ownership
- Table 4: ICMS-Data Hub Data Sources and Data Consumers
- Table 5: I-394 ICM Preliminary Performance Measures
- Table 6: ICMS-System of Systems Level Requirements
- Table 7: ICMS-Data Hub Requirements
- Table 8: ICMS-MTCC Requirements
- Table 9: ICMS-Traffic Operations Requirements
- Table 10: ICMS-ABC Parking Garages Requirements
- Table 11: ICMS-Mn/DOT-ASG Requirements
- Table 12: ICMS-HENN-ASG Requirements
- Table 13: ICMS-COM-ASG Requirements
- Table 14: ICMS-MSP-EMS Requirements
- Table 15: ICMS-COM-EMS Requirements
- Table 16: ICMS-HENN-EMS Requirements
- Table 17: ICMS-SWT Requirements
- Table 18: ICMS-PM Requirements
- Table 19: ICMS Hardware Requirements
- Table 20: Documentation and Training Requirements
FIGURES
- Figure 1: Four Primary Components of the I-394 ICM Initiative
- Figure 2: Block Diagram of ICM Components
- Figure 3: Block Diagram of the ICMS Subsystems and Interconnects
- Figure 4: System Level Diagram of I-394 ICMS.
- Figure 5: Logical Architecture of the ICMS Data
- Figure 6: Logical Architecture of ICMS-Traffic Operations
- Figure 7: Logical Architecture of ICMS-Mn/DOT-ASG
- Figure 8: Logical Architecture of ICMS-MTCC
- Figure 9: Logical Architecture of ICMS-SWT
- Figure 10: Logical Architecture of ICMS-PM
- Figure 11: Logical Architecture of ICMS-ABC
- Figure 12: Logical Architecture of ICMS-MSP-EMS
- Figure 13: Logical Architecture of ICMS-HENN-EMS
- Figure 14: Logical Architecture of ICMS-COM-EMS
- Figure 15: Logical Architecture of ICMS-COM-ASG
- Figure 16: Logical Architecture of ICMS-HENN-ASG
- Figure 17: Scenario 1 Illustration
- Figure 18: Scenario 2 Illustration
- Figure 19: Scenario 3 Illustration
- Figure 20: Scenario 4 Illustration
- Figure 21: Scenario 5 Illustration
- Figure 22: ICMS-Data Hub Functions
- Figure 23: ICMS-MTCC Functions
- Figure 24: ICMS-Traffic Operations Functions.
- Figure 25: ICMS-ABC Parking Garages Functions.
- Figure 26: ICMS-Mn/DOT-ASG Functions
- Figure 27: ICMS-HENN-ASG Functions
- Figure 28: ICMS-COM-ASG Functions
- Figure 29: ICMS-MSP-EMS Functions
- Figure 30: ICMS-COM-EMS Functions
- Figure 31: ICMS-HENN-EMS Functions
- Figure 32: ICMS-SWT Functions
- Figure 33: ICMS-PM Functions
- Figure 34: ICMS Systems and Field Devices Requiring Hardware
All figures, maps, images, and photos are owned by the Minnesota Department of Transportation.