ITS - Intelligent Transportation Systems Report ITS Home Page

High-Level Requirements for the US-75 Integrated Corridor in Dallas, Texas

April 30, 2008
Award# DTFH-61-06-H-00040

7. Requirements

This section covers the functional, performance, interface, data, and hardware requirements. It also covers non-functional and enabling requirements, and constraints. For the requirements provided below, the requirement ID can be broken down as TYPE-SYSTEM-PARENT ID-SUB1 ID-SUB2 ID.

The TYPE of Requirements provided are:

The SUBSYSTEM for the Requirements provided are:

7.1. Assumptions and Dependencies

7.2. ICMS High-Level "Business" Requirements

The first step in the requirements process is the development of the overall ICMS "business" requirements. The ICM Steering Committee developed the User Needs, Goals, and Vision for the corridor; these were then translated into applicable use cases, and high-level requirements for the ICM System as a whole. These requirements are fulfilled by existing and new systems, and are the requirements for the stakeholders to operate the corridor in an integrated manner.

Table 7.2-1 Overall Integrated Corridor Management System Requirements
Requirement ID Requirement Description User Need Source Criticality Verification Method
empty cell Performance Requirements empty cell empty cell empty cell empty cell
P-ICMS-1-0-0

The ICMS shall be tested off-line (running with no failures) for 30 days during acceptance testing of the system

 7 empty cell H Observation
P-ICMS-1-1-0

The ICMS outage time during acceptance testing shall not exceed 5% of the time, not including routine maintenance of the system

 7 empty cell H Observation
P-ICMS-1-2-0

The time to recover the ICMS from an outage during acceptance testing shall not exceed 15 minutes

 7 empty cell H Observation
P-ICMS-2-0-0

The ICMS shall be available 98% of the time during normal operations, not including routine maintenance, and outages due to factors beyond the developers control

 7 empty cell H Observation
P-ICMS-3-0-0

The ICMS shall not be required to run continuously without routine maintenance

 7 empty cell H Observation
P-ICMS-3-1-0

The ICMS must be brought down and restarted once every thirty (30) days for routine maintenance

 7 empty cell H Observation
P-ICMS-4-0-0

The ICMS shall send pre-approved response plan requests to agencies within 2 minutes of selection of a pre-approved response plan

 1, 3, 9, 13 Section 4, 5 Con Ops H Testing
P-ICMS-5-0-0

The ICMS shall receive information on the clearance of any roadway incident within 2 minutes of closure within an Agency's systems

 1, 2, 3, 4, 5, 6, 8, 9,10, 12, 13 Section 4, 5 Con Ops H Testing
P-ICMS-6-0-0

The ICMS shall receive information on the clearance of any bus related incident within 2 minutes of closure within DART's systems

 1, 2, 3, 4, 5, 6, 8, 9, 10, 11, 12, 13 Section 4, 5 Con Ops H Testing
P-ICMS-7-0-0

The ICMS shall receive information on the clearance of any light rail related incident within 2 minutes of closure within DART's systems

 1, 2, 3, 4, 5, 6, 8, 9, 10, 11, 12, 13 Section 4, 5 Con Ops H Testing
P-ICMS-8-0-0

The ICMS shall send update on any posted messages on the dynamic message signs within 5 minutes of update within operating agency's systems

 1, 2, 3, 4, 5, 6, 8, 9,10, 12, 13 Section 4, 5 Con Ops M Testing
P-ICMS-9-0-0

The ICMS shall send update on dynamic message signs status within 5 minutes of change in status within Agency's systems

 1, 2, 3, 4, 5, 6, 8, 9,10, 12, 13 Section 4, 5 Con Ops M Testing
P-ICMS-10-0-0

The ICMS shall send information on the implemented signal timing plan within 5 minutes of change of timing plans within Agency's system

 1, 2, 3, 4, 5, 6, 8, 9,10, 12, 13 Section 4, 5 Con Ops M Testing
P-ICMS-11-0-0

The ICMS shall send freeway link speed observations at one minute resolution for the freeway links to the decision support system

 1, 2, 3, 4, 5, 6, 8, 9,10, 12, 13 Section 4, 5 Con Ops M Testing
P-ICMS-12-0-0

The ICMS shall send arterial link speeds at 30 seconds to one minute resolution for at least 10% of the arterial links to the decision support system.

 1, 2, 3, 4, 5, 6, 8, 9,10, 12, 13 Section 4, 5 Con Ops M Testing
P-ICMS-13-0-0

The ICMS shall send information on transit vehicle location at not more than 2 minute interval.

 1, 2, 3, 4, 5, 6, 8, 9,10, 12, 13 Section 4, 5 Con Ops M Testing
empty cell Security Requirements empty cell empty cell empty cell empty cell
S-ICMS-1-0-0

The ICMS shall require a login username and password

 7 empty cell H Testing
S-ICMS-1-1-0

The ICMS shall have multiple levels of users to include:

  1. Agency User
  2. ICM Coordinator
  3. Administrator
  4. Developer
 1 empty cell H Testing
S-ICMS-1-2-0

Login information and privileges will be stored in a centralized access control database

 1 empty cell M Testing
S-ICMS-1-3-0

The ICMS shall restrict a user account to 1 login instance.

 1 empty cell M Testing
S-ICMS-2-0-0

The ICMS shall include an interface to manage user accounts

 1 empty cell M Testing
S-ICMS-2-1-0

The ICMS shall include an interface to add user accounts

 1 empty cell M Testing
S-ICMS-2-2-0

The ICMS shall include an interface to modify user accounts

 1 empty cell M Testing
S-ICMS-2-3-0

The ICMS shall send an interface to delete user accounts

 1 empty cell M Testing
empty cell Hardware Requirements empty cell empty cell empty cell empty cell
H-ICMS-1-0-0

The ICMS shall consist of a:

  1. Database
  2. Decision Support Subsystem
  3. Communication connection to the Regional Center to Center system
  4. Evaluation Model subsystem
  5. Web subsystem
 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,12,13, 14 Section 4, 5 Con Ops H Testing
H-ICMS-1-1-0

The ICMS shall include a database server for storage of data

 3, 4, 5, 6, 8, 9, 10, 11,12,13, 14 Section 4, 5 Con Ops H Inspection
H-ICMS-1-2-0

The ICMS shall include an application server(s) for the Decision Support Subsystem

 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,12,13, 14 Section 4, 5 Con Ops H Inspection
H-ICMS-1-3-0

