When is the trip score ready?
The score is produced by the end of each trip. After the trip has been completed, it will take approximately 10-20 minutes for the score to be available. Part of this delay is a wait for wifi to become available. Once wifi is available it will be uploaded and processed sooner. If you want to shorten the delay, APIs are available for this.
How do "median", "mean", and "standard deviation vary over time?
The overall distribution of scores remains approximately constant. That is, the distribution is designed to have a positive skew that is consistent and does not reduce over time. However, the median, mean, and standard deviation are not constant values. Keep in mind that as more data is collected, we are able to learn more from the data, and you will see the scores approach the more general statistics.
What happens if we want to ignore a scoring category?
We currently do not provide the ability for custom weighting of individual scoring fields. We provide consistent driver scoring that is applicable to all driving conditions. However, if you wish to ignore a category, like phone handling among your drivers, you would be better off using the aggression and eco scores to gauge your drivers. Or alternatively, you can look at the scores for the individual fields you consider important. The primary effect of phone handling is evident in a driver's distraction score.
What is the top priority for scoring?
The top priority for scoring is overall driving behavior. In other words, we measure the entire drive as a whole. We measure overall behavior in the following categories:
- acceleration - braking - turning - jerk - swerve - phone handling
There is no priority for these individual fields over each other. We do, however, derive different scores such as aggression, distraction, and eco-friendliness from the behavior within those scoring categories. We also look independently at the behavior during low-speed and high-speed driving. We use the total statistical performance over the entire drive as the top priority because it provides a more consistent and detailed look at a driver's performance. It cannot be tricked. In order to generate better behavioral scores, one must improve his or her driving performance. We do, however, also take into account specific driving events: hard accelerations, brakes, and turns as well as indications of phone use and speeding. These are also given equal priority to each other but play a minor role in scores compared to the overall behavior of a driver.
What does an overall driver's score mean compared to a trip score?
The overall driver score is our measure of the driver's behavior over all time. It weights more recent trips more heavily,
but it applies to the user's history. It's like a credit score. The per trip score is more like one transaction for your credit. Some trips are more heavily weighted than others, for various reasons. But the driver score is not just an average of a user's trip scores.
As for the difference between driver score and trip score after one drive:
The driver score takes into account more contextual awareness than is appropriate for a single trip score. So they can be different. One example is that the driver score is fluid in time as other drivers do more activities, whereas the trip score is locked once it happens. The driver score is not just an average of the trip scores.
It is more sophisticated than that;
The trip score can depend on the length of the trip. Shorter trips may have less accurate scoring than longer trips and can lead to more variation in trip scoring. This gets better over time the more a user drives.
What does it mean if a trip has a "low" score?
For a drive with a low brake score, the important thing to keep in mind is that events are independent of the score. The brake score measures what someone's tendencies are throughout the entire drive. A low brake score means that this person is braking throughout the drive harder than average. That doesn't mean that they brake hard enough to generate an event. But probably every time that they do brake it's harder than normal. The person could have every single one of their brakes just under the event threshold and have no events. But compared to someone who brakes very softly every single time and has one hard brake event because the car in front stopped short, for instance, the first driver's braking behavior is much worse. The first driver's behavior tends to indicate aggressive driving style and poor fuel efficiency. The point with all of this is that you can fool events. They're flukey. A driver can figure out how to navigate around generating events. But they can't fool behavior scoring because we look at everything. The only way to get a good score is to actually drive better and safer.
What is a Hard Break?
You can define what should be a hard brake. We can set up the system that way. There isn't an ultimate definition of what a hard brake is, it depends on various factors. Also, it is important to point out that brake events don't have a constant threshold. They change based on speed. Ultimately, they change based on vehicle type, region, etc. They change based on how much the user is turning at a given time too. If they are turning too much at the same time they are braking, what they consider a hard brake we may decide is a hard turn. Further, if a hard turn is currently happening and then the user brakes hard, the whole event will be will reported as a hard turn.
How are speed and speeding limits evaluated?
There is not a set value we use for speeding. We use posted speed limit data that is defined by governments. We do not have speed limit data for all roads. If we are unable to determine the posted speed limit for a given location, we do not identify speeding directly.. However, it is important to mention that the effects of speeding are reflected in other aspects of the vehicle's motion, and so while speeding itself might not be identified, braking and turning behavior, for instance, will be significantly influenced by a person that is driving too fast on a road that is not built for high speeds. Our scoring takes into account the motion behavior more than specific speeding events.
Why does the same trip have different scores?
Trips can be all low speed and not very long. This tends to cause a bit more variation in trip scoring. This will improve over time the more a user drives. We are working on adding confidence values to the scores to make it more clear to the end user in these situations. While a vehicle class isn't required, setting it correctly will lead to more accurate score results. As part of the trip scoring, we include the driver's history in the score.
Is the username and password unique per device or is it going to change with each driver?
You want to create a user for each driver. Since this user entity is internal to your implementation it will probably simplify things ?to use the same password for every driver. The easiest way to create a user is with the easy-register rest call. For initial testing, it's okay to do this from the Mobile App, but you'll want to do this from the server side before moving into production.
Can you track the locations in offline mode?
You can get location events (in the callback) even if your device has no internet connectivity. But when you use the QueryLocations function of the LocationManager, Each location which has been caught by Clip & Go app and tracker will be uploaded to our backend when 1)the internet connectivity becomes available. But there is 2 limitations to the process:
- Locations which have not been able to be uploaded during the last 3 days are dropped.
- When getting the network again it can take until 30 minutes in the worst case for the locations to be uploaded.
Trips are separated in the SDK but not on the Web app, why?
Sometimes there are brief stops in the middle of the drive, with some walking for instance. Usually in this case, if the stop is short enough we will merge the two drives together. So it will not appear as two separate trips.
What about the location updates?
We provide location updates even when a user is not driving while consuming very little battery. These locations are annotated with an activity type that can be used to filter out any locations received while the user is not driving. Having sent a START, the app will send speed, heading, latitude, longitude every "X" distance or time. All of this information is available in the location updates. We just upload every 3 minutes to reduce network usage. Alternatively we can offer to upload more locations and sampling location more aggressively while driving (similar to what we do already for Telematics).
We provide locations every few minutes when the user is moving. The locations provide the time, latitude, longitude, speed, bearing, altitude, and accuracy associated with the location.
Is there any API to cancel or abort current trip?
No, you cannot cancel or abort the current trip.
Is there a limit to number of trips?
There is no limit to the number of trips captured per user as long as you stay under your user limit.
Can the app be uninstalled by the driver and operator of the smartphone?
Only on android if it is a company account/phone. In general not, but the fleet manager will know if it got uninstalled. A company can mandate drivers to agree to a policy that make uninstalling it a violation of the work contract.