Why record IVMS thresholds in one sheet?
An IVMS raises an alarm only when a value crosses a threshold. If the threshold on the device is looser than the one in your contract, events go unrecorded. If it is much tighter, drivers get false alarms and stop listening. Either way, an auditor will ask where each value came from.
The sheet keeps three things next to each other: what the client requires, what you run, and how it is set on the device.
How to use the sheet
- Enter the client value and its source for each event: document, clause and version.
- Enter the value you use on the fleet. Use the same unit as the row.
- Read the Check column. Fix every row marked looser, or get a written deviation.
- Record the device setting. Take the parameter from your device documentation or SCMS, then add the date you verified it.
- Log every change. The Change log keeps the old value, the new value and who approved it.
How the Check column decides
Each row has a Looser when setting. For most events a higher value means fewer alarms, so it is looser. For a minimum break, a lower value is looser.
Converting g to km/h per second
Some standards give harsh acceleration and braking in g, others in km/h per second. The Conversions sheet does both ways.
Keeping values current
Client standards change with new versions. Add the version to the source column and re-check the sheet when your client issues a new one. Many teams start with higher values and tighten them after a review period. The Change log is where you record that.
The grey examples are typical values. They are not requirements and are not taken from any client standard. Tracom does not say that any value in the file matches a client standard. Take client values from your contract and the current version of your client's road safety or IVMS standard. Public guidance exists too, such as IOGP Report 365-12, Implementing and sustaining an in-vehicle monitoring system programme. We read its page at iogp.org, last checked 2026-11-03. Standard gravity 9.80665 m/s² and the mile of 1.609344 km are exact factors in NIST SP 811, checked the same day.
Limits of this sheet
It records and compares values. It does not set anything on a device, and it does not know which events a device supports. Check supported events and parameter names in the device documentation.