PDM-UG: Work Order
From WikiSTEP
This page belongs to the PDM Usage Guide.
Requests for work are processed and result in work orders that direct engineering activities to solve the issues raised by the work request. A work order may address one or multiple work requests.
The work order describes how a particular request for work is addressed and, if authorized, incorporated through appropriate activities during the engineering release or change process. Every work order consists of a work directive (directed in response to a specific work request) and a definition of the work to be done. This work definition represents the main activity defining the work to be completed under a work order, together with a reference to the activity method that identifies the procedure describing how it is to be carried out.
An activity may be associated with status information describing its level of completion. The identification of the items that are the input or the result of an engineering activity that is controlled by a work order is also supported by the STEP PDM Schema.
In addition, person, organization and date and time related information as well as approval information can be attached to an activity.
Contents |
The Instance Model: EXPRESS entities and attributes
The EXPRESS entities and attributes used to support the requirements to represent work order information are illustrated in Diagram 68 below. The corresponding STEP exchange file encoding is given in Example 68.
Diagram 68: Work order Instance Diagram
Action directive
The action_directive entity specifies an authoritative instrument that provides directions to achieve the desired results as specified in some work_request(s). An action_directive is the result of processing one or more versioned_action_requests. It represents the directive for work that must be performed to satisfy the requirements stated by the assessed versioned_action_requests. The work directed by an action_directive is represented by an associated directed_action (see Directed action). The action_directive together with the directed activity defining the work to be completed represents a work order.
Attributes
- The name attribute specifies the identifier used to refer to the action_directive.
- The description attribute specifies additional information about the action_directive.
- The analysis attribute specifies an informal description of the results of the analysis that was carried out on the elements of the versioned_action_requests that are addressed by the action_directive.
- The comment attribute specifies a descriptive label providing some textual commentary.
- The requests attribute specifies the work requests that are addressed by the action_directive.
| ENTITY action_directive | Attribute Population | Remarks |
| name | type: label = text | |
| description | type: text = string | OPTIONAL |
| analysis | type: text = string | |
| comment | type: label = text | |
| requests | type: entity = versioned_action_request | S[1:?] |
===Preprocessor Recommendations=== In the context of the work management area, an action_directive shall be referenced by exactly one directed_action that defines the work that is directed by the action_directive.
The name attribute shall contain a string that, in conjunction with the associated versioned_action_requests, uniquely identifies the action_directive. If an action_directive addresses one particular versioned_action_request, the value of the id attribute of the versioned_action_request may be used to populate the name attribute.
Some types of (release or change) processes in organizations may not involve submission of official work requests. In this case, it is recommended to use the default values for the entities and attributes not supported by the preprocessor as described in the 'General information' section of this usage guide to instantiate the required versioned_action_request.
===Postprocessor Recommendations=== There are no specific postprocessor recommendations.
===Related Entities=== An action_directive may be referenced by the following entities:
- directed_action to specify the work that is being directed by the action_directive, and that addresses the requirements specified in the associated versioned_action_requests. It is strongly recommended that an action_directive has exactly one associated directed_action with name 'work definition'.
Directed action
The directed_action entity represents the work that is controlled by an action_directive, and defined as part of a work order. This is a definition of work that has either taken place, is taking place, or is expected to take place in the future. The work requests that are addressed and incorporated by the directed_action are specified through association to an action_directive.
A directed_action identifies the action_method that describes the method or procedure chosen to carry out the activity. Reference to an action_method that has been identified as a potential solution to a work request (see Action request solution) indicates which procedure or potential solution for a work request has been selected by the work order.
A directed_action may have an associated status representing the level of completion of the work. In addition, it may carry additional information needed to characterize the work defined by the work order, e.g., start or end dates, person and organization related information, and approval authorization information.
A directed_action is related via an applied_action_assignment (see Applied action assignment) to the items that are subject of the work represented by the ‘work definition’ of a work order. This is used to describe the items (e.g., part or document versions, views, or structural relationships between these), which are either input or result from the release or change defined by the directed_action.
It is recommended that exactly one directed_action be used to represent the work being governed by an action_directive. This directed_action may be identified by the name ‘work definition’, and may be further decomposed into sub-activities represented by executed_actions (see Activity decomposition). These sub-activities are related to the work definition (directed_action) through an action_relationship (or a chain of such action_relationships) with name 'decomposition' (see Action relationship). Each sub-activity may have additional information, e.g., start or end dates, person and organization related information, or approvals specifically assigned to it. When many requests are incorporated by one work order using different proposed solutions, the directed_action representing the complete work definition should be decomposed in sub-activities for which the appropriate method is indicated.
Attributes
- The name attribute specifies the word or common name used to refer to the action.
- The description attribute specifies additional information about the action.
- The chosen_method attribute specifies the action_method that defines the procedure selected to carry out the action and a description of the results of the action.
- The directive attribute specifies the action_directive that authorizes and controls the directed_action.
- The id attribute is derived, and may store the unique identifier for a directed_action.
| ENTITY directed_action | Attribute Population | Remarks |
| name | type: label = text | may be ‘work definition’ |
| description | type: text = string | OPTIONAL |
| chosen_method | type: entity = action_method | |
| directive | type: entity = action_directive | |
| id | DERIVEd attribute type: identifier = string | exactly one id may be associated via the entity id_attribute |
===Preprocessor Recommendations=== It is recommended that a directed_action always be related to an action_directive. The name attribute shall be unique in conjunction with the associated action_directive.
If the directed_action representing the ‘work definition’ is broken down in separate sub-activities (see Activity decomposition), it is recommended that this top-level work definition be associated through applied_action_assignment to all input and output items that are defined for the sub-activities.
It is recommended that a directed_action have an associated status, represented by exactly one action_status, which references the directed_action as the assigned_action (see Action status).
The directed_action entity may have an identifier associated with it through the entity id_attribute and its attribute_value attribute.
===Postprocessor Recommendations=== There are no specific postprocessor recommendations.
===Related Entities=== A directed_action may be referenced by the following entities:
- action_relationship to associate two directed_actions or a directed_action and an executed_action, e.g., to define their decomposition relationship, i.e., one action as part of the other, or to describe their dependencies.
- applied_action_assignment to identify the items that are affected by the directed_action.
- applied_approval_assignment to associate authorization information related to a directed_action. See Approval for guidance in creating the approval constructs.
- applied_date_assignment (or applied_date_and_time_assignment) to associate date (and time) information to a directed_action. See Date and Time for guidance in creating the date and time constructs.
- applied_organization_assignment (or applied_person_and_organization_assignment) to associate organization (and person) information to a directed_action. See 13.1 for guidance in creating the organization and person constructs. A recommended value for the name attribute of the person_and_organization_role is 'requestor'.
- applied_contract_assignment to identify that the directed_action is subject of the assigned contract.
Applied action assignment
The applied_action_assignment entity relates an action to the elements of product data that is affected by the action. The applied_action_assignment entity defines a general mechanism to associate an activity that is part of a work order to the items that are affected by the activity.
The types of items to which an activity may be assigned are defined in the action_item select type. Within the scope of the PDM Schema, items that may be affected by an engineering activity are part and document versions (i.e., product_definition_formations), views on these versions (i.e., product_definitions), or structural relationships between these (i.e., product_definition_relationships). The action_item select type as well supports different views of a version of the product and may also include different product configuration_effectivities. For example, a manufacturing configuration represented by the entity configuration_effectivity supports the manufacturing part view requirement for a relationship between an action (Activity) and a manufactured part.
The applied_action_assignment may have a role associated with it through the entity object_role via a role_association. The role specifies the function that is performed by the affected item in the context of the assigned action. Role information may be used to distinguish between items that are used as input or the ones that are the results from the release or change process.
Attributes
- The assigned_action specifies the action that is assigned to the affected items.
- The items attribute specifies the set of items to which the associated action is assigned, i.e., that are affected by the assigned action.
| ENTITY applied_action _assignment | Attribute Population | Remarks |
| assigned_action | type: entity = action | |
| role | DERIVEd attribute type: entity = object_role | OPTIONAL |
| items | type: entity = action_item select | SET[1:?] |
===Preprocessor Recommendations=== If the applied_action_assignment has a role associated with it through the entity object_role, the name attribute of the object role should use the following values where applicable: ’input’ should be used to indicate that the referenced item serves as initial data for the assigned action; ’output’ should be used to indicate that the referenced item is a result of the assigned action. If no role is given, it is assumed that the applied_action_assignment identifies items that are the result of carrying out the assigned action (e.g., ‘output’).
If a directed_action defining the complete work under a work order is further decomposed in sub-activities, then all affected items identified as input or output of the sub-activities should be explicitly associated to the top-level directed_action.
===Postprocessor Recommendations=== If the applied_action_assignment has no role associated with it, it shall be assumed that the items referenced by the applied_action_assignment are the result of carrying out the assigned action.
===Related Entities=== An applied_action_assignment may be referenced by the following entities:
- role_association to specify an object_role defining the role of the assignment.
The Instance Model: STEP exchange file format (ISO10303 Part 21 syntax)
#1=VERSIONED_ACTION_REQUEST('var id1', '0001', 'create new part design', '$');
#2=VERSIONED_ACTION_REQUEST('var id2', '0001', 'technical improvement', 'description of var id2, 0001');
#4=ACTION_REQUEST_STATUS('in-work', #1);
#5=ACTION_REQUEST_STATUS('issued', #2);
#8=ACTION_METHOD('activity method 1', $, 'effects of activity method 1', 'objectives of activity method 1');
#9=ACTION_METHOD('technical improvement method 1', $, 'effects of technical improvement method 1', '$');
#10=ACTION_METHOD('technical improvement method 2', $, 'effects of technical improvement method 2', '$');
#13=ACTION_REQUEST_SOLUTION(#8, #1);
#14=ACTION_REQUEST_SOLUTION(#9, #2);
#15=ACTION_REQUEST_SOLUTION(#10, #2);
#16=APPLICATION_CONTEXT('mechanical design');
#100=PRODUCT_RELATED_PRODUCT_CATEGORY('part', '', (#380, #440, #542));
#220=PRODUCT_CONTEXT('', #16, '');
#230=PRODUCT_DEFINITION_CONTEXT('part definition', #16, 'design');
#340=PRODUCT_DEFINITION_CONTEXT_ROLE('part definition type', $);
#350=PRODUCT_DEFINITION_CONTEXT('assembly definition', #16, '');
#380=PRODUCT('g1', 'gasket', $, (#220));
#390=PRODUCT_DEFINITION_FORMATION('A', '', #380);
#400=PRODUCT_DEFINITION('gv1', 'design view on gasket', #390, #230);
#440=PRODUCT('s1', 'sleeve assembly', $, (#220));
#450=PRODUCT_DEFINITION_FORMATION('A', '', #440);
#460=PRODUCT_DEFINITION('sv1', 'design view on sleeve assembly', #450, #230);
#520=PRODUCT_DEFINITION_CONTEXT_ASSOCIATION(#460, #350, #340);
#530=NEXT_ASSEMBLY_USAGE_OCCURRENCE('gu1', 'single instance usage', 'gasket usage 1', #460, #400, $);
#531=APPLIED_ACTION_REQUEST_ASSIGNMENT(#2, (#450));
#532=APPLIED_ACTION_REQUEST_ASSIGNMENT(#547, (#400));
#547=VERSIONED_ACTION_REQUEST('var id3', '0002', 'production requirement', 'description of var id3, 0002');
#533=ACTION_DIRECTIVE('wo id1', 'design release', 'results of analysis of var id1', 'comment 1', (#1));
#534=ACTION_DIRECTIVE('wo id2', 'design change', 'results of analysis of var id2', 'comment 2', (#2));
#535=DIRECTED_ACTION('design', $, #537, #533);
#536=DIRECTED_ACTION('work definition', $, #10, #534);
#537=ACTION_METHOD('activity method 2', $, 'effects of activity method 2', 'objectives of activity method 2');
#538=PRODUCT_DEFINITION_FORMATION('B', '', #440);
#539=PRODUCT_DEFINITION('new_part_v1', 'design view on new part', #543, #230);
#540=APPLIED_ACTION_ASSIGNMENT(#535, (#539));
#541=APPLIED_ACTION_ASSIGNMENT(#536, (#538));
#542=PRODUCT('new_part_id', 'new part name', $, (#220));
#543=PRODUCT_DEFINITION_FORMATION('A', '', #542);
#544=PRODUCT_DEFINITION('sv2', 'design view on sleeve assembly', #538, #230);
#545=OBJECT_ROLE('output', $);
#546=ROLE_ASSOCIATION(#545, #540);
