6. Interface Requirements
I-880 ICM will be a distributed system and will be built upon the existing ITS systems responsible for managing the transportation systems and providing traveler information along the I-880 corridor. These systems include:
- Bay Area 511 (operated by MTC)
- Freeway management system (operated by Caltrans)
- Arterial traffic control system (operated by Caltrans)
- Arterial traffic control systems (operated by Oakland, San Leandro, Hayward, and Fremont)
- Alameda Smart Corridor (operated by Alameda CMA)
- Transit Advanced Communication System – ACS (operated by AC Transit)
- BART train control system (operated by BART)
- Transit NextBus information system (operated by NextBus under AC Transit contract)
While these systems will become the foundation for the I-880 ICM, new ICM elements that include limited hardware add-ons, additional communication links and software that support the integration of the existing systems into an ICM will be established. The interfaces of the ICM subsystems in the context of the existing ITS systems are depicted in Figure 2.3 through Figure 2.10 in Section 2.5. These interfaces between the new ICM elements and the existing ITS systems will apply the interface standards and protocols adopted for these existing systems. Table 6.1 provides interface requirements. Note that the letters 'a' through 'x' in the requirement names (e.g., RIa) are defined in the Figures 2.3 to Figure 2.10. Interface 'x' refers to existing interfaces, which are not re-specified in the ICM interface requirements. Interface requirements in most of cases refer to the Interface Control Documents (ICD) that the existing ITS systems use. ICDs are already available for some of the ITS systems while ICDs for other systems will need to be created prior to the development of the I-880 ICM system. The ICM ICD will reference the ICDs for the existing systems and will clearly define the requirements for the interfaces between newly established ICM elements and the existing ITS systems.
| ID | Requirement | Subsystems that the interface requirement supports | Physical Interface Requirements | Protocol Requirements | Notes | Criticality |
|---|---|---|---|---|---|---|
| IR-a | The ICMS database manager shall maintain two way communication with freeway TMS | SS-01
SS-02 SS-03 SS-04 SS-05 SS-06 SS-07 SS-08 SS-10 SS-11 SS-12 SS-13 |
The communication between ICMS subsystems and ICMS database manager shall use Internet connection | ICMS subsystems shall communicate with ICMS database manager XML-formatted data via the Java Message Service (JMS) | The interface requirement and communication protocol are defined by "Data Dissemination Architecture for 511" [17] and TravInfo® Open Messaging Service (TOMS) [18] | H |
| IR-b | The ICMS database manager shall maintain two way communication with Freeway PeMS | SS-01 | The communication between ICMS subsystems and ICMS database manager shall use Internet connection | ICMS subsystems shall communicate with ICMS database manager XML-formatted data via the Java Message Service (JMS) | Communication link already exist between 511 and PeMS | H |
| IR-c | The ICMS database manager shall maintain two way communication with CHP emergency response CAD | SS-01
SS-11 SS-12 SS-13 |
The communication between ICMS subsystems and ICMS database manager shall use Internet connection | ICMS subsystems shall communicate with ICMS database manager XML-formatted data via the Java Message Service (JMS) | Communication link already exist between 511 and CHP emergency response CAD | H |
| IR-d | The ICMS database manager shall maintain two way communication with AC Transit ACS | SS-01
SS-02 SS-03 SS-04 SS-07 SS-08 SS-09 SS-13 |
The communication between ICMS subsystems and ICMS database manager shall use Internet connection | ICMS subsystems shall communicate with ICMS database manager XML-formatted data via the Java Message Service (JMS) | Communication link is being developed between 511 and AC Transit ACS. | H |
| IR-e | The ICMS database manager shall maintain two way communication with BART CTC | SS-01
SS-02 SS-03 SS-04 SS-08 SS-09 SS-13 |
The communication between ICMS subsystems and ICMS database manager shall use Internet connection | ICMS subsystems shall communicate with ICMS database manager XML-formatted data via the Java Message Service (JMS) | Communication link is being developed between 511 and BART CTC. | H |
| IR-f | The ICMS database manager shall maintain two way communication with MTC 511 | SS-01
SS-02 SS-03 SS-04 SS-05 SS-06 SS-07 SS-08 SS-09 SS-10 SS-11 SS-12 SS-13 |
The communication between ICMS subsystems and ICMS database manager shall use Internet connection | ICMS subsystems shall communicate with ICMS database manager XML-formatted data via the Java Message Service (JMS) | 511 already uses the said interface and protocols. | H |
| IR-g | The ICMS database manager shall maintain two way communication with Caltrans arterial TMS | SS-01
SS-02 SS-03 SS-04 SS-05 SS-06 SS-07 SS-11 SS-12 SS-13 |
The communication between ICMS subsystems and ICMS database manager shall use Internet connection | ICMS subsystems shall communicate with ICMS database manager XML-formatted data via the Java Message Service (JMS) | H | |
| IR-h | The ICMS database manager shall maintain two way communication with cities arterial TMS | SS-01
SS-02 SS-03 SS-04 SS-05 SS-06 SS-07 SS-11 SS-12 SS-13 |
The communication between ICMS subsystems and ICMS database manager shall use Internet connection | ICMS subsystems shall communicate with ICMS database manager XML-formatted data via the Java Message Service (JMS) | This is optional | H |
| IR-i | The ICMS database manager shall maintain two way communication with ACCMA arterial data system | SS-01
SS-11 SS-12 |
The communication between ICMS subsystems and ICMS database manager shall use Internet connection | ICMS subsystems shall communicate with ICMS database manager XML-formatted data via the Java Message Service (JMS) | H | |
| IR-j | The ICMS database manager shall maintain two way communication with Oakland Coliseum | SS-01 | The communication between ICMS subsystems and ICMS database manager shall use Internet connection | ICMS subsystems shall communicate with ICMS database manager XML-formatted data via the Java Message Service (JMS) | H | |
| IR-k | The ICMS database manager shall maintain two way communication with Port of Oakland Freight Management System | SS-10 | The communication between ICMS subsystems and ICMS database manager shall use Internet connection | ICMS subsystems shall communicate with ICMS database manager XML-formatted data via the Java Message Service (JMS) | H | |
| IR-l | The ICMS database manager shall maintain two way communication with Fire/Police/Paramedics departments | SS-01
SS-13 |
The communication between ICMS subsystems and ICMS database manager shall use Internet connection | ICMS subsystems shall communicate with ICMS database manager XML-formatted data via the Java Message Service (JMS) | H | |
| IR-m | The arterial TMS shall maintain two way communication with Arterial CMS | SS-02
SS-03 SS-04 SS-06 |
The communication between arterial TMS and CMS shall use frame relay or wireless communicaton | The arterial TMS shall communicate with CMS using the Caltrans existing center-to-CMS protocols | H | |
| IR-n | The BART CTC maintain two way communication with rail station ICM signage | SS-02
SS-03 SS-04 SS-08 |
The communication between BART CTC and ICM signage shall use wire communication | The ICMS communicate with signage shall be XML-formatted data via the Java Message Service (JMS) | H | |
| IR-o | The Transit ACS shall maintain two way communication with bus transit station signage | SS-02
SS-03 SS-04 SS-08 |
The communication between AC Transit ACS and station signage shall use wireless communication | The ICMS communicate with signage shall be XML-formatted data via the Java Message Service (JMS) | H | |
| IR-p | The arterial TMS shall maintain two way communication with freeway TMS | SS-05 | The communication between arterial TMX and freeway TMS shall frame relay or wireless communication | The arterial TMS shall communicate with CMS using the Caltrans existing center-to-center comm protocols | H | |
| IR-q | The Freight Management Center shall maintain two way communication with ICM signage | SS-10 | The communication between ICMS subsystems and ICMS database manager shall use Internet connection | ICMS subsystems shall communicate with ICMS database manager XML-formatted data via the Java Message Service (JMS) |