[1] PLCS terminology dictionary, 2000.

NOTE    U.S.A. DoD Access Restriction Codes:

• 2MAN - Two-person access material
• CNWDI - Critical Nuclear Weapons Design Information
• CRYPTO - Cryptographic information
• FRD - Formerly Restricted Data

-NOFORN - Not releasable to foreign nationals

• RD - Restricted Data
• SAR - Special Access Required
• SCI - Special Compartmented Information
• WINTEL - Warning: Intelligence methods and sources disclosed

Normative Ref: DoD 5120.22-M, DoD 5200.1-R (U.S.A. DoD).

2549document-security-access-restriction-text DED0157, document-security-access-restriction-code DED0085.

[1] EIA/ANSI EIA-836, Configuration management data exchange and interoperability

[1] ISO/IEC 12207, Information technology -- Software life cycle processes , 2004.

[1] ISO/IEC 12207, Information technology -- Software life cycle processes , 2004.

NOTE    Action and Activity are synonyms in STEP. Activity is the preferred term at the business level.

[1] ISO 15288, Systems engineering -- System life cycle processes , 2002.

[1] DEXlib definitions, .

NOTE    The STEP equivalent if event_as_realised.

[1] PLCS terminology dictionary, 2000.

NOTE    Note 1: The actual task may diverge from the task description.

Note 2: The equivalent STEP terms are Activity_as_realised (ARM) and Actual_action (AIM).

[1] PLCS terminology dictionary, 2000.

[1] PLCS terminology dictionary, 2000.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

[1] ISO/IEC 12207, Information technology -- Software life cycle processes , 2004.

NOTE    Allocated requirements are typically a subset of the product requirement and may not take into full account of all applicable stakeholders.

[1] PLCS Activity Model, 2000.

[1] Def Stan 05-07, United Kingdom Ministry of Defence Standard 05-57 Issue 4 Configuration Management of Defence Materiel

[1] Def Stan 05-07, United Kingdom Ministry of Defence Standard 05-57 Issue 4 Configuration Management of Defence Materiel

NOTE    This process can be very simple and intuitive it often requires careful weighing of alternatives and cost benefit trade-offs. These preliminary judgements concern:

• The reason for the requested change
• The basic scope and description of the requested change
• The definition of its impact
• The desired effectivity
• Its urgency and importance

[1] PLCS terminology dictionary, 2000.

[1] Oxford English Dictionary, .

NOTE    Note 1: Anomalies includes

• faults (n)
• degradations (n)

Note 2: The need for a modification or upgrade is not treated by PLCS as an anomaly.

[1] PLCS terminology dictionary, 2000.

[1] PLCS terminology dictionary, 2000.

NOTE    Anticipations are the antithesis of extensions, such that they cause a scheduled task to be performed earlier than the scheduled requirement. Like extensions, anticipations are applied to actual product, not generic design. Anticipations must be authorised, but are not associated with a limitation. Records of anticipations and who authorised them must be kept.

[1] PLCS terminology dictionary, 2000.

[1] DEXlib definitions, .

[1] PLCS terminology dictionary, 2000.

(2) Where a system or process is executed within an enterprise (i.e. material handling, design development process, etc.

NOTE    See: software environment

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

See: (http://en.wikipedia.org/wiki/ISO_10303_Application_Modules)

[1] DEXlib definitions, .

[1] DEXlib definitions, .

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

[1] Oxford English Dictionary, .

[1] PLCS terminology dictionary, 2000.

[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 AP239 definition for Assured Product and Support Information corresponds to the EIA 649 term "product configuration information". It includes:

• product definition information that defines the product requirements, documents the product attributes and is the authoritative source for configuration definition
• product operational information, used to test operate maintain and dispose of the product.

Related information may include any content. It includes records of the history of the usage and support of realized products, design and support analysis results and reasons why decisions were taken.

Examples:

• Design and Failure Analysis records
• Logistic Support Analyses
• running hours
• environment
• operating profiles
• test results
• records of maintenance activities
• resources used
• faults found

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

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

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

NOTE    Has both parents and children.

[1] PLCS terminology dictionary, 2000.

[1] PLCS terminology dictionary, 2000.

NOTE    The level of analysis required will be dependent upon the change but will need to take account of facilities, resources (jigs, tooling, people) and other approved changes.

The detailed activities involved in assessing the impact of a change shall lead to determination of:

• Effects on the performance or physical characteristics and interfaces with other products
• The design development and test effort involved
• The modification required to be made to tooling, manufacturing, assembly, installation, and test

-The product documentation revision or replacement required.

• Operating or maintenance instructions or training devices and training materials
• The effect on delivered product (e.g. does it require recall, retrofit, replacement or no action)

-This information is essential to determine effectivity

NOTE    This may include information such as:

• additional maintenance requirements
• limitations on PIF performance within the Support Solution, for example:
  • cautions
  • limitations of speed/altitude or
  • environmental conditions to be avoided
• information of relevance to operators on the readiness of the support system and availability of support elements and services
• information on limitations on availability (time/plans etc)
• any anticipated impact on operational plans from PIF condition, e.g.
  • requirement to do maintenance within specific time
  • inability to do maintenance before a certain time
  • finishing early

[1] PLCS terminology dictionary, 2000.

NOTE    Produces a task for impact assessment, analyses subsequent impact reports and classifies the issues as:

• Requiring change action
• Rejected

-Variances that need to be recorded in the APSI

• Updates to the information set which require no further action

[1] PLCS Activity Model, 2000.

NOTE    May include:

• reports on the support system performance in relation to support objectives or metrics
• recognized deficiencies or proposed improvement to the product or support solution
• issues with the support solution requirement

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

NOTE    May include:

• observations that the strategy for assessment of the support solution is inadequate or unrealistic
• the identification of information sources that do not provide the required information
• reports on inconclusive assessment results due to inadequacies in the assessment method or inadequate information

[1] PLCS Activity Model, 2000.

[1] PLCS terminology dictionary, 2000.

NOTE    Assured Product and Support Information is subject to configuration management.

[1] PLCS Activity Model, 2000.

[1] PLCS Activity Model, 2000.

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

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

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

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

NOTE    Audit evidence can be qualitative or quantitative.

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

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

[1] PLCS Activity Model, 2000.

NOTE    May include configuration records or reports of variance for realized products.

[1] PLCS Activity Model, 2000.

[1] PLCS terminology dictionary, 2000.

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

NOTE    The scope may be expressed in terms of factors such as physical location, organizational units, activities and processes.

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

[1] PLCS terminology dictionary, 2000.

NOTE    Note 1 : The audit team may also include auditors-in-training and, where required, technical experts.

Note 2: Observers may accompany the audit team but do not act as part of it.

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

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

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

NOTE    If authorised to proceed a Change order forimplementation will be issued. If the change is considered non-effective it will be rejected either on price or technicalities. On either rejection a further review can be initiated.

[1] PLCS terminology dictionary, 2000.

[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.