Regional Architecture Logo
 

Send Your Comments

E-Mail

Traffic Maintenance Equipment Package

Architecture Geographic Scope

Description:

Monitoring and remote diagnostics of field equipment - detect failures, issue problem reports, and track the repair or replacement of the failed equipment.

 

Included in:

City of Sherman Traffic Operations Center
Municipal TOCs
TxDOT Paris District TMC

Functional Requirements:

1The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) operational status.
2The center shall collect and store CCTV surveillance system (traffic, pedestrian) operational status.
3The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) fault data and send to the maintenance center for repair.
4The center shall collect and store CCTV surveillance system (traffic, pedestrian) fault data send to the maintenance center for repair.
5The center shall collect environmental sensor operational status.
6The center shall collect environmental sensor equipment fault data and send to the maintenance center for repair.
7The center shall exchange data with maintenance centers concerning the reporting of faulty equipment and the schedule/status of their repair. Information exchanged includes details of new equipment faults, and clearances when the faults are cleared.
8The center shall support an interface with a map update provider, or other appropriate data sources, through which updates of digitized map data can be obtained and used as a background for traffic maintenance 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.3TC shall include a Device Control function.
1.6.3.4(e)Human operator support.
1.7INCIDENT MANAGEMENT
1.7.0ITS shall include an Incident Management (IM) function. Incident Management will identify incidents, formulate response actions, and support initiation and ongoing coordination of those response actions. Four major functions are provided, which are, (1) Incidents Identification, (2) Response Formulation, (3) Response Implementation, and (4) Predict Hazardous Conditions.
1.7.4IM shall provide the capability to Predict Hazardous Conditions, including the time and location of hazardous conditions that may cause an incident.
1.8TRAVEL DEMAND MANAGEMENT
1.8.0ITS shall include a Travel Demand Management (TDM) function. Travel Demand Management will generate and communicate management and control strategies that will support and facilitate the implementation of TDM programs, policies and regulations. It consists of two major functions, which are, (1) Increase Efficiency of Transportation System and (2) Provide Wide Variety of Mobility Options.
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.5The communications function shall provide the capability to receive information and data from transportation operators and/or users that delineate their:
1.8.2TDM shall include a processing function.
1.8.2.13The processing function's dynamically generated management and control strategies for air pollution control shall be based on factors that include, but are not limited to, the following:
1.8.3TDM shall include a sensors/control function.
1.8.3.1The sensors/control function shall provide the capability to gather information needed for the generation of management and control strategies to include, but not be limited to the, following:
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.2Maintenance and Construction Operations shall provide a Roadway Management (RWM) function to monitor traffic, road surface, and environmental conditions and forecast traffic and road surface conditions to support management of routine and hazardous road condition remediation and to communicate changes in conditions. This function includes interactions among Traffic Managers, Supervisors, Dispatchers, Field Crews, Construction Crews, Asset Managers, Planning Agencies, and Weather Services Organizations.
8.1.2.1RWM shall support a number of different services, including but not limited to:
8.1.2.1(e)Repair activities
  
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-12-2005 using Ronald C. Ice and Associates Web Spinner Technology.