NMDOT Historical Traffic Database - Archived Data Management Functionality
Subsystem Description
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.
Functional Area: ITS Data Repository
Collect and maintain data and data catalogs from one or more data sources. May include quality checks, error notification, and archive coordination.
| ID | Requirement | Status |
|---|---|---|
| 1 | The center shall collect data to be archived from one or more data sources. | Planned |
| 3 | The center shall store the archived data in a focused repository that is suited to a particular set of ITS data users. | Planned |
| 6 | The center shall include capabilities for archive to archive coordination. | Planned |
| 7 | The center shall support a broad range of archived data management 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. | Planned |
| 9 | The center shall provide the capability to execute methods on the incoming data such as cleansing, summarizations, aggregations, or transformations applied to the data before it is stored in the archive. | Planned |
| 11 | When data or a catalog of data is received from the archive, the center shall generate the requested data product for the users systems. | Planned |