ICMS Functional Requirements

The I-880 ICM team used a systems engineering process is to gather, review, analyze, and transform user needs identified in the ConOps into functional requirements that define “what” the system will do. The ICM functional requirements are specified as capabilities or functions of the ICM system, and qualifying conditions and bounding constraints that are identified distinctly from capabilities.

4.2 Identify ICMS Needs

Functional requirements of ICMS are rooted from the corridor needs, which were identified by the stakeholders in the ConOps stage. In order to extract functional requirements from the corridor needs, detailed ICM system (ICMS) needs must be defined. In the process of identifying detailed ICMS needs, the project consultants conducted an analysis to determine 'what' will be needed in order to meet the corridor needs from the perspectives of information acquisition, archiving, processing and dissemination. The ICMS needs are decomposed to a level where functional requirements can be defined. Table 4.1 is the summary of the I-880 ICMS needs.

Table 4.1 I-880 ICMS Needs Summary

N1 Need for cross-systems information sharing
1. N1-01 Acquire information
  1. N1-01-01 Acquire traffic information
  2. N1-01-02 Acquire transit information
  3. N1-01-03 Acquire parking information
  4. N1-01-04 Acquire event information
2. N1-02 Process information
  1. N1-02-01 Check information quality
  2. N1-02-02 Calculate travel times
  3. N1-02-03 Determine new incident
  4. N1-02-04 Determine transit service schedule/route adherence
  5. N1-02-05 Determine remaining network capacity
  6. N1-02-06 Forecast network demand
  7. N1-02-07 Forecast congestion
  8. N1-02-08 Determine actions in response to current and forecast conditions
3. N1-03 Publish information
  1. N1-03-01 Publish information to colleague systems
  2. N1-03-02 Publish response actions to colleague systems
4. N1-04 Archive information
  1. N1-04-01 Archive traffic information
    1. N1-04-01-01 Archive freeway traffic information
    2. N1-04-01-02 Archive arterial traffic information
  2. N1-04-02 Archive transit information
    1. N1-04-02-01 Archive bus transit information
    2. N1-04-02-02 Archive rail transit information
  3. N1-04-03 Archive incident information from difference sources
N2 Need for a corridor/region-based multimodal traveler information system
1. N2-01 Acquire information
  1. N2-01-01 Acquire traffic information
  2. N2-01-02 Acquire transit information
  3. N2-01-03 Acquire parking information
  4. N2-01-04 Acquire event information
2. N2-02 Process information
  1. N2-02-01 Check information quality
  2. N2-02-02 Store information
  3. N2-02-03 Calculate travel times
  4. N2-02-04 Determine new incident
  5. N2-02-05 Process video
  6. N2-02-06 Determine transit service schedule/route adherence
  7. N2-02-07 Determine remaining network capacity
  8. N2-02-08 Forecast congestion
3. N2-03 Publish information
  1. N2-03-01 Publish information via DMS
  2. N2-03-02 Publish information via 511
  3. N2-03-03 Publish information via HAR
N3 Need for coordination between freeway and arterial operations
1. N3-01 Configure system response plans
2. N3-02 Acquire information
  1. N3-02-01 Acquire traffic information
  2. N3-02-02 Acquire event information
3. N3-03 Process information
  1. N3-03-01 Check information quality
  2. N3-03-02 Calculate travel times
  3. N3-03-03 Determine new incident
  4. N3-03-04 Determine remaining network capacity
  5. N3-03-05 Forecast network demand
  6. N3-03-06 Forecast congestion
  7. N3-03-07 Determine actions in response to current and forecast conditions
4. N3-04 Publish information
  1. N3-04-01 Publish information via DMS
  2. N3-04-02 Publish information via 511
  3. N3-04-03 Publish information via HAR
  4. N3-04-04 Publish information to colleague systems
N4 Need for coordination between highway and transit operations
1. N4-01 Prepare operational procedures
2. N4-02 Train operations staff
3. N4-03 Acquire information
  1. N4-03-01 Acquire traffic information
  2. N4-03-02 Acquire transit information
  3. N4-03-03 Acquire parking information
  4. N4-03-04 Acquire event information
4. N4-04 Process information
  1. N4-04-01 Check information quality
  2. N4-04-02 Calculate travel times
  3. N4-04-03 Determine new incident
  4. N4-04-04 Determine transit service schedule/route adherence
  5. N4-04-05 Determine remaining network capacity
  6. N4-04-06 Forecast network demand
  7. N4-04-07 Forecast congestion
  8. N4-04-08 Determine actions in response to current and forecast conditions
  9. N4-04-09 Determine bus arrival time at downstream intersections
  10. N4-04-10 Request bus priority at downstream intersections
5. N4-05 Publish information
  1. N4-05-01 Publish information via DMS
  2. N4-05-02 Publish information via 511
  3. N4-05-03 Publish information via HAR
  4. N4-05-04 Publish information to colleague systems
  5. N4-05-05 Publish traffic information to transit users
N5 Need for coordination between transit systems
1. N5-01 Prepare operational procedures
2. N5-02 Train operations staff
3. N5-03 Acquire information
  1. N5-03-01 Acquire transit information
  2. N5-03-02 Acquire parking information
  3. N5-03-03 Acquire event information
