AVSS11-Automated Vehicle Operations (Service Package*)

Description

This service package enables "hands-off" operation of the vehicle on automated portions of the highway system. Implementation requires lateral lane holding, vehicle speed and steering control. Communications between vehicles and between the vehicles and supporting infrastructure equipment supports cooperative check-in to the automated portion of the system and transition to automated mode, coordination of maneuvers between vehicles in automated mode, and checkout from the automated system as the driver resumes control of the vehicle.

Service Package Graphic

TMC Automated Vehicle OperationsRoadway Automated Vehicle OperationsVehicle Automated OperationsTraffic ManagementRoadwayVehicleOther VehicleDriverBasic VehicleRoadway EnvironmentPotential Obstaclesautomated roadway control dataautomated roadway statusautomated vehicle statusautomated vehicle control datavehicle control coordinationdriver updatesbasic vehicle measuresroadway characteristicsdriver inputsvehicle controlphysical presence

Get the Source Graphic, a Windows Metafile (WMF), in ZIP format.
About this Graphic

Includes Architecture Flows:

Source Architecture Flow Destination In Graphic
Basic Vehicle basic vehicle measures Vehicle Yes
Driver driver inputs Vehicle Yes
Other Vehicle vehicle control coordination Vehicle Yes
Potential Obstacles physical presence Vehicle Yes
Roadway automated roadway status Traffic Management Yes
Roadway automated vehicle control data Vehicle Yes
Roadway Environment roadway characteristics Vehicle Yes
Traffic Management automated roadway control data Roadway Yes
Vehicle vehicle control Basic Vehicle Yes
Vehicle driver updates Driver Yes
Vehicle vehicle control coordination Other Vehicle Yes
Vehicle automated vehicle status Roadway Yes
    - This icon indicates that the associated architecture flow either has been or will be addressed by ITS Standards. Select the architecture flow for more information on relevant standards activities.

Associated Planning Factors and Goals

Planning Factor Goal
A. Support the economic vitality of the metropolitan area, especially by enabling global competitiveness, productivity, and efficiency; Support regional economic productivity and development
E. Protect and enhance the environment, promote energy conservation, improve the quality of life, and promote consistency between transportation improvements and State and local planned growth and economic development patterns; Reduce environmental impacts
G. Promote efficient system management and operation; Increase operational efficiency and reliability of the transportation system

Associated Objective Categories

Objective Category
System Efficiency: Cost of Congestion
System Efficiency: Delay
System Efficiency: Duration of Congestion
System Efficiency: Energy Consumption
System Efficiency: Extent of Congestion
System Efficiency: Intensity of Congestion (Travel Time Index)
System Efficiency: Travel Time

Associated Objectives and Performance Measures

Objective Performance Measure
Annual rate of change in regional average commute travel time will not exceed regional rate of population growth through the year Y. Average commute trip travel time (minutes).
Improve average travel time during peak periods by X percent by year Y. Average travel time during peak periods (minutes).
Maintain the rate of growth in facility miles experiencing recurring congestion as less than the population growth rate (or employment growth rate). Percent of lane-miles (or rail) operating at LOS F or V/C > 1.0
Reduce excess fuel consumed due to congestion by X percent by year Y. Excess fuel consumed (total or per capita).
Reduce hours of delay per capita by X percent by year Y. Hours of delay (person-hours).
Reduce hours of delay per capita by X percent by year Y. Hours of delay per capita.
Reduce hours of delay per driver by X percent by year Y. Hours of delay (person-hours).
Reduce hours of delay per driver by X percent by year Y. Hours of delay per driver.
Reduce the annual monetary cost of congestion per capita for the next X years. Cost (in dollars) of congestion or delay per capita.
Reduce the daily hours of recurring congestion on major freeways from X to Y by year Z. Hours per day at LOS F or V/C > 1.0 (or other threshold).
Reduce the number of hours per day that the top 20 most congested roadways experience recurring congestion by X percent by year Y. Hours per day at LOS F or V/C > 1.0 (or other threshold).
Reduce the percentage of facility miles (highway, arterial, rail, etc.) experiencing recurring congestion during the peak period by X percent by year Y. Percent of lane-miles (or rail) operating at LOS F or V/C > 1.0
Reduce the regional average travel time index by X percent per year. Travel time index (the average travel time during the peak period, using congested speeds, divided by the off-peak period travel time, using posted or free-flow speeds).
Reduce the share of major intersections operating at LOS Z by X percent by year Y. Percent of intersections operating at LOS F or V/C > 1.0
Reduce total energy consumption per capita for transportation by X percent by year Y. Total energy consumed per capita for transportation.
Reduce total fuel consumption per capita for transportation by X percent by year Y. Total fuel consumed per capita for transportation.

 
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Related ITS Applications of ITS Taxonomy

Classification Category ITS Application Area ITS Application(s)
Intelligent Vehicles Driver Assistance Intelligent Speed Control

User Services related to this Service Package:

User Service
6.7 Automated Vehicle Operation

Transaction Set Diagram





The source graphic, a Windows Metafile (WMF), for the TSD can be downloaded here: TSD

The following discusses how the National ITS Architecture provides the transportation service described by this service package. Each numbered item describes the operation of that portion of the service package identified with the corresponding number on the transaction set diagram.

  1. The Roadway subsystem provides automated roadway status information to the Traffic Management subsystem, and the Traffic Management subsystem provides automated roadway control data to the Roadway subsystem, allowing the center to monitor and provide strategic control of the automated system.

  2. The Vehicle subsystem collects control inputs from the Driver (driver inputs), and non-ITS system status measures from the Basic Vehicle (basic vehicle measures)

  3. The Vehicle subsystem collects information from sensed physical presence of obstacles and roadway characteristics (e.g. lane markers, exit markers, AHS entry/exit location markers).

  4. The Vehicle subsystem exchanges control and status information directly with Other Vehicles in the vicinity (vehicle control coordination). For example, the lead vehicle in a platoon of vehicles may send its predicted acceleration profile to the vehicle just behind, and that vehicle will send the acceleration profile to the vehicle behind it. In this way, very small and precise headway control is possible while minimizing the power requirements on the individual vehicles that might otherwise be necessary if the headway holding was based entirely on distance sensors.

  5. The Roadway sends automated vehicle control data to the individual vehicles. This would include operating parameters such as maximum speed and information about when and where to merge into or depart the automated portion of the system.

  6. The Vehicle subsystem can send (vehicle control) information to the basic vehicle (e.g. steering, braking, and throttle position).

  7. The Driver receives (driver updates) about the automated system, vehicle operational status, and vehicle condition.

  8. The vehicle can notify the roadway about its operational status and condition (automated vehicle status).