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.
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.
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 location/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 seconds (eg 30).
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). If Min. Duration is set to 0, the event will be counted from the 1st second.
- The minimum speed for the LSR event can be set (e.g. no LSR speed event below 15 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 (eg 15), this is the speed decrease within 1 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 speed for the event must be there at the start of the event
- 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 | Name | Description |
|---|---|---|
| 1 | Standard IVMS <=2019 | Standard mode as it is used currently. Mode 1 is based on driving time with speed > 0. |
| 2 | Standard IVMS >=2019 | This new mode was added in release 3.8.50. Its using the standard logbook for the calculation. In combination with the new asset based settings for the min. speed in combination with ignition, a standard logbook entry means ignition on and speed > 0 (Should be easier to support) |
| 3 | IVMS Logbook based | This new mode was added in release 3.8.50. Its using the standard logbook type 1 table for the calculation as mode 2 is using. Instead of Driving Time Alarm, Rest Alarm and Total KM Alarm, it has the following alarms based on the IVMS specification for Iraq.
|
Mode 1 Driving Alerts
The mode can be configured as follows:
| Driving time in minutes | ||
|---|---|---|
| Light vehicles | Light Vehicle max. total driving time [min] | Maximum driving time per day plus the buffer time: eg. 600 plus 15 driving time = ignition ON and Speed > 1 km/h |
Light Vehicle max. driving time 1 [min] => Excessive Driving Time | XXX minutes driving non-stop with a speed > 1 km/h plus the buffer time and without a stop (light vehicle minimum break time1) a stop must be longer than 5 minutes without moving) | |
| Continuing Driving - Distance | Maximum driving distance with ignition ON and Speed > 1 km/h since the last minimum break time 1 (speed = 0) | |
| Heavy vehicles | Heavy Vehicle max. total driving time [min] | Maximum driving time per day plus the buffer time: eg. 600 plus 15 driving time = ignition ON and Speed > 1 km/h |
| Heavy Vehicle max. driving time 1 [min] | 120 minutes non-stop with a speed > 1 km/h plus the buffer time and without a stop (a stop must be longer than 5 minutes without moving) | |
| Heavy Vehicle min. break time 1 [min] | for a future release | |
Heavy Vehicle max. driving time 2 [min] | 240 minutes non-stop with a speed > 1 km/h plus the buffer time and without a stop (a stop must be longer than 5 minutes without moving) | |
| Heavy Vehicle min. break time 2 [min] | for a future release | |
| Continuing Driving - Distance | Maximum driving distance with ignition ON and Speed > 1 km/h since the last minimum break time (speed = 0) |
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 duration 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.
| RAG configuration | ||
|---|---|---|
| Green for scores: | below 1 | |
| Orange: | between 1 and 3 | |
| Red | above 3 | |
| RAG min. KM for display record | 1 | drivers with less driving distance will not be shown |
| RAG list displayed days | 7 | means that the IVMS module will show data from the last 7 days |
| The formula values can be changed | ||
| RAG Time Function Fact 1 | Used for speeding and seat belt score e.g.: 10 | Speed score = ((Speeding Time*/10)/Trip Distance)*1000 ... speeding seconds per 100 km Seal belt Score = ((Time without seatbelt*/10)/Trip Distance)*1000 |
| RAG Time Function Fact 2 | Used for speeding and seat belt score e.g.: 1000 | Speed score = ((Speeding Time*/10)/Trip Distance)*1000 Seal belt Score = ((Time without seatbelt*/10)/Trip Distance)*1000 |
| RAG Event Function Fact 1 | Used for harsh braking and harsh acceleration events e.g.: 100 | Acceleration score = (Number of harsh accelerations/Trip Distance)*100 Deceleration Score = (Number of harsh braking/Trip Distance)*100 |
| Offset values | The offset values are used report the IVMS score from the last period (prior to having this system) in order to compare old IVMS score with the current score | |
| Config | Violation Yes, show in report list yes | The event is counted as violation and shown in the IVMS event list |
Violation No, show in reports yes | The event is not counted as violation, but shown in the IVMS event list | |
| Violation No, show in reports no | The event is not counted as violation and not shown in the IVMS event list | |
| Show asset names | Will show the names of the assets in the IVMS table | |
IVMS Administration General Options
| Feature | Details |
|---|---|
| Summer Night Shift | Time period for night driving alert |
| Summer End | When the summer time ends |
| Winter Night Shift | Time period for night driving alert |
| Winter End | When the winter time ends |
| Speed Limit | Not in use |
| Adjust event start time | The event duration will only count from the second AFTER the time limit If event limit is 10, the 11th second will be the start (duration 1, not 11) |
| Use HA/HB events | If unchecked: the harsh braking, harsh acceleration events will be calculated by the software using the speed positions and comparing speed changes within second-by-second data Requirement: Devices must send second-by-second data while moving If checked: the software will use device-side configured events for Teltonika devices and second-by-second data for ATrack devices |
| Google Maps | Google Maps Pictures require a separate Google Maps Business license. |
| Tires | Beta-Feature, not in use at the moment |
Other Changes:
- if a private switch is activated and the private flag is true, the data is not taken for IVMS data processing
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.
Server-side road types and geofence based speed limits (graded roads, black top roads,...)
Requirements:
- Provider must add geofences and road types to central server and set the source for speed alerts
- If the road has a road type , it will consider this speed limit (see below).
- If there is NO road type, it will consider the maximum speed limit from a DEFAULT 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 road type speed limit, the geofence speed limit will be considered.
Example for Road types (set by the vendor):
| Light Vehicles | Day time | Night time |
|---|---|---|
| Graded road | 80 | 50 |
| PDO black top road | 100 | 100 |
| Government black top road | 120 | 120 |
| Heavy Vehicles | Day time | Night time |
|---|---|---|
| Graded road | 80 | 50 |
| PDO black top road | 100 | 100 |
| Government black top road | 100 | 100 |
Requirements:
- the asset must be set as light vehicle checkbox in the asset configuration, else it is a heavy vehicle.
- Road type geofence files must be uploaded to the server by the vendor
- The night shift must be set.
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.
Feature to be phased out soon: Second-by-second driving log
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.
