Commercial Vehicle Subsystem

This subsystem resides in a commercial vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient commercial vehicle operations. The Commercial Vehicle Subsystem provides two-way communications between the commercial vehicle drivers, their fleet managers, attached freight equipment, and roadside officials, and provides HAZMAT response teams with timely and accurate cargo contents information after a vehicle incident. This subsystem provides the capability to collect and process vehicle, cargo information from the attached freight equipment, and driver safety data and status and alert the driver whenever there is a potential safety or security problem. Basic identification, security and safety status data are supplied to inspection facilities at mainline speeds. In addition, the subsystem will automatically collect and record mileage, fuel usage, and border crossings.

Security Considerations

The Commercial Vehicle Subsystem contains screening and safety data, and is used to support roadside electronic screenings. Cargo content information should be protected from unauthorized access for knowledge of this information, especially security sensitive HAZMAT cargo, could target the vehicle for hijacking or terrorist attack. In support of driver authentication, driver identity characteristics (i.e. biometrics, Personal Identification Number (PIN)) would be stored on-board the vehicle and appropriate measures should be taken to protect this personal information. In general, the Commercial Vehicle Subsystem handles personal and business sensitive information about the commercial vehicle including container content information that needs to have a relatively high degree of confidentiality in order to safeguard the information. In addition, it is important that the information about the commercial vehicle and its cargo is available to the Commercial Vehicle Administration subsystem. The integrity of the information from the commercial vehicle is also important to prevent deceptive practices.

Functionality: Equipment Packages and PSpecs

• On-board Cargo Monitoring
  
  • 2.4.2 - Collect On-board Commercial Vehicle Sensor Data
  • 2.4.3 - Analyze Commercial Vehicle On-board Data
  • 2.4.7 - Manage CV On-board Data
  • 2.8.3.2 - Monitor Freight Equipment Status
  
  
• On-board CV Electronic Data
  
  • 2.2.3 - Provide CV Driver Electronic Credential and Tax Filing Interface
  • 2.3.7 - Produce Commercial Vehicle Driver Message on Vehicle
  • 2.4.1 - Communicate Commercial Vehicle On-board Data to Roadside
  • 2.4.6 - Provide Commercial Vehicle On-board Data Store Interface
  • 2.6.2 - Transmit Commercial Vehicle Tag Data
  • 2.6.3 - Provide Commercial Driver Tag Data Interface
  • 2.6.4 - Provide Lock Tag Data Interface
  • 2.6.5 - Manage Commercial Vehicle Tag Data Store
  
  
• On-board CV Safety and Security
  
  • 2.3.7 - Produce Commercial Vehicle Driver Message on Vehicle
  • 2.4.1 - Communicate Commercial Vehicle On-board Data to Roadside
  • 2.4.2 - Collect On-board Commercial Vehicle Sensor Data
  • 2.4.3 - Analyze Commercial Vehicle On-board Data
  • 2.4.4 - Provide Commercial Vehicle Driver Interface
  • 2.4.5 - Communicate Commercial Vehicle On-board Data to Vehicle Manager
  • 2.4.6 - Provide Commercial Vehicle On-board Data Store Interface
  • 2.4.7 - Manage CV On-board Data
  • 2.6.2 - Transmit Commercial Vehicle Tag Data
  
  
• On-board Driver Authentication
  
  • 2.4.3 - Analyze Commercial Vehicle On-board Data
  • 2.4.4 - Provide Commercial Vehicle Driver Interface
  • 2.4.7 - Manage CV On-board Data
  • 2.4.9 - Authenticate Commercial Vehicle Driver
  
  
• On-board Intermodal Terminal Interface
  
  • 2.8.3.1 - Provide Driver Interface for Intermodal Freight Dispatch
  • 2.8.3.3 - Manage On-Board Facility Access
  
  
