Define stopes

In this section, we will use the scenario we created in the previous step. Make sure you have this scenario open in MineTwin before continuing. This scenario has basic master data, a layout imported from an external file, and equipment types.

In this section, we will create a single stope for our simple drill-and-blast method.

1. Define advancement rules

Before adding stopes, we need to define the rule of how our stopes will be advanced through. In MineTwin, this can be done by adding advancement rules, or excavation rules as they are called in MineTwin’s UI. To add an excavation rule:

  • Click on Excavation rules item in the scenario tree that is found under the Ore section.

  • Navigate to the list of Excavation rules in the bottom center part of the screen

  • Click + button to add an excavation rule

The animation shows navigating a mining software interface, where an excavation rule is added and configured, with details entered into the properties panel.

As a result, an excavation rule with the default name of "Excavation rule 1" will be created. Let’s change its properties to the following values, as shown below:

UI displaying excavation rule parameters: identifier, drilling depth, advancing fraction, roofbolting, scaling probability, bolts, wells.

Now, we have defined the excavation rule that we’ll be using for all stopes of our sample scenario.

2. Set locations of stopes

Stopes are the places where the extraction of ore happens. In MineTwin, all stopes must be connected with the mine’s transportation network. More specifically, each stope must fully or partially occupy one or several arcs. These arcs occupied by a stope must be consecutive, i.e. they must follow each other in the network. In MineTwin, such a list of consecutive arcs is called a mine segment.

There are the following relationships between mine arcs, mine segments and stopes:

  • Mine arcs are a part of the mine transportation network. Every mine arc begins and ends in a mine node. Mine arcs with zero length are not allowed

  • Mine segment is just one or several consecutive mine arcs.

  • Stope can occupy the whole mine segment or a part of it. In the latter case, the begin and end offsets of the stope inside the mine segment must be specified

In this tutorial, we will only be using a simple setup where 1 stope = 1 mine segment = 1 mine arc. To create such stopes, there is a Stope tool in the palette. Click this tool and click one of the arcs to create a stope as shown below:

The animation shows a zoom-in on a complex network of connected lines and nodes, followed by the addition of a new blue line segment connecting two nodes.

Note that, as a result, a mine segment has also been created.

3. Set ore grades, densities, and fragmentation rates in stopes

Now that we have defined the location of our only stope, it is time to set up the properties of the material in this stope. Let us select the Stopes item in the scenario tree, select our only stope, and set the following values in its General properties section:

  • Set density of the ore to 2 tons per cubic meter

  • Set fragmentation rate to 1.1. The fragmentation rate is the coefficient that sets how the density decreases after the rock is blasted

  • Set the ore type to "Ore", that is, not waste rock. So, our stope is a production stope

Click the “set maximum length” button on the right of the *End offset property to get the value. Remember that the stope covers the entire arc length

The picture below shows the general properties view of our stope:

Properties window for "Stope 1" with fields including Identifier, Name, Offsets, Density, and Ore type. Options for selections.

Now we can go to the Advancement type section of the stope’s properties and specify the simplest possible advancement type called Excavation:

Dropdown menu under "Advancement type" lists options: Not set, Excavation, Cleaning, Composite, Backfill, Continuous.

Next, let us set the width and height of the stope’s face and link our stope with the advancement type we defined earlier in this section:

Properties window for Stope 1 with excavation parameters, advancement rules, and measurement fields.

Note how the excavation parameters of the excavation type are shown at the bottom of the section.

The last thing that we will define for our stope is its grade. In MineTwin, grade is represented with the mixture of materials, some being useful substances and some just empty rock. This mixture of materials can be set in the Material mix section of the stope properties. Let us set the 5% grade for our stope. 5% grade will be 5% of Copper material and 95% of Empty rock material. Remember that we have defined these materials at the very first step of this tutorial. This setup can be done as shown below:

In the animation, a user opens a properties window, modifies the composition of materials by entering new percentage values for copper and empty rock, and confirms the changes, which are then displayed in the properties panel.

Please note that you can use the % button to calculate the last entry of the mix so that the sum of the entries adds up to 100%

4. Review and check stopes

Let us now review the stope that we have just set up. In the scenario tree, select the Stopes item and double-click on the only line in the Stopes table. MineTwin will navigate the map to this stope and highlight it with red color, as shown below:

Network graph with blue nodes and black lines; red line highlights a path. Stope 1 details displayed in properties pane.

You can always hit the Esc button to deactivate any highlighting in the Map view.

Now, our scenario has become complex enough to check it for potential consistency errors and warnings. To do so, hit the Check button on top of the scenario tree:

Interface showing scenario editor toolbar with options: Check, Simulate, Compare, Fleet sizing, Find constraints.

The result of this check will appear in the Errors window in the bottom left part of the application. See how our scenario has 3 errors and 3 warnings:

Error and warning list showing 3 errors and 3 warnings related to scenarios and stopes in scheduling mode.

Let us go through these errors and warnings one by one:

  • The first error is one of two errors found in the scenario. It says that something might be wrong with the scheduling mode. We can skip this for now and return to it at later stages of our scenario setup.

  • The second one says that no ore passes are defined in our scenario. This is an error because MineTwin needs some transportation destinations for ore taken out of the stopes. Ore passes would be the most typical such destination. We will define an ore pass in the next step of this tutorial.

  • The third error says that no path is found from our stope to any ore pass. This is an obvious consequence of the previous error.

  • All three of our warnings tell us that our stope requires some activity, for example, roof bolting, and there are no roof bolters defined in our scenario so far. Let us address these issues in one of the next steps of our tutorial.

This consistency checking functionality is especially useful in the later stages of the scenario setup. It guides the users by hinting what else must be set up to complete the scenario creation.

So, we have set up a stope for our simulation and defined what the characteristics of the stope should be. Now, we can click the Save menu button or hit Ctrl+S to save our intermediate results. You can always download the scenario file that we got so far and continue working with this tutorial later.