Terms: i | Terminology index |
The terms defined in the terminology dictionary and in the Business DEXs.
ICOM | |||
Definition: | input, control, output and mechanism. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | — | ||
Status: | — |
IDEF0 | |||
Definition: | a functional modeling language. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | — | ||
Status: | — |
identified element | |||
Definition: |
An element of the PIF with an unambiguous identifier within the context of Product Life Cycle Support.
NOTE An element is any subdivision of the PIF, the Support system or related information to which consistent reference needs to be made. Certain elements will be selected as Configuration items. |
||
Synonyms: | element | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 4.1 | ||
Status: | complete |
identified solution | |||
Definition: | Identification of a potential solution that may satisfy a valid need for change. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
identified support location | |||
Definition: | Identification and description of an intended location or geographical area where support may be required or provided. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
identifier | |||
Definition: | Alphanumeric string assigned to the product for the purpose of identifying the product within a defined context. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
Identify affected CIs | |||
Definition: | Determination of those CIs that will be affected by the possible solutions. | ||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | in_work |
Identify and prioritise change | |||
Definition: |
The identification of change opportunity based on necessity, urgency or impact of the change, to enable various routes of
processing.
NOTE Variations and variances will also be considered by the classificaiton process. A change priority is determined in order to enable adequate subsequent processing. Typical ways of prioritising change are: Class 1, Class 2, Major, Minor. |
||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | in_work |
Identify elements | |||
Definition: | Provide name, ID and owner for all elements of the product (of interest to support of the product) and of the support system. | ||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | in_work |
Identify product structure views | |||
Definition: |
Develop the means of organising the composition of the product.
NOTE The product structure is a representation of the breakdown hierarchy (product tree) from top down to the lowest level. Each level will be able to reference associated configuration documentation such as engineering models, bills of materials, specifications, software requirements, design documents, processes and operating procedures. The fundamentals for a product structure are:
|
||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | in_work |
IM | |||
Definition: | Information Management | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
IM Plan | |||
Definition: | Information Management Plan | ||
Synonyms: | information management plan | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
IM Rules | |||
Definition: | Information Management Rules | ||
Synonyms: | information management rules | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
impact on related changes | |||
Definition: |
Consequences that a potential solution has on other changes that are proceeding in parallel
NOTE Example: Solution 3 to change 5 requires redesign of the interface with Item YYY, which is also subject to Change 8. Change 7 to item XXX must not be implemented unless Change 6 has already been installed. |
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 3.1 | ||
Status: | complete |
impact report on an issue | |||
Definition: | A report on the potential impact of an issue providing an input to a decision on whether to proceed with a change. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
Implement information data release plan | |||
Definition: | Execution of the release process in accordance with a change order. | ||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | in_work |
Implement task | |||
Definition: | The physical performance of released task(s) on the product-in-focus. Implement task includes the complete work process from start to finish, associated data reporting, and return of support element equipment/material resources to their proper location. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | in_business_review |
implementation directive | |||
Definition: |
Describes the resolution applied to the related request.
NOTE An implementation directive may include description of tasks, manpower, facilities, parts, kits, support equipment and money needed to apply the actual resolution. It also identifies the organization responsible for applying the actual resolution and the timetable for completion. |
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | in_business_review |
implementation plan | |||
Definition: | A plan for implementing a solution to a valid need for change. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
inadequate source | |||
Definition: | Request for a change to the assessment strategy, because of available information collection mechanisms cannot provide the required feedback. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
Incorporate impact assessm and dev. change matrix | |||
Definition: |
Incorporate the results of the assessment reports into the change.
NOTE This process can initiate a reassessment as a result of analysing these co-ordinated responses. The output "Potential solutions" must include the justification for the change solutions and the resulting impacts of each solution as well as a reconciliation of requirements and the various impact reports. Justification and reconciliation must be carried out for each of the potential solutions proposed. |
||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | in_work |
individual product state | |||
Definition: |
The expected configuration and condition of an individual product at the start of the support opportunity.
NOTE Arrow Note: This information may be available from the APSI and related information. |
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
information collection requirement | |||
Definition: |
Requirement for an activity to collect assessment information.
NOTE Requirement may be met by:
|
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
information feedback | |||
Definition: |
Information originating either inside or outside the PLCS model that feeds PLCS activities.
NOTE Note 1: Information feedback includes:
Note 2: In combination with other inputs to the CM process, information feedback may, after analysis, prompt the need for a change. It will also assist the process of developing a change from a valid need for change. |
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | in_business_review |
information for reassessment | |||
Definition: | Information that has failed the approval process and requires reassessment. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | in_business_review |
information from other systems | |||
Definition: |
Information on the identity, description or in-service performance of other products or support systems of relevance to the
PIF.
NOTE This information could be supplied in AP239 format, but may only be available on paper or in other non-STEP compliant data formats. |
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
information management plan | |||
Definition: |
A plan for developing, collecting and releasing the information required for product support.
NOTE Note: This includes a control to ensure that the APSI is released in a timely and appropriate manner. Abbreviation: IM Plan |
||
Synonyms: | IM Plan | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 3.1 | ||
Status: | complete |
information management rules | |||
Definition: |
The set of rules and interpretation guidance provided to achieve effective information sharing and exchange across the PIF
scope.
NOTE The information Management rules include:
Abbreviation: IM Rules |
||
Synonyms: | IM Rules | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
information management strategy | |||
Definition: | The intended approach to managing information for a given product in focus. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
information model | |||
Definition: |
A model to define how product and support information shall be structured.
NOTE The information model is one component of the Information Management Rules. |
||
Synonyms: | IM Rules | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
information need | |||
Definition: | Specification of the information that shall be developed and maintained within the APSI for any PIF or support system element or class of elements. | ||
Synonyms: | APSI, PIF | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
information release plan | |||
Definition: |
A schedule defining the timing for the release of assured information.
NOTE The information release plan may specify who needs what information, when, where, in what formats and what media. |
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
information technology service or infrastructure | |||
Definition: |
An IT capability able to provide timely, convenient and effective access to all participants in support activities for entering
and receiving information.
NOTE The activities defined in the model could be performed without this resource but the model was designed to reflect the use of a shared, and integrated, data environment by all participants. The two components which provide this capability are the information technology service or infrastructure (this arrow) and the information management rules. |
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
information to system operator | |||
Definition: |
Information the system operator required regarding the condition of the supported product.
NOTE This information includes:
|
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
information update | |||
Definition: | Minor corrections to the APSI, arising from assessment of issues, or from configuration audits, that does not require formal change action. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
infrastructure | |||
Definition: | System of permanent facilities and equipment of an organization. | ||
Source: |
[1] ISO 9000, Quality Management System - Fundamentals and vocabulary |
||
Version: | 1.1 | ||
Status: | in_business_review |
Initiate impact assessments on each CI | |||
Definition: |
??See OED, c.f.??
NOTE CIs that will be affected by the proposed solutions need the impact of the change assessed. This activity has two outputs:
and
|
||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | in_work |
inspection | |||
Definition: |
Conformity evaluation by observation and judgment accompanied as appropriate by measurement, testing or gauging. [ISO/IEC
Guide 2]
NOTE [ISO/IEC Guide 2] |
||
Source: |
[1] ISO 9000, Quality Management System - Fundamentals and vocabulary |
||
Version: | 1.1 | ||
Status: | in_business_review |
installation | |||
Definition: | The act of installing an instance of a child product instance within a parent product instance. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | in_work |
interchangeable | |||
Definition: |
A product which is capable of being exchanged with another product which has equivalent or similar product attributes without
alteration of the products themselves, or of adjoining products, except for adjustment.
NOTE The interchangeable product is capable of being exchanged for the other product without selection for fit or performance, and without alteration of the products themselves or of adjoining products, except for adjustment. |
||
Source: |
[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004. |
||
Version: | 2.1 | ||
Status: | complete |
interested party | |||
Definition: |
Person or group having an interest in the performance or success of an organization.
NOTE Examples: Customers, owners, employees, suppliers, bankers, unions, partners or society. A group may comprise an organization, a part thereof, or more than one organization. |
||
Source: |
[1] ISO 9000, Quality Management System - Fundamentals and vocabulary |
||
Version: | 1.1 | ||
Status: | in_business_review |
interface | |||
Definition: | The product attributes that exist at a common boundary of two or more products. | ||
Source: |
[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004. |
||
Version: | 1.1 | ||
Status: | in_business_review |
interface control | |||
Definition: | The process of identifying, recording, and managing interfaces. | ||
Source: |
[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004. |
||
Version: | 1.1 | ||
Status: | in_business_review |
interface information | |||
Definition: | The record of an identified interface. | ||
Source: |
[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004. |
||
Version: | 1.1 | ||
Status: | in_business_review |
interval | |||
Definition: |
A period between events.
NOTE An interval may be measured by elapsed time from a start point, or by a number of events (eg landings). |
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
ISO 10303 | |||
Definition: | ISO 10303 is an ISO (http://www.iso.org) standard for the computer-interpretable representation and exchange of industrial product data. Its official title is Industrial automation systems and integration - Product data representation and exchange, and it is also known as STEP or the Standard for the Exchange of Product model data. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.2 | ||
Status: | complete |
ISO 10303-21 | |||
Definition: |
ISO 10303-21:2002, Industrial automation systems and integration —
Product data representation and exchange — Part 21: Implementation methods:
Clear text encoding of the exchange structure.
ISO 10303-21 defines the encoding mechanism on how to represent data in ASCII according to a given EXPRESS schema. See: (http://en.wikipedia.org/wiki/ISO_10303-21) and (http://www.iso.org) |
||
Source: | PLCS OASIS | ||
Version: | — | ||
Status: | — |
ISO 10303-239 | |||
Definition: |
ISO 10303-239 Industrial automation systems and integration — Product data representation and exchange
Part 239: Application protocol: Product life cycle support,
See: (http://en.wikipedia.org/wiki/ISO_10303) and (http://www.iso.org) |
||
Source: | PLCS OASIS | ||
Version: | 1.2 | ||
Status: | complete |
ISO 10303-28 | |||
Definition: |
ISO/TS 10303-28:2003, Industrial automation systems and integration —
Product data representation and exchange — Part 28:
Implementation methods: XML representations of EXPRESS schemas and data.
ISO 10303-28 specifies the use of the Extensible Markup Language (XML) to represent EXPRESS schema (ISO 10303-11) and the data that is governed by those EXPRESS schema. See: (http://en.wikipedia.org/wiki/ISO_10303-28) and (http://www.iso.org) |
||
Source: | PLCS OASIS | ||
Version: | — | ||
Status: | — |
ISO TC 184/SC4 | |||
Definition: |
The ISO sub committee responsible for developing ISO 10303-239![]() |
||
Source: | PLCS OASIS | ||
Version: | 1.2 | ||
Status: | complete |
isolation method | |||
Definition: | The method by which a failure/defect is isolated. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | in_work |
issue | |||
Definition: |
Any problem or proposal related to Configuration Management
NOTE Issues may include:
|
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 3.1 | ||
Status: | complete |
issue requiring change action | |||
Definition: | An issue that, following assessment, is deemed to be worthy of subsequent change action. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.2 | ||
Status: | complete |
item | |||
Definition: | Any of a number of enumerated or listed things. (Oxford Concise) | ||
Source: |
[1] Oxford English Dictionary, . |
||
Version: | 4.1 | ||
Status: | complete |
Item Unique IDentification (IUID) | |||
Definition: | Item Unique IDentification (IUID) is the strategic system implemented buy the DoD to enhance the traceability of the property. It is an asset identification system to uniquely identify a discrete tangible item or asset and distinguish it from other like and/or unlike tangible items. Tangible items are distinguished from one another by the assignment of a unique identifier in the form of a unique data string and encoded in a bar code placed on the item. An item unique identifier is only assigned to a single item and is never reused. Once assigned to an item, the IUID is never changed even if the item is modified or re-engineered. IUID is similar to social security numbering used to distinguish citizens of the United States from one another. See also: (http://en.wikipedia.org/wiki/IUID) | ||
Source: |
[1] DEXlib definitions, . |
||
Version: | 1.0 | ||
Status: | in_business_review |
© OASIS 2010 — All rights reserved