The ICMS shall include an application server(s) for the Evaluation Model Subsystem

 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,12,13, 14 Section 4, 5 Con Ops H Inspection
H-ICMS-1-4-0

The ICMS shall include an web server(s) for the Web Subsystem

 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,12,13, 14 Section 4, 5 Con Ops H Inspection
H-ICMS-2-0-0

The ICMS shall include network equipment needed to connect to the regional center to center system

 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,12,13, 14 Section 4, 5 Con Ops H Inspection
C-ICMS-1-0-0

The ICMS network equipment shall meet the requirements of the regional center to center system network

 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,12,13, 15 Section 4, 5 Con Ops H Inspection
empty cell Data - Receiving empty cell empty cell empty cell empty cell
D-ICMS-1-0-0

The ICMS shall receive the coordinates of intersections in the corridor from the regional data warehouse via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD

 1, 5, 6, 7, 8, 9, 12, 13 Section 4, 5 Con Ops H Testing
D-ICMS-2-0-0

The ICMS shall receive a list of links in the corridor from the regional data warehouse via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD

 1, 2, 3, 4, 8 Section 4, 5 Con Ops H Testing
D-ICMS-3-0-0

The ICMS shall receive information from the regional data warehouse on each link via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD including:

  1. facility type
  2. number of lanes
  3. capacity per lane
  4. speed limit
  5. average jam density
  6. Link owner (s)
 1, 5, 6, 7, 8, 9, 12, 13 Section 4, 5 Con Ops H Testing
D-ICMS-4-0-0

The ICMS shall receive toll data for toll roads in the corridor from the regional data warehouse via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD

 1, 5, 6, 7, 8, 9, 12, 13 Section 4, 5 Con Ops H Testing
D-ICMS-5-0-0

The ICMS shall receive information from the regional data warehouse for each signalized intersection in the corridor via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD to include:

  1. Control type
  2. Timing Plan
 1, 5, 6, 7, 8, 9, 12, 13 Section 4, 5 Con Ops H Testing
D-ICMS-6-0-0

The ICMS shall receive state information for detectors in the corridor via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD within 2 minutes of any state change in the agency's systems

 1, 5, 6, 7, 8, 9, 12, 13 Section 4, 5 Con Ops H Testing
D-ICMS-7-0-0

The ICMS shall receive location of dynamic message signs in the corridor from the regional data warehouse via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD

 1, 5, 6, 7, 8, 9, 12, 13 Section 4, 5 Con Ops H Testing
D-ICMS-8-0-0

The ICMS shall receive information on the route structure of bus routes in the corridor from the regional data warehouse via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD

 1, 5, 6, 7, 8, 9, 11, 12, 13 Section 4, 5 Con Ops H Testing
D-ICMS-9-0-0

The ICMS shall receive information on the route structure of light rail lines in the corridor from the regional data warehouse via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD

 1, 5, 6, 7, 8, 9, 11, 12, 13 Section 4, 5 Con Ops H Testing
D-ICMS-10-0-0

The ICMS shall receive time table for bus routes in the corridor from the regional data warehouse via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD

 1, 5, 6, 7, 8, 9, 11, 12, 13 Section 4, 5 Con Ops H Testing
D-ICMS-11-0-0

The ICMS shall receive time table for all light rail lines in the corridor from the regional data warehouse via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD

 1, 5, 6, 7, 8, 9, 11, 12, 13 Section 4, 5 Con Ops H Testing
D-ICMS-12-0-0

The ICMS shall receive fare structure data for bus routes in the corridor from the regional data warehouse via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD

 1, 5, 6, 7, 8, 9, 11, 12, 13 Section 4, 5 Con Ops H Testing
D-ICMS-13-0-0

The ICMS shall receive fare structure data for light rail lines in the corridor from the regional data warehouse via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD

 1, 5, 6, 7, 8, 9, 11, 12, 13 Section 4, 5 Con Ops H Testing
D-ICMS-14-0-0

The ICMS shall receive the location of bus stops in the corridor from the regional data warehouse via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD

 1, 5, 6, 7, 8, 9, 11, 12, 13 Section 4, 5 Con Ops H Testing
D-ICMS-15-0-0

The ICMS shall receive the location of light rail stations in the corridor from the regional data warehouse via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD

 1, 5, 6, 7, 8, 9, 11, 12, 13 Section 4, 5 Con Ops H Testing
D-ICMS-16-0-0

The ICMS shall receive information on allowed/prohibited turning movements at each intersection from the regional data warehouse via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD

 1, 5, 6, 7, 8, 9, 12, 13 Section 4, 5 Con Ops H Testing
D-ICMS-17-0-0

The ICMS shall receive the location of park-and-ride facilities in the corridor from the regional data warehouse via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD

 1, 5, 6, 7, 8, 9, 12, 13 Section 4, 5 Con Ops H Testing
D-ICMS-18-0-0

The ICMS shall receive the capacity of park-and-ride facilities in the corridor from the regional data warehouse via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD

 1, 5, 6, 7, 8, 9, 11, 12, 13 Section 4, 5 Con Ops H Testing
D-ICMS-19-0-0

The ICMS shall receive the location of agency managed parking lots in the corridor from the regional data warehouse via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD

 1, 5, 6, 7, 8, 9, 11, 12, 13 Section 4, 5 Con Ops H Testing
D-ICMS-20-0-0

The ICMS shall receive the capacity of agency managed parking lots in the corridor from the regional data warehouse via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD

 1, 5, 6, 7, 8, 9, 11, 12, 13 Section 4, 5 Con Ops H Testing
D-ICMS-21-0-0

The ICMS shall receive the location of approved 3rd Party parking lots in the corridor via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD

 1, 5, 6, 7, 8, 9, 11, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-22-0-0

The ICMS shall receive the capacity of approved 3rd Party parking lots in the corridor via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD

 1, 5, 6, 7, 8, 9, 11, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-23-0-0

The ICMS shall receive information on roadway incidents in the corridor via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD describing:

  1. Location
  2. Time of Day
  3. Number of Lanes affected
  4. Estimated Duration
 1, 2, 3, 4, 5, 6, 7, 8, 9, 12, 13 Section 4, 5 Con Ops H Testing
D-ICMS-24-0-0

The ICMS shall receive information on bus related incidents in the corridor via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD describing:

  1. Location
  2. Time of Day
  3. Bus Route
  4. Estimated Duration
 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 12, 13 Section 4, 5 Con Ops H Testing
D-ICMS-25-0-0

