Multilevel Repair Shop Order
Multilevel Repair Shop Order
Multilevel repair shop order is best suited for advanced repairs in a shop
order environment when a requirement exist to update and maintain a multilevel
tracked part’s as build structure. When a multilevel-tracked part is received
into the inventory after manufacturing, it records the full level as-built structure
underneath. In a multilevel repair process, we retrieve this full level saved
structure and do the necessary structure changes through a repair shop order.
You may add new components to the structure as well as you may remove some components
from the existing structure. Components removed from the structure can be received
into the inventory as salvage parts. Processing of multilevel repair shop order
means the following:
- The multilevel repair shop order provides a possibility to define the
material repair works, for each of the part that appears on the as built
structure.
- A repair replacement history is created to keep track of; replaced,
removed, not present, added, installed and salvaged parts as a result of
the repair.
- When all repair actions are executed for a part then is it possible
to receive the part back in to inventory. When the part is received in to
inventory then is also a new as-built structure revision created based on
taken repair actions.
Requirements
In order to process a multilevel repair there are some requirements to be
fulfilled.
- The parent part to be repaired should be multilevel-tracked and there
should be at least one child existing for the parent part in the as-built
structure. The parent parts should be completely reserved to the multilevel
repair shop order.
- There should exist at least one buildable repair structure alternate
for each of the structure levels to execute multilevel repair in that specific
structure level.
- If there exist a lot tracked, but not serial tracked parent that consist
of serial tracked components in the as-built structure, such parts will
not be able to reserve to a multilevel repair shop order. This combination
should not occur on any level of the as-built structure corresponds to the
reserved parent part.
If the parent part is serial-tracking-enabled
- The quantity in the repair shop order should be 1.
- The parent part serial should not have a structure in Fleet and Asset
Management.
Note: In case the parent part is both serial and lot/batch-tracked,
the generation of as-built structure does not consider the lot/batch number
of the reserved parent part. Here the as-built structure is generated by selecting
the records with the highest as-built revision number for the same parent serial.
This is required to get the latest as-built structure for a serial where the
lot/batch number of the parent has been changed due to some reasons.
If the parent part is not serial-tracked but lot-tracked,
- All the parent parts should be reserved from a single lot/batch.
Changes in Multilevel Repair with Respect to Normal Repair
Although the multilevel repair process inherits the normal shop order flow,
there are further changes that are applied to the multilevel repair process. For
instance,
- Only components in the repair structure with Consumption
Item set to Not Consumed, or with
Exclude from As-Built Structure enabled, will be copied as
material to the multilevel repair shop order. Material that should be
included in the as-built structure must be added to the shop order using
the repair actions from the relevant as-built node.
- It is not possible to add consumable material lines to a multilevel
repair shop order directly, instead you will modify the multilevel repair
shop order structure.
- It is not possible to change the lot size of a multilevel repair shop
order if at least one repair history record exists.
- It is only allowed to reserve a single lot/batch number for a multilevel
repair shop order.
- Material lines of a multilevel repair shop order are not manually editable
(This is not applicable for the Condition Code, Owner
and Ownership fields).
- You cannot use alternate component replacement functionality for the
material of a multilevel repair shop order.
- The existing structure revision/alternate cannot be changed the usual
way - changes are made through the multilevel repair shop order structure.
- You cannot use the shop order split/merge functionality for a multilevel
repair shop order.
Salvage Parts
If a part is replaced or removed from a subassembly then is it possible to
receive this part in to inventory as a salvage part. Depending on if the part
to be salvage is company- or customer owned could the value for it be different.
There is an existing hierarchy implemented for both company- and customer owned
salvage part which is used to provide either an inventory value if the part
is company owned or an acquisition value if the part is customer owned, if the
customer is setup to save such value.
Repair actions
Under multilevel repair it is possible to add a structure component, remove
a structure component, or replace a structure component. It is also possible
to install an already available component to the as-built structure, remove
a component which is not actually present from the as-built structure, or define
a component for direct salvage while it has not been listed in the as-built
structure. These actions can be performed in any level of the as-built structure.
When processing a repair by using the multilevel repair shop order flow then
are the material work scope generated by taking different repair actions from
different nods in the as built structure, i.e. repair actions are initiated
for some of the grandparent part’s subassemblies which are in need of repair
or a modification.
The following repair actions are possible to take
for a subassembly and its constituting parts:
- Replace
- Remove
- Not Present
- Add
- Install
- Salvage
Revert Changes
It is possible to revert the changes done to one or several component lines
in a multilevel repair shop order on following conditions:
- Parent part has not been received into the inventory after the repair.
- If the change has created salvaged parts, then those salvaged parts
should not have already been received into the inventory.
- If the change has created any new material demand, then those materials
should not have been issued. (If there any reserved materials exist, then
those will be un-reserved)
Receiving the Repaired Part
- If the repaired part is lot/batch-tracking-enabled, then a new lot /batch
number should be reserved to the parent part before receiving the repaired
part. You cannot receive the repaired part with the existing lot/batch number.
If the repaired part has order-based lot tracking-enabled, then the generated
lot/batch number will be used. All the new sub-assemblies will also get
the same lot/batch number.
- A new as-built structure is created when receiving the repaired part
for all the changed sub-assemblies and the parts above it.
- When creating the new as-built structure, the number of components marked
as to be removed along with their components are excluded if the Repair
Action for those were set as Removed, Replaced or Not
Present.
- When creating the new as-built structure, any new component added by
using Add, Replace or Install; as the Repair Action
will be installed.
Exception: Components with the Exclude
from As-Built Structure setting enabled will not be added in to the
new as-built structure.
- If a sub-assembly has changes defined where the specific parent part
is serial-tracked, then the as-built revision will be incremented by 1 when
creating the new as-built structure.
- Receiving a multilevel repair shop order is irreversible.
Tracking the Repair Process
For each of the structure changes done to the as-built structure, there exists
a history record . You can update some of the parameters; such as Repair
Reason and Notes in the repair history, if the new as-built structure
has not been created.
How operations are generated for a multilevel repair shop order
If it is a standalone multilevel repair shop order then are all the operations
defined for the grandparent part fetched. If the multilevel repair shop order
instead is created as repair order for a CRO repair then are the operations
generated on the base of the repair codes related to the service types defined
for the CRO repair.