Skip to main content
Sign in

Trips

Marisa Potgieter
  • Updated

FCPlus trips module manual

FCPlus Trips module

The Trips module provides you with the route and additional aspects that are involved in a trip. A Trip can be defined as the segments of a vehicle's journey from one location to another.Trips can be classified as Business or Private and may be transferred to the Journal module for tax purposes. 

The primary purpose of the Trips module is to displays the journey of a vehicle divided by locations where the vehicles spent at least some time.

Trips module the main view

The Trips module Main screen consists of two sections:

1. The "Trips List" on the left-hand side, and 2. The "Trip Details" on the right-hand side

The Trips list displays the list of all the  Trips in an organization for the selected period. The Trip details display the enhanced information of the selected trip from the Trip's List.

The Trip list

The left-handside panel in the trips screen displays a list of all the completed trips for a selected time frame.

At the top of the screen is the Asset and Date Range selector section.

Trips can be searched and filtered by vehicle name, time, trips not in Journal, and trips that match a particular Route. 

On the top, there are also possibilities to export trips in an excel or pdf format.

You can also print trips from the Trip list.

Note: Summarize and Add as private entries buttons are used to move Trips to the Journal module.

Below the sector section, the following columns can be displayed for each trip:

  • Date of the trip.
  • Time of the trip.
  • Route of the trip.
  • Length of the trip.
  • Duration of the trip.
  • Stop duration of the trip.
  • Max speed of the trip.
  • The average speed of the trip.
  • Fuel consumed estimated of the trip.
  • Fuel consumption estimatedof the trip.
  • Fuel consumedis Actual fuel consumed during the trip.
  • Fuel consumption is Actual fuel consumption during the trip.
  • ID is the trip row number in the database.
  • The driver of the trip.
  • Countryof the trip.
  • Distance from the previous trip is the distance between the end location of the last trip and the start location of the next trip.

Note: Columns can be added or removed to the Trip list by checking them.

The Trip details 

When you select a trip from the Trips List Section/Screen on the left-hand side, the application locates that trip on the map to the right-hand side in the Trip Details. 

The Green pushpin on the map indicates the start location of the trip, whereas the Red pushpin indicates the end location of the Trip.

In the Trip detail screen, you can view:

  • The date of the Trip.
  • The Start and End time of the Trip.
  • The Start and End Location of the Trip.
  • Route of the trip on the map.
  • The Length or Distance covered in the Trip.
  • The Duration of the Trip.
  • The Average and Maximum speed during the Trip.
  • A small map of the track for the selected trip.
  • Journal entry to add trips to a Journal.
  • You can add trips as private and business using the buttons on the bottom right-hand side corner.

Distance calculation and end-odometer assigning for Trips and Journal

First system creates segments from sequencial logpoints. Each segment has start time, end time, type (possible values - stop,idling,driving) and length which is calculated in following logic.

  • Between each sequencial GPS lat/lon pair in points consisting a segment, distance is found with mathemathical formula and summarized to GPS-distnace of a segment.
  • Between each log-point odometer value distance is calculated using simple (current_point_odometer - previous_point_odometer logic) and summarized to Odometer-distance of a segment.
  • Between each log-point GPS tracker device distance value distance is calculated and summarized to Device-distance of a segment (not all trackers provide it).

As Odometer and GPS are different measuring systems there is allways difference (1-5% mostly) between those three distances. We want to use odometer distance if possible, but since there are sometimes issues with it in incoming data, some decisions are made to decide what to use as final Segment-distance.

Storing the final Segment-Distance:

  • If vehicle has hasCanBus and useCanDistance - use Odometer-distance;
  • If Odometer-distance is empty use Device-Distance;
  • If Device-distance is empty use GPS-Distance;
  • Quality check fallback: If the distance ends up being calculated from CANDistance, or Device-distance and distance is > 5km and differs from GPS distance by more, than 10%, use GPS distance.

Not regarding the distances used the Begin and End Can odometers are saved to segment if they exist.

Next sequencial Driving segments are summarized to Trip.

If there is short stop or idiling (duration configurable) in between Driving segments, this idle/stop time is summarized also into Trip.

Trip end odometer is taken from: last segment end odometer, if it has value.

Next, if trips are moved to Journal - then Journal distance is taken from the trip distance, but Journal end odometer is taken from previous Jorunal records end-odometer + current trips distance.

To make Journal record distances and odometer not deriving from vehicle odometer - once in a day days last trips Journal end odometer is fixed by vehicles known end-odometer and the distances of the Journal records are slightly corrected - so that previous days end odometer + current days Journal distance = precicely current days end-odometer.

Powered by Zendesk