The ICMS shall receive information on light rail related incidents in the corridor via the regional data warehouse via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD describing:

  1. Location
  2. Time of Day
  3. Light Rail Line
  4. Estimated Duration
 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 12, 13 Section 4, 5 Con Ops H Testing
empty cell Data - Storage empty cell empty cell empty cell empty cell
D-ICMS-26-0-0

The ICMS shall store data received from the corridor systems

 1, 8 Section 4, 5 Con Ops H Testing
D-ICMS-27-0-0

The ICMS database subsystem shall store:

  1. Historical information needed for the modeling and decision support subsystems
  2. Current day activities within the corridor
  3. Pre-approved response plans
  4. Contact Lists
 5, 8, 9, 10, 12 Section 4, 5 Con Ops H Testing
D-ICMS-28-0-0

The ICMS shall store state information for detectors in the corridor to include:

  1. State
  2. Time of Day
  3. ocation
  4. Detector ID (if applicable)
 5, 8, 9, 10, 12 Section 4, 5 Con Ops H Testing
D-ICMS-29-0-0

The ICMS shall store information on roadway incidents in the corridor describing:

  1. Location
  2. Time of Day
  3. Number of Lanes affected
  4. Estimated Duration
  5. Incident ID
  6. Lead Agency
 5, 8, 9, 10, 12 Section 4, 5 Con Ops H Testing
D-ICMS-30-0-0

The ICMS shall store information on bus related incidents in the corridor describing:

  1. Location
  2. Time of Day
  3. Bus Route
  4. Estimated Duration
 5, 8, 9, 10, 11, 12 Section 4, 5 Con Ops H Testing
D-ICMS-31-0-0

The ICMS shall store information on light rail related incidents in the corridor describing:

  1. Location
  2. Time of Day
  3. Light Rail Line
  4. Estimated Duration
 5, 8, 9, 10, 11, 12 Section 4, 5 Con Ops H Testing
empty cell Data - Sending empty cell empty cell empty cell empty cell
D-ICMS-32-0-0

The ICMS shall send new data stored in the database it received during each day to the regional data warehouse utilizing the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD

 8 Section 4, 5 Con Ops H Testing
D-ICMS-33-0-0

The ICMS shall send toll data for toll roads in the corridor to the decision support subsystem

 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-34-0-0

The ICMS shall send the coordinates of intersections in the corridor to the decision support subsystem to include:

  1. number of lanes each direction
  2. Signalized/ unsignalized
  3. Links connected to intersection
  4. allowed turning movements
 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-35-0-0

The ICMS shall send a list of links in the corridor to the decision support subsystem

 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-36-0-0

The ICMS shall send information to the decision support subsystem on each link including:

  1. facility type
  2. number of lanes
  3. capacity per lane
  4. speed limit
  5. average jam density
 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-37-0-0

The ICMS shall send information to the decision support subsystem for each signalized intersection to include:

  1. Control type
  2. Timing Plan
 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-38-0-0

The ICMS shall send state information for detectors in the corridor to the decision support subsystem within 30 seconds of receipt of a state change

 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-39-0-0

The ICMS shall send location of dynamic message signs in the corridor to the decision support subsystem

 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-40-0-0

The ICMS shall send information on allowed/prohibited turning movements at each intersection to the decision support subsystem

 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-41-0-0

The ICMS shall send information on route structure bus routes in the corridor to the decision support subsystem

 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-42-0-0

The ICMS shall send information on route structure light rail lines in the corridor to the decision support subsystem

 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-43-0-0

The ICMS shall send time table for bus routes in the corridor to the decision support subsystem

 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-44-0-0

The ICMS shall send time table for all light rail lines in the corridor to the decision support subsystem

 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-45-0-0

The ICMS shall send fare structure data for bus routes in the corridor to the decision support subsystem

 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-46-0-0

The ICMS shall send fare structure data for light rail lines in the corridor to the decision support subsystem

 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-47-0-0

The ICMS shall send the location of bus stops in the corridor to the decision support subsystem

 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-48-0-0

The ICMS shall send the location of light rail stations in the corridor to the decision support subsystem

 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-49-0-0

The ICMS shall send the location of park-and-ride facilities in the corridor to the decision support subsystem

 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-50-0-0

The ICMS shall send the capacity of park-and-ride facilities in the corridor to the decision support subsystem

 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-51-0-0

The ICMS shall send the location of agency managed parking lots in the corridor to the decision support subsystem

 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-52-0-0

The ICMS shall send the capacity of agency managed parking lots in the corridor to the decision support subsystem

 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-53-0-0

The ICMS shall send the location of approved 3rd Party parking lots in the corridor to the decision support subsystem

 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-54-0-0

The ICMS shall send the capacity of approved 3rd Party parking lots in the corridor to the decision support subsystem

 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-55-0-0

The ICMS shall send information on roadway incidents in the corridor to the decision support subsystem describing:

  1. Location
  2. Time of Day
  3. Number of Lanes affected
  4. Estimated Duration
  5. Incident ID
 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-56-0-0

The ICMS shall send stored information on roadway incidents in the corridor that occurred that day to the regional data warehouse via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD describing:

  1. Location
  2. Start Time
  3. End Time
  4. Date of Incident
  5. Number of Lanes affected
  6. Duration
  7. Incident ID
  8. Lead Agency
 1, 2, 3, 4, 8, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-57-0-0

The ICMS shall send information on bus related incidents in the corridor to the decision support subsystem describing:

  1. Location
  2. Time of Day
  3. Bus Route
  4. Estimated Duration
 1, 2, 3, 4, 8, 11, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-58-0-0

The ICMS shall send stored information on bus incidents in the corridor that occurred that day to the regional data warehouse via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD describing:

  1. Location
  2. Start Time
  3. End Time
  4. Date of incident
  5. Bus Route
  6. Duration
 1, 2, 3, 4, 8, 11, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-59-0-0

The ICMS shall send information on light rail related incidents in the corridor to the decision support subsystem describing:

  1. Location
  2. Time of Day
  3. Light Rail Line
  4. Estimated Duration
 1, 2, 3, 4, 8, 11, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-60-0-0

The ICMS shall send stored information on light rail incidents in the corridor that occurred that day to the regional data warehouse via the regional data warehouse via the regional center to center system in a format to meet the requirements of the Regional Center to Center ICD describing:

  1. Location
  2. Start Time
  3. End Time
  4. Date of incident
  5. Light Rail Line
  6. Duration
 1, 2, 3, 4, 8, 11, 12, 13, 14 Section 4, 5 Con Ops H Testing
