cv inspector interaction Quintuple

Bidirectional?: True

cv inspector interaction (A-Interconnect): This CVRIA application interconnect encapsulates all of the Layer 2 information flows between the 'CVCE Electronic Screening' application object and the 'Commercial Vehicle Inspector' physical object. This application interconnect is bi-directional since the underlying layer 2 information flows carry data in both directions.

Commercial Vehicle Inspector (Source Physical Object): The people who perform regulatory inspection of Commercial Vehicles in the field. CVO Inspectors support roadside inspection, weighing, and checking of credentials either through automated preclearance or manual methods. The Commercial Vehicle Inspector is an inspection and enforcement arm of regulatory agencies with frequent direct interface with Commercial Vehicles and their Drivers.

Commercial Vehicle Check Equipment (Destination Physical Object): 'Commercial Vehicle Check Equipment' supports automated vehicle identification at mainline speeds for credential checking, roadside safety inspections, and weigh-in-motion using two-way data exchange. These capabilities include providing warnings to the commercial vehicle drivers, their fleet managers, and proper authorities of any safety problems that have been identified, accessing and examining historical safety data, and automatically deciding whether to allow the vehicle to pass or require it to stop with operator manual override. Commercial Vehicle Check Equipment also provides supplemental inspection services such as expedited brake inspections, the use of operator hand-held devices, mobile screening sites, on-board safety database access, and the enrollment of vehicles and carriers in the electronic clearance program.

CVCE Electronic Screening (Destination Application Object): "CVCE Electronic Screening" supports electronic credentials and safety screening of commercial vehicles at mainline speeds. It processes the data from the commercial vehicles along with accessed database information to determine whether a pull-in message is needed. It may also generate random pull-in messages with provisions for facility operators and enforcement officials to have manual override capabilities.