Other Archived Data Systems --> Archived Data System:
archive coordination
This triple is bi-directional. See also
Archived Data System --> Other Archived Data Systems: archive coordination
Definitions
archive coordination (Information Flow): Catalog data, meta data, published data, and other information exchanged between archives to support data synchronization and satisfy user data requests.
Other Archived Data Systems (Source Physical Object): 'Other Archived Data Systems' represents distributed archived data systems whose data can be accessed and shared with a local archive. The interface with the Archived Data System allows data from multiple archives to be accessed on demand or imported and consolidated into a single repository.
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) - Guaranteed Secure Internet (ITS) (32)
- US: ADMS - Guaranteed Secure Internet (ITS) (32)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
Development needed |
Security
|
|
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 | National |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Destination |
Authenticable | True |
Encrypt | True |
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 | Moderate | High | High | |
Basis | Archive coordination may involve substantial meta data that indicates how users are using archived data systems, and may include queries that betray intent. Observation of this information provides a third party with intelligence about system users that should not be observable. | Incorrect coordination could lead to substantial performance challenges for the archive systems, degrading overall performance which affects all users. Depending what the archive is used for, this might be reduced to MODERATE | Without this flow, archive usage that spans multiple systems will be impossible, making archive requests unusable. Depending on what the archive is used for, this might be reduced to MODERATE. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |