Send Your Comments

Traffic and Roadside Data Archival Equipment Package

Description:

Collects and archives traffic and environmental information directly from the roadside for use in off-line planning, research, and analysis.

Included in:

City of Victoria Crash Records Database
City of Victoria MPO Archive
City of Victoria Pavement Management System
City of Victoria Sign Inventory Database
City of Victoria Traffic Database
Golden Crescent Regional Planning Commission ITS Database
Municipal/County Crash Records Database
Statewide Crash Records Information System
TexMAP Archive Database
TexTAP Archive Database
TxDOT Public Transportation Division (Austin)
TxDOT Statewide Pavement Management System
TxDOT Statewide Roadway Data Collection System
TxDOT Yoakum District Pavement Management System
TxDOT Yoakum District Public Transportation Management System (PTMS)
TxDOT Yoakum District Roadway Data Collection System

Functional Requirements:

1	The center shall manage the collection of archive data directly from collection equipment located at the roadside.
2	The center shall collect traffic sensor information from roadside devices.
3	The center shall collect environmental sensor information that from roadside devices.
4	The center shall respond to requests from the Archive Data Administer to input the parameters that control the collection process.
5	The center shall send the request for data and control parameters to the field equipment where the information is collected and returned.
6	The center shall record the status about the imported traffic and roadside data.
7	The center shall use the status information to adjust the collection of traffic and roadside data.

User Service Requirements (fully or partially addressed):

7.0	INFORMATION MANAGEMENT
7.1	ARCHIVED DATA FUNCTION
7.1.0	ITS 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.2	The 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.1	ODC shall be capable of receiving and storing all ITS operational data, as received from the source.
7.1.2.1.1	ODC shall ensure ITS operational data are in proper format.
7.1.2.1.2	ODC shall maintain the meta data schema for all ITS data entering the system.
7.1.2.1.3	ODC 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.3	The 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.1	DIV shall be capable of importing selected ITS Operational data from the ITS Operational Repositories.
7.1.3.1.1	DIV 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.3	DIV 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.7	DIV 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.

Last updated on 05-27-2005 using Ronald C. Ice and Associates Web Spinner Technology.