Four Parties Involved in Facial ID Cases:

1. Customer - This is the person who pays monthly for the subscription service to access hdfleet.net and has requested the add-on service called Facial ID.
   
   
2. HD Fleet Application - This is the application that stores the trip data, provides a graphical interface for customers to interact with, and access to the Facial ID API.
   
   
3. EdgeTensor Facial ID API - This is an API service that HD Fleet Application interacts with involving Facial ID profiles. No facial ID profiles are stored within the HD Fleet Application, just a Facial ID # that is shared between HD Fleet and EdgeTensor. No driver information is shared with EdgeTensor API, only driver-facing videos, so it can build a unique facial ID profile to videos and convert the videos into unique FID Profiles.
   
   
4. Driver - People that drive the vehicles, are assigned unique Facial ID profiles, and later linked by the customer to the Facial ID #.

FID Error Codes:

1. N/A - No response from FID Video Processing Matching Servers.  It must have exceeded the 10-minute wait time we have set for maximum returned results.  No action is needed from the customer, but operations will be notified to review whether the FID Application is functioning.
   
   
2. 116 - The video was not good enough to render a FID Profile #.
   
   
3. 113 - The video was obstructed by something and no FID Profile could be created or matched in the system.
   
   
   

   Note
   This is a Facial ID workflow at a high level
   
   

How to Enable Facial ID:

1. Contact us or your local reseller in your area. We will turn on the feature or enroll you in the Facial ID program for up to 4 weeks.
   
   

   Note
   The link to enable FID by reseller is in your secure portal.
   
   
2. To turn it on within our application, go to Settings, then click Customers.
   
   
   
   
3. Find the customer you want to enable Facial ID for and click the Edit button.
   
   
   
   
4. Check the box that says EdgeTensor API to enable it.
   
   
   
   

Warning
Make sure you are legally allowed to collect data from your employees.

How to Enroll Your Vehicles:

1. Within our platform, go to Settings, and then Vehicles.
   
   
   
2. Edit the vehicle you would like to enroll.
   
   
   
   
3. Change the slider named Driver ID Enabled to Yes. The other items should default to Enrollment and Disabled.
   
   
   
   
   

   Note
   When Driver ID is enabled, the default driver is cleared, if set prior. It is neither unassigned nor unrecognized. It will go blank or state that Facial ID is enabled.
   
   Now that Facial ID is enabled and your vehicles are enrolled, it's time to review your drivers. It will take a few days for the API to start assigning Facial ID #'s to your active trips, but it will need to match the drivers it sees to the drivers that are on the platform. If you need help creating drivers, check out this article.
   

How It Works:

1. All trips for the enrolled vehicles send up to 3 videos per trip to the EdgeTensor API for enrollment and then verification.
   
   
2. The vehicle will stay in the enrollment phase until a Facial ID # is returned for that vehicle.
   
   
3. After a Facial ID # is returned, it moves from Enrollment to Verification status, notifying our platform that the vehicle has met the minimum requirements to acknowledge future drivers.
   
   

Facial ID Report:

1. From our platform, go to Reports and find Facial ID API Status.
   
   
2. In the Driver ID Enabled column, there are 6 possible states.
   
   
3. Facial ID - Calibrating.
   
   

   Note
   In this state, it may take a while for the API to identify the driver. We will attempt to identify the Facial ID # for this trip, however, after 3 attempts, it will move from unrecognized to unassigned and await manual assignment. If a Facial ID # is created while being in the Enrollment State, we will provide a Facial ID # and change the state to Verification. Otherwise, there will be an error code in the FID Code column for review.
   
   
4. Facial ID - Identifying.
   
   

   Note
   The system is attempting to identify the driver within the trip, sending 3 videos to the API. If nothing is returned, there will be an error code letting the customer know why a match was not found, and they will have to be manually assigned. If a Facial ID # is returned, then we will attempt to link it to a Driver profile. If there isn't one found, then we will place a link to the Facial Identification Module for future matching to a driver. 
   
   
5. Facial ID #. (It links to the Facial Identification tab)
   
   
6. Driver Name Matched to Facial ID #.
   
   
7. Unrecognized. (It links to the Change Driver pop-up)
   
   
8. Unassigned. (When nothing was able to be linked)
   

Logic for AI Resolution to Unrecognized Drivers:

1. All trips that were flagged with Unrecognized Driver would be in your Alert Board and are waiting for manual assignment and marked with a review status as Not Reviewed.
   
   
   
   
2. If a trip was identified in the same 24-hour period, then it will assign the same Facial ID for all trips that took place prior with the same ID.
   
   

   Note
   The status on the Alert Board will change to Completed and the Driver Assigned will be moved from Unrecognized Driver to the Facial ID #. The same will happen in the Vehicle Pop-up and Reports.

Special Use Cases:

1. If only 1 Facial ID # was found within the same day, then all previous trips and proceeding trips would be assigned to that Facial ID #.
   
   
2. If 2 or more Facial ID #'s were found on trips throughout the day, then the logic would be all previous trips prior to the Facial ID # being assigned would be assigned to the first facial ID #, and all the proceeding trips would be assigned to the most recent Facial ID #.
   
   
3. If no Facial ID #'s were assigned that day, then the application would keep the trips as unrecognized and is awaiting for them to be assigned manually.
   
   

Assigning Facial ID #'s to Drivers:

1. Alert of Facial ID #'s that need to be matched with Drivers.
   
   
2. Alert for Unrecognized Drivers.
   
   

   Note
   Both of these Alerts can be modified to email the end user. We recommend the Facial ID #'s need to be matched to drivers to be notified by email, but not required.

Videos Being Sent to EdgeTensor:

1. Videos will be sent at 30-second intervals based on ignition on and when the vehicle exceeds 5 mph with a 5-minute gap.
   
   
2. All assignments would be done within 18 minutes at the most.