|
Roadway Data Collection Equipment Package
|
|
Description:
|
Field elements to collect traffic, road, and environmental conditions information for use in transportation planning, research, and other off-line applications. Includes the sensors, supporting roadside infrastructure, and communications equipment.
|
Included in:
|
City of Victoria ITS Field Equipment
City of Victoria MPO Field Devices
|
Functional Requirements:
|
1 | The field element shall collect traffic, road, and environmental conditions information. |
2 | The field element shall include the sensors and supporting roadside devices that sense, collect, and send traffic, road, and environmental conditions information to a center for archival. |
3 | The field element shall collect sensor status and sensor faults from roadside equipment and send it along with the recorded data to a center for archival. |
| |
|
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.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. |
7.1.3.1.9 | DIV shall be capable of importing data on ITS Physical Characteristics of Transportation Infrastructure to include: |
7.1.3.1.9(c) | Equipment maintenance status |
| |
|
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.
|
|