Perform Execution Logic Structure Sequencing
Explanation
This activity is used to sequence an execution logic structure (ELS). You
can start sequencing and add or remove dependencies to the execution logic orders
(ELOs) and task cards of an ELS once it is generated.
You can use the
Predecessors and Successors dialog to add predecessor and successor relationships
between ELOs in the structure or between task cards within an ELO. You can also
manually draw dependencies in the Gantt. To do this:
- Make sure Show Dependencies is enabled in the Gantt
settings.
- Select the relevant node + CTRL key + the dependent node. You can select
several nodes and draw dependencies at once. The dependency will be created
in the order the nodes are selected.
- The Create Dependencies command (arrow with direction
to the Right) gets enabled at the top of the Gantt.
- Click this command and the dependencies are drawn automatically.
- If you click on the dependency arrow, there are two more options that
are enabled and these can be used to delete the dependency and to swap the
direction of the dependency. It’s also possible to delete or swap several
dependencies at once by selecting the relevant dependency arrows and clicking
the relevant command.
It is also possible to move an ungrouped task card into an ELO node.
This functionality is described in detail in the activity
Move Task Card within Execution
Logic Structure.
When planning an ELS maintenance order, the planned dates for task cards, ELOs and grouping nodes are set using the earliest start date of the
maintenance order (MO) as a starting point. When the ELS is created or
updated (when adding events and task cards to the maintenance order), the
planned dates are set as follows:
- For task cards, the MO earliest start is initially set as the
planned start. The task card or subtask duration is then used to
calculate the planned finish. For example, if a task card is planned for
5 hours with a planned start at 08:00:00, the planned finish will be set
for 13:00:00 (5 hours later). Note: When you run Plan Execution
Logic Structure, the calendar will be applied as described
below, and dependencies will be considered and reflected in the planned
dates.
- For ELO nodes, the planned start is determined by the earliest
planned start of any task card within the ELO, while the planned finish
is based on the latest planned finish of the task cards within the ELO.
- For grouping nodes, the planned start is determined by the earliest
planned start of any ELO within the grouping node, while the planned
finish is based on the latest planned finish of the ELOs within the
grouping node.
Once you have finished sequencing the ELS, you need to run the Plan Execution
Logic Structure option from the Execution Logic
Structure Gantt page to get the ELOs and task cards placed correctly
in time.
When setting the planned dates, the work time calendar
for the maintenance organization associated with the workshop is applied. With
time zone support, the calendar is applied using the time zone of the workshop’s
site. This ensures that the ELS planning will be carried out in the time zone
where the work will be performed. Since the calendar is applied in the time
zone of the site, it is highly recommended to set the user's working time zone
to match the site's time zone before running the Plan Execution Logic
Structure option. If the planned dates are outside the required date interval, the
Change Required Dates on the Maintenance Order
dialog will open, and you can enter the earliest start and latest finish dates
there. If you wish to reset the entire ELS back to how it was default generated
but based on the changed, earliest start and latest finish dates, enable the
Reset the Execution Logic option from the dialog.
Prerequisites
- A maintenance order in the Under Preparation status must exist.
- An ELS must exist for the maintenance order.
System Effects
- The task cards and ELOs connected to the maintenance order will be sequenced
and dependencies defined.
- Predecessor and successor relationships between task cards in the structure
will be defined.
- The planned dates on the task cards, ELOs (including grouping nodes)
and the maintenance order will be updated automatically when sequenced.
- If demands have been released on the maintenance order, and planning
dates are changed or resources added to new ELOs, corresponding resource
activities will be generated or updated.
- The sequencing will be transferred to the work order (in IFS/Work Order
Management) when the corresponding maintenance order is released.