Department of Transportation: Federal Highway Administration

Integrated Corridor Management Initiative – ICMS Surveillance and Detection Needs Analysis for the Transit Data Gap

APPENDIX D – ICMS Surveillance and Detection Needs

The following table lists the abstracted needs identified for ICMS Surveillance and Detection in the ICMS technical integration task [29].

ID

Abstracted Need

Reference

Needs related to general ICM characteristics: SD-001

Surveillance and detection in an ICMS should cover all networks. Typical networks in an ICMS include freeways (including HOV, HOT, reversible, transit-only, and emergency vehicle-only lanes), arterial and other surface streets, and transit facilities (bus and rail); the junctions between them, including freeway on- and off-ramps; and associated facilities such as park-and-ride lots.

Implementation Guidance [32] p 13
Generic ConOps [31] p 16, 19, 35
ICM Technical Systems Integration Focus Group

Needs related to general ICM characteristics: SD-002

Surveillance and detection in an ICMS should cover all modes. Modes in an ICMS will include autos, buses, and rail transit.

Generic ConOps [31] p 19, 35

Needs related to general ICM characteristics: SD-003

Surveillance and detection in an ICMS should support integrated operational approaches by the agencies.

ICM Approaches and Strategy [20] p 4
ICMS Requirements [19] p 14

Needs related to general ICM characteristics: SD-004

Surveillance and detection in an ICMS should support real-time, automated data sharing between agencies.

Implementation Guidance [32] p 13, 27

Needs related to ICM approaches: SD-005

Surveillance and detection in an ICMS may support load balancing across the network to utilize any spare capacity.

Generic ConOps [31] p 16
Implementation Guidance [32] p 23

Needs related to ICM approaches: SD-006

Surveillance and detection in an ICMS may support real-time route shifts.

Generic ConOps [31] p 16
Implementation Guidance [32] p 3, 23
ICM Technical Systems Integration Focus Group
ICMS Requirements [19] p 14

Needs related to ICM approaches: SD-007

Surveillance and detection in an ICMS may support real-time mode shifts.

Generic ConOps [31] p 16
Implementation Guidance [32] p 3, 23
ICMS Requirements [19] p 14

Needs related to ICM strategies: SD-008

Surveillance and detection in an ICMS may support real-time travel demand management.

Implementation Guidance [32] p 3

Needs related to ICM strategies: SD-009

Surveillance and detection in an ICMS may support the provision of a network-wide, real-time holistic view of the corridor for the traveler, both pre-trip and en-route.

Generic ConOps [31] p 16, 19
Implementation Guidance [32] p 23

Needs related to ICM strategies: SD-010

Surveillance and detection in an ICMS may support network-wide, real-time traffic monitoring.

Implementation Guidance [32] p 3

Needs related to ICM strategies: SD-011

Surveillance and detection in an ICMS may support the real-time monitoring of recurring and non-recurring congestion.

Implementation Guidance [32] p 3
ICM Transit Focus Group Meeting
ICMS Requirements [19] p 14

Needs related to ICM strategies: SD-012

Surveillance and detection in an ICMS may support network-wide, real-time response to incidents, events, and emergencies, including those caused by weather conditions.

Generic ConOps [31] p 16, 19, 40, 43,55
Implementation Guidance [32] p 3
ICM Transit Focus Group Meeting;
ICMS Requirements [19] p 14

Needs related to ICM strategies: SD-013

Surveillance and detection in an ICMS should support efficient bus and rail transit operations.

Generic ConOps [31] p 16, 19
Implementation Guidance [32] p 23
ICM Transit Focus Group Meeting
ICM Approaches and Strategy [20] p 7

Needs related to ICM strategies: SD-014

Surveillance and detection in an ICMS should support the ease of use of bus and rail transit services, including associated facilities such as park-and-ride lots.

Implementation Guidance [32] p 23
Generic ConOps [31] p 19
ICM Approaches and Strategy [1] p 7

