Maintenance plan - Business perspective

Maintenance plan overview

This exchange enables the transmission of the data exchange set (DEX) Maintenance Plan.

A maintenance plan is initially prepared during the latter stages of the detail design and development phases and is continuously assessed and adjusted throughout the lifetime of a system or product. The plan is prepared and established based on a Logistic Support Analysis, LSA, including:

• Failure analysis of the product;
• Analysis of maintenance resources and supportability characteristics of an established or assumed maintenance concept;
• Analysis of use and reliability performance requirements of the product.

The purpose of a maintenance plan is to specify maintenance tasks necessary to sustain the requirements of use, reliability performance, safety and economy throughout its lifetime.

A maintenance plan contains information on:

• General administrative data;
• The context in which the maintenance plan applies;
• The product to which maintenance plan applies;
• The tasks to be performed.

General administrative data includes identification of an individual revision of the maintenance plan, involved parties, status, and date of issue.

The context information identifies the top item product to which the maintenance plan relates, the maintenance concept being applied, the support requirements which the plan adresses, and the deployment environment to which the plan applies, including the assumed operational use and resource availability.

The product information identifies and classifies each element in the breakdown of the product (system, functional, assembly etc) to which maintenance tasks applies.

The main purpose of the maintenance plan is to identify the maintenance tasks that applies to each element in the products breakdown structure. For each specified task it also specifies who will perform the task, where it will be performed, the condition under which the task falls due, and how the task is to be performed.

A maintenance plan may include sub plans covering relevant sub-divisions of the product or deployment environment.

Maintenance plans provide the basis for planning, budgeting, preparing, performing and assessing current maintenance of a product and its included parts.

Maintenance plans may be produced by manufacturers, suppliers, procurement authorities, users and others.

Maintenance plan information content

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.

Maintenance plan - Implementation details

Model overview

This section is a detailed description on how to implement a typical Maintenance Plan in PLCS, using defined PLCS capabilities and PLCS reference data.

This implementation may be further tailored by specific parties, firstly by extending the reference data library, and secondly by introducing new relationships between entities available in the schema for the Maintenance plan DEX, which are not used in this basic implementation of the DEX.

The implementation details are organized in accordance with the section 'Maintenace Plan Information Content' above.

An overview of the capabilities used by this DEX is shown in figure 2 below.

Basic constructs

A maintenance plan is an actual product and is therefore represented as a Product_as_realized as described in the C011: representing_analysis_result capability. The actual maintenance plan (Product_as_realized) is a realization of a Part representing all editions of the fault state analysis result. The Part should be classified as [MaintenancePlan]
Error RDL1: The class MaintenancePlan does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
and the Product_as_realized should be classified as [Revision]
Error RDL1: The class Revision does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
.

Representation of general administrative and context information

The representation of the general administrative and context information of a maintenance plan, is based on the constructs described within the "Representing context information" section of the C011: representing_analysis_result capability, along with some additional reference data.

The general administrative information is represented as follows:

• Identification of an individual revision - of a maintenance plan is represented as firstly, an Identification_assignment being assigned to the Part entity representing all revisions of the maintenance plan, and secondly, an Identification_assignment being assigend to the Product_as_realized representing the revision of the maintenance plan. The Identification_assignment being assigned to the Part should be classified as [AnalysisResultIdentification]
  Error RDL1: The class AnalysisResultIdentification does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  and the Identification_assignment being assigned to the Product_as_realized should be classified as [Revision_identification]
  Error RDL1: The class Revision_identification does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  .

  NOTE    For more details on how to represent the identification of an analysis result see the "Identification" section of the C011: representing_analysis_result capability.

• Author - is represented as a Person, Person_in_organization or as an Organization as described in the "Involved parties" section of the C011: representing_analysis_result capability. The Organization_or_person_in_organization_assignment should be classified as [IssuedBy]
  Error RDL1: The class IssuedBy does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  .
• Customer - is represented as a Person, Person_in_organization or as an Organization as described in the "Involved parties" section of the C011: representing_analysis_result capability. The Organization_or_person_in_organization_assignment should be classified as "Customer" (urn:plcs:rdl:std:Customer).
• Project - is represented as Project as described in the "Project" section of the C011: representing_analysis_result capability. The Project_assignment should be classified as [TargetProject]
  Error RDL1: The class TargetProject does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  .
• Status - of the revision of the maintenance plan is represented as a State as described in the "Status" section of the C011: representing_analysis_result capability. The State representing the status should be assigned to the Product_as_realized representing the revision of the maintenance plan. The types of states that a maintenance plan may be in are defined as classes of State_definition (as described in the C007: representing_state_type capability). Typical classes representing the status of a maintenance plan are "Draft" (urn:plcs:rdl:std:Draft), "Reviewed" (urn:plcs:rdl:std:Reviewed) and "Final" (urn:plcs:rdl:std:Final).
The Applied_state_definition_assignment should be classified as [InState]
Error RDL1: The class InState does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml

• Approvals - are represented as Approval, as described in the "Approval" section of the C011: representing_analysis_result capability. The Approval should be classified as "Approved" (urn:plcs:rdl:std:Approved).
• Dates - are represented as Calendar_date or Date_time as described in the "Dates" section of the C011: representing_analysis_result capability. The Date_or_date_time_assignment should be classified. A typical value is [DateOfIssue]
  Error RDL1: The class DateOfIssue does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  .

The maintenance plan context information is represented as follows:

• The top item product to which the maintenance plan relates - is represented as either a Part, Breakdown_element or as a Product_configuration as described in the "Related product" section of the C011: representing_analysis_result capability. The product is referenced by its identifier which in turn could be classified as e.g. [Part_code]
  Error RDL1: The class Part_code does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  , [LCN_code]
  Error RDL1: The class LCN_code does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  or [NameIdentification]
  Error RDL1: The class NameIdentification does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  depending on the context. The relationship between the Part representing the maintenance plan and the Part representing the product under consideration is established using the Product_relationship entity. The Product_relationship should be classified as [ContextItem]
  Error RDL1: The class ContextItem does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  .






Figure 4 —  The top item product to which the maintenance plan relates


• Operating environment, maintenance concept and maintenance solution - are all represented as typical environments, as described in the "Environment" section of the C011: representing_analysis_result capability. The State_definition is classified according to the environment aspect that it represents. The following classifications are valid in the context of a maintenance plan ; [OperatingEnvironment]
  Error RDL1: The class OperatingEnvironment does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  , [MaintenanceConcept]
  Error RDL1: The class MaintenanceConcept does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  and [MaintenanceSolution]
  Error RDL1: The class MaintenanceSolution does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  .
• Reliability and maintenance characteristics and requirements - are represented as a String_representation_item. The String_representation_item is assigned to the Product_as_realized using the Assigned_property. The Assigned_property should be classified as [CharacteristicsAndRequirementsDescription]
  Error RDL1: The class CharacteristicsAndRequirementsDescription does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  .
• Feedback routine - is represented as
  Error ER-7: The express_ref linkend
  task_specification:arm:Task_specification_arm.Task
  is incorrectly specified.
  The entity does not exist.
  Note linkend is case sensitive.
  Task as described in the referencing_task
  Error C1: Capability referencing_task not in dex_index.xml
  capability. The
  Error ER-7: The express_ref linkend
  task_specification:arm:Task_specification_arm.Task
  is incorrectly specified.
  The entity does not exist.
  Note linkend is case sensitive.
  Task should describe the routines and facilities for maintenance reporting and field feedback analysis and assessment, and should be classifed as [MaintenanceFeedbackTaskDefinition]
  Error RDL1: The class MaintenanceFeedbackTaskDefinition does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  .
• Document references - are represented as Document_assignments as described in the "Related documents" section of the C011: representing_analysis_result capability. The Document_assignment should be classifed as [Reference]
  Error RDL1: The class Reference does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  .

Representation of the detail data section

The representation of the detail data section is based on the usage guidance provided in the "Representing content information" section in the C011: representing_analysis_result capability.

Product breakdown

Each record/row in a maintenance plan is based on a maintenance
Error ER-7: The express_ref linkend
task_specification:arm:Task_specification_arm.Task
is incorrectly specified.
The entity does not exist.
Note linkend is case sensitive.
Task being assigned to a Part,
Error ER-7: The express_ref linkend
attachment_slot:arm:Attachment_slot_arm.Slot
is incorrectly specified.
The entity does not exist.
Note linkend is case sensitive.
Slot or Breakdown_element within the within the Product breakdown or Assembly structure of the product under consideration.

What to perform

Each maintenance task is represented as a
Error ER-7: The express_ref linkend
task_specification:arm:Task_specification_arm.Task
is incorrectly specified.
The entity does not exist.
Note linkend is case sensitive.
Task being assigned to a Part,
Error ER-7: The express_ref linkend
attachment_slot:arm:Attachment_slot_arm.Slot
is incorrectly specified.
The entity does not exist.
Note linkend is case sensitive.
Slot or Breakdown_element using
Error ER-7: The express_ref linkend
task_specification:arm:Task_specification_arm.Task_assignment
is incorrectly specified.
The entity does not exist.
Note linkend is case sensitive.
Task_assignment.

A maintenance plan should not include in-depth descriptions of the respective maintenance task, but merely a reference to the
Error ER-7: The express_ref linkend
task_specification:arm:Task_specification_arm.Task
is incorrectly specified.
The entity does not exist.
Note linkend is case sensitive.
Task using the principles decribed in the referencing_task
Error C1: Capability referencing_task not in dex_index.xml
capability. The
Error ER-7: The express_ref linkend
task_specification:arm:Task_specification_arm.Task
is incorrectly specified.
The entity does not exist.
Note linkend is case sensitive.
Task identifier (Identification_assignment) should be classified as [TaskIdentification]
Error RDL1: The class TaskIdentification does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
.

Each
Error ER-7: The express_ref linkend
task_specification:arm:Task_specification_arm.Task
is incorrectly specified.
The entity does not exist.
Note linkend is case sensitive.
Task can be classified to describe e.g; type of maintenance or type of task. Typical values includes:

• [MaintenanceTypeDefinition]
  Error RDL1: The class MaintenanceTypeDefinition does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  ;
  • [PreventiveMaintenance]
    Error RDL1: The class PreventiveMaintenance does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
    ;
    • [ConditionBased]
      Error RDL1: The class ConditionBased does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
      ;
      • [Scheduled]
        Error RDL1: The class Scheduled does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
        ;
      • [Continuous]
        Error RDL1: The class Continuous does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
        ;
      • [OnRequest]
        Error RDL1: The class OnRequest does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
        ;
    • [Predetermined]
      Error RDL1: The class Predetermined does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
      ;
    • [Scheduled]
      Error RDL1: The class Scheduled does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
      ;
  • [CorrectiveMaintenance]
    Error RDL1: The class CorrectiveMaintenance does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
    ;
• [MaintenanceTaskTypeDefinitions]
  Error RDL1: The class MaintenanceTaskTypeDefinitions does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  ;
  • "Adjust" (urn:plcs:rdl:std:Adjust);
  • "Clean" (urn:plcs:rdl:std:Clean);
  • "Inspect" (urn:plcs:rdl:std:Inspect);
  • "Repair" (urn:plcs:rdl:std:Repair);
  • "Lubricate" (urn:plcs:rdl:std:Lubricate);
  • "Overhaul" (urn:plcs:rdl:std:Overhaul);
  • "Service" (urn:plcs:rdl:std:Service);
  • "Test" (urn:plcs:rdl:std:Test).

A maintenance task can also be classified in many other ways e.g according to criticality etc. However, no reference data is provided in this DEX.

Additional characterization of a maintenance task includes:

• report code - is represented as a String_representation_item and is assigned to a
  Error ER-7: The express_ref linkend
  task_specification:arm:Task_specification_arm.Task
  is incorrectly specified.
  The entity does not exist.
  Note linkend is case sensitive.
  Task by Activity_property as described in the C077: assigning_process_properties capability. The Activity_property should be classified as [ReportCode]
  Error RDL1: The class ReportCode does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  ;
• notes - is represented as a String_representation_item and is assigned to a
  Error ER-7: The express_ref linkend
  task_specification:arm:Task_specification_arm.Task
  is incorrectly specified.
  The entity does not exist.
  Note linkend is case sensitive.
  Task by Activity_property as described in the C077: assigning_process_properties capability. The Activity_property should be classified as "Note" (urn:plcs:rdl:std:Note).

Who to perform

The responsible organizational unit or maintenance line is represented as an Organization or as a Organization_type respectively. The organisational unit or maintenance line is assigned to the
Error ER-7: The express_ref linkend
task_specification:arm:Task_specification_arm.Task
is incorrectly specified.
The entity does not exist.
Note linkend is case sensitive.
Task using Organization_or_person_in_organization_assignment as described in the referencing_person_organization
Error C1: Capability referencing_person_organization not in dex_index.xml
capability. The Organization_or_person_in_organization_assignment should be classified as [LineOfMaintenance]
Error RDL1: The class LineOfMaintenance does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml

Where to perform

The representation of whether a maintenance task is to be performed without removing, or after removing the item from the system or product is done by classification of the
Error ER-7: The express_ref linkend
task_specification:arm:Task_specification_arm.Task
is incorrectly specified.
The entity does not exist.
Note linkend is case sensitive.
Task. PLCS defined classes are:

• [OnEquipmentMaintenance]
  Error RDL1: The class OnEquipmentMaintenance does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  ;
• [OffEquipmentMaintenance]
  Error RDL1: The class OffEquipmentMaintenance does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  .

When to perform

A description of the parameter that triggers a specified maintenance task is represented as Activity_property assigned to the
Error ER-7: The express_ref linkend
task_specification:arm:Task_specification_arm.Task_assignment
is incorrectly specified.
The entity does not exist.
Note linkend is case sensitive.
Task_assignment using the C053: representing_periodicity capability (where not specified otherwise).

Depending on how the task trigger is defined, the Activity_property should be classified accordingly. Activity_property classes are:

• [TaskTrigger]
  Error RDL1: The class TaskTrigger does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  ;
  • [ScheduledTrigger]
    Error RDL1: The class ScheduledTrigger does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
    ;
    • [OperatingTimeTrigger]
      Error RDL1: The class OperatingTimeTrigger does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
      ;
    • [TimeScheduledTrigger]
      Error RDL1: The class TimeScheduledTrigger does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
      ;
    • [NumberOfUnitsOfUseTrigger]
      Error RDL1: The class NumberOfUnitsOfUseTrigger does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
      .
  • [EventBasedTrigger]
    Error RDL1: The class EventBasedTrigger does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
    ;
    • [PreOperativeTrigger]
      Error RDL1: The class PreOperativeTrigger does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
      ;
    • [PostOperativeTrigger]
      Error RDL1: The class PostOperativeTrigger does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
      ;
    • [ConditionTrigger]
      Error RDL1: The class ConditionTrigger does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
      ;
    • [FailureTrigger]
      Error RDL1: The class FailureTrigger does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
      .

The respective task trigger should represented as follows:

• operating time trigger - The value of operating time should be represented as Value_limit where Unit should be classified as e.g. [Days]
  Error RDL1: The class Days does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  , [Hours]
  Error RDL1: The class Hours does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  , [Minutes]
  Error RDL1: The class Minutes does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  , [Seconds]
  Error RDL1: The class Seconds does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  etc;
• time scheduled trigger - The value of the scheduled time should be represented as Value_limit where Unit should be classified as e.g. [Years]
  Error RDL1: The class Years does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  , [Months]
  Error RDL1: The class Months does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  , [Days]
  Error RDL1: The class Days does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  , [Hours]
  Error RDL1: The class Hours does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  , [Minutes]
  Error RDL1: The class Minutes does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  , [Seconds]
  Error RDL1: The class Seconds does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  etc;
• number of units of use trigger - The value of the number of units of use should be represented as Value_limit where Unit should be classified as e.g. "Landings" (urn:plcs:rdl:std:Landings), "Rounds" (urn:plcs:rdl:std:Rounds), [OperationCycles]
  Error RDL1: The class OperationCycles does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
  etc;
• pre operative trigger - The description of the pre operative trigger should be represented as String_representation_item;
• post operative trigger - The description of the post operative trigger should be represented as String_representation_item;
• condition trigger; The value of the condition should be represented as Condition being assigned to the
  Error ER-7: The express_ref linkend
  task_specification:arm:Task_specification_arm.Task_assignment
  is incorrectly specified.
  The entity does not exist.
  Note linkend is case sensitive.
  Task_assignment using the C026: representing_condition capability;
• failure - The description of the failure trigger should be represented as String_representation_item.

If the scheduled task triggers allows tolerances, it should be represented as Value_with_tolerances instead of Value_limit as described in the C053: representing_periodicity capability. Task trigger tolerances could be specified for:

• operating time trigger (+/-);
• time scheduled trigger (+/-);
• number of units of use trigger (+/-).

A description of the applicability of the
Error ER-7: The express_ref linkend
task_specification:arm:Task_specification_arm.Task
is incorrectly specified.
The entity does not exist.
Note linkend is case sensitive.
Task being assigned, is represented as a Condition using the C026: representing_condition capability. The parameter describing the condition should be represented as Condition_parameter. Examples of condition parameters are:

• Operational requirement - Should be represented as a typical environment using the C043: representing_environment_typical capability. Examples of classes of typical environments are:
  • [Peacetime]
    Error RDL1: The class Peacetime does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
    ;
  • [Wartime]
    Error RDL1: The class Wartime does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
    ;
  • [InternationalOperation]
    Error RDL1: The class InternationalOperation does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
    .
• Operating state - Should be represented as a State_definition using the C007: representing_state_type capability. Classes of C007: representing_state_type that could be used to describe operating states are:
  • [Operating]
    Error RDL1: The class Operating does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
    ;
  • "Standby" (urn:plcs:rdl:std:Standby);
  • [Storage]
    Error RDL1: The class Storage does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
    ;
  • [ColdShutDown]
    Error RDL1: The class ColdShutDown does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
    ;
  • [HotShutDown]
    Error RDL1: The class HotShutDown does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
    .
• Product configuration - Should be represented as Product_configuration using the referencing_product_configuration
  Error C1: Capability referencing_product_configuration not in dex_index.xml
  capability.
• product version - Should be represented as Product_version using the referencing_part_or_slot
  Error C1: Capability referencing_part_or_slot not in dex_index.xml
  capability.

How to perform

Document references are represented as a Document or a Document_version being assigned to the
Error ER-7: The express_ref linkend
task_specification:arm:Task_specification_arm.Task
is incorrectly specified.
The entity does not exist.
Note linkend is case sensitive.
Task using the Document_assignment as described in the referencing_documents
Error C1: Capability referencing_documents not in dex_index.xml
capability. The Document or Document_version is identified by its Identification_assignment.

Notes

Notes can be made for any record in the maintenence plan as needed. This is represented as a String_representation_item and is assigned to a
Error ER-7: The express_ref linkend
task_specification:arm:Task_specification_arm.Task_assignment
is incorrectly specified.
The entity does not exist.
Note linkend is case sensitive.
Task_assignment by Activity_property as described in the C077: assigning_process_properties capability. The Activity_property should be classified as "Note" (urn:plcs:rdl:std:Note).