Home

Statewide:

 by Stakeholder

 by Entity

District 1

District 2

District 3

District 4&6

District 5

District 7

Turnpike
 

 Send Your 

 Comments



Traffic and Roadside Data Archival Equipment Package

Description:

 This equipment package collects and archives traffic, roadway, and environmental information for use in off-line planning, research, and analysis. The equipment package controls and collects information directly from equipment at the roadside, reflecting the deployment of traffic detectors that are used primarily for traffic monitoring and planning purposes rather than for traffic management.

 

Included in:

 Air Quality Database
Contracts Administration System (Virtis)
Control Burn Permitting Database
County and City Transp. Data Collection Systems
Demand-Response/Rural Transit Database
Draw Bridge Operational Status System
Draw Bridge Operations Schedules
Equipment Management and Inventory System
FDOT Aviation Database
FDOT Bridge Management Inventory System (Pontis)
FDOT District Transp. Data Collection Systems
FDOT Roadway Characteristics Inventory
FDOT Seaport Database
FDOT Traffic Characteristics Inventory
FDOT Transit Database
Florida Safety and Crash Data Collection System
Manpower, Assets, and Resources System (MARS)
Rail Operations Database
Rail-Highway Grade Crossings Database
RPC/MPO Transp. Data Collection System
Skid Hazard Inventory
State Highway System Crash Analysis Reporting System

Processes:
8.9Manage Roadside Data Collection
  

User Service Requirements (fully or partially addressed):

7.0Information Management
7.1Archived Data Function
7.1.0ITS shall provide an Archived Data Function to control the archiving and distribution of ITS data. The Archived Data User Service provides the Historical Data Archive Repositories and controls the archiving functionality for all ITS data with five major functions: 1) the Operational Data Control function to manage operations data integrity; 2) the Data Import and Verification function to acquire historical data from the Operational Data Control function; 3) the Automatic Data Historical Archive function for permanently archiving the data; 4) the Data Warehouse Distribution function, which integrates the planning, safety, operations, and research communities into ITS and processes data products for these communities; and 5) the ITS Community Interface which provides the ITS common interface to all ITS users for data products specification and retrieval. ADUS helps achieve the ITS information goal of unambiguous interchange and reuse of data and information throughout all functional areas.
7.1.2The Archived Data Function shall include an Operational Data Control (ODC) function to ensure integrity of operational data as received from field equipment or data collection devices.
7.1.2.1ODC shall be capable of receiving and storing all ITS operational data, as received from the source.
7.1.2.1.1ODC shall ensure ITS operational data are in proper format.
7.1.2.1.2ODC shall maintain the meta data schema for all ITS data entering the system.
7.1.2.1.3ODC shall be capable of assigning the following meta attributes, when available, to ITS operational data during the archive process.
7.1.2.1.3(a)The equipment used to collect the data.
7.1.2.1.3(b)The conditions under which the data were collected.
7.1.2.1.3(c)The status of the equipment at the time of collection.
7.1.3The Archived Data Function shall include a Data Import and Verification (DIV) function to acquire historical data from the Operational Data Control function.
7.1.3.1DIV shall be capable of importing selected ITS Operational data from the ITS Operational Repositories.
7.1.3.1.1DIV shall be capable of importing ITS Freeway Operations data to include:
7.1.3.1.1(a)Freeway traffic flow surveillance data.
7.1.3.1.1(c)Ramp meter operational data.
7.1.3.1.3DIV shall be capable of importing ITS Arterial data to include:
7.1.3.1.3(e)Arterial traffic flow surveillance data.
7.1.3.1.7DIV shall be capable of importing ITS Environmental data to include:
7.1.3.1.7(a)Emission data.
  
The detailed process and user service requirement traceability information on this page was extracted from the National ITS Architecture. Consult the National ITS Architecture web site for more information.

This page was last updated on 12-11-2000 using Web Spinner Technology.