ITS Roadway Equipment --> Archived Data System:
roadway performance data
Definitions
roadway performance data (Information Flow): Roadway data from sensors and intersection equipment used to define the performance of the roadway and intersections.
ITS Roadway Equipment (Source Physical Object): 'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway. This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.
Archived Data System (Destination Physical Object): The 'Archived Data System' collects, archives, manages, and distributes data generated from ITS sources for use in transportation administration, policy evaluation, safety, planning, performance monitoring, program assessment, operations, and research applications. The data received is formatted and tagged with attributes that define the data source, conditions under which it was collected, data transformations, and other information (i.e. meta data) necessary to interpret the data. The archive can fuse ITS generated data with data from non-ITS sources and other archives to generate information products utilizing data from multiple functional areas, modes, and jurisdictions. The archive prepares data products that can serve as inputs to federal, state, and local data reporting systems. The 'Archived Data System' may reside within an operational center and provide focused access to a particular agency's data archives. Alternatively, it may operate as a distinct center that collects data from multiple agencies and sources and provides a general data warehouse service.
Included In
This Triple is in the following Service Packages:
This triple is associated with the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
| None |
Communication Solutions
-
(None-Data) - Secure Internet (ITS) (43)
-
(None-Data) - OMG DDS (44)
-
(None-Data) - Apache Kafka (44)
-
(None-Data) - Eclipse Zenoh (45)
-
(None-Data) - OASIS MQTT (50)
-
(None-Data) - OASIS AMQP (61)
Selected Solution
(None-Data) - Apache KafkaSolution Description
|
ITS Application Entity
![]()
Development needed ![]() |
Click gap icons for more info.
|
||
|
Mgmt
Apache Zookeeper ![]() |
Facilities
![]() ![]()
Development needed ![]() Apache Kafka ![]() Apache Zookeeper ![]() |
Security
IETF RFC 8446 ![]() |
|
|
TransNet
|
|||
|
Access
Internet Subnet Alternatives ![]() |
|||
Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.
Characteristics
| Characteristic | Value |
|---|---|
| Time Context | Recent |
| Spatial Context | Regional |
| Acknowledgement | True |
| Cardinality | Unicast |
| Initiator | Source |
| Authenticable | True |
| Encrypt | False |
| Interoperability | Description |
|---|---|
| Local | In cases where an interface is normally encapsulated by a single stakeholder, interoperability is still desirable, but the motive is vendor independence and the efficiencies and choices that an open standards-based interface provides. |
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | Low | Moderate | Low | |
| Basis | Should eventually be public, and regardless it is unlikely that sharing this data will cause any harm. | Could be used to make traffic management and personnel decisions, so some guarantee the data at the destination is what the sender intended is warranted. Still, this flow is a candidate for LOW if the range for integrity is opened up to include it. | Unlikely that the lack of this flow will radically change outcomes. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | False |


