Tracker Verification Overview

Tracker verification allows you to ensure each tracker is functioning properly at the time of installation and ensure data is flowing accurately from the tracker to Tenna.

Permission Requirements:

  • Users with Tracker Verification permission can verify trackers after they were installed on assets.

NOTE: Tracker Verification is only available for Tenna Trackers (except TennaQR). Assets that have OEM Telematics and Tenna Integrations are not eligible.

Important: Each Tracker Verification process is made up of criteria - specific to that tracker type - that the "verifier" must access as pass or fail. See the tracker type's specific Tracker Verification pages for more details.

Tracker Verification Workflow

The status of a tracker changes throughout the tracker installation and verification process. View the visual below to learn more about the lifecycle of a tracker's status.

Click to view larger

Customer Inventory

  • Tracker has been allocated to the customer, but not yet installed
  • Tracker is shown in Tracker Status page
  • Data available includes Tracker Type, Tracker Model, Tracker Serial No, IMEI/ICCID (if applicable)

Installation in Progress

  • Tracker QR code has been scanned in Tenna App to begin installation process, but installation is not yet complete.
  • Tracker is shown in Tracker Status page
  • More data, like asset name, location, timestamp, etc., begins to populate.

Installation Pending Verification

  • Tenna App installation is complete and the tracker must now be verified in Tenna on your desktop.
  • Tracker is shown in Tracker Verification page

Installation Failure

  • Tenna App installation is complete, but Tenna did not receive accurate data to allow for Verification. The verifier finds inaccurate data and marks "fail" for one or more item on the Tracker Verification page.
  • Tracker is shown in Tracker Verification page
  • Installer should troubleshoot and begin installation process again.

Online

  • Verification is complete. The verifier passed all data.
  • All applicable data is showing in Tenna.
  • Tracker is removed from Tracker Verification page, but stays in Tracker Status page.

Tracker Verification Criteria Matrix

The matrix below shows all of the criteria necessary to verify for each tracker type during the Tracker Verification process.

Click to view larger

*Accurate Hours and Miles: The above are the default criteria for Tracker Verification. If your use case does not justify hours or miles on a certain asset (and you have opted out of hours or miles reporting), then the accurate hours or miles field will not show on the Tracker Verification page.

Trip Report: The Trip Report allows the user to confirm multiple data points captured during the last test trip after tracker installation.

  • Accurate Address: The trip start and trip end addresses are accurate

NOTE: Before trackers are verified, their status is “Installation Pending Verification,” limiting your visibility of asset location and certain asset detail information. Assets without "online" trackers show the asset Site as "Sandbox", which is simply a name for the holding place for assets without verified trackers.

  • Accurate Position: The position is accurately represented on the map.
  • Accurate Path: The dots on the map connecting Point A and Point B provide an accurate estimate of the path of the vehicle’s first trip.
  • Accurate Miles: Accurate Miles requires the user to first select the mileage source that will be used when updating Current Miles (ECU Odometer vs Baseline + Trip Distance), and then verify that the reported value is accurate as compared to the vehicle’s odometer reading.
  • Accurate Camera Feed: The camera feed shown on the app is accurate.

Cycle Report: The Cycle Report allows the user to confirm multiple data points captured during the last test cycle after tracker installation.

  • Accurate Hours: (TennaMINI only) The Accurate Hours step allows the user to confirm the running time for one or more test cycles after tracker installation.

Location Reading Timestamp: (TennaBLE only) allows the user to confirm that the date and time of location capture is accurate.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.