PDM-UG: Event Reference
From WikiSTEP
This page belongs to the PDM Usage Guide.
In the PDM Schema, events are characterized by instances of the event_occurrence entity or its subtype relative_event_occurrence.
Contents |
The Instance Model: EXPRESS entities and attributes
The EXPRESS entities and attributes required to support the requirements for event occurrence assignment are illustrated in Diagram 60. A Part 21 file segment using event reference is shown in Example 60.
Diagram 60: Event Occurrence Instance Diagram
Event occurrence
The event_occurrence entity describes aspects relevant to characterizing a state transition.
Attributes
- The id attribute identifies the event_occurrence.
- The name attribute provides the word or group of words by which the event_occurrence is referred.
- The description attribute provides additional descriptive information about the event_occurrence.
| ENTITY event_occurrence | Attribute Population | Remarks |
| id | type: identifier | |
| name | type: label | |
| description | type: text | OPTIONAL |
===Preprocessor Recommendations=== There are no specific preprocessor recommendations.
===Postprocessor Recommendations=== There are no specific postprocessor recommendations.
===Related Entities=== Event_occurrence may be used to specify the limits in dated_effectivity (see Dated effectivity).
Relative event occurrence
The relative_event_occurrence entity is a subtype of event_occurrence that is characterized by an offset to another event_occurrence.
Attributes
- The base_event attribute identifies the event_occurrence providing the basis for definition of the relative_event_occurrence.
- The offset attribute specifies the amount of time between the base_event and the relative_event_occurrence.
| ENTITY relative_event_occurrence | Attribute Population | Remarks |
| base_event | type: entity = event_occurrence | |
| offset | type: entity = time_measure_with_unit |
===Preprocessor Recommendations=== There are no specific preprocessor recommendations.
===Postprocessor Recommendations=== There are no specific postprocessor recommendations.
===Related Entities=== There are no specific related entities.
Applied event occurrence assignment
The applied_event_occurrence_assignment entity allows for association of events with product data.
Attributes
- The assigned_event_occurrence attribute specifies the event_occurrence to be assigned to product data.
- The role attribute specifies the purpose of the assignment of the event_occurrence to product data.
- The items attribute is a reference to the product data to which the event_occurrence is being assigned.
| ENTITY applied_event_occurrence_assignment | Attribute Population | Remarks |
| assigned_event_occurrence | type: entity = event_occurrence | |
| role | type: entity = event_occurrence_role | |
| items | type: date_item = SELECT | SET [1:?] – In the PDM Schema the select type is constrained to the entity organizational_project. |
===Preprocessor Recommendations=== There are no specific preprocessor recommendations.
===Postprocessor Recommendations=== There are no specific postprocessor recommendations.
===Related Entities=== There are no specific related entities.
Event occurrence role
The event_occurrence_role entity specifies a role for an event_occurrence_assignment.
Attributes
- The name attribute specifies the word or group of words by which the event_occurrence_role is referred.
- The description attribute specifies additional descriptive information about the event_occurrence_role.
| ENTITY event_occurrence_role | Attribute Population | Remarks |
| name | type: label | |
| description | type: text | OPTIONAL |
===Preprocessor Recommendations=== There are no specific preprocessor recommendations.
===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=APPLICATION_CONTEXT('mechanical design');
#220=PRODUCT_CONTEXT('', #1, '');
#230=PRODUCT_DEFINITION_CONTEXT('part definition', #1, 'design');
#100=PRODUCT_RELATED_PRODUCT_CATEGORY('part', $, (#2));
#2=PRODUCT('11000', 'solid cube', 'description for part 11000', (#220));
#3=PRODUCT_DEFINITION_FORMATION('A', 'version A for solid cube', #2);
#4=PRODUCT_DEFINITION('D1', 'detailed drawing as planned for STEP conformance testing', #3, #230);
/* start and end events for effectivity */
#910=EVENT_OCCURRENCE('ev1', 'start production', 'lot for customer A');
#910=EVENT_OCCURRENCE('ev2', 'end production', 'lot for customer A');
/* effectivity definition and assignment */
#1040=DATED_EFFECTIVITY('', #910, #970);
#1042=APPLIED_EFFECTIVITY_ASSIGNMENT(#1040, (#3));
#1044=OBJECT_ROLE('actual', $);
#1045=ROLE_ASSOCIATION(#1044, #1042);
