- Release Date:
14th April 2026
Summary
Enables an underground‑specific Bulk Action: “Mark Hole as Checked”. This enhancement improves Prep Crew efficiency and productivity by allowing users to quickly mark multiple holes as meeting site prepping standards, reducing the number of interactions required with the BlastIQ™ Mobile device.
Follow these steps to enable the checked hole feature in the BlastIQ™ Mobile.
- Login to the BIQ Admin portal and open your site.
- Click the BlastIQ Mobile Configuration menu.
-
On the BlastIQ Mobile Configuration page, locate and click the "Edit" button.
- Find the "Enable Checked Holes" section in the configuration options and tick the checkbox to enable the feature.
-
Click "Save".
For details on how to use the bulk action, refer to BlastIQ™ Mobile - Underground 'Bulk Action'.
The "Enable checked holes" setting is a vital component of BlastIQ Mobile Configuration, and its behaviour varies depending on whether it's configured at the plant or quarry/site levels via the Admin portal.
Note: Please see this article on How to configure a site that can support multiple customer sites for BlastIQ Mobile using ODS Admin portal
-
Plant-Level Configuration
- Activating "Enable checked holes" at the plant level affects all sites within that plant. In other words, it activates the "Enable checked holes" feature for all sites linked to the plant.
- If you deactivate "Enable checked holes" at the plant level and activate it at the site level, the site-level setting won't override the plant-level setting. This means that the "Bulk Action" button will not be visible in the BlastIQ Mobile interface.
- Configuring "Enable checked holes" at the site level linked to a plant is impossible, as it would affect the login.
-
Site-Level Configuration
- When a site isn't linked to a plant, users can control the 'Enable Stem All' feature. When enabled, the 'Enable checked holes' function is included in bulk action.
-
Recommendation
- It's not advisable to disable "Enable checked holes" at the site level because a site may be accessed directly or through a plant-level setup. It's best to manage this setting at the plant level to ensure consistent behaviour and avoid unexpected issues.