Regional Architecture Logo
 

Send Your Comments

E-Mail

Logo

Regional Architecture Banner Architecture Geographic Scope

Collect Traffic Surveillance Equipment Package

Description:

This Equipment package collects, stores, and provides electronic access to the traffic surveillance data.

 

Included in:

County, Municipal and Tribal Traffic Operations and Communications Center
SDDOT Mobile Traffic Management Center
SDDOT Office of Operations
SDDOT Region and Area Construction and Maintenance Office
SDDOT Road and Weather Information System

Processes:

1.1.2.1Process Traffic Data for Storage
1.1.2.2Process Traffic Data
1.1.2.3Update Data Source Static Data
1.1.4.1Retrieve Traffic Data
1.1.4.2Provide Traffic Operations Personnel Traffic Data Interface
1.1.4.4Update Traffic Display Map Data
  

User Service Requirements (fully or partially addressed):

1.0TRAVEL AND TRAFFIC MANAGEMENT
1.6TRAFFIC CONTROL
1.6.0ITS shall include a Traffic Control (TC) function. Traffic Control provides the capability to efficiently manage the movement of traffic on streets and highways. Four functions are provided, which are, (1) Traffic Flow Optimization, (2) Traffic Surveillance, (3) Control, and (4) Provide Information. This will also include control of network signal systems with eventual integration of freeway control.
1.6.1TC shall include a Traffic Flow Optimization function to provide the capability to optimize traffic flow.
1.6.1.7Implementation of the Control function shall include strategies that account for at least the following:
1.6.1.7(a)Human factors.
1.6.2TC shall include a Traffic Surveillance function.
1.6.2.2Traffic Surveillance shall include a data collect function to provide the capability to collect data for determining traffic flow and prediction.
1.6.2.2.1The data collect function shall provide the capability to quickly feedback traffic data to the control processes.
1.6.2.3Traffic Surveillance shall include a wide-area surveillance capability to include several jurisdictions.
1.6.2.3.2The wide-area surveillance shall cover a large number of roadway segments.
1.6.2.4TC shall provide the capability to acquire detailed traffic measurements at specific locations.
1.6.2.4.1Traffic Surveillance shall include a data process function to process the traffic data which are acquired.
1.6.2.5The wide area surveillance shall acquire sufficient data to provide the system with the knowledge of the existing conditions.
1.6.2.5.1The data process function shall combine and process traffic data from multiple sources and times in order to improve the accuracy of the view of the current traffic condition.
1.6.3TC shall include a Device Control function.
1.6.3.4Device Control shall communicate control data to the following devices.
1.6.3.4(e)Human operator support.
1.6.3.4.1Traffic Surveillance shall include a data process function to process the traffic data which are acquired.
1.6.4Device Control shall provide traffic control information to other elements of the ITS, including but not limited to the following:
1.6.4(a)In-vehicle navigation.
1.6.4(b)Trip planning.
1.6.4(c)Routing systems.
1.6.4(d)Fleet management systems.
1.7INCIDENT MANAGEMENT
1.7.1Incident Management shall provide an Incident Identification function to identify incidents.
1.7.1.1The Incident Identification function shall include the capability to identify predicted incidents.
1.7.1.1.1The Incident Identification function shall use information from the following types of sources, where available, to identify predicted incidents:
1.7.1.1.1(a)Traffic flow sensors.
1.7.1.1.1(b)Environmental sensors.
1.8TRAVEL DEMAND MANAGEMENT
1.8.1TDM shall include a communications function.
1.8.1.4The communications function shall provide the capability to send information and data as needed to implement management and control strategies that respond to changing environments, conditions, and policy needs to include, but not limited to, the following:
1.8.1.4(a)Sensor data.
1.8.1.6The communications function shall include the capability for two-way communications with other ITS user services including, but not limited to, the following:
1.8.1.6(f)Traffic Control.
1.8.2TDM shall include a processing function.
1.8.2.1The processing function shall provide the capability to generate management and control strategies that facilitate the implementation of policies and regulations designed to address the following:
1.8.2.1(b)HOV lanes and ramps.
1.8.2.3Strategies developed by the processing function shall include the guidance for the operation of physical systems that:
1.8.2.3(a)Monitor traffic.
1.8.2.3(d)Detect traffic.
1.8.2.10The processing function's dynamically generated management and control strategies shall include the parking management and controls to include, but not be limited to, the following:
1.8.2.10(c)Variable message signs.
1.10HIGHWAY RAIL INTERSECTION
1.10.0ITS shall include a Highway-Rail Intersection (HRI) function to control highway and rail traffic in at-grade HRIs. Two sub-services are supported: Standard Speed Rail Subservice which is applicable to light rail transit, commuter rail and heavy rail trains with operational speeds up to 79 miles per hour (MPH); and High Speed Rail Subservice which is applicable to all passenger and freight trains with operational speeds from 80 to 125 MPH.
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.3.1DIV shall be capable of importing selected ITS Operational data from the ITS Operational Repositories.
7.1.3.1.9DIV shall be capable of importing data on ITS Physical Characteristics of Transportation Infrastructure to include:
7.1.3.1.9(e)GIS map of network.
8.0MAINTENANCE AND CONSTRUCTION MANAGEMENT
8.1MAINTENANCE AND CONSTRUCTION OPERATIONS
8.1.1Maintenance and Construction Operations shall provide a Maintenance Vehicle Fleet Management (MVFM) function to schedule and dispatch, monitor and track location, and monitor operational condition and maintenance requirements of public and contracted fleets of maintenance, construction, and specialized service vehicles. This function includes interactions among Traffic Managers, Supervisors, Dispatchers, Field Crews, Construction Crews, Vehicle Maintenance Crews, Equipment Maintenance Crews, Weather Services Organizations, and Information Service Providers.
8.1.1.6MVFM shall be capable of providing dispatchers and operators of maintenance, construction, and specialized service vehicles with information regarding potential and actual roadway problems.
8.1.1.6.1MVFM shall provide information to dispatchers and vehicle operators, including but not limited to:
8.1.1.6.1(a)Congestion
8.1.1.6.1(b)Incidents
  
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 Update: 02-23-2003