Execute Maintenance Visit

Execute maintenance visit essentially means releasing the various prepared work orders from the work package and executing the work tasks included in each of the work orders.

Execute Work Order

Once scheduling of work has been performed and resources allocated the work can be assigned to the resources for actual execution. During this process, engineers will review the work needed to be performed, verify that the information is correct against the maintenance manual and illustrated parts catalogue, determine any interrelated resource requirements, i.e., an inspector needed to observe actual maintenance activities been performed and start on the work.

During execution of the work it is possible that due to the type of inspection activities performed:

• Faults are discovered, thereby requiring non routines to be reported against the work order or work task on which it was discovered.
• Recorded condition measurements may exceed the defined limits, thereby resulting in a corrective event being generated to address the issue.

Both these instances of non routines need to be reported against the ongoing work scope, and usually need to be included as part of the maintenance visit package to ensure that the asset can be returned to a reliable condition.

As part of this process:

• Findings are captured.
• Time is recorded for the given resource.
• Material is reserved and issued.

Report In, Work Order

Once a work task has been performed various recording activities can occur, namely:

• Reporting of findings. Any specific requirements that need to be recorded as part of normal feedback can be performed at this stage. For instance the recording of various measurements, not included as part of condition measurements but rather to record the actual degradation of a function or capability from its original design and manufactured values, e.g., fuel pressure and number of loose rivets. Often these recordings are used by engineering to determine whether the tasks being performed are relevant and applicable to the functions which are to be corrected.
• Structure changes. These changes need to be recorded specifically where the service provider has responsibility for maintaining the configuration records of the asset during the maintenance visit. Structure changes also provide a view to the real health of an asset. The more unscheduled structure changes which are performed as part of the visit the less reliable the asset could be judged.

Integrate Emergent Work

Where non routines have been discovered as part of the normal execution of maintenance, they need to be integrated against the most appropriate ELO (execution logic order) work order, i.e., work orders created for Execution Logic Structures in the work scope. If the non routine cannot be included automatically into the appropriate ELO work order, according to the grouping criteria, the floor planner will need to move the operations to the next ELO work order which is deemed most appropriate or create an additional work order and change the dependencies based on the correction actions of the non routine. This in turn may result in a total rescheduling of the work scope to take into consideration the additional task durations and requirements.

Test and Acceptance

The process of test and acceptance is one where engineers, planners, QA managers and operational personnel review the various maintenance activities performed and then the extent of testing required to ensure that the asset can meet its certification requirements, once returned to service.

Once the requirements for testing are identified, engineers and planners determine how to execute and validate the identified requirements. The required steps/process of tests to be performed can be documented and attached to the relevant tasks which could be carried out as validation activities.

Often test schedules will exist or in certain cases maintenance manuals could define the test requirements. Depending on which activities are required, they may be raised either as additional maintenance activities or as operational test activities.