D-ICMS-61-0-0

The ICMS shall send information on light rail related incidents in the corridor to the decision support subsystem describing:

  1. Location
  2. Time of Day
  3. Light Rail Line
  4. Estimated Duration
 1, 2, 3, 4, 8, 11, 12, 13, 14 Section 4, 5 Con Ops H Testing
empty cell Data - Processing empty cell empty cell empty cell empty cell
F-ICMS-1-0-0

The ICMS shall determine a recommended response plan based on network conditions within the corridor

 3, 4, 5, 6, 8, 10, 13, 14 Section 4, 5 Con Ops H Testing
F-ICMS-2-0-0

The ICMS shall create an Incident ID associated with each unique incident it receives from the corridor agencies

 3, 4, 5, 6, 8, 10, 13, 14 Section 4, 5 Con Ops H Testing
F-ICMS-3-0-0

The ICMS shall send the information necessary to determine a pre-approved response plan to the decision support subsystem as defined by the requirements of the decision support system

 3, 4, 5, 6, 8, 10, 13, 14 Section 4, 5 Con Ops H Testing
empty cell Interface Requirements/ Constraints empty cell empty cell empty cell empty cell
I-ICMS-1-0-0

The ICMS shall interface to the regional center to center system

 1 Section 4, 5 Con Ops H empty cell
I-ICMS-2-0-0

The ICMS shall interface to the regional data and video sharing system

 1 Section 4, 5 Con Ops H empty cell
C-ICMS-1-0-0

The ICMS shall comply with the Regional Center to Center ICD for data exchange between the systems

 1 Section 4, 5 Con Ops H empty cell
C-ICMS-2-0-0

The ICMS shall comply with the Regional Data and Video Sharing (RDVS) system ICD for video exchanged between the systems

 1 Section 4, 5 Con Ops H empty cell

7.3. Subsystem Technical Requirements

For each of the ICM subsystems, requirements were developed to provide high-level functions, data, interfaces, and performance requirements to complete the ICMS. All of these subsystems are a part of the overall ICM System.

Table 7.3-1 Decision Support Subsystem Requirements
Requirement ID Requirement Description User Need Source Criticality Verification Method
C-DSS-1-0-0 The DSS shall utilize existing data from the regional data warehouse 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-1-0-0 The DSS shall receive the coordinates of all intersections in the corridor. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-2-0-0 The DSS shall receive a list of all links in the corridor 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-3-0-0 The DSS shall receive information on each link including:
  1. facility type
  2. number of lanes
  3. capacity per lane
  4. speed limit
  5. average jam density. (jam density is defined as the maximum number of vehicles per unit length of the highway link)
 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-4-0-0 The DSS shall receive toll data for all toll roads in the corridor 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-5-0-0 The DSS shall receive information on the control type and associated timing plan at each signalized intersection. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-6-0-0 The DSS shall receive information on each active (not marked as out-of-order or in-maintenance) detectors in the network. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-7-0-0 The DSS shall receive location of active (not marked as out-of-order or in-maintenance) dynamic message signs in the network. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-8-0-0 The DSS shall receive information on allowed/prohibited turning movements at each intersection. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-9-0-0 The DSS shall receive information on route structure of all bus and train lines in the network. The route is described in terms of a list of intersections and roadway links. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-10-0-0 The DSS shall receive time table for all bus and train lines in the network. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-11-0-0 The DSS shall receive fare structure data for all bus and train lines in the network. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-12-0-0 The DSS shall receive the location of all bus stops in the network. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-13-0-0 The DSS shall receive the location of all train stations. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-14-0-0 The DSS shall receive the location of all park-and-ride facilities in the network. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-15-0-0 The DSS shall receive the capacity of all park-and-ride facilities in the network. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-16-0-0 The DSS shall receive data from the regional center to center network within 2 minutes of a change in data. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-16-1-0 The DSS shall receive information on all roadway incidents in the corridor within 2 minutes of verification in controlling agency's systems describing:
  1. Location
  2. Time of Day
  3. Number of Lanes affected
  4. Estimated Duration
 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-16-2-0 The DSS shall receive information on all bus related incidents in the corridor within 2 minutes of verification within DART's systems describing:
  1. Location
  2. Time of Day
  3. Bus Route
  4. Estimated Duration
 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-16-3-0 The DSS shall receive information on all train related incidents in the corridor within 2 minutes of verification within DART's systems describing
  1. Location
  2. Time of Day
  3. Route
  4. Direction of Travel
  5. Estimated Duration
 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-16-4-0 The DSS shall receive information on the clearance of all roadway incident within 2 minutes of closure within agency's systems 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-16-5-0 The DSS shall receive information on the clearance of all bus related incident within 2 minutes of closure within DART's systems 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-16-6-0 The DSS shall receive information on the clearance of all train related incident within 2 minutes of closure within DART's systems 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-16-7-0 The DSS shall receive updates on all posted messages on the dynamic message signs within 2 minutes of update 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-16-8-0 The DSS shall receive update on dynamic message signs status within 2 minutes of change in status 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-16-9-0 The DSS shall receive information on the implemented signal timing plan within 2 minutes of signal timing plan change 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-16-10-0 The DSS shall receive update on traffic signal status within 2 minutes of status change 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-16-11-0 The DSS shall receive real-time link speed observations at 30 seconds to one minute resolution for at least 20% of the freeway links. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-16-12-0 The DSS shall receive real-time observations at 30 seconds to one minute resolution for at least 10% of the arterial links. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
