Driver ID

Raven Connected is excited to offer QR Code Driver Identification to our partners. This optional feature is designed to be leveraged within your existing Raven offering to provide secure, verifiable identification of employees operating your customers' vehicles.

By utilizing the Raven cabin-facing camera, this simple-to-use system scans a unique driver QR code upon vehicle startup. This immediately notifies your system of the driver's identity, unlocking three critical value pillars for your customers:

• Managed Access & Safety: Improve fleet safety by ensuring that only authorized individuals are operating specific vehicles.
• Performance Context: Move beyond tracking the vehicle to tracking the driver. Pair Driver ID data with telematics events to monitor specific employee performance (e.g., linking harsh braking events to a specific driver, not just the truck).
• Operational Efficiency: Increase efficiency by allowing automated systems to track vehicle usage for payroll, timesheets, or compliance, removing the need for manual logs.

To support these goals, we have exposed a set of flexible configuration options via the RC-API. Below is a guide to these settings and how they shape the user experience for different types of fleets.

Configuration Guide: Tailoring the Driver Experience

One size rarely fits all for this reason we designed the API settings to allow you to customize the Driver ID flow to fit different fleet needs.

The Master Switch: Enabling Driver ID

• API Setting: barcode_driver_id_enabled
• This is the foundational setting that toggles the feature on or off.
• The Experience: When set to false, Raven behaves like a standard video telematics device. When set to true, Raven transforms into an active identification terminal. Upon vehicle startup, it will interrupt the standard screen flow to present a prompt, asking the user to present their unique QR code to the cabin-facing camera.
• Why use it: This must be enabled for any of the specific behaviors below to function.

The Frequency: Per Trip vs. Per Day

• API Setting: barcode_driver_id_request_period
• Once the feature is enabled, this setting dictates how often a driver needs to prove their identity. You can choose between two modes based on how the fleet operates.
  • Option A: PER_TRIP (High Accuracy)
    • The Experience: Raven asks for a scan every time the engine starts.
    • Best For: Fleets where vehicles travel for lengthy periods of time where stops are infrequent or where drivers might switch off throughout the day.
  • Option B: PER_DAY (Convenience)
    • The Experience: Raven asks for a scan only once per calendar day.
    • Best For: Assigned vehicles or take-home cars. If a technician is assigned a specific van for the day, they scan in at 8:00 AM and are authenticated for the rest of the day, regardless of how many stops they make. 

The "Grace Period" (Crucial for Delivery Fleets)

• API Setting: barcode_driver_id_grace_period
• This is the most critical User Experience (UX) setting for last-mile and service fleets. It functions only when the request period is set to PER_TRIP. It defines a time window (in seconds) during which a driver can turn the vehicle off and back on without needing to rescan their badge.
• The Scenario: Vehicles don’t have set drivers and may have several shifts within a given day. A delivery driver turns off the engine to drop off a package and returns 10 minutes later.
  • Without Grace Period: The driver must pull out their badge and scan again at every single stop. This leads to frustration and "alert fatigue."
  • With Grace Period (e.g., 300 seconds): Raven recognizes the short stop. If the driver restarts the car within 5 minutes, the system remembers them and waives the scan requirement.
• Why use it: It balances granular data tracking with driver sanity.

Note: The grace period is configurable measured in seconds up to a maximum of 24 hours.

Audio Reminders (The "Nudge")

• API Setting: barcode_driver_id_audio_delay
• Drivers are busy. Sometimes they start the car, check their mirrors, and buckle up before they are ready to present their ID. This setting controls the delay (in seconds) before Raven plays an audio prompt reminding them to scan.
• The Experience:
  • Short Delay (0s): Immediate compliance. Best for high-security environments.
  • Longer Delay (15-30s): A "polite" workflow. It gives the driver time to get settled in the cabin before the device asks for attention.
• Why use it: Adjusting this delay helps integrate the scanning process smoothly into the driver's existing pre-trip routine without feeling intrusive.

Security During Idling

• API Setting: barcode_driver_id_check_at_idle
• Most driver ID systems only check credentials when the car starts. But what if a driver leaves the vehicle running to grab a coffee, and another driver takes over?
• The Experience: This setting forces a re-scan if the vehicle has been idling for a set period. For example, if set to 300 seconds (5 minutes), and the truck idles for 6 minutes, Raven will begin the scanning process again and ask, "Who is driving now?"
• Why use it: This can be used as a security feature for emergency vehicles, or vehicles carrying sensitive cargo. It alerts management to unauthorized access if a vehicle is left running and unattended.

Customer Profile	Recommended Configuration	Why?
Delivery / Courier	PER_TRIP Request Period + High Grace Period	Ensures accurate trip tracking but eliminates annoyance during quick drop-offs.
Pool / Shared Fleet	PER_TRIP Request Period + Low Grace Period	Strict tracking. Since drivers change often, the system must verify every start.
Assigned / Techs	PER_DAY Request Period	Convenience. The driver owns the car for the day; one scan is enough.
High Security / Cargo	Check at Idle	Monitors unauthorized access if the vehicle is left running/unattended.