4. N5-04 Process information
  1. N5-04-01 Check information quality
  2. N5-04-02 Determine transit service schedule/route adherence
  3. N5-04-03 Forecast network demand
  4. N5-04-04 Determine actions in response to current and forecast conditions
  5. N5-04-05 Log information regarding requests for connection protection
5. N5-05 Publish information
  1. N5-05-01 Publish information via DMS
  2. N5-05-02 Publish information via 511
  3. N5-05-03 Publish information via HAR
  4. N5-05-04 Publish information to colleague systems
  5. N5-05-05 Publish information at transit stops
N6 Need for coordination between highway and freight operations
1. N6-01 Acquire information
  1. N6-01-01 Acquire traffic information
  2. N6-01-02 Acquire port operation information
2. N6-02 Process information
  1. N6-02-01 Check information quality
  2. N6-02-02 Calculate travel times
  3. N6-02-03 Calculate port delay times
3. N6-03 Publish information
  1. N6-03-01 Publish information to trucking companies
  2. N6-03-02 Publish information to truck drivers
  3. N6-03-03 Publish information to information kiosk at rest stops
  4. N6-03-04 Publish information to DMS
  5. N6-03-05 Publish information at the port
N7 Need for coordination between highway control systems and emergency response
1. N7-01 Prepare operational plans
2. N7-02 Train operations staff
3. N7-03 Acquire information
  1. N7-03-01 Acquire traffic information
  2. N7-03-02 Acquire event information
4. N7-04 Process information
  1. N7-04-01 Check information quality
  2. N7-04-02 Calculate travel times
  3. N7-04-03 Forecast network demand
  4. N7-04-04 Forecast congestion
  5. N7-04-05 Determine actions in response to current and forecast conditions
  6. N7-04-06 Determine best route for emergency vehicles
5. N7-05 Publish information
  1. N7-05-01 Publish information to related cities
  2. N7-05-02 Publish information to emergency vehicles
N8 Need for coordination for incident response
1. N8-01 Prepare operational procedures
2. N8-02 Train operations staff
3. N8-03 Configure system response plans
4. N8-04 Acquire information
  1. N8-04-01 Acquire traffic information
  2. N8-04-02 Acquire transit information
  3. N8-04-03 Acquire event information
5. N8-05 Process information
  1. N8-05-01 Check information quality
  2. N8-05-02 Calculate travel times
  3. N8-05-03 Determine new incident
  4. N8-05-04 Determine transit service schedule/route adherence
  5. N8-05-05 Determine actions in response to current and forecast conditions
6. N8-06 Publish information
  1. N8-06-01 Publish information to colleague systems
  2. N8-06-02 Publish response actions to colleague systems
  3. N8-06-03 Publish information to transportation network users
  4. N8-06-04 Publish response actions to transportation network users
7. N8-07 Archive incident data from different sources
N9 Need for coordination for infrastructure construction and maintenance
1. N9-01 Prepare guidelines and protocols for coordination
2. N9-02 Train operations staff
3. N9-03 Acquire information
  1. N9-03-01 Acquire traffic information
  2. N9-03-02 Acquire transit information
  3. N9-03-03 Acquire event information
4. N9-04 Process information
  1. N9-04-01 Check information quality
  2. N9-04-02 Estimate impact of the special event
  3. N9-04-03 Determine response actions based on the prepared guidelines and protocols
5. N9-05 Publish information
  1. N9-05-01 Publish information to colleague systems
  2. N9-05-02 Publish response actions to colleague systems
  3. N9-05-03 Publish information to 511 system
N10 Need for coordination of construction work during emergencies
1. N10-01 Prepare guidelines and protocols for coordination
2. N10-02 Train operations staff
3. N10-03 Acquire information
  1. N10-03-01 Acquire traffic information
  2. N10-03-02 Acquire transit information
  3. N10-03-03 Acquire event information
4. N10-04 Process information
  1. N10-04-01 Check information quality
  2. N10-04-02 Calculate travel times
  3. N10-04-03 Determine transit service schedule/route adherence
  4. N10-04-04 Determine remaining network capacity
  5. N10-04-05 Determine action in response to current and forecast conditions
5. N10-05 Publish information
  1. N10-05-01 Publish information to colleague systems
  2. N10-05-02 Publish response actions to colleague systems

4.3 Defining Functional Requirements

A well-formed requirement is a statement of system functionality (a capability) that can be validated, that must be met or possessed by a system to solve a customer problem or to achieve a customer objective, and that is qualified by measurable conditions and bounded by constraints.

The I-880 ICM team followed IEEE1233 and guidance from the U.S. DOT to derive raw functional requirements from the needs. In many cases, after a higher level functional requirement was defined based on the ICMS needs, it was necessary to further decompose such requirements into lower level requirements. After the functional requirements were identified, it was necessary to combine the repetitive requirements as some functions (such as freeway traffic data collection) may be required by more than one need.

Based on the raw functional requirements, well formed requirements were then developed. Requirements were traced back to the needs. In many cases, each requirement may trace to more than one need, as several ICM needs may require one similar ICMS function. Requirements for information content were directly traceable to ITS standards design and data contents (messages and data elements). This was necessary in order to achieve interoperability within the corridor.

4.4 Categorization of the Functional Requirements

