DigTix v2.32 Release Notes (Risk Score Seeding, Recommended Close Codes, Follow Up Creation Improvements, BI Suite Data, and More!)
Posted
8 months ago
by John Gayness
J
John GaynessAdmin
RISK SCORE SEEDING
It is now possible to import some of your most valuable damage prevention data into DigTix: historical damage rates. If your organization was keeping track of this data manually or in another system prior to using DigTix, it is possible to input this information into your system for the purposes of quantifying past performance and managing risk.
Simply navigate to the "Excavators" page or the "Users" or "Contract Locator Registry" sections of the Administration page and you'll see two new fields:
Pre-DigTix Locate Requests: The number of locate requests completed prior to using DigTix.
Pre-DigTix At Fault Incidents: The number of at-fault incidents prior to using DigTix.
Specifying these numbers for an excavator, user, or contract locator will instruct DigTix to consider them when calculating risk scores. This allows your organization to consider years or even decades worth of your most critical damage prevention data.
Locate requests now provide a list of all follow ups which have been triggered for that locate request. This includes information such as the current status of the follow up, who it is assigned to, when it is scheduled to start, the time of completion, notes, and more.
Locators can create follow ups via the "Create Follow Up for Locate Request" button which shows a drop down of all the available follow up types.
These improvements provide more insight into the damage prevention efforts for each excavation job - because damage prevention does not stop after the locate request is completed.
Figure 3: Improved Locate Request Follow Up Creation Process
MORE BI SUITE DATA
Three new data sets have been added to DigTix's Enterprise BI Suite:
qs_Excavators: This data set can be used to build visuals relating to the excavators which are calling in locate requests and their associated data such as risk scores, damage ratios, and more.
qs_Locate_Assignment_Events: This data set includes every time a locate request is assigned from one user to another. It provides insight into dispatching productivity and the internal passing of locate requests from one user to another.
qs_Locate_Close_Code_Events: This data set includes every time a close code is applied to a locate request. It provides insight into utility locating productivity, workflows, and the update of locate requests from one close code to another.
Figure 4: Excavator BI Dashboard (NOTE: Data is Simulated)
RECOMMENDED CLOSE CODES
When creating a new call center CDC, DigTix now provides the option to automatically configure recommended close codes. These recommended close codes are based upon the positive response options of the call center for which that CDC belongs to. This can be used to ensure compliance with that call center's positive response requirements.
In the screenshot below, the "Include Recommended Close Codes" box is checked. This will trigger DigTix to create not only the CDC, but also the recommended close codes for the selected One Call Center "Dig Safely NY".
Figure 5: Automatic Configuration of Recommended Call Center Close Codes
Note that the recommended close codes may be modified at any time to support your organization's workflows. The recommended close codes are simply created as a starting point for your organization.
DIRT INCIDENT VALIDATION AND SUBMISSION
DigTix can now be configured to automatically validate your incident data by the CGA's DIRT standards and submit it to DIRT upon completion. Within the "Incident Statuses" section of the Administration page, a new "Submit to DIRT" configuration option has been added. When checked, updating an incident to that status will trigger DigTix to automatically validate and submit the incident data to the DIRT system.
Figure 6: Configuration of "Submit to DIRT" Incident Statuses.
If the incident is unable to pass DIRT validation, the application of the Incident Status will fail and the DIRT invalidation information will be displayed so the incident can be corrected.
Figure 7: DIRT Validation Message.
By default, incidents which are submitted to DIRT through DigTix are submitted using DigTix's DIRT credentials. If you would like DigTix to submit incidents to DIRT using your organization's DIRT credentials, please contact our support team.
MANUAL POSITIVE RESPONSE EMAILS
Within the "Actions" tab of the locate request window, a new "Send Positive Response Email" button has been added. This button will allow you to specify one or more email addresses to send the positive response email to.
Note that this does not affect the automatic sending of the positive response email to the excavator upon the completion of the locate request within DigTix. Rather, this is a separate method to distribute the positive response email on an as-needed basis.
Figure 8: Manual Sending of Positive Response Email.
MISCELLANEOUS
This DigTix release contains a considerable amount of "under the hood" improvements which provide the foundation for many exciting, upcoming features and improvements.
Switching and feedback submission structure for the upcoming new user interface.
Improved logging and trace information for debugging and monitoring.
Added more descriptive error messages for attachment files with unsupported types (.exe, .dmg, etc). For a full list of unsupported attachment file types, see File Attachments and the File Upload Manager.
Improved satellite base layer imagery. For more information, click here.
Better resilience for data record race conditions.
RISK SCORE SEEDING
It is now possible to import some of your most valuable damage prevention data into DigTix: historical damage rates. If your organization was keeping track of this data manually or in another system prior to using DigTix, it is possible to input this information into your system for the purposes of quantifying past performance and managing risk.
Simply navigate to the "Excavators" page or the "Users" or "Contract Locator Registry" sections of the Administration page and you'll see two new fields:
Specifying these numbers for an excavator, user, or contract locator will instruct DigTix to consider them when calculating risk scores. This allows your organization to consider years or even decades worth of your most critical damage prevention data.
Figure 1: Specifying Pre-DigTix Excavation Performance
Figure 2: Specifying Pre-DigTix Locator Performance
FOLLOW UP CREATION IMPROVEMENTS
Locate requests now provide a list of all follow ups which have been triggered for that locate request. This includes information such as the current status of the follow up, who it is assigned to, when it is scheduled to start, the time of completion, notes, and more.
Locators can create follow ups via the "Create Follow Up for Locate Request" button which shows a drop down of all the available follow up types.
These improvements provide more insight into the damage prevention efforts for each excavation job - because damage prevention does not stop after the locate request is completed.
Figure 3: Improved Locate Request Follow Up Creation Process
MORE BI SUITE DATA
Three new data sets have been added to DigTix's Enterprise BI Suite:
Figure 4: Excavator BI Dashboard (NOTE: Data is Simulated)
RECOMMENDED CLOSE CODES
When creating a new call center CDC, DigTix now provides the option to automatically configure recommended close codes. These recommended close codes are based upon the positive response options of the call center for which that CDC belongs to. This can be used to ensure compliance with that call center's positive response requirements.
In the screenshot below, the "Include Recommended Close Codes" box is checked. This will trigger DigTix to create not only the CDC, but also the recommended close codes for the selected One Call Center "Dig Safely NY".
Figure 5: Automatic Configuration of Recommended Call Center Close Codes
Note that the recommended close codes may be modified at any time to support your organization's workflows. The recommended close codes are simply created as a starting point for your organization.
DIRT INCIDENT VALIDATION AND SUBMISSION
DigTix can now be configured to automatically validate your incident data by the CGA's DIRT standards and submit it to DIRT upon completion. Within the "Incident Statuses" section of the Administration page, a new "Submit to DIRT" configuration option has been added. When checked, updating an incident to that status will trigger DigTix to automatically validate and submit the incident data to the DIRT system.
Figure 6: Configuration of "Submit to DIRT" Incident Statuses.
If the incident is unable to pass DIRT validation, the application of the Incident Status will fail and the DIRT invalidation information will be displayed so the incident can be corrected.
Figure 7: DIRT Validation Message.
By default, incidents which are submitted to DIRT through DigTix are submitted using DigTix's DIRT credentials. If you would like DigTix to submit incidents to DIRT using your organization's DIRT credentials, please contact our support team.
MANUAL POSITIVE RESPONSE EMAILS
Within the "Actions" tab of the locate request window, a new "Send Positive Response Email" button has been added. This button will allow you to specify one or more email addresses to send the positive response email to.
Note that this does not affect the automatic sending of the positive response email to the excavator upon the completion of the locate request within DigTix. Rather, this is a separate method to distribute the positive response email on an as-needed basis.
Figure 8: Manual Sending of Positive Response Email.
MISCELLANEOUS
This DigTix release contains a considerable amount of "under the hood" improvements which provide the foundation for many exciting, upcoming features and improvements.
0 Votes
0 Comments
Login or Sign up to post a comment