- Version 6.13.1 of SHOTPlus™ Production, first offered to users on Thursday 16th March 2023.
- A notification will appear on start-up in SHOTPlus™ Production once the update is available.
- For further information on updating the SHOTPlus™, please contact the BlastIQ™ Support Team via support.blastiq.com.
This notification is relevant to upcoming changes in SHOTPlus™. The changes will take place in these future releases:
- SHOTPlus™ Beta version 6.14.1
- SHOTPlus™ Production version 6.14.1
SHOTPlus™ has recently undergone a refactor of it’s blasthole data structure. This work was undertaken to improve integration between SHOTPlus™ and BlastIQ™ and better align the information presented to users when comparing blast design information and blast outcomes within the BlastIQ™ ecosystem.
As a part of the refactor a number of changes have been made to clarify and standardise terminology used when importing and exporting data into and out of SHOTPlus™ via text file or from BlastIQ™. These changes include:
- Removal of ‘Actual’ terminology - ‘Actual’ was previously a mixed terminology used to define data that was sourced from a drill e.g. ‘Actual Collar X’, or was captured through a field measurement e.g. ‘Actual Length'.
- Standardisation of ‘Drilled’ - All data that has been recorded by a drilling system will now be defined as ‘Drill Data’, e.g. Drilled Length, Drilled Diameter, and Drilled Coordinates. Data imported into SHOTPlus™, via text import as Drill Data, will be exported to BlastIQ™ as having been recorded by a drilling system.
- Standardisation of ‘Measurements' - All data that has been recorded by a physical measurement will now be defined as ‘Measured’, e.g. Measured Length, and Measured Diameter. Data imported into SHOTPlus™ via text import as a Measurement will be exported to BlastIQ™ as having been recorded by a field device.
- Introduction of ‘Surveyed Collar’ - Surveyed collar has been added to the text importer for users who wish to import collar coordinates recorded by a GNSS device, but do not wish to have this data tagged as ‘Drilled’. This data does not integrate with BlastIQ™.
- Introduction of Adjusted Design Length - Where users are importing Drilled or Surveyed Collars, the Adjusted Design Length is the updated length required to reach the target toe position from the new collar position.
Due to the above changes compatibility of files generated or saved in newer versions of SHOTPlus™ may be impacted. What does this mean for you:
Existing files, saved in previous versions of SHOTPlus™, will still open in newer versions of SHOTPlus™. Existing files, saved in the newer versions of SHOTPlus™, will no longer be compatible with older versions of SHOTPlus™.
Existing Text Import and Text Export Templates using superseded terminology for data fields will link to data fields with new terminology on first use. Due to the above compatibility issues it is recommended that updates of for SHOTPlus are completed ASAP for all users.
- Ability to export profile data that exists in holes1.
- Ability to use a polygon to filter triangulation results based on view direction2
- It is now possible to export hole profile data if it exists. To access, go to File > Export > Profile Logs... The option is disabled if there is no profile data against any hole.
- In the Surface Manager, if a polygon is also selected, this can be used to filter output triangulation results. The filter logic can either be in plan (top down), or in the current view direction to filter.
- It is now possible to discard hole profile logs when multiple holes are selected.
- Increased the "Screening parameter" to accept 2 decimal places in the MSW calculation dialog.
- References to BlastIQ™ Classic or BlastIQ™ Quarry have been removed.
- The "Quantities by Hole Type" quantities report has been improved:
- "Boosters" and "Initiating Systems" categories have been added.
- "Stemming" product summary now reports the number of holes and a volume in m3.
- The Surface Manager tool has been improved:
- An information tool tip has been added to explain the "Use as Boundary" option.
- An information tool tip has been added to explain when to use "Best Fit".
- "Use as Boundary" has been disabled if "Best Fit" triangulation is used1.
- When a polygon has been selected, it can be used to filter points for triangulation in the users current view2.
- The "Edit Raw Data" button has been re-enabled in the face station.
- The "Use Actual Holes Loading For Calculation" checkbox has removed and replaced with the ability to submit AVM™ predictions for Vibration and Airblast based on the following loading states3:
- Design - Prediction based on design charging and initiation information.
- Updated Design - Prediction based on Updated Design charging and initiation information where present.4
- Actual and Design - Prediction based on Actual charging and initiation information.5,6
- Filter and search option 'Incomplete Actuals' has been added to allow users to search for holes that do not have the required information to be submitted as an 'Actual'.
- Added menu option to clear profile logging from multiple holes.7
- "Best Fit" triangulation method should not be used with a polygon selected for "Use as Boundary", this could have led to undesirable results.
- In the Surface Manager, users can create a surface with selected objects. If a polygon is also selected, this can be used to filter the input data used in the triangulation. The filter logic can either be in plan (top down), or in the current view direction to filter.
- Loading state is selecting via a dialog when submitting a blast for prediction.
- Where a hole submitted does not have an Updated Design, the design will be used instead.
- Where a hole summitted does not have the required 'Actual' information the Updated Design (first preference) or Design (second preference) will be used.
- The 'Actual' information required to submit an AVM™ job based on actuals is:
- Actual Charge Weight for all recorded decks in a hole;
- Surface initiation; and
- Actual Initiation Time for all recorded decks in a hole. Actual initiation times can be sourced from BlastIQ™ for pyrotechnic initiators, or i-kon™ Loggers for i-kon™ initiators.
- Tools > Holes > Clear Profile Logging.
- Sometimes the selection lasso can appear far from the extent of the data on screen. This has been fixed.
- The "Expand Polygon" tool can sometimes cause overlapping points in the result. Where logical, this has been improved.
- When importing design holes via the text importer, a message prompt alerts the user if incomplete design information is available. This message was appearing even if appropriate fields are mapped for import, this has been fixed.
- When using surface and downhole combo detonators, the tie legend display was not printing correctly in the plan print out.
- When attempting to upload plans to BlastIQ™, if an i-kon™ resource exists in the upload that had a mismatched product region, an error would occur. This has been fixed.
- After importing hole positions from BlastIQ™, toe points for some situations did not match.
- Borders were not being printed when attempting to print a report on all rows in the "Row View".
- The "Butt Check" tool was misidentifying holes even when outside search radius.
- Hole Labels were not showing on opaque rendered surfaces.
- Time Envelope View was not scaling correctly when initiation times were adjusted with Time Window open.
- AVM™ Modelling domain needed to be selected after each import from BlastIQ™.
- Renaming a hole in SHOTPlus™ using the hole renaming tool was not renaming the hole correctly in BlastIQ™.
- The loading tool was incorrectly applying a loading design to holes marked as 'Not Drilled' in certain situations.
- Actual decks recorded in BlastIQ™ were being displayed incorrectly in certain circumstances.
- An unhandled exception was occurring when viewing 'Actual' charge information where holes had a recorded booster only.
- Inputting a delay for a surface EBS connection, when SHOTPlus™ was displaying imperial units, was resulting in the incorrect time being added.
- Unhandled exception was occurring when exporting a profile log and an exported profile log file was already open.
- Generating a custom report from the Profile Wizard was causing an unhandled exception.
- Profile Logging Tool was incorrectly showing erroneous data points.
- Negative profile values were not being shown in the Profile Logging Tool.
- Generating a surface with 'Include in Surface' option selected was generating an unhandled exception in certain circumstances.
- Importing logged detonators from an i-kon™ logger was not correctly populating the 'Actual' loading for a hole.
- Grade RL input in "Edit Hole" was incorrectly handled when using Imperial display units.
- When printing the "Row View " report, sometimes an unhandled error would occur.