|DEX: (D003) task_set — Task Set||Date: 2010/03/25 17:49:46
This section provides a high level overview of the business information that can be represented by this DEX. A more detailed overview of the information is described in the Task Set: Information Requirements section, and a detailed definition of how the information is represented using ISO 10303-239 PLCS is provided in the Task Set: ISO 10303-239 Representation section.
The information concerned for a Task Set containing two specifications of the task related information is summarized in Figure 7 below.
The information exchanged is contained within a message (Task Set) that is sent to the recipients. The message contains one or more specifications of the task related information, each separately identified, containing the following:
The product in scope for a specification of the task related information. Can be either a part, or an element in a logical breakdown structure of a defined end item. Each specification of the task related information will relate to one product.
The maintenance task being specified, which is a defined maintenance procedure that is to be performed on a defined product. A message may have several maintenance tasks.
Are used to subdivide the maintenance task if the procedure if the procedure can and would benefit from being split. This might be necessary if (upon analysis) the procedure contains other types of procedures which may be repeated by themselves; if it requires the item to be removed from the end item during the procedure, before the rest of the procedure can be carried out; if different resources are required at different times within the procedure etc.. See the section on Task Structure for more guidance on this.
A task may need a set of resources in order to execute the task. Needed resources may include:
Resources may be specified, they may have properties and documents attached, and they can be realized as products.
A task trigger describes the conditions which may cause a task to be executed.
The task effectivity describes the possible validity constraints of the task to a specific context, e.g. a product variant or configuration, a customer, an operational environment.
© OASIS 2010 — All rights reserved