4 Information requirements

This clause specifies the information requirements for the Activity 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 Activity_arm;
(*

4.1 Units of functionality

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

• Activity.

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.

• Product_specification_or_set.

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

4.1.1 Activity

The Activity UoF specifies:

• the relationship between an activity and a product that performs the activity;

  EXAMPLE - 'XYZ_123' is a product specification. 'XYZ_123 start up' is an activity specification. An individual product of type XYZ_123 can perform an activity of type 'XYZ_123 start up'.

• the relationship between two activities 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 start up' is an activity specification. 'XYZ_123 drive shaft start up' is another activity specification. If an individual product of type 'XYZ_123' performs the activity 'XYZ_123 start up', then it contains an 'XYZ_123 drive shaft' that performs the activity 'XYZ_123 drive shaft start up'.

  The existence of activity 'XYZ_123 start up' depends upon the existence of activity 'XYZ_123 drive shaft start up'.

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

  EXAMPLE - 'XYZ_123 start up' is an activity specification. 'XYZ_123 start up when cold' and 'XYZ_123 start up when hot' are two other activity specifications.

  Valve 'XYZ_123/V_1' closes after 50 seconds for activity specification 'XYZ_123 start up when cold', but closes after 10 seconds for activity specification 'XYZ_123 start up when hot'.

  Both activity specification 'XYZ_123 start up when cold' and activity specification 'XYZ_123 start up when hot' are specialisations of the more generic activity specification 'XYZ_123 start up'.

The following application objects are used by the Activity UoF:

• Activity;
• Activity_for_product;
• Composition_of_activity;
• Creating_activity_for_product;
• Destroying_activity_for_product;
• Specialisation_of_activity.

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 Activity module:

• Class_of_physical_individual;
• Mapping;
• Specialisation_of_class.

4.1.3 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 Activity module:

• Product_specification_or_set.

4.2 Required AM ARMs

EXPRESS specification:

*)
USE FROM Engineering_analysis_basics_arm -- Engineering_analysis_basics
  (Class_of_physical_individual,
  Mapping,
  Specialisation_of_class);
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

• Activity
• Activity_for_product
• Composition_of_activity
• Creating_activity_for_product
• Destroying_activity_for_product
• Specialisation_of_activity

4.5 ARM rule definitions

• none.

4.6 ARM function definitions

• none.

EXPRESS specification:

*)
END_SCHEMA;
(*