The functional requirements must be categorized in order to check the completeness and for indexing. In this process, the I-880 ICM team added structure to the functional requirements by relating them to one another according to the data flow of the traffic control systems. Based on this method, the ICMS functional requirements were categorized into four groups:

Data collection functional requirements (A series of requirements – RA )
Data archiving functional requirements (B series of requirements – RB)
Data processing functional requirements (C series of requirements – RC)
Data dissemination functional requirements (D series of requirements – RD)

Tables 4.4.1 through Table 4.4.4 document the four sets of the ICMS functional requirements. When applicable, quantitative requirements, including primarily time delays and sampling rate, are provided. The requirements are traced back to ICMS needs, denoted under the traceability. The comments section is intended to provide current availability of the function and validation methods.

Table 4.4.1 Data Collection Functional Requirements
ID	Requirement	Traceability	Data Requirements	Allocation		Criticality
RA	ICMS shall acquire corridor-wide transportation information. .	N1 N2 N3 N4 N5 N6 N7 N8 N9 N10		FWY TMC Arterial control center Alameda CMA Cities AC Transit ACS BART control center		H
RA-01	ICMS shall acquire traffic information at a sampling rate of 30 seconds with no more than 30 seconds latency.	N1-01-01 N2-01-01 N3-02-01 N4-03-01 N6-01-01 N7-03-01 N8-04-01 N9-03-01 N10-03-01		FWY TMC Arterial control center Alameda CMA Cities		H
RA-01-01	ICMS shall acquire freeway traffic data from existing detection systems.	N1-01-01 N2-01-01 N3-02-01 N4-03-01 N6-01-01 N7-03-02 N8-04-01 N9-03-01 N10-03-01		FWY TMC		H
RA-01-01-01	ICMS shall acquire freeway traffic flow volume, occupancy, sensor status and speed data along the mainline.	N1-01-01 N2-01-01 N3-02-01 N4-03-01 N6-01-01 -03-02 -04-01 -03-01 N10-03-01	DF-02 DF-03	FWY TMC	Existing	H
RA-01-01-02	ICMS shall acquire freeway ramp volume and sensor status data at all on-ramps with errors of 20% or less.	N1-01-01 N2-01-01 N3-02-01 N4-03-01 N6-01-01 N7-03-02 N8-04-01 N9-03-01 N10-03-01	DF-06	FWY TMC	Existing	H
RA-01-01-03	ICMS shall acquire freeway travel time estimates between predetermined location pairs based on the existing 511 system.	N1-02-02 N2-02-03 N3-03-02 N4-04-02 N6-02-02 N7-04-02 N8-05-02 N10-04-02	DF-01	FWY TMC	Existing	H
RA-01-01-04	ICMS shall acquire status information about the freeway traffic operations system, including the current operational condition of all ramp meters and current messages displayed on variable message signs.	N1-01-04 N2-01-04 N3-02-02 N4-03-04 N5-03-03 N7-03-02 N8-04-03 N10-04-03	DF-04 DF-05 DF-07	FWY TMC	Existing data at TMC	H
RA-01-02	ICMS shall acquire arterial traffic data at intervals of 30 s, with latency of no more than 5s.	N1-01-01 N2-01-01 N3-02-02 N4-03-02 N8-04-01 N9-03-01 N10-03-01		Arterial control center Alameda CMA Cities		H
RA-01-02-01	ICMS shall acquire traffic volume data at signalized intersections on the major arterials parallel to I-880, with errors of 20% or less.	N1-01-01 N2-01-01 N3-02-02 N4-03-02 N8-04-01 N9-03-01 N10-03-01	DA-01	Arterial control center Alameda CMA Cities	Existing for smart corridor	H
RA-01-02-02	ICMS shall acquire traffic speed information at signalized intersections on the major arterials parallel to I-880.	N1-01-01 N2-01-01 N3-02-02 N4-03-02 N8-04-01 N9-03-01 N10-03-01	DA-02	Arterial control center Alameda CMA Cities	Existing for smart corridor	H
RA-01-02-03	ICMS shall acquire traffic flow and speed along major arterials parallel to I-880.	N1-01-01 N2-01-01 N3-02-02 N4-03-02 N8-04-01 N9-03-01 N10-03-01	DA-02	Arterial control center Alameda CMA Cities	Existing for smart corridor	H
RA-02	ICMS shall acquire transit operation data.	N1-01-02 N2-01-02 N4-03-02 N5-03-01 N8-04-02 N9-03-02 N10-03-02		Transit ACS BART control center	Existing but at lower sampling rate	H
RA-02-01	ICMS shall acquire transit bus operation data at a sampling interval of 15 seconds with a latency no greater than 30 seconds.	N1-01-02 N2-01-02 N4-03-03 N5-03-01 N8-04-02 N9-03-02 N10-03-02	DT-01 DT-02 DT-03	Transit ACS BART control center	Existing but at lower sampling rate	H
RA-02-02	ICMS shall acquire rail transit (BART) travel operation data at a sampling interval of 30 seconds, with a latency no greater than 5 seconds.	N1-01-02 N2-01-02 N4-03-03 N5-03-01 N8-04-02 N9-03-02 N10-03-02	DT-04 DT-05 DT-06	Transit ACS BART control center	Existing	H
RA-03	ICMS shall acquire information about the availability of parking spaces at major parking facilities in the corridor (BART lots, Oakland Coliseum, Oakland Airport), with a latency not to exceed 5 minutes and errors not to exceed 5 %.	N1-01-03 N2-01-03 N4-03-03 N5-03-02	DT-07	BART control center Caltrans TMS		H
RA-04	ICMS shall acquire information about major events and major incidents with a latency not to exceed 60 s.	N1-01-04 N2-01-04 N3-02-02 N4-03-04 N5-03-03 N9-03-03		Caltrans TMS Oakland Coliseum		H
RA-04-01	ICMS shall acquire freeway, arterial and transit incident reports from the CHP CAD system or the regional 511 system.	N1-01-04 N2-01-04 N3-02-02 N4-03-04 N5-03-03 N7-03-02 N8-04-03 N9-03-03 N10-03-03	DI-01 DI-02 DI-03	FWY TMC CHP		H
RA-04-02	ICMS shall acquire local incident reports from the city police departments in the corridor, including traffic incidents, major fires and law enforcement actions that disrupt traffic.	N1-01-04 N2-01-04 N3-02-02 N4-03-04 N5-03-03 N7-03-02 N8-04-03 N9-03-03 N10-03-03		Arterial control center Alameda CMA Cities		H
RA-04-02-01	ICMS shall acquire positions of fire, ambulance vehicles.	N1-01-04 N2-01-04 N3-02-02 N4-03-04 N5-03-03 N7-03-02 N8-04-03 N9-03-03 N10-03-03	DI-04	Cities		H
RA-04-03	ICMS shall acquire incident reports from participating incident response agencies in the corridor.	N1-01-04 N2-01-04 N3-02-02 N4-03-04 N5-03-03 N7-03-02 N8-04-03 N9-03-03 N10-03-03	DI-04	FWY TMC Arterial control center Transit ACS BART control center Alameda CMA CHP Cities		H
RA-04-04	ICMS shall acquire reports of strong earthquakes or floods.	N1-01-04 N2-01-04 N3-02-02 N4-03-04 N5-03-03 N7-03-02 N8-04-03 N9-03-03 N10-03-03	DI-05			H
RA-04-05	ICMS shall acquire information about damaged infrastructure, planned road closures and construction from the agencies responsible for operating the affected facilities.	N1-01-04 N2-01-04 N3-02-02 N4-03-04 N5-03-03 N7-03-02 -04-03 N9-03-03 N10-03-03	DI06	FWY TMC		H
RA-04-06	ICMS shall acquire maintenance and construction schedules from all agencies (location and time of lane and road closures).	N9-03-03	DI-07	FWY TMC Arterial control center Cities		H
RA-04-07	ICMS shall acquire information about the type and condition of the emergency response.	N10-03-03	DI-08	FWY TMC CHP Cities		H
RA-04-08	The ICMS shall acquire information about special events at the Coliseum.	N9-03-03		Oakland Coliseum		H
RA-04-09	The ICMS shall receive information about incidents at Port of Oakland.	N9-03-03		Port of Oakland		H

