IVMS Driver-Rating System (in-vehicle monitoring system) for safe driving

     Download this page as PDF

Requirements

• The license for using the IVMS module must be activated by your vendor & our support. Contact your vendor for more details.
  
• The tracking telematics need a special configuration (settings and firmware) and the right accessories such as driver identification (with ignition interruption; buzzer , panic alert, connection to the seat belt signal (if the seatbelt is worn, the input must be positive). The local vendor is responsible for using appoved configuration files. Changes in eventIDs or parameters will have an effect on low or high driver ratings.
• The device in-vehicle installation must be done tamper-proof by professionals. Faulty installation can lead to high or low driver ratings. All relevant features must be tested at the end of the installation using a special test driver. The test trip must be clearly highlighted in the system.
• It is recommended, that the panic alert button is always connected to the same digital input and that the seat belt worn signal is always connected to the same digital input. These inputs can be configured for each asset or globally for all assets.
• In order to receive SMS alerts, an sms gateway must be used by the sytem integrator. The cost of sending sms is not included in the software license. Contact your vendor for more details.

IVMS Module Overview

• You can filter for specific drivers and set a start and end date for the report.
• The Excel or PDF Export will export the current Red-amber-green report with the current data and the formula calculation on page 2.

A double click on a driver opens the detailed RAG overview report for this driver. The data of the current year is compared to the last period.

False alerts (numbers in brackets)

The number in the brackets stands for the false alerts (that have been marked in the Events List as false alert). A test during installation or other reasons could lead to events that should not be counted as effective event.

Event view

You can filter for all IVMS events in this view.

You can set an alert as "false alert" with a comment in this view (e.g. test during installation or wrong data from device). The operators are responsible to mark false alerts and add a comment why the alert is false.

Harsh accelerations and brakes

Overspeeding view

Seatbelt view

Settings for assets to be counted as IVMS asset

The IVMS checkbox on the asset configuration must be activated so that the asset is counted as IVMS asset.

The Light Vehicle checkbox is very important so that the special regulations for light vehicles apply. If this checkbox is empty, the regulations for heavy-vehicles will apply.

Device Input configuration

You must set the digital input for each asset that is connected to special signals such as the ignition, the seat belt or the alarm button. The ignition must be configured. If no seatbelt signal nor alarm button is configured, the IVMS system will take the global IVMS settings.

Second-by-second driving log (BETA-Feature, this feature will be phased out)

You can dowload the available second-by-second driving log data from your tracking device. Please be aware that this feature requires special device settings (and a special firmware). Past second-by-second data will be deleted from the tracking device storage after some time. We recommend to download the data immediatelly if you need it or to use a standard configuration that sends data every second.

IVMS Settings

All IVMS alarms can be configured in the IVMS alarm section:

Alarm types (alarm list, email, reports, etc.)

You can select the type of notification if an event occures. If you keep the event "-" empty, the event will not be shown.

Report, view

If you select "Report, View", the event is shown in the alarm table and the alarm & event report.

Email

If you select email, the alert will be sent via email and is shown in the alarm list and alarm report.

Your GPS Fleet Software server needs a valid Google maps business license so that pictures are shown in the alert emails.

SMS

If you select sms, the alert will be sent via SMS and email and is shown in the alarm list and alarm report.

Your GPS Fleet Software server needs a working sms gateway so that the messages are forwarded via sms.Contact your vendor for more details.

Alarm call

If you select Alarm call, the alert will be routed as a automatic voice call and email and is shown in the alarm list and alarm report.

Your GPS Fleet Software server needs a working voice call service so that the messages are forwarded via sms. Contact your vendor for more details.

Report, no view

If you select "Report, no view, the event will be shown in the event list and can be clicked or downloaded as PDF or Excel.

Beep

If you select Beep alert, the software user will be notified with an acoustic "beep" sound in the browser. The loudspeaker must be turned on.

Overspeeding events

A new overspeeding event is generated under the following conditions

• the driving speed is higher then the speed limit for the current road or geofence (see below) plus the additional Limit that is set in the IVMS options (e.g. 10).
• the duration of the speeding event is longer than the minimum duration in the IVMS options.

Source of speed limits

The source for the speed limits is set by the provider on a central server that manages the online mapping data. Contact your provider for more information.

General speed source "Online Maps" (NO-Speed-KML)

The current road speed limit comes from different sources:

• In general, the road based speed limit comes from online maps (openstreetmaps.org). The road based speed limit plus the "exceeding speed limit by" value from the asset is the speed limit.
• If there is NO road based speed limit, the asset based maximum speed is the speed limit.
• If the asset speed limit is lower then the road-based speed limit, the asset-based speed limit will be considered.
• If there is a geofence-based speed limit and it is lower than the asset-based speed limit, the geofence-based speed limit will be considered.

KML-File road-based speeds (old version for Oman)

• If the road has a KML-file road speed, it will consider this speed limit (see below).
  • If there is NO KML-file road speed limit for that road, it will consider the maximum speed limit from the government black top road (depending on day vs. night time and light vs. heavy vehicle).
  • If there is a geofence-based speed limit that is lower then the KML road-based speed limit, the geofence speed limit will be considered.

If a KML file is set, the following road based speed limits apply (set by the vendor):

Requirements:

• the asset must be set as light vehicle checkbox in the asset configuration, else it is a heavy vehicle.
• A KML file must be uploaded to the web-server and set as "KML Speedfile Path" under options (see below)
• The night shift must be set.
• The KML street precision must be set to a value. We recommend "0.001". 

The KML street precision is a distance value to match vehicles to a certain KML road type. The KML road is a line and we add a corridor to the line so that the vehicle is recognized for this KML road:

• Smaller precision values: if no nearby KML road type will be found, it will consider the maximum speed limit from the government black top road (depending on day vs. night time and light vs. heavy vehicle).
• Higher precision values: a nearby KML road type will be found, the road-based speed limit will apply

Geofence Polygons as source of Speed Limits

Your provider can upload geofences as polygons to act as speed limits for your country. 

Corridor or polygon geofances can be setup in the software and assigned to road type groups (= geofence groups). 

The road type groups will have different speed limits based on day vs. night or light vs. heavy vehicles.

The roadtypeid with def=1 is the DEFAULT GEOFENCE (DG) that is used if NO geofence is found.

In case that server side geofences are used for speed limits, the source of the speed limit is shown in the gps tracking data.

Excessive Overspeeding (Life Safety Rule LSR event)

The LSR excessive overspeeding event is triffered under the following conditions:

• The driving speed exceeds the speed limit for that road with the higher speed limit (e.g. 20 km/h above the speed limit)
• The higher speed is reached for a minimum duration (e.g. 5 seconds)
• The minimum speed for the LSR event can be set (e.g. no LSR speed event below 50 km/h).

Seatbelt Violation

• The asset must drive while the signal of the seatbelt sensor must be off.
• The seatbelt sensor must be assigned and connected in the asset configuration for this asset or globally for all assets using the pulldown. "-" means no global seat belt sensor connected for all assets. If you drive and there is no positive signal for the seatbelt input, there will be long seatbelt violations!
• The minimum speed for the seatbelt violation must be reached 
• The minimum duration for the seatbelt violation must be reached.
• The tracking device will activate the buzzer in case of driving without seatbelt (refer to the tracking device configuration).

Harsh Braking

• The minimum limit in km/h per second must be reached. The minimum limit is configured in the device configuration with a corresponding "g" value (refer to the device configuration) and sends a device event or is triggered by the software if the tracking device sends second-by-second data.
• The minimum speed for the event must be reached.
• The tracking device will activate the buzzer in case of the event (if configured on the device).

Harsh Acceleration

• The acceleration must be larger than the limit in km/h per second. The minimum limit is configured in the device configuration with a corresponding "g" value (refer to the device configuration) and sends a device event or is triggered by the software if the tracking device sends second-by-second data.
• The minimum duration for the event
  • If the minimum duration is 0, the software compares 2 consecutive positions or accepts a device event. It is counted as harsh acceleration only if the speed increase between the 2 positions is higher than the limit or if the device sends a device event.
  • If the minimum duration is 1, 2 or 3 seconds (or more), the software counts only longer events and does NOT count device events. It is counted as harsh acceleration only if the speed increase above the limit between the start and the end position is longer than 1,2 or 3 seconds.
  • Example for second-by-second data: a minimum limit of 10 km/h/s for consecutive 3 seconds means a real speed increase of 30 km/h within 3 seconds.
• The tracking device will activate the buzzer in case of the event (if configured on the device).

Continuing Driving alerts

The mode can be configured in the IVMS options.

Mode 1 Driving Alerts

The mode can be configured as follows:

Overdriving alert comments

After the driving time is exceeded, an alert is generated.

The start TS are the beginn of the generated alert (start of overdriving alert).

The comment shows the total duration of the overdriving event and the configured limit. The overdriving event starts after the last break that was longer than the minimum break time.

Please note that the overdriving comment will change if the driving event is still on-going (current overdriving trip has not yet ended).

Mode 2 Driving Alerts

Uses the same settings as mode 1, but with logbook-based data. Only recommended if assets use ignition plus minimum speed > 1 for the logbook.

Mode 3 New Setting and Events

All settings for mode 3 can be done in a new tab, because the events might have the same name, but have different logic and parameter

Night Driving Alert

A night driving alert is triggered under the following conditions:

• The asset is moving during the night shift time window (refer to options below)
• The asset is moving outside a geofence that is marked as "night driving". This means that a trip within the night driving geofence doesn't trigger a night driving alert.
• You can create a geofence with a radius in meters and activate the checkbox "is Night Zone"
• Minimum distance out of night zone must be travelled. If the device enters the night zone again, the minimum distance will count again.

It is possible to deactivate the Night Driving Alarm for specific assets and/or specific drivers (this option is only shown if you use IVMS module);

Panic Button alert

The Panic or SOS alert is sent if

• A button is pressed and the digital input of the asset is set as "Alarm switch"
• The button must be pressed with a minimum duration (depending on the device configuration).

GPS Visibility alert

The GPS visbility event refers to the HDOP value of a device. If a tracking device has no valid GPS signal (HDOP value is 0.0 or 99) AND ignition is ON, this warning event will occur. Please consider that every GPS device will have no GPS during waking up or when entering or leaving a building or garage.

Crash event alert

Requirements:

• Devices configuration "Crash detection" must be enabled, we recommend "Low priority" setting because else old data prior to the crash is lost
• Devices configuration "Acceleration treshold" and duration must be tested so that it is really meaningful
• Software-setting IVMS must be activated on account and for the asset

New Crash Events will be generated as alerts (alarm list and/or email/sms/...)

The above limit is the speed limit for this position.

Tampering event

If the device recognizes a movement without ignition, this is called a "Tampering" or tow event.

Options for RAG Report Event

The colour code settings can be set as follows.

General Options (for Night Driving)

Google Maps Pictures require a separate Google Maps Business license.

Other Changes:

• if a private switch is activated and the private flag is true, the data is not taken for IVMS data processing