Create a scenario from scratch

1. Use new scenario wizard

In this section, we start building a new MineTwin OpenPit scenario from scratch using the scenario wizard. We will walk through the initial configuration together and show how the general scenario settings, ore types, and shift calendar are defined before any geometry, equipment, or production logic is added.

These initial settings create the foundation for the rest of the guided training, where we will gradually turn an empty scenario into a working simulation model.

A user interacts with a scenario editor interface, opening and filling out a "New Scenario" settings window.

We begin by opening the new scenario wizard. This wizard guides us through the required setup steps and helps ensure that the scenario has the minimum configuration needed before we continue with modeling.

New Scenario settings: Identifier, dates, scheduling mode, and options for trucks with tolerances, costs, and map settings.

Here we define the general scenario settings: the scenario name and the planning method. These settings identify the scenario and determine how we will approach planning before we continue with the rest of the model setup.

"New Scenario" window, step 2 of 7, listing mine areas with navigation and action buttons.

At this step, we add a single mine area to the scenario. In MineTwin OpenPit, a mine area is used to logically group adjacent mining blocks and can later help organize where specific equipment or transport units operate.

Ore types setup dialog with "Iron ore" and "Overburden" entries, featuring mining type options.

We configure two ore types: iron ore and overburden. MineTwin uses ore types during scheduling and to determine where material from blocks can be hauled, so this step prepares the scenario for later block setup and material flow configuration.

A user interacts with a software interface to create and specify shifts, adjusting parameters such as the number of shifts, shift change duration, and start time before confirming with OK.

Finally, we configure two shifts for the scenario calendar. Shifts define the periods when mobile equipment is available for operation, and this schedule will be used later during planning, simulation, and result analysis.

2. Draw simple geometry and add text labels

In this section, we will create a simple schematic layout for the scenario. We will add text labels, draw the main road line with mine nodes and arcs, check the scenario for configuration issues, and add the first material destination object.

We will also prepare the geometry for later simulation by setting elevation values, reviewing the model in 3D, and adjusting virtual arc lengths. At the end of this section, we will run an empty simulation to confirm that the base scenario can be executed before we add excavation blocks and equipment.

The animation shows a series of interface transitions where labels and properties on a map are edited and replaced, including changes from detailed settings to simpler text descriptions.

We start by adding a text label with the scenario title. This label helps make the model easier to read during the guided demonstration and gives the scenario canvas a clear visual reference.

A text label saying "Simple scenario" is added to a grid, followed by a straight line with nodes, and additional text labels labeled "Text" are added along the line.

Next, we draw a simplified road geometry for the training scenario and place labels for the main areas. The layout represents the future excavation block, the in-pit road, and the off-pit road as a simple connected network of mine nodes and arcs.

Interface with toolbar, displaying a simple map layout with labels for excavation block, in-pit road, and off-pit road.

We then update the labels shown on the map for the Excavation block, In-pit road, and Off-pit road. These labels make the simplified layout easier to read during the next configuration steps.

Scenario editor interface with tree structure, error and warning messages displayed below.

After creating the initial geometry, we check the scenario for errors. At this stage, MineTwin reports that the dump area list is still empty and shows a warning that the scenario uses the By target planning mode but has no target records yet. We will address these items in the following steps by adding a dump area and then defining the production target later in the training.

The animation depicts a cursor selecting a point along a linear path labeled "Excavation block," "In-pit road," and "Off-pit road," followed by the display of detailed information about a "Dump area 1" on the right side of the interface.

We add a dump area at the end of the road network and name it Crushing site. In MineTwin OpenPit, dump areas act as haulage destinations for material from blocks, so this step prepares the scenario for material movement once excavation blocks and equipment are configured.

Diagram showing an off-pit road with a node, labeled "Mine node 3," leading to a crushing site. Node coordinates: X 657.20, Y -185.80, Z 200.00.

At this step, we set elevation values for the mine nodes. The screenshot shows the Z coordinate being edited for a mine node. MineTwin uses these node elevation values to calculate road grades for the connected arcs.

3D map showing excavation block, in-pit and off-pit roads, leading to a crushing site with zoom and navigation controls.

We review the scenario in the 3D view to confirm that the road profile, labels, and Crushing site are displayed as expected. This visual check helps us verify that the node elevations created the intended vertical profile before simulation objects are added.

Diagram displaying a mining scenario with excavation block, in-pit and off-pit roads, and properties table for "Mine arc 2".

We set custom virtual lengths for the road arcs, including a 2,500 m in-pit road section and a 500 m off-pit road section. This allows the simplified schematic geometry to represent realistic haulage distances without drawing every road segment at full scale.

