4 Information requirements

This clause specifies the information requirements for the Required resource 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.

This clause defines the information requirements to which implementations shall conform using the EXPRESS language as defined in ISO 10303-11. The following begins the Required_resource_arm schema and identifies the necessary external references.

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 Requirement_identification_and_version_arm;    --  ISO/TS 10303-1140



USE FROM Resource_item_arm;    --  ISO/TS 10303-1268



USE FROM Value_with_unit_arm;    --  ISO/TS 10303-1054
(*



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

Classification_assignment_arm	ISO/TS 10303-1114
Requirement_identification_and_version_arm	ISO/TS 10303-1140
Resource_item_arm	ISO/TS 10303-1268
Value_with_unit_arm	ISO/TS 10303-1054

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 required_resource_classification_item   

The required_resource_classification_item type is an extension of the classification_item type. It adds the data types Required_resource, Required_resource_assignment and Required_resource_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 required_resource_classification_item = EXTENSIBLE GENERIC_ENTITY SELECT BASED_ON classification_item WITH
   (Required_resource,
    Required_resource_assignment,
    Required_resource_relationship);
END_TYPE;
(*

4.2.2 required_resource_item   

The required_resource_item type is an extensible list of alternate data types. Additional alternate data types are specified in select data types that extend the required_resource_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 required_resource_item = EXTENSIBLE GENERIC_ENTITY SELECT;
END_TYPE;
(*

4.2.3 resource_requirement_select   

The resource_requirement_select type is an extensible list of alternate data types that allows for the designation of the data type Requirement_version.

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

EXPRESS specification:

*)
TYPE resource_requirement_select = EXTENSIBLE SELECT
   (Requirement_version);
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 Required_resource   

A Required_resource is an identified need for resource. The role of a required resource is determined by classification.

EXAMPLE 1   "facility", "test equipment", "supervisor" are examples of classifications of a required resource.

EXPRESS specification:

*)
ENTITY Required_resource
  ABSTRACT SUPERTYPE OF (ONEOF (Required_resource_by_reference,
                                Required_resource_by_requirement,
                                Required_resource_by_resource_item));
  name : STRING;
  description : OPTIONAL STRING;
  required_quantity : OPTIONAL Value_with_unit;
END_ENTITY;
(*

Attribute definitions:

name: the words by which the required resource is known.

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

required_quantity: the required quantity of the required resource. The value of this attribute need not be specified.

EXAMPLE 2   Quantity can be specified using amount or duration.

4.3.2 Required_resource_assignment   

EXAMPLE 1   task, task step, activity, activity method, organization are examples of entities to which the resource requirement statement could be related.

EXAMPLE 2   The assignment can be classified as "required by".

NOTE    An association between a required resource and actions that are needed prior to its usage.

EXAMPLE 3   A resource required by the activity "12" needs to be calibrated prior to usage. The calibration activity "21" is associated with the same required resource.using

EXAMPLE 4   A resource required by the task "123" needs to be disposed after its usage. This disposal task "456" is associated with the same required resource.

EXPRESS specification:

*)
ENTITY Required_resource_assignment;
  assigned_resource : Required_resource;
  item : required_resource_item;
END_ENTITY;
(*

Attribute definitions:

assigned_resource: the required resource that is to be associated with the requiring entity.

item: the entity to which the required resource statement is assigned.

4.3.3 Required_resource_by_reference   

EXPRESS specification:

*)
ENTITY Required_resource_by_reference
  SUBTYPE OF (Required_resource);
  item : resource_item_select;
END_ENTITY;
(*

Attribute definitions:

item: a reference to an item that satifies a resource requirement.

4.3.4 Required_resource_by_requirement   

EXPRESS specification:

*)
ENTITY Required_resource_by_requirement
  SUBTYPE OF (Required_resource);
END_ENTITY;
(*

4.3.5 Required_resource_by_resource_item   

EXPRESS specification:

*)
ENTITY Required_resource_by_resource_item
  SUBTYPE OF (Required_resource);
  resource_item : Resource_item;
END_ENTITY;
(*

Attribute definitions:

resource_item: a reference to an identifiable Resource_item (within the application context) that will satisfy that requirement.

EXAMPLE    Tool kit, facility, and product category are examples of resource items.

4.3.6 Required_resource_relationship   

EXAMPLE 1   "alternative" and "realized by" are examples of required resource relationship.

EXAMPLE 2   A Required_resource_by_requirement for a power supply may be realized by a Required_resource_by_reference with part number "ABC-1234".

EXPRESS specification:

*)
ENTITY Required_resource_relationship;
  name : STRING;
  description : OPTIONAL STRING;
  relating : Required_resource;
  related : Required_resource;
END_ENTITY;
(*

Attribute definitions:

name: the words by which the relationship is known.

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

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

related: the other instance of Required_resource that is a part of the relationship. If one element of the relationship is dependent upon the other, this attribute shall be the dependent one.

4.3.7 Required_resource_requirement   

EXPRESS specification:

*)
ENTITY Required_resource_requirement;
  item : resource_requirement_select;
  resource_requirement : Required_resource_by_requirement;
END_ENTITY;
(*

Attribute definitions:

item: the Requirement_version that (possibly together with other requirement versions) fulfills the Required_resource_by_requirement.

resource_requirement: the Required_resource_by_requirement that is fulfilled by one or more requirement version entities

© ISO 2011 — All rights reserved