Table 4.4.2 Data Archiving Functional Requirements
ID RB= Functional requirement for Data Archiving Functions	Requirement	Traceability	Allocation (Where the function will be allocated, i.e., - FWY TMC - Arterial control center - Transit ACS - BART control center - Alameda CMA - CHP CAD )	Comment (Measurements methods are to be included here, which will be developed once the requirements are confirmed)	Criticality
RB	ICMS shall archive corridor-wide traffic, transit, and incident data.	N1-04-01 N1-04-02 N1-04-03 N1-04-05 N5-05-04 N8-07	511 FWY TMC		H
RB-01	ICMS shall archive traffic data within 1 second after data are received.	N1-04-01	511 FWY TMC		H
RB-01-01	ICMS shall archive freeway traffic data within 1 second after data are received.	N1-04-01-01	511 FWY PeMS		H
RB-01-02	ICMS shall archive arterial highway traffic data within 1 second after data are received.	N1-04-01-02	Arterial PeMS Alameda CMA Cities		H
RB-02	ICMS shall archive transit data within 1 second after data are received.	N1-04-02		Existing but at lower sampling rate	H
RB-02-01	ICMS shall archive bus transit data within 1 second after data are received.	N1-04-02-01	Transit ACS	Existing but at lower sampling rate	H
RB-02-02	ICMS shall archive rail transit data within 1 second after data are received.	N1-04-02-02	BART control center	Existing	H
RB-02-03	ICMS shall archive transit schedules.	N5-05-04	Transit ACS BART control center		H
RB-02-04	ICMS shall log the confirmation of a schedule modification within 60 seconds after it is received from the AC Transit and/or BART.	N5-05-04	Transit ACS BART control center		H
RB-02-05	ICMS shall log a request from a transit agency for connection protection with a delay of no more than 60 seconds.	N5-04-05	Transit ACS BART control center		H
RB-03	ICMS shall archive incident information collected from all the networks in the corridor in a common database.	N5-04-03 N8-07		Existing for highways using speed measurements	H
RB-03-01	ICMS shall archive incident information collected from local police.	N5-04-03 N8-07	511 Cities		H
RB-03-02	ICMS shall archive incident information collected from CHP.	N5-04-03 N8-07	511 CHP		H
RB-03-03	ICMS shall archive incident information collected from local fire departments.	N5-04-03 N8-07	511 Cities		H

