PDM-UG: Person and Organization
From WikiSTEP
This page belongs to the PDM Usage Guide.
The PDM Schema specifies information about people through the person entity. A person is identified by an id with other data representing their name and optionally titles which may apply to them. In populating the data, the id must be unique. This is typically not a problem when the person is taken in the context of some specific group such as a company or even country. In these instances, there are typically identifying numbers assigned to people. If the data being assembled is for worldwide consumption, the id must be unique in that domain.
In the PDM Schema, a person always exists in the context of some organization. The connection of people to organizations is accomplished through the person_and_organization entity. This entity is related to certain constructs to identify the people in organizations responsible for them and how they are responsible. This is specified through the applied_person_and_organization_assignment, which relates a person and organization in some role to an entity. The role is established in the name attribute of the person_and_organization_role entity. The person_and_organization_role and person_and_organization entity may have a description associated with it through the entity description_attribute and its attribute_value attribute. The person_and_organization entity may have a name associated with it through the entity name_attribute and its attribute_value attribute. This name describes the relationship of the person to the organization.
Contents |
The Instance Model: EXPRESS entities and attributes
The EXPRESS entities and attributes used to support the requirements for person and organization are illustrated in Diagram 54.
Person
Entity represents the identification of an individual. In the PDM Schema, a person always exists in the context of some organization.
Attributes
- The id attribute distinguishes the person.
- The last_name attribute has the last name of the person.
- The first_name attribute has the first name of the person.
- The middle_names attribute is a list of strings representing the middle names.
- The prefix_titles attribute is a list of text which specify the person's social and/or professional standing and appear before his or her names.
- The suffix_titles attribute is a list of text, which specifies the person's social and/or professional standing and appear after his or her names.
| ENTITY person | Attribute Population | Remarks |
| id | type: identifier = string | must be unique in the scope of the associated organization(s) |
| last_name | type: label = string | OPTIONAL it is recommended to instantiate this attribute |
| first_name | type: label = string | OPTIONAL |
| middle_names | type: label = string | OPTIONAL SET |
| prefix_titles | type: label = string | OPTIONAL SET |
| suffix_titles | type: label = string | OPTIONAL SET |
===Preprocessor Recommendations=== All preprocessors should provide values for at least the last_name and first_name attributes for the person entity in order to provide a sense of meaning to the id attribute. In cases where uniqueness of the id attribute may be a problem, preprocessors should prefix the id attribute with the organization id (as described in the following section) followed by a comma. For example, if the organization id value were 'USA,93699' and the person id were '111111', the actual value of the person id would be 'USA,93699,111111'.
===Postprocessor Recommendations=== There are no specific postprocessor recommendations.
===Related Entities=== There are no specific related entities.
Person and organization
The person_and_organization entity represents the identification of a person within an organization. In the PDM Schema, a person always exists in the context of some organization. The connection of people to organizations is accomplished through the person_and_organization entity.
Attributes
- The name attribute is a label, which describes the role of the person in person_and_organization, i.e., the relationship between the person and the organization.
- The description attribute characterizes the person_and_organization.
- The the_person attribute is the person who is related to the organization.
- The the_organization attribute is the organization to which the person is related.
| ENTITY person_and_organization | Attribute Population | Remarks |
| name | type label = string | DERIVE the name is established via the entity name_attribute that has a label for the name as first attribute and references the person_and_organization in the second attribute |
| description | type: text = string | OPTIONAL |
| the_person | type: entity = person | |
| the_organization | type: entity = organization |
===Preprocessor Recommendations=== Description (i.e., the structure for the derived attribute) shall not be instantiated.
===Postprocessor Recommendations=== There are no specific postprocessor recommendations.
===Related Entities=== There are no specific related entities.
Person and organization role
The person_and_organization_role entity describes the assignment role for the assignment of a person_and_organization to product data.
Attributes
- The name attribute indicates the nature of the assignment.
- The description attribute characterizes the person_and_organization_role.
| ENTITY person_and_organization_role | Attribute Population | Remarks |
| name | type: label = string | |
| description | type: text = string | DERIVED |
===Preprocessor Recommendations=== See recommendations for organization_role.
===Postprocessor Recommendations=== See recommendations for organization_role.
===Related Entities=== There are no specific related entities.
Applied person and organization assignment
The applied_person_and_organization_assignment entity is a subtype of person_and_organization_assignment, and represents the assignment of a person_and_organization to product data.
NOTE - In the scope of this usage guide, applied_person_and_organization_assignment is used to associate information about responsibility, not to represent an electronic signature.
Attributes
- The assigned_person_and_organization attribute references the person_and_organization.
- The role attribute describes the nature of the assignment.
- The items attribute is a reference to the product data having the person_and_organization assigned.
| ENTITY applied_person_and_organization_assignment | Attribute Population | Remarks |
| assigned_person_and_organization | type: entity = person_and_organization | |
| role | type: entity = person_and_organization_role | &nbps; |
| items | type: entity = person_and_organization_item select | SET[1:?] |
===Preprocessor Recommendations=== This entity shall be used when the assignment involves an organization as well as a person related to that organization.
===Postprocessor Recommendations=== There are no specific postprocessor recommendations.
Related Entities
- applied_date_assignment and applied_date_time_assignment to specify the assignment of a person_and_organization together with a date.
The Instance Model: STEP exchange file format (ISO10303 Part 21 syntax)
#120=APPLIED_PERSON_AND_ORGANIZATION_ASSIGNMENT(#130,#170,(#70));
#130=PERSON_AND_ORGANIZATION(#150,#140);
#140=ORGANIZATION('org_id','Miller Company',$);
#150=PERSON('p_id','Miller',$,$,$,$);
#155=NAME_ATTRIBUTE('employee',#130)
#310=APPLIED_ORGANIZATION_ASSIGNMENT(#320,#330,(#270));
#320=ORGANIZATION('ord_id_34','Doc Writers Com',$);


