Trips Report (Desktop)

What: The purpose of the Trips report is to capture the run time of assets with a category type of vehicles or trucks, defined as a “trip,” within a given time frame.  

(The run time of equipment is defined as a “cycle” and is captured in the Cycles Report.) 

Trackers: Assets with the following trackers will pull into this report for the time period selected, provided the tracker is installed, verified and online: 

• TennaFLEET Tracker OBD II 
• TennaFLEET Tracker JBUS 
• TennaFLEETII 

Data from the Trips report is paginated (results displayed across multiple pages to speed up loading time)and can be exported as “All Results” or “Only Displayed” (i.e., only displayed on that page). Each page displays 100 Trips. The default display is sorted by the End Time column in descending order.  

Who: Users who have the Trips permission switched ON can see the Trips Reports. This report is a part of the TennaCORE product suite (i.e., not tied to a premium product).  

Where: The Trips report is organized within the Location reports and is accessible via Reports on the left navigation, under the Location category or via the Reports drop down shortcut at the top of the screen under Location 

When: The default range for viewing the Trips report is one week ago to today. The quick date range options are Today, Yesterday, Previous Week, Previous Month. You can select a max date range of 45 days’ worth of results and can search back to the beginning of your account's history to capture each asset’s lifespan on Tenna. These time periods are shown in the account time zone as determined per Settings>Configurations.  

Sample Report-Overview of Trips Report Fields

• Major Category: Results in the trips report are driven by an asset’s category type. Assets categorized as a Truck or Vehicle will pull into the Trips Report if they were operated (i.e., ignition: ON) during the time period the report is run for. 
• Asset Organization: This begins an expandable column set that the asset is organized within, starting with the highest level of the Org Chart. 
• Fleet Number: Asset identifier. This entry is a hyperlink to that individual trip on the Trip tab with that Asset’s Details.  
• Asset Name: Asset identifier. This entry is a hyperlink to that individual trip on the Trip tab with that Asset’s Details. 
• User Organization: This begins an expandable column set that the asset’s assignee (at the time of the trip) is organized within, starting with the highest level of the Org Chart. In the sample above, the assets shown did not have an assignee assigned to them at the time the trip was captured, so there are no values. 
• Start Time: the start of the ignition: ON event, triggering the start of the trip. This is displayed in the User profile time zone.  
• Start Location: The GPS position (location) of the asset at the time of Trip start. 
• Start Site: The site the asset was on (determined by which geofence the asset is located in) at the time of Trip start. If a site has been deleted, the historical Trips report will display “deleted” for the start site.  

• End Time: the time of the ignition: OFF event, triggering the end of the trip. This is displayed in the User profile time zone.  
• End Location: The GPS position (location) of the asset at the time of Trip end. 
• End Site: The site the asset was on (determined by which geofence the asset is located in) at the time of Trip end.  
• Idling: Idling is captured as a distinct event and the duration per trip is shown in this column. Idling is reported when the engine is on (ignition: ON) and the vehicle is moving at less than 5mph for a period of three to five minutes, depending on the model of your fleet tracker. Tenna fleet trackers have timers that record and report when an asset is running and is not moving.  
  • For vehicles that support idling identification, they will report idling in this column by TennaFLEET OBD II, TennaFLEET JBUS, TennaFLEET II, TennaCAM and TennaCAM 2.0.  
  • AEMP assets do not produce trips, so they will not be included in AEMP assets even if the asset reports idling. However, AEMP assets will be included in the Idling Report.  

• PTO: Total time elapsed while asset was in Power Takeoff mode during the trip, shown as (hours:minutes:seconds) Available from TennaFLEET II devices that support capturing power takeoff. TennaCANbus trackers will report PTO as well.  
• Duration: The total length of the trip from start to end (hours:minutes:seconds) 
• Trip Miles: Total miles traveled during the trip according to the GPS distance traveled, rounded to the nearest tenth of a decimal. 
• Total Cumulative Miles: Snapshot of the total cumulative miles traveled during the trip, rounded to the nearest tenth of a decimal.
  • When a Tenna fleet tracker is installed on an asset, an odometer reading is required to be recorded as part of the installation process to set a baseline value for future trips to be added to. There are two ways to do this: 
  • You can choose to read miles from the ECU if the asset provides mileage (i.e., odometer reading) from the ECU  
  • You can choose a baseline mileage per the dashboard odometer and allow trip mileage to accumulate from there.  

• If a user wishes to use a calculated value for the Trips report, then Tenna will keep track of the aggregate miles traveled by the asset for all its Trips. For example, for the asset’s latest trip, the cumulative miles will show the total calculated odometer value for the asset, which should closely match the actual odometer reading on the asset (if the baseline was captured accurately during installation).  
  • Refer to Current Miles Overview and FAQ for more information.

• ECU Odometer Available: This is a Yes or No value. This column will read Yes if the asset allows Tenna trackers to read the odometer value directly from the ECU during that trip. The column will read No if not allowed.  
  • If ignored (column reflects No), mileage will add to the baseline value provided during installation vs. the mileage value provided by the ECU. In this case, (by user choice), you can expect discrepancies between what you see on Tenna and what the ECU odometer reads.   
    • There is an option on the Edit Asset page to ignore the ECU odometer for each individual asset (see image above). 
  • If not ignored (column reflects Yes), mileage reported on Tenna will reflect the vehicle’s true odometer value.  

• Assignee: The person assigned to the asset at the time of the trip. 
• Total Gallons Used: Total fuel consumed (in gallons) by the asset during the trip, rounded to the nearest tenth of a decimal. 
• Trip MPG: Fuel efficiency calculated as [Miles Traveled] / [Gallons Consumed] 
• Violation Count: This column corresponds to the Driver Scorecard product. If a violation is detected during the trip per a pre-configured Driver Scorecard threshold, it will be recorded here. If you click the eye icon for a trip with a violation, it will navigate you to the individual trip level where you can view the detailed list of all violations recorded on that trip. See the FAQ section below for more information on Trip violations.  