Simulation interface showing current production status, map visualization, and summary statistics in mining software.

Finally, we run the scenario without excavation blocks or equipment. The simulation view shows the basic road network and one dump area, while production and development values remain zero. This confirms that the base scenario can run and is ready for the next stage of the training.

3. Add excavation block, ore, and set target

In this section, we will turn the schematic road layout into the first mineable part of the scenario. We will create a mine segment, add a block that corresponds to this segment, and define the block properties needed for planning and simulation.

We will also configure the block advancement logic, material mix, scenario duration, and target plan. By the end of this section, MineTwin will know where material can be mined from, what material is inside the block, and what production target we want to reach during the planning period.

The animation depicts a software interface in which a simple scenario map is zoomed in on, focusing on the "Excavation block" section of a mine arc, with the properties of "Mine arc 1" displayed in the side panel.

We start by creating a mine segment on the road network and setting its direction. The mine segment represents the location on the plan where the future block will be mined, so its position and direction define how the block is connected to the haulage layout.

A line in a mining software interface changes color from green to blue, and corresponding property details appear in a side panel.

Next, we add a block and associate it with the mine segment. In MineTwin OpenPit, a block is the place where equipment performs mining operations, and on the mine plan it corresponds to a mine segment.

UI showing block advancement properties: length, wells count, width, thickness, drilling machines, ore mass, and length with ore.

We configure the block advancement type as Block and set the initial state to Haulage. In this training scenario, the block already contains ore mass ready to be hauled, so we specify the ore mass to haul and the length of the block where this ore is located.

A dialog box is opened showing a composition of materials being adjusted, and then closed to update the material mix in the properties panel.

We fill in the block material mix. This step is required because MineTwin uses the material composition to calculate the block quality; the material fractions must add up to 100% before the block can be used correctly in planning and simulation.

Properties window showing scenario identifier, begin and end dates, and options for stopping when no ore, refueling, and recharging.

We adjust the scenario end date so the planning period lasts one week, from January 1, 2026 to January 8, 2026. This gives the model a clear time horizon for the first target-based planning run.

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

Finally, we add a target plan record for the same one-week period. The target specifies Production mining type, 10% quality, and 500,000 t of planned mass, which tells MineTwin what production result we want the scenario to achieve.

4. Add trucks, excavators, and run simulation

In this section, we will complete the minimum working configuration for the scenario by adding mobile equipment. We will first define the equipment types, then create actual truck and excavator units that can be used by the simulation.

After the equipment is added, we will run the first working simulation. This lets us confirm that the block, material destination, road network, target plan, and equipment are connected well enough for MineTwin to execute the mining and haulage process.

The animation shows a software interface where different truck types and their specifications are being managed and selected from a library for a mining scenario.

We start by adding a truck type from the MineTwin truck models library. In this example, we use the Komatsu HD785-8 Tier 4 Final model. Its parameters are populated from the library, but they can still be edited in the scenario, including payload capacity, body volume, dumping duration, and loaded and empty travel speeds.

Interface displaying excavator type details: speed, shovel capacity, cycle duration, and setup time in a tabbed format.

Next, we add an excavator type for the loading operation. The screenshot shows the Komatsu PC2000-11 Tier 4 Final model. Its parameters are also populated from the library and can be adjusted if needed, including shovel capacity and loading cycle duration.

A truck is added and configured in a mining simulation software, with its settings updated, including truck type selection.

We create a truck unit based on the selected truck type and assign it to a base node. The base node defines the truck’s initial position at the start of the simulation.

Interface showing excavator settings: Identifier, Excavator type, Active mine node, shovel capacity, and cycle duration.

We create an excavator unit based on the selected excavator type and assign it to a base node as its initial position. The excavator task type is set to Block excavating, which means this excavator will load ore from the excavation block rather than perform dump area load-out.

The animation shows a simulation of mining operations over a week, illustrating changes in production metrics, equipment status, and haulage distances, accompanied by data charts and statistics updates.

Finally, we run the first working simulation. As the simulation starts, MineTwin opens the simulation view and shows callouts for the excavator and truck on the map. The excavator goes through setup and load-out states, while the truck cycles through loading, moving to unloading, unloading, and returning for the next load. During the run, the status panel, daily volumes table, production cumulative chart, haulage distance chart, and truck Gantt chart are updated. By the end of the one-week period, the scenario has mined and hauled material, but the production result is still below the 500,000 t target, giving us a baseline for later analysis and improvement.