D-DSS-16-13-0 The DSS shall receive real-time information on transit vehicle location at not more than 2 minute interval. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-1-0-0 The DSS shall provide real-time estimation of the intermodal network conditions at 30 seconds interval. Elements of the intermodal network include freeways, HOV lanes, arterials, bus lines, light rail lines, and park-and-ride facilities. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-2-0-0 The DSS shall provide consistency with the real-world conditions for all travel modes and facilities.
  1. The system's estimation error of the traffic speed, density and volume on every highway link in the network should not exceed 15% (plus or minus).
  2. The system's estimation error of the location of every transit vehicle in the network should not exceed 10% (plus or minus).
  3. The system's estimation error of the occupancy of every park-and-ride facility in the network should not exceed 20% (plus or minus).
 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-3-0-0 The DSS shall provide short term prediction of the intermodal network conditions for one hour horizon. Elements of the intermodal network include freeways, HOV lanes, arterials, bus lines, light rail lines, and park-and-ride facilities. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-4-0-0 Predicting the network future conditions (travel times and traffic density on every link) requires predicting the travel demand between every origin destination pairs for the prediction horizon which is one hour. The DSS shall provide prediction of the time-dependent origin-destination network demand at 5 to 10 minutes resolution. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-5-0-0 The DSS shall provide the capability to evaluate all user-specified (predefined) corridor management strategies. These strategies are
  1. pre-trip and en-route traveler information provision
  2. congestion pricing
  3. signal timing modification
  4. transit service modification
  5. transit signal priority
  6. parking management and pricing
  7. combinations of the above
 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-6-0-0 The DSS shall provide the capability to develop a real-time traffic management scheme. A traffic management scheme consists of the different actions that will be implemented by all agencies to manage the corridor. These actions are: - List of Dynamic Message Signs (DMS) to be activated along with their messages - Transit vehicle service pattern including any route and headway modifications - Timing plan of all signalized intersections 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-7-0-0 The DSS shall provide measures of performance for all travel modes and facilities. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-8-0-0 The DSS shall provide estimation of vehicle emissions including CO, CO2, NO2 and SO2 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-9-0-0 The DSS shall provide visualization capabilities of the traffic distribution and associated measures of performance. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-10-0-0 The DSS shall provide real-time estimation of the current conditions for the entire intermodal network. Elements of the intermodal network include freeways, HOV lanes, arterials, bus lines, light rail lines, and park-and-ride facilities. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-10-1-0 The DSS shall provide real-time estimation of average link speed and traffic density for the freeway system at 30 second interval. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-10-2-0 The DSS shall provide real-time estimation of average link speed and traffic density for the HOV system at 30 second interval. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-10-3-0 The DSS shall provide real-time estimation of average link speed and traffic density for the arterial system at 30 second interval. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-10-4-0 The DSS shall provide real-time estimation of queue length on the links of the arterial system at 30 second interval. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-10-5-0 The DSS shall provide real-time estimation of transit vehicle (train/bus) locations at 30 second interval. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-10-6-0 The DSS shall provide real-time estimation of number of passengers on board for all transit vehicles at 30 second interval. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-10-7-0 The DSS shall provide real-time estimation of number of passengers at all bus stops and train stations at 30 second interval. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-10-8-0 The DSS shall provide real-time estimation of the occupancy of parking lots at 30 second interval. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-10-9-0 The DSS shall provide real-time estimation of vehicle emissions including CO, CO2, NO2 and SO2. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-10-10-0 The DSS shall perform internal consistency checking at 2 minutes interval using real-time observations of link speeds and traffic densities.
  1. The system's estimation error of the traffic speed, density and volume on every highway link in the network should not exceed 15% (plus or minus).
  2. The system's estimation error of the location of every transit vehicle in the network should not exceed 10% (plus or minus).
  3. The system's estimation error of the occupancy of every park-and-ride facility in the network should not exceed 20% (plus or minus).
 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-10-11-0 The DSS shall provide animation capabilities of the vehicular traffic along all arterials and freeways. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-10-12-0 The DSS shall provide animation capabilities of the transit vehicles (buses and trains) along shared and exclusive ROW facilities. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-0-0 The DSS shall provide short-term prediction of the conditions of the entire intermodal network 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-1-0 The DSS shall predict average link speed and traffic density for the freeway system at 30 second interval for one hour horizon. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-2-0 The DSS shall predict average link speed and traffic density for the HOV system at 30 second interval for one hour horizon. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-3-0 The DSS shall predict average link speed and traffic density for the arterial system at 30 second interval for one hour horizon. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-4-0 The DSS shall predict average queue length on the links of the arterial system at 30 second interval for one hour horizon. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-5-0 The DSS shall predict transit vehicle (train/bus) locations at 30 second interval for one hour horizon. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-6-0 The DSS shall predict number of passengers on board for all transit vehicles at 30 second interval for one hour horizon. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-7-0 The DSS shall predict number of passengers at all bus stops and train stations at 30 second interval for one hour horizon. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-8-0 The DSS shall provide real-time estimation of the occupancy of parking lots at 30 second interval for one hour horizon. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-9-0 Predicting the network future conditions (travel times and traffic density on every link) requires predicting the travel demand between every origin destination pairs for the prediction horizon which is one hour. The DSS shall predict the origin-destination demand matrix for the entire prediction horizon. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-10-0 The DSS shall predict how traffic is distributed along the different routes that connect every origin-destination pair. Equilibrium-based traffic assignment models are widely accepted as a technique for modeling route choice in urban networks. The DSS shall predict the traffic route assignment pattern based on equilibrium network conditions 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-11-0 The DSS shall predict traffic route assignment pattern based on multi-criteria (travel time and toll) route-mode choice behavior. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-12-0 The DSS shall provide the prediction results in real-time. For a prediction horizon of X minutes, the prediction results should be available no later than 0.10X minutes from the start of the prediction module. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-13-0 The DSS shall update the prediction results every 10 minutes. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-14-0 The DSS shall predict measures of performance at the arterial level including average travel time and average stop time. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-15-0 The DSS shall predict measures of performance at the network level including average travel time and average stop time. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-16-0 The DSS shall predict measures of performance for the freeway system including travel time and throughput. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-17-0 The DSS shall provide the prediction of measures of performance for the HOV system including travel time and throughput. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-18-0 The DSS shall predict measures of performance for the transit system including average vehicle speed, load factor, and average passenger waiting time. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-19-0 The DSS shall predict measures of performance for park-and-ride facilities including average occupancy. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-20-0 The DSS shall predict of measures of performance for every origin-destination pair including average travel time and average stop time. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-11-21-0 The DSS shall predict vehicle emissions including CO, CO2, NO2 and SO2 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-12-0-0 The DSS shall provide evaluation capabilities of pre-developed integrated real-time traffic management schemes 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-12-1-0 The DSS shall evaluate the impact of roadway incidents with different levels of severity (for different number of closed lanes and for different duration) at the facility and the corridor levels. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-12-2-0 The DSS shall evaluate pre-timed intersection control timing plans at the network level at the facility and the corridor levels. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-12-3-0 The DSS shall evaluate adaptive signal control at the network level at the facility and the corridor levels. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-4-0 The DSS shall evaluate the coordination of traffic signals along arterials at the facility and the corridor levels. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-5-0 The DSS shall evaluate transit vehicle priority schemes at the facility and the corridor levels. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-6-0 The DSS shall evaluate congestion pricing strategies, using up to 15-minute toll interval, for the freeway system at the facility and the corridor levels. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-7-0 The DSS shall evaluate congestion pricing strategies, using up to 15-minute toll interval, for the HOV/managed lanes system at the facility and the corridor levels. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-8-0 The DSS shall evaluate congestion pricing strategies, using up to 15-minute toll interval, for the arterial system at the facility and the corridor levels. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-9-0 The DSS shall evaluate the effect of providing route guidance information to travelers through dynamic message signs at freeways and arterials. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-10-0 The DSS shall evaluate the effect of posting speed advisory information to travelers through dynamic message signs at freeways and arterials. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-11-0 The DSS shall evaluate the effect of posting information on incident(s) location and severity on dynamic message signs at freeways and arterials. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-12-0 The DSS shall evaluate the effect of posting park-and-ride information on dynamic message signs at freeways and arterials. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-13-0 The DSS shall evaluate the effect of providing travelers with pre-trip information on efficient intermodal routes. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-14-0 The DSS shall evaluate the effect of providing travelers with pre-trip information on incident(s) location and severity. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-15-0 The DSS shall evaluate the effect of providing travelers with pre-trip information on travel time. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-16-0 The DSS shall evaluate the effect of providing travelers with pre-trip information on park-and-ride locations. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-17-0 The DSS shall evaluate the effect of providing travelers with en-route information on efficient intermodal routes. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-18-0 The DSS shall evaluate the effect of providing travelers with en-route information on incident(s) location and severity. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-19-0 The DSS shall evaluate the effect of providing travelers with en-route information on travel time. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-20-0 The DSS shall evaluate the effect of providing travelers with en-route information on park-and-ride locations. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-21-0 The DSS shall evaluate bus/train deadheading strategies. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-22-0 The DSS shall evaluate bus/train stop skipping strategies. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-23-0 The DSS shall evaluate real-time bus detour. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-24-0 The DSS shall evaluate bus/train service headways change. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-25-0 The DSS shall evaluate transit charter express services. 1, 9, 10, 13 Section 5.3, Con Ops L Testing
