Assign Additional Events to the Maintenance Order
Explanation
This activity is used to assign additional pending events to a maintenance
order that has been released and for which work orders have already been generated.
You can assign events only for the same top serial (or a serial in its structure)
as the one currently on the maintenance order.
If additional events, including non routines and condition measurement events,
without connected task cards are assigned, the event will not be distributed
automatically. Instead, it will be set to the Incomplete status. Before
the event can be set to the Under Preparation or Released status,
a valid task card (i.e., for the part revision of the serial defined on the
event) must be connected to it.
Note: If you are working with manual maintenance events, it is also
possible to add the event to a maintenance order directly from the
Manual Maintenance Event page.
Prerequisites
- A maintenance order must exist.
- Pending events for the serial or for serials in its structure must exist.
System Effects
- Task cards connected to the event code will be added to the maintenance event along
with the connected subtasks, resources, and material.
Ownership of the material will be set based on
predefined rules, i.e., based on the part provisioning rules of the
contract connected to the maintenance order or defaulted as company
owned stock. For more information on setting ownership on material
demands, refer the activity
View
Material Demands.
- The event is distributed to the same workshop as the rest of the order
with the same planned start and finish dates and with the same distribution
type.
- The event(s) will be added to the maintenance order.
- If the distribution type is either Work Order or Execution
Logic Structure the event will be distributed to the work order. A work
task will be created for each task card and subtask on the event, and belonging
resources, material, sign off requirements etc. will be transferred to the
task.
- If the distribution type is Execution Logic Structure, task cards
connected to the additional events be mapped into the correct execution
logic orders (ELOs) on the execution logic structure. In addition, the task
cards will be mapped into the corresponding ELO work orders in IFS Work
Order Management. If the task card meets more than one grouping requirement
(e.g., a task card requires an engineer and technician and an ELO node exists
in the generated ELS for both resource IDs), the task card will be copied
to each applicable ELO.