A reconciliation may be required to eliminate inconsistencies between the ‘as designed’ configuration used by the support engineer to develop the support solution and current configuration found by the maintenance manager. In many cases it will also be necessary to maintain a configuration history
Components of the Product may already have a maintenance history, a usage history and a record of current state (e.g. a wear or corrosion record). Information about all three may be needed to identify the appropriate maintenance. Information on the condition may need to be captured in terms of the parameters used by the relevant “condition monitoring” regime, so that the forward maintenance schedule can pick up at the correct point in the component lifecycle.
There may also be a requirement to record a maintenance history that attaches to a slot within the structure of the higher level product. This slot may be occupied by many instances of an exchangeable component throughout the lifecycle of the product, but has a history that is independent of the component currently fitted.
It may also be necessary to record the service and maintenance history of components that are removed from a higher assembly, refurbished, stored and re-installed into a different location (i.e. a 'log card' for the component).
Servicing routines are undertaken as part of the operating cycle of the product. They cover such tasks as fuelling and lubricating and, while clearly part of the maintenance schedule, are not normally planned as part of the maintenance programme. They do not generally associate with the FMECA. Where an association has been made, the routine would probably be better classified as a ‘condition monitoring’ task.
Certain components within the product will reveal measurable wear parameters. Condition Monitoring tasks, identified during Support Engineering, may require these parameters to be measured and recorded at the appropriate interval to detect deterioration. Such measurements will need to be scheduled by the maintenance management system. Data may be collected automatically if an appropriate sensor is installed. Results of condition monitoring must be compared with pre-determined values to detect when wear thresholds have been breached. Out-of-tolerance values should cause the MMS to add the appropriate remedial occasional tasks into the work scheduler for action before failure occurs.
Certain components will be assessed as having a finite life, attracting a routine tasks to replace or refurbish them before end-of-life. Where life is measured as a linear unit of time, the work scheduler can programme these in the schedule from the date last done. Where the measure is more complex, such as ‘number of starts’, an alternative means of scheduling must be invoked.
Occasional Tasks are the pre-planned actions necessary to recover from the impending or actual failure of a component or product. They are called forward and scheduled when condition monitoring detects impending failure or when actual failure has occurred. Their justification is derived directly from the FMEA and they are determined by the Support Engineer in his attempt to control product non-availability by ensuring that a cost effective and quick recovery procedure is already in place before the failure is encountered in service. The statistical probability of the failure occurring provides much of the justification for the decisions taken on the associated spares inventory holdings
Уважаемый посетитель!
Чтобы распечатать файл, скачайте его (в формате Word).
Ссылка на скачивание - внизу страницы.