PDM-UG: Request for Work
From WikiSTEP
This page belongs to the PDM Usage Guide.
The work done as part of an engineering process may be triggered or initiated by official requests that identify the need for a potential release or change of functionality. These requests may or may not ever actually be incorporated, depending upon the level of authorization granted to the request and its associated work order.
The STEP PDM Schema supports the representation of these work requests including their level of completion, the reason for the suggested work to be done, and the desired outcome. The items that are planned as the possible subject of this work may be identified as in scope and attached to the work request. If the request is in fact incorporated, these planned affected items of the work request may or may not actually be the items affected by the associated work order. One or more potential alternative solutions for addressing the work request may also be specified.
Additional administrative information such as persons, organizations, and date and time related information as well as approval authorization information can also be attached to a work request.
Contents |
The Instance Model: EXPRESS entities and attributes
The EXPRESS entities and attributes used to support the requirements to represent request for work information are illustrated in Diagram 67 below. The corresponding STEP exchange file encoding is given in Example 67.
Diagram 67: Request for Work Instance Diagram
Versioned action request
The versioned_action_request entity represents a request for some work which may be an initial release or a change. A versioned_action_request also specifies the reason for this work.
Possible ways to achieve the purpose of the request, i.e., potential alternative solutions, may be identified as one or more action_method instances that are attached to the versioned_action_request using the entity action_request_solution (see Action request solution). Status information describing the level of completion of the versioned_action_request must be represented through an associated action_request_status (see Action request status).
The items that are planned as the subject of the work request are associated to the work request using applied_action_request_assignment (see Applied action request assignment). For example, if a versioned_action_request represents a request for change the items to be changed are identified through an applied_action_request_assignment. Such items may be part or document versions, view definitions, or part properties. For additional information, see applied_document_reference Applied document reference.
Attributes
- The id attribute specifies an identifier that distinguishes the versioned_action_request.
- The version attribute specifies the identification of the version of the versioned_action_request.
- The purpose attribute specifies a descriptive label providing an informal description of the reason for the versioned_action_request.
- The description attribute specifies additional information about the versioned_action_request.
| ENTITY versioned_action_request | Attribute Population | Remarks |
| id | type: identifier = string | must be unique in conjunction with the version attribute |
| version | type: label = text | |
| purpose | type: text = string | |
| description | type: text = string | OPTIONAL |
===Preprocessor Recommendations=== There is no standard mapping for the id attribute of versioned_action_request; however the value should be unique in conjunction with the version attribute.
The purpose attribute is mandatory, and may contain any appropriate/mutually-agreed-upon string. Where applicable, the following values for the purpose attribute may be used: 'technical improvement', 'government regulation', 'durability improvement', 'tool improvement', 'production relief', 'production requirement', 'quality improvement', 'security reason', 'standardization', 'cost reduction', 'customer rejection', 'change of standard', 'production alignment', and 'procurement alignment'.
A versioned_action_request shall have an associated status, represented by exactly one action_request_status, which references the versioned_action_request as the assigned_request (see Action request status).
===Postprocessor Recommendations=== There are no specific postprocessor recommendations.
===Related Entities=== A versioned_action_request may be referenced by the following entities:
- action_request_solution to identify potential solutions to address the versioned_action_request.
- applied_action_request_assignment to identify the items that are planned as the subject of the assigned work request.
NOTE - If a versioned_action_request is referenced as the assigned_request by an applied_action_request_assignment specifying one or more product_definition_formations, product_definitions, or product_definition_relationships as the affected items, it is assumed that the versioned_action_request represents a request for change of the referenced objects, otherwise it represents a request for an initial design.
- action_directive to identify the definition of related engineering action(s) that provide the work definition proposed to incorporate the purpose of the versioned_action_request.
- applied_approval_assignment to associate approval information related to a versioned_action_request. See Approval for guidance in creating the approval constructs.
- applied_date_assignment (or applied_date_and_time_assignment) to associate date information to a versioned_action_request. See Date and Time for guidance in creating the date and time constructs. A recommended value for the name attribute of the date_role is 'request date'.
- applied_organization_assignment (or applied_person_and_organization_assignment) to associate organization (and person) information to a versioned_action_request. See Organization and Person for guidance in creating the organization and person constructs. A recommended value for the name attribute of the organization_role (or person_and_organization_role) is 'requestor'.
- applied_document_reference to associate a document with the versioned_action_request.
Action request status
The action_request_status entity represents the status describing the level of completion of the associated versioned_action_request.
Attributes
- The status attribute specifies a label that provides a user-interpretable designation for the level of completion of the versioned_action_request.
- The assigned_request attribute specifies the versioned_action_request for which the status is specified.
| ENTITY action_request_status | Attribute Population | Remarks |
| status | type: label = text | |
| assigned_request | type: entity = versioned_action_request |
===Preprocessor Recommendations=== The status attribute characterizes the level of completion of the versioned_action_request and therefore should be populated with predefined values that are commonly understood by both sides of the exchange. Recommended values to be used are 'proposed', 'in-work', 'issued', and 'hold'.
===Postprocessor Recommendations=== There are no specific postprocessor recommendations.
===Related Entities=== There are no specific related entities.
Applied action request assignment
A work request may be raised against different types of product data that might be subject to the requested work. The applied_action_request_assignment entity defines a mechanism to associate a work request with the items that are thought or planned to be affected by the work request.
The types of items to which a work request may be assigned are defined in the action_request_item select type. The STEP PDM Schema allows versions, views, and structure relationships of parts and documents (i.e., product_definition_formation, product_definition, and product_definition_relationship instances) to be subject of a work request. The action_request_item select type as well supports part properties to be subject of a work request.
Attributes
- The assigned_action_request specifies the versioned_action_request, which is assigned to the affected product data.
- The items attribute specifies the set of items that are subject of the work request represented by the associated versioned_action_request.
| ENTITY applied_action_request_assignment | Attribute Population | Remarks |
| assigned_action_request | type: entity = versioned_action_request | |
| role | DERIVEd attribute type: entity = object_role | OPTIONAL |
| items | type: entity = action_request_item select | SET[1:?] |
===Preprocessor Recommendations=== The applied_action_request_assignment entity may have a role associated with it through the entity object_role. Where applicable, the value ’scope’ should be used to indicate that the referenced items are planned in scope of the assigned work request. If there is no role specified for an applied_action_request_assignment, it is assumed that the versioned_action_request represents a change request for the referenced objects.
===Postprocessor Recommendations=== If no object_role is specified for the applied_action_request_assignment, the assigned versioned_action_request shall be interpreted as a change request requesting a change of the associated items (‘scope’).
===Related Entities=== An action_request_assignment may be referenced by the following entities:
- role_association to specify an object_role defining the role of the assignment, i.e., purpose of the association of the applied_action_request_assignment with product data.
- property_definition to specify properties of a work_request
Action request solution
The action_request_solution entity represents an association between a work and an action_method that describes a potential solution for the request. Identified solutions of a versioned_action_request may be explicitly recommended or explicitly excluded from a recommendation.
Attributes
- The method attribute specifies an action_method that is a potential solution for the request.
- The request attribute specifies the versioned_action_request for which the (potential) solution is specified.
| ENTITY action_request_solution | Attribute Population | Remarks |
| method | type: entity = action_method | |
| request | type: entity = versioned_action_request | |
| description | DERIVEd attribute type: text = string | at most one description can be associated via the entity description_attribute |
| name | DERIVEd attribute type: label = string | at most one name can be associated via the entity name_attribute |
===Preprocessor Recommendations=== If a potential solution identified by an action_request_solution is explicitly recommended to address the issue raised by the versioned_action_request, the value 'recommended method' may be used for the name attribute. If a potential solution is identified as such, but not recommended to solve the work request, the value 'non-recommended method' may be used for the name attribute.
===Postprocessor Recommendations=== There are no specific postprocessor recommendations.
===Related Entities=== There are no specific related entities.
Action method
The action_method entity defines relevant information about the process for executing an activity. This definition includes the activity’s objectives and effects and describes how the activity is to be carried out. Within the work management area, action_methods may be used to describe procedures for how to carry out activities and to represent the potential solutions to address a work request. Document files representing action_method can be associated by using applied_document_reference. For additional information, see applied_document_reference Applied document reference.
Attributes
- The name attribute specifies the word or common name used to refer to the action_method.
- The description attribute specifies additional information about the action_method.
- The consequence attribute contains an informal description of the effects of the action_method.
- The purpose attribute specifies a descriptive label characterizing the objectives of the action_method.
| ENTITY action_method | Attribute Population | Remarks |
| name | type: label = text | |
| description | type: text = string | OPTIONAL |
| consequence | type: text = string | |
| purpose | type: label = text |
===Preprocessor Recommendations=== There are no specific preprocessor recommendations.
===Postprocessor Recommendations=== There are no specific postprocessor recommendations.
===Related Entities=== An action_method may be referenced by the following entities:
- executed_action and directed_action to indicate the activities for which the action_method describes the procedure.
- action_request_solution to specify the versioned_action_request(s) for which the action_method defines a potential solution.
- applied_document_reference to associate a document with the action_method.
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');
#3=VERSIONED_ACTION_REQUEST('var id3', '0002', 'production requirement', 'description of var id3, 0002');
#4=ACTION_REQUEST_STATUS('proposed', #1);
#5=ACTION_REQUEST_STATUS('issued', #2);
#6=ACTION_REQUEST_STATUS('in-work', #3);
#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));
#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(#3, (#400));
