4.     ICMS Individual System Requirements

The section includes the requirements for the ICMS to ease software development and testing. Each requirement in the following subsections as well as Section 5: Hardware Requirements includes the following information:

ID                                            Unique identifier

Requirement Description           Text description of actual requirement

Source                                     Identifies which User Need from Table 1 of this document that the requirement relates to

Allocation                                 Identifies the responsibility for accomplishing the requirement

Criticality                                  High = required to complete the ICMS
                                                Medium = will improve the ICMS
                                                Low = nice to have, but won’t affect the completion of the ICMS

4.1    ICMS Data Hub System Requirements

The ICMS Data Hub will be a new system developed for the I-394 ICM Deployment. The ICMS-Data Hub System will perform seven key functions:

• Receive and store data from ICMS-MTCC System;
• Receive and store data from ICMS-Traffic Operations System;
• Receive and store data from ICMS-ABC System;
• Receive and store data from ICMS-EMS Systems (note there are three ICMS-EMS systems proposed (MSP-EMS, HENN-EMS, COM-EMS) the ICMS Data Hub System shall treat interfaces from any EMS system in the same manner, therefore supporting future additional EMS systems sending data to the ICMS-Data Hub;
• Receive and store data from ICMS-ASG Systems (note there are three ICMS-ASG systems proposed (Mn/DOT-ASG, HENN-ASG, COM-ASG) the ICMS Data Hub System shall treat interfaces from any ASG system in the same manner, therefore supporting future additional ASG systems sending data to the ICMS-Data Hub;
• Post Data for systems to acquire; and
• Provide an Operator/Administrator Interface.

Figure 22 illustrates the ICMS-Data Hub functions and Table 7 includes the ICMS-Data Hub requirements to ease software development and testing.

Figure 22: ICMS-Data Hub Functions

Table 7: ICMS-Data Hub Requirements

ID	Requirement Description	Source	Allocation	Criticality
DH-1	The ICMS-Data Hub System Shall Receive and Store Messages Describing Incidents within the ICM Corridor from the ICMS-EMS Systems.	User Need 1	ICMS-Data Hub	H
DH-1-1	ICMS-Data Hub Receive and Store ICMS-EMS Incident Data: Data Exchanges The ICMS-Data Hub System shall receive and store ICMS-EMS incident data from the ICMS-EMS System , as per the ICMS-EMS to ICMS-Data Hub ICD.	User Need 1	ICMS-Data Hub	H
DH-1-2	ICMS-Data Hub Receive and Store ICMS-EMS Incident Data: Time Log The ICMS-Data Hub System shall log the time of each test message, received from an EMS System.	User Need 1	ICMS-Data Hub	H
DH-1-3	ICMS-Data Hub Receive and Store ICMS-EMS Incident Data: Alert of no data The ICMS-Data Hub System shall send an alert to an administrator (within 10 seconds) when no incident messages or test messages have been received for an amount of time that is configurable by an ICMS-Data Hub system administrator, noting that connections with the EMS systems may be down.	User Need 1	ICMS-Data Hub	H
DH-2	The ICMS-Data Hub System Shall Receive and Store Data within the ICM Corridor from ICMS-Traffic Operations System.	User Need 1	ICMS-Data Hub	H
DH-2-1	ICMS-Data Hub Receive and Store ICMS-Traffic Operations Incident and Event Data The ICMS-Data Hub System shall receive and store ICMS Traffic Operations incident and event data from the ICMS-Traffic Operations System, as per the ICMS-Traffic Operations to ICMS-Data Hub ICD.	User Need 1	ICMS-Data Hub	H
DH-2-2	ICMS-Data Hub Receive and Store ICMS-Traffic Operations Freeway Traffic Data  The ICMS-Data Hub System shall receive and store ICMS Traffic Operations Freeway Traffic Data from the ICMS Traffic Operations System, as per the ICMS Traffic Operations to ICMS-Data Hub ICD.	User Need 1 and 2	ICMS-Data Hub	H
DH-2-2-1	ICMS-Data Hub Receive and Store ICMS-Traffic Operations Freeway Traffic Data: Traffic Details   The ICMS Traffic Operations Freeway Traffic Data shall consist of the most recent volume, occupancy, and speed data for all sensor stations along: the I-394 mainline and I-394  ramps I-494 within the boundaries of the corridor; Hwy 100 within the boundaries of the corridor; and Hwy 169 within the boundaries of the corridor.	User Need 1 and 2	ICMS-Data Hub	H
DH-2-2-2	ICMS-Data Hub Receive and Store ICMS-Traffic Operations Freeway Travel Times The ICMS-Data Hub System shall receive and store messages describing travel time along I-394, I-494, Hwy 100, and Hwy 169 from the ICMS-Traffic Operations system, as per the ICMS-Traffic Operations to ICMS-Data Hub ICD.	User Need 3	ICMS-Data Hub	H
DH-2-3	ICMS-Data Hub Receive and Store ICMS-Traffic Operations Mn/PASS Data The ICMS-Data Hub System shall receive and store Mn/PASS Travel Time from the Traffic Operations Center.	User Need 2	ICMS-Data Hub	H
DH-2-3-1	CMS-Data Hub Receive and Store ICMS-Traffic Operations Mn/PASS Data: Data Exchanges The ICMS-Data Hub System shall receive and store ICMS-Traffic Operations Mn/PASS Data from the Traffic Operations Center, as per the ICMS-Traffic Operations to ICMS-Data Hub ICD.	User Need 2	ICMS-Data Hub	H
DH-2-3-2	ICMS-Data Hub Receive and Store ICMS-Traffic Operations Mn/PASS Data: Details The ICMS-Data Hub System shall receive and store ICMS-Traffic Operations Mn/PASS Data describing the direction of flow and current accessibility of the Mn/PASS lane.	User Need 2	ICMS-Data Hub	H
DH-2-3-3	ICMS-Data Hub Receive and Store ICMS-Traffic Operations Mn/PASS Travel Times The ICMS-Data Hub System shall receive and store messages describing travel times in the Mn/PASS lanes from the Traffic Operations Center, as per the ICMS-Traffic Operations Center to ICMS-Data Hub ICD.	User Need 3	ICMS-Data Hub	H
DH-3	The ICMS-Data Hub System shall Receive and Store Messages Describing Arterial Traffic Conditions with the ICM Corridor from ICMS-ASG Systems.	User Need 2	ICMS-Data Hub	H
DH-3-1	ICMS-Data Hub Receive and Store ICMS-Mn/DOT-ASG Arterial Traffic Data: Data Exchanges The ICMS-Data Hub System shall receive and store arterial traffic data from any Arterial Signal Group (ASG) system, as per the ICMS-ASG to ICMS-Data Hub ICD.	User Need 2	ICMS-Data Hub	H
DH-3-2	ICMS-Data Hub Receive and Store ICMS-Mn/DOT-ASG Arterial Traffic Data: No Data Available The ICMS-Data Hub System shall receive and store Arterial Traffic Data from the ICMS-Mn/DOT-ASG indicating “no data available’ if no data is available.	User Need 1	ICMS-Data Hub	H
DH-3-3	ICMS-Data Hub Receive and Store ICMS-Mn/DOT-ASG Arterial Traffic Data: Travel Times The ICMS-Data Hub System shall receive and store Arterial Traffic Data from the ICMS-Mn/DOT-ASG describing real-time travel times.	User Need 2	ICMS-Data Hub	H
DH-3-4	ICMS-Data Hub Receive and Store ICMS-Mn/DOT-ASG Arterial Traffic Data: Volume and Speed Data The ICMS-Data Hub System shall receive and store Arterial Traffic Data from the ICMS-Mn/DOT-ASG describing volume and speed.	User Need 2	ICMS-Data Hub	H
DH-3-5	ICMS-Data Hub Receive and Store ICMS-ASG Special Event and Incident Signal Timing Plans Data The ICMS-Data Hub System shall receive and store Special Event and Signal Timing Plans Data from the ICMS-ASG.	User Need 17	ICMS-Data Hub	H
DH-3-6	ICMS-Data Hub Receive and Store ICMS-ASG Special Event and Incident Signal Timing Plans Data: Selected Signal Timing Plan The ICMS-Data Hub System shall receive and store Special Event and Incident Signal Timing Plans Data from the ICMS-ASG identifying which signal timing plan was implemented.	User Need 17	ICMS-Data Hub	H
DH-3-6-1	ICMS-Data Hub Receive and Store ICMS-ASG Special Event and Incident Signal Timing Plans Data: Time Implemented The ICMS-Data Hub System shall receive and store Special Event and Incident Signal Timing Plans Data from the HICMS-ASG identifying the time a signal timing plan was implemented.	User Need 17	ICMS-Data Hub	H
DH-3-6-2	ICMS-Data Hub Receive and Store ICMS-ASG Special Event and Incident Signal Timing Plans Data: Time Deactivated The ICMS-Data Hub System shall receive and store Special Event and Incident Signal Timing Plans Data from the ICMS-ASG identifying the time a signal timing plan was deactivated.	User Need 17	ICMS-Data Hub	H
DH-4	The ICMS-Data Hub System Shall Receive and Store messages within the ICM Corridor from the ICMS-MTCC System.	User Need 1	ICMS-Data Hub	H
DH-4-1	ICMS-Data Hub Receive and Store ICMS-MTCC Transit Route Travel Time Data The ICMS-Data Hub System shall receive and store messages describing bus travel times between park-and-ride locations and downtown Minneapolis along ICM corridor routes, as per the ICMS-MTCC to ICMS-Data Hub ICD.	User Need 1	ICMS-Data Hub	H
DH-4-2	ICMS-Data Hub Receive and Store ICMS-MTCC Park-and-Ride Data The ICMS-Data Hub System shall receive and store messages describing Park-and-Ride space availability for parking facilities within the ICM Corridor from the ICMS-MTCC, as per the ICMS-MTCC to ICMS-Data Hub ICD.	User Need 4	ICMS-Data Hub	H
DH-4-2-1	ICMS-Data Hub Receive and Store ICMS-MTCC Park-and-Ride Data: Details The ICMS-Data Hub System shall receive and store ICMS-MTCC Park-and-Ride Data describing the lot ID, the number of spaces that exist on the lot, the number of spaces occupied, and a timestamp of when the data was collected.	User Need 4	ICMS-Data Hub	H
DH-4-3	ICMS-Data Hub Receive and Store ICMS-MTCC Transit Incident Data The ICMS-Data Hub System shall receive and store messages describing Transit Incidents from the ICMS-MTCC system, as per the ICMS-MTCC to ICMS-Data Hub ICD.	User Need 1	ICMS-Data Hub	H
DH-4-3-1	ICMS-Data Hub Receive and Store ICMS-MTCC Transit Incident Data: Location The ICMS-Data Hub System shall receive and store ICMS-MTCC Transit Incident Data describing the incident location.	User Need 1	ICMS-Data Hub	H
DH-4-3-2	ICMS-Data Hub Receive and Store ICMS-MTCC Transit Incident Data: Type The ICMS-Data hub System shall receive and store Transit Incident Data describing the incident type.	User Need 1	ICMS-Data Hub	H
DH-4-3-3	ICMS-Data Hub Receive and Store ICMS-MTCC Transit Incident Data: Time The ICMS-Data Hub System shall receive and store ICMS-MTCC Transit Incident Data describing incident time elements: expected duration and estimated impact.	User Need 1	ICMS-Data Hub	H
DH-5	The ICMS-Data Hub Shall Receive and Store Data within the ICM Corridor from the ICMS-ABC Parking Garages System.	User Need 9	ICMS-Data Hub	H
DH-5-1	ICMS-Data Hub Receive and Store ICMS-ABC Parking Garages Data The ICMS-Data Hub System shall receive and store messages describing ABC Parking Space Availability from the ICMS-ABC system, as per the ICMS-ABC System to ICMS-Data Hub ICD.	User Need 9	ICMS-Data Hub	H
DH-6	The ICMS-Data Hub System Shall Provide a Mechanism for Administrators to Enter Configurable Values from an Internet Access Point.	User Need 9	ICMS-Data Hub	H
DH-6-1	ICMS-Data Hub Configurable Alert Timeframe The ICMS-Data Hub System shall provide a mechanism for operators/administrators to specify the time period that would be used to trigger and send an alert if no incident or test messages are received.	User Need 9	ICMS-Data Hub	H
DH-6-2	ICMS-Data Hub Configurable Alert Contact List The ICMS-Data Hub System shall provide a mechanism for operators/administrators to enter the email contact information for users to receive alerts.	User Need 9	ICMS-Data Hub	H
DH-6-3	ICMS-Data Hub Configurable Post Refresh Time The ICMS-Data Hub System shall provide a mechanism for operators/administrators to enter the time period at which the ICMS Data Hub shall post data for other systems to acquire.	User Need 9	ICMS-Data Hub	H
DH-6-4	ICMS-Data Hub Configurable Data Storage Timeframe The ICMS-Data Hub System shall provide a mechanism for operators/administrators to enter the time period that messages and data shall be stored for before being discarded.	User Need 9	ICMS-Data Hub	H
DH-6-5	ICMS-Data Hub shall maintain security by requiring administrators to login to the system. The ICMS-Data Hub System shall require administrators to login to the system before configuring settings.	User Need 9	ICMS-Data Hub	H
DH-6-6	ICMS-Data Hub security of operator interface The ICMS-Data Hub System shall provide a mechanism for operators to enter login and passwords to access the system.	User Need 9	ICMS-Data Hub	H
DH-6-7	ICMS-Data Hub security of administrator interface The ICMS-Data Hub System shall provide a mechanism for administrators to enter login and passwords to access the system to adjust configurable values.	User Need 9	ICMS-Data Hub	H
DH-6-8	ICMS-Data Hub security create user accounts The ICMS-Data Hub System shall provide a mechanism for system administrators to create user accounts and assign privileges.	User Need 9	ICMS-Data Hub	H
DH-6-9	ICMS-Data Hub adjust configuration settings The ICMS-Data Hub System shall adjust configuration settings when administrators enter new values within 30 seconds and shall not require a restart of the system.	User Need 9	ICMS-Data Hub	H
DH-7	The ICMS-Data Hub Shall Post ICMS-Data.	User Need 1	ICMS-Data Hub	H
DH-7-1	ICMS-Data Hub Post Data: Time The ICMS-Data Hub System shall post data sent to the ICMS-Data Hub from the ICMS Systems within a certain time after receiving the data, this time period shall be configurable by an ICMS Administrator, as per the ICMS Data Hub Post ICD.	User Need 1 and 6	ICMS-Data Hub	H
DH-7-2	ICMS-Data Hub Post Incident Data: Malfunctioning The ICMS-Data Hub System shall post ‘no data available’ if no data is received from specific ICMS Systems.	User Need 1 and 6	ICMS-Data Hub	H
DH-8	The ICMS-Data Hub Shall Store ICMS-Data Received from the ICMS Systems.	User Need 1	ICMS-Data Hub	H
DH-8-1	ICMS-Data Hub Store ICMS Data: Summary The ICMS-Data Hub System shall store messages and data received from other systems.	User Need 1	ICMS-Data Hub	H
DH-8-2	ICMS-Data Hub Store ICMS Data: Duration The ICMS-Data Hub System shall store messages and data received from other systems for a duration that is configurable by an ICMS Administrator up to a maximum of one week.	User Need 1	ICMS-Data Hub	H

4.2    ICMS Enhancements to Metro Transit Control Center (ICMS-MTCC) Functional Requirements

This section describes the requirements for the enhancements to the MTCC (referred to as ICMS-MTCC). The enhanced MTCC will perform five key functions (data input and storage, interface to field devices, information dissemination to travelers, operator/administrator interface, and data output to ICMS Data Hub). Figure 23 illustrates the five key functions and Table 8 includes the ICMS-MTCC System requirements to ease software development and testing.

Figure 23: ICMS-MTCC Functions

Table 8: ICMS-MTCC Requirements

ID	Requirement Description	Source	Allocation	Criticality
MTCC-1	The ICMS-MTCC System Shall Acquire and Store Data within the ICM Corridor from the ICMS-Data Hub.	User Need 7,11,12,13	ICMS-MTCC	H
MTCC-1-1	ICMS-MTCC Acquire and Store Incident and Event Data The ICMS-MTCC System shall acquire and store from the ICMS-Data Hub Incident and Event Data for roadways within the ICM corridor.	User Need 7,11,12,13	ICMS-MTCC	H
MTCC-1-1-1	ICMS-MTCC Acquire and Store Incident and Event Data: Data Exchanges The ICMS-MTCC System shall interface to the ICMS-Data Hub according to requirements of the ICMS-Data Hub Post ICD to acquire and store Incident and Event Data.	User Need 7,11,12,13	ICMS-MTCC	H
MTCC-1-1-2	ICMS-MTCC Acquire and Store Incident and Event Data: Frequency The ICMS-MTCC System shall acquire and store Incident and Event Data from the ICMS-Data Hub at a frequency that may be configured by an administrator.	User Need 7,11,12,13	ICMS-MTCC	H
MTCC-1-1-3	ICMS-MTCC Acquire and Store Incident and Event Data: Location The ICMS-MTCC System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event location.	User Need 7,11,12,13	ICMS-MTCC	H
MTCC-1-1-3-1	ICMS-MTCC Acquire and Store Incident and Event Data: Location Detail The ICMS-MTCC System shall acquire and Incident and Event Data from the ICMS-Data Hub describing the incident or event location as a geo reference.	User Need 7,11,12,13	ICMS-MTCC	H
MTCC-1-1-4	ICMS-MTCC System Acquire and Store Incident and Event Data: Type The ICMS-MTCC System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident type.	User Need 7,11,12,13	ICMS-MTCC	H
MTCC-1-1-5	ICMS-MTCC Acquire and Store Incident and Event Data: Time The ICMS-MTCC System shall acquire and store any available Incident and Event Data from the ICMS-Data Hub describing the incident or event time elements: start time, vehicle arrival time, and clearance time.	User Need 7,11,12,13	ICMS-MTCC	H
MTCC-1-2	ICMS-MTCC Acquire and Store Freeway Traffic Data The ICMS-MTCC System shall acquire and store Freeway Traffic Data from the ICMS-Data Hub.	User Need 1,7,17	ICMS-MTCC	H
MTCC-1-2-1	ICMS-MTCC Acquire and Store Freeway Traffic Data: Data Exchanges The ICMS-MTCC System shall interface with the ICMS-Data Hub in accordance with the ICMS-Data Hub Post ICD to acquire and store Freeway Traffic Data.	User Need 1,7,17	ICMS-MTCC	H
MTCC-1-2-2	ICMS-MTCC Acquire and Store Freeway Traffic Data: Frequency The ICMS-MTCC System shall acquire and store Freeway Traffic Data from the ICMS-Data Hub at a frequency configurable by an ICMS-MTCC Administrator.	User Need 1,7,17	ICMS-MTCC	H
MTCC-1-2-3	ICMS-MTCC Acquire and Store Freeway Traffic Data: Traffic Details The ICMS-MTCC System shall acquire and store Freeway Traffic Data from the ICMS-Data Hub describing volume, occupancy, and speed data for sensor stations along: The I-394 mainline and I-394 ramps I-494 Hwy 100 Hwy 169.	User Need 1,7,17	ICMS-MTCC	H
MTCC-1-2-4	ICMS-MTCC Acquire and Store Freeway Traffic Data: Travel Times The ICMS-MTCC System shall acquire and store Freeway Traffic Data from the ICMS-Data Hub describing travel times.	User Need 1,7,17	ICMS-MTCC	H
MTCC-1-2-5	ICMS-SWT Acquire Mn/PASS direction and rate data. The ICMS-SWT System shall acquire Mn/PASS lane direction and pricing data from the ICMS-Data Hub, as per the ICMS-Data Hub Post ICD at least once every 2 minutes.	User Need 17	ICMS-SWT	H
MTCC-1-3	ICMS-MTCC Acquire and Store Special Event and Incident Signal Timing Plans Data The ICMS-MTCC System shall acquire and store Special Event and Incident Signal Timing Plans Data from the ICMS-Data Hub.	User Need 17	ICMS-MTCC	H
MTCC-1-3-1	ICMS-MTCC Acquire and Store Special Event and Incident Signal Timing Plans Data: Data Exchanges The ICMS-MTCC System shall interface with the ICMS-Data Hub in accordance with the ICMS-Data Hub Post ICD to acquire and store Special Events and Incident Signal Timing Plans Data.	User Need 17	ICMS-MTCC	H
MTCC-1-3-2	ICMS-MTCC Acquire and Store Special Event and Incident Timing Plans: Frequency The ICMS-MTCC System shall acquire and store Special Event and Incident Timing Plans from the ICMS-Data Hub at a frequency configurable by an ICMS-MTCC Administrator.	User Need 17	ICMS-MTCC	H
MTCC-2	The ICMS-MTCC System Shall Acquire and Store Park-and-Ride Space Information	User Need 5,6,8,9	ICMS-MTCC	H
MTCC-2-1	ICMS-MTCC Acquire and Store Park-and-Ride space availability information. The ICMS-MTCC System shall acquire and store Park-and-Ride space availability data for each Metro Transit operated Park-and-Ride facility in the ICM corridor from field equipment operated at the Park-and-Ride facility.	User Need 5,6,8,9	ICMS-MTCC	H
MTCC-2-1-1	ICMS-MTCC Acquire and Store Park-and-Ride space availability information - format The ICMS-MTCC System shall interface with the Park-and-Ride facilities in accordance with the MTCC ICD.	User Need 5,6,8,9	ICMS-MTCC	H
MTCC-2-2	ICMS-MTCC Acquire and Store Notices of Temporary Park-and-Ride Lot operation when entered into the MTCC CAD system. The ICMS-MTCC System shall acquire data describing temporary Park-and-Ride lot operation when activated within the MTCC system.	User Need 5,6,8,9	ICMS-MTCC	H
MTCC-3	The ICMS-MTCC System Shall Calculate Transit Travel Times.	User Need 5,6,8,9	ICMS-MTCC	H
MTCC-3-1	ICMS-MTCC Calculate Transit Travel Times: Route Designation The ICMS-MTCC System shall calculate transit travel times that estimate the time for a transit rider to travel from each park-and-ride facility to downtown Minneapolis.	User Need 5,6,8,9	ICMS-MTCC	H
MTCC-3-2	ICMS-MTCC Calculate Transit Travel Times: Frequency The ICMS-MTCC System shall calculate transit travel times at a frequency configurable by an ICMS Administrator.	User Need 5,6,8,9	ICMS-MTCC	H
MTCC-4	The ICMS-MTCC System Shall Calculate the Park-and-Ride Lot Parking Availability.	User Need 5,6,8,9	ICMS-MTCC	H
MTCC-4-1	ICMS-MTCC Calculate Park-and-Ride Lot Parking Status: Frequency The ICMS-MTCC System shall calculate park-and-ride lot parking status updates using the data acquired from each Park-and-Ride lot at a frequency configurable by an ICMS Administrator.	User Need 5,6,8,9	ICMS-MTCC	H
MTCC-5	The ICMS-MTCC System shall Send Data to the ICMS-Data Hub.	User Need 5,6,8,9,10	ICMS-MTCC	H
MTCC-5-1	ICMS-MTCC Generate and Send Transit Travel Time Messages. The ICMS-MTCC System shall generate and send transit travel time messages to the ICMS-Data Hub System for each Park-and-Ride facility to downtown Minneapolis.	User Need 10,11,12,13	ICMS-MTCC	H
MTCC-5-1-1	ICMS-MTCC Generate and Send Transit Travel Time Messages: Data Exchanges The ICMS-MTCC System shall interface with the ICMS Data-Hub System according to the ICMS-MTCC to ICMS-Data Hub ICD to send Transit Travel Time Data.	User Need 10,11,12,13	ICMS-MTCC	H
MTCC-5-1-2	ICMS-MTCC Generate and Send Transit Travel Time Messages: Frequency The ICMS-MTCC System shall send Transit Travel Time Data to the ICMS-Data Hub at a schedule frequency configurable by an ICMS Administrator.	User Need 10,11,12,13	ICMS-MTCC	H
MTCC-5-1-3	ICMS-MTCC Generate and Send Transit Travel Time Messages: No Data The ICMS-MTCC System shall send a message reporting that “no data available’ if the transit travel times can not be calculated for any reason.	User Need 10,11,12,13	ICMS-MTCC	H
MTCC-5-2	ICMS-MTCC Generate and Send Messages Describing Transit Incidents The ICMS-MTCC System shall generate and send messages describing Transit Incidents along transit routes that pass through the ICM corridor.	User Need 10,11,12,13	ICMS-MTCC	H
MTCC-5-2-1	ICMS-MTCC Generate and Send Messages Describing Transit Incidents: Data Exchanges The ICMS-MTCC System shall interface with the ICMS Data-Hub System according to the ICMS-MTCC to ICMS-Data Hub ICD to send Transit Incident Data.	User Need 10,11,12,13	ICMS-MTCC	H
MTCC-5-2-2	ICMS-MTCC Generate and Send Messages Describing Transit Incidents: Frequency The ICMS-MTCC System shall send Transit Incident Data to the ICMS-Data Hub within 3 minutes from when the incident is entered in the MTCC CAD system.	User Need 4	ICMS-MTCC	H
MTCC-5-3	ICMS-MTCC Generate and Send Messages Describing Park-and-Ride status The ICMS-MTCC System shall generate and send messages describing Transit Park-and-Ride Status for each Metro Transit operated lot  to the ICMS-Data Hub.	User Need 4	ICMS-MTCC	H
MTCC-5-3-1	ICMS-MTCC Generate and Send Messages Describing Park-and-Ride status: Data Exchanges The ICMS-MTCC System shall interface with the ICMS Data-Hub System according to the ICMS-MTCC to ICMS-Data Hub ICD to send Park-and-Ride Parking Status Data.	User Need 4	ICMS-MTCC	H
MTCC-5-3-2	ICMS-MTCC Generate and Send Messages Describing Park-and-Ride status: Data Exchanges: Frequency The ICMS-MTCC System shall generate and send Park-and-Ride Parking Status Data to the ICMS-Data Hub System each time a new Park-and-Ride calculation is performed.	User Need 4	ICMS-MTCC	H
MTCC-5-3-3	ICMS-MTCC Generate and Send Messages Describing Park-and-Ride status: Data Exchanges No Data Available The ICMS-MTCC System shall generate and send Park-and-Ride Parking Status Data to the ICMS-Data Hub System indicating “no data available’ if no data is available.	User Need 4	ICMS-MTCC	H
MTCC-5-3-4	ICMS-MTCC Generate and Send Transit Park-and-Ride Parking Status Data: Details The ICMS-MTCC System shall generate and send to the ICMS-Data Hub System Park-and-Ride Parking Status messages that include: the lot ID, the number of spaces that exist on the lot, the number of spaces calculated to be occupied, and a timestamp of when the data was collected.	User Need 4	ICMS-MTCC	H
MTCC-5-4	ICMS-MTCC Generate and Send Messages Describing Temporary Park-and-Ride Lots The ICMS-MTCC System shall generate and send messages describing Temporary Park-and-Ride Lot operation to the ICMS-Data Hub System.	User Need 4,15,16	ICMS-MTCC	H
MTCC-5-4-1	ICMS-MTCC Generate and Send Messages Describing Transit Temporary Park-and-Ride Lot Data: Data Exchanges The ICMS-MTCC shall interface with the ICMS Data-Hub System according to the ICMS-MTCC to ICMS-Data Hub ICD to send Temporary Park-and-Ride Lot Data.	User Need 4,15,16	ICMS-MTCC	H
MTCC-5-4-2	ICMS-MTCC Generate and Send Messages Describing Transit Temporary Park-and-Ride Lot Data: Frequency The ICMS-MTCC System shall send Temporary Park-and-Ride Lot Data to the ICMS-Data Hub when temporary Park-and-Ride information is available in the MTCC CAD system.	User Need 4,15,16	ICMS-MTCC	H
MTCC-5-4-3	ICMS-MTCC Generate and Send Messages Describing Transit Temporary Park-and-Ride Parking Status Data: No Data Available The ICMS-MTCC System shall send Temporary Park-and-Ride Parking Status Data to the ICMS-Data Hub indicating “no data available’ if no data is available.	User Need 4,15,16	ICMS-MTCC	H
MTCC-5-4-4	ICMS-MTCC Generate and Send Temporary Transit Park-and-Ride Lot Data: Details The ICMS-MTCC System shall generate and send messages to the ICMS-Data Hub describing Temporary Park-and-Ride Lot Data describing the lot ID, the location of the lot, the bus routes served by the lot, and the name of the event the lot was opened for .	User Need 4,15,16	ICMS-MTCC	H
MTCC-6	The ICMS-MTCC System Shall Disseminate Information to Transit Travelers using Existing Metro Transit Operated Traveler Information Systems.	User Need 8,9	ICMS-MTCC	H
MTCC-6-1	ICMS-MTCC shall disseminate transit travel times. The ICMS-MTCC System shall disseminate transit travel times to travelers using the Metro Transit information dissemination system.	User Need 8,9	ICMS-MTCC	H
MTCC-6-2	ICMS-MTCC shall disseminate Park-and-Ride availability information. The ICMS-MTCC System shall disseminate Park-and-Ride availability information using the Metro Transit information dissemination system.	User Need 8,9	ICMS-MTCC	H
MTCC-7	The ICMS-MTCC System Shall Interface with Field Devices.	User Need 7,8	ICMS-MTCC	H
MTCC-7-1	ICMS-MTCC shall Interface with Transit Signal Priority Devices The ICMS-MTCC System shall provide a mechanism for buses or bus operators to activate Transit Signal Priority at designated locations.	User Need 7,8	ICMS-MTCC	H
MTCC-7-2	ICMS-MTCC shall Interface with DMS The ICMS-MTCC System shall automatically generate and post messages to DMS located at Park-and-Ride facilities.	User Need 4,9	ICMS-MTCC	H
MTCC-7-2-1	ICMS-MTCC shall Interface with DMS: Park-n-Ride messages The ICMS-MTCC System shall automatically generate and post messages to DMS located at Park-and-Ride facilities describing the parking availability at the facility.	User Need 4,9	ICMS-MTCC	H
MTCC-7-2-2	ICMS-MTCC shall Interface with DMS: Transit Travel Times The ICMS-MTCC System shall automatically generate and post messages to DMS located at Park-and-Ride facilities describing transit travel times to downtown Minneapolis.	User Need 4,9	ICMS-MTCC	H
MTCC-7-2-3	ICMS-MTCC shall Interface with DMS: Configuration of message content The ICMS-MTCC System shall provide a mechanism for operators/administrators to configure whether park-and-ride messages or transit travel time messages, or both are posted to the signs.	User Need 4,9	ICMS-MTCC	H
MTCC-7-2-4	ICMS-MTCC shall Interface with DMS: Frequency The ICMS-MTCC System shall automatically generate and post messages to DMS located at Park-and-Ride facilities each time the Park-and-Ride calculations update the parking availability during periods of time each day that are configurable by an administrator.	User Need 4,9	ICMS-MTCC	H
MTCC-7-2-5	ICMS-MTCC shall Interface with DMS: Protocol The ICMS-MTCC System shall communicate messages to the DMS signs in accordance with the requirements in the ICMS-MTCC Sign Control ICD	User Need 4,9	ICMS-MTCC	H
MTCC-7-3	ICMS-MTCC shall Interface with Park-and-Ride Lots  The ICMS-MTCC System shall communicate with Park-and-Ride lot vehicle counters in order to acquire the data from park-and-ride facilities.	User Need 4,5,9	ICMS-MTCC	H
MTCC-7-4	ICMS-MTCC shall Interface with Transit Agencies  The ICMS-MTCC System shall provide a mechanism for MTCC Operators to interface with other Transit Agencies within the corridor.	User Need 10	ICMS-MTCC	H
MTCC-7-5	ICMS-MTCC shall Interface with Wireless Internet The ICMS-MTCC System shall provide a mechanism for MTCC Riders to interface with Internet Access.	User Need 7,8,10	ICMS-MTCC	H
MTCC-8	The ICMS-MTCC System Shall Provide an Operator/Administrator Interface.	User Need 10,11,12,13	ICMS-MTCC	H
MTCC-8-1	ICMS-MTCC shall configure frequency of transit travel time calculations. The ICMS-MTCC System shall provide a mechanism for operators/administrators to configure the frequency at which the transit travel times are calculated.	User Need 10,11,12,13	ICMS-MTCC	H
MTCC-8-2	ICMS-MTCC shall configure frequency of transit travel time message send. The ICMS-MTCC shall provide a mechanism for operators/administrators to configure the frequency at which the transit travel times messages are generated and sent to the ICMS-Data Hub System.	User Need 9	ICMS-MTCC	H
MTCC-8-3	ICMS-MTCC shall configure frequency of Park-and-Ride data acquisition. The ICMS-MTCC shall provide a mechanism for operators/administrators to configure the frequency at which the ICMS-MTCC acquires Park-and-Ride space availability data from the Metro Transit operated Park-and-Ride lots.	User Need 4,5,8,9	ICMS-MTCC	H
MTCC-8-4	ICMS-MTCC shall configure time periods when DMS messages are posted. The ICMS-MTCC shall provide a mechanism for operators/administrators to configure periods of time each day that DMS messages are posted describing Park-and-Ride Lot availability.	User Need 4,5,8,9	ICMS-MTCC	H
MTCC-8-5	ICMS-MTCC shall configure DMS content display. The ICMS-MTCC System shall provide a mechanism for operators/administrators to configure what messages are sent to the DMS displays.	User Need 4,5,8,9	ICMS-MTCC	H
MTCC-8-6	ICMS-MTCC shall configure frequency for DMS message posts The ICMS-MTCC shall provide a mechanism for operators/administrators to configure the frequency that messages are posted to DMS signs.	User Need 4,5,8,9	ICMS-MTCC	H
MTCC-8-7	ICMS-MTCC shall provide an operator interface The ICMS-MTCC shall provide a mechanism for operators to view the information and data acquired by the ICMS-MTCC from the ICMS-Data Hub and from the park-and-ride lot monitors.	User Need 4,5,8,9	ICMS-MTCC	H
MTCC-8-8	ICMS-MTCC shall provide an administrator and operator log-in The ICMS-MTCC shall provide a mechanism for operators and administrators to log in to the system by entering a password.	User Need 4,5,8,9	ICMS-MTCC	H
MTCC-8-9	ICMS-MTCC shall provide an operator interface – security of login The ICMS-MTCC shall provide a mechanism for the system administrator to create user accounts for operators and administrators.	User Need 4,5,8,9	ICMS-MTCC	H
MTCC-8-9	ICMS-MTCC shall maintain security by requiring administrators to login to the system. The ICMS-MTCC System shall require administrators to login to the system before configuring settings.	User Need 4,5,8,9	ICMS-MTCC	H

4.3    ICMS Enhancements to Mn/DOT Traffic Operations (ICMS-Traffic Operations) Functional Requirements

The Mn/DOT Traffic Operations Center will be enhanced as part of the ICMS project. This section describes the requirements for the enhancements to the Mn/DOT Traffic Operations Center. In summary, the Mn/DOT Traffic Operations requirements are presented according to five overall functions to be performed by the operations center specifically for the ICMS (data input and storage, operator interface, message generation and dissemination, field device control, and data output to the ICMS Data Hub). Figure 24 illustrates the ICMS-Traffic Operations System functions and Table 9 includes the ICMS-Traffic Operations System requirements to ease software development and testing.

Figure 24: ICMS-Traffic Operations Functions

Table 9: ICMS-Traffic Operations Requirements

ID	Requirement Description	Source	Allocation	Criticality
TO-1	The ICMS-Traffic Operations System Shall Acquire and Store Messages from the ICMS-Data Hub.	User Need 1,5,6,8	ICMS-Traffic Operations	H
TO-1-1	ICMS-Traffic Operations Acquire and Store Travel Time Data The ICMS-Traffic Operations System shall acquire and store messages describing Travel Times for Arterial Streets and Transit Routes within the ICM Corridor posted by the ICMS-Data Hub.	User Need 1,5,6,9	ICMS-Traffic Operations	H
TO-1-1-1	ICMS-Traffic Operations Acquire and Store Travel Time Data: Data Exchanges The ICMS-Traffic Operations System shall interface with the ICMS-Data Hub System, as per the ICMS-Data Hub Post ICD to acquire and store messages describing Travel Times.	User Need 1,5,6,9	ICMS-Traffic Operations	H
TO-1-1-2	ICMS-Traffic Operations Acquire and Store Travel Time Data: Frequency The ICMS-Traffic Operations System shall acquire and store Travel Time Data from the ICMS-Data Hub at a frequency configurable by an ICMS Traffic Operations Administrator.	User Need 1,5,6,9	ICMS-Traffic Operations	H
TO-1-2	ICMS-Traffic Operations Acquire and Store A,B,C Parking Messages The ICMS-Traffic Operations System shall acquire and store messages describing Parking Availability in the A,B,C Garages posted by the ICMS-Data Hub System so that the ICMS-Traffic Operations system may post these messages on DMS signs controlled by the ICMS-Traffic Operations.	User Need 5,9,10	ICMS-Traffic Operations	H
TO-1-2-1	ICMS-Traffic Operations Acquire and Store A,B,C Parking Messages: Data Exchanges The ICMS-Traffic Operations System shall interface with the ICMS-Data Hub according to the requirements of the ICMS-Data Hub Post ICD to acquire and store messages describing Parking Availability in the A,B,C Garages.	User Need 5,9,10	ICMS-Traffic Operations	H
TO-1-2-2	ICMS-Traffic Operations Acquire and Store A,B,C Parking Messages: Frequency The ICMS-Traffic Operations System shall acquire and store Parking Availability Messages from the ICMS-Data Hub at a frequency configurable by an ICMS Traffic Operations Administrator.	User Need 5,9,10	ICMS-Traffic Operations	H
TO-1-3	ICMS-Traffic Operations Acquire and Store Incident and Event Data The ICMS-Traffic Operations System shall acquire and store from the ICMS-Data Hub System Incident and Event Data (including incidents and events sent to the ICMS-Data Hub from ICMS-EMS and ICMS-Transit Systems) for all roads within the ICM Corridor.	User Need 1,10,11,12,13	ICMS-Traffic Operations	H
TO-1-3-1	ICMS-Traffic Operations Acquire and Store Incident and Event Data: Data Exchanges The ICMS-Traffic Operations System shall interface with the ICMS-Data Hub System as per the ICMS-Data Hub Post ICD to acquire and store Incident and Event Data.	User Need 1, ,11,12,13	ICMS-Traffic Operations	H
TO-1-3-2	ICMS-Traffic Operations Acquire and Store Incident and Event Data: Frequency The ICMS-Traffic Operations System shall acquire and store Incident and Event Data from the ICMS-Data Hub System at a frequency configurable by an ICMS Administrator.	User Need 1,11,12,13	ICMS-Traffic Operations	H
TO-1-3-3	ICMS-Traffic Operations Acquire and Store Incident and Event Data: Location The ICMS-Traffic Operations shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event location.	User Need 1,11,12,13	ICMS-Traffic Operations	H
TO-1-3-4	ICMS-Traffic Operations Acquire and Store Incident and Event Data: Location Detail The ICMS-Traffic Operations shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event location as a geo reference.	User Need 1,11,12,13	ICMS-Traffic Operations	H
TO-1-3-5	ICMS-Traffic Operations Acquire and Store Incident and Event Data: Type The ICMS-Traffic Operations shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident type.	User Need 1,11,12,13	ICMS-Traffic Operations	H
TO-1-3-6	ICMS-Traffic Operations Acquire and Store Incident and Event Data: Time The ICMS-Traffic Operations shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event time elements: start time, vehicle arrival time, and clearance time.	User Need 1,11,12,13	ICMS-Traffic Operations	H
TO-1-4	ICMS-Traffic Operations Acquire and Store park-and-ride space availability data. The ICMS-Traffic Operations System shall acquire and store from the ICMS-Data Hub System park-and-ride space availability data for all park-and-ride facilities within the ICM Corridor.	User Need 4	ICMS-Traffic Operations	H
TO-1-4-1	ICMS-Traffic Operations Acquire and Store Park-and-ride availability data: Data Exchanges The ICMS-Traffic Operations System shall interface with the ICMS-Data Hub System as per the ICMS-Data Hub Post ICD to acquire and store park-and-ride space availability data.	User Need 4	ICMS-Traffic Operations	H
TO-1-4-2	ICMS-Traffic Operations Acquire and Store park-and-ride availability Data: Frequency The ICMS-Traffic Operations System shall acquire and store park-and-ride availability Data from the ICMS-Data Hub System at a frequency configurable by an ICMS Administrator.	User Need 4	ICMS-Traffic Operations	H
TO-1-5	ICMS-Traffic Operations Acquire and Store transit performance data. The ICMS-Traffic Operations System shall acquire and store from the ICMS-Data Hub System transit performance data for transit vehicles operating within the ICM Corridor.	User Need 4	ICMS-Traffic Operations	H
TO-1-5-1	ICMS-Traffic Operations Acquire and Store Park-and-ride availability data: Data Exchanges The ICMS-Traffic Operations System shall interface with the ICMS-Data Hub System as per the ICMS-Data Hub Post ICD to acquire and store transit performance data.	User Need 4	ICMS-Traffic Operations	H
TO-1-5-2	ICMS-Traffic Operations Acquire and Store park-and-ride availability Data: Frequency The ICMS-Traffic Operations System shall acquire and store transit performance data from the ICMS-Data Hub System at a frequency configurable by an ICMS Administrator.	User Need 4	ICMS-Traffic Operations	H
TO-2	The ICMS-Traffic Operations System Shall Generate and Disseminate Messages.	User Need 3	ICMS-Traffic Operations	H
TO-2-1	Generate Travel Times Messages  The ICMS-Traffic Operations System shall generate travel time messages describing conditions on I-394, Hwy 55, and transit routes between park-and-ride lots and downtown Minneapolis using formats and data structures compatible with the Mn/DOT Traffic Operations 511 phone and web information dissemination systems.	User Need 3	ICMS-Traffic Operations	H
TO-2-1-1	Generate Travel Times Messages: Corridor-Wide The ICMS-Traffic Operations System shall generate a travel time message that describes the corridor-wide travel time conditions along I-394, Hwy 55, and transit routes from park-and-ride lots to Downtown Minneapolis, including a comment about park-and-ride space availability.	User Need 3, 4	ICMS-Traffic Operations	H
TO-2-1-2	Generate Travel Times Messages: Corridor-Wide Travel Times Resolution The ICMS-Traffic Operations System shall generate a corridor-wide travel time message that contains travel time estimates as numerical values rounded to the nearest whole minute.	User Need 3	ICMS-Traffic Operations	H
TO-2-1-3	Generate Travel Times Messages: Corridor-Wide Travel Times Expiry The ICMS-Traffic Operations System shall generate travel time messages using stored data that is less than 5 minutes old. If new data is not available, no message shall be generated or disseminated.	User Need 3	ICMS-Traffic Operations	H
TO-2-1-4	Generate Travel Times Messages: Corridor-Wide Travel Times Handling or Missing Data When generating travel time messages, the ICMS-Traffic Operations System shall omit a road in the message in the event that no current data is available to calculate travel time.	User Need 3	ICMS-Traffic Operations	H
TO-2-2	Generate Travel Times Messages: Corridor-Wide Message The ICMS-Traffic Operations System shall generate corridor-wide travel time messages that include a timestamp, travel times and route description.	User Need 3	ICMS-Traffic Operations	H
TO-2-3	Disseminate Travel Time Messages The ICMS-Traffic Operations System shall insert the generated Travel Time Messages into the existing Mn/DOT Traveler Information Systems so the messages are disseminated to the public.	User Need 3	ICMS-Traffic Operations	H
TO-2-4	Malfunctioning Device Reports The ICMS shall create and store reports of any malfunctioning interface.	User Need 18	ICMS-Traffic Operations	H
TO-2-4-1	Malfunctioning Device Reports: Send to Operators The ICMS-Traffic Operations shall send a report of any malfunctioning interface to ICMS-Traffic Operations operators designated during the design process.	User Need 18	ICMS-Traffic Operations	H
TO-2-4-2	Malfunctioning Device Reports: Monitor Send Failures The ICMS-Traffic Operations shall generate a log report every time an interface fails to send data to another system.	User Need 18	ICMS-Traffic Operations	H
TO-2-4-3	Malfunctioning Device Reports: Monitor Receive Failures The ICMS shall generate a log report every time an attempt to acquire data from an external system fails.	User Need 18	ICMS-Traffic Operations	H
TO-2-5	Generate I-394 Advisory Speed Limit Messages The ICMS-Traffic Operations shall create advisory speed messages.	User Need 17	ICMS-Traffic Operations	H
TO-2-5-1	Generate I-394 Advisory Speed Limit Messages: Calculation  The ICMS-Traffic Operations System shall calculate recommended advisory speed limits for each segment of I-394 and generate messages compatibility with the data structure and standards used to post messages to advisory speed signs.	User Need 17	ICMS-Traffic Operations	H
TO-2-5-2	Generate I-394 Advisory Speed Messages: Data Input The ICMS-Traffic Operations System shall calculate advisory speed limits using an algorithm that considers data describing the current flow, speed, and occupancy as well as any additional factors defined during the design process.	User Need 17	ICMS-Traffic Operations	H
TO-2-5-3	Generate I-394 Advisory Speed Messages: Speed Resolution The ICMS-Traffic Operations System shall calculate recommended advisory speed limits in 10 MPH increments.	User Need 17	ICMS-Traffic Operations	H
TO-2-5-4	Generate I-394 Advisory Speed Messages: Trigger Processing The ICMS-Traffic Operations System shall compare the recommended advisory speeds that are calculated against the posted regulatory speed limit (either static or variable if variable is in operation).	User Need 17	ICMS-Traffic Operations	H
TO-2-5-5	Generate I-394 Advisory Speed Messages: Trigger Processing: Alert Notification The ICMS-Traffic Operations shall trigger an alert if the recommended advisory speed limit differs from the current posted speed by more than 10 MPH.	User Need 17	ICMS-Traffic Operations	H
TO-2-5-6	Generate I-394 Advisory Speed Messages: Trigger Processing: Over-ride The ICMS-Traffic Operations operators shall have the ability to manually over-ride the Advisory Speed Limit Message.	User Need 17	ICMS-Traffic Operations	H
TO-3	The ICMS-Traffic Operations System Shall Provide an Operator/Administrator Interface.	User Need 1,11,12,13	ICMS-Traffic Operations	H
TO-3-1	ICMS Display Corridor Conditions to Operators The ICMS-Traffic Operations System shall provide a mechanism for Operators to control systems or field devices.	User Need 1,11,12,13	ICMS-Traffic Operations	H
TO-3-1-1	ICMS Display Corridor Conditions to Operators: ICMS-Traffic Operations Display ICMS Messages The ICMS-Traffic Operations System shall store ICMS-Data Hub messages acquired and display the information contained in the messages to operators using existing display terminals.	User Need 1,11,12,13	ICMS-Traffic Operations	H
TO-3-1-2	I-394 Speed Limit Algorithm: Display to Operators  The ICMS-Traffic Operations shall provide a mechanism for ICMS-Traffic Operations System operators to view the recommended advisory speed limit that the ICMS-Traffic Operations has recommended.	User Need 17	ICMS-Traffic Operations	H
TO-3-1-3	ICMS Allow Operator Override of VSL Device Communication The ICMS-Traffic Operations shall provide a mechanism for operators to override recommended advisory variable speed limit messages from being sent to the sign.	User Need 17	ICMS-Traffic Operations	H
TO-3-2	ICMS Traffic Operations Acquire ICMS Messages The ICMS-Traffic Operations System shall allow administrator/operator control of configurable settings.	User Need 1,6,9	ICMS-Traffic Operations	H
TO-3-2-1	ICMS Traffic Operations Acquire ICMS Messages: Configuration of frequency The ICMS-Traffic Operations System shall provide a mechanism for administrators or operators to configure the frequency at which the ICMS-Traffic Operations System acquires data.	User Need 6	ICMS-Traffic Operations	H
TO-3-2-2	ICMS Traffic Operations Acquire Data from ICMS-Data Hub: Incident and Event Data The ICMS Traffic Operations System shall provide a mechanism for the administrator/operator to configure the frequency at which the ICMS Traffic Operations System acquires Incident and Event messages from the ICMS-Data Hub	User Need 10	ICMS- Traffic Operations	H
TO-3-2-3	ICMS Traffic Operations Acquire Data from ICMS-Data Hub: Travel Time Data The ICMS Traffic Operations System shall provide a mechanism for the administrator/operator to configure the frequency at which the ICMS Traffic Operations System acquires Travel Time messages from the ICMS-Data Hub	User Need 10	ICMS- Traffic Operations	H
TO-3-2-4	ICMS Traffic Operations Acquire Data from ICMS-Data Hub: A,B,C Parking Data The ICMS Traffic Operations System shall provide a mechanism for the administrator/operator to configure the frequency at which the ICMS Traffic Operations System acquires messages describing A,B,C Parking Garage Availability from the ICMS-Data Hub	User Need 10	ICMS- Traffic Operations	H
TO-3-2-5	I-394 Advisory Speed Limit Calculation: Frequency The frequency of Advisory speed limit calculations shall be configurable by an ICMS administrator.	User Need 1	ICMS-Traffic Operations	H
TO-3-3	Provide mechanism to create operator/administrator accounts The ICMS Traffic Operations Systems shall provide a mechanism for system administrators to create user accounts that enable operators and administrators to login to the system.	User Need 1	ICMS-Traffic Operations	H
TO-3-4	ICMS-Traffic Operations shall maintain security by requiring administrators to login to the system. The ICMS-Traffic Operations System shall require administrators to login to the system before configuring settings.	User Need 1	ICMS-Traffic Operations	H
TO-4	The ICMS-Traffic Operations System Shall Control Field Devices.	User Need 10	ICMS-Traffic Operations	H
TO-4-1	Post Messages to Dynamic Message Signs (DMS) The ICMS-Traffic Operations System shall post and verify DMS messages.	User Need 10	ICMS-Traffic Operations	H
TO-4-1-1	Post Messages to Dynamic Message Signs (DMS) The ICMS-Traffic Operations System shall provide a mechanism to allow operators to post messages to travelers on signs along TH 55, and TH 7.	User Need 10	ICMS-Traffic Operations	H
TO-4-1-2	Post Messages on TH 55 The ICMS-Traffic Operations System shall provide a mechanism allowing operators within the RTMC to select the messages to be displayed on DMS signs located on TH 55.	User Need 10	ICMS-Traffic Operations	H
TO-4-1-3	Post Messages on TH 55: RTMC Control The ICMS-Traffic Operations System shall provide a mechanism for operators within the RTMC to post messages on DMS signs on TH 55.	User Need 10	ICMS-Traffic Operations	H
TO-4-1-4	Visual Verification of Messages Posted on TH 55 The ICMS-Traffic Operations System shall provide a mechanism for operators to visually verify the successful implementation of the DMS messages.	User Need 10	ICMS-Traffic Operations	H
TO-4-1-5	Post Messages on TH 7 The ICMS-Traffic Operations System shall provide a mechanism allowing operators within the RTMC to select the messages to be displayed on DMS signs located on TH 7.	User Need 10	ICMS-Traffic Operations	H
TO-4-1-6	Post Messages on TH 7: RTMC Control The ICMS-Traffic Operations System shall provide a mechanism for operators within the RTMC to post messages on DMS signs on TH 7.	User Need 10	ICMS-Traffic Operations	H
TO-4-1-7	Visual Verification of Messages Posted on TH 7 The ICMS-Traffic Operations System shall provide a mechanism allowing operators to visually verify the successful implementation of the DMS messages.	User Need 10	ICMS-Traffic Opera-tions	H
TO-4-2	ICMS-Traffic Operations to Post ABC Garage DMS Message The ICMS-Traffic Operations System shall post messages to DMS signs on the approach to ABC Garages.	User Need 10	ICMS-Traffic Operations	H
TO-4-2-1	ICMS-Traffic Operations to Post ABC Garage DMS Message: Send Message The ICMS-Traffic Operations shall send a message generated by the ICMS-Traffic Operations message generation subsystem to the DMS display on the approach to the ABC garage requesting that the message be displayed immediately upon receiving the DMS message from the ICMS-Traffic Operations.	User Need 10	ICMS-Traffic Operations	H
TO-4-2-2	ICMS-Traffic Operations to Post ABC Garage DMS Message: Protocol The ICMS-Traffic Operations shall interface to the DMS on the approach to the ABC garage according to the requirements of the (National Transportation Communications for ITS Protocol) NTCIP DMS standards.	User Need 10	ICMS-Traffic Operations	H
TO-4-2-3	ICMS-Traffic Operations to Post ABC Garage DMS Message: Remove Messages The ICMS-Traffic Operations shall interface to the DMS on the approach to the ABC garage to remove messages that are no longer active when the ICMS-Traffic Operations no longer receives messages to be posted from the ICMS ABC System.	User Need 10	ICMS-Traffic Operations	H
TO-4-3	I-394 Speed Limit Algorithm The ICMS-Traffic Operations System shall post Variable Speed Limit Messages.	User Need 1	ICMS-Traffic Operations	H
TO-4-3-1	I-394 Speed Limit Algorithm: Automatic Posts The ICMS-Traffic Operations system shall send messages generated by the ICMS-Traffic Operations System to variable speed limit signs on the ICMS Corridor describing the recommended speed limits to be posted on the signs.	User Need 1	ICMS-Traffic Operations	H
TO-4-3-2	I-394 Speed Limit Algorithm: Manual Posts The ICMS-Traffic Operations shall send messages to variable advisory speed limit signs within 5 seconds of message creation.	User Need 1	ICMS-Traffic Operations	H
TO-4-3-3	I-394 Speed Limit Send to Signs: Data Exchanges The variable advisory speed limit message shall adhere to NTCIP standards for protocols and data structure for communication with field devices.	User Need 1	ICMS-Traffic Operations	H
TO-4-3-4	I-394 Speed Limit Send to Signs: Confirmation The ICMS-Traffic Operations shall receive verification from the sign that the advisory speed limit has been posted.	User Need 1	ICMS-Traffic Operations	H
TO-4-3-5	I-394 Speed Limit Send to Signs: Confirmation Latency The ICMS-Traffic Operations shall display the verification from the sign that the advisory speed limit has been posted within 1 second of receipt.	User Need 1	ICMS-Traffic Operations	H
TO-4-3-6	I-394 Speed Limit Allow Operator Override of VSL Device Communication: Default Display The ICMS-Traffic Operations shall display the legally posted speed limit on the signs in the event ICMS-Traffic Operations operators override the VSL Device Communication.	User Need 1	ICMS-Traffic Operations	H
TO-4-4	DOT-TO-Video Sharing The ICMS-Traffic Operations System shall share streaming video to the City of Minneapolis (traffic and EMS), Hennepin County (traffic and EMS), Metro Transit, SouthWest Transit and Plymouth Metrolink  to view current images captured by Mn/DOT operated CCTV cameras along the corridor.	User Need 1, 2	ICMS-Traffic Operations	H
TO-4-4-1	DOT-TO-Video Sharing: accessibility The ICMS-Traffic Operations System shall provide a mechanism where authorized agencies can view streaming video from CCTV cameras using Internet browsers and existing Internet connections.	User Need 1, 2	ICMS-Traffic Operations	H
TO-4-4-2	DOT-TO-Video Sharing: control The ICMS-Traffic Operations System shall not allow agencies who are not located in the Mn/DOT RTMC control Mn/DOT cameras (pan/tilt/zoom).	User Need 1, 2	ICMS-Traffic Operations	H
TO-5	The ICMS-Traffic Operations System Shall Send Data to the ICMS Data Hub System.	User Need 1	ICMS-Traffic Operations	H
TO-5-1	ICMS-Traffic Operations System Send Incident and Event Data The ICMS-Traffic Operations System shall send messages describing Incidents and Events reported in the Traffic Operations System on State Operated Highways within the ICM Corridor to the ICMS-Data Hub System.	User Need 1	ICMS-Traffic Operations	H
TO-5-1-1	ICMS-Traffic Operations Send Incident and Event Data: Data Exchanges The ICMS-Traffic Operations System shall interface to the ICMS-Data Hub according to the requirements of the ICMS-Traffic Operations to ICMS-Data Hub ICD when sending Incident and Event Data.	User Need1	ICMS-Traffic Operations	H
TO-5-1-2	ICMS-Traffic Operations Send Incident and Event Data: Frequency The ICMS-Traffic Operations System shall send Incident and Event Data to the ICMS-Data Hub each time an incident or event is entered into the Reporting System by a Traffic Operations operator.	User Need 1	ICMS-COM-ASG	H
TO-5-1-3	ICMS-Traffic Operations Send Incident and Event Data: No Data Available The ICMS-Traffic Operations System shall send messages to the ICMS-Data Hub indicating “no data available’ if no data is available.	User Need 1	ICMS-COM-ASG	H
TO-5-2	ICMS-Traffic Operations Send Freeway Traffic Data The ICMS-Traffic Operations System shall send messages describing Freeway Traffic Data (volume, occupancy and speed) for those portions of Mn/DOT operated freeways within the ICMS Corridor to the ICMS-Data Hub.	User Need 1 and 2	ICMS-Traffic Operations	H
TO-5-2-1	ICMS-Traffic Operations Send Freeway Traffic Data: Data Exchanges The ICMS-Traffic Operations System shall interface to the ICMS-Data Hub according to the requirements of the ICMS-Traffic Operations to ICMS-Data Hub ICD when sending messages describing Freeway Traffic Data.	User Need1	ICMS-Traffic Operations	H
TO-5-2-2	ICMS-Traffic Operations Send Freeway Traffic Data: Frequency The ICMS-Traffic Operations System shall send messages describing Freeway Traffic Data to the ICMS-Data Hub each time Freeway Traffic Data is acquired by the existing Traffic Operations Center.	User Need 1	ICMS-COM-ASG	H
TO-5-2-3	ICMS-Traffic Operations Send Freeway Traffic Data: No Data Available The ICMS-Traffic Operations System shall send messages to the ICMS-Data Hub indicating “no data available’ if no data is available.	User Need 1	ICMS-COM-ASG	H
TO-5-3	ICMS-Traffic Operations Send Mn/PASS Data The ICMS-Traffic Operations System shall send Mn/PASS Data to the ICMS-Data Hub describing the current travel time and direction of flow in the Mn/Pass Lane.	User Need 2	ICMS-Traffic Operations	H
TO-5-3-1	ICMS-Traffic Operations Send Mn/PASS Data: Data Exchanges The ICMS-Traffic Operations System shall interface to the ICMS-Data Hub according to the requirements of the ICMS-Traffic Operations to ICMS-Data Hub ICD when sending messages describing Mn/PASS Travel Times.	User Need1	ICMS-Traffic Operations	H
TO-5-3-2	ICMS-Traffic Operations Send Mn/PASS Data: Frequency The ICMS-Traffic Operations System shall send messages describing Mn/PASS Travel Times to the ICMS-Data Hub each time a travel time is calculated by the Mn/PASS system.	User Need 1	ICMS-COM-ASG	H
TO-5-3-3	ICMS-Traffic Operations Send Mn/PASS Data: Mn/PASS Not in Operation The ICMS-Traffic Operations System shall send messages to the ICMS-Data Hub indicating “Mn/PASS Not in Operation” if the Mn/PASS lane is not operational.	User Need 1	ICMS-COM-ASG	H

4.4    ICMS Enhancements to the A, B, and C (ICMS-ABC) Garage System Requirements

The ABC Garages will be enhanced as part of the ICMS project. This section describes the requirements for the enhancements to the ABC Garages (referred to as ICMS-ABC). The enhanced ABC will perform four key functions (data input from ICMS Data Hub, field device control, operator/administrator interface, and data output to ICMS Data Hub). Figure 25 illustrates the ICMS-ABC System functions and Table 10 includes the ICMS-ABC System requirements to ease software development and testing.

Figure 25: ICMS-ABC Parking Garages Functions

Table 10: ICMS-ABC Parking Garages Requirements

ID	Requirement Description	Source	Allocation	Criticality
ABC-1	The ICMS-ABC System Shall Acquire and Store Data from the ICMS-Data Hub.	User Need 8,9,10,13	ICMS-ABC	H
ABC-1-1	ICMS-ABC System Acquire and Store Incident and Event Data The ICMS-ABC System shall acquire and store from the ICMS-Data Hub Incident and Event Data (including traffic and weather events) for all roads within the ICM Corridor.	User Need 8,9,10,13	ICMS-ABC System	H
ABC-1-1-1	ICMS-ABC System Acquire and Store Incident and Event Data: Data Exchanges The ICMS-ABC System shall interface with the ICMS-Data Hub as per the ICMS-Data Hub Post ICD to acquire and store Incident and Event Data.	User Need 8,9,10,13	ICMS-ABC System	H
ABC-1-1-2	ICMS-ABC System Acquire and Store Incident and Event Data: Frequency The ICMS-ABC System shall acquire and store Incident and Event Data from the ICMS-Data Hub at a frequency configurable by an ICMS Administrator.	User Need 8,9,10,13	ICMS-ABC System	H
ABC-1-1-3	ICMS-ABC System Acquire and Store Incident and Event Data: Location The ICMS-ABC System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event location.	User Need 8,9,10,13	ICMS-ABC System	H
ABC-1-1-4	ICMS-ABC System Acquire and Store Incident and Event Data: Location Detail The ICMS-ABC System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event location as a geo reference.	User Need 8,9,10,13	ICMS-ABC System	H
ABC-1-1-5	ICMS-ABC System Acquire and Store Incident and Event Data: Type The ICMS-ABC System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident type.	User Need 8,9,10,13	ICMS-ABC System	H
ABC-1-1-6	ICMS-ABC System Acquire and Store Incident and Event Data: Time The ICMS-ABC System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event time elements: start time, vehicle arrival time, and clearance time.	User Need 8,9,10,13	ICMS-ABC System	H
ABC-2	ICMS-ABC System Shall Interface with Field Devices.	User Need 6,8,9	ICMS-ABC System	H
ABC-2-1	ICMS-ABC Close Exit Gates. The ICMS-ABC System shall provide a mechanism for operators of the ABC garages to close exit gates such that vehicles can not pass the gate.	User Need 6	ICMS-ABC System	H
ABC-2-1-1	ICMS-ABC close ABC Garage Exit: access point The ICMS-ABC System shall provide a mechanism for operators of the ABC garages to close the ABC Exit gates on to Westbound I-394.	User Need 6,8,9	ICMS-ABC System	H
ABC-2-1-2	ICMS closes ABC Garage Exit: Activate internal ABC Closure Signs The ICMS-ABC System shall provide a mechanism for operators to activate signage to alert garage patrons that the exit to I-394 is closed.	User Need 6,8,9	ICMS-ABC System	H
ABC-2-1-3	ICMS closes ABC Garage Exit: Exit Gate Closure Performance The ICMS-ABC System shall provide a mechanism for the operator to activate the needed closures and signage within 5 minutes from the decision to close the exits.	User Need 6,8,9	ICMS-ABC System	H
ABC-2-1-4	ICMS closes ABC Garage Exit: Exit Gate Closure Personnel Requirement The ICMS-ABC System shall provide a mechanism where one operator can close all exit gates within the 5 minute parameter, without assistance from others.	User Need 6,8,9	ICMS-ABC System	H
ABC-2-1-5	ICMS closes ABC Garage Exit: Notify Garage Patrons of Closure The ICMS-ABC System shall post a message within the parking garage that describes the current closure of access to I-394.	User Need 6,8,9	ICMS-ABC System	H
ABC-2-1-6	ICMS closes ABC Garage Exit: Post Alternate Route Information The ICMS-ABC System shall post messages describing alternate routes that parking patrons can view before departure.	User Need 6,8,9	ICMS-ABC System	H
ABC-2-2	Disseminate Traveler Information in ABC Garages The ICMS-ABC System shall generate and display messages or map images on kiosks in the ABC garage describing corridor conditions to travelers approaching their vehicles.	User Need 6,8,9	ICMS-ABC System	H
ABC-2-2-1	Disseminate Traveler Information in ABC Garages: Visual Display - Kiosk The ICMS-ABC System shall post messages to Internet based kiosks located in the ABC garages.	User Need 6,8,9	ICMS-ABC System	H
ABC-2-2-2	Disseminate Traveler Information in ABC Garages: Impending Event Traffic Alerts The ICMS-ABC System shall display information to travelers in the garages about special events that have been acquired by the A,B,C Garage System.	User Need 6,8,9	ICMS-ABC System	H
ABC-2-2-3	Disseminate Traveler Information in ABC Garages: Parameters of Impending Event Traffic Alerts The ICMS-ABC System shall display notices of planned events and parking impacts acquired by the ICMS-ABC System beginning at 12:01 AM on the day of the planned event.	User Need 6,8,9	ICMS-ABC System	H
ABC-3	ICMS-ABC System shall send Messages to the ICMS-Data Hub System.	User Need 5,8,9	ICMS-ABC System	H
ABC-3-1	ICMS-ABC Send Parking Message to ICMS-Data Hub The ICMS-ABC System shall send message to the ICMS Data Hub System describing the parking space availability of each garage to the ICMS Data Hub.	User Need 5,8,9	ICMS-ABC System	H
ABC-3-1-1	ICMS-ABC Send Parking Message to ICMS-Data Hub: Data Exchanges The ICMS-ABC System shall interface with the ICMS Data-Hub System according to the ICMS-ABC to ICMS-Data Hub ICD to send Parking Messages.	User Need 5,8,9	ICMS-ABC System	H
ABC-3-1-2	ICMS-ABC Send Parking Message to ICMS-Data Hub: Frequency The ICMS-ABC System shall send parking messages to the ICMS-Data Hub at a schedule frequency configurable by an ICMS Administrator.	User Need 5,8,9	ICMS-ABC System	H
ABC-4	The ICMS-ABC System Shall Provide a Mechanism for Operators/Administrators to Enter Configurable Settings from an Internet Accessible Workstation.	User Need 5,8,9	ICMS-ABC System	H
ABC-4-1	ICMS-ABC shall configure frequency of sending parking messages to ICMS-Data Hub. The ICMS-ABC System shall provide a mechanism for operators/administrators to configure the frequency at which the parking messages are sent to the ICMS-Data Hub.	User Need 5,8,9	ICMS-ABC System	H
ABC-4-2	ICMS-ABC shall configure frequency of acquiring incident and event messages from the ICMS-Data Hub. The ICMS-ABC System shall provide a mechanism for operators/administrators to configure the frequency at which the ICMS-ABC System acquires messages describing incidents and special events form the ICMS-Data Hub.	User Need 5,8,9	ICMS-ABC System	H
ABC-4-3	ICMS-ABC shall provide a mechanism to create user accounts. The ICMS-ABC System shall provide a mechanism for system administrators to create user accounts for operators and administrators.	User Need 5,8,9	ICMS-ABC System	H
ABC-4-4	ICMS-ABC shall maintain security by requiring administrators to login to the system. The ICMS-ABC System shall require administrators to login to the system before configuring settings.	User Need 5,8,9	ICMS-ABC System	H

4.5    ICMS Enhancements to Mn/DOT Arterial Signals Group (ICMS-Mn/DOT-ASG) Functional Requirements

The Mn/DOT Arterial Signals Group (ASG) System will be enhanced as part of the ICMS project. This section describes the requirements for the enhancements to the ASG System (referred to as ICMS-Mn/DOT-ASG System or ICMS-Mn/DOT-ASG). The enhanced ASG System will perform five key functions (data input from ICMS Data Hub, interface with field device, display data to operator, calculate arterial travel times, and send data to ICMS-Data Hub System). Figure 26 illustrates the ICMS-Mn/DOT-ASG System functions and Table 11 includes the ICMS-Mn/DOT-ASG System requirements to ease software development and testing.

Figure 26: ICMS-Mn/DOT-ASG Functions

Table 11: ICMS-Mn/DOT-ASG Requirements

ID	Requirement Description	Source	Allocation	Criticality
DOT-ASG-1	The ICMS-Mn/DOT-ASG System Shall Acquire and Store Data from the ICMS-Data Hub.	User Need 2,5,17	ICMS-Mn/DOT-ASG	H
DOT-ASG-1-1	ICMS-Mn/DOT-ASG Acquire and Store Incident and Event Data The ICMS-Mn/DOT-ASG System shall acquire and store from the ICMS-Data Hub Incident and Event Data for all roads within the ICM Corridor.	User Need 2,5,17	ICMS-Mn/DOT-ASG	H
DOT-ASG-1-1-1	ICMS-Mn/DOT-ASG Acquire and Store Incident and Event Data: Data Exchanges The ICMS-Mn/DOT-ASG System shall interface with the ICMS-Data Hub as per the ICMS-Data Hub Post ICD to acquire and store Incident and Event Data.	User Need 2,5,17	ICMS-Mn/DOT-ASG	H
DOT-ASG-1-1-2	ICMS-Mn/DOT-ASG Acquire and Store Incident and Event Data: Frequency The ICMS-Mn/DOT-ASG System shall acquire and store Incident and Event Data from the ICMS-Data Hub at a frequency configurable by an ICMS Administrator.	User Need 2,5,17	ICMS-Mn/DOT-ASG	H
DOT-ASG-1-1-3	ICMS-Mn/DOT-ASG Acquire and Store Incident and Event Data: Location The ICMS-Mn/DOT-ASG System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event location.	User Need 2,5,17	ICMS-Mn/DOT-ASG	H
DOT-ASG-1-1-4	ICMS-Mn/DOT-ASG Acquire and Store Incident and Event Data: Location Detail The ICMS-Mn/DOT-ASG System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event location as a geo reference.	User Need 2,5,17	ICMS-Mn/DOT-ASG	H
DOT-ASG-1-1-5	ICMS-Mn/DOT-ASG Acquire and Store Incident and Event Data: Type The ICMS-Mn/DOT-ASG System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident type.	User Need 2,5,17	ICMS-Mn/DOT-ASG	H
DOT-ASG-1-1-6	ICMS-Mn/DOT-ASG Acquire and Store Incident and Event Data: Time The ICMS-Mn/DOT-ASG System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event time elements: start time, vehicle arrival time, and clearance time.	User Need 2,5,17	ICMS-Mn/DOT-ASG	H
DOT-ASG-1-2	ICMS-Mn/DOT-ASG Acquire and Store Freeway Traffic Data The ICMS-Mn/DOT-ASG System shall acquire and store from the ICMS-Data Hub Freeway Traffic Data.	User Need 17	ICMS-Mn/DOT-ASG	H
DOT-ASG-1-2-1	ICMS-Mn/DOT-ASG Acquire and Store Freeway Traffic Data: Data Exchanges The ICMS-Mn/DOT-ASG System shall interface with the ICMS-Data Hub as per the ICMS-Data Hub Post ICD to acquire and store Freeway Traffic Data in order to be able to display this data to arterial signals operators to assist in selecting signal timing plans.	User Need 17	ICMS-Mn/DOT-ASG	H
DOT-ASG-1-2-2	ICMS-Mn/DOT-ASG Acquire and Store Freeway Traffic Data: Frequency The ICMS-Mn/DOT-ASG System shall acquire and store Freeway Traffic Data from the ICMS-Data Hub at a frequency configurable by an ICMS Administrator.	User Need 17	ICMS-Mn/DOT-ASG	H
DOT-ASG-1-2-3	ICMS-Mn/DOT-ASG Acquire and Store Freeway Traffic Data: Traffic Details The ICMS-Mn/DOT-ASG System shall acquire and store Freeway Traffic Data from the ICMS-Data Hub describing volume, occupancy, and speed data for sensor stations along: The I-394 mainline and I-394 ramps I-494 Hwy 100 Hwy 169.	User Need 17	ICMS-Mn/DOT-ASG	H
DOT-ASG-1-2-4	ICMS-Mn/DOT-ASG Acquire and Freeway Traffic Data: Travel Times The ICMS-Mn/DOT-ASG System shall acquire and store messages describing Freeway Travel Times from the ICMS-Data Hub.	User Need 17	ICMS-Mn/DOT-ASG	H
DOT-ASG-1-3	ICMS-Mn/DOT-ASG Acquire and Store Special Event and Incident Signal Timing Plans Data The ICMS-Mn/DOT-ASG System shall acquire and store Special Event and Incident Signal Timing Plans that have been posted to the ICMS-Data Hub by other agencies operating arterial traffic signals (Hennepin County and City of Minneapolis) from the ICMS-Data Hub.	User Need 17	ICMS-Mn/DOT-ASG	H
DOT-ASG-1-3-1	ICMS-Mn/DOT-ASG Acquire and Store Special Event and Incident Signal Timing Plans Data: Data Exchanges The ICMS-Mn/DOT-ASG System shall interface with the ICMS-Data Hub Post as per the ICMS-Data Hub Post ICD to acquire and store Special Events and Incident Signal Timing Plans Data.	User Need 11,12,17	ICMS-Mn/DOT-ASG	H
DOT-ASG-1-3-2	ICMS-Mn/DOT-ASG Acquire and Store Special Event and Incident Signal Timing Plans Data: Frequency The ICMS-Mn/DOT-ASG System shall acquire and store Special Event and Incident Signal Timing Plans Data from the ICMS-Data Hub at a frequency configurable by an ICMS Administrator.	User Need 11,12,17	ICMS-Mn/DOT-ASG	H
DOT-ASG-1-3-3	ICMS-Mn/DOT-ASG Acquire and Store Special Event and Incident Signal Timing Plans Data: Selected Signal Timing Plan The ICMS-Mn/DOT-ASG System shall acquire and store messages from the ICMS-Data Hub identifying which signal timing plan was implemented at signals within the ICM corridor.	User Need 11,12,17	ICMS-Mn/DOT-ASG	H
DOT-ASG-1-3-4	ICMS-Mn/DOT-ASG Acquire and Store Special Event and Incident Signal Timing Plans Data: Time Implemented The ICMS-Mn/DOT-ASG System shall acquire and store messages from the ICMS-Data Hub identifying the time a signal timing plan was implemented.	User Need 11,12,17	ICMS-Mn/DOT-ASG	H
DOT-ASG-1-3-5	ICMS-Mn/DOT-ASG Acquire and Store Special Events and Incident Signal Timing Plans Data: Time Deactivated The ICMS-Mn/DOT-ASG System shall acquire and messages from the ICMS-Data Hub identifying the time a signal timing plan was deactivated.	User Need 11,12,17	ICMS-Mn/DOT-ASG	H
DOT-ASG-2	The ICMS-Mn/DOT-ASG System shall Calculate Arterial Travel Times.	User Need 1,9	ICMS-Mn/DOT-ASG	H
DOT-ASG-2-1	ICMS-Mn/DOT-ASG Calculate Arterial Travel Times: Locations The ICMS-Mn/DOT-ASG System shall calculate arterial travel times between downtown Minneapolis and intersections with I-494, Hwy 169, and Hwy 100.	User Need 1,9	ICMS-Mn/DOT-ASG	H
DOT-ASG-2-2	ICMS-Mn/DOT-ASG Calculate Arterial Travel Times: Categorize travel conditions The ICMS-Mn/DOT-ASG System shall calculate arterial performance and classify segments of Hwy 55 into either free flowing, slow, or congested.	User Need 1,9	ICMS-Mn/DOT-ASG	H
DOT-ASG-2-3	ICMS-Mn/DOT-ASG Calculate Arterial Travel Times: Frequency The ICMS-Mn/DOT-ASG System shall calculate arterial travel times at a frequency configurable by an ICMS Administrator.	User Need 1,9	ICMS-Mn/DOT-ASG	H
DOT-ASG-3	The ICMS-Mn/DOT-ASG System shall Display Data to ASG Operators.	User Need 1,2,17	ICMS-Mn/DOT-ASG	H
DOT-ASG-3-1	ICMS-Mn/DOT-ASG Mechanism to Display Arterial and Freeway Incident Data The ICMS-Mn/DOT-ASG System shall provide a mechanism for Mn/DOT ASG Operators to view Incident Data acquired and stored in the ICMS-Mn/DOT-ASG.	User Need 1,2,17	ICMS-Mn/DOT-ASG	H
DOT-ASG-3-2	ICMS-Mn/DOT-ASG Mechanism to Display Arterial and Freeway Volume Data The ICMS-Mn/DOT-ASG System shall provide a mechanism for Mn/DOT ASG Operators to view arterial and freeway traffic volume data acquired and stored in the ICMS-Mn/DOT-ASG.	User Need 1,2,17	ICMS-Mn/DOT-ASG	H
DOT-ASG-3-3	ICMS-Mn/DOT-ASG Mechanism to Display Freeway Time Data The ICMS-Mn/DOT-ASG System shall provide a mechanism for Mn/DOT ASG Operators to view freeway Travel Time Data acquired and stored in the ICMS-Mn/DOT-ASG.	User Need 1,2,17	ICMS-Mn/DOT-ASG	H
DOT-ASG-3-4	ICMS-Mn/DOT-ASG Mechanism to Display Arterial Travel Time Data The ICMS-Mn/DOT-ASG System shall provide a mechanism for Mn/DOT ASG Operators to view arterial Travel Time Data calculated in the ICMS-Mn/DOT-ASG.	User Need 1,2,17	ICMS-Mn/DOT-ASG	H
DOT-ASG-3-5	ICMS-Mn/DOT-ASG Mechanism to Display Signal Timing Data The ICMS-Mn/DOT-ASG System shall provide a mechanism for Mn/DOT ASG Operators to view signal timing plans implemented on signals controlled by the City of Minneapolis and Hennepin County to coordinate timing plans on Mn/DOT intersections.	User Need 1,2,17	ICMS-Mn/DOT-ASG	H
DOT-ASG-4	The ICMS-Mn/DOT-ASG System shall Interface with Field Devices.	User Need 2,10,17	ICMS-Mn/DOT-ASG	H
DOT-ASG-4-1	The ICMS-Mn/DOT-ASG System shall Interface with the Traffic Signal Controllers.	User Need 17	ICMS-Mn/DOT-ASG	H
DOT-ASG-4-1-1	ICMS-Mn/DOT-ASG Acquire and Store Signal Phasing and Volume Data The ICMS-Mn/DOT-ASG System shall acquire and store signal phasing and traffic volume data from the Mn/DOT operated traffic signal controllers on Hwy 55 and Hwy 7.	User Need 17	ICMS-Mn/DOT-ASG	H
DOT-ASG-4-1-2	ICMS-Mn/DOT-ASG Store Special Event and Incident Signal Timing Plans The ICMS-Mn/DOT-ASG System shall store pre-created special event and incident signal timing plans.	User Need 17	ICMS-Mn/DOT-ASG	H
DOT-ASG-4-1-3	ICMS-Mn/DOT-ASG Store Special Event and Incident Signal Timing Plans: Location The ICMS-Mn/DOT-ASG System shall store pre-created special event and incident signal timing plans for Mn/DOT operated intersections along Hwy 55 and Hwy 7.	User Need 17	ICMS-Mn/DOT-ASG	H
DOT-ASG-4-1-4	ICMS-Mn/DOT-ASG Mechanism to Select and Download Special Event and Incident Signal Timing Plans The ICMS-Mn/DOT-ASG System shall provide a mechanism for Mn/DOT ASG Operators to select pre-defined special event and incident signal timing plans to be downloaded to in-field traffic signal controllers.	User Need 17	ICMS-Mn/DOT-ASG	H
DOT-ASG-4-2	The ICMS-Mn/DOT-ASG System shall Interface with DMS.	User Need 10	ICMS-Mn/DOT-ASG	H
DOT-ASG-4-2-1	ICMS-Mn/DOT-ASG Mechanism to Operate DMS The ICMS-Mn/DOT-ASG System shall provide a mechanism for Mn/DOT ASG Operators to post messages on arterial DMS.	User Need 10	ICMS-Mn/DOT-ASG	H
DOT-ASG-4-2-2	ICMS-Mn/DOT-ASG Mechanism to View DMS messages posted The ICMS-Mn/DOT-ASG System shall provide a mechanism for Mn/DOT ASG Operators to view current messages posted on arterial DMS.	User Need 10	ICMS-Mn/DOT-ASG	H
DOT-ASG-4-3	The ICMS-Mn/DOT-ASG System shall Interface with Closed Circuit Television.	User Need 2	ICMS-Mn/DOT-ASG	H
DOT-ASG-4-3-1	ICMS-Mn/DOT-ASG Mechanism to View and Operate Visual Surveillance The ICMS-Mn/DOT-ASG System shall provide a mechanism for Mn/DOT ASG Operators to view and operate visual surveillance on the mainline approaches at each signalized intersection on Hwy 55 and Hwy 7.	User Need 2	ICMS-Mn/DOT-ASG	H
DOT-ASG-4-3-2	ICMS-Mn/DOT ASG Provide Visual Verification of Messages Posted on TH 55 The ICMS-Mn/DOT-ASG System shall provide a mechanism for Mn/DOT ASG Operators to visually verify the successful implementation of messages posted to travelers on Hwy 55 and Hwy 7.	User Need 10	ICMS-Mn/DOT-ASG	H
DOT-ASG-4-3-3	ICMS-Mn/DOT-ASG Provide Visual Monitoring of Signal Timing Plans The ICMS-Mn/DOT-ASG System shall provide visual monitoring of traffic conditions as special event and incident signal timing plans are implemented.	User Need 17	ICMS-Mn/DOT-ASG	H
DOT-ASG-4-4	DOT-ASG-Video Sharing The ICMS-Mn/DOT-ASG System shall share streaming video to the City of Minneapolis (traffic and EMS), Hennepin County, Metro Transit, SouthWest Transit and Plymouth Metrolink  to view current images captured by  CCTV cameras along Hwy 55 and Hwy 7.	User Need 1, 2	ICMS-Mn/DOT-ASG	H
DOT-ASG-4-4-1	DOT-ASG-Video Sharing: accessibility The ICMS-Mn/DOT-ASG System shall provide a mechanism where authorized agencies can view streaming video from CCTV cameras using Internet browsers and existing Internet connections.	User Need 1, 2	ICMS-Mn/DOT-ASG	H
DOT-ASG-4-4-2	DOT-ASG-Video Sharing: control The ICMS-Mn/DOT-ASG System shall not allow other agencies to control Mn/DOT cameras (pan/tilt/zoom).	User Need 1, 2	ICMS-Mn/DOT-ASG	H
DOT-ASG-5	The ICMS-Mn/DOT-ASG System shall Send Data to the ICMS-Data Hub.	User Need 1,2,17	ICMS-Mn/DOT-ASG	H
DOT-ASG-5-1	ICMS-Mn/DOT-ASG Send Arterial Travel Time Data: Travel Times The ICMS-Mn/DOT-ASG System shall send to the ICMS-Data Hub messages describing real-time travel times along Hwy 55.	User Need 1,2	ICMS-Mn/DOT-ASG	H
DOT-ASG-5-1-1	ICMS-Mn/DOT-ASG Send Travel Time Messages to the ICMS-Data Hub: Data Exchanges The ICMS-Mn/DOT-ASG System shall interface with the ICMS-Data Hub ICD according to the requirements of the ICMS-ASG to ICMS-Data Hub ICD to send Travel Time messages.	User Need 2	ICMS-Mn/DOT-ASG	H
DOT-ASG-5-1-2	ICMS-Mn/DOT-ASG System Send Arterial Travel Times: Frequency The ICMS-Mn/DOT-ASG System shall send messages describing Travel Times to the ICMS-Data Hub each time arterial traffic data is acquired from the signal controllers.	User Need 1	ICMS-Mn/DOT-ASG	H
DOT-ASG-5-1-3	ICMS-Mn/DOT-ASG Send Arterial Traffic Data: No Data The ICMS-Mn/DOT-ASG System shall send messages to the ICMS-Data Hub indicating “no data available’ if no Travel Time data is available.	User Need 1	ICMS-Mn/DOT-ASG	H
DOT-ASG-5-2	ICMS-Mn/DOT-ASG Send Special Event and Incident Signal Timing Plans Data The ICMS-Mn/DOT-ASG System shall send to the ICMS-Data Hub Special Event and Incident Signal Timing Plans implemented at each Mn/DOT operated signal.	User Need 17	ICMS-Mn/DOT-ASG	H
DOT-ASG-5-2-1	ICMS-Mn/DOT-ASG Send Special Event and Incident Signal Timing Plans Data to the ICMS-Data Hub: Data Exchanges The ICMS-Mn/DOT-ASG System shall interface with the ICMS-Data Hub ICD according to the requirements of the ICMS-ASG to ICMS-Data Hub ICD to send Travel Time messages.	User Need 2	ICMS-Mn/DOT-ASG	H
DOT-ASG-5-2-2	ICMS-Mn/DOT-ASG Send Special Event and Incident Signal Timing Plans Data: Frequency The ICMS-Mn/DOT-ASG System shall send Special Event and Incident Signal Timing Plans Data to the ICMS-Data Hub each time a signal timing plan is downloaded to a signalized intersection along the corridor.	User Need 11	ICMS-Mn/DOT-ASG	H
DOT-ASG-5-2-3	ICMS-Mn/DOT-ASG Send Special Event and Incident Signal Timing Plans Data: Selected Signal Timing Plan The ICMS-Mn/DOT-ASG System shall send Special Event and Incident Signal Timing Plans Data to the ICMS-Data Hub identifying which signal timing plan was implemented.	User Need 11	ICMS-Mn/DOT-ASG	H
DOT-ASG-5-2-4	ICMS-Mn/DOT-ASG Send Special Event and Incident Signal Timing Plans Data: Time Implemented The ICMS-Mn/DOT-ASG System shall send Special Event and Incident Signal Plans Data to the ICMS-Data Hub identifying the time a signal timing plan was implemented.	User Need 11	ICMS-Mn/DOT-ASG	H
DOT-ASG-5-2-5	ICMS-Mn/DOT-ASG Send Special Event and Incident Signal Timing Plans Data: Time Deactivated The ICMS-Mn/DOT-ASG System shall send Special Event and Incident Signal Timing Plans Data to the ICMS-Data Hub identifying the time a signal timing plan was deactivated.	User Need 11	ICMS-Mn/DOT-ASG	H

4.6    ICMS Enhancements to Hennepin County Arterial Signals Group (ICMS-HENN-ASG) Functional Requirements

The Hennepin County (HENN) Arterial Signals Group (ASG) System will be enhanced as part of the ICMS project. This section describes the requirements for the enhancements to the system (referred to as ICMS-HENN-ASG System or ICMS-HENN-ASG). The enhanced ASG System will perform four key functions (data input from ICMS Data Hub, interface with field device, display data to operator, and send data to ICMS-Data Hub System). Figure 27 illustrates the ICMS-HENN-ASG System functions and Table 12 includes the ICMS-HENN-ASG System requirements to ease software development and testing.

Figure 27: ICMS-HENN-ASG Functions

Table 12: ICMS-HENN-ASG Requirements

ID	Requirement Description	Source	Allocation	Criticality
HENN-ASG-1	The ICMS-HENN-ASG System Shall Acquire and Store Data from the ICMS-Data Hub.	User Need 2,5,17	ICMS-HENN-ASG	H
HENN-ASG-1-1	ICMS-HENN-ASG Acquire and Store Incident and Event Data The ICMS-HENN-ASG System shall acquire and store from the ICMS-Data Hub Incident and Event Data for all roads within the ICM Corridor.	User Need 2,5,17	ICMS-HENN-ASG	H
HENN-ASG-1-1-1	ICMS-HENN-ASG Acquire and Store Incident and Event Data: Data Exchanges The ICMS-HENN-ASG System shall interface with the ICMS-Data Hub as per the ICMS-Data Hub Post ICD to acquire and store Incident and Event Data.	User Need 2,5,17	ICMS-HENN-ASG	H
HENN-ASG-1-1-2	ICMS-HENN-ASG Acquire and Store Incident and Event Data: Frequency The ICMS-HENN-ASG System shall acquire and store Incident and Event Data from the ICMS-Data Hub at a frequency configurable by an ICMS Administrator.	User Need 2,5,17	ICMS-HENN-ASG	H
HENN-ASG-1-1-3	ICMS-HENN-ASG Acquire and Store Incident and Event Data: Location The ICMS-HENN-ASG System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event location.	User Need 2,5,17	ICMS-HENN-ASG	H
HENN-ASG-1-1-4	ICMS-HENN-ASG Acquire and Store Incident and Event Data: Location Detail The ICMS-HENN-ASG System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event location as a geo reference.	User Need 2,5,17	ICMS-HENN-ASG	H
HENN-ASG-1-1-5	ICMS-HENN-ASG Acquire and Store Incident and Event Data: Type The ICMS-HENN-ASG System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident type.	User Need 2,5,17	ICMS-HENN-ASG	H
HENN-ASG-1-1-6	ICMS-HENN-ASG Acquire and Store Incident and Event Data: Time The ICMS-HENN-ASG System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event time elements: start time, vehicle arrival time, and clearance time.	User Need 2,5,17	ICMS-HENN-ASG	H
HENN-ASG-1-2	ICMS-HENN-ASG Acquire and Store Freeway Traffic Data The ICMS-HENN-ASG System shall acquire and store from the ICMS-Data Hub Freeway Traffic Data.	User Need 17	ICMS-HENN-ASG	H
HENN-ASG-1-2-1	ICMS-HENN-ASG Acquire and Store Freeway Traffic Data: Data Exchanges The ICMS-HENN-ASG System shall interface with the ICMS-Data Hub as per the ICMS-Data Hub Post ICD to acquire and store Freeway Traffic Data.	User Need 17	ICMS-HENN-ASG	H
HENN-ASG-1-2-2	ICMS-HENN-ASG Acquire and Store Freeway Traffic Data: Frequency The ICMS-HENN-ASG System shall acquire and store Freeway Traffic Data from the ICMS-Data Hub at a frequency configurable by an ICMS Administrator.	User Need 17	ICMS-HENN-ASG	H
HENN-ASG-1-2-3	ICMS-HENN-ASG Acquire and Store Freeway Traffic Data: Traffic Details The ICMS-HENN-ASG System shall acquire and store Freeway Traffic Data from the ICMS-Data Hub describing volume, occupancy, and speed data for sensor stations along: The I-394 mainline and I-394 ramps I-494 Hwy 100 Hwy 169.	User Need 17	ICMS-HENN-ASG	H
HENN-ASG-1-2-4	ICMS-HENN-ASG Acquire and Freeway Traffic Data: Travel Times The ICMS-HENN-ASG System shall acquire and store messages describing Freeway Travel Times from the ICMS-Data Hub.	User Need 17	ICMS-HENN-ASG	H
HENN-ASG-1-3	ICMS-HENN-ASG Acquire and Store Special Event and Incident Signal Timing Plans Data The ICMS-HENN-ASG System shall acquire and store Special Event and Incident Signal Timing Plans Data from the ICMS-Data Hub.	User Need 17	ICMS-HENN-ASG	H
HENN-ASG-1-3-1	ICMS-HENN-ASG Acquire and Store Special Event and Incident Signal Timing Plans Data: Data Exchanges The ICMS-HENN-ASG System shall interface with the ICMS-Data Hub Post as per the ICMS-Data Hub Post ICD to acquire and store Special Events and Incident Signal Timing Plans Data.	User Need 11,12,17	ICMS-HENN-ASG	H
HENN-ASG-1-3-2	ICMS-HENN-ASG Acquire and Store Special Event and Incident Signal Timing Plans Data: Frequency The ICMS-HENN-ASG System shall acquire and store Special Event and Incident Signal Timing Plans Data from the ICMS-Data Hub at a frequency configurable by an ICMS Administrator.	User Need 11,12,17	ICMS-HENN-ASG	H
HENN-ASG-1-3-3	ICMS-HENN-ASG Acquire and Store Special Event and Incident Signal Timing Plans Data: Selected Signal Timing Plan The ICMS-HENN-ASG System shall acquire and store messages from the ICMS-Data Hub identifying which signal timing plan was implemented at signals within the ICM corridor.	User Need 11,12,17	ICMS-HENN-ASG	H
1-3-4	ICMS-HENN-ASG Acquire and Store Special Event and Incident Signal Timing Plans Data: Time Implemented The ICMS-HENN-ASG System shall acquire and store messages from the ICMS-Data Hub identifying the time a signal timing plan was implemented.	User Need 11,12,17	ICMS-HENN-ASG	H
HENN-ASG-1-3-5	ICMS-HENN-ASG Acquire and Store Special Events and Incident Signal Timing Plans Data: Time Deactivated The ICMS-HENN-ASG System shall acquire and messages from the ICMS-Data Hub identifying the time a signal timing plan was deactivated.	User Need 11,12,17	ICMS-HENN-ASG	H
HENN-ASG-2	The ICMS-HENN-ASG System shall Display Data to Hennepin County ASG Operators.	User Need 1,2,17	ICMS-HENN-ASG	H
HENN-ASG-2-1	ICMS-HENN-ASG Mechanism to Display Arterial and Freeway Incident Data The ICMS-HENN-ASG System shall provide a mechanism for Hennepin County ASG Operators to view Incident Data acquired and stored in the ICMS-HENN-ASG on arterials and freeways within the ICM Corridor.	User Need 1,2,17	ICMS-HENN-ASG	H
HENN-ASG-2-2	ICMS-HENN-ASG Mechanism to Display Arterial and Freeway Volume Data The ICMS-HENN-ASG System shall provide a mechanism for Hennepin County ASG Operators to view Volume Data acquired and stored in the ICMS-HENN-ASG on arterials and freeways within the ICM Corridor.	User Need 1,2,17	ICMS-HENN-ASG	H
HENN-ASG-2-3	ICMS-HENN-ASG Mechanism to Display Arterial and Freeway Travel Time Data The ICMS-HENN-ASG System shall provide a mechanism for Hennepin County ASG Operators to view Travel Time Data acquired and stored in the ICMS-HENN-ASG on arterials and freeways within the ICM Corridor.	User Need 1,2,17	ICMS-HENN-ASG	H
HENN-ASG-2-4	ICMS-HENN-ASG Mechanism to Display Signal Timing Data The ICMS-HENN-ASG System shall provide a mechanism for Hennepin County ASG Operators to view signal timing plans implemented on signals controlled by the City of Minneapolis and Mn/DOT to coordinate timing plans on county maintained intersections.	User Need 1,2,17	ICMS-HENN-ASG	H
HENN-ASG-3	The ICMS-HENN-ASG System shall Interface with Field Devices.	User Need 2,10,17	ICMS-HENN-ASG	H
HENN-ASG-3-1	The ICMS-HENN-ASG shall Interface with the Traffic Signal Controllers.	User Need 17	ICMS-HENN-ASG	H
HENN-ASG-3-1-1	ICMS-HENN-ASG Acquire and Store Signal Phasing and Volume Data The ICMS-HENN-ASG System shall acquire and store signal phasing and traffic volume data from the Hennepin County operated traffic signal controllers.	User Need 17	ICMS-HENN-ASG	M
HENN-ASG-3-1-2	ICMS-HENN-ASG Store Special Event and Incident Signal Timing Plans The ICMS-HENN-ASG System shall store pre-created special event and incident Hennepin County signal timing plans.	User Need 17	ICMS-HENN-ASG	M
HENN-ASG-3-1-2-1	ICMS-HENN-ASG Store Special Event and Incident Signal Timing Plans: Location The ICMS-HENN-ASG System shall store pre-created special event and incident signal timing plans for Hennepin County operated intersections.	User Need 17	ICMS-HENN-ASG	M
HENN-ASG-3-1-3	ICMS-HENN-ASG Mechanism to Select and Download Special Event and Incident Signal Timing Plans The ICMS-HENN-ASG System shall provide a mechanism for Hennepin County ASG Operators to select pre-defined special event and incident signal timing plans to be downloaded to in-field traffic signal controllers.	User Need 17	ICMS-HENN-ASG	M
HENN-ASG-3-2	The ICMS-HENN-ASG System shall Interface with Dynamic Message Signs (DMS).	User Need 10	ICMS-HENN-ASG	M
HENN-ASG-3-2-1	ICMS-HENN-ASG Mechanism to Operate DMS The ICMS-HENN-ASG System shall provide a mechanism for Hennepin County ASG Operators to post messages on arterial DMS.	User Need 10	ICMS-HENN-ASG	M
HENN-ASG-3-2-2	ICMS-HENN-ASG Mechanism to View DMS messages posted The ICMS-HENN-ASG System shall provide a mechanism for Hennepin County ASG Operators to view current messages posted on arterial DMS.	User Need 10	ICMS-HENN-ASG	M
HENN-ASG-3-3	The ICMS-HENN-ASG System shall Interface with Closed Circuit Television.	User Need 2	ICMS-HENN-ASG	M
HENN-ASG-3-3-1	ICMS-HENN-ASG Mechanism to View and Operate Visual Surveillance The ICMS-HENN-ASG System shall provide a mechanism for Hennepin County ASG Operators to view and operate visual surveillance on the mainline approaches at each signalized intersection on Hwy 55 and Hwy 7.	User Need 2	ICMS-HENN-ASG	M
HENN-ASG-3-3-2	ICMS-Mn/DOT ASG Provide Visual Verification of Messages Posted on TH 55 The ICMS-HENN-ASG System shall provide a mechanism for Hennepin County ASG Operators to visually verify the successful implementation of messages posted to travelers on Hwy 55 and Hwy 7.	User Need 10	ICMS-HENN-ASG	M
HENN-ASG-3-3-3	ICMS-HENN-ASG Provide Visual Monitoring of Signal Timing Plans The ICMS-HENN-ASG System shall provide visual monitoring of traffic conditions as special event and incident signal timing plans are implemented.	User Need 17	ICMS-HENN-ASG	M
HENN-ASG-3-4	HENN-Video Sharing The ICMS-HENN-ASG System shall share streaming video to the City of Minneapolis (traffic and EMS), Mn/DOT, Metro Transit, SouthWest Transit and Plymouth Metrolink  to view current images captured by county operated CCTV cameras along the corridor.	User Need 1, 2	ICMS-HENN-ASG	H
HENN-ASG-3-4-1	HENN-Video Sharing: accessibility The ICMS-HENN-ASG System shall provide a mechanism where authorized agencies can view streaming video from CCTV cameras using Internet browsers and existing Internet connections.	User Need 1, 2	ICMS-HENN-ASG	H
HENN-ASG-3-4-2	HENN-Video Sharing: control The ICMS-HENN-ASG System shall not allow other agencies to control Hennepin County cameras (pan/tilt/zoom).	User Need 1, 2	ICMS-HENN-ASG	H
HENN-ASG-4	The ICMS-HENN-ASG System shall Send Data to the ICMS-Data Hub.	User Need 1,2,17	ICMS-HENN-ASG	H
HENN-ASG-4-1	ICMS-HENN-ASG Send Arterial Traffic Data The ICMS-HENN-ASG System shall send to the ICMS-Data Hub Arterial Traffic Data to the ICMS-Data Hub.	User Need 1,2	ICMS-HENN-ASG	H
HENN-ASG-4-1-1	ICMS-HENN-ASG Send Arterial Traffic Data: Data Exchanges The ICMS-HENN-ASG System shall interface with the ICMS-ASG according to requirements of the ICMS-ASG to ICMS-Data Hub ICD to send Arterial Traffic Data.	User Need 2	ICMS-HENN-ASG	H
HENN-ASG-4-1-2	ICMS-HENN-ASG Send Arterial Traffic Data: Frequency The ICMS-HENN-ASG System shall send Arterial Traffic Data to the ICMS-Data Hub each time arterial traffic data is acquired from signal controllers.	User Need 1	ICMS-HENN-ASG	H
HENN-ASG-4-1-3	ICMS-HENN-ASG Send Arterial Traffic Data: No Data The ICMS-HENN-ASG System shall send Arterial Traffic Data to the ICMS-Data Hub indicating “no data available’ if no data is available.	User Need 1	ICMS-HENN-ASG	H
HENN-ASG-4-1-4	ICMS-HENN-ASG Send Arterial Traffic Data: Volume and Speed Data The ICMS-HENN-ASG System shall send to the ICMS-Data Hub Arterial Traffic Data describing volume and speed.	User Need 17	ICMS-HENN-ASG	H
HENN-ASG-4-2	ICMS-HENN-ASG Send Special Event and Incident Signal Timing Plans Data The ICMS-HENN-ASG System shall send to the ICMS-Data Hub Special Event and Incident Signal Timing Plans Data.	User Need 2	ICMS-HENN-ASG	H
HENN-ASG-4-2-1	ICMS-HENN-ASG Send Special Event and Incident Signal Timing Plans Data: Data Exchanges The ICMS-HENN-ASG System shall interface to the ICMS-Data Hub according to the requirements of the ICMS-ASG to ICMS-Data Hub ICD to send Special Event and Incident Signal Timing Plans Data.	User Need 11	ICMS-HENN-ASG	H
HENN-ASG-4-2-2	ICMS-HENN-ASG System Send Special Event and Incident Signal Timing Plans Data: Frequency The ICMS-HENN-ASG System shall send Special Event and Incident Signal Timing Plans Data to the ICMS-Data Hub at a frequency configurable by an ICMS Administrator.	User Need 11	ICMS-HENN-ASG	H
HENN-ASG-4-2-3	ICMS-HENN-ASG Send Special Event and Incident Signal Timing Plans Data: Selected Signal Timing Plan The ICMS-HENN-ASG System shall send Special Event and Incident Signal Timing Plans Data to the ICMS-Data Hub identifying which signal timing plan was implemented.	User Need 11	ICMS-HENN-ASG	H
HENN-ASG-4-2-4	ICMS-HENN-ASG Send Special Event and Incident Signal Timing Plans Data: Time Implemented The ICMS-HENN-ASG System shall send Special Event and Incident Signal Plans Data to the ICMS-Data Hub identifying the time a signal timing plan was implemented.	User Need 11	ICMS-HENN-ASG	H
HENN-ASG-4-2-5	ICMS-HENN-ASG Send Special Event and Incident Signal Timing Plans Data: Time Deactivated The ICMS-HENN-ASG System shall send Special Event and Incident Signal Timing Plans Data to the ICMS-Data Hub identifying the time a signal timing plan was deactivated.	User Need 11	ICMS-HENN-ASG	H

4.7    ICMS Enhancements to City of Minneapolis Arterial Signals Group (ICMS-COM-ASG) Functional Requirements

The City of Minneapolis (COM) Arterial Signals Group (ASG) System will be enhanced as part of the ICMS project. This section describes the requirements for the enhancements to the system (referred to as ICMS-COM-ASG System or ICMS-COM-ASG). The enhanced ASG System will perform four key functions (data input from ICMS Data Hub, interface with field device, display data to operator, and send data to ICMS-Data Hub System). Figure 28 illustrates the ICMS-COM-ASG System functions and Table 13 includes the ICMS-COM-ASG System requirements to ease software development and testing.

Figure 28: ICMS-COM-ASG Functions

Table 13: ICMS-COM-ASG Requirements

ID	Requirement Description	Source	Allocation	Criticality
COM-ASG-1	The ICMS-COM-ASG System Shall Acquire and Store Data from the ICMS-Data Hub.	User Need 2,5,17	ICMS-COM-ASG	H
COM-ASG-1-1	ICMS-COM-ASG Acquire and Store Incident and Event Data The ICMS-COM-ASG system shall acquire and store from the ICMS-Data Hub Incident and Event Data for all roads within the ICM Corridor.	User Need 2,5,17	ICMS-COM-ASG	H
COM-ASG-1-1-1	ICMS-COM-ASG Acquire and Store Incident and Event Data: Data Exchanges The ICMS-COM-ASG system shall interface with the ICMS-Data Hub according to the requirements of the ICMS-Data Hub Post ICD to acquire and store Incident and Event Data.	User Need 2,5,17	ICMS-COM-ASG	H
COM-ASG-1-1-2	ICMS-COM-ASG Acquire and Store Incident and Event Data: Frequency The ICMS-COM-ASG system shall acquire and store Incident and Event Data from the ICMS-Data Hub at a frequency configurable by an ICMS Administrator.	User Need 2,5,17	ICMS-COM-ASG	H
COM-ASG-1-1-3	ICMS-COM-ASG Acquire and Store Incident and Event Data: Location The ICMS-COM-ASG system shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event location.	User Need 2,5,17	ICMS-COM-ASG	H
COM-ASG-1-1-4	ICMS-COM-ASG Acquire and Store Incident and Event Data: Location Detail The ICMS-COM-ASG system shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event location as a geo reference.	User Need 2,5,17	ICMS-COM-ASG	H
COM-ASG-1-1-5	ICMS-COM-ASG Acquire and Store Incident and Event Data: Type The ICMS-COM-ASG shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident type.	User Need 2,5,17	ICMS-COM-ASG	H
COM-ASG-1-1-6	ICMS-COM-ASG Acquire and Store Incident and Event Data: Time The ICMS-COM-ASG system shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event time elements: start time, vehicle arrival time, and clearance time.	User Need 2,5,17	ICMS-COM-ASG	H
COM-ASG-1-2	ICMS-COM-ASG Acquire and Store Freeway Traffic Data The ICMS-COM-ASG system shall acquire and store from the ICMS-Data Hub Freeway Traffic Data.	User Need 17	ICMS-COM-ASG	H
COM-ASG-1-2-1	ICMS-COM-ASG Acquire and Store Freeway Traffic Data: Data Exchanges The ICMS-COM-ASG system shall interface with the ICMS-Data Hub as per the ICMS-Data Hub Post ICD to acquire and store Freeway Traffic Data.	User Need 17	ICMS-COM-ASG	H
COM-ASG-1-2-2	ICMS-COM-ASG Acquire and Store Freeway Traffic Data: Frequency The ICMS-COM-ASG system shall acquire and store Freeway Traffic Data from the ICMS-Data Hub at a frequency configurable by an ICMS Administrator.	User Need 17	ICMS-COM-ASG	H
COM-ASG-1-2-3	ICMS-COM-ASG Acquire and Store Freeway Traffic Data: Traffic Details The ICMS-COM-ASG system shall acquire and store Freeway Traffic Data from the ICMS-Data Hub describing volume, occupancy, and speed data for sensor stations along: The I-394 mainline and I-394 ramps I-494 Hwy 100 Hwy 169.	User Need 17	ICMS-COM-ASG	H
COM-ASG-1-2-4	ICMS-COM-ASG Acquire and Freeway Traffic Data: Travel Times The ICMS-COM-ASG system shall acquire and store messages describing Freeway Travel Times from the ICMS-Data Hub.	User Need 17	ICMS-COM-ASG	H
COM-ASG-1-3	ICMS-COM-ASG Acquire and Store Special Event and Incident Signal Timing Plans Data The ICMS-COM-ASG shall acquire and store Special Event and Incident Signal Timing Plans Data from the ICMS-Data Hub.	User Need 17	ICMS-COM-ASG	H
COM-ASG-1-3-1	ICMS-COM-ASG Acquire and Store Special Event and Incident Signal Timing Plans Data: Data Exchanges The ICMS-COM-ASG system shall interface with the ICMS-Data Hub Post as per the ICMS-Data Hub Post ICD to acquire and store Special Events and Incident Signal Timing Plans Data.	User Need 11,12,17	ICMS-COM-ASG	H
COM-ASG-1-3-2	ICMS-COM-ASG Acquire and Store Special Event and Incident Signal Timing Plans Data: Frequency The ICMS-COM-ASG system shall acquire and store Special Event and Incident Signal Timing Plans Data from the ICMS-Data Hub at a frequency configurable by an ICMS Administrator.	User Need 11,12,17	ICMS-COM-ASG	H
COM-ASG-1-3-3	ICMS-COM-ASG Acquire and Store Special Event and Incident Signal Timing Plans Data: Selected Signal Timing Plan The ICMS-COM-ASG system shall acquire and store messages from the ICMS-Data Hub identifying which signal timing plan was implemented at signals within the ICM corridor.	User Need 11,12,17	ICMS-COM-ASG	H
COM-ASG-1-3-4	ICMS-COM-ASG Acquire and Store Special Event and Incident Signal Timing Plans Data: Time Implemented The ICMS-COM-ASG system shall acquire and store messages from the ICMS-Data Hub identifying the time a signal timing plan was implemented.	User Need 11,12,17	ICMS-COM-ASG	H
COM-ASG-1-3-5	ICMS-COM-ASG Acquire and Store Special Events and Incident Signal Timing Plans Data: Time Deactivated The ICMS-COM-ASG system shall acquire and messages from the ICMS-Data Hub identifying the time a signal timing plan was deactivated.	User Need 11,12,17	ICMS-COM-ASG	H
COM-ASG-2	The ICMS-COM-ASG System shall Display  Data to City of Minneapolis (COM) ASG Operators.	User Need 1,2,17	ICMS-COM-ASG	H
COM-ASG-2-1	ICMS-COM-ASG Mechanism to Display Arterial and Freeway Incident Data The ICMS-COM-ASG system shall provide a mechanism for City of Minneapolis ASG Operators to view Incident Data acquired and stored in the ICMS-COM-ASG on arterials and freeways within the ICM Corridor.	User Need 1,2,17	ICMS-COM-ASG	H
COM-ASG-2-2	ICMS-COM-ASG Mechanism to Display Arterial and Freeway Volume Data The ICMS-COM-ASG system shall provide a mechanism for City of Minneapolis ASG Operators to view Volume Data acquired and stored in the ICMS-COM-ASG on arterials and freeways within the ICM Corridor.	User Need 1,2,17	ICMS-COM-ASG	H
COM-ASG-2-3	ICMS-COM-ASG Mechanism to Display Arterial and Freeway Travel Time Data The ICMS-COM-ASG system shall provide a mechanism for Hennepin County ASG Operators to view Travel Time Data acquired and stored in the ICMS-COM-ASG on arterials and freeways within the ICM Corridor.	User Need 1,2,17	ICMS-COM-ASG	H
COM-ASG-2-4	ICMS-COM-ASG Mechanism to Display Signal Timing Data The ICMS-COM-ASG System shall provide a mechanism for City of Minneapolis ASG Operators to view signal timing plans implemented on signals controlled by Hennepin County and Mn/DOT to coordinate timing plans on city maintained intersections.	User Need 1,2,17	ICMS-COM-ASG	H
COM-ASG-3	The ICMS-COM-ASG shall Interface with Field Devices.	User Need 2,10,17	ICMS-COM-ASG	H
COM-ASG-3-1	The ICMS-COM-ASG System shall Interface with the Traffic Signal Controllers.	User Need 17	ICMS-COM-ASG	H
COM-ASG-3-1-1	ICMS-COM-ASG Acquire and Store Signal Phasing and Volume Data The ICMS-COM-ASG system shall acquire and store signal phasing and traffic volume data from the City of Minneapolis operated traffic signal controllers.	User Need 17	ICMS-COM-ASG	H
COM-ASG-3-1-2	ICMS-COM-ASG Store Special Event and Incident Signal Timing Plans The ICMS-COM-ASG system shall store pre-created special event and incident signal timing plans.	User Need 17	ICMS-COM-ASG	H
COM-ASG-3-1-2-1	ICMS-COM-ASG Store Special Event and Incident Signal Timing Plans: Location The ICMS-COM-ASG system shall store pre-created special event and incident signal timing plans for City of Minneapolis operated intersections.	User Need 17	ICMS-COM-ASG	H
COM-ASG-3-1-3	ICMS-COM-ASG Mechanism to Select and Download Special Event and Incident Signal Timing Plans The ICMS-COM-ASG system shall provide a mechanism for City of Minneapolis ASG Operators to select pre-defined special event and incident signal timing plans to be downloaded to in-field traffic signal controllers.	User Need 17	ICMS-COM-ASG	H
COM-ASG-3-2	The ICMS-COM-ASG System shall interface with Dynamic Message Signs (DMS)	User Need 10	ICMS-COM-ASG	M
COM-ASG-3-2-1	ICMS-COM-ASG Mechanism to Operate DMS The ICMS-COM-ASG system shall provide a mechanism for City of Minneapolis ASG Operators to post messages on arterial DMS.	User Need 10	ICMS-COM-ASG	M
COM-ASG-3-2-2	ICMS-COM-ASG Mechanism to View DMS messages posted The ICMS-COM-ASG system shall provide a mechanism for City of Minneapolis ASG Operators to view current messages posted on arterial DMS.	User Need 10	ICMS-COM-ASG	M
COM-ASG-3-3	The ICMS-COM-ASG shall interface with Closed Circuit Television	User Need 2	ICMS-COM-ASG	M
COM-ASG-3-3-1	ICMS-COM-ASG Mechanism to View and Operate Visual Surveillance The ICMS-COM-ASG system shall provide a mechanism for City of Minneapolis ASG Operators to view visual surveillance on the mainline approaches at each signalized intersection on Hwy 55 and Hwy 7.	User Need 2	ICMS-COM-ASG	H
COM-ASG-3-3-2	ICMS-Mn/DOT ASG Provide Visual Verification of Messages Posted on TH 55 The ICMS-COM-ASG system shall provide a mechanism for City of Minneapolis ASG Operators to visually verify the successful implementation of messages posted to travelers on Hwy 55 and Hwy 7.	User Need 10	ICMS-COM-ASG	H
COM-ASG-3-3-3	ICMS-COM-ASG Provide Visual Monitoring of Signal Timing Plans The ICMS-COM-ASG system shall provide visual monitoring of traffic conditions as special event and incident signal timing plans are implemented.	User Need 17	ICMS-COM-ASG	H
COM-ASG-3-4	COM-Video Sharing The ICMS-COM-ASG System shall share streaming video to Hennepin County (traffic and EMS), Mn/DOT, Metro Transit, SouthWest Transit and Plymouth Metrolink  to view current images captured by city operated CCTV cameras along the corridor.	User Need 1, 2	ICMS-COM-ASG	H
COM-ASG-3-4-1	COM=Video Sharing: accessibility The ICMS-COM-ASG System shall provide a mechanism where authorized agencies can view streaming video from CCTV cameras using Internet browsers and existing Internet connections.	User Need 1, 2	ICMS-COM-ASG	H
COM-ASG-3-4-2	COM-Video Sharing: control The ICMS-COMM-ASG System shall not allow other agencies to control City of Minneapolis cameras (pan/tilt/zoom).	User Need 1, 2	ICMS-COM-ASG	H
COM-ASG-4	The ICMS-COM-ASG System shall Send Data to the ICMS-Data Hub.	User Need 1,2,17	ICMS-COM-ASG	H
COM-ASG-4-1	ICMS-COM-ASG Send Arterial Travel Traffic Data The ICMS-COM-ASG system shall send to the ICMS-Data Hub Arterial Traffic Data to the ICMS-Data Hub.	User Need 1,2	ICMS-COM-ASG	H
COM-ASG-4-1-1	ICMS-COM-ASG Send Arterial Traffic Data: Data Exchanges The ICMS-COM-ASG system shall interface with the ICMS-Data Hub according to the requirements of the ICMS-ASG to ICMS-Data Hub ICD to send Arterial Traffic Data.	User Need 2	ICMS-COM-ASG	H
COM-ASG-4-1-2	ICMS-COM-ASG Send Arterial Traffic Data: Frequency The ICMS-COM-ASG system shall send Arterial Traffic Data to the ICMS-Data Hub each time traffic volume data is acquired from signal controllers.	User Need 1	ICMS-COM-ASG	H
COM-ASG-4-1-3	ICMS-COM-ASG Send Arterial Traffic Data: No Data The ICMS-COM-ASG system shall send Arterial Traffic Data to the ICMS-Data Hub indicating “no data available’ if no data is available.	User Need 1	ICMS-COM-ASG	H
COM-ASG-4-1-4	ICMS-COM-ASG Send Arterial Traffic Data: Volume and Speed Data The ICMS-COM-ASG system shall send to the ICMS-Data Hub Arterial Traffic Data describing volume and speed.	User Need 17	ICMS-COM-ASG	H
COM-ASG-4-2	ICMS-COM-ASG Send Special Event and Incident Signal Timing Plans Data The ICMS-COM-ASG system shall send to the ICMS-Data Hub Special Event and Incident Signal Timing Plans Data.	User Need 2	ICMS-COM-ASG	H
COM-ASG-4-2-1	ICMS-COM-ASG Send Special Event and Incident Signal Timing Plans Data: Data Exchanges The ICMS-COM-ASG system shall follow the ICMS-ASG to ICMS-Data Hub ICD to send Special Event and Incident Signal Timing Plans Data.	User Need 11	ICMS-COM-ASG	H
COM-ASG-4-2-2	ICMS-COM-ASG Send Special Event and Incident Signal Timing Plans Data: Frequency The ICMS-COM-ASG system shall send Special Event and Incident Signal Timing Plans Data to the ICMS-Data Hub each time a special signal timing plan is downloaded to an intersection within the ICM corridor.	User Need 11	ICMS-COM-ASG	H
COM-ASG-4-2-3	ICMS-COM-ASG Send Special Event and Incident Signal Timing Plans Data: Selected Signal Timing Plan The ICMS-COM-ASG system shall send Special Event and Incident Signal Timing Plans Data to the ICMS-Data Hub identifying which signal timing plan was implemented.	User Need 11	ICMS-COM-ASG	H
COM-ASG-4-2-4	ICMS-COM-ASG Send Special Event and Incident Signal Timing Plans Data: Time Implemented The ICMS-COM-ASG system shall send Special Event and Incident Signal Plans Data to the ICMS-Data Hub identifying the time a signal timing plan was implemented.	User Need 11	ICMS-COM-ASG	H
COM-ASG-4-2-5	ICMS-COM-ASG Send Special Event and Incident Signal Timing Plans Data: Time Deactivated The ICMS-COM-ASG system shall send Special Event and Incident Signal Timing Plans Data to the ICMS-Data Hub identifying the time a signal timing plan was deactivated.	User Need 11	ICMS-COM-ASG	H

4.8    ICMS Enhancements to Minnesota State Patrol (ICMS-MSP-EMS) Functional Requirements

The Minnesota State Patrol (MSP) Emergency Management System will be enhanced as part of the ICMS project. Currently, the MSP dispatchers are co-located in the RTMC dispatch center, and have full access to Mn/DOT video feeds. This section describes the requirements for the enhancements to the MSP EMS (referred to as ICMS-MSP-EMS System). The enhanced MSP-EMS will perform one key function (Generate and Send Messages to ICMS-Data Hub). Figure 29 illustrates the ICMS-MSP-EMS System functions and Table 14 includes the ICMS-MSP-EMS System requirements to ease software development and testing.

Figure 29: ICMS-MSP-EMS Functions

Table 14: ICMS-MSP-EMS Requirements

ID	Requirement Description	Source	Allocation	Criticality
EMS-MSP-1	The ICMS-MSP-EMS System Shall Generate Messages to be Sent to the ICMS-Data Hub System Describing Incidents on Highways within the ICM Corridor.	User Need 1	ICMS-MSP-EMS	H
EMS-MSP-1-1	ICMS-MSP-EMS Select incidents for transmission. The ICMS-MSP-EMS shall compare each incident report entered in the CAD system against an algorithm to determine if the message shall be sent to the ICMS-Data Hub system.	User Need 1	ICMS-MSP-EMS	H
EMS-MSP-1-2	ICMS-MSP-EMS generate message The ICMS-MSP-EMS shall generate a message that contains all information contained in the CAD system describing the incident.	User Need 1	ICMS-MSP-EMS	H
EMS-MSP-1-3	ICMS-MSP-EMS Filter incident messages The ICMS-MSP-EMS shall remove any data elements from messages describing incidents that are not public information.	User Need 1	ICMS-MSP-EMS	H
EMS-MSP-1-4	ICMS-MSP-EMS Format message sets for transmission to ICMS-Data Hub The ICMS-MSP-EMS shall assign each message a unique message ID.	User Need 1	ICMS-MSP-EMS	H
EMS-MSP-1-4-1	ICMS-MSP-EMS Handling of message updates The ICMS-MSP-EMS shall generate messages identified as update messages to earlier messages by assigning a unique message ID that references the earlier message ID.	User Need 1	ICMS-MSP-EMS	H
EMS-MSP-2	The ICMS-MSP-EMS Shall Send Messages Describing Current Incidents to the ICMS-Data Hub System.	User Need 1	ICMS-MSP-EMS	H
EMS-MSP-2-1	ICMS-MSP-EMS Send Incident Data: Data Exchanges The ICMS-MSP-EMS shall interface to the ICMS-Data Hub System according to requirements of the ICMS-EMS to ICMS-Data Hub ICD to send Incident Data to the ICMS-Data Hub.	User Need 1	ICMS-MSP-EMS	H
EMS-MSP-2-2	ICMS-MSP-EMS Send Incident Data: Frequency The ICMS-MSP-EMS shall send messages describing incidents to the ICMS-Data Hub after each message is generated.	User Need 1	ICMS-MSP-EMS	H
EMS-MSP-2-3	ICMS-MSP-EMS Send Incident Data: Timing The ICMS-MSP-EMS shall send messages describing  incidents to the ICMS-Data Hub within a time period from when the incident is entered in the CAD system. This time period shall be configurable by the administrator of the system.	User Need 1	ICMS-MSP-EMS	H
EMS-MSP-2-4	ICMS-MSP-EMS Send Incident Data: Test Messages The ICMS-MSP-EMS shall send test messages to the ICMS-Data Hub system if a period of time has elapsed without any incidents being entered into the MSP CAD system to enable the ICMS-Data Hub to verify that the connection is still active. This period of time shall be configurable by the administrator.	User Need 1	ICMS-MSP-EMS	H
EMS-MSP-2-5	ICMS-MSP-EMS Send Incident Data: Location The ICMS-MSP-EMS shall send Incident Data to the ICMS-Data Hub describing the incident location.	User Need 1	ICMS-MSP-EMS	H
EMS-MSP-2-5-1	ICMS-MSP-EMS Send Incident Data: Location Detail The ICMS-MSP-EMS shall send Incident Data to the ICMS-Data Hub describing the incident location as a geo reference.	User Need 1	ICMS-MSP-EMS	H
EMS-MSP-2-6	ICMS-MSP-EMS Send Incident Data: Type The ICMS-MSP-EMS shall send Incident Data to the ICMS-Data Hub describing incident type and severity.	User Need 1	ICMS-MSP-EMS	H
EMS-MSP-2-7	ICMS-MSP-EMS Send Incident Data: Time The ICMS-MSP-EMS shall send Incident Data to the ICMS-Data Hub describing incident time elements: incident start time, vehicle arrival time, and clearance time.	User Need 1	ICMS-MSP-EMS	H
EMS-MSP-2-8	ICMS-MSP-EMS Send Incident Data: Response Activity The ICMS-MSP-EMS shall send Incident Data to the ICMS-Data Hub describing incident response activity.	User Need 1 and 11	ICMS-MSP-EMS	H

4.9    ICMS Enhancements to City of Minneapolis Emergency Management System (ICMS-COM-EMS) Functional Requirements

The City of Minneapolis (COM) Emergency Management System will be enhanced as part of the ICMS project. This section describes the requirements for the enhancements to the COM EMS referred to as ICMS-COM-EMS System). The enhanced COM-EMS will perform three key functions (Generate and Send Messages to ICMS-Data Hub, Acquire and store data from the ICMS-Data Hub, and Display information to operators). Figure 30 illustrates the ICMS-COM-EMS System functions and Table 15 includes the ICMS-COM-EMS System requirements to ease software development and testing.

Figure 30: ICMS-COM-EMS Functions

Table 15: ICMS-COM-EMS Requirements

ID	Requirement Description	Source	Allocation	Criticality
EMS-COM-1	The ICMS-COM-EMS System Shall Acquire and Store Incident Data Describing Incidents from the ICMS-Data Hub	User Need 1, 10,11,12	ICMS-COM-EMS	H
EMS-COM-1-1	ICMS-COM-EMS System Acquire and Store Incident Data: Data Exchanges The ICMS-COM-EMS System shall follow the ICMS-EMS to ICMS-Data Hub ICD to acquire and store ICMS-EMS Incident Data from the ICMS-Data Hub.	User Need 1,10,11,12	ICMS-COM-EMS	H
EMS-COM-1-2	ICMS-COM-EMS Acquire and Store Incident Data: Frequency The ICMS-COM-EMS System shall acquire and store ICMS-EMS Incident Data from the ICMS-Data Hub at a frequency configurable by an ICMS Administrator.	User Need 1,11,10,12	ICMS-COM-EMS	H
EMS-CoM-1-3	ICMS-COM-EMS Acquire and Store Incident Data: Location The ICMS-COM-EMS System shall acquire and store ICMS-EMS Incident Data from the ICMS-Data Hub describing the incident location.	User Need 1,10,11,12	ICMS-COM-EMS	H
EMS-COM-1-4	ICMS-COM-EMS Acquire and Store Incident Data: Location Detail The ICMS-COM-EMS System shall acquire and store ICMS-EMS Incident Data from the ICMS-Data Hub describing the incident location as a geo reference.	User Need 1,10,11,12	ICMS-COM-EMS	H
EMS-COM-1-5	ICMS-COM-EMS Acquire and Store Incident Data: Type The ICMS-COM-EMS System shall acquire and store ICMS-EMS Incident Data from the ICMS-Data Hub describing incident type and severity.	User Need 1,10,11,12	ICMS-COM-EMS	H
EMS-COM-1-6	ICMS-COM-EMS Acquire and Store Incident Data: Time The ICMS-COM-EMS System shall acquire and store ICMS-EMS Incident Data from the ICMS-Data Hub describing incident time elements: incident start time, vehicle arrival time, and clearance time.	User Need 1,10,11,12	ICMS-COM-EMS	H
EMS-COM-1-7	ICMS-COM-EMS Acquire and Store Incident Data: Response Activity The ICMS-COM-EMS System shall acquire and store ICMS-EMS Incident Data from the ICMS-Data Hub describing incident response activity.	User Need 1,10, 11,12	ICMS-COM-EMS	H
EMS-COM-2	The ICMS-COM-EMS System Shall Generate Messages to be Sent to the ICMS-Data Hub System Describing Incidents on City of Minneapolis Highways within the ICM Corridor.	User Need 1,10,111,12	ICMS-COM-EMS	H
EMS-COM-2-1	ICMS-COM-EMS Select incidents for transmission. The ICMS-COM-EMS System shall compare each incident report entered in the CAD system against an algorithm to determine if the message shall be sent to the ICMS-Data Hub system.	User Need 1,10,11,12	ICMS-COM-EMS	H
EMS-COM-2-2	ICMS-COM-EMS generate message The ICMS-COM-EMS System shall generate a message that contains all information contained in the CAD system describing the incident.	User Need 1,10,11,12	ICMS-COM-EMS	H
EMS-COM-2-3	ICMS-COM-EMS Filter incident messages The ICMS-COM-EMS System shall remove any data elements from messages describing incidents that are not public information.	User Need 1,10,11,12	ICMS-COM-EMS	H
EMS-COM-2-4	ICMS-COM-EMS Format message sets for transmission to ICMS-Data Hub The ICMS-COM-EMS System shall assign each message a unique message ID.	User Need 1,10,1,12	ICMS-COM-EMS	H
EMS-COM-2-5	ICMS-COM-EMS Handling of message updates The ICMS-COM-EMS System shall generate messages identified as update messages to earlier messages by assigning a unique message ID that references the earlier message ID.	User Need 1,10,11,12	ICMS-COM-EMS	H
EMS-COM-3	The ICMS-COM-EMS System Shall Send Incident Data Describing Incidents to the ICMS-Data Hub system.	User Need 1,10,11,12	ICMS-COM-EMS	H
EMS-COM-3-1	ICMS-MSP-EMS Send Incident Data: Data Exchanges The ICMS-COM-EMS System shall follow the ICMS-EMS to ICMS-Data Hub ICD to send Incident Data to the ICMS-Data Hub.	User Need 1,10,11,12	ICMS-COM-EMS	H
EMS-COM-3-2	ICMS-COM-EMS Send Incident Data: Frequency The ICMS-COM-EMS System shall send messages describing incidents to the ICMS-Data Hub after each message is generated.	User Need 1,10,11,12	ICMS-COM-EMS	H
EMS-COM-3-3	ICMS-COM-EMS Send Incident Data: Timing The ICMS-COM-EMS System shall send messages describing incidents to the ICMS-Data Hub within a time period from when the incident is entered in the CAD system. This time period shall be configurable by the administrator of the system.	User Need 1,10,11,12	ICMS-COM-EMS	H
EMS-COM-3-4	ICMS-COM-EMS Send Incident Data: Test Messages The ICMS-COM-EMS System shall send test messages to the ICMS-Data Hub system if a period of time has elapsed without any incidents being entered into the COM CAD system to enable the ICMS-Data Hub to verify that the connection is still active. This period of time shall be configurable by the administrator.	User Need 1,10,11,12	ICMS-COM-EMS	H
EMS-COM-3-5	ICMS-COM-EMS Send Incident Data: Location Detail The ICMS-COM-EMS System shall send Incident Data to the ICMS-Data Hub describing the incident location as a geo reference.	User Need 1,10,11,12	ICMS-COM-EMS	H
EMS-COM-3-6	ICMS-COM-EMS Send Incident Data: Type The ICMS-COM-EMS System shall send Incident Data to the ICMS-Data Hub describing incident type and severity.	User Need 1,10,11,12	ICMS-COM-EMS	H
EMS-COM-3-7	ICMS-COM-EMS Send Incident Data: Time The ICMS-COM-EMS System shall send Incident Data to the ICMS-Data Hub describing incident time elements: incident start time, vehicle arrival time, and clearance time.	User Need 1,10,11,12	ICMS-COM-EMS	H
EMS-COM-3-8	ICMS-COM-EMS Send Incident Data: Response Activity The ICMS-COM-EMS System shall send Incident Data to the ICMS-Data Hub describing incident response activity.	User Need 1,10, 11,12	ICMS-COM-EMS	H
EMS-COM-4	The ICMS-COM-EMS System Shall Display ICMS-EMS Incident Data to COM Operators.	User Need 1,10,11,12	ICMS-COM-EMS	H
EMS-COM-4-1	ICMS-COM-EMS Mechanism to Display ICMS-EMS Incident Data The ICMS-COM-EMS System shall provide a mechanism for COM Operators to view Incident Data acquired and stored in the ICMS-COM-EMS.	User Need 1,10,11,12	ICMS-COM-EMS	H

4.10  ICMS Enhancements to Hennepin County Emergency Management System (ICMS-HENN-EMS) Functional Requirements

The Hennepin County (HENN) Emergency Management System will be enhanced as part of the ICMS project. This section describes the requirements for the enhancements to the HENN EMS (referred to as ICMS-HENN-EMS System). The enhanced HENN-EMS will perform three key functions (Generate and Send Messages to ICMS-Data Hub, Acquire and store data from the ICMS-Data Hub, and Display information to operators). Figure 31 illustrates the ICMS-HENN-EMS System functions and Table 16 includes the ICMS-HENN-EMS System requirements to ease software development and testing.

Figure 31: ICMS-HENN-EMS Functions

Table 16: ICMS-HENN-EMS Requirements

ID	Requirement Description	Source	Allocation	Criticality
EMS-HENN-1	The ICMS-HENN-EMS System Shall Acquire and Store Incident Data Describing Incidents from the ICMS-Data Hub.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-1-1	ICMS-HENN-EMS Acquire and Store Incident Data: Data Exchanges The ICMS-HENN-EMS System shall interface to the ICMS-Data Hub System according to the requirements of the ICMS-EMS to ICMS-Data Hub ICD to acquire and store Incident Data from the ICMS-Data Hub.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-1-2	ICMS-HENN-EMS Acquire and Store Incident Data: Frequency The ICMS-HENN-EMS System shall acquire and store Incident Data from the ICMS-Data Hub at a frequency configurable by an ICMS Administrator.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-1-3	ICMS-HENN-EMS Acquire and Store Incident Data: Location The ICMS-HENN-EMS System shall acquire and store Incident Data from the ICMS-Data Hub describing the incident location.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-1-4	ICMS-HENN-EMS Acquire and Store Incident Data: Location Detail The ICMS-HENN-EMS System shall acquire and Incident Data from the ICMS-Data Hub describing incident location as a geo reference.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-1-5	ICMS-HENN-EMS Acquire and Store Incident Data: Type The ICMS-HENN-EMS System shall acquire and store Incident Data from the ICMS-Data Hub describing incident type and severity.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-1-6	ICMS-HENN-EMS Acquire and Store Incident Data: Time The ICMS-HENN-EMS System shall acquire and store Incident Data from the ICMS-Data Hub describing incident time elements: incident start time, vehicle arrival time, and clearance time.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-1-7	ICMS-HENN-EMS Acquire and Store Incident Data: Response Activity The ICMS-HENN-EMS System shall acquire and store Incident Data from the ICMS-Data Hub describing incident response activity.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-2	The ICMS-HENN-EMS System Shall Generate Messages to be Sent to the ICMS-Data Hub System Describing Incidents on Highways within the ICM Corridor.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-2-1	ICMS-HENN-EMS Select incidents for transmission. The ICMS-HENN-EMS System shall compare each incident report entered in the CAD system against an algorithm to determine if the message shall be sent to the ICMS-Data Hub system.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-2-2	ICMS-HENN-EMS generate message The ICMS-HENN-EMS System shall generate a message that contains all information contained in the CAD system describing the incident.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-2-3	ICMS-HENN-EMS Filter incident messages The ICMS-HENN-EMS System shall remove any data elements from messages describing incidents that are not public information.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-2-4	ICMS-HENN-EMS Format message sets for transmission to ICMS-Data Hub The ICMS-HENN-EMS System shall assign each message a unique message ID.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-2-5	ICMS-HENN-EMS Handling of message updates The ICMS-HENN-EMS System shall generate messages identified as update messages to earlier messages by assigning a unique message ID that references the earlier message ID.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-3	The ICMS-HENN-EMS Shall Send Messages Describing Current Incidents to the ICMS-Data Hub system.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-3-1	ICMS-HENN-EMS Send Incident Data: Data Exchanges The ICMS-HENN-EMS System shall follow the ICMS-EMS to ICMS-Data Hub ICD to send Incident Data to the ICMS-Data Hub.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-3-2	ICMS-HENN-EMS Send Incident Data: Frequency The ICMS-HENN-EMS System shall send messages describing incidents to the ICMS-Data Hub after each message is generated.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-3-3	ICMS-HENN-EMS Send Incident Data: Timing The ICMS-HENN-EMS System shall send messages describing incidents to the ICMS-Data Hub within a time period from when the incident is entered in the CAD system. This time period shall be configurable by the administrator of the system.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-3-4	ICMS-HENN-EMS Send Incident Data: Test Messages The ICMS-HENN-EMS System shall send test messages to the ICMS-Data Hub system if a period of time has elapsed without any incidents being entered into the HENN CAD system to enable the ICMS-Data Hub to verify that the connection is still active. This period of time shall be configurable by the administrator.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-3-5	ICMS-HENN-EMS Send Incident Data: Location Detail The ICMS-HENN-EMS System shall send Incident Data to the ICMS-Data Hub describing incident location as a geo reference.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-3-6	ICMS-HENN-EMS Send Incident Data: Type The ICMS-HENN-EMS System shall send Incident Data to the ICMS-Data Hub describing incident type and severity.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-3-7	ICMS-HENN-EMS Send Incident Data: Time The ICMS-HENN-EMS System shall send Incident Data to the ICMS-Data Hub describing incident time elements: incident start time, vehicle arrival time, and clearance time.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-3-8	ICMS-HENN-EMS Send Incident Data: Response Activity The ICMS-HENN-EMS System shall send Incident Data to the ICMS-Data Hub describing incident response activity.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-4	The ICMS-HENN-EMS System Shall Display ICMS-EMS Incident Data to HENN Operators.	User Need 1,10,11,12	ICMS-HENN-EMS	H
EMS-HENN-4-1	ICMS-HENN-EMS Mechanism to Display ICMS-EMS Incident Data The ICMS-HENN-EMS System shall provide a mechanism for HENN Operators to view Incident Data acquired and stored in the ICMS-HENN-EMS.	User Need 1,10,11,12	ICMS-HENN-EMS	H

4.11  ICMS Enhancements to SouthWest Transit Dispatch Center (ICMS-SWT System)

The SouthWest Transit dispatch center will be enhanced as part of the ICMS project. This section describes the requirements for the enhancements to the system (referred to as ICMS-SWT System. The enhanced System will perform two key functions (data input from ICMS Data Hub, and display data to operator). Figure 32 illustrates the ICMS-SWT System functions and Table 17 includes the ICMS-SWT System requirements to ease software development and testing.

 

Figure 32: ICMS-SWT Functions

Table 17: ICMS-SWT Requirements

ID	Requirement Description	Source	Allocation	Criticality
SWT-1	The ICMS-SWT System Shall Acquire and Store Data from the ICMS-Data Hub.	User Need 2,5,17	ICMS-SWT	H
SWT-1-1	ICMS-SWT Acquire and Store Incident and Event Data The ICMS-SWT System shall acquire and store from the ICMS-Data Hub Incident and Event Data for all roads within the ICM Corridor.	User Need 2,5,17	ICMS-SWT	H
SWT-1-1-1	ICMS-SWT Acquire and Store Incident and Event Data: Data Exchanges The ICMS-SWT System shall interface with the ICMS-Data Hub according to the requirements of the ICMS-Data Hub Post ICD to acquire and store Incident and Event Data.	User Need 2,5,17	ICMS-SWT	H
SWT-1-1-2	ICMS-SWT Acquire and Store Incident and Event Data: Frequency The ICMS-SWT System shall acquire and store Incident and Event Data from the ICMS-Data Hub at least once per minute.	User Need 2,5,17	ICMS-SWT	H
SWT-1-1-3	ICMS-SWT Acquire and Store Incident and Event Data: Location The ICMS-SWT System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event location.	User Need 2,5,17	ICMS-SWT	H
SWT-1-1-4	ICMS-SWT Acquire and Store Incident and Event Data: Location Detail The ICMS-SWT System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event location as a geo reference.	User Need 2,5,17	ICMS-SWT	H
SWT-1-1-5	ICMS-SWT Acquire and Store Incident and Event Data: Type The ICMS-SWT System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident type.	User Need 2,5,17	ICMS-SWT	H
SWT-1-1-6	ICMS-SWT Acquire and Store Incident and Event Data: Time The ICMS-SWT System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event time elements: start time, vehicle arrival time, and clearance time.	User Need 2,5,17	ICMS-SWT	H
SWT-1-2	ICMS-SWT Acquire and Store Freeway Traffic Data The ICMS-SWT System shall acquire and store from the ICMS-Data Hub Freeway Traffic Data.	User Need 17	ICMS-SWT	H
SWT-1-2-1	ICMS-SWT Acquire and Store Freeway Traffic Data: Data Exchanges The ICMS-SWT System shall interface with the ICMS-Data Hub according to the requirements of the ICMS-Data Hub Post ICD to acquire and store Freeway Traffic Data.	User Need 17	ICMS-SWT	H
SWT-1-2-2	ICMS-SWT Acquire and Store Freeway Traffic Data: Frequency The ICMS-SWT System shall acquire and store Freeway Traffic Data from the ICMS-Data Hub at least once per minute.	User Need 17	ICMS-SWT	H
SWT-1-2-3	ICMS-SWT Acquire and Store Freeway Traffic Data: Traffic Details The ICMS-SWT System shall acquire and store Freeway Traffic Data from the ICMS-Data Hub describing volume, occupancy, and speed data for sensor stations along: The I-394 mainline and I-394 ramps I-494 Hwy 100 Hwy 169.	User Need 17	ICMS-SWT	H
SWT-1-2-4	ICMS-SWT Acquire and Freeway Traffic Data: Travel Times The ICMS-SWT System shall acquire and store messages describing Freeway Travel Times from the ICMS-Data Hub.	User Need 17	ICMS-SWT	H
SWT-1-3	ICMS-SWT Acquire Mn/PASS direction and rate data. The ICMS-SWT System shall acquire Mn/PASS lane direction and pricing data from the ICMS-Data Hub, as per the ICMS-Data Hub Post ICD at least once every 2 minutes.	User Need 17	ICMS-SWT	H
SWT-2	The ICMS-SWT System shall Display Data to SouthWest Transit Dispatchers.	User Need 1,2,17	ICMS-SWT	H
SWT-2-1	ICMS-SWT Mechanism to Display Arterial and Freeway Incident Data The ICMS-SWT System shall provide a mechanism for SouthWest Transit Dispatchers to view Incident Data acquired and stored in the ICMS-SWT on arterials and freeways within the ICM Corridor.	User Need 1,2,17	ICMS-SWT	H
SWT-2-2	ICMS-SWT Mechanism to Display Arterial and Freeway Volume Data The ICMS-SWT System shall provide a mechanism for SouthWest Transit Dispatchers to view Volume Data acquired and stored in the ICMS-SWT on arterials and freeways within the ICM Corridor.	User Need 1,2,17	ICMS-SWT	H
SWT-2-3	ICMS-SWT Mechanism to Display Arterial and Freeway Travel Time Data The ICMS-SWT System shall provide a mechanism for SouthWest Transit Dispatchers to view Travel Time Data acquired and stored in the ICMS-SWT on arterials and freeways within the ICM Corridor.	User Need 1,2,17	ICMS-SWT	H

4.12  ICMS Enhancements to Plymouth Metrolink Transit Dispatch Center (ICMS-PM System)

The Plymouth Metrolink (operated by Plymouth Transit) dispatch center will be enhanced as part of the ICMS project. This section describes the requirements for the enhancements to the system (referred to as ICMS-PM System. The enhanced System will perform two key functions (data input from ICMS Data Hub, and display data to operator). Figure 33 illustrates the ICMS-PM System functions and Table 18 includes the ICMS-PM System requirements.

 

Figure 33: ICMS-PM Functions

Table 18: ICMS-PM Requirements

ID	Requirement Description	Source	Allocation	Criticality
PM-1	The ICMS-PM System Shall Acquire and Store Data from the ICMS-Data Hub.	User Need 2,5,17	ICMS-PM	H
PM-1-1	ICMS-PM Acquire and Store Incident and Event Data The ICMS-PM System shall acquire and store from the ICMS-Data Hub Incident and Event Data for all roads within the ICM Corridor.	User Need 2,5,17	ICMS-PM	H
PM-1-1-1	ICMS-PM Acquire and Store Incident and Event Data: Data Exchanges The ICMS-PM System shall interface with the ICMS-Data Hub according to the requirements of the ICMS-Data Hub Post ICD to acquire and store Incident and Event Data.	User Need 2,5,17	ICMS-PM	H
PM-1-1-2	ICMS-PM Acquire and Store Incident and Event Data: Frequency The ICMS-PM System shall acquire and store Incident and Event Data from the ICMS-Data Hub at least once per minute.	User Need 2,5,17	ICMS-PM	H
PM-1-1-3	ICMS-PM Acquire and Store Incident and Event Data: Location The ICMS-PM System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event location.	User Need 2,5,17	ICMS-PM	H
PM-1-1-4	ICMS-PM Acquire and Store Incident and Event Data: Location Detail The ICMS-PM System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event location as a geo reference.	User Need 2,5,17	ICMS-PM	H
PM-1-1-5	ICMS-PM Acquire and Store Incident and Event Data: Type The ICMS-PM System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident type.	User Need 2,5,17	ICMS-PM	H
PM-1-1-6	ICMS-PM Acquire and Store Incident and Event Data: Time The ICMS-PM System shall acquire and store Incident and Event Data from the ICMS-Data Hub describing the incident or event time elements: start time, vehicle arrival time, and clearance time.	User Need 2,5,17	ICMS-PM	H
PM-1-2	ICMS-PM Acquire and Store Freeway Traffic Data The ICMS-PM System shall acquire and store from the ICMS-Data Hub Freeway Traffic Data.	User Need 17	ICMS-PM	H
PM-1-2-1	ICMS-PM Acquire and Store Freeway Traffic Data: Data Exchanges The ICMS-PM System shall interface with the ICMS-Data Hub according to the requirements of the ICMS-Data Hub Post ICD to acquire and store Freeway Traffic Data.	User Need 17	ICMS-PM	H
PM-1-2-2	ICMS-PM Acquire and Store Freeway Traffic Data: Frequency The ICMS-PM System shall acquire and store Freeway Traffic Data from the ICMS-Data Hub at least once per minute.	User Need 17	ICMS-PM	H
PM-1-2-3	ICMS-PM Acquire and Store Freeway Traffic Data: Traffic Details The ICMS-PM System shall acquire and store Freeway Traffic Data from the ICMS-Data Hub describing volume, occupancy, and speed data for sensor stations along: The I-394 mainline and I-394 ramps I-494 Hwy 100 Hwy 169.	User Need 17	ICMS-PM	H
PM-1-2-4	ICMS-PM Acquire and Freeway Traffic Data: Travel Times The ICMS-PM System shall acquire and store messages describing Freeway Travel Times from the ICMS-Data Hub.	User Need 17	ICMS-PM	H
PM-2	The ICMS-PM System shall Display Data to Plymouth Metrolink Transit Dispatchers.	User Need 1,2,17	ICMS-PM	H
PM-2-1	ICMS-PM Mechanism to Display Arterial and Freeway Incident Data The ICMS-PM System shall provide a mechanism for Plymouth Metrolink Transit Dispatchers to view Incident Data acquired and stored in the ICMS-PM on arterials and freeways within the ICM Corridor.	User Need 1,2,17	ICMS-PM	H
PM-2-2	ICMS-PM Mechanism to Display Arterial and Freeway Volume Data The ICMS-PM System shall provide a mechanism for Plymouth Metrolink Transit Dispatchers to view Volume Data acquired and stored in the ICMS-PM on arterials and freeways within the ICM Corridor.	User Need 1,2,17	ICMS-PM	H
PM-2-3	ICMS-PM Mechanism to Display Arterial and Freeway Travel Time Data The ICMS-PM System shall provide a mechanism for Plymouth Metrolink Transit Dispatchers to view Travel Time Data acquired and stored in the ICMS-PM on arterials and freeways within the ICM Corridor.	User Need 1,2,17	ICMS-PM	H

Previous | Next