• On-board Trip Monitoring
  
  • 2.1.4 - Provide Commercial Vehicle Driver Routing Interface
  • 2.2.2 - Provide Vehicle Static Route
  • 2.2.4 - Provide Commercial Vehicle Driver Communications
  • 2.4.2 - Collect On-board Commercial Vehicle Sensor Data
  • 2.4.3 - Analyze Commercial Vehicle On-board Data
  • 2.4.4 - Provide Commercial Vehicle Driver Interface
  • 2.4.5 - Communicate Commercial Vehicle On-board Data to Vehicle Manager
  • 2.4.6 - Provide Commercial Vehicle On-board Data Store Interface
  • 2.4.7 - Manage CV On-board Data
  • 2.4.8 - Correlate Commercial Vehicle Route
  
  

Inputs/Outputs: Architecture Flows and Data Flows

Basic Commercial Vehicle > Commercial Vehicle Subsystem

• commercial vehicle measures - Commercial vehicle and driver status measured by on-board ITS equipment.
  Data Flows:
  • fbcv-distance_traveled
  • fbcv-vehicle_identity
  • fbcv-brake_condition
  • fbcv-driver_safety_status
  • fbcv-driver_status
  • fbcv-vehicle_safety_status
  • fbcv-vehicle_security_status
  • fbcv-weight
  
  

Border Inspection Systems > Commercial Vehicle Subsystem

• border pass/pull-in - Command to commercial vehicle to pull into or bypass border inspection station
  Data Flows:
  • border_vehicle_pass_pull_in
  
  
• clearance notification - Notification that cargo has been cleared through customs.
  Data Flows:
  • border_vehicle_clearance_notice
  
  

Commercial Vehicle Check > Commercial Vehicle Subsystem

• border clearance data request - Request for trip specific data regarding the movement of goods across international borders. Includes trip identification number. May also include results from recent border crossing screening events.
  Data Flows:
  • cvo_border_clearance_request
  
  
• border clearance event - Reports clearance event data regarding action taken at border, including acceptance or override of system decision, and date/time stamp
  Data Flows:
  • cv_on_board_border_record
  
  
• driver log request - Request for driver log data.
  Data Flows:
  • cvo_driver_log_request
  
  
• electronic lock data request - Request from roadside for data regarding presence and status of electronic cargo locks.
  Data Flows:
  • cv_request_electronic_clearance_data
  
  
• electronic screening request - Request for identification data to support electronic screening.
  Data Flows:
  • cv_request_electronic_screening_data
  
  
• on-board safety request - Request for on-board vehicle safety data by the roadside equipment.
  Data Flows:
  • cv_request_on_board_data
  • cvo_onboard_safety_data_request
  
  
• pass/pull-in - Command to commercial vehicle to pull into or bypass inspection station.
  Data Flows:
  • cv_on_board_pull_in_output
  
  
• request tag data - Request for tag information including credit identity, stored value card cash, etc.
  Data Flows:
  • cvo_request_tag_data
  
  
• safety inspection record - Record containing results of commercial vehicle safety inspection.
  Data Flows:
  • cv_inspection_data_output
  
  
• safety inspection request - Request for safety inspection record.
  Data Flows:
  • cvo_safety_inspection_request
  
  
• screening event record - Results of CVO electronic screening activity.
  Data Flows:
  • cv_on_board_screening_record
  
  

Commercial Vehicle Driver > Commercial Vehicle Subsystem

• alert response - 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:
  • fcvd-driver_response
  
  
• CVO driver initialization - 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.
  Data Flows:
  • fcvd-enrollment_request
  • fcvd-route_request
  • fcvd-route_data
  • fcvd-request_tag_data_output
  • fcvd-other_data_input
  • fcvd-enrollment_payment_request
  • fcvd-driver_input_type
  • fcvd-driver_general_message
  • fcvd-driver_data_input
  • fcvd-carrier_number
  • fcvd-activity_request
  • fcvd-vehicle_number
  • fcvd-driver_number
  • fcvd-request_routing_instructions
  
  
• driver identity characteristics - 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:
  • fcvd-driver_characteristics
  
  
• trip identification number input - Commercial vehicle driver input containing the unique trip load number for a specific cross-border shipment.
  Data Flows:
  • fcvd-trip_identification_number
  
  

Commercial Vehicle Subsystem > Basic Commercial Vehicle

• safe vehicle disable - Control signal disabling or enabling commercial vehicle.
  Data Flows:
  • tbcv-disable_vehicle
  
  

Commercial Vehicle Subsystem > Border Inspection Systems

