Dependencies
On the Dependencies tab of the Auxiliary Task Rules form, specify the relationships to be established between nominated types of auxiliary tasks, both within and between cycles. The relationships are established by creating dependencies between the appropriate source and destination tasks in the schedule.
Auxiliary Task Cycle Generation Rules
The Auxiliary Task Cycle Generation Rules grid list lists the relationships that are to be established between nominated types of auxiliary tasks within each cycle.
Use the icon buttons on the top right of the grid list to add, delete and clear items in the list.
Task filters can be used to ensure that different types of auxiliary tasks are created for tasks based on their values for characteristic attributes. For example, the type of blasting task used could be based on the compressive strength of the rock. Alternatively, the blasting task could be excluded if blasting were not required for the contained material.
Enter the following details for each relationship to be established:
Source
Specify the details for the type of auxiliary task from which the relationship is to be established and the connection is to start. Tasks generated in this context are referred to as "source tasks".
Auxiliary Task Type
Select the type of auxiliary task from which the relationship is to be established and the connection is to start.
Task Filter
Select the filter to be applied to the primary tasks to identify the tasks from which the relationships are to be established.
This filter is applied in addition to the filter specified for Source > Auxiliary Task Type on the Task Types tab.
For further details on creating and using task filters, see: Task Filter
Destination
Specify the details for the type of auxiliary task to which the relationship is to be established and the connection is to finish. Tasks generated in this context are referred to as "destination tasks".
Connection
Select the type of Connection to be established between the source task and destination tasks.
| Type | Description | |
|---|---|---|
| Finish-Start |
|
The second Task (B) in the relationship cannot begin until the first Task (A) is completed. This is the most common type of relationship. Note: In this type of relationship, Task (B) does not have to begin as soon as Task (A) is completed; there may be a delay. |
| Finish-Finish |
|
The second Task (B) in the relationship cannot be completed until the first Task (A) is completed as well. Note: In this type of relationship, the Finish-Finish link type does not require that both Tasks be completed simultaneously. Task (B) can be completed any time after Task (A) is completed. |
| Start-Start |
|
The second Task (B) in the relationship cannot begin until the first Task (A) begins. Note: The Start-Start link type does not require that both Tasks begin simultaneously. Task (B) can begin any time after Task (A) begins. |
| Start-Finish |
|
The second Task (B) in the relationship cannot be completed until the first Task (A) begins. However, the second Task (B) can be completed any time after the first Task (A) begins. Note: The second Task (B) can be completed any time after Task (A) begins. The Start-Finish link type does not require that the dependent Task be completed concurrent with the beginning of the Task on which it depends. |
Lag Size
Specify the Lag Size, which is the amount by which the enforcement of the connection relationship should be delayed. If necessary, click on the = symbol at the left of the expression input box to use the variables, constants and functions provided by the Expression Editor.
Lag Units
When specifying relationships between tasks in the schedule, or rules for creating those relationships, the following options are available for specifying the units in which the enforcement delays (lags) for each connection are measured.
|
Lag Unit |
Description |
Example |
|---|---|---|
|
hours |
Number of hours to have passed. |
Connection = Finish→Start Lag | Size = 8 Lag | Units = hours specifies that the destination task cannot start until 8 hours after the source task has been completed. |
|
quantity |
Value of the quantity attribute for the source task that must be reached. |
Quantity attribute for the source task = "MASS" Connection = Start→Start Lag | Size = 2000 Lag | Units = quantity specifies that the destination task cannot start until 2000 units of the "MASS" attribute (e.g. tonnes) have been completed in the source task. |
|
% complete |
Percentage of the source task that must have been completed. |
Quantity attribute for the source task = "VOLUME" Connection = Start→Finish Lag | Size = 25 Lag | Units = % complete specifies that the destination task cannot finish until 25% of the "VOLUME" attribute has been completed in the source task. |
Note: Only one of these conditions can be specified for each connection.
Auxiliary Task Type
Select the type of auxiliary task to which the relationship is to be established and at which the connection is to finish.
Task Filter
Select the filter to be applied to the primary tasks to identify the tasks to which the relationships are to be established.
This filter is applied in addition to the filter specified for Destination > Auxiliary Task Type on the Task Types tab.
Note: Within a cycle, if either the source task or the destination task (as generated in accordance with the Task Types tab) is excluded by a dependency filter, the dependency will not be generated (and the tasks will not be affected).
Auxiliary Task Inter-Cycle Relationships
The Auxiliary Tasks Inter-Cycle Relationships grid list defines the relationships that are to be established between the cycles of auxiliary tasks that are generated.
Two (2) cycles of tasks are referenced for this purpose:
-
Current cycle, which contains the “destination” tasks to which the relationships are to be established and the connections are to finish; and
-
Related cycle, which contains the “source” tasks from which the relationships are to be established and the connections are to start.
The related cycle is specified relative to the current cycle using an integer offset value that reflects their separation within the sequence of primary tasks for which auxiliary tasks were generated.
Use the icon buttons on the top right of the grid list to add, delete and clear items in the list.
Enter the following details for each inter-cycle relationship to be established:
Source
Specify the details for the type of auxiliary task, within the related cycle, from which the relationship is to be established and the connection is to start. Tasks generated in this context are referred to as “source tasks”.
Offset
Enter the number of cycles by which the source primary task differs from the destination primary task within the list of primary tasks identified for inclusion in this rule set.
Any non-zero integer value will be accepted here and interpreted as follows:
|
Value |
Description |
|---|---|
|
< 0 |
Number of primary tasks prior to this one in the sequence of tasks for which auxiliary tasks of the source auxiliary task type were generated. e.g. -1 = previous, -2 = second previous |
|
> 0 |
Number of primary tasks after this one in the sequence of tasks for which auxiliary tasks of the source auxiliary task type were generated. e.g. 1 = next, 2 = one after next |
Note 1: Zero (0) will not be accepted here. Such relationships should be defined in the Auxiliary Task Cycle Generation Rules grid list above.
Note 2: In the case of primary tasks for which the offset references multiple source primary tasks, relationships will be established with ALL source primary tasks referenced.
Auxiliary Task Type
Select the type of auxiliary task, within the related cycle, from which the relationship is to be established and the connection is to start.
Task Filter
Select the filter to be applied to the primary tasks to identify the tasks from which the relationships are to be established. See: Task Filter
Destination
Specify the details for the type of auxiliary task, within the current cycle, to which the relationship is to be established and the connection is to finish. Tasks generated in this context are referred to as “destination tasks”.
Connection
Select the type of Connection to be established between the source task and destination tasks.
| Type | Description | |
|---|---|---|
| Finish-Start |
|
The second Task (B) in the relationship cannot begin until the first Task (A) is completed. This is the most common type of relationship. Note: In this type of relationship, Task (B) does not have to begin as soon as Task (A) is completed; there may be a delay. |
| Finish-Finish |
|
The second Task (B) in the relationship cannot be completed until the first Task (A) is completed as well. Note: In this type of relationship, the Finish-Finish link type does not require that both Tasks be completed simultaneously. Task (B) can be completed any time after Task (A) is completed. |
| Start-Start |
|
The second Task (B) in the relationship cannot begin until the first Task (A) begins. Note: The Start-Start link type does not require that both Tasks begin simultaneously. Task (B) can begin any time after Task (A) begins. |
| Start-Finish |
|
The second Task (B) in the relationship cannot be completed until the first Task (A) begins. However, the second Task (B) can be completed any time after the first Task (A) begins. Note: The second Task (B) can be completed any time after Task (A) begins. The Start-Finish link type does not require that the dependent Task be completed concurrent with the beginning of the Task on which it depends. |
Lag Size
Specify the Lag Size, which is the amount by which the enforcement of the connection relationship should be delayed. If necessary, click on the = symbol at the left of the expression input box to use the variables, constants and functions provided by the Expression Editor.
Lag Units
When specifying relationships between tasks in the schedule, or rules for creating those relationships, the following options are available for specifying the units in which the enforcement delays (lags) for each connection are measured.
|
Lag Unit |
Description |
Example |
|---|---|---|
|
hours |
Number of hours to have passed. |
Connection = Finish→Start Lag | Size = 8 Lag | Units = hours specifies that the destination task cannot start until 8 hours after the source task has been completed. |
|
quantity |
Value of the quantity attribute for the source task that must be reached. |
Quantity attribute for the source task = "MASS" Connection = Start→Start Lag | Size = 2000 Lag | Units = quantity specifies that the destination task cannot start until 2000 units of the "MASS" attribute (e.g. tonnes) have been completed in the source task. |
|
% complete |
Percentage of the source task that must have been completed. |
Quantity attribute for the source task = "VOLUME" Connection = Start→Finish Lag | Size = 25 Lag | Units = % complete specifies that the destination task cannot finish until 25% of the "VOLUME" attribute has been completed in the source task. |
Note: Only one of these conditions can be specified for each connection.
Auxiliary Task Type
Select the type of auxiliary task, within the current cycle, to which a relationship is to be established and at which the connection is to finish.
Task Filter
Select the filter to be applied to the primary tasks to identify the tasks to which the relationships are to be established.
Further details on creating and using task filters can be found here.
OK
Click OK to save the changes to the auxiliary task rules for the primary task type.