When failures occur that have not been anticipated through the support engineering activity, or work of a non routine maintenance origin (such as a change of paint scheme) is required, then the MMS must be capable of capturing the work requirement and managing it through the common work scheduler. It is particularly important to capture as much information as possible when an unexpected failure has occurred, since this represents a failure of the support engineering process to anticipate the failure and prepare a solution. In addition to providing management control of the remedial activity, the MMS should also generate a discrepancy report, as outlined below.
Within a task description, there must be sufficient detail on what is to be done to allow a technical cost centre to quote a fixed price for the work. The Task Description can take any format or combination of formats, from simple text through to a video clip with a sound track. The list of parts required to execute the task must be separately identified and accessible to external processes, such as automatic stores ordering when the task is scheduled.
The task scheduler within the MMS is a management tool for programming work known to be due and then allocating it to appropriate staff for execution. As a described task may be common to one or more components within the product, the scheduler must be able to associate the due task with the particular instance of the component against which the task is required. In addition to scheduling work on a day by day basis, as required by the different task natures already described, it must also allow the manager to package one or more of the outstanding tasks into requests for external assistance. When a task has been scheduled, the MMS should be capable of demanding all the necessary resources, such as spares, external facilities and specialist skill teams as necessary
Individual maintenance tasks will generate requirements for spare parts that may be consumed during the execution of the task. There must, therefore, be an interface between the Maintenance Management System and the Inventory Control System for these demands to be presented and satisfied before the task can be started. Certain tasks will result in repairable components being returned to the Inventory System for refurbishment.
Where maintenance tasks call for resources beyond the capability of the local maintenance staff, (e.g. Maintainer skill levels, special facilities or capacity to undertake) then the system must be able to communicate a request for assistance to an external support authority. If that authority has access to the support solution data, this could take the form of a simple pointer to the relevant task records but where this access is not available, then a more complete transfer will be required.
At its simplest, the MMS will collect data on the material state of the product. This will take the form of parameter values from condition monitoring, records of maintenance tasks completed and occurrence information on actual failures. Provided the recovery from failure runs according to the prediction contained within the ‘occasional’ task description, this information serves to validate the support engineering analysis and to provide statistical data to the product owner.
Before any instance of a task is confirmed as complete, the maintainer should confirm that the task description gave a full and correct account of the task. Where any part of the description was found to be in error or inadequate, then the maintainer should record the discrepancy to trigger a review by the support engineering activity. Revisions will be promulgated as changes to the approved support solution.
Уважаемый посетитель!
Чтобы распечатать файл, скачайте его (в формате Word).
Ссылка на скачивание - внизу страницы.