Archived Data System --> Government Reporting Systems:
government reporting system data

Definitions

government reporting system data (Information Flow): Information provided by an ITS archive, formatted as appropriate, that can be used as input to government data reporting systems.

Archived Data System (Source 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.

Government Reporting Systems (Destination Physical Object): 'Government Reporting Systems' represents the system and associated personnel that prepare the inputs to support the various local, state, and federal government transportation data reporting requirements (e.g. Highway Performance Monitoring System, Fatality Analysis Reporting System) using data collected by ITS systems. It represents a system interface that provides access to the archived data relevant to these reports. In most cases, this system will combine data collected from ITS archives with data from non-ITS sources to assemble the required information.

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:

RelationshipSourceDestinationFlow
Interactive Government Reporting Systems Archived Data System government reporting data receipt

Communication Solutions

Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

US: ADMS - Secure Internet (ITS)

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with US: ADMS with those for I-I: Secure Internet (ITS). The US: ADMS standards include upper-layer standards required to implement interfaces with an archived data management system. The I-I: Secure Internet (ITS) standards include lower-layer standards that support secure communications between ITS equipment using X.509 or IEEE 1609.2 security certificates.

ITS Application Entity
Mind the gapMind the gap
Click gap icons for more info.
Mgmt
Facilities
Mind the gap

Development needed
Security
Mind the gapMind the gap
TransNet
Access

Internet Subnet Alternatives
TransNet TransNet

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Access Access

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

ITS Application ITS Application

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Mgmt Mgmt

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Facility Facility

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Security Security

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

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 Historical
Spatial Context Regional
Acknowledgement True
Cardinality Unicast
Initiator Source
Authenticable True
Encrypt False


Interoperability Description
National This triple should be implemented consistently within the geopolitical region through which movement is essentially free (e.g., the United States, the European Union).

Security

Information Flow Security
  Confidentiality Integrity Availability
Rating Low High Low
Basis Data to be used as the basis for published reports probably does not need obfuscation. The cost of exposing this data is minimal, as it presumably should be publicly accessible through some means. Given that the data will be used to produce public reports upon which policy may be enacted, its accuracy is critically important, as any misrepresentation could lead to public distrust or decisions based on incorrect data. Should not often be sent, so intermittent connectivity should be sufficient.


Security Characteristics Value
Authenticable True
Encrypt False