ATMS09-Traffic Decision Support and Demand Management Transaction Set Diagram



Get the Source Graphic, a Windows Metafile (WMF), in ZIP format.
More about ZIP files

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.

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 above TSD.

ATMS09 transaction set diagrams: 1 2 Next TSD

  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 (traffic information coordination) 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) 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 Toll 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.