F-DSS-12-26-0 The DSS shall provide the capability to simultaneously run and compare several (at least three) operation scenarios. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-13-0-0 The DSS shall provide the capabilities to develop optimal traffic management scheme in real-time 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-13-1-0 The DSS shall provide the capability to develop efficient incident management scheme. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-13-2-0 The DSS shall provide the capability to develop optimal arterial-based signal timing scheme. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-13-3-0 The DSS shall provide the capability to develop optimal area-wide signal timing scheme. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-13-4-0 The DSS shall provide the capability to develop optimal congestion pricing strategies. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-13-5-0 The DSS shall provide the capability to develop travelers' pre-trip information provision strategies on all travel modes including route structure, travel time, tolls, parking location, etc. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-13-6-0 The DSS shall provide the capability to develop travelers' en-route information provision strategies on all travel modes including route structure, travel time, tolls, parking location, etc. 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-14-0-0 The DSS shall be compliant with the Regional Center to Center ICD 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-15-0-0 The DSS shall provide a user interface for the agencies 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-15-1-0 The DSS shall provide an API to integrate with existing agency systems 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-15-2-0 The DSS shall provide a web based interface for agencies not connected to the regional network 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-16-0-0 The DSS shall provide a security subsystem 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-16-1-0 The DSS shall provide a security subsystem to manage user authentication 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-16-2-0 The DSS shall provide a security subsystem to manage user authorization 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-17-0-0 The DSS shall provide a report generation function 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-18-0-0 The DSS shall provide an alarm subsystem 1, 9, 10, 13 Section 5.3, Con Ops M Testing
F-DSS-19-0-0 The DSS shall provide a response plan database to store pre-approved response plans 1, 9, 10, 13 Section 5.3, Con Ops H Testing
F-DSS-21-0-0 The DSS shall select a recommended pre-approved response plan based on current network conditions 1, 9, 10, 13 Section 5.3, Con Ops H Testing
F-DSS-21-1-0 The DSS shall include a search function for selecting pre-approved response plans 1, 9, 10, 13 Section 5.3, Con Ops H Testing
F-DSS-21-2-0 The DSS shall present recommended pre-approved response plans based on current network conditions 1, 9, 10, 13 Section 5.3, Con Ops H Testing
F-DSS-21-2-1 The DSS shall provide controls for Operator to receive a response plan request 1, 9, 10, 13 Section 5.3, Con Ops H Testing
F-DSS-21-2-2 The DSS shall provide controls for an Operator to accept a response plan request 1, 9, 10, 13 Section 5.3, Con Ops H Testing
F-DSS-21-2-3 The DSS shall provide controls for an Operator to reject a response plan request 1, 9, 10, 13 Section 5.3, Con Ops H Testing
F-DSS-21-2-4 The DSS shall provide controls for an Operator to modify a response plan request 1, 9, 10, 13 Section 5.3, Con Ops H Testing
F-DSS-21-2-5 The DSS shall provide controls for an Operator to cancel a response plan 1, 9, 10, 13 Section 5.3, Con Ops H Testing
F-DSS-21-2-6 The DSS shall provide controls for an Operator to request an alternate response plan 1, 9, 10, 13 Section 5.3, Con Ops H Testing
F-DSS-21-2-7 The DSS shall provide controls for an Operator to distribute the approved response plan 1, 9, 10, 13 Section 5.3, Con Ops H Testing
Table 7.3-2 Evaluation Model Subsystem Requirements
Requirement ID Requirement Description User Need Source Criticality Verification Method
C-MOD-1-0-0 The ICM Model shall utilize existing data from the regional data warehouse 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
D-MOD-1-0-0 The ICM Model shall receive the coordinates of intersections in the corridor. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
D-MOD-2-0-0 The ICM Model shall receive a list of links in the network. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
D-MOD-3-0-0 The ICM Model shall receive information on each link including:
  1. facility type
  2. number of lanes
  3. capacity per lane
  4. speed limit
  5. average jam density.
 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
