Tables are a database holding a hierarchy of 3D scheduling blocks. In this step we define the levels of the pit and dump trees, and specify which level is the bench/lift level (the truck travel level).
A table marked Holds Dumps has no reserves information and cannot be mined. If an area must be dumped and reclaimed (such as a land bridge), then the blocks must be imported twice (once as dumps, once as reserves).
Every table must specify the Bench Level, which is the running level of the trucks. This is used in the generation of On Bench Dependencies to determine bench access and progression.
"Bench" and "Lift" refer to the truck travel level in the hierarchy. It is used in calculating 2D dependencies. The truck travel level must always be a child to the "Stage"/"Phase" level. If you are using flitches, then the "Bench" and "Bench Level" will map to the flitch elevations, which will be a child of the "Stage"/"Phase".
Tables
Tables should be created for each class of blocks: pits, dumps, and (optionally) backfills. The number of levels in each table should match the level hierarchy of the inventory files, so they can be mapped one-to-one in the Map Fields step.
Tables can be added to the project using the add and remove icons.
Click in the Table Name column field to rename it.
Select “Dumps” from the dropdown if it holds dumps or backfills.
Level Hierarchy
Levels should be set so that general scheduling rules can be applied higher in the tree. This reduces the amount of rework to write duplicate rules for the lower branches.
Levels can be added to a table using the add and remove icons.
Levels can be ordered using the up and down arrows icons.
Click in the Level Name column field to rename it.
The Sort Direction column will determine whether benches are listed top to bottom or bottom to top.
The Bench/Lift Level must be specified at the running level of the trucks.
Naming Conventions
Constraints
The following naming convention makes it hard to control the total tonnes in "Q1" pit, because the stages are not properly nested:
Reserves/Q/Q1_AReserves/Q/Q1_B
Consider adding a new level to the tree instead:
Reserves/Q/Q1/Q101Reserves/Q/Q1/Q102
With this setup, a constraint can be applied to "Q1" pit that automatically limits all nested children.
Filters
When choosing a naming convention, consider the following recommended practice:
Reserves/Q/Q1/Q101Reserves/M/M1/M101
If we filter on stage name "Q101", we immediately know what pit and deposit it belongs to without using any additional filters. This makes reporting a lot easier when the schedule is finished.