ATMS09-Transportation Decision Support and Demand Management (Service Package*)

Description

This service package recommends courses of action to traffic operations personnel based on an assessment of current and forecast road network performance. Recommendations may include predefined incident response plans and regional surface street and freeway control strategies that correct network imbalances. Where applicable, this service package also recommends transit, parking, and toll strategies to influence traveler route and mode choices to support travel demand management (TDM) programs and policies managing both traffic and the environment. TDM recommendations are coordinated with transit, parking, and toll administration centers to support regional implementation of TDM strategies. Incident response and congestion management recommendations are implemented by the local traffic management center and coordinated with other regional centers by other service packages (see ATMS07-Regional Traffic Management and ATMS08-Traffic Incident Management). All recommendations are based on historical evaluation, real-time assessment, and forecast of the roadway network performance based on predicted travel demand patterns. Traffic data is collected from sensors and surveillance equipment as well as other transportation management centers (see ATIS06-Transportation Operations Data Sharing). Forecasted traffic loads are derived from historical data and route plans supplied by the Information Service Provider Subsystem. This service package also collects air quality, parking availability, transit usage, and vehicle occupancy data to support TDM, where applicable.

Service Package Graphic

Transit Center Multi-Modal CoordinationTMC Demand Management CoordinationTMC Traffic Network Performance EvaluationTMC Traffic Management Decision SupportParking ManagementTraffic ManagementTraffic Operations PersonnelInformation Service ProviderPayment AdministrationTransit ManagementRoadwayEvent PromotersMap Update ProviderOther Traffic Managementparking demand management responsetraffic operator datatraffic operator inputsparking informationtraffic flowparking demand management requestroad network conditionsfare and price informationlogged vehicle routestoll service change requesttoll service change responsetransit demand management requesttransit system datatransit demand management responseevent plansmap updatesparking lot inputsmap update requesttraffic sensor controlrequest transit informationparking lot data requesttraffic imagesroad network conditions

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

Includes Architecture Flows:

Source Architecture Flow Destination In Graphic
Archived Data Management archived data products Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management No
Emissions Management widearea statistical pollution information Traffic Management No
Event Promoters event plans Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Information Service Provider fare and price information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Information Service Provider logged vehicle routes Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Map Update Provider map updates Traffic Management Yes
Other Traffic Management road network conditions Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Parking Management parking demand management response Traffic Management Yes
Parking Management parking information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Payment Administration toll service change response Traffic Management Yes
Roadway traffic flow Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Traffic Management archived data product requests Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Archived Data Management No
Traffic Management pollution state data request Emissions Management No
Traffic Management road network conditions Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Information Service Provider Yes
Traffic Management traffic images Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Information Service Provider Yes
Traffic Management map update request Map Update Provider Yes
Traffic Management road network conditions Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Other Traffic Management Yes
Traffic Management parking demand management request Parking Management Yes
Traffic Management parking lot data request Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Parking Management Yes
Traffic Management parking lot inputs Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Parking Management Yes
Traffic Management toll service change request Payment Administration Yes
Traffic Management traffic sensor control Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Roadway Yes
Traffic Management traffic operator data Traffic Operations Personnel Yes
Traffic Management request transit information Transit Management Yes
Traffic Management transit demand management request Transit Management Yes
Traffic Operations Personnel traffic operator inputs Traffic Management Yes
Transit Management transit demand management response Traffic Management Yes
Transit Management transit system data Traffic Management 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
D. Increase the accessibility and mobility of people and for freight; Enhance mobility, convenience, and comfort for transportation system users
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
Special Event Management: Entry/Exit Travel Times
Special Event Management: Mode Shift from SOV
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
System Efficiency: Vehicle Miles Traveled
System Options: Mode Share
System Options: Transit Use
System Reliability: Non-Recurring Delay
Travel Demand Management: Auto Commuter Trip Reduction Programs
Travel Demand Management: Parking Management

Associated Objectives and Performance Measures

