Commercial Vehicle Driver (Terminator*)
This terminator represents the human entity that operates vehicles transporting goods including both long haul trucks and local pick up and delivery vans. This terminator is complementary to the Driver terminator in that it represents those interactions which are unique to Commercial Vehicle Operations. Data flowing from the Commercial Vehicle Driver terminator will include those system inputs specific to Commercial Vehicle Operations, such as information back to the Fleet-Freight Manager. Data flowing to the Commercial Vehicle Driver may include system outputs such as commands to pull into a roadside safety inspection facility. Showing the Driver as a terminator includes the user interface devices within the ITS architecture boundary. The Commercial Vehicle Driver will be expected to interact with the ITS interface devices designed to provide support for their usage.
Inputs/Outputs: Architecture Flows* and Data Flows*
Commercial Vehicle
Commercial Vehicle Driver
- alerts (Architecture Flow*) - This flow represents the visual or auditory interface with ITS equipment containing specific alerts and messages related to commercial vehicles (e.g. trucks not advised, trucks over 10 tons not allowed on bridge, route details). This also includes detected route deviations and warning indications detected by on-board sensors (e.g., safety) and freight equipment sensors (e.g., breach, cargo).
Data Flows*: - CVO pass/pull-in message (Architecture Flow*) - This flow represents the visual or auditory interface with ITS equipment containing a message sent to commercial vehicle driver indicating whether to bypass or requesting pull in to inspection/verification stop along with inspection results (e. g., LED indicator on transponder or variable message sign).
Data Flows*: - trip log information (Architecture Flow*) - This flow represents the tactile or auditory interface with ITS equipment containing the information entered into the trip log, or request for update.
Data Flows*:
Commercial Vehicle Check
Commercial Vehicle Driver
- CVO pass/pull-in message (Architecture Flow*) - This flow represents the visual or auditory interface with ITS equipment containing a message sent to commercial vehicle driver indicating whether to bypass or requesting pull in to inspection/verification stop along with inspection results (e. g., LED indicator on transponder or variable message sign).
Data Flows*:
Commercial Vehicle Driver
Commercial Vehicle
- alert response (Architecture Flow*) - This flow represents the tactile or auditory interface with ITS equipment containing the response by a Commercial Vehicle Driver or Fleet-Freight Manager that confirms or cancels an alert.
Data Flows*: - CVO driver initialization (Architecture Flow*) - This flow represents the tactile or auditory interface with ITS equipment containing the commercial vehicle driver and vehicle information. This flow contains inquiries to the commercial vehicle managing system, interaction with on-board equipment including setup, configuration, and initiation of self tests, and entry of carrier, driver, vehicle, and route information.
Data Flows*:- fcvd-activity_request
- fcvd-carrier_number
- fcvd-driver_data_input
- fcvd-driver_general_message
- fcvd-driver_input_type
- fcvd-driver_number
- fcvd-enrollment_payment_request
- fcvd-enrollment_request
- fcvd-other_data_input
- fcvd-request_routing_instructions
- fcvd-request_tag_data_output
- fcvd-route_data
- fcvd-route_request
- fcvd-vehicle_number
- driver identity characteristics (Architecture Flow*) - The physical or visible characteristics of a commercial vehicle driver that can be measured to uniquely identify a driver. Could be an Identification Card with a Personal Identification Number, biometrics, or visual verification by an operator.
Data Flows*: - trip identification number input (Architecture Flow*) - Commercial vehicle driver input containing the unique trip load number for a specific cross-border shipment.
Data Flows*:
