Range Dependencies 
A Range Dependency is used to set dependencies between ranges of tasks by explicitly defining Predecessor and Successor pairs. Range dependencies are commonly used to group blocks together to form a single shot together, limit mining in an area until access is established, ensure cast and dozer material isn't blasted until the coal in the previous strip is mined or in situations where anomalies need to be controlled.
When you add or edit a Dependency of this type, you can set the following parameters (or accept the defaults where applicable):
Description
Optionally, enter a Description that can be used with the Name to further identify the Dependency. Detail useful for diagnosing issues with Dependencies should be added here.
Relationship
The Predecessor to Successor Relationship. Defaults to Source to Source. Source to Destination means a Destination Task is waiting on a Source Task to be finished.
Treat Predecessors as OR Group
Where multiple predecessor tasks have the same successor task and the OR check box is NOT enabled, the successor task will only be released after ALL of the predecessor tasks are completed.
Where multiple predecessor tasks have the same successor task and the OR check box is enabled, then the successor task will be released when ANY of the predecessor tasks are completed.
Priority
The Priority is a numerical method to classify your dependencies by importance. Ranges with Priority 1 will be resolved first, meaning if there are conflicting dependencies between two or more ranges, ranges with lower priority will become circular, rather than randomly resolving the conflict.
Act As Constraint
Normally a Dependency takes into consideration the relationship between Tasks regardless of the Equipment or Date involved. Selecting the Act As Constraint check box
For example, if the user ticks act as constraint in the dependency range, and excludes Drills, the Drills will not honour the dependency range.
Filter with Range
Select the Filter with Range check box to select a picked range to set the Predecessor Range and the Successor Range of the Dependency.
Dependency Entries
Use the local toolbar to add Dependency Entries. Copy, Insert Copy and Move options are available when you right-click on a Dependency Entry. The menu also includes a Show Dependency Pairs option. Note that each pair follows the key concept mentioned in the Dependencies Overview topic.
|
Add a new item to the list. |
|
Delete the item(s) currently selected in the list. |
|
Move the currently selected item(s) Up to reorder the list. |
|
Move the currently selected items) Down to reorder the list. |
|
Use the Bulk Editor to make bulk modifications to the items in the list. |
Name
The Name used to identify the Dependency Entry in the Snapshot Viewer.
Active
Use the Active check box to toggle the inclusion/exclusion of the Entry in the Schedule.
Predecessor/Successor Range
This is where you enter the Dependency text. For example:
Predecessor: MyPit/S1/B1-B10/A-F
Successor: MyPit/S1/B1-B10/G
Predecessor/Successor Processes
Allows you to control which Processes are used for the Dependency.
Release Delay
Once a Predecessor Range has been completed, the Release Delay controls how long until the Successor Range is considered "Released" and can be worked. Accept the default (None) or build a Release Delay Expression using the operators, constants and functions provided by the Expression Editor.
Description
Optionally, enter a Description that can be used with the Name to further identify the Dependency Entry.
Colour
Click the Colour box to set a colour to identify the Entry in the Snapshot Viewer.
