Alastri is pleased to announce the release of v21.2
Starting with v21.2, the concept of Early Access has been retired. All users now have access to all versions - for assistance on which version to use, consult this guide: /wiki/spaces/DED/pages/27230462
If you work for a large company, consult your company’s central Alastri contact for when to switch versions.
Upgrading to v21.2 of ATS and APS may require updates to your scripts. Consult your friendly Alastri Support team for assistance - it’s included as part of your subscription.
Improvements
All Products
Production Scheduler
Truck Optimisation
Problem: In version 21.1, we introduced the Truck Dispatch system, which was a significant improvement over the previous trucking system, which mixed instantaneous logic with TUM logic. When using the Truck Dispatch mode, it was highlighted that it was challenging to troubleshoot why the optimiser was doing certain things, i.e., sending material to a stockpile despite the crusher being starved. This was a result of the schedule needing to complete two passes to assign the trucks. Other limitations existed around the period-based digger assignments.
Solution: In version 21.2, trucks have been included as part of the optimisation equation. Agents are now automatically assigned to Agents based on how much revenue each Agent is making. The digger priority table in the calendar has been removed as cash flows dictate how trucks are assigned. More information on the subject can be found here PS Haulage Calculations.
Delay Sequence
Problem: It is common practice to model tramming delays for drills and, in some cases, diggers. The only way to achieve this in APS was to have multiple sequence bars containing one pattern and have delay bars inserted between them. This process is rather inefficient, and users lose the ability to quickly draw their sequence in one go using the sequence painter. If a pattern is delayed during the schedule, all of the delay sequence bars need to be repositioned, which is time-consuming.
Solution: A new Sequence type has been developed called a ‘Delay Sequence’, enabling users to insert delays directly between blocks chosen in the block picker. Users can configure the delays in the XXX found in the Sequence Painter UI or the properties panel of the selected sequence.
The type of delay to be applied can be set by either clicking in the duration box next to the pattern name and selecting the delay from the list or selecting a delay from the drop-down list of the multi-select window. Like the delay type, users can enter the delay duration directly in the duration box or the delay length input located in the multi-select window. Users can also insert delays at the start and end of the sequence by using the two buttons located on the far left of the toolbar.
Please note that ‘Can Skip Tasks’ is not available in the new Delay Sequence. Tramming delays should take into account the distance between the predecessor and successor records. For this reason, it makes no sense to jump ahead as the delay duration may increase or decrease based on the location of the next selected record.
Sequence Reordering
Problem: If a user wants to reorder the blocks in the sequence, the Sequence Painter window would need to be launched for that sequence, and the records reordered. This process can get quite tedious if the order is constantly changing.
Solution: To help speed up the process, we have added the functionality to move blocks around directly in a sequences properties panel. Records can be repositioned using drag-and-drop or via the up and down buttons located in the toolbar.
Code Filters
Problem: Within one parcel, there can be a lot of variability in the grades. When this happens, we sometimes want the destination of the parcel to be dependent on the grades within it. There may be a stockpile that houses HG material that has a SiO2 value of over 4.0, HG material with a SiO2 less than 4.0 goes to another stockpile. Instantaneous grade targets can be used to try and manage this; however, they are not a hard constraint. As long as the average grade going to a destination meets the criteria, it will allow material to be sent there.
Solution: Code filters have been introduced to help enforce hard constraints when mining Agents are selecting a destination. A Code Filter is an additional piece of logic evaluated when Agents select a destination rule to use. Code filters can either be scripted in which is recommended where a large number of code filters need to be written, or they can be created through an inbuilt Code Editor in the Destinations Rules step. More information about Code Filters and how to construct them can be found at the following link https://alastri.atlassian.net/wiki/spaces/212AD/pages/5483987078/PS+Code+Filters.
. For
Flow Optimisation - Minimum Rate
Problem: When the optimiser runs, it is a possibility that a mining Agent will be selected to operate at a rate that is not practical in reality.
Solution: It is now possible to define a minimum rate that a mining Agent can operate at. This option can be enabled in the Final Configuration step, and enabling it will add a row per Agent in the calendar. When enabled, the minimum rate will be included as a binary variable in the optimisation. As it is a binary variable, the optimisation becomes mixed-integer and as a result, can slow the scheduling speed down.
Chrono Data Sources - Production Blasting and Presplit Blasting
Problem: When creating reports, it is not uncommon to wish to include blast data; however, blast data is not an available Data Source inside Chrono Reports.
Solution: The Data Sources within Chrono reports have now been updated to include ProductionBlasting and PresplitBlasting. PreplsitBlasting will only appear if the activity has been enabled within the project.
Custom Wall Activities
Problem: Within APS it was not possible to schedule multiple wall-related activities on a wall section → Scaling → Rock Bolting → Shotcrete
Solution: It is now possible to model up to 10 user-defined wall activities on a section of the wall. To enable this functionality, the “Model Wall Panels” feature must be enabled, as well as enabling the creation of wall panels within the RR project. More information regarding Wall Activities can be found here (Insert Document Link).
Improvement in drill hole visualisation
Problem: When PreplistDrilling and PresplitChargingweres enabled, it wasn't easy to visually distinguish the drilled and blasted states.
Solution: The appearance of presplit holes has been reconfigured to make it easier for users to determine the current state of the activity. Two additional visualization options have also been given to the user in the “Production Mode Features” Step.
Option | Description |
|---|---|
Show Undrilled Holes | If enabled, when preplit drilling begins on a pattern, empty production holes won’t be laid out on the reamaing area. |
Show Blasted Holes | If enabled, once presplit holes have been fired, the blasted holes will remain present on the pattern until blasting of the production holes occur. |
Stockpiles - Force new decision point
Problem: When stockpiles in a mutex set have a build target type, the “Hours between stockpile decision” input could cause loaders to remain on stockpiles that do not align with the new build targets. The result would cause a volatile grade curve for the stockpile build.
Solution: Once the state of the stockpile build changes, override the “Hours between stockpile decision” option and force Agents to make a new decision. This functionality can be enabled in the Stockpile Build Settings.
Period Filter for Animation Export
Problem: When exporting the animation it was not possible to filter the export by period. The whole animation would need to be exported and then filtered in external editing software
Solution: Include a period filter in the Animation export configuration allowing users to specify which periods they want to export the animation for.
Properties Gird available in Destinations tab
Problem: When analysing source blocks in the Destinations tab, it was not possible to review information on the record. Users would need to go and find the block in the Database tab to review information about it.
Solution: Provide the same Properties panel that is present in the Gantt tab. When a record is selected, its data will be shown in the Properties panel eliminating the need to source it elsewhere.
Tactical Scheduler
Extension Data Sources & Parameters
Dependencies
Custom Exports
Spatial Conformetrics
Rapid Reserver
Bench Preconditioning
Infrastructure