Terms: s | Terminology index |
The terms defined in the terminology dictionary and in the Business DEXs.
safety or support critical issue | |||
Definition: | Issues arising from identification of support drivers that may require action by the Life cycle owner for reasons of safety or critical significance to the delivery of viable support. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
sanction | |||
Definition: |
(1) Authorization and approval from a designated authority or body.
(2) Explicit or official approval, permission, or ratification. |
||
Source: |
[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004. |
||
Version: | 1.1 | ||
Status: | in_business_review |
schedule (n) | |||
Definition: | The timing, sequence and allocation of tasks, resources and events. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 3.1 | ||
Status: | complete |
schedule (v) | |||
Definition: | The process of defining the timing, sequence and allocation of planned tasks, resources and events taking into account related the constraints applicable to specific support opportunities. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
Schedule maintenance tasks | |||
Definition: | This activity integrates the maintenance plan logic and activities, and identifies when the tasks are to begin or be completed. This fits maintenance activities within the operational schedule and support planning information regarding resource requirement availability. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | in_business_review |
scheduled task | |||
Definition: | A task expected or required to be performed on a product needing support during a specific support opportunity. | ||
Synonyms: | task (n) | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 4.1 | ||
Status: | complete |
scheduling problem report | |||
Definition: |
Issues which prevent succesful completion of the commissioning schedule.
NOTE May identify tasks that cannot be scheduled due to constraints from resource availability, operational schedule, or other reasons. |
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
scheme | |||
Definition: |
A declaration of intent to perform one or more actions, or to expect one or more events
NOTE Note 1: A scheme may represent a support solution or support schedule. Note 2: Schemes may also represent any other type of expected events and actions, including those arising from configuration change management. Note 3: Schemes include most types of plans, schedules and to-do lists. |
||
Synonyms: | support schedule, plan (n), configuration change management, support solution, schedule (n) | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 3.1 | ||
Status: | complete |
scheme entry | |||
Definition: |
An entry in a plan or schedule.
NOTE Example: An activity in a plan. |
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
scrap | |||
Definition: |
Action taken on a nonconforming product to preclude its originally intended usage.
NOTE In a nonconforming service situation, usage is precluded by "discontinuance" the service. Examples: Recycling, disposal or destruction. |
||
Source: |
[1] ISO 9000, Quality Management System - Fundamentals and vocabulary |
||
Version: | 1.1 | ||
Status: | in_business_review |
scrapped | |||
Definition: | Discarded as useless. | ||
Source: |
[1] Oxford English Dictionary, . |
||
Version: | 1.1 | ||
Status: | in_work |
security | |||
Definition: | The protection of information and data so that unauthorised persons or systems cannot read or modify then and authorised persons or systems are not denied access to them. | ||
Source: |
[1] ISO/IEC 12207, Information technology -- Software life cycle processes , 2004. |
||
Version: | 1.1 | ||
Status: | in_business_review |
Select maintenance activities | |||
Definition: |
This activity selects specific product instance tasks for carrying out specific jobs or tasks in a maintenance activity to
meet maintenance objectives taking into account maintenance status and scheduling problems.
NOTE Maintenanceactivities detect and resolve actual or potential shortfalls in functional capability, e.g. detect and diagnose failure, inspect, test, strip, assembly, modify, calibrate, perform operational and support tasks (eg fuel). |
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | in_business_review |
selected change | |||
Definition: | The change solution, complete with the coordinated impact assessments, which has been selected. This allows the change to be evaluated for effectivity and cost implications and work to plan change tasks can be initiated. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.2 | ||
Status: | in_business_review |
selected change | |||
Definition: | The change solution complete with coordinated impact assessments. | ||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | in_business_review |
selected commissioning task | |||
Definition: | An activity required to establish a viable support system, capable of applying a support solution that shall be included in the commissioning schedule. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
selected support provider | |||
Definition: | The organization, or organizations, selected to perform scheduled tasks. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
sequencing | |||
Definition: |
The definition of order, taking into account dependencies and other constraints.
NOTE Successor and predecessor relationships are developed in a network format. This allows those involved in a project to visualize the work flow. |
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
serviceable conditions | |||
Definition: | Ability to render service. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
severitiy | |||
Definition: | The severity of the effect of the failure/defect. | ||
Source: | ![]() |
||
Version: | 1.1 | ||
Status: | in_work |
skill | |||
Definition: | Expertness, practised ability, facility in an action (dexterity or tact) | ||
Source: |
[1] Oxford English Dictionary, . |
||
Version: | 1.1 | ||
Status: | in_work |
software | |||
Definition: |
Intellectual product consisting of information on a support medium
NOTE Note 1: Software can be in the form of concepts, transactions or procedures. Note 2: A computer program is an example of software. |
||
Source: |
[1] ISO 9000, Quality Management System - Fundamentals and vocabulary |
||
Version: | 3.1 | ||
Status: | complete |
solution definition report | |||
Definition: | Definition of a potential solution plus recommendations for further work required to complete assessment of this option. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
solutions/impact reports | |||
Definition: | Definition of the solution plus information to enable the decision to proceed with design, development or implementation of the change. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.2 | ||
Status: | in_business_review |
solutions/impact reports | |||
Definition: | Definition of the solution plus information to enable the decision to proceed with design, development or implementation of the change. | ||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | in_business_review |
special to type tool | |||
Definition: | ?? | ||
Synonyms: | tool | ||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | in_work |
specification | |||
Definition: |
Information stating requirements.
NOTE A specification may be related to activities (eg process specification and test specification), or products. (Eg a product specification, performance specification and drawing). |
||
Source: |
[1] ISO 9000, Quality Management System - Fundamentals and vocabulary |
||
Version: | 1.1 | ||
Status: | in_business_review |
standard commercial transaction set | |||
Definition: |
Set of standardized business transactions that execute requests for the provision of resources, and provide responses on their
expected delivery.
NOTE These transactions can include:
|
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
state | |||
Definition: | A state is the condition in which a thing is. | ||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | complete |
state | |||
Definition: |
A state is the condition in which a thing is.
NOTE Note 1: A state may be defined, predicted or observed. Note 2: States may apply to the environment, a product, a person or an activity. Note 3: A sequence of states may be used to define stages within a process. Note 4: States are used to define and describe normal and degraded conditions of a product, including operating states and faults. |
||
Source: |
[1] Oxford English Dictionary, . |
||
Version: | 1.1 | ||
Status: | complete |
status | |||
Definition: | A status indicates a "state" in time. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | in_business_review |
status of change task | |||
Definition: | Report on progress of a task from the change development plan. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
STEP | |||
Definition: | ISO 10303 - Product data representation and exchange (abbreviation stands for "STandard for the Exchange of Product model data"). A family of standards for product data exchange. | ||
Source: |
[1] DEXlib definitions, . |
||
Version: | 1.0 | ||
Status: | in_business_review |
stock | |||
Definition: | A supply or quantity of anything for use. | ||
Source: |
[1] Oxford English Dictionary, . |
||
Version: | 1.1 | ||
Status: | in_work |
stock level | |||
Definition: | The quantity of a specific stock. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | in_work |
subassembly | |||
Definition: |
A further decomposition of an assembly.
NOTE Has both parents and children. Synonym to middle item. |
||
Synonyms: | middle item | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
subsystem | |||
Definition: | A system that is part of a larger system. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
suggestion for improvement | |||
Definition: |
Suggestions to improve the support solution or product-in-focus.
NOTE This equates to change request for CM and could include changes to IM rules. |
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
supplier | |||
Definition: | The reference to the organization supplying the product instance or service. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | in_work |
supply | |||
Definition: | Provide or furnish a thing needed. | ||
Source: |
[1] Oxford English Dictionary, . |
||
Version: | 1.1 | ||
Status: | in_work |
support (n) | |||
Definition: | The actions carried out to support the product-in-focus. | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 3.1 | ||
Status: | complete |
support (v) | |||
Definition: |
Establish, retain, preserve and change the functional capability of the product-in-focus.
NOTE Includes commission, maintain, modify, pack, transport, store and manage resources. |
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
support characteristic | |||
Definition: | A quantifiable parameter used to define an aspect of support system performance. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
support characteristic clarification request | |||
Definition: | Requests back to the stakeholders for clarification of required support characteristics. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
support data | |||
Definition: | Not used by PLCS. | ||
Synonyms: | support information | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 3.1 | ||
Status: | complete |
support driver | |||
Definition: |
Identification and description of a justified need for support activity.
NOTE Consists of predicted product failure or degradation, safety drivers (legal and others), environmental drivers or operation and readiness drivers. Also includes requirements for tasks to collect the information needed to assess support performance. |
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
support element | |||
Definition: |
Support elements are the physical items required to sustain product capability.
NOTE Support elements include:
In this activity model fixed support infrastructure is shown as a resource. |
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 3.1 | ||
Status: | complete |
support element status record | |||
Definition: |
Observations on the condition, measured property or status of a support element, which has been, or is being used, as a resource
for a task.
NOTE Possible states include:
|
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
support engineering objectives | |||
Definition: |
Objectives to be met by the support engineering program.
NOTE May use AP233. |
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
support engineering schedule | |||
Definition: |
A schedule that defines the processes (activities), procedures (task specifications) and resources required to develop a support
solution which meets the support engineering objectives and the support solution requirement, within the constraints specified
by the Life cycle directives and Change directives.
NOTE It includes:
|
||
Synonyms: | life cycle directive, change directive | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
support environment | |||
Definition: |
The environment, in which support is undertaken, described in ways that influence the work or working methods.
NOTE Eg changing a wheel by a roadside v changing a wheel in a workshop. |
||
Synonyms: | deployment environment, operating environment | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
support equipment | |||
Definition: | Equipment required to maintain an item, system, or facility in its operational status, including related computer programs. | ||
Synonyms: | support element | ||
Source: |
[1] Def Stan 00-60, The United Kingdom Ministry of Defence Standard for Integrated Logistic Support |
||
Version: | 1.1 | ||
Status: | in_business_review |
support feedback | |||
Definition: |
Information on the condition or usage of a product receiving support and on the execution of support activities.
NOTE Support feedback is generated when tasks are performed on a product needing support. It includes information on:
|
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
support impact on design | |||
Definition: |
The proposals generated by support engineering, to influence the design of a product or related support elements.
NOTE Support impact on design includes influence on the product design (from the support perspective) and plus statements of requirement for the design of support items. |
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 3.1 | ||
Status: | in_business_review |
support improvement opportunity | |||
Definition: | An opportunity to improve the performance of a support solution, which may warrant investigation as part of the support engineering program. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
support information | |||
Definition: | The information needed to provide support to an operational product, in accordance with a support solution. | ||
Synonyms: | support data | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
support information rules | |||
Definition: |
Information models, reference data and rules that specify for the PIF how support information shall be collected and stored
to achieve efficient management of support delivery.
NOTE Note 1: Requirements to capture specific information may be included in task procedures. Note 2: This activity model assumes that:
|
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
support infrastructure | |||
Definition: |
Permanent installation providing one or more functional capability needed to provide support.
NOTE Synonym to facility. |
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
support issue | |||
Definition: |
A request for action to resolve a problem arising from working on a product needing support
NOTE May include requests to modify the product or support solution. |
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.2 | ||
Status: | complete |
support item | |||
Definition: |
Any product used in providing support.
NOTE See: consumables, part, repairable, tool, test equipment, facility. |
||
Synonyms: | consumable, tool, test equipment, repairable (n), facility, part (1) | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 5.1 | ||
Status: | complete |
support location capability | |||
Definition: | The capability of the one or more support organizations at a given location, expressed in terms of their ability to undertake classes of tasks within a support solution. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
support metric clarification request | |||
Definition: | Request for clarification of a support metric proposed by a stakeholder. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
support opportunity | |||
Definition: |
An opportunity to perform work on a product needing support.
NOTE Support opportunities may have dates, time and location. They may also have priorities and readiness requirements. Support opportunities may apply to any combination of operational products, parts of product, and to support elements. Support opportunities may arise whilst the operational product is in use. Example: Ship on passage. |
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 3.1 | ||
Status: | complete |
support opportunity (2) | |||
Definition: |
An occasion on which work can be done on one or more realized products or support elements.
NOTE Includes which realized products or support elements will be available, for how long, at what location (or possible locations) and under what conditions. It may also specify the planned future usage of the product or support elements to assist identification of necessary tasks. |
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
support opportunity objectives | |||
Definition: | The objectives applicable to a specific support opportunity. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
support opportunity type | |||
Definition: |
Identification and description of the type of opportunities that may be available when work can be done on a product needing
support.
NOTE Examples:
|
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
support plan | |||
Definition: |
Identification of the tasks required to support a product within a specified deployment environment, including the logic through
which tasks are combined or otherwise related.
NOTE A support plan may include a presentation of a typical maintenance program for a product needing support. It may also specify non-maintenance tasks, such as activities required to provide and prepare required resources. Some necessary tasks may never be implemented if the conditions under which they would fall due, fail to arise (eg a task to correct a rare fault state). |
||
Synonyms: | support solution | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 4.1 | ||
Status: | complete |
support plan option | |||
Definition: | A possible support plan, corresponding to a specific support policy. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
support policy | |||
Definition: | The support policy. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
support prediction | |||
Definition: |
A prediction of the support system performance to be expected when applying a support solution in the context of a predicted
operating or usage schedule and support provider performance. May include predictions on resource consumption, and hence on
provisioning requirements.
NOTE The prediction of some metrics may require assumptions to be made about resource availability and delay times. |
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
support review result | |||
Definition: | Identified needs to change program objectives, strategies or plans. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
support schedule | |||
Definition: |
A schedule for performing one or more support tasks.
NOTE The status of the schedule will change as it develops. The support schedule may include a maintenance schedule defining work to be performed on the product needing support. A support schedule may also define tasks applicable to support elements or required resources (eg calibrate a test instrument). |
||
Synonyms: | schedule (n) | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
support solution | |||
Definition: |
The information required to support a set of products within a deployment environment.
NOTE The support solution may include:
|
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 5.1 | ||
Status: | complete |
support solution requirement | |||
Definition: |
The set of requirements that shall be addressed during the design of a support solution in the context of a deployment environment.
NOTE The requirement may include specified performance metrics for the support solution, with threshold or other tolerance values, defined in terms of agreed support characteristics. May use Application Protocol 233. |
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
support system | |||
Definition: |
The integrated sum of support elements.
NOTE To be updated! How does it fit to support solution? |
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 3.1 | ||
Status: | in_business_review |
support system failure | |||
Definition: | |||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | in_work |
support system release | |||
Definition: | Confirmation that the system required to provide support, as required by a support solution, is in place and ready for use. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
support task | |||
Definition: |
A task that form part of the work required to sustain a product in one or more deployment environments.
NOTE A type of task. Examples:
|
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 3.1 | ||
Status: | complete |
support task exception | |||
Definition: |
Anomalies of actual task against predicted task.
NOTE Examples include:
|
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
support task record | |||
Definition: |
Record of the state of a current or completed task.
NOTE This may include records of completion of individual task steps. |
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
supported product | |||
Definition: | A realized product that is available to the life cycle owner for operational use. | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 1.1 | ||
Status: | complete |
symptom | |||
Definition: |
A symptom is an observed property, or behaviour, of a product, arising, or assumed to arise, from one or more anomalies.
NOTE Note 1: Symptoms
Note 2: The diagnostics process is used to link symptoms to anomaly. |
||
Synonyms: | anomaly (n) | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
system | |||
Definition: |
Has two meanings within PLCS:
(1) A synonym of product. Eg a communication system (2) A subdivision of a product comprising a set of physical items that satisfy a given function (or deliver a capability). Eg the fuel system. |
||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
systems engineering requirement | |||
Definition: | Engineering requirements originating from the User requirements document and Systems requirements document. As the project is developed more detailed information is produced, this along with Support engineering requirements enables the process of configuration identification at all stages of the lifecycle. | ||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | in_business_review |
© OASIS 2010 — All rights reserved