Objective Performance Measure
Achieve X percent alternative (non-SOV) mode share in transit station communities (or other destinations) by year Y. Percent of all trips made using alternative modes in transit station communities.
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).
Biannually increase preferred parking spaces for carpool/vanpool participants within downtown, at special events, and among major employers by X percent within Y years. Number of preferred parking spaces for carpool/vanpool participants.
Decrease the percent of special event attendees traveling to the event in single-occupancy vehicles by X percent in Y years. Percent of special event attendees using single-occupancy vehicles each year for selected events.
Implement parking pricing for X communities every Y years. Number of communities with priced parking stalls.
Implement shared parking for X communities every Y years. Number of communities with shared parking.
Improve average travel time during peak periods by X percent by year Y. Average travel time during peak periods (minutes).
Increase active (bicycle/pedestrian) mode share by X percent by year Y. Share of trips by each mode of travel.
Increase alternative (non-SOV) mode share for all trips by X percent within the next Y years. Share of trips by each mode of travel.
Increase average transit load factor by X percent by year Y. Number of riders on various transit units per trip at peak travel times.
Increase park-and-ride lot capacity by X percent over Y years. Capacity of park & ride lots.
Increase passenger miles traveled per capita on transit by X percent by year Y. Number of passenger miles traveled per capita.
Increase the number of residents/commuters receiving information on parking pricing and availability within Y years. Number of residents/commuters receiving information on parking pricing and availability.
Increase the percent of special event attendees using park & ride lots by X percent in Y years. Percent of special event attendees utilizing park & ride lots each year for selected events.
Increase the percent of special events with dedicated shuttle service by X percent in Y years. Percent of special events with dedicated shuttle service for selected events during a 1-year period.
Increase transit mode share by X percent by year Y during peak periods. Percent of all peak-period trips made by transit.
Increase transit mode share by X percent by year Y. Percent of all trips made by transit.
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 commuter vehicle miles traveled (VMT) per regional job by X percent in Y years. Commuter VMT per regional employee.
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 non-special event VMT in the event area during events by X percent in Y years. Non-special event VMT in the event area during events over a year.
Reduce per capita SOV commute trip rate by X percent in Y years. SOV commute trips per capita.
Reduce SOV vehicle trips by X percent through travel demand management strategies (e.g., employer or residential rideshare) by year Y. Share of employees walking, biking, telecommuting, carpooling/vanpooling, riding transit, driving alone.
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.
Reduce total person hours of delay (or travel-time delay per capita) by time period (peak, off-peak) caused by all transient events such as traffic incidents, special events, and work zones. Total person hours of delay during scheduled and/or unscheduled disruptions to travel.
Reduce total person hours of delay (or travel-time delay per capita) by time period (peak, off-peak) caused by scheduled events, work zones, or system maintenance by x hours in y years. Travel time delay during scheduled and/or unscheduled disruptions to travel.
Reduce total person hours of delay (or travel-time delay per capita) by time period (peak, off-peak) caused by unscheduled disruptions to travel. Total person hours of delay during scheduled and/or unscheduled disruptions to travel.
Reduce vehicle miles traveled per capita by X percent by year Y. Average VMT per capita per day, per week, or per year.


 
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 Infrastructure Transit Management Transportation Demand Management

User Services related to this Service Package:

User Service
1.6 Traffic Control
1.8 Travel Demand Management

Transaction Set Diagram

Note that this transaction set diagram (TSD) is only 1 of the 2 TSDs and so only a portion of the numbered items below refer to the TSD.
ATMS09 transaction set diagrams: Part 1, Part 2,



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

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. Data collected by the Traffic Management Subsystem can be associated with links and nodes of the transportation network. An interface to a Map Update Provider is available to keep this model of the transportation network current (map updates). The update can be requested (map update request) when one is desired. Otherwise, the Map Update Provider could provide an update on a set schedule or as revisions warrant it.

  2. To forecast traffic and develop demand management strategies, data on current and historic traffic flow and expected events are needed. Event promoters can notify Traffic Management Subsystem of planned events (event plans.) To obtain information on the flow of traffic such as volume and speed, the Traffic Management Subsystem can control (traffic sensor control) and monitor (traffic flow) sensors in or along the roadway. Traffic information (road network conditions) can also be obtained from Other Traffic Managements in the region.

  3. A data archive, either a focused archive owned by the agency or a regional data warehouse, may be mined for historical information to support traffic forecast and demand management. Historical traffic data (archived data products) are obtained from the Archived Data Management Subsystem on request (archived data product requests).

  4. Information on current values of transit fares, tolls and parking fees (fare and price information) can be obtained from an Information Service Provider (ISP).

  5. Information on current or projected air quality for the region (widearea statistical pollution information) can be obtained from an Emissions Management Subsystem. This information can be requested (pollution state data request) when desired. Otherwise, it can be provided on a set schedule or as revisions warrant it.

  6. The Traffic Management Subsystem can share the current and/or expected use of the road network (road network conditions and traffic images) with an ISP. The information can be requested when desired or it can be provided on a set schedule or when conditions warrant an update. The ISP can provide its view of the network provided by collected probe information (logged vehicle routes).

  7. The entire process is under the asynchronous monitoring (traffic operator data) and control (traffic operator inputs) of Traffic Operations Personnel.

  8. Traffic Management Subsystem receives the current or expected parking availability, fares, etc. (parking information) from Parking Management Subsystem. This information can be requested (parking lot data request) when desired. Otherwise, it can be provided on a set schedule or as revisions warrant it. Based on the availability of parking, traffic conditions and other factors, a regional traffic management plan can be developed. To implement the plan, parking instructions (parking lot inputs) are sent to the Parking Management Subsystem.

  9. To assist in travel demand management, the Traffic Management Subsystem may request (parking demand management request) a change in parking prices or procedures. The Parking Management Subsystem may send a response (parking demand management response) to indicate when the request was or will be honored.

  10. To assist in travel demand management, the Traffic Management Subsystem may request (toll service change request) a change in toll prices or procedures. The Payment Administration Subsystem may send a response (toll service change response) to indicate when the request was or will be honored.

  11. Traffic Management Subsystem receives the current transit system operations information indicating current transit routes, the level of service on each route, and the progress of individual vehicles along their routes (transit system data) from Transit Management Subsystem. This information can be requested (request transit information) when desired. Otherwise, it can be provided on a set schedule or as revisions warrant it.

  12. To assist in travel demand management, the Traffic Management Subsystem may request (transit demand management request) a change in transit prices or procedures. The Transit Management Subsystem may send a response (transit demand management response) informing when the request was or will be honored.