First Data
As previously mentioned, the Telematics device contains GPS as well as wireless data, and apparently an accelerometer. It seems to record events at 2 sec intervals and reports them to the database when able (i.e. within range).
Each user gets their own "dashboard" which is a web portal on the Insurance Company's website and provides a synopsis of their driving behavior. Each Monday the user will get a report by email of the previous week's summary.
In addition to the Dashboard, further reports are available, such as the Events Report. Events are defined as Overspeeds (both "soft" and "extreme"), Hard Accelerations, and Hard Brakes. As of yet, there is no data on cornering force, but building that capability is supposedly one of the main criteria. Given the technical issues, it is understandable that this may take some time to develop. The Events Report can be generated for any specific date or range of dates. It's kind of neat as it shows exactly what, where and when. The "where" is accomplished with a map and locator arrows that show precisely where each "event" took place. Hovering your mouse (not shown) over any arrowhead pops up the specific log entry detailed at left. The log provides detailed date and time (hours/min/sec), the event, and the associated data. In my case, all my events so far are overspeeds, so the log provides my actual instantaneous speed, and the posted limit for that section of road in brackets. Errors of posted limits in the database are to be reported and fixed as they show up. I'll try and incur some hard accelerations and braking for my next example to determine their thresholds and how they are measured.
In the example I've shown, this is the cloverleaf intersection of Main Street North and #1 Highway. Because this is the Prairies, and corners are to be valued, I often take three leafs of the cloverleaf rather than just turn right. This is apparent when you see that I approached from the west on the #1 (limit 100 kph), passed under Main Street (limit 70 kph), and turned north, then back west on #1 and finally a turn back south on Main Street (call it my version of the "Long Way Round" ). The top visible log entry (08:49:57) is the first of the arrows as I exit the #1 for the first time.
Well, the data shows that I held relatively constant speeds through the corners and accelerated smoothly out of them (I used no brakes throughout). Unfortunately, the on and off-ramps are entered into the database as 50 kph limit, resulting in my impressive collection of "events". Logically, one should not slow to 50 kph on a major highway prior to exiting, nor maintain 50 until you are already in the 100 kph zone before accelerating. Admittedly one of the program's stated criteria is to ultimately measure cornering force, but arbitrarily placing speed limits in corners is not the same thing. I have pointed this out through the site feedback forum, received agreement, and understand it will be corrected.
As mentioned above, I'll report again when I have more observations.
JP
As previously mentioned, the Telematics device contains GPS as well as wireless data, and apparently an accelerometer. It seems to record events at 2 sec intervals and reports them to the database when able (i.e. within range).
Each user gets their own "dashboard" which is a web portal on the Insurance Company's website and provides a synopsis of their driving behavior. Each Monday the user will get a report by email of the previous week's summary.
In addition to the Dashboard, further reports are available, such as the Events Report. Events are defined as Overspeeds (both "soft" and "extreme"), Hard Accelerations, and Hard Brakes. As of yet, there is no data on cornering force, but building that capability is supposedly one of the main criteria. Given the technical issues, it is understandable that this may take some time to develop. The Events Report can be generated for any specific date or range of dates. It's kind of neat as it shows exactly what, where and when. The "where" is accomplished with a map and locator arrows that show precisely where each "event" took place. Hovering your mouse (not shown) over any arrowhead pops up the specific log entry detailed at left. The log provides detailed date and time (hours/min/sec), the event, and the associated data. In my case, all my events so far are overspeeds, so the log provides my actual instantaneous speed, and the posted limit for that section of road in brackets. Errors of posted limits in the database are to be reported and fixed as they show up. I'll try and incur some hard accelerations and braking for my next example to determine their thresholds and how they are measured.
In the example I've shown, this is the cloverleaf intersection of Main Street North and #1 Highway. Because this is the Prairies, and corners are to be valued, I often take three leafs of the cloverleaf rather than just turn right. This is apparent when you see that I approached from the west on the #1 (limit 100 kph), passed under Main Street (limit 70 kph), and turned north, then back west on #1 and finally a turn back south on Main Street (call it my version of the "Long Way Round" ). The top visible log entry (08:49:57) is the first of the arrows as I exit the #1 for the first time.
Well, the data shows that I held relatively constant speeds through the corners and accelerated smoothly out of them (I used no brakes throughout). Unfortunately, the on and off-ramps are entered into the database as 50 kph limit, resulting in my impressive collection of "events". Logically, one should not slow to 50 kph on a major highway prior to exiting, nor maintain 50 until you are already in the 100 kph zone before accelerating. Admittedly one of the program's stated criteria is to ultimately measure cornering force, but arbitrarily placing speed limits in corners is not the same thing. I have pointed this out through the site feedback forum, received agreement, and understand it will be corrected.
As mentioned above, I'll report again when I have more observations.
JP