Table 4.4.3 Data Processing Functional Requirements
ID RC=Functional requirement for Data Processing Functions	Requirement	Traceability	Allocation (Where the function will be allocated, i.e., - FWY TMC - Arterial control center - Transit ACS - BART control center - Alameda CMA - CHP CAD )	Comment (Measurements methods are to be included here, which will be developed once the requirements are confirmed)	Criticality
RC-01	ICMS shall check and verify data from different sources.	N1-02-01 N2-02-01 N3-03-01 N4-04-01 N5-04-01 N6-02-01 N7-04-01 N8-05-01 N9-04-01 N10-04-01	ICMS		H
RC-01-01	ICMS shall check the quality of information collected.	N1-02-01 N2-02-01 N3-03-01 N4-04-01 N5-04-01 N6-02-01 N7-04-01 N8-05-01 N9-04-01 N10-04-01	ICMS		H
RC-01-02	ICMS shall process data from different data sources.	N1-02-01 N2-02-01 N3-03-01 N4-04-01 N5-04-01 N6-02-01 N7-04-01 N8-05-01 N9-04-01 N10-04-02	ICMS		H
RC-02	ICMS shall estimate corridor-wide travel time for each link of each network within 10 seconds (freeway, arterial, bus and rail transit).	N1-02-02 N2-02-03 N3-03-02 N4-04-02 N6-02-02 N7-04-02 N8-05-02 N10-04-02	511 FWY TMC Arterial control center Transit ACS BART control center Alameda CMA Cities	Existing for freeways through 511, but needs implementation elsewhere	H
RC-02-01	ICMS shall process freeway data to derive freeway condition estimates in terms of average traffic volume and travel time.	N1-02-02 N1-02-09 N2-02-03 N3-03-02 N4-04-02 N6-02-02 N7-04-02 N8-05-02 N10-04-02	511 FWY TMC	Existing through TOS, 511 and PeMS	H
RC-02-02	ICMS shall estimate arterial travel time between predetermined intersection pairs to derive traffic condition estimates in terms of average traffic volume and travel time.	N1-02-02 N2-02-03 N3-03-02 N4-04-02 N6-02-02 N7-04-02 N8-05-02 N10-04-02	511 Arterial control center Alameda CMA		H
RC-02-03	ICMS shall process transit travel data to derive transit operation condition estimates in terms of passenger volume, travel time and schedule delay.	N1-02-04 N2-02-06 N4-04-04 N5-04-02 N8-05-04 N10-04-03	511 Transit ACS BART control center	Existing in limited portions of the corridor, but needs improvements	H
RC-02-03-01	The ICMS shall estimate time of transit vehicle arrival at the next stop.	N1-02-04 N2-02-06 N4-04-04 N5-04-02 N8-05-04 N10-04-03	511 Transit ACS BART control center		H
RC-02-03-02	ICMS shall estimate time of arrival of other transit vehicles in order to provide connection information at each stop or station.	N1-02-04 N2-02-06 N4-04-04 N5-04-02 N8-05-04 N10-04-03	511 Transit ACS BART control center		H
RC-03	The ICMS shall process information to determine network condition.	N1-02 N2-02 N3-03 N4-04 N5-04 N6-02 N7-04 N8-05 N9-04 N10-04			H
RC-03-01	The ICMS shall process information to determine new incident.	N1-02-03 N2-02-04 N3-03-03 N4-04-03 N8-05-03	ICMS		H
RC-03-02	The ICMS shall process information to forecast major congestion conditions.	N1-02-07 N2-02-08 N3-03-06 N4-04-07 N7-04-04	ICMS		H
RC-03-03	The ICMS shall process information to determine remaining network capacity.	N1-02-05 N2-02-07 N3-03-04 N4-04-05 N10-04-04	ICMS		H
RC-03-04	The ICMS shall process information to forecast network demand.	N1-02-06 N3-03-06 N4-04-06 N5-04-03 N7-04-03 N10-04-04	ICMS		H
RC-04	The ICMS shall generate corridor-wide route/trip guidance information for travelers.	N1-02 N2-02	ICMS 511		H
RC-04-01	The ICMS shall provide dynamic guidance information for requested highway routes.	N1-02 N2-02	ICMS 511		H
RC-04-02	The ICMS shall provide dynamic guidance information for requested transit routes.	N1-02 N2-02	ICMS 511		H
RC-04-03	The ICMS shall provide dynamic guidance information for mixed mode trip requests.	N1-02 N2-02	ICMS 511		H
RC-05	The ICMS shall initiate coordinated operations between freeways and arterials when determining that the available capacity can be better used to balance the network traffic load.	N3	ICMS FWY TMC Arterial control center Cities		H
RC-05-01	The ICMS shall generate signal control strategies for both freeway ramps and arterials when determining that the available capacity can be better used to balance the network traffic load.	N3	ICMS FWY TMC Arterial control center Cities		H
RC-05-02	The ICMS shall generate routing advisory information for travelers based on the updated signal control strategies.	N3	ICMS FWY TMC Arterial control center Cities		H
RC-06	The ICMS shall compute suggested operations for connection protections for incident and special event situations.	N5-04			H
RC-06-01	The ICMS shall compute suggested operations for connection protections for incident.	N5-04			H
RC-06-02	The ICMS shall compute suggested operations for connection protections for special event.	N5-04			H
RC-07	The ICMS shall process information for special event.	N9-04	Oakland coliseum ICMS 511		H
RC-07-01	The ICMS shall estimate traffic volumes on nearby arterial streets and freeway based on the event attendance and event type, combined with normal traffic for that time of day.	N9-04	FWY TMC Arterial control center Alameda CMA Cities		H
RC-07-02	The ICMS shall produce recommendations of a set of signal timing plans to accommodate the estimated traffic volume between 2 hours prior to and 2 hours after the special event.	N9-04-03	FWY TMC Arterial control center Alameda CMA Cities		H
RC-08	ICMS shall process data to enhance OCC's ability to manage transit operation under severe incident conditions and for special events.	N4-05-04	Transit ACS BART control center		H
RC-08-01	ICMS shall process data to support transit OCC's decisions to adjust routes and/or operating schedules based on severity of the incident conditions or to follow pre-arranged operations plans.	N4-05-04	Transit ACS BART control center		H
RC-08-02	ICMS shall process data to support OCC's decisions to adjust routes and/or operating schedules based on special events at least one day in advance.	N4-05-04	Transit ACS BART control center		H
RC-09	ICMS shall enable signal pre-emption for emergency vehicles and recommend best route.	N4-04-09	511 Arterial control center CHP Cities		H
RC-09-01	ICMS shall estimate bus time of arrival (TOA) at intersection with error less than 30 sec at the time when TOA is generated.	N4-04-09	511 Arterial control center CHP Cities		H
RC-09-02	ICMS shall estimate travel time for up to 3 available routes based on real-time traffic data and availability of signal pre-emption.	N4-04-04	511 Arterial control center CHP Cities		H
RC-09-03	ICMS shall generate best routing for emergency vehicles recommendations within 60 seconds of inquiry.	N7-04-06	511 Arterial control center CHP Cities		H
RC-10	ICMS shall process the information about port delays and estimated travel time.	N6	511 Port of Oakland		H
RC-11	ICMS shall process maintenance and construction schedules.	N10	511 FWY TMC Cities		H
RC-12	ICMS shall process traffic condition information to generate recommendations for planning of construction and repair work during emergencies.	N10-04-05	511 FWY TMC Cities		H
RC-13	ICMS shall process information for transit signal priority (through centralized transit CAD/AVL).	N5	Transit ACS		H

