Capability (C043):— representing_environment_typical Date: 2007/02/02 10:14:08
Revision: 1.23

Capability EXPRESS information model

This section describes the EXPRESS information model for the capability.

Open issue Issue: GYL-7 by Leif Gyllstrom (2005-11-09) [minor_technical, open] - {Type = usage}
In the examples given the State_definition representing the state is classified as State_of_environment. This is missleading since the State_definition is not defining the state of the environment but the environment itself. If Environment_typical would have been a subclass od State_definition in the ARM it would probably have been namned Environment_typical. Therefore I would suggest to create a subclass to State_definition in the RDL named "Environment_typical"
Closed issue Issue: GYL-6 by Leif Gyllstrom (2004-03-06) [minor_technical, closed] - {Type = usage}
Should the state_definition module really be part of the usage section since it's being brought in by the representing_state_type capability ?
Comment: (Rob Bodington 04-05-07)
The capability is no longer dependent on representing_state_type capability As all that is required from the state_definition module is state_definition. It makes no sense to typical environments. Any environment can follow on from any other environment.

From module : state_definition - using subset



TYPE state_definition_activity_item = EXTENSIBLE GENERIC_ENTITY SELECT BASED_ON activity_item WITH
   (Applied_state_definition_assignment);
END_TYPE;



TYPE state_definition_classification_item = EXTENSIBLE GENERIC_ENTITY SELECT BASED_ON classification_item WITH
   (Applied_state_definition_assignment,
    State_definition,
    State_definition_relationship);
END_TYPE;



TYPE state_definition_identification_item = EXTENSIBLE SELECT BASED_ON identification_item WITH
   (State_definition,
    State_definition_relationship);
END_TYPE;



TYPE state_definition_of_item = EXTENSIBLE GENERIC_ENTITY SELECT;
END_TYPE;


Applied_state_definition_assignment

An Applied_state_definition_assignment is a mechanism that enables an object to have or to be in a State_definition.

The Applied_state_definition_assignment represents the fact that a given Product_as_individual (Either planned Product_as_planned or actual Product_as_realized) can operate in a given typical environment.


ENTITY Applied_state_definition_assignment;
  described_state_definition : State_definition;
  assigned_to : state_definition_of_item;
  role : State_definition_role;
END_ENTITY;

described_state_definition: the State_definition that is assigned.

assigned_to: the object whose State_definition is given by the described_state_definition.

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


State_definition

A State_definition is a mode of being. A State_definition defines the types of State that can exist. A State's existence can be assessed and asserted against State_definition from State.

The State_definition represents a typical environment.

The State_definition is classified as "State_of_environment" (urn:plcs:rdl:std:State_of_environment).

The State_definition is identified by using Identification_assignment to assign an identifier as described in C001: assigning_identifiers.


ENTITY State_definition;
  name : STRING;
  description : OPTIONAL STRING;
END_ENTITY;

name: the words by which the State_definition is known.

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