D-MOD-4-0-0 The ICM Model shall receive toll data for toll roads in the network. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
D-MOD-5-0-0 The ICM Model shall receive information on the control type and associated timing plan at each intersection. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
D-MOD-6-0-0 The ICM Model shall receive information on active detectors in the network. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
D-MOD-7-0-0 The ICM Model shall receive location of active dynamic message signs in the network. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
D-MOD-8-0-0 The ICM Model shall receive information on allowed/prohibited turning movements at each intersection. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
D-MOD-9-0-0 The ICM Model shall receive information on route structure of all bus and train lines in the network. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
D-MOD-10-0-0 The ICM Model shall receive time table for bus and train lines in the network. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
D-MOD-11-0-0 The ICM Model shall receive fare structure data for bus and train lines in the network. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
D-MOD-12-0-0 The ICM Model shall receive the location of bus stops in the network. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
D-MOD-13-0-0 The ICM Model shall receive the location of train stations. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
D-MOD-14-0-0 The ICM Model shall receive the location of park-and-ride facilities in the network 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
D-MOD-15-0-0 park-and-ride facilities in the network 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-1-0-0 The ICM Model shall develop a incident response plan 9, 12 Section 4.10, 4.11, 5.1 Con Ops H Testing
F-MOD-2-0-0 The ICM Model shall calculate measures of performance for all travel modes and facilities. 9, 12 Section 4.10, 4.11, 5.1 Con Ops H Testing
F-MOD-2-1-0 The ICM Model shall calculate travel time index 9, 12 Section 4.10, 4.11, 5.1 Con Ops H Testing
F-MOD-2-2-0 The ICM Model shall calculate average travel time 9, 12 Section 4.10, 4.11, 5.1 Con Ops H Testing
F-MOD-2-3-0 The ICM Model shall calculate the average corridor throughput 9, 12 Section 4.10, 4.11, 5.1 Con Ops H Testing
F-MOD-2-4-0 The ICM Model shall calculate the average response time to an incident by jurisdiction 9, 12 Section 4.10, 4.11, 5.1 Con Ops H Testing
F-MOD-2-5-0 The ICM Model shall calculate the parking lot volumes at transit locations 9, 12 Section 4.10, 4.11, 5.1 Con Ops H Testing
F-MOD-2-6-0 The ICM Model shall calculate the ridership per transit vehicle 9, 12 Section 4.10, 4.11, 5.1 Con Ops H Testing
F-MOD-2-7-0 The ICM Model shall calculate the queue wait time at intersections 9, 12 Section 4.10, 4.11, 5.1 Con Ops H Testing
F-MOD-3-0-0 The ICM Model shall calculate environment-oriented measures of performance. 9, 12 Section 4.10, 4.11, 5.1 Con Ops H Testing
F-MOD-3-1-0 The ICM Model shall estimate vehicle emissions including:
  1. CO
  2. CO2
  3. NO2
  4. SO2
 9, 12 Section 4.10, 4.11, 5.1 Con Ops H Testing
F-MOD-5-0-0 The ICM Model shall evaluate pre-approved incident response plans 9, 12 Section 4.10, 4.11, 5.1 Con Ops H Testing
F-MOD-5-1-0 The ICM Model shall evaluate the impact of roadway incidents 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-2-0 The ICM Model shall evaluate pre-timed intersection control timing plans 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-3-0 The ICM Model shall evaluate adaptive signal control at the network level at the facility and the corridor levels. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-4-0 The ICM Model shall evaluate the coordination of traffic signals along arterials at the facility and the corridor levels. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-5-0 The ICM Model shall evaluate transit vehicle priority schemes at the facility and the corridor levels. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-6-0 The ICM Model shall evaluate congestion pricing strategies, using up to 15-minute toll interval, for the freeway system at the facility and the corridor levels. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-7-0 The ICM Model shall evaluate congestion pricing strategies, using up to 15-minute toll interval, for the HOV/managed lanes system at the facility and the corridor levels. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-8-0 The ICM Model shall evaluate congestion pricing strategies, using up to 15-minute toll interval, for the arterial system at the facility and the corridor levels. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-9-0 The ICM Model shall evaluate the effect of providing route guidance information to travelers through dynamic message signs at freeways and arterials. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-10-0 The ICM Model shall evaluate the effect of posting speed advisory information to travelers through dynamic message signs at freeways and arterials. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-11-0 The ICM Model shall evaluate the effect of posting information on incident(s) location and severity on dynamic message signs at freeways and arterials. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-12-0 The ICM Model shall evaluate the effect of posting park-and-ride information on dynamic message signs at freeways and arterials. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-13-0 The ICM Model shall evaluate the effect of providing travelers with pre-trip information on efficient intermodal routes. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-14-0 The ICM Model shall evaluate the effect of providing travelers with pre-trip information on incident(s) location and severity. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-15-0 The ICM Model shall evaluate the effect of providing travelers with pre-trip information on travel time. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-16-0 The ICM Model shall evaluate the effect of providing travelers with pre-trip information on park-and-ride locations. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-17-0 The ICM Model shall evaluate the effect of providing travelers with en-route information on efficient intermodal routes. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-18-0 The ICM Model shall evaluate the effect of providing travelers with en-route information on incident(s) location and severity. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-19-0 The ICM Model shall evaluate the effect of providing travelers with en-route information on travel time. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-20-0 The ICM Model shall evaluate the effect of providing travelers with en-route information on park-and-ride locations. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-21-0 The ICM Model shall evaluate bus/train deadheading strategies. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-22-0 The ICM Model shall evaluate bus/train stop skipping strategies. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-23-0 The ICM Model shall evaluate bus detours 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
F-MOD-5-24-0 The ICM Model shall evaluate bus/train service headways change. 9, 12 Section 4.10, 4.11, 5.1 Con Ops M Testing
Table 7.3-3 Web Subsystem Requirements
Requirement ID Requirement Description User Need Source Criticality Verification Method
empty cell SECURITY empty cell empty cell empty cell empty cell
S-WEB-1-0-0 The Web subsystem shall allow users, with appropriate authorization the following capabilities for the ICMS data:
  1. Create
  2. Update
  3. Close
  4. Receive
  5. Distribute
7 Section 4 Con Ops M Testing
S-WEB-1-1-0 The Web subsystem shall provide the capability to refresh all views automatically based on an associated time interval. 7 Section 4 Con Ops M Testing
S-WEB-1-2-0 The Web subsystem shall require a login username and password 7 Section 4 Con Ops M Testing
S-WEB-1-3-0 The Web subsystem shall have multiple levels of users to include:
  1. Agency User
  2. ICM Coordinator
  3. Administrator
  4. 3rd Party Partner
  5. Regional ATIS
 7 Section 4 Con Ops M Testing
