6.7.3 - Provide Traveler Services in Vehicle DFD

This DFD shows the processes that make up the Provide Traveler Services in Vehicle facility within the Provide Driver Personal Services function. These processes enable the driver to obtain traveler information and to plan trips from their vehicle.

The key points about the facility are as follows:

Drivers can plan trips and obtain traffic, transit, events, and yellow pages services information;
Trips may be multimodal, including such things as demand responsive transit and ridesharing;
Planned trips may be confirmed and paid for in advance as may yellow pages services;
Drivers may also obtain traffic and transit information without planning any trips or making reservations;
Provides “kiosk” type facilities for travelers using in-vehicle devices;
Provides traveler information to vehicles using short range communications field equipment.

There are five processes in this DFD:
a) Get Driver Personal Request (6.7.3.1)
b) Provide Driver with Personal Traveler Information (6.7.3.2)
c) Provide Driver Information Interface (6.7.3.3)
d) Update Driver Display Map Data (6.7.3.4)
e) Provide Short Range Traveler Information (6.7.3.5)

The driver provides trip planning, trip confirmation, plus traveler information requests through process (c). These are sent to process (a), which distributes the trip planning and confirmation requests to the appropriate processes in the Provide Trip Planning Services facility - see DFD 6.1. Requests for traveler information are sent for implementation by process (b) which also receives the results from the trip planning requests made by process (a). All data received by process (b) is sent to process (c) for output to the driver. Drivers can request as many trip plans as are needed before an acceptable match is found to their trip requirements. Data used for previous inputs and regularly used data is kept in the store of vehicle_regular_data by process (c). The outputs produced by process (c) may be shown against a background of digitized map data produced by process (d). This process will also update the store of map data on request from the driver through process (c), and successful completion of payment through the Collect Advanced Payments facility - see DFD 7.4.1. All data received by process (e) will be sent to process (b) which in turn will send it on to process (c).

These processes form a tightly coupled group and communicate with many other ITS functions. They can only be implemented as a group, except that process (d) may be omitted if digitized map data is not to be used as the background for data output.

DFD: 6.7.3 - Provide Traveler Services in Vehicle

Parent DFD: 6.7 - Provide Driver Personal Services

PSpecs in this DFD: