Information Overview

Administrative and context information

General administrative information includes all the information to uniquely identify and describe the plan, its status and involved parties. This information includes:

• Identification of an individual revision of the maintenance plan;
• Author;
• Customer;
• Project;
• Status such as draft, issued etc;
• Date of issue;
• Approval(s).

Context information identifies the context and deployment environment for which the plan has been developed. This includes:

• Identification of the top item product to which the maintenance plan relates;
• Applicable operational context(s);
• Applicable maintenance concept;
• Assumed maintenance solution implemented by the customer/user including organization and resources;
• Description of the reliability and maintenance characteristics and requirements of the product;
• Identification of the assumed approach to collect and assess feedback;
• Reference to documents such as applicable regulations.

Details

Product breakdown

Each record in the detail section of a maintenance plan identifies and classifies each element in a product breakdown (system, functional, assembly etc) to which a maintenance task applies.

Identification of a product breakdown element includes:

• iIentifier;
• Name of the element;
• Version.

Classification of product breakdown elements can be made against any designed criteria including maintenance characteristics and proposed maintenance solution. Typically classification includes classes used to distinguish between repairable and non-repairable items:

• Repairable item, subject to preventive and/or corrective maintenance (EN 13306:2001: Repairable item. Item which may be restored under given conditions, and after a failure to a state in which it can perform a required function. Given conditions may be economical, ecological, technical and/or others)
• Spare part/nonrepairable item, subject to preventive maintenance (EN 13306:2001: Spare part. Item intended to replace a corresponding item in order to restore the original required function of the item. Spare parts/nonrepairable items that are not subjected to preventive maintenance should not be included in a maintenance plan.)

For product breakdowns where the elements are not parts, e.g. functional or system breakdowns, each element in the breakdown may also be associated with one or more parts that may realize the specified product breakdown element.

Task assignment

Each element in a product breakdown may have one or more assigned maintenance tasks. Each combination of product breakdown element and task constitutes a record in a maintenance plan. Each record is characterized by:

• What maintenance tasks to perform - a reference to a task description provided outside the maintenance plan;
• Who should perform the task - identification of the organizational unit or type of organization that shall perform the task;
• Where to perform the task - if the task can be done without removing the part or not;
• When, or under which conditions, the task falls due - a description of the condition that triggers the task;
• How to perform the task - a reference to a detailed description on how to perform the task.

Each maintenance task in the maintenance plan is characterized by:

• Unique identification of the task;
• Maintenance type classification;
• Maintenance task type classification;
• Criticality classification;
• Report code assigned to the task;
• Notes assigned to the task.

Typical maintenance types classes are (based on EN 13306:2001):

• Preventive maintenance
  • Condition based
    • Scheduled
    • Continuous
    • On request
  • Predetermined
  • Scheduled
• Corrective maintenance

Maintenance task type classification can be done in accordance with EN 13306:2001, AECMA S1000-D, MIL-STD-1388-2 or others. Examples are:

• EN 13306:2001
  • Inspection;
  • Overhaul;
  • Repair.
• AECMA S1000-D Information codes, chapter 3.2.1
  • 320, Operation test;
  • 350, Structure test;
  • 750, Load software;
  • 920, Change = remove and install.
• MIL-STD-1388-2
  • Adjust;
  • Clean;
  • Inspect;
  • Lubricate;
  • Overhaul;
  • Repair;
  • Service;
  • Test.

The responsible maintenance line or organizational unit is specified for each maintenance task. The specification is made explicitly so that there may be no doubt who is to perform a particular task.

• Line of maintenance (EN 13306:2001: Position in an organization where specified levels of maintenance are to be carried out on an item).

For each specified maintenance task it is specified if the task is to be performed without or after removing the item from the system or product. This is specified as:

• On equipment maintenance (MIL-STD-1388-2: Maintenance task is performed without removing the item from the system);
• Off equipment maintenance (MIL-STD-1388-2: Maintenance task is performed after the item has been removed from the system).

For each specified maintenance task it is specified when the task falls due:

• Task trigger (239 AAM: The conditions that require a task to be done, in the context of its assignment to a specific product element within a support solution definition)
• Scheduled;
  • Operating time;
  • Time scheduled;
  • Number of units of use;
    • Landings;
    • Rounds;
    • Operation cycles;
    • etc.
• Event based;
  • Pre operative;
  • Post operative;
  • Condition based;
  • Failure;
  • etc.
• Applicability;
  • Operational requirement;
    • Peacetime;
    • Wartime;
    • International operations;
    • etc;
  • Operating state;
    • Operations;
    • Standby;
    • Storage;
    • Cold shut down;
    • Hot shut down;
    • etc.
  • Product configuration;
  • product version;
  • product change status;
• Task trigger tolerances;
  • Operating time (+/-);
  • Time scheduled (+/-);
  • Number of units of use (+/-).

For each specified maintenance task there should exist a detailed description on how the task should be performed. In these cases the maintenance plan provides document references e.g. to a maintenance instruction.

Maintenance instructions provide a detailed description on how to perform a maintenance tasks and the required resources and facilities. Applicable general regulations, regulations from outside authorities and technical product/item desriptions necessary to perform a maintenance task are also specified in the maintenance instructions either by references or by representation.

Notes are made for any maintenance task when needed, for example additional information regarding task trigger conditions, limitations in compability.

© OASIS 2010 — All rights reserved