archived data products Quintuple

Bidirectional?: True

archived data products (A-Interconnect): This CVRIA application interconnect encapsulates all of the Layer 2 information flows between the 'Archive Data Repository' application object and the 'Archived Data User Systems' physical object. This application interconnect is bi-directional since the underlying layer 2 information flows carry data in both directions.

Archived Data User Systems (Source Physical Object): 'Archived Data User Systems' 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.

Archived Data Center (Destination Physical Object): The 'Archived Data Center' 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 Center' 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.

Archive Data Repository (Destination Application Object): "Archive Data Repository" collects data and data catalogs from one or more data sources and stores the data in a focused repository that is suited to a particular set of ITS data users. It includes capabilities for performing quality checks on the incoming data, error notification, and archive to archive coordination. It supports a broad range of implementations, ranging from simple data marts that collect a focused set of data and serve a particular user community to large-scale data warehouses that collect, integrate, and summarize transportation data from multiple sources and serve a broad array of users within a region.