Driver (Terminator*)
This terminator represents the human entity that operates a licensed vehicle on the roadway. Included are operators of private, Transit, Commercial, and Emergency vehicles where the data being sent or received is not particular to the type of vehicle. Thus this terminator originates driver requests and receives driver information that reflects the interactions which might be useful to all drivers, regardless of vehicle classification. The Driver terminator is the operator of the Basic Vehicle terminator. Information and interactions which are unique to drivers of a specific vehicle type (e.g., fleet interactions with transit, commercial, or emergency vehicle drivers) are covered separately.
Inputs/Outputs: Architecture Flows* and Data Flows*
Driver
Vehicle
- driver inputs (Architecture Flow*) - Driver input to the vehicle including configuration data, settings and preferences, interactive requests, and control commands.
Data Flows*: - request for service (Architecture Flow*) - Driver inputs that summon an emergency response, request a financial transaction, or initiate other services.
Data Flows*:
Maintenance and Construction Vehicle
Driver
- driver information (Architecture Flow*) - Regulatory, warning, and guidance information provided to the driver while en route to support safe and efficient vehicle operation.
Data Flows*:
Parking Management
Driver
- driver parking information (Architecture Flow*) - Presentation of general parking information to drivers including lot status, parking availability, and directions to available spaces, entrances, and exits.
Data Flows*: - roadside transaction status (Architecture Flow*) - The status of an electronic payment transaction provided directly to the driver via sign or other roadside infrastructure.
Data Flows*:
Roadway
Driver
- driver information (Architecture Flow*) - Regulatory, warning, and guidance information provided to the driver while en route to support safe and efficient vehicle operation.
Data Flows*:
Roadway Payment
Driver
- roadside transaction status (Architecture Flow*) - The status of an electronic payment transaction provided directly to the driver via sign or other roadside infrastructure.
Data Flows*:
Vehicle
Driver
- driver updates (Architecture Flow*) - Information displayed or otherwise conveyed by the vehicle to the driver.
Data Flows*: - in-vehicle transaction status (Architecture Flow*) - The status of an electronic payment transaction presented to the driver by in-vehicle equipment.
Data Flows*:
