Maintenance plan Business Process

AP239 Activity model coverage

An application activity model (AAM) is provided in AP239 as an aid to understanding the scope and information requirements defined in AP239. The model is presented as a set of figures that contain the activity diagrams and a set of definitions of the activities and their data.

This DEX will support a subset of the activities and data flows. These are highlighted in yellow in the subsequent figures.

Activities and data flows that are out of scope of AP239 are marked with an asterisk.

Figure 1 — A24323 Develop Support Plan Logic (In scope)

AP239 Activity model definitions

The following terms are used in the application activity model.

Define task trigger

action to define the logical conditions that require a task to be done within a specific support solution definition and deployment environment, including a justification for the selection of the trigger, with appropriate reference to any analysis process that established the trigger condition

Rationalize tasks & task relationships

action to rationalize the set of necessary tasks and task triggers to develop a viable support plan for each product group, and support concept within a deployment environment

NOTE A further level of rationalization may be required across support plans and resource holdings across many product groups for the PIF as a whole. This activity is not made explicit in this AAM.

task to product relationship

relationship between a necessary task and the product element, or elements to which it applies

task trigger

conditions that require a task to be done, in the context of its assignment to a specific product element within a support solution definition

support solution requirement

set of requirements that shall be addressed during the development of a support solution definition in the context of a deployment environment

NOTE The requirement may include specified performance metrics for the support solution, with threshold or other tolerance values, defined in terms of agreed support characteristics.

deployment environment

context for which a support solution definition is created

NOTE A deployment environment identifies the set of products and defines the operating and support environment to which a support solution definition applies. A deployment environment may relate to the entire product in focus, or to a subset of it. A product in focus may thus give rise to several support solution definitions, each tailored to a different deployment environment.

Error: no icom_inc (support_policy) found in the AP

support plan option

possible support plan, corresponding to a specific support policy

DEX Business application

This DEX enables the transmission of maintenance tasks which are to be performed on a product in order to sustain the required function of the product, together with the conditions under which these maintenance tasks fall due.

The plan is prepared and established based on a Logistic Support Analysis, LSA, including:

Failure analysis of the product (see dex 2 D002: fault_states);
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 maintenance plan will provide input to maintenance scheduling activities (see DEX D004: work_package_definition).

The types of tasks that is within the scope of maintenance plan is visualized in figure 2.

Figure 2 — Tasks within scope of dex 5 Maintenance Plan

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

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.