[1] Oxford English Dictionary, .

[1] Oxford English Dictionary, .

[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004.

NOTE    Note 1: Performance attributes include

• quantity (how many or how much)
• quality (how well)
• coverage (how much area, how far)
• timeliness (how responsive, how frequent)
• readiness (availability, mission/operational readiness)

Note 2: Performance is an attribute for all systems, people, products and processes including those for development, production, verification, deployment, operations, support, training and disposal. Thus, supportability parameters, manufacturing process variability, reliability and so forth, are all performance measures.

[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004.

NOTE    A performance report may include:

• a report on progress achieved in relation to the support engineering program
• achievement v predictions v requirements in terms of the support metrics applicable to a given support solution
• observations on the performance v expectations in regard to identified support objectives- observations on the ability of the PIF and its support solution to meet expectations of operators and support personnel

[1] PLCS Activity Model, 2000.

[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004.

[1] Oxford English Dictionary, .

[1] PLCS terminology dictionary, 2000.

[1] PLCS terminology dictionary, 2000.

NOTE    The PIF scope establishes a common boundary for:

• the life cycle Configuration Management activity
• the information management rules
• the set of related support solutions drawing from a common task library.

PIF scope should be defined in sufficient detail to identify which products will require support, both at the design and realized level, and to indicate the required level or depth of support to be provided.

[1] PLCS Activity Model, 2000.

NOTE    The PIF Structure comprises:

• the individual structures (eg functional, physical, zonal, other) for the product design and the realized product, including effectivity statements on the current, required and permitted configurations of each individual planned or realized product
• relationships between structures that the information rules require (eg functional-to-physical links and physical to zonal links for both design and individual structures)
• identification of interfaces between elements

These structures are built from elements, which have been identified and classified.

[1] PLCS Activity Model, 2000.

Each task may be supported by a task description or task procedure, and by a task resource model. Task may be related to relevant support drivers and assigned to relevant product groups, versions, support locations, support opportunity type or class of task.

NOTE    The PIF task set may include tasks that are not used by any support solution (eg commissioning tasks and tasks that are defined but are not selected for use when a support solution is developed).

[1] PLCS Activity Model, 2000.

[1] PLCS terminology dictionary, 2000.

[1] PLCS terminology dictionary, 2000.

NOTE    Establish which elements(s) of the PIF are to be changed, including both production and retrofit as necessary. There are many influencing factors including an assessment of the urgency/priority of the change and the availability of parts and materials, software and spares. Determining an effectivity requires knowledge not only of the lead times associated with changing the product (whether in production or by retrofit, recall or other means) but of the actions and lead times necessary to effect the associated change in all impacted support areas (such as the update of support software, availability of spare and repair parts, or revision to operating and maintenance instructions). Once the change is approved detailed implementation planning, which expands but remains consistent with the basic planning is normally required. Implementation of a change involves the release of new or revised configuration documentation including requirements and design information. It may involve changes to information on; operation and maintenance, build and test, and commercial documentation. The new or revised information is identified and released (via AAM CM A133). The release process collates the document revisions to the change(s). It is not always necessary to have a plan before a change task can be authorised, however a change implementation plan is always needed.

NOTE    The plan established under AAM CM A11321 is further embellished by the inputs from impact assessments in respect the effectivity of the change and any other additional work that establishes it as a quantified change. Plan the implementation of the change by establishing which existing and intended items will be changed (effectivity), i.e. the point in production at which the change will take effect and to determine for which units already in production or in service retrospective action is required. Related change tasks will be identified in this plan.

NOTE    The plans and schedules must enable allocation of resources for the tasks to be carried out and must enable monitoring of progress against the plan. The plans are to be based on the decision taken concerning the introduction point and effectivity of the change. It will cover both production embodiment and retrospective embodiment, before or after the delivery of the product as appropriate. An approved change is planned and scheduled for implementation in all documents, facilities, hardware and software impacted change. The implementation is carried out in accordance with the plan. Implementation of a change involves the release of new or revised configuration documentation (APSI) including requirements and design information. It may involve changes to operation and maintenance information, build and test information, and sales information (such as catalogues, marketing literature). The new or revised information is identified and released as APSI. The release process should correlate the document revisions to the change, or changes, incorporated. A common method of disseminating document change is by means of document change notices, which establish a permanent record of specific changes and facilitates distribution.

[1] PLCS Activity Model, 2000.

NOTE    Maintenance plans and schedules have specific planning horizons such as annual, quarterly, monthly, weekly, and daily. Each schedule is a subset of the larger time period covered under the plan. Maintenance tasks are scheduled against a specific products/equipment in focus. The maintenance schedule contains all scheduled jobs and tasks, beginning/completion trigger event such as time, cycles, hours, lists specific resources and locations as to where the work package, job, or task will be accomplished.

[1] PLCS terminology dictionary, 2000.

[1] PLCS terminology dictionary, 2000.

NOTE    The basic planning for implementation of the change is accomplished during the change evaluation before the change is approved. The level of detail required in the plans and schedules will be dependent upon the change complexities in respect to the interrelated change activities across the whole business scenario. A change development plan is established and becomes an input to the business solution assessment

[1] PLCS terminology dictionary, 2000.

1. The project developing ISO 10303-239.
2. The name of ISO 10303-239 (published by ISO in 2005).

[1] DEXlib definitions, .

NOTE    The skeletal PIF structure, produced by activity AAM CM A122, is populated with the product information [could simply be in the form of a Bill Of Material (BOM)]. All relevant interfaces and interchangeability (ICY) information will be aligned the elements. The relevant product and support information for the PIF is attached. All this becomes the set of Product and Support Information (PSI) for that PIF.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

NOTE    The product state may include predictions of anticipated faults.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

NOTE    Preliminary assessments are documented so that the implications of implementing the proposed change can be considered by both the CM team who are documenting the change and external authorities who will need to assess the implications to the operational scenario. A change proposal may be stopped as a result of the preliminary assessment.

[1] PLCS terminology dictionary, 2000.

[1] PLCS terminology dictionary, 2000.

NOTE    Note 1: Procedures may be documented or not.

Note 2: When a procedure is documented, the term "written procedure" or "documented procedure" is frequently used.

[1] ISO 9000, Quality Management System - Fundamentals and vocabulary

NOTE    Note 2: Processes in an organization typically are planned and carried out under controlled conditions to add value.

Note 3 : A process where the conformity of the resulting product cannot be readily or economically verified is frequently referred to as a "special process".

[1] ISO 9000, Quality Management System - Fundamentals and vocabulary

[1] PLCS terminology dictionary, 2000.

NOTE    Encompasses all activities to incorporate the change in the information databases affected by the change eg models, process sheets, operating manuals, service/ maintenance manuals. The change may involve the creation of completely new documentation or the incorporation of changes in already existing documents. In all cases the documents are to be identified according the applicable document identification and issue rules. This activity is triggered by feedback from the various activities identified in the implementation and verification plan. It can also be also triggered by a agreed Variance. Once all activities specified by a change order are completed the task is closed.

NOTE    Synonym to equipment.

Examples:

• facilities
• systems
• hardware
• software
• firmware
• data
• processes
• materials
• services

[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004.

NOTE    There are four agreed generic product categories:

• Hardware (eg engine mechanical part)
• Software (eg computer program)
• Services (eg transport)
• Processed materials (eg lubricant)

Hardware and processed materials are generally tangible products, while software or services are generally intangible. Most products comprise elements belonging to different generic product categories. Whether the product is then called hardware, processed material, software or service depends on the dominant element.

Example: The offered product "car" consists of hardware (eg the tyres), processed materials (eg. fuel, cooling liquid), software (engine control software, the driver's manual), and service (eg the payment facilities or the guaranty).

[1] ISO 9000, Quality Management System - Fundamentals and vocabulary

NOTE    This information includes:

• product design
• product performance
• predicted failures
• diagnostic data
• descriptions
• drawings
• manufacturing records
• other product characteristics of relevance to support
• descriptions of people and organizations

In addition, this information may include the operating and maintenance history of individual acquired items if relevant to future support.

This arrow does not include information about the support solution.

[1] PLCS Activity Model, 2000.

NOTE    After release this information becomes Assured Product and Support Information (APSI).

Abbreviation: PSI

[1] PLCS terminology dictionary, 2000.

[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004.

NOTE    This includes operating and fault states, expected values of measurable parameters, and relationship of symptoms to possible causes.

[1] PLCS Activity Model, 2000.

NOTE    Product configuration information includes product definition information and supplementary types of information (eg operating procedures, maintenance procedures, disposal methods) necessary to support all phases of the products life cycle. It does not consist of project or administrative types of information (eg cost, schedule, and planning)

[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004.

NOTE    Includes design data, drawings, product structure etc. This information will have been subject to configuration management throughout the design, development and production phases of the PIF life cycle. Combined with the Support solution this becomes Assured Product and Support Information (APSI).

NOTE    Product definition information may include futher information derived from the product definition information and made subject to configuration management (eg operating procedures, maintenance procedures, disposal methods).

Examples:

• specifications
• drawings
• source code

[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004.

[1] PLCS Activity Model, 2000.

NOTE    This may include:

• the duration of deployments
• the intended frequencies, duration (time and distance) , profile and nature of operating periods
• the anticipated physical and climatic environments in which usage is expected to occur

A product group may have several usage profiles, including a prediction of the percentage of time for which each may apply.

NOTE    This may include:

• the duration of deployments
• the intended frequencies, duration (time and distance) , profile and nature of operating periods
• the anticipated physical and climatic environments in which usage is expected to occur

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

NOTE    These identifiers may include a supplementary identifier used to distinguish one of several sequentially created configurations of a product from the previous configuration of the same product (i.e. revision or version).

[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004.

[1] PLCS terminology dictionary, 2000.

NOTE    Eg an aircraft by tail number.

[1] PLCS terminology dictionary, 2000.

[1] PLCS terminology dictionary, 2000.

[1] PLCS terminology dictionary, 2000.

NOTE    Eg running, standby.

[1] PLCS terminology dictionary, 2000.

NOTE    Eg product instance run hours, gun firings, deck landings.

[1] PLCS terminology dictionary, 2000.

NOTE    The absence of a response to such exceptions may prevent release of the product to service. Product integrity exceptions may lead to an extension of the support solution.

[1] PLCS Activity Model, 2000.

[1] PLCS terminology dictionary, 2000.

1. The project developing ISO 10303-239.
2. The name of ISO 10303-239 (published by ISO in 2005).

[1] DEXlib definitions, .

NOTE    The product needing support may include any realized element of the product-in-focus.

The product needing support may include embedded information of relevance to support activities. This information can take the form of stamped on serial numbers, bar codes, embedded chips, log books or other media carried with the product itself.

[1] PLCS Activity Model, 2000.

NOTE    Includes information about the product configuration, product status and product condition.

Examples: Test results, readings, wear measurements and information derived from embedded capabilities such as built in test or condition monitoring.

[1] PLCS Activity Model, 2000.

NOTE    Report may contain or make reference to:

• the identity and configuration of the realized product
• confirmation of ready for use status
• a date/time stamp
• the organization/location/person authorizing release
• any restrictions/limitations applicable to product instance use (part of information to operators)
• the tasks scheduled and completed

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

NOTE    The state of a product may include the existence of fault, an operational state or a status in relation to recognized steps/stages of a support process (eg awaiting test, ready for dispatch).

[1] PLCS Activity Model, 2000.

[1] PLCS terminology dictionary, 2000.

NOTE    Product use may be quantified against any usage parameter in any operational (usage) state eg life, number of landings, hours spent above 50% power.

Product use records may be contained in, or extracted from, logbooks or electronic record (tapes, discs, etc) provided by operators from the operational product

[1] PLCS Activity Model, 2000.

NOTE    The PIF may include:

• Many versions of the product design
• Many operational products, used by different users in different ways
• Any part of the operational product needing support

-Any support item or infrastructure element that are addressed by a given Support Solution

Abbreviation: PIF.

[1] PLCS terminology dictionary, 2000.

[1] PLCS Activity Model, 2000.

[1] PLCS terminology dictionary, 2000.

NOTE    Note 1: Properties may describe physical attributes, such as mass, pressure, voltage and less tangible attributes such as "mean time between failures".

Note 2: Shape, colour, location and price are also treated as properties.

Note 3: Properties may apply to the environment, a product, a person or an activity.

Synonym to characteristics.

[1] PLCS terminology dictionary, 2000.

[1] PLCS terminology dictionary, 2000.

[1] Oxford English Dictionary, .

[1] PLCS terminology dictionary, 2000.

[1] PLCS terminology dictionary, 2000.