Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

When viewing detailed results of the Speed Event Management Report

Step-by-Step guide

STEP 1:

When you have opened up the detailed view of a Speed Event from the report results (or have been linked to one via an alert), the first information you will see will be the following;

Image Removed

Device: Shows the device which

Data fields

After running a Speed Event Management Report, each event will contain the following information:

DeviceShows the device that generated the speed event. This will be either an IVU, Qube or

...

iFace screen

...

VehicleIndicates the vehicle that the aforementioned device is assigned to in NextGen

...

Fleet

...

Fleet that the vehicle is a member of

...

Driver

...

If you have driver login enabled and your driver was logged in at the time of the incident, then their name will be displayed in this column

...

BranchBranch that the driver is a member of
Start LocationLocation of the Speed Event 
Start

...

Time at which the speed event started
End

...

Time at which the speed event finished

Details: 

  • Duration of the speed event
  • Maximum speed reached
  • Speed limit 
  • Offset (speed over the limit at which the speed event is triggered)
  • Threshold type
  • Threshold duration
  • End type

STEP 2:

The map indicates where the speed event took place. Green indicates the beginning of the speed event and red the end. 

Image Removed

...

Threshold TypeThis refers to which type of speed event has been triggered: 
  • SignPosted - based off road-specific maps data. Please note that this option is only applicable to iFaces, not standalone IVUs or Qubes. 
  • Config - a set speed dictated by our default settings our chosen by the Transport Operator upon request. You have the option of choosing a Config threshold for all of your vehicles in NextGen, specific fleets or even individual vehicles. Please contact Support if you would like to configure this setting. 
Speed Events can be generated using either of these threshold types, or both (if both are selected, the lowest speed will always be used. For example, if the Config threshold is set at 100 km/h, but your vehicle drives at 95 km/h in a 90 zone, a SignPosted event will be generated). 
Speed Limit (km/h)The limit that was breached 
Max Speed (km/h)The highest actual speed that was recorded for this particular event 
Duration (h:m:s)The length of the event
End TypeThe reason why the event ended. 
  • Normal - The vehicle went back below the threshold
  • InvalidSpd - We had invalid GPS 
  • ThrshChange - if the speed threshold changed (for example, Threshold type was SignPosted and the vehicle moved from an 80 km/h zone to a 90km/h zone) 
View Event

Click on the iconImage Addedto view more details related to a particular Speed Event

Event map

After clicking on the View Event iconImage Addedyou will see the location of the event on a map. 

Image Added

Green = Start of the trip | Orange = Middle of the trip | Red = End of the trip

Speed graph

Expand
titleIf your vehicle has an IVU or standalone iFace

Below the map, you will see a speed vs altitude chart. This is particularly useful in understanding the driver's behaviour. Most of the time you will see the altitude decrease as the speed increases, indicating that the vehicle was speeding up as it came off a hill

Image Added

If your vehicle is fitted with an IVU, the speed event will most likely be generated from this unit and not the iFace

...

Image Removed

...


Expand
titleIf your vehicle has a Qube

Below the map, you will see a speed chart. This is particularly useful in understanding the driver's behaviour. 

Image Added


Event data

NextGen also displays second-by-second speed information underneath the speed vs altitude chartat the bottom of the page. This gives you a clear view of the rate at which the speed increased increases, as well as valuable information regarding the quality of the GPS signal during the speed event. If the GPS signal is less than ideal during the event, this brings the validity of the event into question. 

Image Removed

The above second by second data indicates a perfectly valid speed event - the NSAT (Number of Satellites 7+) is high, and the HDOP is consistently low (<1.5) 

At times, invalid speeds may display. However, the report will provide GPS values to allow a user to determine the validity of an event. 

A valid speed event is typically indicated by a high number of satellites (4+) in the NSAT column, and a low number (<4.0) in the HDOP column.


EXAMPLE POOR SPEED EVENT

Filter by label (Content by label)
showLabelsfalse
max5
spacesTKB
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel in ( "speed" , "events" , "event" , "speeding" ) and type = "page" and space = "TKB"
labelsspeed speeding event events

...