Dependencies: When and Where?

With a growing number of Dependency types available in the application, and with plenty of functionality overlap between them, it can be difficult to determine which Dependency works best for a certain task.

To start with, think about the type of interaction you are expecting and turn it into a sentence. The following examples are common use cases for most sub-level stoping models.

Process Order

When to use: When you want to have a hierarchy order in your processes. For example, it is common to create a process order for stoping activities. In most cases, we always do production drilling before bogging and we conduct bogging before filling. Therefore, a process order would be the most straightforward method to follow this sequence for every stope.

When NOT to use: to create dependencies between multiple solids.

Offset

When to use: When there is a clear ascending or descending dependency based on the level structure. For example, the cut sequence in development tunnels or the undercut mining direction in a block cave.

When NOT to use: When the rule is field attribute based.

Field Offset

When to use: When we want to create systematic ascending or descending dependencies between solids, based on field attributes. Common examples: Include retreating stopes in bench mining, or doing top-down/bottom-up sequences for sub-level stoping, or doing a primary/secondary sequence for transverse mining.

When NOT to use: When creating dependencies that are not based on clear systematic rules.

Range

When to use: When you want a specific dependency rule to apply to only certain activities or mining areas.

When NOT to use: When the user wants a global rule to apply to the whole model.

Chain Offset

When to use: when we want to do any type of manual dependencies between solids. Common cases include stope sequences that don’t follow a repeatable methodology or to connect ad-hoc activities. Chain offset is more common in the shorter-term planning space, when the engineer needs to be reactive to the dynamic environment.

When NOT to use: when there is a clear systematic approach that could be solved through an automatic rule.

Geometric

When to use: When we want create a spatial rule to connect different solids. Common cases include the last cut of an ore-drive or cross-cut to the first stope in the sequence. Another case is ensuring the last cut of a stockpile is complete before proceeding the decline. Note that geometric dependencies can likely create circular-reference dependencies. It is important to prioritise each dependency accordingly.

When NOT to use: When the geometric rule doesn’t add much value to the model. Consider manual dependencies in those cases.