S-WEB-1-4-0 Login information and privileges will be stored in a centralized access control database 7 Section 4 Con Ops M Testing
S-WEB-1-5-0 The Web subsystem shall restrict a user account to 1 login instance. 7 Section 4 Con Ops M Testing
S-WEB-2-0-0 The ICM Coordinator shall be able to verify any event, and shall be able to override any event 7 Section 4 Con Ops M Testing
S-WEB-3-0-0 An Agency User shall have the capability to enter an active construction event 7 Section 4 Con Ops M Testing
S-WEB-4-0-0 An Agency User shall have the capability to enter an active special event 7 Section 4 Con Ops M Testing
S-WEB-5-0-0 An Agency User shall be able to reopen a previously closed organization owned event. 7 Section 4 Con Ops M Testing
S-WEB-6-0-0 The Web subsystem shall allow all users with read-only privileges to view events 7 Section 4 Con Ops M Testing
empty cell FUNCTIONALITY empty cell empty cell empty cell empty cell
F-WEB-1-0-0 The Web subsystem shall include a web interface to the ICM System 1, 2, 3, 4, 5, 6, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-2-0-0 The Web subsystem shall allow users to view data on a GIS based map to include:
  1. incident data
  2. construction data
  3. special events data
  4. link data
  5. DMS data
  6. HAR data
  7. highway point data
  8. ransit point data
  9. CCTV data
  10. transit stop data
  11. parking data
  12. traffic signal data
 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-3-0-0 The Web Subsystem shall allow users to view pre-approved response plans 9, 13 empty cell empty cell Testing
F-WEB-4-0-0 The Web Subsystems subsystem shall utilize the Regional GIS based map 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 empty cell empty cell Testing
F-WEB-5-0-0 The Web subsystem shall provide an event tracking interface 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-6-0-0 The Web subsystem shall include separate event tracking interface module for:
  1. Incidents
  2. Construction
  3. Special Events
  4. Alarms/ Help
 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 empty cell empty cell Testing
empty cell Event Tracking empty cell empty cell empty cell empty cell
F-WEB-7-0-0 The Event Tracking interface shall have a separate highway and transit view for each of the incident, construction, and special event tracking views 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-8-0-0 The Event Tracking interface shall allow Agency Users to create new events. 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-9-0-0 The Event Tracking interface shall allow Agency Users to update existing events created by that reporting organization 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-10-0-0 The Event Tracking interface shall allow Agency Users to close existing events which were created by that reporting organization 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-11-0-0 The Event Tracking interface shall allow the ICM Coordinator user to update and close events that were created by other organizations. 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-12-0-0 The Event Tracking interface shall allow a user to select values from pick lists to populate fields in the event tracking screen. 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-13-0-0 The Event Tracking interface shall automatically build the event description as values are selected or entered during Create and Update event entry 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-14-0-0 The Event Tracking interface shall allow a user with edit privileges to edit the event description directly. 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-15-0-0 The Event Tracking interface shall provide a default organization based on the user's profile. 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
empty cell Incident Module empty cell empty cell empty cell empty cell
F-WEB-16-0-0 The Incident Tracking view shall allow Agency users to:
  1. update incident information
  2. view incident information
  3. close incidents
 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-17-0-0 The Incident Tracking view shall have the capability to sort the incidents based on:
  1. date/time
  2. Organization
  3. incident type
  4. facility
 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
empty cell Construction Module empty cell empty cell empty cell empty cell
F-WEB-18-0-0 The Construction Tracking view shall allow entry of construction event schedule information 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-19-0-0 The Construction Tracking view shall allow Agency users to:
  1. create construction information
  2. update construction information
  3. view construction information
 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-20-0-0 The Construction Tracking view shall allow Agency users to delete construction information 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-21-0-0 Active Construction events shall appear as an incident in the Incident Tracking view. 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-22-0-0 A planned construction schedule shall generate an active alarm, when the scheduled start is about to occur 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
empty cell Special Events Module empty cell empty cell empty cell empty cell
F-WEB-23-0-0 The Special Event Tracking interface shall allow entry of special event information 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-24-0-0 The Special Event Tracking interface shall allow Agency users to:
  1. Create special event information
  2. Update special event information
  3. View special event information
 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-25-0-0 The Special Event Tracking interface shall allow Agency users to delete special event information 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-26-0-0 Active Special Events shall appear as an incident in the Incident Tracking view. 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-27-0-0 A planned special event schedule shall be generate an active alarm, when the scheduled start is about to occur 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
empty cell Network Data empty cell empty cell empty cell empty cell
F-WEB-28-0-0 The Web subsystem shall allow ICM Coordinator to view network data 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-29-0-0 The Web subsystem shall allow Agency User to view network data 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-30-0-0 The Web subsystem shall allow ICM Coordinator to update static network data 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-31-0-0 The Web subsystem shall allow Agency User to update static network data for their network 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-32-0-0 The Web subsystem shall allow ICM Coordinator to add network data for new infrastructure 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
empty cell Help/ Alarms empty cell empty cell empty cell empty cell
F-WEB-33-0-0 The Web subsystem shall include an alarm subsystem 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-34-0-0 The Web subsystem shall maintain a log storing system errors and a log storing user requests 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-35-0-0 The Web subsystem shall provide a help screen 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-36-0-0 The Alarm view shall display alarms for new, update, and closed events. 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-37-0-0 The Alarm view shall provide a alarm filter for searching 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-38-0-0 The Alarm view shall provide filtering based on type (highway/ Transit), Facility, time of day, direction, and duration 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-39-0-0 The Alarm view filter shall be available to all users. 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-40-0-0 The Alarm view filter criteria shall only be editable by the Administrator 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-41-0-0 The Alarm view shall received alarms for pending events, incidents, and planned events. 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-42-0-0 Alarms shall be removed from the Alarm View when a user acknowledges or confirms the notification. 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
F-WEB-43-0-0 Alarms shall be removed for an organization from the Alarm View when an Agency user acknowledges or confirms the notification. 1, 2, 3, 4, 5, 6, 7, 8, 13, 14 Section 4 Con Ops M Testing
Table 7.3-4 ICM Database Requirements
Requirement ID Requirement Description User Need Source Criticality Allocation
F-DBA-1-0-0 The Database shall store data received from the ICMS subsystems 8 empty cell H Testing
F-DBA-2-0-0 The Database shall store data received from the corridor systems 8 empty cell H Testing
F-DBA-4-0-0 The Database shall store:
  1. Historical information needed for the modeling and decision support subsystems
  2. Current day activities within the corrido
  3. Pre-approved response plans
  4. Contact Lists
 8 empty cell H Testing

Previous | Table of Contents | Next