Needs related to ICM strategies: SD-015

Surveillance and detection in an ICMS may support network-wide, real-time transit system monitoring, including recognition of the different operating segments in the system, such as local versus express service.

Generic ConOps [31] p 19, 40
Implementation Guidance [32] p 3, 23
ICM Transit Focus Group Meeting
ICMS Requirements [19] p 14

Needs related to ICM strategies: SD-016

Surveillance and detection in an ICMS may support transit hub connection protection.

Generic ConOps [31] p 16
Implementation Guidance [32] p 23

Needs related to ICM strategies: SD-017

Surveillance and detection in an ICMS may support transit priority and emergency vehicle pre-emption at traffic signals.

Generic ConOps [31] p 16, 19
Implementation Guidance [32] p 23
ICMS Requirements [19] p 14

Needs related to ICM strategies: SD-018

Surveillance and detection in an ICMS may support network-wide, variable transportation pricing and payment strategies, including those affecting highways, transit services, and parking facilities.

Implementation Guidance [32] p 3, 23
ICMS Requirements [19] p 14

Needs related to ICM strategies: SD-019

Surveillance and detection in an ICMS may support variable lane operations, such as reversible lanes, contra-flow systems, transit-only and emergency vehicle-only lanes, and use of shoulders as travel lanes.

Implementation Guidance [32] p 23
ICMS Requirements [19] p 14

Needs related to ICM strategies: SD-020

Surveillance and detection in an ICMS may support the implementation of variable speed limits.

Implementation Guidance [32] p 23

Needs related to ICM strategies: SD-021

Surveillance and detection in an ICMS may support the implementation of variable truck restrictions.

Implementation Guidance [32] p 23
ICMS Requirements [19] p 14

Needs related to ICM strategies: SD-022

Surveillance and detection in an ICMS may support real-time special event management.

Generic ConOps [31] p 37

Needs related to ICM strategies: SD-023

Surveillance and detection in an ICMS may support the coordinated operation of ramp meters and arterial signal systems.

Implementation Guidance [32] p 23

Needs related to ICM strategies: SD-024

Surveillance and detection in an ICMS may support the coordinated operation of arterial signal systems and at-grade rail crossings.

Implementation Guidance [32] p 23

Needs related to ICM strategies: SD-025

Surveillance and detection in an ICMS may support the ability to determine in real-time when operating conditions on any part of the network return to normal.

ICMS Requirements [19] p 14

Needs related to ICM strategies: SD-026

Surveillance and detection in an ICMS should support the utilization of corridor assets by multiple agencies, including the resolution of conflicting requests from agencies.

Implementation Guidance [32] p 23, 32

Needs related to data: SD-027

Surveillance and detection in an ICMS should provide the data types required for the various ICM operational approaches.

ICM Approaches and Strategy [20] p 7
Implementation Guidance [32] p 17
Generic ConOps [31] p 55
ICMS Requirements [19] p 14, 18
ICM Technical Systems Integration Focus Group
ICM Approaches and Strategy [45] p 7

Needs related to data: SD-028

Surveillance and detection in an ICMS should support the provision of the required data in a consistent form to the agencies.

ICM Approaches and Strategy [20] p 7
Implementation Guidance [32] p 23
Generic ConOps [31] p 19

Needs related to data: SD-029

Surveillance and detection in an ICMS may support data archiving.

ICM Technical Systems Integration Focus Group

Needs related to data: SD-030

Surveillance and detection in an ICMS may support the provision of required data to analysis, modeling, and simulation (AMS) activities.

ICM Sample Data List p 4, 6
ICM AMS Methodology p 3-2, 3-4

Needs related to data: SD-031

Surveillance and detection in an ICMS may support the provision of required data for performance measurement.

Generic ConOps [31] p 16, 19, 72
Implementation Guidance [32] p 16, 25
Analysis Modeling & Simulation Focus Group
ICM AMS Methodology [1] p 3-4

previous | next
Office of Operations