Table 4.4.4 Data Dissemination Functional Requirements
ID RD=Functional requirement for Data Dissemination Functions	Requirement	Traceability	Data Requirements	Allocation	Comment	Criticality
RD-01	The ICMS shall enable data exchange between centrally managed database and all transportation systems not to exceed 30 seconds after the information is being requested.	N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11		ICMS 511 FWY TMC Arterial control center Transit ACS BART control center Alameda CMA CHP Cities		H
RD-01-01	ICMS shall provide data to freeway operation management center.	N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11	DPF-01 to 02 DPA-01 to 08 DPT-01 to 07 DPR-01 to04 DPI-01 to 07 DPCM-01 DPSE-01 to 04 DPER-01 to 03 DPPO-01	ICMS FWY TMC		H
RD-01-02	The ICMS shall provide data to arterial traffic operation management center.	N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11	DPF-01 to 02 DPA-01 to 08 DPT-01 to 07 DPR-01 to04 DPI-01 to 07 DPCM-01 DPSE-01 to 04 DPER-01 to 03 DPPO-01	ICMS Arterial control center Alameda CMA Cities		H
RD-01-03	The ICMS shall provide data to AC Transit operation management center.	N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11	DPF-01 to 02 DPA-01 to 08 DPT-01 to 07 DPR-01 to04 DPI-01 to 07 DPCM-01 DPSE-01 to 04 DPER-01 to 03 DPPO-01	ICMS 511 Transit ACS		H
RD-01-02	The ICMS shall provide data to arterial traffic operation management center.	N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11	DPF-01 to 02 DPA-01 to 08 DPT-01 to 07 DPR-01 to04 DPI-01 to 07 DPCM-01 DPSE-01 to 04 DPER-01 to 03 DPPO-01	ICMS Arterial control center Alameda CMA Cities		H
RD-01-04	The ICMS shall provide data to BART operation management center.	N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11	DPF-01 to 02 DPA-01 to 08 DPT-01 to 07 DPR-01 to04 DPI-01 to 07 DPCM-01 DPSE-01 to 04 DPER-01 to 03 DPPO-01	ICMS BART control center		H
RD-01-05	The ICMS shall provide data to CHP operation management center.	N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11	DPF-01 to 02 DPA-01 to 08 DPT-01 to 07 DPR-01 to04 DPI-01 to 07 DPCM-01 DPSE-01 to 04 DPER-01 to 03 DPPO-01	ICMS CHP		H
RD-01-06	The ICMS shall provide data to police operation management center.	N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11	DPF-01 to 02 DPA-01 to 08 DPT-01 to 07 DPR-01 to04 DPI-01 to 07 DPCM-01 DPSE-01 to 04 DPER-01 to 03 DPPO-01	ICMS Cities		H
RD-01-07	The ICMS shall provide data to paramedics operation center.	N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11	DPF-01 to 02 DPA-01 to 08 DPT-01 to 07 DPR-01 to04 DPI-01 to 07 DPCM-01 DPSE-01 to 04 DPER-01 to 03 DPPO-01	ICMS Cities		H
RD-01-08	The ICMS shall provide data to fire department operation management center.	N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11	DPF-01 to 02 DPA-01 to 08 DPT-01 to 07 DPR-01 to04 DPI-01 to 07 DPCM-01 DPSE-01 to 04 DPER-01 to 03 DPPO-01	ICMS Cities		H
RD-02	The ICMS shall provide information to travelers with a latency not to exceed 60 seconds.	N2 N3-04 N4-05 N5-05 N6-03 N8-06 N9-05	DPF-01 to 02 DPA-01 to 08 DPT-01 to 07 DPR-01 to04 DPI-01 to 07 DPCM-01 DPSE-01 to 04 DPER-01 to 03	ICMS 511 Caltrans TMS		H
RD-02-01	The ICMS shall provide information to travelers through CMS.	N2-03-01 N3-04-01 N4-05-01 N5-05-01 N6-03-04	DPF-01 to 02 DPA-01 to 08 DPT-01 to 07 DPR-01 to04 DPI-01 to 07 DPCM-01 DPSE-01 to 04 DPER-01 to 03	ICMS 511 FWY TMC Arterial control center	provides real-time highway info and transit schedules	H
RD-02-02	The ICMS shall provide information to travelers through the 511 system.	N2 N3-04 N4-05 N5-05 N6-03 N8-06 N9-05	DPF-01 to 02 DPA-01 to 08 DPT-01 to 07 DPR-01 to04 DPI-01 to 07 DPCM-01 DPSE-01 to 04 DPER-01 to 03	ICMS 511	511 provides real-time highway info and transit schedules	H
RD-02-02-01	The ICMS shall provide information to travelers through web.	N2 N3-04 N4-05 N5-05 N6-03 N8-06 N9-05	DPF-01 to 02 DPA-01 to 08 DPT-01 to 07 DPR-01 to04 DPI-01 to 07 DPCM-01 DPSE-01 to 04 DPER-01 to 03	ICMS 511		H
RD-02-02-02	The ICMS shall provide information to travelers through phone.	N2 N3-04 N4-05 N5-05 N6-03 N8-06 N9-05	DPF-01 to 02 DPA-01 to 08 DPT-01 to 07 DPR-01 to04 DPI-01 to 07 DPCM-01 DPSE-01 to 04 DPER-01 to 03	ICMS 511		H
RD-02-03	The ICMS shall provide information to travelers at transit stations no later than 60 seconds after the information is being generated.	N2 N3-04 N4-05 N5-05 N6-03 N8-06 N9-05	DPF-01 to 02 DPA-01 to 08 DPT-01 to 07 DPR-01 to04 DPI-01 to 07 DPCM-01 DPSE-01 to 04 DPER-01 to 03	ICMS 511 Transit ACS BART control center		H
RD-02-03-01	The ICMS shall provide information to travelers at AC transit stations.	N2 N3-04 N4-05 N5-05 N6-03 N8-06 N9-05	DPF-01 to 02 DPA-01 to 08 DPT-01 to 07 DPR-01 to04 DPI-01 to 07 DPCM-01 DPSE-01 to 04 DPER-01 to 03	ICMS 511 Transit ACS		H
RD-02-03-02	The ICMS shall provide information to travelers in AC transit buses.	N2 N3-04 N4-05 N5-05 N6-03 N8-06 N9-05	DPF-01 to 02 DPA-01 to 08 DPT-01 to 07 DPR-01 to04 DPI-01 to 07 DPCM-01 DPSE-01 to 04 DPER-01 to 03	ICMS 511 Transit ACS		H
RD-02-03-03	The ICMS shall provide information to travelers at BART stations.	N2 N3-04 N4-05 N5-05 N6-03 N8-06 N9-05	DPF-01 to 02 DPA-01 to 08 DPT-01 to 07 DPR-01 to04 DPI-01 to 07 DPCM-01 DPSE-01 to 04 DPER-01 to 03	ICMS 511 BART control center		H
RD-02-03-04	The ICMS shall provide information to travelers in BART trains.	N2 N3-04 N4-05 N5-05 N6-03 N8-06 N9-05	DPF-01 to 02 DPA-01 to 08 DPT-01 to 07 DPR-01 to04 DPI-01 to 07 DPCM-01 DPSE-01 to 04 DPER-01 to 03	ICMS 511 BART control center		H
RD-02-04	The ICMS shall provide information to truck drivers at Port of Oakland or truck deport no later than 60 seconds after the information is being generated.	N6	DPF-01 to 02 DPA-01 to 08 DPR-01 to04 DPI-01 to 07 DPCM-01 DPSE-01 to 04 DPER-01 to 03 DPPO-01	ICMS 511 Port of Oakland		H

