| 1.0 | TRAVEL AND TRAFFIC MANAGEMENT |
| 1.6 | TRAFFIC CONTROL |
| 1.6.0 | ITS 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.2 | TC shall include a Traffic Surveillance function. |
| 1.6.2.2 | Traffic Surveillance shall include a data collect function to provide the capability to collect data for determining traffic flow and prediction. |
| 1.6.2.2.1 | The data collect function shall provide the capability to quickly feedback traffic data to the control processes. |
| 1.6.2.3 | Traffic Surveillance shall include a wide-area surveillance capability to include several jurisdictions. |
| 1.6.2.3.2 | The wide-area surveillance shall cover a large number of roadway segments. |
| 1.6.2.4 | TC shall provide the capability to acquire detailed traffic measurements at specific locations. |
| 1.6.2.4.1 | Traffic Surveillance shall include a data process function to process the traffic data which are acquired. |
| 1.6.2.5 | The wide area surveillance shall acquire sufficient data to provide the system with the knowledge of the existing conditions. |
| 1.6.2.5.1 | The 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.3 | TC shall include a Device Control function. |
| 1.6.3.4 | Device Control shall communicate control data to the following devices. |
| 1.6.3.4.1 | Traffic Surveillance shall include a data process function to process the traffic data which are acquired. |
| 1.6.4 | Device 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.7 | INCIDENT MANAGEMENT |
| 1.7.0 | ITS 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.1 | Incident Management shall provide an Incident Identification function to identify incidents. |
| 1.7.1.1 | The Incident Identification function shall include the capability to identify predicted incidents. |
| 1.7.1.1.1 | The 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.7.1.1.1(c) | Public safety sources. |
| 1.7.1.1.1(d) | Media sources. |
| 1.7.1.1.1(e) | Weather information sources. |
| 1.7.1.1.1(f) | Transportation providers. |
| 1.7.1.1.1(g) | Sponsors of special events. |
| 1.7.1.1.1(h) | Hazardous condition prediction algorithms. |
| 1.7.1.1.2 | The Incident Identification function shall determine at least the following characteristics of each predicted incident: |
| 1.7.1.1.2(a) | Type (including Terrain Hazards). |
| 1.7.1.1.2(b) | Extent. |
| 1.7.1.1.2(c) | Severity. |
| 1.7.1.1.2(d) | Location. |
| 1.7.1.1.2(e) | Expected duration. |
| 1.7.1.1.3 | The Incident Identification function shall determine the expected traffic flow impact of each predicted incident. |
| 1.7.1.2 | The Incident Identification function shall include the capability to identify existing (both planned and unplanned) incidents. |
| 1.7.1.2.1 | The Incident Identification function shall use information from the following types of sources, where available, to identify existing incidents: |
| 1.7.1.2.1(a) | Traffic flow sensors. |
| 1.7.1.2.1(b) | Environmental sensors. |
| 1.7.1.2.1(c) | Public safety sources. |
| 1.7.1.2.1(d) | Media sources. |
| 1.7.1.2.1(e) | Weather information sources. |
| 1.7.1.2.1(f) | Transportation providers. |
| 1.7.1.2.1(g) | Travelers. |
| 1.7.1.2.2 | The Incident Identification function shall determine and continuously monitor at least the following characteristics of each existing incident: |
| 1.7.1.2.2(a) | Type (including Terrain Hazards). |
| 1.7.1.2.2(b) | Extent. |
| 1.7.1.2.2(c) | Severity. |
| 1.7.1.2.2(e) | Expected duration. |
| 1.7.1.2.3 | The Incident Identification function shall determine and continuously monitor the current and expected traffic flow impact of each existing incident. |
| 1.7.2 | IM shall provide a Response Formulation function to formulate appropriate response actions to each identified incident and revise those actions when necessary. |
| 1.7.2.1 | The Response Formulation function shall propose and facilitate the appropriate scheduling of those predicted incidents that can be scheduled to minimize incident potential, incident impacts, and/or the resources required for incident management. |
| 1.7.3 | IM shall include a Response Implementation function to provide the services to implement a response coordinated with all appropriate agencies. |
| 1.7.3.1 | The Response Implementation function shall provide at least the following decision support capabilities needed to implement coordinated incident response actions by all participating institutions: |
| 1.7.3.1(b) | Response Implementation shall provide the status of all resources needed for incident resolution to those agencies responding to the incident. |
| 1.7.3.2 | The Response Implementation function shall provide a link between Incident Management and all other user services necessary to implement incident response actions. |
| 1.7.4 | IM shall provide the capability to Predict Hazardous Conditions, including the time and location of hazardous conditions that may cause an incident. |
| 1.8 | TRAVEL DEMAND MANAGEMENT |
| 1.8.1 | TDM shall include a communications function. |
| 1.8.1.4 | The 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.6 | The 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.2 | TDM shall include a processing function. |
| 1.8.2.1 | The 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.3 | Strategies 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.10 | The 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.10 | HIGHWAY RAIL INTERSECTION |
| 1.10.0 | ITS 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. |
| 8.0 | MAINTENANCE AND CONSTRUCTION MANAGEMENT |
| 8.1 | MAINTENANCE AND CONSTRUCTION OPERATIONS |
| 8.1.0 | ITS shall provide Maintenance and Construction Operations (MCO) functions to support monitoring, operating, maintaining, improving and managing the physical condition of roadways, the associated infrastructure equipment, and the required resources. MCO shall focus on four major functions: 1) the Maintenance Vehicle Fleet Management function, to monitor and track locations and conditions of fleets of maintenance, construction, and specialized service vehicles; 2) the Roadway Management function, to monitor and forecast conditions and manage treatment of roadways during various travel conditions; 3) the Work Zone Management and Safety function, to support effective and efficient roadway operations during work zone activities; and 4) the Roadway Maintenance Conditions and Work Plan Dissemination function, to coordinate work plans and to communicate conditions. This User Service will utilize ITS systems and processes to support interchange of information among diverse groups of users, to improve efficiency and effectiveness of operational, maintenance, and managerial activities. |
| 8.1.1 | Maintenance 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.6 | MVFM 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.1 | MVFM 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 |
| 8.1.2 | Maintenance 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.1 | RWM shall support a number of different services, including but not limited to: |
| 8.1.2.1(c) | Emergency activities (incident response, planning, alternate routing, etc.) |
| 8.1.4 | Maintenance and Construction Operations shall provide a Roadway Maintenance Conditions and Work Plan Dissemination (RMCWPD) function to provide Intra- and Inter-agency coordination of work plans. This function includes interactions among Traffic Managers, Supervisors, Planning Agencies, Public Safety Organizations, and Information Service Providers. |
| 8.1.4.1 | RMCWPD shall coordinate information on planned maintenance and construction activities, including work zone information, and unplanned remediation activities, such as inclement weather responses, so that routing, scheduling, and resource allocation can be accomplished. |
| 8.1.4.2 | RMCWP shall support inter-agency coordination of response and scheduling of resources for significant events with broad impact, like natural disasters, major incidents, and large planned or seasonal events. |
| 8.1.4.3 | RMCWPD shall coordinate information with other transportation agencies, including but not limited to: |
| 8.1.4.3(a) | Public Safety |
| 8.1.4.3(b) | Emergency Medical Management |
| 8.1.4.3(d) | Traffic Management |
| | |
Web Spinner Technology.