| 1.0 | TRAVEL AND TRAFFIC MANAGEMENT |
| 1.2 | EN-ROUTE DRIVER INFORMATION |
| 1.2.3 | DI shall provide an In-vehicle Signing capability. |
| 1.2.3.2 | The DI In-vehicle Signing function shall include a long term capability to serve more of the traveler's needs. |
| 1.2.3.2.3 | The In-vehicle Signing function shall provide the capability to utilize data from roadside environmental sensors as inputs to warning messages. |
| 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.2.5.2 | The data process function shall process traffic data to generate near term predictions of traffic conditions. |
| 1.6.3 | TC shall include a Device Control function. |
| 1.6.3.6 | Device Control shall provide the operator the capability to adaptively change system response in order to provide a response that is coordinated with other TMCs responding to incidents. |
| 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.7 | INCIDENT MANAGEMENT |
| 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.8 | TRAVEL DEMAND MANAGEMENT |
| 1.8.0 | ITS 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.1 | TDM shall include a communications function. |
| 1.8.1.1 | The communications function shall include the capability to send the information needed to implement management and control strategies that are in response to policies and regulations. |
| 1.8.1.2 | The communications function shall include the capability to send information and rates needed to implement management and control strategies that respond to changing environments, conditions, and policy needs to include, but not limited to, the following locations of action: |
| 1.8.1.2(a) | Parking facilities. |
| 1.8.1.2(e) | Toll facilities. |
| 1.8.1.2(f) | Travel (and traveler) information facilities. |
| 1.8.1.3 | TDM shall provide the capability to receive information and rates needed to implement management and control strategies that respond to changing environments, conditions, and policy needs to include, but not limited to, the following locations of action: |
| 1.8.1.3(e) | Toll facilities. |
| 1.8.1.3(f) | Travel (and traveler) information facilities. |
| 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.5 | The communications function shall provide the capability to receive information and data from transportation operators and/or users that delineate their: |
| 1.8.1.5(a) | Current status. |
| 1.8.1.5(b) | Needs. |
| 1.8.1.5(c) | Level of activity. |
| 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(d) | Ride Matching and Reservation. |
| 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(a) | Vehicle trip reduction. |
| 1.8.2.1(b) | HOV lanes and ramps. |
| 1.8.2.1(f) | Public awareness of travel alternatives. |
| 1.8.2.2 | The processing function shall provide capabilities to enhance the ability to implement and enforce the following: |
| 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(b) | Inform travelers. |
| 1.8.2.3(c) | Collect fees. |
| 1.8.2.3(d) | Detect traffic. |
| 1.8.2.4 | The processing function shall provide the capability generate guidance for the pricing and control for locations of action that include, but are not limited to, the following: |
| 1.8.2.4(f) | Travel information facilities. |
| 1.8.2.5 | The processing function shall provide the capability to develop strategies for implementation of policies and regulations that will accommodate the following: |
| 1.8.2.5(a) | Public sector users and service providers. |
| 1.8.2.5(b) | Private sector users and service providers. |
| 1.8.2.5(c) | Issues of legality. |
| 1.8.2.5(d) | Privacy act. |
| 1.8.2.5(e) | Multi-jurisdictional settings. |
| 1.8.2.6 | The processing function shall provide the capability to generate management and control strategies that dynamically respond to changing environments, conditions, and policies. |
| 1.8.2.7 | The processing function's dynamically generated management and control strategies shall include the control of HOV facilities including, but not limited to, the following: |
| 1.8.2.7(a) | Lanes. |
| 1.8.2.7(b) | Ramps. |
| 1.8.2.7(c) | Parking areas. |
| 1.8.2.8 | The processing function's generation of management and control strategies for HOV facilities shall include as factors, but not be limited to, the following: |
| 1.8.2.8(a) | Auto occupancy requirements. |
| 1.8.2.9 | The processing function's dynamically generated management and control strategies shall include those roadway pricings that respond to the need for congestion control to include, but not be limited to, the following: |
| 1.8.2.9(a) | Road user and toll rates. |
| 1.8.2.9(b) | Transit fares adjusted concomitant with tolls. |
| 1.8.2.9(c) | Time of day usage pricing (i.e. off hour rates). |
| 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.8.2.11 | The processing function's dynamically generated management and control strategies for parking management and controls shall be based on factors that include, but are not limited to, the following: |
| 1.8.2.12 | The processing function's dynamically generated management and control strategies shall include the capability to respond to the need for control of pollution by generating messages for variable signs that include, but are not limited to, the following: |
| 1.8.2.13 | The 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.2.13(a) | Sensor data. |
| 1.8.2.14 | The processing function's dynamically generated management and control strategies shall include the capability to respond to the need for the travelers to change modes by generating messages for variable signs that include, but are not limited to, the following: |
| 1.8.2.14(a) | Where the mode change requests are being made. |
| 1.8.2.14(b) | How the mode changes are requested to be made. |
| 1.8.2.14(c) | Why the mode changes are requested to be made. |
| 1.8.3 | TDM shall include a sensors/control function. |
| 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. |
| 3.0 | ELECTRONIC PAYMENT |
| 3.1 | ELECTRONIC PAYMENT SERVICES |
| 3.1.0 | ITS shall include an Electronic Payment capability. Electronic Payment Services allows travelers to pay for transportation services by electronic means. Four functions are provided, which are, (1) Electronic Toll Collection, (2) Electronic Fare Collection, (3) Electronic Parking Payment, and (4) Electronic Payment Services Integration. |
| 3.1.5 | ITS shall provide a Roadway Pricing (RP) capability. |
| 3.1.5.1 | RP shall provide the capability to implement various road pricing policies. |
| 3.1.5.1.1 | Road pricing policies capable of being implemented by RP shall include variable pricing. |
| 3.1.5.2 | RP shall provide the capability to implement roadway pricing strategies, developed by other services, that alleviate congestion. |
| 3.1.5.3 | RP shall provide the capability to implement roadway pricing, developed by other services, that can be used to influence mode selection. |
| 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.9 | DIV shall be capable of importing data on ITS Physical Characteristics of Transportation Infrastructure to include: |
| 7.1.3.1.9(a) | Roadway network attributes. |
| 7.1.3.1.9(d) | Transportation facilities. |
| | |