• tag data - Unique tag ID and related vehicle information.
  Data Flows:
  • border_vehicle_onboard_clearance_data
  
  

Commercial Vehicle Subsystem > Commercial Vehicle Check

• border clearance data - Trip specific data regarding the movement of goods across international borders. Includes trip identification number. May also include results from recent border crossing screening events.
  Data Flows:
  • cvo_border_clearance_data
  
  
• commercial vehicle breach - Information about a breach or tamper event on a Commercial Vehicle or its attached freight equipment which includes identity, type of breach, location, and time.
  Data Flows:
  • freight_breach_for_rs
  • cv_security_alarm
  
  
• commercial vehicle disable status - This flow provides the status of the disable flag in the commercial vehicle.
  Data Flows:
  • cv_disable_info
  
  
• driver log - A daily log showing hours in service for the current driver.
  Data Flows:
  • cvo_driver_log
  
  
• electronic lock data - Notification to roadside (via transponder) of the presence and status of electronic cargo locks.
  Data Flows:
  • cv_electronic_clearance_data
  
  
• expected driver identity characteristics - Driver identification information e.g. encrypted PIN codes issued to drivers, encrypted driver biometric parameters.
  Data Flows:
  • stored_driver_identity_characteristics
  
  
• freight equipment information - Container, trailer, or chassis information regarding identity, type, location, brake wear data, mileage, seal #, seal type, door open/close status, chassis bare/covered status, tethered / untethered status, Bill of Lading, and sensor status.
  Data Flows:
  • freight_equipment_info
  • freight_info_for_inspection
  
  
• on-board safety data - Safety data measured by on-board sensors. Includes information about the vehicle, vehicle components, cargo, and driver.
  Data Flows:
  • cvo_onboard_safety_data
  • cv_on_board_data
  
  
• safety inspection record - Record containing results of commercial vehicle safety inspection.
  Data Flows:
  • cvo_safety_inspection
  
  
• screening event record - Results of CVO electronic screening activity.
  Data Flows:
  • cv_electronic_screening_data
  
  
• tag data - Unique tag ID and related vehicle information.
  Data Flows:
  • cvo_tag_data
  
  

Commercial Vehicle Subsystem > Commercial Vehicle Driver

• alerts - 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:
  • tcvd-route_data
  • tcvd-critical_safety_problem
  • tcvd-critical_security_problem
  • tcvd-data_request
  • tcvd-routing_instructions
  
  
• CVO pass/pull-in message - 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:
  • tcvd-on_board_pull_in_output
  
  
• intermodal dispatch - Directions for dispatch for pickup or delivery of an intermodal load.
  Data Flows:
  • tcvd-container_transfer_location
  • tcvd_intermodal_dispatch_route
  • tcvd-intermodal_container_transport_assignment
  
  
• trip log information - 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:
  • tcvd-data_input_request
  • tcvd-output_data
  • tcvd-confirm_data_stored
  • tcvd-enrollment_confirmation
  • tcvd-enrollment_payment_confirmation
  • tcvd-type_input_request
  • tcvd-other_data_request
  • tcvd-output_tag_data
  
  

Commercial Vehicle Subsystem > Emergency Management

• hazmat spill notification - Information provided to emergency response organizations when cargo sensors detect a release of hazardous material. This information will include sensor information, vehicle location and identification, and carrier identification.
  Data Flows:
  • cvo_hazmat_spill_data
  
  

Commercial Vehicle Subsystem > Fleet and Freight Management

• commercial vehicle breach - Information about a breach or tamper event on a Commercial Vehicle or its attached freight equipment which includes identity, type of breach, location, and time.
  Data Flows:
  • cv_freight_breach
  • cvo_security_alarm
  
  
• driver alert response - Commercial Vehicle Driver response to a breach alert for a Freight Equipment breach or tamper event.
  Data Flows:
  • cv_driver_response
  
  
• driver to fleet request - Requests from the driver and vehicle for routing, payment, and enrollment information.
  Data Flows:
  • cv_driver_enrollment_request
  • cv_driver_route_request
  • cv_driver_storage_request
  • cf_driver_route_instructions_request
  • cv_driver_enrollment_payment_request
  • cv_static_route_data
  
  
