PDM-UG: Recommendations for the assignment of person and organization

From WikiSTEP

This page belongs to the PDM Usage Guide.

Person and organization data considered in this section is information about the responsibilities of persons and organizations in respect to product data. The entities for the assignments are person_and_organization_assignment and organization_assignment. The assignment entity has a role attribute that contains information about the meaning of the assignment. Of the variety of possible items to which the assignments of person and organizational data can be made, Table 2 gives the recommendations for scenarios and roles that should be supported.

person_organization_assignment	product (as part)	product_definition_formation (as part version)	product_definition (as view on part version)	product (as document)	product_definition_formation (as document version)
creator		X	X		X
id owner	X			X

Table 2: Recommended Assignment of Person/Organization to Product Data

The interpretations of the roles are:

• the role 'creator' indicates that the referenced object has been created (i.e., originally defined) by the organization (or person_and_organization),
• the role 'id owner' describes the person or organization in which the id of the referenced object is valid.

In a given application scenario additional roles might be negotiated. Where applicable the following values may be used:

• 'custodian': The assigned Person or Organization is responsible for the continued existence and integrity of the referenced object;
• 'customer': The assigned Person or Organization acts as a purchaser or consumer of the referenced object;
• 'design supplier': The assigned Person or Organization is the one who is responsible for delivery or the data describing the referenced object;
• 'editor': The assigned Person or Organization is responsible for making any changes to any attribute of the referenced object;
• 'location': The assigned Organization is the place where the referenced object can be found or where it takes place;
• 'manufacturer': The assigned Person or Organization is the one who produces the actual (physical) object;
• 'owner': The assigned Person or Organization owns the referenced object, and has final say over its disposition and any changes to it;
• 'supplier': The assigned Person or Organization is the one who delivers the actual (physical) object (e.g., a dealer);
• 'wholesaler': The assigned Person or Organization is the one who is in the sales chain between the manufacturer and the supplier.

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

A complete instantiation example for person and organization assignments is given in Example 55.

ISO-10303-21;
HEADER;
FILE_DESCRIPTION(('pdm_schema data', 'pdm_schema'), '2;1');
FILE_NAME('C:\document_xample.stp', '1999-5-20 T12:39:1', (''), (), '', '', '');
FILE_SCHEMA(('PDM_SCHEMA {1.2}'));
ENDSEC;
DATA;
/*   Entities #10 - #20 define part master data                     */
/*   To the product_definition #90 is a life cycle specific view on */
/*  that part to which organization and person are assigned in the  */
/*  role of the id owner                                            */
#10=APPLICATION_CONTEXT('');
#20=APPLICATION_PROTOCOL_DEFINITION('version 1.2','pdm_schema',20002000,#10);
#30=PRODUCT_DEFINITION_CONTEXT_ROLE('',$);
#40=APPLICATION_CONTEXT('mechanical design');
#50=PRODUCT_DEFINITION_CONTEXT('part definition',#40,'design');
#60=PRODUCT_CONTEXT('',#10,'');
#70=PRODUCT('MP-03-2','my part',$,(#60));
#80=PRODUCT_DEFINITION_FORMATION('03','3rd modification',#70);
#90=PRODUCT_DEFINITION('/NULL',$,#80,#50);
#100=PRODUCT_DEFINITION_CONTEXT_ASSOCIATION(#90,#50,#30);
#110=PRODUCT_RELATED_PRODUCT_CATEGORY('part',$,(#70));

/* Entities #120 to #170 model the assignment of a person within an */
/* organization to the part. The role of this person/organization  */
/* is that of 'id owner'                                    */
#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)
#160=PERSONAL_ADDRESS('office 321',$,$,$,$,$,$,$,'423 -21','423-33','miller@my-com.com',$,$,'coordinates of Mr Miller');
#170=PERSON_AND_ORGANIZATION_ROLE('id owner');

/*   Entities #240 to #300 model a managed document (document as product)  */
/*   The document gets an assigned organization in the role of 'creation'  */

#240=APPLICATION_CONTEXT('');
#250=PRODUCT_DEFINITION_CONTEXT('digital document definition',#240,'');
#260=PRODUCT_CONTEXT('',#240,'');
#270=PRODUCT('doc_4711','packaging guide','packaging guideline for part',(#260));
#280=PRODUCT_DEFINITION_FORMATION('ver3.1','version 3.1',#270);
#290=PRODUCT_DEFINITION('id of digital document','digital document for representing guideline ver3.1',#280,#250);
#300=PRODUCT_RELATED_PRODUCT_CATEGORY('document',$,(#270));

/* Entities #310 to #340 model the assignment of an organization   */
/* to the document defined via #270. The info transferred with the */
/* assignment is that the organization has created the document    */
#310=APPLIED_ORGANIZATION_ASSIGNMENT(#320,#330,(#270));
#320=ORGANIZATION('ord_id_34','Doc Writers Com',$);
#330=ORGANIZATION_ROLE('creation');
#340=ORGANIZATIONAL_ADDRESS($,'14a','E street','P.O 321','My Town','Nice Region','postal code','My Country','345 - 21','345 - 31','info@company',$,$,$);
ENDSEC;
END-ISO-10303-21;

Example 55: exchange file for complete person and organization .