AP scope  |  AP module  |  AP contents  |  AP index
Application module: State observed ISO/TS 10303-1256: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 ARMs
   4.2 ARM type definitions
   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
     5.2.2 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 State observed 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 State_observed_arm schema and identifies the necessary external references.

EXPRESS specification:

*)
SCHEMA State_observed_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 Classification_assignment_arm;    --  ISO/TS 10303-1114

USE FROM State_definition_arm;    --  ISO/E2 WD 10303-1255
(*

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

Classification_assignment_arm ISO/TS 10303-1114
State_definition_arm ISO/E2 WD 10303-1255

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

4.2 ARM type definitions

This subclause specifies the ARM types for this application module. The ARM types and definitions are specified below.

4.2.1 state_classification_item   EXPRESS-G

The state_classification_item type is an extension of the classification_item type. It adds the data types Applied_state_assignment, State and State_relationship to the list of alternate data types.

NOTE  The list of entity data types may be extended in application modules that use the constructs of this module.

EXPRESS specification:

*)
TYPE state_classification_item = EXTENSIBLE GENERIC_ENTITY SELECT BASED_ON classification_item WITH
   (Applied_state_assignment,
    State,
    State_relationship);
END_TYPE;
(*

4.2.2 state_of_item   EXPRESS-G

The state_of_item type is an extensible list of alternate data types. Additional alternate data types are specified in select data types that extend the state_of_item type.

NOTE   This empty extensible select requires extension in a further module to ensure that entities that refer to it have at least one valid instantiation.

EXPRESS specification:

*)
TYPE state_of_item = EXTENSIBLE GENERIC_ENTITY SELECT;
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 Applied_state_assignment   EXPRESS-GMapping table

An Applied_state_assignment is a relationship that allows a subject to have State or to be in a State.

EXPRESS specification:

*)
ENTITY Applied_state_assignment;
  described_state : State;
  assigned_to : state_of_item;
  role : State_role;
END_ENTITY;
(*

Attribute definitions:

described_state: a State the subject has or is in.

assigned_to: the subject which has or is in a State.

role: the purpose of the association of the Applied_state_assignment with product or activity data.

4.3.2 Composition_of_state   EXPRESS-GMapping table

A Composition_of_state is a type of state relationship and it relates the nature of states in relation to one another, where two or more State parts compose a whole State; and furthermore, whole states can become parts of yet another whole State.

EXPRESS specification:

*)
ENTITY Composition_of_state
  SUBTYPE OF (State_relationship);
  SELF\State_relationship.relating RENAMED whole : SET[1:?] OF State;
  SELF\State_relationship.related RENAMED part : SET[1:?] OF State;
END_ENTITY;
(*

Attribute definitions:

whole: a complete State which contain parts of its state composition.

part: the State parts that comprise a whole State.

4.3.3 Defined_state_relationship   EXPRESS-GMapping table

A Defined_state_relationship is a relationship that links a State_assertion to a State_assessment.

EXPRESS specification:

*)
ENTITY Defined_state_relationship;
  name : STRING;
  description : OPTIONAL STRING;
  definitive_state : State_assertion;
  defined_state : State_assessment;
END_ENTITY;
(*

Attribute definitions:

name: the words by which the Defined_state_relationship is known.

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

definitive_state: the State_assertion being related to the defined subject State from State_assessment.

defined_state: the State_assessment being related to the definitive subject State from State_assertion.

4.3.4 Sequence_of_state   EXPRESS-GMapping table

A Sequence_of_state is a type of State_relationship in which one set of States precedes another set of States.

EXPRESS specification:

*)
ENTITY Sequence_of_state
  SUBTYPE OF (State_relationship);
  SELF\State_relationship.relating RENAMED successor : SET[1:?] OF State;
  SELF\State_relationship.related RENAMED predecessor : SET[1:?] OF State;
END_ENTITY;
(*

Attribute definitions:

successor: the next State in the sequence.

predecessor: the previous State in the sequence.

4.3.5 State   EXPRESS-GMapping table

A State is the mode of being in which something does or could exist or existed for a period of time.

NOTE 1   A state's existence can be just a state that an object is currently in, a predicted state that an object will eventually be in, or an observed state that an object has been in.

NOTE 2   The period of existence may be an instant or longer.

EXAMPLE 1   Main Engine No. 1 is in "operation".

EXAMPLE 2   When Generator No. 2 surpasses 5,000 service hours, it will enter "maintenance" mode.

EXAMPLE 3   The portable computer's power supply was attached after it displayed a "low-battery" warning.

EXPRESS specification:

*)
ENTITY State
  SUPERTYPE OF (ONEOF (State_observed,
                       State_predicted));
  name : STRING;
  description : OPTIONAL STRING;
END_ENTITY;
(*

Attribute definitions:

name: the words by which the State is known.

NOTE    Identifiers are assigned to State using statechar_identification_item.

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

4.3.6 State_assertion   EXPRESS-GMapping table

A State_assertion is used to assert that the subject State is in conformance with a particular
[warning:]Error ER-7: The express_ref linkend
    state_definition:arm:State_definition_arm.State_definition
     is incorrectly specified.
     The data type State_definition_arm.State_definition does not exist.
    Note linkend is case sensitive.

State_definition.

EXPRESS specification:

*)
ENTITY State_assertion;
  name : STRING;
  description : OPTIONAL STRING;
  asserted_state : State;
  conformance_state : State_definition;
END_ENTITY;
(*

Attribute definitions:

name: the words by which the State_assertion is known.

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

asserted_state: the subject State being asserted.

conformance_state: a particular
[warning:]Error ER-7: The express_ref linkend
    state_definition:arm:State_definition_arm.State_definition
     is incorrectly specified.
     The data type State_definition_arm.State_definition does not exist.
    Note linkend is case sensitive.

State_definition the subject State is being asserted against.

4.3.7 State_assessment   EXPRESS-GMapping table

A State_assessment is used to determine whether the subject State is comparable with a particular
[warning:]Error ER-7: The express_ref linkend
    state_definition:arm:State_definition_arm.State_definition
     is incorrectly specified.
     The data type State_definition_arm.State_definition does not exist.
    Note linkend is case sensitive.

State_definition.

EXPRESS specification:

*)
ENTITY State_assessment;
  name : STRING;
  description : OPTIONAL STRING;
  assessed_state : State;
  comparable_state : State_definition;
END_ENTITY;
(*

Attribute definitions:

name: the words by which the State_assessment is known.

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

assessed_state: a subject State that will be assessed against a particular
[warning:]Error ER-7: The express_ref linkend
    state_definition:arm:State_definition_arm.State_definition
     is incorrectly specified.
     The data type State_definition_arm.State_definition does not exist.
    Note linkend is case sensitive.

State_definition.

comparable_state: a particular
[warning:]Error ER-7: The express_ref linkend
    state_definition:arm:State_definition_arm.State_definition
     is incorrectly specified.
     The data type State_definition_arm.State_definition does not exist.
    Note linkend is case sensitive.

State_definition the subject State is assessed against.

4.3.8 State_cause_effect   EXPRESS-GMapping table

A State_cause_effect is a type of state relationship and it relates two or more states as one state causing particular resulting effect state(s). In turn, an effect state can become a new causing state yielding in yet more effect states.

EXPRESS specification:

*)
ENTITY State_cause_effect
  SUBTYPE OF (State_relationship);
  SELF\State_relationship.relating RENAMED effect : SET[1:?] OF State;
  SELF\State_relationship.related RENAMED cause : SET[1:?] OF State;
END_ENTITY;
(*

Attribute definitions:

effect: a State resulting from a cause State.

cause: a State causing an effect State.

4.3.9 State_observed   EXPRESS-GMapping table

A State_observed is a type of State. It is an individual or realized State that is observed.

EXPRESS specification:

*)
ENTITY State_observed
  SUBTYPE OF (State);
END_ENTITY;
(*

4.3.10 State_predicted   EXPRESS-GMapping table

A State_predicted is a type of State It is a predicted actual State. Where a predicted state needs to be related to an observed state, the State_predicted_to_observed entity shall be used.

EXPRESS specification:

*)
ENTITY State_predicted
  SUBTYPE OF (State);
END_ENTITY;
(*

4.3.11 State_predicted_to_observed   EXPRESS-GMapping table

A State_predicted_to_observed is a type of state relationship. It specifies the relationship between two individual states, one of which is a State_predicted to a second state which is a State_observed.

EXPRESS specification:

*)
ENTITY State_predicted_to_observed
  SUBTYPE OF (State_relationship);
  SELF\State_relationship.relating RENAMED observed_state : SET[1:?] OF State_observed;
  SELF\State_relationship.related RENAMED predicted_state : SET[1:?] OF State_predicted;
END_ENTITY;
(*

Attribute definitions:

observed_state: the observed state.

predicted_state: the predicted state.

4.3.12 State_relationship   EXPRESS-GMapping table

A State_relationship is a relationship between two or more States.

EXPRESS specification:

*)
ENTITY State_relationship;
  name : STRING;
  description : OPTIONAL STRING;
  relating : SET[1:?] OF State;
  related : SET[1:?] OF State;
END_ENTITY;
(*

Attribute definitions:

name: the words by which the State_relationship is known.

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

relating: one of the set of instances of State that is a part of the relationship.

related: the other of the set of instances of State that is a part of the relationship.

4.3.13 State_role   EXPRESS-GMapping table

A State_role is a specification of the purpose of the association of the Applied_state_assignment with product or activity data.

EXPRESS specification:

*)
ENTITY State_role;
  name : STRING;
  description : OPTIONAL STRING;
END_ENTITY;
(*

Attribute definitions:

name: the words by which the State_role is known.

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

4.3.14 State_transition   EXPRESS-GMapping table

A State_transition is a type of state relationship and it relates two or more states before and after a transition in State, where at least one State is a start state and at least one State is an end state.

EXPRESS specification:

*)
ENTITY State_transition
  SUBTYPE OF (State_relationship);
  SELF\State_relationship.relating RENAMED end_state : SET[1:?] OF State;
  SELF\State_relationship.related RENAMED start_state : SET[1:?] OF State;
END_ENTITY;
(*

Attribute definitions:

end_state: an end state after transition.

start_state: a start state before transition.



*)
END_SCHEMA;  -- State_observed_arm
(*


© ISO 2004 — All rights reserved