PDM-UG: Organization

From WikiSTEP

Jump to: navigation, search

This page belongs to the PDM Usage Guide.

The PDM Schema represents groups of people (e.g., companies, countries, etc.) through the organization entity. The identification or id data is optional. However, because this information is very important in providing unique identification to the organization or company, it is recommended that this field always be populated with unique data. If appropriate, a URL-like convention for the organization identifier may be useful, e.g., prostep.de. The name attribute should contain the common nomenclature of the organization. The description attribute may contain a characterization of the type of the organization, or a textual explanation of its reason for existence.

The organization entity is related to certain constructs to identify the organizations responsible for them and how they are responsible. This relationship is defined through the applied_organization_assignment entity (which relates an organization in some role) to an entity. The role is established in the organization_role entity name attribute. The sections, which describe the use of the entity to which the organization is assigned, will identify the allowed values for the name attribute of the organization_role entity. The organization_role entity may have a description associated with it through the entity description_attribute and its attribute_value attribute.

Contents

The Instance Model: EXPRESS entities and attributes

The EXPRESS entities and attributes essential to support the requirements for organization are illustrated in Diagram 53.

Image:Diagram_53_Organization_Instance_Diagram.png
Diagram 53: Organization Instance Diagram

Organization

Entity represents the identification of an identified group of people gathered and structured for a purpose.

Attributes

  • The id attribute is the identifier that distinguishes the organization.
  • The name attribute is the label by which the organization is known.
  • The description attribute characterizes the type of organization, or an explanation of its reason for existence.


ENTITY organization Attribute Population Remarks
id type: identifier = string OPTIONAL
it is recommended to instantiate this attribute
name type: label = string  
description type: text = string OPTIONAL
if available the type of organization shall be mapped into this attribute

===Preprocessor Recommendations=== All preprocessors should provide a unique organization id to eliminate ambiguities where organizations may have the same names. If the intended domain for the data is large, the reader is referred to ISO/IEC 8824-1, which can provide some guidance on creating unique identifiers. If appropriate, a URL-like convention for the organization identifier may be used, e.g., prostep.de. A unique string obtained under ISO/IEC 8824-1 can be used as, or prefixed to, the organization identifier. For example, if the organization typically used an identifier of '93699' and the unique string were 'USA', the unique value of the organization id would be 'USA93699'. If available and appropriate, the following values should be used to describe the organization type: ‘company’ to indicate a business entity; ‘department’ to indicate an organizational group within a company.

===Postprocessor Recommendations=== All postprocessors should make use of any provided information in the id attribute to eliminate ambiguities where organizations may have the same name.

===Related Entities=== There are no specific related entities.

Applied organization assignment

The applied_organization_assignment entity is a subtype of organization_assignment, allowing the representation of the assignment of an organization to some product data.

Attributes

  • The assigned_organization is the organization which is to be associated with the product data.
  • The role attribute specifies the purpose of the association of the organization_assignment with product data.
  • The items attribute is a reference to the product data to which the organization is being assigned.


ENTITY applied_organization_assignment Attribute Population Remarks
assigned_organization type: entity = organization  
role type: entity = organization_role  
items type: entity (defined by organization_item_select) SET[1:?]

===Preprocessor Recommendations=== For applied_organization_assignments the potential organization_roles 'id owner' and 'creator' are recommended.

===Postprocessor Recommendations=== Postprocessors should support the assignment of the above roles to products, product_definition_formations and product_definitions (either related to parts or managed documents).

===Related Entities=== There are no specific related entities.

Organization role

Entity represents the role for the assignment of a person_and_organization to product data.

Attributes

  • The name attribute is the label by which the organization_role is known.
  • The description attribute characterizes the role with further descriptive text.


</td> </table>

===Preprocessor Recommendations=== Role.name should be 'creator' or 'id owner' where applicable.

===Postprocessor Recommendations=== Postprocessors should at least support the above role names. Postprocessors should expect that some existing implementations might export files that use other role names such as 'design supplier' or 'designer'.

===Related Entities=== There are no specific related entities.

The Instance Model: STEP exchange file format (ISO10303 Part 21 syntax)

#310=APPLIED_ORGANIZATION_ASSIGNMENT(#320,#330,(#270));
#320=ORGANIZATION('ord_id_34','Doc Writers Com',$);
Example 52: exchange file segment for organization
Retrieved from "http://www.wikistep.org/index.php/PDM-UG:_Organization"
ENTITY organization_ role Attribute Population Remarks
name type: label = string  
description type: text = string DERIVED