Release Work Scope

Explanation

This activity is used to release the work scope for an overhaul object (work order part) and create the interim order structure. During the release process, the work scope will be validated against maintenance level structures and routings. Verify the assigned maintenance levels and then click Release Work Scope in the header of the Define Work Scope page. Any deviation will generate a message displayed as log details in the Define Work Scope/Log Details tab.

The messages in log details are listed in three severity levels, Error, Warnings, and Informational message. Warnings and informational messages are for you to correct at your convenience. Errors are problems found during validations which affect the creation of interim orders. 

Error messages are generated when:

• Affected parts are not included in the maintenance level assigned for a sub-assembly
• When assigned maintenance level structure or routing is not in state Active. 
• A not buildable routing for a part that has a maintenance level. 
• A not buildable routing for a disposition order code for a part which does not have components. 

Warning messages are generated when:

• A structure exists for a disposition order code part which is not in state Buildable. 
• A  disposition order code part has routing operations and is not in state Buildable. 
• Sub-assemblies not having any maintenance levels assigned. 
• Sub-assemblies which have a maintenance level but its parent does not have a maintenance level. 
• Include parts which are in disassembly order code but not in assembly order code. 

Informational messages are generated when:

• No routing operations are defined for disposition order code part. 
• Parts are included  in assembly but not in disassembly order structure.

If an error message appears, the release of the work scope fails. You need to review the error log details and take corrective actions. If no errors are generated then the work scope will be released and an interim order structures is created. To view the interim order, click Interim Order Structure (under Navigation) in the header of the Define Work Scope page.

If maintenance levels for the work order part or a sub-assembly is changed after the work scope is released, the original work scope is changed. The change in work scope can happen due to following reasons:

• When new modification or life limited events with affected parts are transferred, the original maintenance level may not expose these affected parts. New maintenance level may be required to expose (disassemble) the affected part.
• While in disassembly if a different part or serial is found (other than parts or serials in the serial structure in IFS/Fleet and Asset Management); due calculation has to be performed in order to determine events for new part or serial. New maintenance level may be required to expose these event affected parts.
• While in disassembly or disposition if the part needs more disassembly due to problems identified during disassembly or disposition, new maintenance level is needed to expose the sub-assembly.

The work scope can be re-released after changing maintenance levels for the work order part or sub-assemblies. For more information, refer the activity Change Work Scope.

It is possible to manually include components in the work scope of a shop visit from the Disposition Summary page. This makes it possible to expand the work scope when the available maintenance levels do not sufficiently cover the maintenance requirements. Click Include in Work Scope for the required record in the page. The work scope can also be re-released at this time, by enabling the relevant option in the Include to Work Scope dialog.

Prerequisites

• The work scope for the work order part must be defined.
• Maintenance levels must be assigned for each affected position part.
• Maintenance level structures and routings must be in the Active status.

System Effects

As a result of this activity, the work scope is released and the interim order structure is created. If errors are generated, the release of the work scope will fail. The errors must be solved before the work scope can be released. Whether there are errors or not, any informational and warning messages that are found will be generated in log details.

Pages

Define Work Scope

Activity Diagrams

Configure And Approve Work Scope