AP scope  |  AP module  |  AP contents  |  AP index
Application module: Activity as realized ISO/TS 10303-1259:2004(E)
© ISO

Cover page
Table of contents
Copyright
Foreword
Introduction
1 Scope
2 Normative references
3 Terms, definitions and abbreviations

4 Information requirements
   4.1 Required AM ARM
   4.2 ARM entity definitions
5 Module interpreted model
   5.1 Mapping specification
   5.2 MIM EXPRESS short listing
     5.2.1 MIM entity 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
Bibliography
Index

4 Information requirements

This clause specifies the information requirements for the Activity as realized 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.

The following EXPRESS specification begins the Activity_as_realized_arm schema and identifies the necessary external references.

EXPRESS specification:

*)
SCHEMA Activity_as_realized_arm;
(*

4.1 Required AM ARM

The following EXPRESS interface statement specifies the elements imported from the ARM of another application module.

EXPRESS specification:

*)
USE FROM Activity_arm;    --  ISO/TS 10303-1047
(*

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

Activity_arm ISO/TS 10303-1047

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

4.2 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.2.1 Activity_actual   EXPRESS-GMapping table

An Activity_actual is a type of Activity. It is a record of the occurrence of an Activity. The Activity_actual is related through an Activity_happening to the Activity for which it is an occurrence. The existence of an Activity_actual instance means that the Activity_actual has started.

NOTE 1   A Calendar_date or Date_time should be assigned to the Activity_actual with the role "start date" to record when the activity started.

NOTE 2   A Calendar_date or Date_time may be assigned to the activity with role "end date" to record when the activity finished. In general, the absence of this assignment cannot be used to infer that the activity is continuing, only that the end of the activity has not yet been recorded.

NOTE 3   A more detailed history of the progress of an activity may be recorded by applying states to the activity, but the meaning of these states must be defined through local business rules.

EXPRESS specification:

*)
ENTITY Activity_actual
  SUBTYPE OF (Activity);
END_ENTITY;
(*

4.2.2 Activity_happening   EXPRESS-GMapping table

An Activity_happening is a type of Activity_relationship. It is a relationship between the definition of an activity (predicted) and its actual occurrence (actual).

NOTE 1   The ordinary value for name may be "actual", though this is redundant.

NOTE 2   Many Activity_actuals may be the actual for a single Activity.

EXAMPLE 1   a single defined activity is recorded historically by several sub-activities.

NOTE 3   A single Activity_actual may fulfil several activities.

EXAMPLE 2   a single servicing activity takes the opportunity to make additional checks and repairs.

EXPRESS specification:

*)
ENTITY Activity_happening
  SUBTYPE OF (Activity_relationship);
  SELF\Activity_relationship.relating_activity RENAMED actual : Activity_actual;
  SELF\Activity_relationship.related_activity RENAMED predicted : Activity;
WHERE
  WR1: NOT ('ACTIVITY_AS_REALIZED.ACTIVITY_ACTUAL' IN TYPEOF(predicted));
END_ENTITY;
(*

Attribute definitions:

actual: the Activity which is the record of the historical occurrence.

predicted: the Activity as defined in advance of its historical occurrence.

Formal propositions:

WR1: The Activity specified as predicted shall not be an Activity_actual.



*)
END_SCHEMA;  -- Activity_as_realized_arm
(*


© ISO 2004 — All rights reserved