• About
  • Connected Vehicle
  • Architecture
  • Approach
  • Viewpoints
  • Security
• Applications
• Views
  • Enterprise
  • Functional
  • Physical
  • Communications
• Standards
  • CV Standards
  • CV Standards Plan
• Resources
  • Databases
  • Diagrams
  • Documents
  • Presentations
  • Tools
  • Training
• Glossary
  • Acronyms
• Contact Us

2.6.3: Provide Commercial Driver Tag Data Interface

This process shall be responsible for providing the interface through which the commercial vehicle driver can set up the data in an on-board vehicle unit (e.g. an electronic tag). In this instance the driver is assumed to be acting in the role of a commercial vehicle fleet manager, and is thus likely to be the owner of the vehicle. The data the process enables the manager to write to the tag will be that which identifies the carrier, driver and vehicle. The process shall also enable the read this data from the tag, but shall not enable the manager to read any other data from the tag. The process shall support inputs from the commercial vehicle driver in both manual and audio form, and shall provide its outputs in audible and visual forms. It shall enable the visual output to be in hardcopy, or as a display.

This process is associated with the Commercial Vehicle OBE physical object.

This process is associated with the following application objects:

• CV On-Board Electronic Screening Support

This process is associated with the following data flows:

• cv_tag_data_store_output - In
• cv_tag_data_store_request - Out
• cv_tag_data_store_write - Out
• fcvd-carrier_number - In
• fcvd-driver_number - In
• fcvd-request_tag_data_output - In
• fcvd-trip_identification_number - In
• fcvd-vehicle_number - In
• tcvd-confirm_data_stored - Out
• tcvd-output_tag_data - Out