ITS Object --> Other ITS Objects:
ITS information
This triple is bi-directional. See also
Other ITS Objects --> ITS Object: ITS information
Definitions
ITS information (Information Flow): Information exchanged by ITS systems or devices. This flow is a super-flow; it does not define specific content since it represents any information flow exchange between physical objects defined in ARC-IT. This information flow represents any of those information flows and inherits the data content and attributes defined in the more detailed information flows.
ITS Object (Source Physical Object): The general 'ITS Object' includes core capabilities common to any class of object.
Other ITS Objects (Destination Physical Object): Representing other ITS Objects, 'Other ITS Objects' provides a source and destination for information exchange between ITS Objects.
Included In
This Triple is in the following Service Packages:
This Triple is described by the following Functional View Functional Objects:
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
| None |
Communication Solutions
No communications solutions identified.Characteristics
| None defined |
| Interoperability | Description |
|---|---|
| Regional | Interoperability throughout the geopolitical region is highly desirable, but if implemented differently in different transportation management jurisdictions, significant benefits will still accrue in each jurisdiction. Regardless, this Information Flow Triple should be implemented consistently within a transportation jurisdiction (i.e., the scope of a regional architecture). |
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | High | High | High | |
| Basis | This value is derived from the specific flows satisfied by this super-flow. HIGH is set because some flows may require it. If the implementation includes flows with only a MODERATE or LOW confidentiality requirement, then this could be MODERATE or LOW, as appropriate. | This value is derived from the specific flows satisfied by this super-flow. HIGH is set because some flows may require it. If the implementation includes flows with only a MODERATE integrity requirement, then this could be MODERATE. | This value is derived from the specific flows satisfied by this super-flow. HIGH is set because some flows may require it. If the implementation includes flows with only a MODERATE integrity requirement, then this could be MODERATE. | |
| None defined |