All parameters simultaneously handled,delivering multiple scenarios

Vertical Rate

Estimated reading: 4 minutes 1713 views


The vertical rate of advance (VR) or sinking rate is also considered within the objective function on MiningMath. This parameter is defined as the vertical distance mined on each period. The total vertical distance mined across all periods should be consistent with the pit depth and equipment available. In cases of unfeasibility it will respect the constraints hierarchy in which it is placed at a lower priority.

Bottom width, mining width and vertical rate of advance.

How to calculate it

The vertical rate of advance is defined as the vertical distance, in meters, mined in each period, and it is calculated by evaluating each mining face independently, as shown in this figure.

Complexity and recommendations

It is important to understand that this is also a 3-dimensional non-linear model, which means that it is a complex parameter within the optimization. The VR works as an upper bound to avoid operationally unfeasible solutions. Therefore, testing different values is a great strategy to identify opportunities that could bring the best mining sequence and NPV.

The Mining Width (MW) is not mandatory when using VR, but it plays an important role when defining its value. The MW and VR, together, define volumes of material for each mining period. A reduced MW might create additional challenges for the algorithm to comply with the VR. Therefore, it is important to play with different values, especially when VR is not being fully respected. 

Vertical Rate: Definition, Hierarchy of Constraints & Complexity

Example evaluation

To evaluate different values for the VR constraint, you can use Decision Trees. The figures below depict a base case for VR evaluation using the Marvin dataset and a respective decision tree built with different VR values.

Notice the fluctuation in NPV illustrated below, influenced by this singular parameter. Additionally, take note that smallest values like 30m (equivalent to block height) and 60m trigger warning violations in the generated report file. This indicates that MiningMath’s algorithm had to adapt the VR constraint for a viable solution to be achieved, keeping other indicators, such as tonnage, within limits. You can see more on the next section on how to prioritize the VR constraint in case adjustments like that are necessary to achieve feasible solutions.

NPV achieved with the Marvin dataset for different values of Vertical Rate. (*) 30m and 60m constraints were not respected in all periods and generated warnings in the report file.

The vertical rate of advance is one of the first constraints to be relaxed within MiningMath’s Hierarchy of Constraints (read more). To ensure VR is at least closer to what you need, relax low-priority constraints manually. This way you will lead the algorithm to a more flexible scenario and a broader solution space, which may help it to find a feasible solution for the new set of constraints.

Besides, if the user aims to force a maximum vertical rate for a given period, it can be created a flat surface constraint regarding the achievable depth and input it as a Restrict Mining. Beyond that is important to notice that even the goal of achieving “process full” could result in a non-feasible solution while the VR is still respected, therefore, this feature is very sensitive to any other parameter.

Vertical rates controlled by surface constraints

In summary, it is crucial to assess various parameter values to gain a deeper understanding of how they can impact your project, particularly concerning geometric constraints. You can explore additional workflows presented here that can assist you in achieving better results.

Share this Doc

Vertical Rate

Or copy link

Chat Icon

Hi, it's Mima here 😇 Ask me any questions!