Archived Data System --> Archived Data User System:
performance metrics

Definitions

performance metrics (Information Flow): Data that indicates how well the transportation system is performing. Performance metrics are tracked over time to monitor progress towards operations objectives and identify needs and deficiencies to be addressed.

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.

Archived Data User System (Destination Physical Object): 'Archived Data User System' represents the systems users employ to access archived data. The general interface provided allows a broad range of users (e.g. planners, researchers, analysts, operators) and their systems (e.g. databases, models, analytical tools, user interface devices) to acquire data and analyses results from the archive.

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

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

Selected Solution

(None-Data) - Secure Internet (ITS)

Solution Description

This solution is used within Australia, Canada, the E.U. and the U.S.. It combines standards associated with (None-Data) with those for I-I: Secure Internet (ITS). The (None-Data) standards include an unspecified set of standards at the upper layers. 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 gapMind the gap

Development needed
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

CharacteristicValue
Time Context Historical
Spatial Context Regional
Acknowledgement True
CardinalityUnicast
InitiatorDestination
AuthenticableTrue
EncryptFalse


InteroperabilityDescription
RegionalInteroperability 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 Low Moderate Low
Basis Contains information characterizing the performance of some aspect(s) of the transportation system; not typically competetive, will include no PII. Might in some circumstances be slightly sensitive, but there's no clear case where observation of this information by a third party would cause significant impact. Decisions may be made regarding this information; if the information were incorrect, suboptimal decisions may be made. Much depends on how integrated the performance information is to traffic management decision-making. If integral, this could be MODERATE. Generally though, the transportation system should be able to function reasonably with occasional outages.


Security CharacteristicsValue
AuthenticableTrue
Encrypt False