Terms: c | Terminology index |
The terms defined in the terminology dictionary and in the Business DEXs.
CAD | |||
Definition: | Computer Aided Design | ||
Source: | PLCS OASIS | ||
Version: | — | ||
Status: | — |
Capability | |||
Definition: |
A description of how EXPRESS entities are used to represent a given concept
(a specific "functionality" or "capability").
It provides guidance and rules on what Entities
should be used to represent a given concept,
how the entities should be related, and what Reference Data![]() |
||
Source: |
[1] DEXlib definitions, . |
||
Version: | 1.0 | ||
Status: | in_business_review |
CCM | |||
Definition: | Configuration Change Management | ||
Synonyms: | configuration change management | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
CDM | |||
Definition: | Configuration and Data Management | ||
Synonyms: | configuration and data management | ||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | in_business_review |
change development plan | |||
Definition: | Plan that identifies and schedules the tasks required to develop a change. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
change development report | |||
Definition: | A report on progress against the Change development plan. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | in_business_review |
change development task | |||
Definition: | A task requested in order to proceed with the development of a change. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 3.1 | ||
Status: | complete |
change directive | |||
Definition: |
Work orders and work requests that result from the configuration change management process.
NOTE Change directives serve as controls on the implementation or investigation of an identified change. Change directives may include: change orders, change tasks, change plans and change requests. |
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 3.1 | ||
Status: | complete |
change justification | |||
Definition: |
Business case for change, including assessment of cost, benefits and risks.
NOTE Acts a s a control when authorizing change. |
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 3.1 | ||
Status: | complete |
change matrix | |||
Definition: | Identification of configuration items affected by change or a group of changes and the relationships between such changes. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
change order | |||
Definition: |
An authority to implement a change to a product and/or its support solution.
NOTE It defines the change and authorizes release of the update to the APSI which will define what work is to be done. It will also specify
|
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
change plan | |||
Definition: |
Information defining the tasks required to implement a potential solution including the required time, resources and budget.
NOTE Includes:
|
||
Synonyms: | change development plan, audit plan | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
change priority | |||
Definition: | A priority, which has been assigned in accordance with information management (IM) rules (and local business rules) to enable adequate subsequent processing. | ||
Synonyms: | IM, information management rules | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
change proposal | |||
Definition: | A proposal to change the configured state of two or more instances of product instance. | ||
Source: |
[1] TRILS, 2000. |
||
Version: | 1.1 | ||
Status: | in_work |
change risks | |||
Definition: | Risk register for change. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.2 | ||
Status: | complete |
change target | |||
Definition: |
The elements of the PIF, of its support system or related information (APSI), that are subject to configuration change.
NOTE A change may have many change targets. |
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
change task | |||
Definition: |
A task related to the development, planning or implementation of a configuration change.
NOTE Note 1: Change tasks may be reflected in an associated change plan. Note 2: Instructions to implement a change are conveyed by a change order. Examples:
|
||
Synonyms: | task (n) | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
characteristics | |||
Definition: |
Distinguishing feature.
NOTE There are various classes of characteristic, such as:
|
||
Source: |
[1] ISO 9000, Quality Management System - Fundamentals and vocabulary |
||
Version: | 1.1 | ||
Status: | in_business_review |
checklist | |||
Definition: |
A detailed list of possible features of the product and its support solution that may be affected by the change, each of which
requires assessment before a change decision can be made.
NOTE The checklist may form part of the life cycle directives. |
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
chosen solution | |||
Definition: | The selected solution which fulfils the life cycle owners change request. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
CI | |||
Definition: | Configuration Item | ||
Synonyms: | configuration item | ||
Source: |
[1] Def Stan 05-07, United Kingdom Ministry of Defence Standard 05-57 Issue 4 Configuration Management of Defence Materiel |
||
Version: | 4.2 | ||
Status: | complete |
classified elements and relationships | |||
Definition: |
An element of the PIF or its support system which has been identified and assigned to one or more classes of element, plus
any relationships between elements which need to be tracked for support purposes.
NOTE Unambiguous identification includes the assignment of a name (for use by humans) and an alphanumeric identifier (for use within computers), which are unique within a context. The context for a name or identifier is the organization, which provides the name and id. Elements may have more than one name/identifier assigned by different organizations. The classification of an element may include a class which helps identify the Assured Product and Support Information that is required for this element type (eg this element is a ships system, therefore we will hold a functional performance statement, a system diagram, a set of system drawings, a test form, an electrical wiring diagram). Relationships may include:
|
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 4.1 | ||
Status: | complete |
classified solution | |||
Definition: |
A potential solution to a valid need for change.
NOTE This includes specification of the intended design change and related impact assessments to be evaluated for effectivity and cost implications and work to plan change tasks can be initiated. |
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
classify elements and interfaces | |||
Definition: |
Categorization of elements used to provide convenient reference in the business context.
NOTE It is assumed that the classification method will also assist in defining information needs. Classification of elements may include: -The selection of Configuration items and Configurationi tem interfaces
??major unit, minor unit and Configurationi tem interfaces are not defined?? |
||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | in_business_review |
classify solution | |||
Definition: | Classifies the chosen solution with respect to the appropriate priority. | ||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | in_business_review |
CM | |||
Definition: | Configuration Management | ||
Synonyms: | configuration management | ||
Source: |
[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004. |
||
Version: | 1.1 | ||
Status: | in_business_review |
CMP | |||
Definition: | Configuration Management Plan | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
Collect data and provide feedback | |||
Definition: | The review, analysis, and processing of data generated for export and updating APSI and related information. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | in_business_review |
Commercial And Government Entity Code (CAGE Code) | |||
Definition: |
A CAGE (Commercial And Government Entity) Code is a five (5) position code that identifies companies doing or wishing to do
business with the Federal Government. The codes are assigned by Defense Logistics Information Service (DLIS). The format of
the code is that the first and fifth position must be numeric. The second, third and fourth may be any mixture of alpha/numeric
excluding I and O. All positions are non-significant.
For details see: (http://www.dlis.dla.mil/cage_welcome.asp)In PLCS it is used as a
Reference Data![]() |
||
Source: |
[1] DEXlib definitions, . |
||
Version: | 1.0 | ||
Status: | in_business_review |
commissioning feedback | |||
Definition: |
Reports on the progress of commissioning activities against the plan. Recommendations for change to the support solution,
the product or the commissioning schedule, arising from commissioning experience.
NOTE This feedback includes:
|
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
commissioning objective | |||
Definition: | An objective to be achieved by the commissioning activity. The objectives may address any phase of the commissioning process including acquisition, construction, testing or certification of support system elements. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
commissioning program logic | |||
Definition: | The logical constraints and relationships applicable to intended commissioning activities. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
commissioning schedule | |||
Definition: |
A schedule showing the intended timing and sequencing of intended commissioning tasks.
NOTE Commissioning tasks are those required to create the support system. |
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
commissioning task | |||
Definition: | |||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | in_business_review |
commissioning task feedback | |||
Definition: |
Data on the progress, resource consumption and issues arising from performing commissioning tasks.
NOTE Information provided to identify trends or potential problems from applying a commissioning solution. |
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
commissioning task metrics | |||
Definition: | Metrics applicable to the performance of commissioning tasks. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
commissioning task request | |||
Definition: | Request for the development of a task specification for a commissioning activity not included in the current PIF task set. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
compile justification for change | |||
Definition: | Review the total change package and complete a justification for the implementation requirements with a recommended classification and priority. | ||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | in_business_review |
completed task | |||
Definition: | Record of successful completion of a task required by a support schedule. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
component | |||
Definition: |
Part of a larger whole, any subdivision of interest.
NOTE Synonym to element. |
||
Synonyms: | element | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 4.1 | ||
Status: | complete |
concession | |||
Definition: |
Authorization to use or release a product that does not conform to specified requirements.
NOTE A concession is typically limited to the delivery of a product that has nonconforming characteristics within specified limits for an agreed time or quantity of product. |
||
Source: |
[1] ISO 9000, Quality Management System - Fundamentals and vocabulary |
||
Version: | 1.1 | ||
Status: | in_business_review |
configuration | |||
Definition: |
(1) The product attributes of an existing or planned product, or a combination of products.
(2) One of a series of sequentially created variations of a product. |
||
Source: |
[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004. |
||
Version: | 1.1 | ||
Status: | in_business_review |
configuration and data management | |||
Definition: |
???
NOTE Abbreviation: CDM |
||
Synonyms: | CDM | ||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | in_business_review |
configuration audit | |||
Definition: |
The CM function that validates a requirement has been fulfilled.
NOTE Examples:
|
||
Source: |
[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004. |
||
Version: | 1.1 | ||
Status: | in_business_review |
configuration baseline | |||
Definition: | The attributes of a product at a point in time, which serves as reference for activities throughout its life cycle. | ||
Source: |
[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004. |
||
Version: | 1.1 | ||
Status: | in_business_review |
configuration change | |||
Definition: | A change to a product and its product configuration information. | ||
Source: |
[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004. |
||
Version: | 2.1 | ||
Status: | complete |
configuration change management | |||
Definition: |
The configuration management activity that ensures that changes to product configuration information are properly identified,
recorded, evaluated, approved, incorporated, and verified.
NOTE The configuration change management activity applies to:
Abbreviation: CCM |
||
Synonyms: | CCM | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 3.1 | ||
Status: | complete |
configuration identification | |||
Definition: | The configuration management activity, which selects, describes and organizes product attributes and assigns and applies identifiers to a product, its components, and its configuration information. | ||
Source: |
[1] ISO 9000, Quality Management System - Fundamentals and vocabulary |
||
Version: | 2.1 | ||
Status: | complete |
configuration information | |||
Definition: |
Information to identify and define a product's attributes.
NOTE Includes but is not limited to
|
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | in_business_review |
configuration item | |||
Definition: |
Item designated for Configuration Management (CM).
NOTE Abbreviation: CI |
||
Synonyms: | CI, CM | ||
Source: |
[1] Def Stan 05-07, United Kingdom Ministry of Defence Standard 05-57 Issue 4 Configuration Management of Defence Materiel |
||
Version: | 2.1 | ||
Status: | complete |
configuration management | |||
Definition: |
The activity that establishes and maintains consistency of a product with its requirements and configuration information throughout
its life cycle.
NOTE Configuration management consists of the five interrelated activities:
Abbreviation: CM |
||
Synonyms: | CM | ||
Source: |
[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004. |
||
Version: | 1.1 | ||
Status: | complete |
configuration management plan | |||
Definition: |
The document that describes the scope of configuration management (CM), the CM organization, and the CM activities for a product
and its support throughout the life cycle of that product.
NOTE The CMP provides details of the processes, schedules and associated toolset for performing Configuration Management including resources and skills. Development of the CMP is not addressed within this AAM but is an integral part of the CM process defined by ISO 10007. Abbreviation: CMP |
||
Synonyms: | CMP, CM | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 4.1 | ||
Status: | complete |
configuration record | |||
Definition: |
A record of the configuration of a realized product.
NOTE Configuration status record may be required following incorporation of a configuration change, the removal of a serialized item, the replacement of a serialized item or the performance of a configuration audit task. |
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
configuration status accounting | |||
Definition: |
The configuration management activity that manages the capture, storage, retrieval and access of product configuration information
necessary to account for the configuration of a product.
NOTE Abbreviation: CSA |
||
Source: |
[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004. |
||
Version: | 3.1 | ||
Status: | complete |
configuration status record | |||
Definition: |
The output of the Configuration Status Accounting (CSA) activity.
NOTE The configuration status record (CSR) is the source of configuration information to support through life program activities including program management, system engineering, manufacturing, software development, logistic support, maintenance and modification. The CSR contains the status information of the Configuration Item (CI) at any stage in its life cycle, including where appropriate, the current version of each CI. Abbreviation: CSR |
||
Synonyms: | CSA, CSR | ||
Source: |
[1] Def Stan 05-07, United Kingdom Ministry of Defence Standard 05-57 Issue 4 Configuration Management of Defence Materiel |
||
Version: | 3.1 | ||
Status: | complete |
configuration verification | |||
Definition: | The configuration change management activity, which verifies that the product has achieved its requirements and is accurately documented. | ||
Source: |
[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004. |
||
Version: | 1.1 | ||
Status: | complete |
conformity | |||
Definition: |
Fulfillment of a requirement.
NOTE This definition is consistent with ISO/IEC Guide 2 but differs from it in phrasing to fit into the ISO 9000 concepts. |
||
Source: |
[1] ISO 9000, Quality Management System - Fundamentals and vocabulary |
||
Version: | 1.1 | ||
Status: | in_business_review |
consequential task | |||
Definition: |
An activity that needs to be included in a schedule as a consequence of another task.
NOTE May include additional tasks required by the proposed activity logic or by resource preparation requirements (eg set up and calibrate a test rig). |
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
consignment | |||
Definition: | The act of changing the configured state of two or more instances of product instance | ||
Source: | ![]() |
||
Version: | 1.1 | ||
Status: | in_work |
Consolidate solution/Impact reports | |||
Definition: |
The merging of solution(s) with the/their impact reports for risk assessment.
NOTE Specialists include: engineering (Design/System/Support), supply chain, production, manufacturing, commercial. |
||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | in_business_review |
constraint | |||
Definition: |
(1) A restriction, limit, or regulation imposed on a product, project, or process.
(2) A type of requirement or design feature that cannot be traded off. |
||
Source: |
[1] EIA/ANSI EIA-836, Processes for Engineering a System , 1998. |
||
Version: | 1.1 | ||
Status: | in_business_review |
consumable | |||
Definition: |
Anything consumed by operation of a product or a support activity.
NOTE Eg fluids, lubricants in general, paints, adhesives, fuel, oil, chemicals, cleaners, solvents, abrasives, metals, fabrics. |
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 5.1 | ||
Status: | complete |
consumed life | |||
Definition: | The portion of product instance life accrued through being used. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | in_work |
consumption | |||
Definition: | The purchase and use of product instance. | ||
Source: |
[1] Oxford English Dictionary, . |
||
Version: | 1.1 | ||
Status: | in_work |
contract | |||
Definition: | See Concise Oxford English Dictionary | ||
Source: |
[1] Oxford English Dictionary, . |
||
Version: | 1.1 | ||
Status: | in_business_review |
Contractual price offer request | |||
Definition: | The offer that is generated subsequent to the authorisation of the change proposal. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | in_business_review |
Contractual requirements | |||
Definition: |
Contractual requirements are the obligations that have to be fulfilled based on the contract.
NOTE Part of life cycle directives. |
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | in_business_review |
Control maintenance | |||
Definition: | An acceptance process to ensure that a released task has been completed in accordance with the maintenance plan?? | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | in_business_review |
correction | |||
Definition: |
Action taken to eliminate a detected nonconformity.
NOTE Note 1: A correction may or may not be made in conjunction with a corrective action. Note 2 : A correction may involve repair, rework or regrade. |
||
Source: |
[1] ISO 9000, Quality Management System - Fundamentals and vocabulary |
||
Version: | 1.1 | ||
Status: | in_business_review |
corrective action | |||
Definition: |
Action taken to eliminate the cause of a detected nonconformity or other undesirable situation.
NOTE Note 1: Corrective action is taken to prevent recurrence whereas preventive action is taken to prevent occurrence. Note 2: There is a distinction between correction and corrective action. |
||
Source: |
[1] ISO 9000, Quality Management System - Fundamentals and vocabulary |
||
Version: | 1.1 | ||
Status: | in_business_review |
cost to repair | |||
Definition: | The total monetary cost to rectify the failure/defect. | ||
Source: | ![]() |
||
Version: | 1.1 | ||
Status: | in_work |
costed change | |||
Definition: | Quantified change with life cycle costs incorporated. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.2 | ||
Status: | complete |
Create information release plan | |||
Definition: |
Ensures that "release dependencies" are collected together in a structured format.
NOTE This ensures that certain product information is released together with (before/after) other product information and only to approved recipients. In an electronic CM model this latter will simply consist of pointers to the modified information sets. |
||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | in_business_review |
Create maintenance plan | |||
Definition: |
Create the maintenance plan is the activity that integrates maintenance activity objectives (maintenance tasks) to be accomplished
and time phasing for all levels of maintenance, including both preventive and corrective maintenance. It includes modelling
for matching maintenance tasks with facility capabilities and availability to produce an authorised maintenance plan.
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. |
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | in_business_review |
Create suggestions for improvements | |||
Definition: | The collection of ideas and comments generated by support personnel to identify opportunities for making the support solution's application efficiency and effectiveness better. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.2 | ||
Status: | in_business_review |
Create suggestions for improvements | |||
Definition: | "Creates suggestions for improvements" collects ideas and comments generated by support personnel to identify opportunities for making the support solution's application efficiency and effectiveness better. | ||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | in_business_review |
CSA | |||
Definition: | Configuration Status Accounting | ||
Synonyms: | configuration status accounting | ||
Source: |
[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004. |
||
Version: | 1.1 | ||
Status: | complete |
CSR | |||
Definition: | Configuration Status Record. | ||
Source: |
[1] Def Stan 05-07, United Kingdom Ministry of Defence Standard 05-57 Issue 4 Configuration Management of Defence Materiel |
||
Version: | 1.2 | ||
Status: | complete |
current configuration | |||
Definition: | The configured state of two or more instances of product instance at a given point in time. | ||
Source: | ![]() |
||
Version: | 1.1 | ||
Status: | in_work |
customer | |||
Definition: |
Organization or person that receives a product.
NOTE Examples:
A supplier can be internal or external to the customer's organization. |
||
Source: |
[1] ISO 9000, Quality Management System - Fundamentals and vocabulary |
||
Version: | 1.1 | ||
Status: | in_business_review |
customer disposition | |||
Definition: |
A lifecycle directive confirming the approval, deferment or rejection of a change by a customer or other external authority.
NOTE The disposition may specify:
|
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
CVS | |||
Definition: | Concurrent Versions System, a revision control system, popular for open source and commercial software development. | ||
Source: |
[1] Wikipedia , . http://en.wikipedia.org |
||
Version: | 1.2 | ||
Status: | complete |
© OASIS 2010 — All rights reserved