Report Non Routine
Explanation
This activity is used to report any non routine work that was discovered
during a maintenance visit. A non routine is a fault that is discovered during
the repair phase of a scheduled maintenance, which needs to be corrected in
the ongoing work scope. In order to repair a non routine fault, it must be reported
on the work order or work task on which it was discovered. Once the fault is
reported a fault event will be created automatically for it and added to the
work package (maintenance order) for the ongoing work scope.
A non routine can be reported from the Execute Work Task
page and the Execute Work Order page for work orders/tasks
with the VIM connection type. Choose one of the following options
when reporting a non routine:
- Report Fault - The non routine fault will be repaired as part
of the current work scope. Use the steps in the assistant to register fault
information and connect documents/media items to the fault.
- Report Already Repaired Fault - This is used to indicate that
the fault has already been repaired and a fault history record is to be
generated. In addition to registering fault information and documents/media
items, following can be entered in the relevant assistant steps:
- Enter information on the repaired fault, e.g., workshop, resource
and resource time, work description.
- Enter material utilized for the work.
- Enter operational parameter values.
- Report Partially Repaired Fault - This is used to indicate that
some work has already been performed for the fault being reported. In addition
to registering fault information and documents/media items, following can
be entered in the relevant assistant steps:
- Enable the Already Performed option for the task
cards and subtasks that have already been performed.
- Enter measurement values, if condition measurements are required.
The previous measurement appears by default, and the system date is
set as the measure date.
- Enable the Resource Used option for the resources
that have been utilized. Enter the time taken in the Hours Spent
field.
- Enable the Material Used option for the material
that has been utilized. Enter the Quantity Issued and
a Serial Number for serialized parts.
For more information on how to report faults, refer the
Report a Fault activity.
Prerequisites
- A work order with connected work tasks must exist. The work order and
work task must be in either the Released or Started status.
- Basic data for faults:
- Persons must have been registered in the Person page.
- Person categories must have been defined in basic data.
- Fault categories must have been defined in basic data.
- Persons must be connected to one or more person categories in basic
data. A default category per person is required.
- The number of levels required for the function breakdown must have
been defined. For more information, refer the activity Verify or
Adjust Default Object Properties.
- Products and models must have been defined and valid functions registered
per product and model.
- Fault codes must have been defined and connected to a function breakdown
in basic data. For more information on registering fault codes for a
function breakdown, refer the activity Define Fault Function.
- If reporting an already repaired fault and sign off requirements
are connected to the function breakdown, these sign off requirements
will not be considered.
- To report time on resources, the resources must be valid for the work
order or work task site.
- To issue material, the material must be available in inventory at the
work order or work task site.
System Effects
- A pending maintenance event is created and connected to the maintenance
order when the non routine is registered as a pending fault or partially
repaired fault.
- For partially repaired faults, consumed resource time and material can
be reported.
- The maintenance event is added to the maintenance order for the ongoing
work scope. If the maintenance order is distributed with the distribution
type,
- Execution Logic Structure - The task cards and subtasks connected
to this event will be transferred automatically to the relevant work
orders based on the given grouping ID. If a relevant work order does
not exist, i.e., does not match the grouping criteria or is already
finished, a new work order will be created automatically and added to
the work order structure.
- Work Order - A new work order is created and the task cards
and subtasks that are connected to the event will be transferred automatically
to this work order.
- A historical work order is generated when the non routine is registered
as an already repaired fault.