4.4 Validation of Functional Requirements Through Functional Analysis

In order to make sure the functional requirements are complete, it is necessary to validate the completeness of the set of requirements and identify inconsistencies among requirements. Because ICMS will be integrated with the existing ITS systems, it is critical to validate the functional requirements in the context of these existing ITS systems. The I-880 ICM team chose to establish the relationships among ICMS functional requirements in the context of the existing ITS system functions. This approach helps to ensure that each requirement is a necessary and definitive statement of need. The steps of this approach include:

Established the Functional Block Diagram for the existing ITS systems.
Defined the high level functions that accomplish the specific strategy (defined based on needs)
Identified a set of ICMS functions from corresponding functional requirements. The functional groups are:
- Data collection functions (A series of functions)
- Data archiving functions (B series of functions)
- Data processing functions (C series of functions)
- Data dissemination functions (D series of functions)
Established dependency of the ICMS functions in the context of the existing ITS and configured the relevant functions to accomplish high level ICMS functions
Defined Functional Block Diagram that achieves each of the ICM strategies
Verified if the function flow is technically sound

Functional analysis provides a systematic view of what functional elements are needed to support an ICMS system. The functional elements can be graphically connected to form a system functional block diagram, which would become the basis for the initial system design.

In addition to validating the completeness of the functions, this analysis also helps to:

