Define Work Scope

Define Shop Visit Work Scope is where you define the maintenance level  for a position part, e.g. an airplane engine requiring service. For a particular Shop Visit, the customer requests some type of maintenance service. The maintenance may be standard services offered by the vendor or pre-negotiated services for the customer. These pre-negotiated services are defined within the customer's agreement.

Some parts also involve complex configurations and require the IFS/Vehicle Information Management component to define and maintain this information. The IFS/Vehicle Information Management component keeps track of each configuration and the usage of all parts within the configuration. In addition, you are able to define rules for life limitations, interval based maintenance and all applicable modifications for a complex part configuration in IFS/Vehicle Information Management. 

Define Maintenance Levels

In order to define the work scope for a position part (work order part) you first have to define the maintenance levels for the service structure that represents the makeup of the part (airplane engine) requiring service. These maintenance levels define, which parts should be disassembled, inspected (disposition), repaired and re-assembled. Maintenance levels include both maintenance level structure and routing. When you create the maintenance level structure and routing you use the monolithic structure and routing in IFS/Manufacturing Standard, which is transferred from IFS/Vehicle Information Management. 

Before the work scope can be defined for a complex part, some additional activities are required. First, the current configuration (provided by the customer) for the complex part is entered in IFS/Vehicle Information Management. Next, IFS/Vehicle Information Management examines the configuration and determines what part specific maintenance tasks are applicable. After that you will determines the part specific maintenance tasks that are appropriate for the Shop Visit. The work scope is established by using these maintenance tasks along with the standard service structure to define the necessary maintenance service levels.

Define Work Scope

This feature describes the process where you assign maintenance level to the sub-assembly parts based on tasks (modifications and Life Limited Parts) from IFS/Vehicle Information Management. The Modifications and Life Limited Parts are maintained in IFS/Vehicle Information Management and transferred after approval as tasks connected to a complex assembly work order. In addition to modifications, affected parts for the modifications are transferred by IFS/Vehicle Information Management. These tasks with affected parts are used to determine the maintenance level for each sub-assembly.

Note: The maintenance level components and operations can also be defined without any information from IFS/Vehicle Information Management i.e. there are no modifications and affected part information available. The maintenance level is assigned solely based on the type of service required for the overhaul object (work order part).

Approve and Release Work Scope

Approve Work Scope

Before you can release the work scope in order to proceed with the actual work you require an approval from the customer. This process is entirely manual there is no documents or report available to support this process at this stage. During the approval process, the work scope may be adjusted due to new demands for maintenance or modifications from the customer. 

Release Work Scope

When you have received the approval from the customer you can release the defined work scope. Now all maintenance levels that you have assigned to the sub-assembly parts are validated against MRO basic data, such as maintenance level structures and routings. If any inconsistency is found this will generate messages in log details. There are three types of log details, Error, Warning and Informational message. Warnings and informational messages are for the user to correct at users convenience. Errors are problems found during validations that affect the creation process of interim orders and that you must correct before you can release the work scope. After the work scope is released, execution orders (interim orders) are created and the real maintenance work can start. 

Change of Work Scope

During the execution of the work scope you might have to re-define the work scope. The change in work scope can be of two types. First, when additional modifications are approved in IFS/Vehicle Information Management for transfer to MRO. Second, when during disassembly a part is determined to have a different maintenance level, e.g. the subassembly requires more parts to be disassembled. For a simple part, this is a matter of adjusting the maintenance service levels and receiving approval from the customer. For a complex part, there are circumstances when information about the configuration has to be updated and IFS/Vehicle Information Management has to re-examine the part specific maintenance tasks. The revised part specific maintenance tasks are reviewed and the maintenance service levels are adjusted. Once the new work scope has been approved, the execution orders are revised and the work continues. 

Signoff Tasks

When the maintenance is completed for a complex part, it is necessary to signoff the part specific maintenance tasks in order to update information in IFS/Vehicle Information Management. The new configuration and applied maintenance tasks from IFS/Vehicle Information Management together with the serviced part are delivered to the customer.