The Archived Data Management Subsystem 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, Provincial, and local data reporting systems. This subsystem may be implemented in many different ways. It may reside within an operational centre and provide focused access to a particular agency's data archives. Alternatively, it may operate as a distinct centre that collects data from multiple agencies and sources and provides a general data warehouse service for a region.
Security Considerations
The Archived Data Management Subsystem security considerations are directly related to the sensitivity of the data contained in the archive. Some ITS archives include crash reports, personal information, and other sensitive information that requires significant security safeguards. Most archives are much less sensitive, containing bulk ITS information that is not confidential and does not require special security measures. Like confidentiality, the required availability of each archive must be considered based on the archive’s application. In many, but not all, cases, archives are used for off-line applications where short-term loss of availability will not cause serious impact to the transportation system. In many cases, the most critical objective for data archives will be data integrity. Since archives are frequently used to measure performance of the transportation system and provide data that supports operations and planning, the accuracy and reliability of the data contained in the archive is paramount. Each archive should be reviewed by the system manager and data owners to ensure that security is consistent with the sensitivity of the archived data.
Functionality: Equipment Packages and PSpecs
Inputs/Outputs: Architecture Flows and Data Flows
- archive management requests - User input from the administrator including commands, requests, and queries that support data collection, administration, and management of an ITS data archive.
Data Flows:
- archive management data - 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:
- archive analysis results - 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 - Confirmation that an archive request has been received and processed with information on the disposition of the request.
Data Flows:
- archived data products - 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 Subsystem > Asset Management
- archive requests - 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 - 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:
- archive requests - 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 - 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:
- archive requests - 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 - 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:
- archive requests - 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 - 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:
- archive requests - 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 - 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:
- payment request - Request for payment from financial institution.
Data Flows:
- government reporting system data - Information provided by an ITS archive, formatted as appropriate, that can be used as input to government data reporting systems.
Data Flows:
- archive requests - 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 - 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:
- archive requests - 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 - 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:
- archive requests - 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 - 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:
- map update request - Request for a map update which could include a new underlying map or map layer updates.
Data Flows:
- archive requests - 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 - 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:
- archive requests - 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 - 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:
- archive requests - 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 - 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 Subsystem > Other Archives
- archive coordination - 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 Subsystem > Other Data Sources
- archive requests - 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 - 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 Subsystem > Parking Management
- archive requests - 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 - 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 Subsystem > Roadway Subsystem
- archive requests - 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 - 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 Subsystem > Traffic Management
- archive requests - 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 - 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 - 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 Subsystem > Transit Management
- archive requests - 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 - 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 - 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:
- archive analysis requests - 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 - 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 Subsystem
- asset archive data - 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 information archive data - 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:
- commercial vehicle archive data - 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 archive data - 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 archive data - 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:
- transaction status - Response to transaction request. Normally dealing with a request for payment.
Data Flows:
- government reporting data receipt - 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:
- traveller archive data - Data associated with traveller information services including service requests, facility usage, rideshare, routing, and traveller 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 archive data - 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:
- maint and constr archive data - 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 updates - Map update which could include a new underlying static or real-time map or map layer(s) update.
Data Flows:
- transportation weather information - 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:
- multimodal archive data - 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:
- weather archive data - 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:
Other Archives > Archived Data Management Subsystem
- archive coordination - 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 Subsystem
- other data source archive data - 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 Subsystem
- parking archive data - 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:
Roadway Subsystem > Archived Data Management Subsystem
- probe archive data - 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 - 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:
- toll archive data - 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:
Traffic Management > Archived Data Management Subsystem
- archived data product requests - 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 - 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 Subsystem
- archived data product requests - 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 - 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: