PDM-UG: Project Identification
From WikiSTEP
This page belongs to the PDM Usage Guide.
The project identification area contains the constructs to represent projects, i.e., programs of work for which one or more organizations are responsible, and relationships between projects. Events may be defined to specify when a project is planned to or actually starts and/or ends. Projects may be related to the product concept(s) that are affected by the work carried out within the project
Contents |
The Instance Model: EXPRESS entities and attributes
The EXPRESS entities and attributes used to support the requirements to represent project identification information are illustrated in Diagram 70 below. The corresponding STEP exchange file encoding is given in Example 70.
Organizational project
An organizational_project is an identified program of work for which one or more organizations are responsible.
Attributes
- The name attribute specifies the word or common name used to refer to the organizational_project.
- The description attribute specifies additional information about the organizational_project.
- The responsible_organization attribute specifies the organizations that are responsible for the project.
| ENTITY organizational_project | Attribute Population | Remarks |
| name | type: label = text | |
| description | type: text = string | OPTIONAL |
| responsible_organization | type: entity = organization | S[1:?] |
| id | DERIVEd attribute type: identifier = string | exactly one id may be associated via the entity id_attribute |
===Preprocessor Recommendations=== There are no specific preprocessor recommendations.
===Postprocessor Recommendations=== There are no specific postprocessor recommendations.
===Related Entities=== An organizational_project may be referenced by the following entities:
- organizational_project_relationship to associate two organizational_projects, e.g., to define their hierarchical relationships or to describe their dependencies.
- applied_organizational_project_assignment to associate the assigned organizational_project to the product concepts that are affected by the work carried out within the project.
- applied_event_occurrence_assignment to attach event information to organizational_projects. See Event Reference for guidance in creating the event_occurrence constructs. Where applicable, the following values for the name attribute of the event_occurrence_role are recommended: 'planned start', 'planned end'.
Applied organizational project assignment
The applied_organizational_project_assignment entity defines a mechanism to associate an organizational_project to some product data. In the PDM Schema, an organizational_project may be assigned to a product_concept, indicating the product_concept is affected by the work carried out within the assigned organizational_project.
Attributes
- The assigned_organizational_project specifies the organizational_project, which is assigned to some product data.
- The role identifies the organizational_project_role that specifies the purpose of the association of the organizational_project_assignment with product data.
- The items attribute specifies the product data to which the organizational_project is assigned.
| 'ENTITY applied_organizational_project_assignment | Attribute Population | Remarks |
| assigned_organizational_project | type: entity = organizational_project | |
| role | type: entity = organizational_project_role | |
| items | type: entity = organizational_project_item select | SET[1:?] |
===Preprocessor Recommendations=== The organizational_project may only be assigned to the product_concepts that are affected by the work carried out within the project. The name attribute of the associated organizational_project_role is therefore recommended to be 'affecting project'.
===Postprocessor Recommendations=== There are no specific postprocessor recommendations.
===Related Entities=== There are no specific related entities.
Organizational project role
An organizational_project_role defines a role for an organizational_project_assignment and a description of that role to characterize the nature of the assignment.
Attributes
- The name attribute specifies the word or common name used to refer to the organizational_project_role.
- The description attribute specifies additional information about the organizational_project_role.
| ENTITY organizational_project_role | Attribute Population | Remarks |
| name | type: label = text | |
| description | type: text = string | OPTIONAL |
===Preprocessor Recommendations=== An organizational_project may only be assigned to product_concepts that are affected by the work carried out within the project. The name attribute of the associated organizational_project_role is therefore recommended to be 'affecting project'.
===Postprocessor Recommendations=== There are no specific postprocessor recommendations.
===Related Entities=== An organizational_project_role may be referenced by the following entities:
- applied_organizational_project_assignment to specify the assignment for which the organizational_project_role defines a role. The organizational_project_role shall be referenced by at least one applied_organizational_project_assignment.
Organizational project relationship
An organizational_project_relationship is a relationship between two organizational_projects. The meaning of the organizational_project_relationship is given by its name attribute. An organizational_project_relationship may be used to define an organizational_project as part of some higher-level organizational_project, or to express some dependency such as sequential relationship between two organizational_project objects.
Attributes
- The name attribute specifies the meaning of the relationship.
- The description attribute specifies additional information text that characterizes the organizational_project_relationship.
- The relating_organizational_project specifies the first organizational_project, which is related by the organizational_project_relationship. The relating_organizational_project usually identifies the project the definition of the related_organizational_project is based on, e.g., derived from or dependent on. The semantics of this attribute should be defined by the name attribute.
- The related_organizational_project specifies the second organizational_project related by the organizational_project_relationship. The related_organizational_project usually identifies the organizational_project, which is based on the definition of the relating_organizational_project. The semantics of this attribute should be defined by the name attribute.
| ENTITY organizational_project_relationship | Attribute Population | Remarks |
| name | type: label = string | |
| description | type: text = string | OPTIONAL |
| relating_organizational_project | type: entity = organizational_project | |
| related_organizational_project | type: entity = organizational_project |
===Preprocessor Recommendations=== The name attribute is used to specify the type of the organizational_project_relationship. Where applicable, the following values should be used:
- ’decomposition’ to indicate that the related_organizational_project is a sub-project in a hierarchical breakdown of the relating_organizational_project;
- ’dependency’ to indicate that the related_organizational_project is dependent upon the relating_organizational_project; ’sequence’ to indicate that the relating_organizational_project must be completed before the related_organizational_project starts;
- ’succession’ to indicate that the relating_organizational_project is the successor of the relating_organizational_project.
===Postprocessor Recommendations=== There are no specific postprocessor recommendations.
===Related Entities=== There are no specific related entities.
The Instance Model: STEP exchange file format (ISO10303 Part 21 syntax)
#1=ORGANIZATION('organization_id', 'organization_name', $);
#2=ORGANIZATIONAL_PROJECT('project_name', 'project_description', (#1));
#4=ORGANIZATIONAL_PROJECT_ROLE('affecting project', $);
#5=PRODUCT_CONCEPT('product_concept_id', 'product_concept_name', $, #7);
#6=APPLIED_ORGANIZATIONAL_PROJECT_ASSIGNMENT(#2, #4, (#5));
#7=PRODUCT_CONCEPT_CONTEXT('pcc_name1', #8, '');
#8=APPLICATION_CONTEXT('');


