Archived Data Management (Subsystem*)
The Archived Data Management Subsystem (ADMS) 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 subsystem 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 subsystem prepares data products that can serve as inputs to federal, state, and local data reporting systems. This subsystem may be implemented in many different ways. It 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 for a region.Subsystem Interfaces Diagram
Get the Source Graphic, a Enhanced Windows Metafile (EMF), in ZIP format.
Functionality: Equipment Packages* and PSpecs*
- Government Reporting Systems Support (Equipment Package*)
PSpecs:- 8.8-Prepare Government Reporting Inputs
- ITS Data Repository (Equipment Package*)
PSpecs: - On-Line Analysis and Mining (Equipment Package*)
PSpecs:- 8.6-Analyze Archive
- Traffic and Roadside Data Archival (Equipment Package*)
PSpecs:- 8.9-Manage Roadside Data Collection
- Virtual Data Warehouse Services (Equipment Package*)
PSpecs:- 8.4-Coordinate Archives
Inputs/Outputs: Architecture Flows* and Data Flows*
Archived Data Administrator
Archived Data Management
- archive management requests (Architecture Flow*) - User input from the administrator including commands, requests, and queries that support data collection, administration, and management of an ITS data archive.
Data Flows*:
Archived Data Management
Archived Data Administrator
- archive management data (Architecture Flow*) - Presentation of information to the administrator to support the management of an ITS archive including database reports on the condition and quality of the archived data, status of the import and collection process, reports that monitor archive usage, and any special requests that require direct action by the administrator (e.g., requests for access to new data sources).
Data Flows*:
Archived Data Management
Archived Data User Systems
- archive analysis results (Architecture Flow*) - Processed information products, supporting meta data, and any associated transaction information resulting from data mining, analytical processing, aggregation or summarization, report formulation, or other on-line processing and analysis of archived data.
Data Flows*: - archive request confirmation (Architecture Flow*) - Confirmation that an archive request has been received and processed with information on the disposition of the request.
Data Flows*: - archived data products (Architecture Flow*) - Raw or processed data, meta data, data catalogs and other data products provided to a user system upon request. The response may also include any associated transaction information.
Data Flows*:
Archived Data Management
Asset Management
- archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*: - archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*:
Archived Data Management
Border Inspection Administration
- archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*: - archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*:
Archived Data Management
Commercial Vehicle Administration
- archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*: - archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*:
Archived Data Management
Emergency Management
- archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*: - archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*:
Archived Data Management
Emissions Management
- archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*: - archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*:
Archived Data Management
Financial Institution
- payment request (Architecture Flow*) - Request for payment from financial institution.
Data Flows*:
Archived Data Management
Government Reporting Systems
- government reporting system data (Architecture Flow*) - Information provided by an ITS archive, formatted as appropriate, that can be used as input to government data reporting systems.
Data Flows*:
Archived Data Management
Information Service Provider
- archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*: - archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*:
Archived Data Management
Intermodal Freight Depot
- archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*: - archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*:
Archived Data Management
Maintenance and Construction Management
- archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*: - archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*:
Archived Data Management
Map Update Provider
- map update request (Architecture Flow*) - Request for a map update which could include a new underlying map or map layer updates.
Data Flows*:
Archived Data Management
Multimodal Transportation Service Provider
- archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*: - archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*:
Archived Data Management
Other Archives
- archive coordination (Architecture Flow*) - Catalog data, meta data, published data, and other information exchanged between archives to support data synchronization and satisfy user data requests.
Data Flows*:
Archived Data Management
Other Data Sources
- archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*: - archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*:
Archived Data Management
Parking Management
- archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*: - archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*:
Archived Data Management
Payment Administration
- archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*: - archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*:
Archived Data Management
Roadway
- data collection and monitoring control (Architecture Flow*) - Information used to configure and control data collection and monitoring systems.
Data Flows*:
Archived Data Management
Surface Transportation Weather Service
- archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*: - archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*:
Archived Data Management
Traffic Management
- archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*: - archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*: - archived data products (Architecture Flow*) - Raw or processed data, meta data, data catalogs and other data products provided to a user system upon request. The response may also include any associated transaction information.
Data Flows*:
Archived Data Management
Transit Management
- archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*: - archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*: - archived data products (Architecture Flow*) - Raw or processed data, meta data, data catalogs and other data products provided to a user system upon request. The response may also include any associated transaction information.
Data Flows*:
Archived Data Management
Weather Service
- archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*: - archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*:
Archived Data User Systems
Archived Data Management
- archive analysis requests (Architecture Flow*) - A user request that initiates data mining, analytical processing, aggregation or summarization, report formulation, or other advanced processing and analysis of archived data. The request also includes information that is used to identify and authenticate the user and support electronic payment requirements, if any.
Data Flows*: - archived data product requests (Architecture Flow*) - A user-specified request for archived data products (i.e. data, meta data, or data catalogs). The request also includes information that is used to identify and authenticate the user and support electronic payment requirements, if any.
Data Flows*:
Asset Management
Archived Data Management
- asset archive data (Architecture Flow*) - Information describing transportation assets including pavements, bridges, and all other infrastructure included in the transportation network. In addition, information can cover support assets (support equipment and systems, software, etc.). Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows*:
Border Inspection Administration
Archived Data Management
- border information archive data (Architecture Flow*) - Border inspection activities data. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows*:
Border Inspection Systems
Archived Data Management
- border wait times archived data (Architecture Flow*) - Wait time data to be archived and used for planning and analysis activities.
Data Flows*:
Commercial Vehicle Administration
Archived Data Management
- commercial vehicle archive data (Architecture Flow*) - Information describing commercial vehicle travel and commodity flow characteristics. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows*:
Emergency Management
Archived Data Management
- emergency archive data (Architecture Flow*) - Logged emergency information including information that characterizes identified incidents (routine highway incidents through disasters), corresponding incident response information, evacuation information, surveillance data, threat data, and resource information. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows*:
Emissions Management
Archived Data Management
- emissions archive data (Architecture Flow*) - Air quality and vehicle emissions information that is collected by sensors or derived from models. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows*:
Financial Institution
Archived Data Management
- transaction status (Architecture Flow*) - Response to transaction request. Normally dealing with a request for payment.
Data Flows*:
Government Reporting Systems
Archived Data Management
- government reporting data receipt (Architecture Flow*) - The acknowledgement of satisfactory receipt of information used as input to government data systems or a report identifying problems or issues with the data submittal.
Data Flows*:
Information Service Provider
Archived Data Management
- traveler archive data (Architecture Flow*) - Data associated with traveler information services including service requests, facility usage, rideshare, routing, and traveler payment transaction data. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows*:
Intermodal Freight Depot
Archived Data Management
- intermodal freight archive data (Architecture Flow*) - Information describing demand at intermodal freight terminals including loading/unloading activities of trailers and containers. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows*:
Maintenance and Construction Management
Archived Data Management
- maint and constr archive data (Architecture Flow*) - Information describing road construction and maintenance activities identifying the type of activity, the work performed, and work zone information including work zone configuration and safety (e.g., a record of intrusions and vehicle speeds) information. For construction activities, this information also includes a description of the completed infrastructure, including as-built plans as applicable. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows*:
Map Update Provider
Archived Data Management
- map updates (Architecture Flow*) - Map update which could include a new underlying static or real-time map or map layer(s) update.
Data Flows*:
Multimodal Transportation Service Provider
Archived Data Management
- multimodal archive data (Architecture Flow*) - Operational information from alternate passenger transportation modes including air, rail transit, taxis, and ferries. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows*:
Other Archives
Archived Data Management
- archive coordination (Architecture Flow*) - Catalog data, meta data, published data, and other information exchanged between archives to support data synchronization and satisfy user data requests.
Data Flows*:
Other Data Sources
Archived Data Management
- other data source archive data (Architecture Flow*) - Data extracted from other data sources. A wide range of ITS and non-ITS data and associated meta data may be provided.
Data Flows*:
Parking Management
Archived Data Management
- parking archive data (Architecture Flow*) - Data used to analyze and monitor trends in parking demand, pricing, and operational actions. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows*:
Payment Administration
Archived Data Management
- toll archive data (Architecture Flow*) - Data indicating toll facility usage and pricing schedules. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows*:
Roadway
Archived Data Management
- probe archive data (Architecture Flow*) - Probe data that allows calculation of travel times, volumes, and other measures that support transportation planning. Optionally, this flow also includes origin and destination information for vehicles that opt to provide this information.
Data Flows*: - roadside archive data (Architecture Flow*) - A broad set of data derived from roadside sensors that includes current traffic conditions, environmental conditions, and any other data that can be directly collected by roadside sensors. This data also indicates the status of the sensors and reports of any identified sensor faults.
Data Flows*:
Surface Transportation Weather Service
Archived Data Management
- transportation weather information (Architecture Flow*) - Current and forecast road conditions and weather information (e.g., surface condition, flooding, wind advisories, visibility, etc.) associated with the transportation network. This information is of a resolution, timeliness, and accuracy to be useful in transportation decision making.
Data Flows*:
Traffic Management
Archived Data Management
- archived data product requests (Architecture Flow*) - A user-specified request for archived data products (i.e. data, meta data, or data catalogs). The request also includes information that is used to identify and authenticate the user and support electronic payment requirements, if any.
Data Flows*: - traffic archive data (Architecture Flow*) - Information describing the use and vehicle composition on transportation facilities and the traffic control strategies employed. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows*:
Transit Management
Archived Data Management
- archived data product requests (Architecture Flow*) - A user-specified request for archived data products (i.e. data, meta data, or data catalogs). The request also includes information that is used to identify and authenticate the user and support electronic payment requirements, if any.
Data Flows*: - transit archive data (Architecture Flow*) - Data used to describe and monitor transit demand, fares, operations, and system performance. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows*:
Weather Service
Archived Data Management
- weather archive data (Architecture Flow*) - Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity, precipitation, visibility, light conditions, etc.) as well as qualified environmental sensor data. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows*:

