Element

 

 

Sedgwick County Government Data Repository

Interconnects - Flows - Entities - Services - Functional Requirements

Status:

Existing

Definition:

Maintain/archive data for a variety of uses and operates similar to a data clearinghouse.

Stakeholder:

Sedgwick County

return to top

Systems Interconnected
with the Sedgwick County Government Data Repository

Interconnect

Diagram

return to top

Architecture Flow Diagrams
which include Sedgwick County Government Data Repository:

return to top

Architecture Flows
to/from the Sedgwick County Government Data Repository:

Sedgwick County Government Data Repositoryflows intoKDOT Planning Archive Sedgwick County Government Data Repositoryflows intoSedgwick County 911 Sedgwick County Government Data Repositoryflows intoWichita Government Data Repository KDOT Planning Archiveflows intoSedgwick County Government Data Repository Sedgwick County 911flows intoSedgwick County Government Data Repository Wichita Government Data Repositoryflows intoSedgwick County Government Data Repository

return to top

National ITS Architecture Subsystems
mapped to the Sedgwick County Government Data Repository:

return to top

National ITS Architecture Services
associated with Sedgwick County Government Data Repository:

return to top

National ITS Architecture Functional Requirements
associated with Sedgwick County Government Data Repository:

ITS Data Repository
  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 respond to requests from the administrator interface function to maintain the archive data.
  10. When data or a catalog of data is received from the archive, the center shall generate the requested data product for the users systems.
Government Reporting Systems Support
  1. The center shall provide data from an ITS archive to federal, state, or local government reporting systems.
  2. The center shall support requests for ITS archived data from Government Reporting Systems.
On-Line Analysis and Mining
  1. The center shall support the interface with Archive Data User Systems for requests for analysis of the archive data.

Date modified: 11/17/2006