• freight equipment information - Container, trailer, or chassis information regarding identity, type, location, brake wear data, mileage, seal #, seal type, door open/close status, chassis bare/covered status, tethered / untethered status, Bill of Lading, and sensor status.
  Data Flows:
  • cv_freight_location
  • cv_cargo_information
  • cv_freight_operations
  • cv_freight_maintenance
  • cv_freight_integrity
  
  
• identities - Identification information for the Commercial Vehicle (e.g., license plate number), Freight Equipment (e.g., container, chassis, or trailer identification), and Driver.
  Data Flows:
  • cv_identities
  
  
• intermodal status - Information from a commercial vehicle on the status of container and chassis systems that the vehicle is transporting.
  Data Flows:
  • intermodal_container_status
  • intermodal_chassis_monitoring_status
  • intermodal_chassis_status
  • intermodal_container_monitoring_status
  
  
• on-board safety data - Safety data measured by on-board sensors. Includes information about the vehicle, vehicle components, cargo, and driver.
  Data Flows:
  • cvo_tag_safety_data
  • cvo_on_board_safety_data
  
  
• on-board vehicle data - Information about the commercial vehicle stored on-board (for maintenance purposes, gate access, cargo status, lock status, etc.).
  Data Flows:
  • cf_on_board_vehicle_data
  • cf_tag_data_store_output
  
  
• route deviation alert - An alert that indicates a deviation from a planned route has been detected. The alert will contain the current Commercial Vehicle location and identity.
  Data Flows:
  • cv_route_warning
  
  
• trip log - Driver's daily log, vehicle location, mileage, and trip activity (includes screening, inspection and border clearance event data as well as fare payments).
  Data Flows:
  • cvo_trip_log_data
  
  

Commercial Vehicle Subsystem > Freight Consolidation Station

• container transfer location request - Request for the location within an intermodal facility for the transfer of a container.
  Data Flows:
  • tfcs-container_consolidation_location_request
  
  
• entry request - Request by a commercial vehicle for permission to enter an intermodal transfer facility.
  Data Flows:
  • tfcs-entry_request
  
  
• exit request - Request by a commercial vehicle for permission to leave an intermodal transfer facility.
  Data Flows:
  • tfcs-exit_request
  
  
• vehicle identification - Identification of a commercial vehicle to an intermodal terminal for the purpose of entrance and exit control, guidance, and safety monitoring.
  Data Flows:
  • tfcs-commercial_vehicle_identification
  
  

Commercial Vehicle Subsystem > Intermodal Terminal

• container transfer location request - Request for the location within an intermodal facility for the transfer of a container.
  Data Flows:
  • container_transfer_location_request
  
  
• entry request - Request by a commercial vehicle for permission to enter an intermodal transfer facility.
  Data Flows:
  • entry_request
  
  
• exit request - Request by a commercial vehicle for permission to leave an intermodal transfer facility.
  Data Flows:
  • exit_request
  
  
• vehicle identification - Identification of a commercial vehicle to an intermodal terminal for the purpose of entrance and exit control, guidance, and safety monitoring.
  Data Flows:
  • cv_vehicle_identification
  
  

Commercial Vehicle Subsystem > Vehicle

• commercial vehicle data - Information about the commercial vehicles cargo, credentials, and payments.
  Data Flows:
  • cv_driver_enrollment_cost
  • processed_cargo_data
  
  

Driver Identification Card > Commercial Vehicle Subsystem

• cv driver credential - Driver information (e.g., identity, biometrics, address, date of birth, endorsements, restrictions) stored on a driver’s license or other official identification card used to identify a driver of commercial vehicles.
  Data Flows:
  • fdic-driver_cred_info
  
  

Fleet and Freight Management > Commercial Vehicle Subsystem

• commercial vehicle disable - This flow safely disables a specific commercial vehicle.
  Data Flows:
  • cv_disable
  
  
• container transport assignment - Instructions to a commercial vehicle for the transportation of a container.
  Data Flows:
  • intermodal_container_dispatch_assignment
  • intermodal_route
  
  
• expected driver identity characteristics - Driver identification information e.g. encrypted PIN codes issued to drivers, encrypted driver biometric parameters.
  Data Flows:
  • cv_driver_assignment
  
  
