Cincinnati (OKI) Regional ITS Architecture


Menu
Region Home
Stakeholders
ITS Inventory by Stakeholder
ITS Inventory by Entity
Market Packages by Stakeholder
Market Packages by Functional Area
Projects By Stakeholder
Projects By Functional Area
Market Package Descriptions
Sausage Diagram
Equipment Package Descriptions
Architecture Flow Descriptions
Project Documents
Send Your Comments

 

 

Equipment Package: ITS Data Repository

Description: This equipment package 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. This equipment package includes capabilities for performing quality checks on the incoming data, error notification, and archive to archive coordination. This equipment package 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.
Included In: ARTIMIS Archive
INDOT Traffic Data Archive
KSP CRASH Database
KYTC Division of Planning
ODOT D8 Traffic Data Archive
ODOT Office of Technical Services
ODPS Crash System
OKI Transportation Planning Database
SORTA Data Warehouse
TANK Data Archive
Functional Requirements 1 - The center shall collect data to be archived from one or more data sources.
2 - The center shall collect data catalogs from one or more data sources. A catalog describes the data contained in the collection of archived data and may include descriptions of the schema or structure of the data, a description of the contents of the data; e.g., time range of entries, number of entries; or a sample of the data (e. g. a thumbnail).
3 - The center shall store the archived data in a focused repository that is suited to a particular set of ITS data users.
4 - The center shall include capabilities for performing quality checks on the incoming archived data.
5 - The center shall include capabilities for error notification on the incoming archived data.
6 - The center shall include capabilities for archive to archive coordination.
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.
8 - The center shall perform quality checks on received data.
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.
10 - The center shall respond to requests from the administrator interface function to maintain the archive data.
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.
12 - For archive data requiring financial payment, the center shall process the financial requests and manage an interface to a Financial Institution.

Last updated: 03-11-08