DEX: (D003) task_set — Task Set | Date: 2010/03/25 17:49:46 Revision: 1.80 |
For the purposes of this specification, the following terms apply:
NOTE Once identified, these areas can be the subject of trade-offs to amend the design in order to reduce these cost drivers.
Abbreviation: LSA
The term "logistic support analysis" has the following synonyms: LSA,
[1] PLCS terminology dictionary, 2000.
NOTE A maintenance task is a type of support task.
Examples:
Remove a replacement part
Investigate a symptom
The term "maintenance task" has the following synonyms: task (plcs), task (n),
[1] PLCS terminology dictionary, 2000.
NOTE Product configuration information includes product definition information and supplementary types of information (eg operating procedures, maintenance procedures, disposal methods) necessary to support all phases of the products life cycle. It does not consist of project or administrative types of information (eg cost, schedule, and planning)
[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004.
NOTE The PIF may include:
Many versions of the product design
Many operational products, used by different users in different ways
Any part of the operational product needing support
-Any support item or infrastructure element that are addressed by a given Support Solution
Abbreviation: PIF.
The term "product-in-focus" has the following synonyms: PIF,
[1] PLCS terminology dictionary, 2000.
[1] PLCS terminology dictionary, 2000.
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.
[1] PLCS Activity Model, 2000.
NOTE The support solution may include:
a listing of relevant support drivers
a support plan, that identifies necessary tasks to respond to these support drivers, and specifies the conditions under which each task falls due
justification for the above
task procedures for necessary tasks
identification and quantification of resources needed to achieve necessary tasks, including types of person with skill level
resource models for necessary tasks
identification of the deployment environment and requirements for which the support solution was designed.
[1] PLCS terminology dictionary, 2000.
NOTE A type of task.
Examples:
Transport a replacement part.
Repair an operational product
[1] PLCS terminology dictionary, 2000.
NOTE Task in PLCS is the designed action, whereas activities are the actual actions.
The term "task (plcs)" has the following synonyms: task (n),
[1] PLCS terminology dictionary, 2000.
NOTE The same task may be supported by several task procedures, each tailored to the needs of a class of users (eg to accommodate different skill levels).
[1] PLCS terminology dictionary, 2000.
NOTE Includes definition of required skills and experience of required support personnel.
[1] PLCS terminology dictionary, 2000.
[1] PLCS terminology dictionary, 2000.
NOTE Note 1: A task specification may include a task objective, a task method (including sequence within the task), task predecessors/successors, pre-/post conditions, required skills/skill levels, required resources, duration and level of effort, applicable constraints, the relationship to the support requirements, etc.
Note 2: The level of detail within a task specification is a business decision.
[1] PLCS terminology dictionary, 2000.
NOTE A task step has a definite start and a definite finish.
The term "task step" has the following synonyms: task specification, task procedure,
[1] PLCS terminology dictionary, 2000.
NOTE Note 1: The type of trigger will vary with the type of task:
Corrective tasks, including diagnostic tasks, are triggered by events (the occurrence of damage, the detection of a failure or a symptom.)
Preventative tasks, including pre-programmed inspections, are triggered by time, life, usage or other conditions (hours run, number of landings, interval, frequency, if frost is expected).
-Operational and servicing tasks are triggered by actual or intended product use (eg tow out of hangar, re-fuel, de-fuel, configure-for-role) .
Note 2: Triggers may include relative conditions eg 4 months after last inspection.
Note 3: If a usage scenario is adequately defined, and if tasks are linked to resources, the task triggers may be used, in conjunction with product reliability data, to forecast resource requirements and support system performance over a given period.
[1] PLCS terminology dictionary, 2000.
Additional terms used in the Help/Information pages.
NOTE These terms are not part of the released specification.
© OASIS 2010 — All rights reserved