• fleet to driver update - Updated instructions to the driver including dispatch, routing, and special instructions.
  Data Flows:
  • cf_tag_data_store_request
  • cvo_general_message
  • cf_tag_data_store_write
  • cf_driver_route_instructions
  • cf_manager_route_monitoring_parameters
  • cv_driver_route_data
  • cvo_vehicle_route
  • cv_driver_enrollment_information
  • cv_static_route_request
  • cv_driver_enrollment_payment_confirmation
  
  
• intermodal status request - Request from a fleet manager for the status of an intermodal load.
  Data Flows:
  • intermodal_chassis_status_request
  • intermodal_container_status_request
  
  
• on-board safety request - Request for on-board vehicle safety data by the roadside equipment.
  Data Flows:
  • cvo_on_board_safety_data_request
  • cvo_tag_safety_data_request
  
  
• on-board vehicle request - Request for on-board vehicle data.
  Data Flows:
  • cvo_tag_data_store_request
  • cvo_on_board_vehicle_data_request
  
  
• trip identification number - The unique trip load number for a specific cross-border shipment.
  Data Flows:
  • cvo_trip_identification_number
  
  
• trip log request - Request for trip log.
  Data Flows:
  • cvo_trip_log_data_request
  
  

Freight Consolidation Station > Commercial Vehicle Subsystem

• container transfer location - Location within an intermodal facility that a container is to be received at or delivered to; may include guidance as well as location.
  Data Flows:
  • ffcs-container_consolidation_location
  
  
• entry permission - Permission for a commercial vehicle to enter an intermodal transfer facility.
  Data Flows:
  • ffcs-entry_permission
  
  
• exit permission - Permission for a commercial vehicle to leave an intermodal transfer facility.
  Data Flows:
  • ffcs-exit_permission
  
  

Intermodal Customer > Commercial Vehicle Subsystem

• trip identification number - The unique trip load number for a specific cross-border shipment.
  Data Flows:
  • fic-trip_identification_number
  
  

Intermodal Freight Equipment > Commercial Vehicle Subsystem

• cargo data - Measures associated with the cargo inside a container, like temperature.
  Data Flows:
  • cargo_status_for_cv
  
  
• chassis data - Measures from chassis systems like brakes, tires, and fasteners.
  Data Flows:
  • chassis_status_for_cv
  
  
• container status - Measures from systems on-board the container, possibly including refrigeration, shock measurement, controlled atmosphere sensing and any other systems that support special needs of the cargo.
  Data Flows:
  • container_status
  • container_status_for_cv
  
  
• freight breach - Information about a breach or tamper event on Freight Equipment which includes identity, type of breach, location, and time.
  Data Flows:
  • fe_breach_warning_for_cv
  
  
• freight equipment information - Container, trailer, or chassis information regarding identity, type, location, brake wear data, mileage, seal #, seal type, door open/close status, chassis bare/covered status, tethered / untethered status, Bill of Lading, and sensor status.
  Data Flows:
  • fe_maintenance_data_for_cv
  • fe_lock_tag_data_for_cv
  • fe_location_data_for_cv
  • fe_operational_data_for_cv
  • fe_integrity_data_for_cv
  • fe_cargo_info_for_cv
  
  

Intermodal Terminal > Commercial Vehicle Subsystem

• container transfer location - Location within an intermodal facility that a container is to be received at or delivered to; may include guidance as well as location.
  Data Flows:
  • container_transfer_location
  
  
• entry permission - Permission for a commercial vehicle to enter an intermodal transfer facility.
  Data Flows:
  • entry_permission
  
  
• exit permission - Permission for a commercial vehicle to leave an intermodal transfer facility.
  Data Flows:
  • exit_permission
  
  

Location Data Source > Commercial Vehicle Subsystem

• position fix - Information which provides a traveller's or vehicle's geographical position.
  Data Flows:
  • From_Location_Data_Source
  
  

Vehicle > Commercial Vehicle Subsystem

• commercial vehicle data request - Requests from the vehicle for information about the commercial vehicle's cargo, credentials, and payments.
  Data Flows:
  • cargo_data_request
  • cv_driver_credit_identity