Add stopes and increase target

In this section, we will proceed with the scenario developed in the previous step. Ensure that this scenario is currently active in MineTwin before moving forward.

We will now focus on adding more stopes, i.e. places from which we extract the ore.

1. Make sure everything is ok with a single stope

Let us simulate our scenario till the end and check the end state of our simulation model. Below is how the MineTwin window will look after finishing the simulation experiment. :

Mining simulator interface showing production graphs, statistics, map, and current operation statuses.

You might need to zoom out of the Production Cumulative Total, t chart in the top right corner to replicate the screenshot above. You can do this by clicking on the chart and scrolling with your mouse.

On the Simulation status view, we can see that 365 days of the mining operations have been simulated:

On the Animation view, we can also see that our stope has been emptied:

Map with overlay window showing stope details: quality 5.00%, density 2.00 t/m³, mine area 1, remaining 0 t.

Indeed, on the Production cumulative total view, we see that we were meeting our target up until July. When the production line went flat:

Graph showing production cumulative total over time with different process stages and a planned target line.

Note: You can click on any chart to show a vertical line with the date, and then all the legend items will show the exact value at the specific point in time

So, we have made sure our only stope is mined till its end in our scenario.

2. Specify other stope locations

Let us now go back to Editor mode and create several stopes using the Stope palette tool. Feel free to create as many as you want:

An animation shows a network map with nodes and lines, where selected paths are highlighted in blue, and directional arrows indicate route changes and updates.

Make sure the direction of the stopes makes sense. Below is an example of a stope direction that will not work as the direction of development goes into the road, and there is no way to access the stope from the starting point of the stope.

Diagram showing interconnected nodes with blue lines and arrows, overlaid with software toolbar for mapping and optimization.

In case it does not, use the Reverse button in the upper part of the Map view.

A section of the map briefly highlights in blue with an overlay displaying \"ROAD-94\" before reverting to its original state.

Now let us review the stopes we have just created in the Stopes table view:

A table lists stopes, showing identifiers, names, advancement type, quality percentages, and status, with one selected row.

Now we have created our stopes and corresponding mine segments, but we have not defined any properties for these stopes (i.e. material mix, mining method, etc.). We can now click the Check button and see how MineTwin points us to these multiple missing properties:

Error list showing 65 issues, including missing values and path errors, under the "Stopes" category.

MineTwin provides a stope properties copying tool similar to the "Format painter" tool of Microsoft Office applications.

To do this, you can right-click on the block with the properties you want to copy and select Create stope pattern from the context menu. You can then select the new block where you want to paste the first block’s characteristics by right-clicking and selecting Apply stope pattern from the context menus.

On Windows, the block copying tool can be activated by clicking the stope pattern button in the upper part of the stopes table view. Let us now activate this tool and apply the properties of our first block to all other blocks by Ctrl-clicking the lines in the stopes table.

The animation shows rows in a table being sequentially updated, changing the "Advancement type" to "Excavation" and the "Quality, %" to "5.00" across all entries.

We can now click the Check button once again to make sure all the errors are gone.

If we now go to the simulation mode and run our scenario again, we will see that we are perfectly meeting our target:

Cumulative production graph with stages: bolting, drilling, mined, charged, blasted, haulage, and plan metrics over time.

3. Adjust simulation period and production target

Let us now go back to the Editor mode and do the 2 final adjustments before going into the scenario analysis mode.

Firstly, let us shorten the simulated period to just 3 months:

"Training Scenario" properties panel with tabs: General, Scheduling, Advanced, Expenses. Inputs for name, dates, simulate fueling.

Secondly, let us adjust the end date of our target accordingly and increase the production target to 50Kt per 3 months (200Kt per annum):

A table displays plans with columns: Begin date, End date, Mining type, Quality (%), and Planned mass (t).

Note: The format of the date is dependent on your local machine settings and might look different compared to the screenshot above.

Let us now save the scenario and rerun the simulation. Note how we are now falling 64% behind our target in our 90-days scenario:

Dashboard showing shift details, production plan, fulfillment percentages, road length, stope status, and equipment usage.

Here is the scenario that must be the result of this training.