• Video Count: This column corresponds with the original TennaCAM devices and reports the number of videos captured during this trip. TennaCAM 2.0 devices displays N/A because the video information is recorded in Rosco, not in Tenna.  
  • For TennaCAM 2.0 devices, the video count can be seen at the individual trip level indicating that footage is available which can be viewed in the Rosco portal.  

Trips Reports FAQs

Why is there a speeding alert when the driver is doing the speed limit?

Why this happens sometimes: Tenna partners with HereMaps to look up the speed limit for each road at each location along the trip. If the vehicle is traveling above that number (determined by the tracker), a speeding violation is returned. However, HereMaps is not always 100% accurate. They have a long turnaround time on updating their road maps, and you may have a specific road your drivers travel often where you get multiple speeding violations a day. 

What is the difference between a tracker event reported on the Trips Report and a Scorecard violation? 

Trips Reports and Driver Scorecards are closely related, but independent and distinct from one another. Not every tracker event reported on the Trips Report will equal a Driver Scorecard violation. The fleet tracker reports information tied to each Trip in the Trips Report. If a trip event is outside the limit of a driver scorecard trigger, the event reported by the tracker will still display in the Trips report, even if it does not pull into the Driver Scorecard. Events that populate in both Trips Reports and Driver Scorecards (if the tracker event triggers a violation based on the scorecard threshold) include speeding, idling, hard accelerating and hard braking (e.g. hard braking > 0.5Gs). PTO and Camera Connected are specific to the Trips report and are unrelated to Driver Scorecard. Also, Trips Reports are part of TennaCORE and always available for Tenna users with fleet assets tagged with fleet trackers, even if they do not have Driver Scorecards enabled. 

Where the confusion lies: Sometimes you see a speeding start and end event on a Trip (with that section of the trip painted red on the map), but there is no correlated Driver Scorecard violation. This means that the tracker detected the asset speeding above 70mph, which is default tracker behavior. This speed may not have met the threshold set on your driver scorecard for speeding (determined post-trip via HereMaps, described in FAQ 1 above), and therefore will not appear on the Driver Scorecard. Driver Scorecard speeding thresholds can be based on any speed reported by the tracker, not just the speed reported by the tracker in the Trip speeding event (70mph, always). 

How it really works: Tenna receives speed in nearly all fleet tracker messages, which is how it knows if the asset was traveling, for example, at 32 mph vs. 45 mph, which is then (if Driver Scorecard is enabled) cross checked against HereMaps to know if the asset was traveling above the speed limit. In the above example, going 45mph in a 35mph zone could be considered a Driver Scorecard violation and shown as a violation on the trip map based on a Driver Scorecard speeding threshold of >10mph. This has nothing to do with the tracker over-speeding event of 70mph, which will appear on all trips regardless of whether Driver Scorecard is enabled.  

What do the Trips map icons indicate and how do they relate to the Trip report?  

The Violation exclamation on the map is a Driver Scorecard related violation. These will only appear if Driver Scorecard is enabled on your account. Solid red dot (no exclamation) are tracker events reported for that Trip. For example, a “Tracker: Over Speeding” start/end event, indicated in red on the map, is a tracker specific event that a TennaFLEET II triggers on/off at 70mph.These are not related to the scorecard, so they will not show a value under the Threshold column. Events labeled Speeding are labeled as a Violation with an exclamation on the map and were triggered by the scorecard thresholds limits, thereby indicating a value in the Threshold column. 

Why are there no values for some Trips thresholds?

Threshold columns are only filled out for scorecard events. The visibility of the Threshold columns is not tied to the Driver Scorecard feature being enabled for an account – they are always visible. If you do not have the Driver Scorecard product, these columns will always be empty. A value in the “Threshold Met”, “Value,” “Speed Limit” and “Points” columns correspond with the relevant scorecard threshold that triggered the event. A blank value (or “- -”) indicates that this was a tracker triggered event.  

Why is the start or end address wrong or missing? 

Why this sometimes happens: Tenna gets a lat/long location from the tracker, which we send to Google Maps. Google Maps either tells us that address for those coordinates if one exists, or they return nothing if the location does not correlate with a mapped road(i.e., Google has not determined this location is a defined place). While Google Maps is correct very often, sometimes they are wrong in more remote locations including small dirt roads, mines, quarries, etc.  

Why am I not getting video/events from my Trips Report?

Why this happens: Usually this happens when someone has covered the camera lens, in which case you get significantly fewer events. The camera will still report video for external events, but these are typically fewer than internal facing video events.  

Why is my Trip starting off the coast of Africa?  

Why this happens: This is a GPS issue and is a reality for all gps-enabled devices. GPS devices sometimes take a few moments to get a good reading depending on environmental factors such as weather, asset location in an area of poor service, an obstructed view of the tracker to the sky, etc. The tracker itself has not received a valid GPS location and is reporting coordinates (0,0) as a default, which results in the South Atlantic Ocean. This results in the Trips report reporting the asset traveling many more miles than it truly did. This is usually a transient/temporary issue while the tracker waits for a better GPS reading. 

“My asset hasn’t moved in three days – why is it bouncing around the yard?” and other GPS inaccuracies.  

Why this happens: The relates to how GPS works. GPS reporting determines a location via satellite. 30 to 40 feet of GPS drift is common. You may notice this in your personal life when you are waiting for an Uber pickup and the app shows your location across the street from where you truly are, or how the map on your vehicle GPS thinks you may have exited the highway when roadways merge.