[1] PLCS terminology dictionary, 2000.

[1] PLCS Activity Model, 2000.

[1] PLCS terminology dictionary, 2000.

NOTE    Eg scrap, modification, Missing product instance, Life limit exceeded, Not repairable in time.

NOTE    This may include: users, supporters, developers, producers, trainers, maintainers, disposers, acquirers, supplier organizations, regulatory bodies, members or groups in society, including representatives or designated proxy stakeholders.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

[1] PLCS terminology dictionary, 2000.

[1] Oxford English Dictionary, .

[1] DEXlib definitions, .

[1] DEXlib definitions, .

[1] DEXlib definitions, .

(2) A Variance, which has been rejected because it is not, considered an efficient method of correcting a non- conformance. A configuration change would normally be expected now to correct this variance.

[1] PLCS terminology dictionary, 2000.

[1] PLCS Activity Model, 2000.

NOTE    These rejected issues and changes include:

• issues that will not be taken forward as change orders and for which exists no further planned configuration change management action
• a change for which a need has been established but has been rejected following evaluation. This rejection can be on cost, effectiveness or repercussions.
• a variance that has been rejected on the basis of inefficiency as a method of correcting a non-conformance. Such a non- conformance would usually be corrected by proposing a change.

Rejections should include reasons for rejection.

[1] PLCS Activity Model, 2000.

[1] PLCS terminology dictionary, 2000.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

NOTE    A change proposal would normally be expected following a rejected variance.

[1] PLCS terminology dictionary, 2000.

NOTE    Includes feedback form operations and maintenance.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

NOTE    Release is subject to configuration change management.

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

[1] PLCS terminology dictionary, 2000.

[1] PLCS terminology dictionary, 2000.

NOTE    The PSI is taken through a qualitative/quantitative check to ensure that it is fit for purpose, meeting the specific requirements called for in the change order. When released it becomes Assured Product and Support Information (APSI).

[1] PLCS Activity Model, 2000.

[1] Def Stan 00-49, The United Kingdom Ministry of Defence Standard for Reliability and Maintainability MOD Guide to Terminology Definitions Issue : 1 , 26-Jan-96.

NOTE    The potential failures are then analysed to decide whether a corrective or preventive maintenance task would be most appropriate.

Abbreviation: RCM

[1] MIL-STD-2173, Reliability-centered maintenance requirements for naval aircraft, weapons systems and support equipment (S/S BY MIL-HDBK-2173)

[1] PLCS terminology dictionary, 2000.

[1] PLCS terminology dictionary, 2000.

NOTE    A replacement part commonly economic to repair over a period less or equal to the life of the product to which it is related. It may, however, be disposed of due to circumstances as defined in the support solution.

Synonym to repairable part.

[1] PLCS terminology dictionary, 2000.

NOTE    Synonym to repairable (n).

[1] PLCS terminology dictionary, 2000.

NOTE    Built up of repairables and/or discard parts. May also include consumables and expendables.

[1] PLCS terminology dictionary, 2000.

[1] PLCS Activity Model, 2000.

NOTE    The change request may arise in the contractor or in the customer organization. Initially it may be documented in any format, however it will be given an identifier so that it can be audited and traced by Configuration Status Accounting (CSA). It includes:

• one off requests
• resulting deviations
• concessions
• waivers

All of these will follow the same decision process.

[1] PLCS terminology dictionary, 2000.

[1] PLCS Activity Model, 2000.

NOTE    Requests may arise from

• new product concepts
• developing breakdowns of existing products
• changes

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

NOTE    May include:

• proposal to change the resource provision related to a given task
• proposal to change the support solution
• requests to relax support solution requirements
• proposal to change the product
• requests for additional data from existing source or for new data sources

[1] PLCS Activity Model, 2000.

NOTE    May include request for additional information to support change action, or the deferral of change action to a later date.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

NOTE    May include reports of deferred tasks or requests for additional activities that should be considered for inclusion in a subsequent revision of a support schedule.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

NOTE    Arrow Note: Also captures the formal requirements and specifications for design, modification and/or acquisition of new or critical support items. Contains requests for information on support cost and lead time for products that are provided, maintained or modified inside their own life cycle, such as repairable components that are replaced on the product-in-focus.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

NOTE    May result from requirements to improve reliability, maintainability, redundancy, durability, sustainability or product life.

Requests to embed may seek to incorporate capability within the product for prognostics, diagnostics, condition monitoring, built in test, safety or environmental protection that are needed for support reasons.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

NOTE    These include:

• requests for action to develop support items
• requests for information
• proposals for changes to the product requirement, allocated support requirements, product design or life cycle directives to reflect support needs

Changes resulting from such requests will re-enter the model as configuration management issues.

These requests may result from supportability analyses, assessments or experience.

Examples include:

• support requirements and constraints on design
• standardization requirements
• needs for embedded support capability such as built in test or condition monitoring capability
• requests for design change to meet support needs
• supportability test requirements
• design discrepancies identified during operational use or support
• requests for cost and feasibility information on alternative support elements and influences on existing support infrastructure, to meet a supplied specification

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

NOTE    Note 1: May include legal requirements, business goals and organization policy that shall be taken into account when designing the support solution.

Note 2: Such requirements may conflict with allocated support requirements. Conflicts are resolved in A223.

Note 3: May use AP233.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

NOTE    Note 1: May include:

• requests to designers to assess the feasibility of changing the product to improve supportability
• requests to investigate the feasibility of changing the product design to meet support solution requirements (eg to improve reliability or prevent a specific failure mode)
• notification of potential health, safety and environmental risks identified by the task analysis that may require design activity

- notification of constraints imposed by support activity on the intended use of the product

• requests for action to identify or modify existing resources required by tasks
• requests for the provision of new resource capability

Note 2 : All of the above can be communicated by Work Requests. Work requests may be supported by requirement statements, or specifications for required resources.

Note 3: May use AP233.

[1] PLCS Activity Model, 2000.

(2) Need or expectation that is stated, generally implied or obligatory.

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

[1] PLCS terminology dictionary, 2000.

NOTE    Note: The assignment may specify dates, organisations and locations.

[1] PLCS terminology dictionary, 2000.

NOTE    Identifies task and/or resource imbalance or deficiency that may justify a reassessment of the resource aspects within a task analysis.

[1] PLCS Activity Model, 2000.

NOTE    The scheduling of individual resources is linked to a support schedule

is undertaken in conjunction with defining the resource schedule

[1] PLCS terminology dictionary, 2000.

NOTE    Contains allocation of individual resources (quantity, timing, location, using organisation).

[1] PLCS terminology dictionary, 2000.

NOTE    Usage may be measured by elapsed time, number of starts, cycles of operation or other parameter.

It includes the consumption of spares or consumables; time spent by human resources in performing support tasks and the usage of support locations or facilities.

[1] PLCS Activity Model, 2000.

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

NOTE    Example: Management review, design and development review, review of customer requirements and nonconformity review.

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

[1] PLCS terminology dictionary, 2000.

NOTE    Monitors the approved changes through a planned and scheduled implementation in all documents, facilities, hardware, and software affected. The implementation is carried out in accordance with the Change activity plans (AAM CM A1132). Change accomplishment in all impacted areas is monitored and verified to track progress and to maintain consistency between each unit of the PIF and its applicable configuration and support information (APSI).

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