Prism FTC’s Post

It's certainly off road, but is the engine running.... This example from a recent audit map review highlights one of the nuances of using telematics device data for FTC. How reliable is the ignition state data and when might it be lying? Some of the common methods and their drawbacks are: 🔑 Hard-wired inputs from the ignition key assembly ➜ May not differentiate between 'Accessory' and 'On' positions ⚙️ Reading the CAN Bus for the ignition reference or engine RPMs ➜ Not available for all vehicles and dependent on CAN configuration 🛰️ Detecting speed breaching a threshold value by comparing sequential GPS readings ➜ Will not detect idling and can give false readings if the vehicle experiences motion via other means (such as on board a ferry). 📟 Detecting movement via on-device accelerometer ➜ Same as above. No single method is perfect so increasingly device manufacturers are combining multiple inputs to determine if a vehicle really is running, or just moving. Spot and resolve edge cases like this before they come up in an audit. Talk with us about automating your FTC today.

  • map

To view or add a comment, sign in

Explore topics