You may notice a difference in the total miles or kilometers when comparing, for instance the Monthly Trip report and the RAG Augmented Summary report for the same time period or when comparing a report with the information displayed in MiX Insight Agility.
It is important to note that these differences do not indicate data integrity issues but rather that reports take a snapshot of data for a certain time period, working with different logic, which means that the data you see might differ slightly as a result of certain factors detailed in this article.
Edge cases that may cause a difference in the results returned:
- Your driver has driven over midnight and because some reports use trips and others use sub-trips, it could result in the report excluding a sub-trip if movement only started before or after the day included in the report criteria.
- Different security levels (i.e. your permissions) might influence what is displayed in a report.
- MiX Insight Agility offers an extra layer of reporting that is not be available in MiX Insight reports that allows a user to view reports by current site and this could influence values if a driver or asset was moved to a different site.
- Rounding could cause slight differences in values.
Edge case - a trip over midnight
These slight differences in values are caused by calculations performed on trips where driving took place over midnight. Some reports use trips, other reports use sub-trips when calculating totals, which may then result in a discrepancy in the totals that are shown when comparing certain reports.
Example
The driver started a trip just before midnight on 31 August and ended the trip on 1 September. In this example the sub-trip took place on 1 September but the trip started on 31 August. If the report selection is to see information for trips, all the sub-trip distances that occurred on 1 September will be included. If the selection is by sub-trips, they will be excluded for 31 August.
See below for a depiction:
The trips are indicated in blue and the sub-trips are represented by the green. The illustration shows one trip going over midnight at the start of the month and one going over midnight at the end of the month. In this example, the user is selecting the start and the end of the month as the date range selection for reports.
The Monthly Trip report is generated based on the full trip's start date and time, not the sub-trip. Therefore it will include sub-trip #3 and #4, because the full trip starts in the month. This report does not take into account that sub-trip #4 actually starts in the next month. Sub-trips #1 and Sub-trip #2 will be excluded because the full trip starts before the month, it does not take into account that Sub-trip #2 starts in the month.
The Augmented RAG Summary report selection is based on the start of a sub-trip and ignores the full trip start date and time. Sub-trip #2 will be included, but Sub-trip #1 will be excluded because it starts before the month. Sub-trip #3 will be included but Sub-trip #4 will be excluded because it starts outside of the selection, even though its full trip starts inside.
This means the start of month scenario will have a slightly larger distance value for the Augmented Summary report whereas the end-of-month example means a slightly larger distance value for the Monthly Trip report. Note that these tend to be edge cases and that it tends to even out over large selections.
Edge case - different security levels
Users may have different permissions to different organisations, sites or groups and when a driver or asset has been moved from one site to another and the selection criteria excludes the new site that the driver/asset has been moved to, based on the user's permissions, the new results will also exclude the driver or asset from the results on the report. This does not mean that the driver or asset has now been excluded from the data itself or that the data is missing, it simply means that the user does not have access to the information and therefore the snapshot of data shown on the report is different to a report viewed by a user with full access or permissions to extra sites or groups.
Edge case - current site vs. historical site
A significant difference between MiX Insight Reports and MiX Insight Agility is that MiX Insight reports display information for the current site, whereas Agility displays information for the current site as well as historically correct data, which means that you will see an "extra layer" of information in MiX Insight Agility.
Some reports roll up the information and show the current sites, like the summary and overview reports, while others like the detailed reports and the daily reports show lines of information displaying the current site of the driver as well as the previous site.
Example
An example of this would be that a driver has been moved from site A to site B in the middle of the month. A user then views an Insight Report for the entire month but only sees the information for that driver in site B, because that is the current site the driver belongs to.
A driver belonged to a site called, Alabama in September but was moved to a site called, Florida in November. When a user selects the Report on "Site by Driver" option and chooses to view results for September, the site column will display as Florida for the driver that was moved as it uses the current site the driver belongs to and not where the driver was assigned to during that time period.
Thus, the site column is in indication of the current grouping of a driver or asset.
The report will then generate and display the information for those drivers and not ones that used to be in the site during the selection period if they have been moved, but note that whether or not the asset or driver's historically accurate site is displayed depends on the report too.
Detailed and Daily reports
These reports have one or many entries per driver/asset per day. This allows to report on the driver/asset site on that day in time. The report will thus show the historically accurate site data and name (if the “Site name” column is displayed). Examples of these reports are the Daily Trip Report, Detailed Event Report and RAG Daily Report. In other words, if you generate a report for September, the site name column will display as Alabama for the driver as explained in the example above.
Summary and Overview reports
If the report is grouped by site or any time period longer than a day, it displays the driver/asset's current site. If the data is aggregated by site, this will include all the drivers/assets currently in that site. If the report does not report on same-day data, the “current site” will be the latest site recorded for the time period the report has data for. Examples of these reports are the Monthly Measured Fuel Report and RAG Summary Report. The site name for the driver in the example above, will then be displayed as Florida for period selection, September even though the driver was in the Alabama site in September because these reports reflect the current grouping of the driver.
If this driver has driven 200 miles whilst belonging to site, Alabama and 200 miles whilst belonging to site, Florida, the 400 miles will be rolled up into one distance under the driver's current site, Florida. Note however, if a user does not have permissions to the one site they will not see the values for say for instance, Florida, but only to Alabama that they have access to.
In MiX Insight Agility a user has the option to select "Current Site" and "Site" where the last filters will also display the historically correct information, which in this case would be the information for the driver in the previous site too.
The security level edge case that was described above will influence the information that is displayed, because if a user does not have permission to the previous site that the driver or asset belonged to, they will not see this information in MiX Insight Agility. Another user with full access will see a different value since the driver or asset will be included in their results.
Edge case - Rounding
MiX Insight Agility does not round values, but displays all the decimals. MiX Insight reports round the values to two decimals.
Edge case - Trips vs. sub-trip logic
Scenario 1 - store trips with the start date of the trip - i.e. the date the ignition was switched on.
Scenario 2 - store trips with the start date of each sub-trip, i.e. each time a vehicle starts moving again after having been stationary for a duration of time. For example, a driver starts the ignition on 15 January 11:58 pm but only starts moving at 12:02 on 16 January. The start date for the sub-trip is when the movement started, thus on 16 January.
For trips that spanned a duration of multiple days (i.e. over midnight) the trips saved for scenario 1 will contain the date the trip started whereas scenario 2 will have the date for each sub-trip's start.
Some reports use logic for scenario 1 (e.g. all the trip reports, while MiX Insight Agility and some of the other relevant report (e.g. Daily Movement report) use information as explained in scenario 2. 
When you build a Insight Agility pivot table with the date-driver dimension to only show data for January 2018, Trip A, sub-trip 1 and Trip B, sub-trip 2 will be excluded from the pivot table as they both start outside of the date-driver range.