Define the appropriate conditions (quantitative or qualitative measures) for each requirement and avoid requirements pitfalls
Further define data requirements
Provide the basis for the requirements allocation that guides the system implementation and testing.
Facilitate the development of interface requirements

The Figures below show the Functional Black Diagram for the ICMS subsystems. They establish the dependency of the ICMS functions in the context of the existing traffic control system. By means of Functional Diagrams, functions are crossed checked with functional requirements, which become a very useful tool to verify and validate the completeness of the functional requirements.

The functional analysis process has proven to be very effective. Due to the fact that the ICMS will need to be built based upon and integrated with the existing ITS systems, the functional definition and subsystem configuration must be developed in the context of the existing ITS systems. The system analysis method used by the I-880 ICM team put the functional requirements in the context of the existing ITS systems and helped us to discover considerable number of requirement items that were missing or not at the right level. The needs driven requirements process is less structured and it's not easy to come up requirements in the context the existing system designs, conditions and constraints. On the other hands, the needs driven approach also help us to find some gaps from the functional analysis process. The use of the functional analysis and needs driven approaches for the requirements development process provided complimentary means to ensure that the requirements are complete and suitable for implementation.

SS-01 Information Sharing Larger View - use back button to return.

SS-01 Flow Chart showing Information Sharing from Data Collection through Processing

SS-01 Information Sharing (Cont'd) Larger View - use back button to return.

Continuation of SS-01 Flow Chart showing Information Sharing through dissemination

SS-02 Providing Travel Information Through 511 Larger View - use back button to return.

SS-02 Flow Chart showing Providing Traveler Information from Data Collection to Dessemination

SS-03 Providing Information in Real-time to Travelers for En-route Decision Making Larger View - use back button to return.

SS-03 Flow Chart showing En-route Decision Making Information from Data Collection to Dessemination

SS-04 Presenting Travel Advisory Information in Real-Time at Transit Stations and Transit Vehicles Larger View - use back button to return.

SS-04 Flow Chart showing Travel Advisory Information from Data Collection to Dessemination

SS-05 Arterial/Ramp Metering Larger View - use back button to return.

SS-05 Flow Chart showing Arterial/Ramp Metering from Data Collection to Dessemination

SS-06 Facilitating Arterial Signal Control Systems to Handle Special Events Larger View - use back button to return.

SS-06 Flow Chart showing Special Events Facilitation from Data Collection to Dessemination

SS-07 Managing Arterial Signal to Provide Transit System Priority Larger View - use back button to return.

SS-07 Flow Chart showing Managing Arterial Signals for priority from Data Collection to Dessemination

SS-08 Managing Transit Operations under Severe Incident Conditions Larger View - use back button to return.

SS-08 Flow Chart showing Managing Severe Incident Conditions from Data Collection to Dessemination

SS-09 Managing Transit Hub Connection Protection for Special Events Larger View - use back button to return.

SS-09 Flow Chart showing Managing Transit hub for Special Events from Data Collection to Dessemination

SS-10 Advising Truck operators and Driver About Port Delay and Estimated Travel Time Larger View - use back button to return.

SS-11 Flow Chart showing Truck Advisories for Special Events from Data Collection to Dessemination

SS-11 Providing Emergency Vehicle with Signal Pre-emption and Best Routing Recommendations Larger View - use back button to return.

SS-11 Flow Chart showing Routing Recommendations for emergency vehicles from Data Collection to Dessemination

SS-12 Facilitate Rapid Incident Response Larger View - use back button to return.

SS-12 Flow Chart showing Rapid Incident Response from Data Collection to Dessemination

SS-13 Supporting Maintenance and Construction Coordination Larger View - use back button to return.

SS-13 Flow Chart showing Maintenance and Construction Coordination from Data Collection to Dessemination

SS-14 Supporting Coordination of Construction Work During Emergencies Larger View - use back button to return.

SS-14 Flow Chart showing Maintenance and Construction Coordination During Emergencies from Data Collection to Dessemination

Continue to 5: Data Requirements ⇒