Application module: Event ISO/TS 10303-1064:2018-11(E)
© ISO

Cover page
Table of contents
Copyright
Foreword
Introduction
1 Scope
2 Normative references
3 Terms, definitions and abbreviated terms
    3.1 Terms and definitions
    3.2 Abbreviated terms

4 Information requirements
   4.1 Required AM ARMs
   4.2 ARM type definition
   4.3 ARM entity definitions
5 Module interpreted model
   5.1 Mapping specification
   5.2 MIM EXPRESS short listing
     5.2.1 MIM type definitions

A MIM short names
B Information object registration
C ARM EXPRESS-G   EXPRESS-G
D MIM EXPRESS-G   EXPRESS-G
E Computer interpretable listings
F Application module implementation and usage guide
G Change history
Bibliography
Index

4 Information requirements

This clause specifies the information requirements for the Event application module. The information requirements are specified as the Application Reference Model (ARM) of this application module.

NOTE 1  A graphical representation of the information requirements is given in Annex C.

NOTE 2  The mapping specification is specified in 5.1. It shows how the information requirements are met by using common resources and constructs defined or imported in the MIM schema of this application module.

This clause defines the information requirements to which implementations shall conform using the EXPRESS language as defined in ISO 10303-11. The following begins the Event_arm schema and identifies the necessary external references.

EXPRESS specification:

*)
SCHEMA Event_arm;
(*

4.1 Required AM ARMs

The following EXPRESS interface statements specify the elements imported from the ARMs of other application modules.

EXPRESS specification:

*)
USE FROM Date_time_arm;    --  ISO/TS 10303-1010

USE FROM Date_time_assignment_arm;    --  ISO/TS 10303-1014

USE FROM Value_with_unit_arm;    --  ISO/TS 10303-1054
(*

NOTE 1   The schemas referenced above are specified in the following part of ISO 10303:

Date_time_arm ISO/TS 10303-1010
Date_time_assignment_arm ISO/TS 10303-1014
Value_with_unit_arm ISO/TS 10303-1054

NOTE 2   See Annex C, Figures C.1and C.2 for a graphical representation of this schema.

4.2 ARM type definition

This subclause specifies the ARM type for this application module. The ARM type and definition is specified below.

4.2.1 date_or_event   EXPRESS-G

A date_or_event type is a formal mechanism to refer either to a Calendar_date, a Date_time, or an Event.

EXPRESS specification:

*)
TYPE date_or_event = SELECT
   (Calendar_date,
    Date_time,
    Event);
END_TYPE;
(*

4.3 ARM entity definitions

This subclause specifies the ARM entities for this module. Each ARM application entity is an atomic element that embodies a unique application concept and contains attributes specifying the data elements of the entity. The ARM entities and definitions are specified below.

4.3.1 Event   EXPRESS-GMapping table

An Event is the fact of the existence of a state at some point in time.

NOTE 1   The event may have occurred or may be not yet started.

NOTE 2   The point in time where an event will start or started, may not be known or specified.

EXPRESS specification:

*)
ENTITY Event;
  id : STRING;
  name : STRING;
  description : OPTIONAL STRING;
  actual_start_date : OPTIONAL date_or_date_time_select;
  planned_start_date : OPTIONAL date_or_date_time_select;
END_ENTITY;
(*

Attribute definitions:

id: the identifier that distinguishes the Event.

name: the words by which the event is known.

EXAMPLE    'Start of production' and 'break down of machine A' are examples of event names.

description: the text that provides further information about the event. The value of the attribute need not be specified.

actual_start_date: the Calendar_date or Date_time when the event started. The value of the attribute need not be specified.

planned_start_date: the Calendar_date or Date_time when the event is or was planned to start. The value of the attribute need not be specified.

4.3.2 Event_relationship   EXPRESS-GMapping table

An Event_relationship is a relationship which exists between two Events.

EXAMPLE    An instance of this entity data type with relation_type 'sequence' may be used to specify that an event shall end before another event starts.

EXPRESS specification:

*)
ENTITY Event_relationship;
  relation_type : STRING;
  description : OPTIONAL STRING;
  relating_event : Event;
  related_event : Event;
END_ENTITY;
(*

Attribute definitions:

relation_type: the string that defines the kind of relationship that is specified.

Where applicable, the following values shall be used:

NOTE    The criteria for 'simultaneity' and in particular the allowed delay between two events declared simultaneous, are user-dependent.

description: the text that provides further information about the Event_relationship. The value of the attribute need not be specified.

relating_event: one of the instances of Event that is a part of the relationship.

related_event: the other related instance of Event is a part of the relationship. If one element of the relationship is dependent upon the other, this attribute shall be the dependent one.

4.3.3 Relative_event   EXPRESS-GMapping table

A Relative_event is a type of Event the start of which will occur, respectively has occurred, with a time offset from the start of another Event.

EXPRESS specification:

*)
ENTITY Relative_event
  SUBTYPE OF (Event);
  base_event : Event;
  offset : Duration;
END_ENTITY;
(*

Attribute definitions:

base_event: the Event with respect which the relative event is based on.

offset: the difference in time between the start of both events. A negative offset specifies that the Relative_event occurs before the base_event.



*)
END_SCHEMA;  -- Event_arm
(*


© ISO 2018 — All rights reserved