Reconfigure Work Scope

There can be several reasons for reconfiguring a running work scope. One of the main reasons being the changes introduced to the overhaul object's structure as a result of a Different Part Found scenario. A Different Part Found (DPF) scenario occurs when the expected serial part is not the same as the serial part received during disassembly. DPFs are handled through several processes. 

See also Change Work Scope.

Once the interim order for the work scope is released, the expected off-log and off-log are created. At creation, these logs will be populated with a copy of the overhaul object's serial structure (in Fleet and Asset Management), since it is;
a. after the disk sheet updates have been performed by the customer, and,
b. before the disassembly orders for the overhaul object have started

When the first disassembly order is started the serial structure in Fleet and Asset Management will no longer be intact. The expected off-log and off-log can then be used to view details of the structure, as it was when the maintenance process started.

The expected off-log will never change, it retains information of the original structure throughout the entire maintenance process. The off-log is updated with the serials found during disassembly of the overhaul object. If all serials are found as expected (i.e., no DPF), details in the expected off-log and off-log will be the same.
However, if serials that are not expected are found (i.e., DPF occurs), the expected off-log and off-log will not contain similar details. The off-log will be updated with the new serials that were found during the disassembly process. These new serials will be created automatically if they do not exist in the application. Additional information for the new serial must be entered manually in Fleet and Asset Management. The old serials that, although expected, were not in the overhaul object, will be shown in the generated Structure Mismatch Log. You need to update the serial structure in Fleet and Asset Management according to the data generated in the structure mismatch log. For instance, you need to remove the old serial from the structure after a DPF occurred. Note: When an assembly shop order is closed for each level in the structure, the associated structure in the off-log is closed.

Once disassembly and disposition have been completed for the structure or sub-structure, a preliminary conformance check must be run in order to validate the assembly setup. You can manually run a preliminary conformance check on the assembly shop order. The preliminary conformance check will also be executed automatically at the first issue of material on an assembly shop order. Through this check the system will verify that the structure on the level below is in conformance with given configuration rules and that the chosen assembly shop order contains reserved serials.

One other significant result of the preliminary conformance check is that the expected on-log is created [or updated]. The expected on-log is created [or updated] on a level-by-level basis. The log will be populated with serials on the level below the selected assembly order each time the preliminary conformance check is run. When the last assembly order is finished the expected on-log will be closed.

A final configuration conformance check can be run once assembly of the overhauled object is completed. Through this check the system will verify that all work scope events are signed off, the structure is completed according to the template structure and given configuration rules, and that all shop visit requirements have been fulfilled. Warnings generated through this check will be shown in the final conformance log. A person with relevant authority, for instance, an engineer, will manually perform corrections on the structure OR approve the warning record. Once all warnings have been approved, the operational condition of the overhaul object is set to Operational and the status of the associated MRO work order is set to Work Done. When the status of the MRO work order (i.e., the work order for for the work scope) is set to Work Done, the actual on-log is created.

Usually, the expected on-log and on-log will contain similar structure details. However, if serials other than the reserved serials are used during assembly of the structure, the expected on-log and on-log will contain different structure details.

The following list outlines a typical work flow for executing a work scope for a shop visit.

1. Release Interim Order Structure (sub process Handle Order Structure)
   • expected off-log is created
   • off-log is created
2. Identify Parts/Serials (sub process Disassemble Overhaul Object)
   • If the serial is not registered in Fleet and Asset Management, it is created automatically
   • off-log is updated automatically
   • Structure Mismatch Log is updated
3. Resolve Mismatch Structures, variant MRO
   • Structure updates for the "new" serials must be done manually - these updates will be updated automatically in the off-log as well
   • Component Life data must be added manually for the "new" serials
   • The "old" serials will appear in the Structure Mismatch Log and they should manually be checked.
4. Plan Maintenance Events, variant MRO 
   • Structure details of the disassembled overhaul object structure can be analyzed using the off-log structure.
   • The off-log can be updated with the new serials in the work scope for which structure information has been registered in Fleet and Asset Management.
   • New events must be added manually for additional changes, other modifications or different LLPs (Life Limited Parts).
   • Superfluous events must be removed from the work scope
5. During the Disposition Overhaul Object sub process and when reserving other Serials to assembly orders in the Assemble Overhaul Object sub process, that are not reserved from the disassembly orders, the user must manually control that the new serials match the visit requirements for modification compliance and LLP's remaining life. The application does not have automatic controls for this.
6. A preliminary conformance check can be performed (either manually or automatically) on the assembly shop order to perform the following activities:
   • Update Fleet and Asset Management with information that the serial structure for the shop visit is currently in the Assembly phase.
   • Warnings are generated if the structure on the level below the selected assembly shop order is not in compliance with given configuration rules, is not complete according to the template structure, and if one or more assembly shop orders do not have serials reserved for all demands.
   • The expected on-log is created [or updated] and will show all reserved serials for the level below the selected assembly shop order.
7. The serial structure in Fleet and Asset Management is automatically updated each time an assembly shop order is completed. Once assembly of the overhaul object is completed, you can run a final conformance check.
8. The final conformance check makes sure that all events are approved and that the structure is complete.
9. When the status of the work order is set to Work Done,  the on-log is created. This will hold information of the structure, as it is before return to the customer.
10. If a different serial than the one reserved to the assembly order is installed, this will be shown in the As Built log in IFS/Manufacturing.