The Data exclusion management tool (DEMT) is a module that is used internally to quarantine events and trips that are deemed inaccurate or private.
The module also allows you to reassign trips to different drivers. Note that organizations that are enabled for Hours of Service will only see the events tab.
The new DEMT module will be available to all organizations that have been migrated to Lightning 3B data processing. Organizations that have not been migrated can still use the Data exclusion (legacy) feature on the same menu.
- Click Manage.
- Under Operations, click Data exclusion.
- Choose the relevant organization. You can only go down to organization level and you can only select one organization.
- On this page you will see a list of existing data queries, if relevant.
- Click the refresh button at the top to see the latest list.
- Enter text in the filter bar to search for a query as shown above.
- This page will display the query type (if the query was related to trips or events), the date and time the query was submitted, the user who performed the last action (i.e. if John Smith created it, it will display John Smith but if James Brown performs the quarantine, the username will change accordingly).
Important note: if the user viewing the page (e.g. organization-level user) is lower down in the organization tree than the user who created the query (e.g. RSO user) then the username will not be visible to the organization-level user viewing the page.
- User comments are displayed if they were added to provide a reason for the query. If the comment is longer than the provided space, click on the comment to open a pop up box to view the full comment.
- The date and time the status was recorded is also shown, which will assist users to know when the status changed and how much time they have left to take action if needed. See status descriptions below for the amount of time before a query expires or is removed.
- Various statuses will inform users of the progress of the query. See below for a description of each.
Statuses:
- Retrieving data - if the lookup is still processing (could take up to 72hours).
- Data retrieval failed - Click the red text to see an error code. After 5 days the query will be removed from the grid.
- Ready for review - Click on the green text to navigate to the results page to quarantine events, quarantine trips or reassign trips.
- Query expiring soon - This status is displayed after a query has been in "ready for review" for 10 days. Click the amber text to navigate to the results page to quarantine events, quarantine trips or reassign trips.
If a query has not been actioned in 14 days since it was created, the query will be deleted and removed from the grid.
- Quarantine in progress - will show once the user has selected "Quarantine" on the results page.
- Quarantine successful - once the quarantine is completed and the ETL has been successful. The query will be removed after 5 days.
- Quarantine failed - click the red text to see the error code. The query will be removed after 5 days.
- Reassignment in progress - will show once the user has selected "Reassign" on the Trips results page.
- Reassignment successful - once the reassignment is complete. The query will be removed from the grid after 5 days.
- Reassignment failed - Click the red text to open a pop up with the relevant error code. You can click Yes to retry the reassignment or No to ignore. The query will removed from the grid after 5 days.
Add new data exclusion query
Click here to learn how to create a new query
Permissions: You need the Data Exclusion (Access) permission to access this feature.
Please note
- ETL needs to run before events are successfully removed from reports. This requires using the ETL refresh button and changes should reflect within 12-24 hours.
- You can view a Data exclusion audit report.
- There may be cases where trips and/or events, that are not within your defined date range, are displayed. This is because of the way the lookup is done on multiple sites (org-level or multi-site selection). It is based on minimum and maximum time zone values for the assets and applies that same time zone across all sites when doing the lookup. This is applicable to organizations that have sites in different time zones or if an asset was moved from one site to another.