4 Information requirements

This clause specifies the information requirements for the State application module.

The information requirements are specified as a set of units of functionality, application elements, and application assertions. These assertions pertain to individual application entities and to relationships between application entities. The information requirements are defined using the terminology of the subject area of this application module.

1. - A graphical representation of the information requirements is given in annex C.
2. - The mapping specification is specified in 5.1 which shows how the information requirements are met using the integrated resources of this International Standard. The use of the integrated resources introduces additional requirements which are common to application modules and application protocols.

EXPRESS specification:

*)
SCHEMA State_arm;
(*

4.1 Units of functionality

This subclause specifies the units of functionality (UoF) for the State application module as well as any support elements needed for the module definition. This part of ISO 10303 specifies the following units of functionality:

• State.

This part of ISO 10303 uses the following units of functionality:

• Engineering_analysis_basics;

  NOTE - The Engineering analysis basics AM contains supertypes of the application objects in this AM. These supertypes have no attributes and merely clarify the meaning of the application objects. These supertypes have no impact on the MIM.

• Activity;
• Product_specification_or_set.

The units of functionality and a description of the functions that each UoF supports are given below.

4.1.1 State

The State UoF specifies:

• the relationship between a state and a product that possesses the state;

  EXAMPLE - 'XYZ_123' is a product specification. 'XYZ_123 at full power' is a state specification. An individual product of type XYZ_123 can have a state of type 'XYZ_123 at full power'.

• the relationship between a state and an activity that causes a product to possesses the state;

  EXAMPLE - 'XYZ_123 start up' is an activity specification. 'XYZ_123 at full power' is a state specification. An individual activity of type 'XYZ_123 start up' ends with an individual product in a state of type 'XYZ_123 at full power'.

• the relationship between two states that indicates the existence of one depends upon the existence of the other;

  EXAMPLE - 'XYZ_123' is a product specification. 'XYZ_123 drive shaft' is another property specification that is a part of 'XYZ_123'.

  'XYZ_123 at full power' is a state specification. 'XYZ_123 drive shaft turning at 3000 rpm' is another state specification. If an individual product of type 'XYZ_123' is in state 'XYZ_123 at full power', then it contains an 'XYZ_123 drive shaft' in state 'XYZ_123 drive shaft turning at 3000 rpm'.

• the relationship between two states that indicates one is a specialisation of the other.

  EXAMPLE - 'XYZ_123 at full power' is a state specification. 'XYZ_123 at full power when cold' and 'XYZ_123 at full power when hot' are two other state specifications.

  The drive shaft of product specification 'XYZ_123' turns at 3000 rpm for each of these three state specifications. Valve 'XYZ_123/V_1' is open for state specification 'XYZ_123 at full power when cold', but closed for state specification 'XYZ_123 at full power when hot'.

  An individual product of type 'XYZ_123' can change from being in state 'XYZ_123 at full power when cold' to being in state 'XYZ_123 at full power when hot', whilst remaining in state 'XYZ_123 at full power'.

  Both state specification 'XYZ_123 at full power when cold' and state specification 'XYZ_123 at full power when hot' are specialisations of the more generic state specification 'XYZ_123 at full power'.

The following application objects are used by the State UoF:

• Composition_of_state;
• Final_state_for_activity;
• Initial_state_for_activity;
• Specialisation_of_state;
• State;
• State_for_activity;
• State_for_product.

4.1.2 Engineering_analysis_basics

This UoF is defined in the Engineering_analysis_basics module. The following application entities from this UoF are referenced in the State module:

• Class_of_physical_individual;
• Mapping;
• Specialisation_of_class.

4.1.3 Activity

This UoF is defined in the Activity module. The following application entities from this UoF are referenced in the State module:

• Activity.

4.1.4 Product_specification_or_set

This UoF is defined in the Product_specification_or_set module. The following application entities from this UoF are referenced in the State module:

• Product_specification_or_set.

4.2 Required AM ARMs

*)
USE FROM Engineering_analysis_basics_arm -- Engineering_analysis_basics
  (Class_of_physical_individual,
  Mapping,
  Specialisation_of_class);
USE FROM Activity_arm -- Activity
  (Activity);
USE FROM Product_specification_or_set_arm -- Product_specification_or_set
  (Product_specification_or_set);
(*

4.3 ARM type definitions

• none.

4.4 ARM entity definitions

• Composition_of_state
• Final_state_for_activity
• Initial_state_for_activity
• Specialisation_of_state
• State
• State_for_activity
• State_for_product

4.5 ARM rule definitions

• none.

4.6 ARM function definitions

• none.

EXPRESS specification:

*)
END_SCHEMA;
(*