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:

Requirements

In order to process a multilevel repair there are some requirements to be fulfilled.

If the parent part is serial-tracking-enabled

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,

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,

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:

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:

  1. Parent part has not been received into the inventory after the repair.
  2. If the change has created salvaged parts, then those salvaged parts should not have already been received into the inventory.
  3. 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

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.