AP scope  |  AP module  |  AP contents  |  AP index
Application module: Resource management ISO/TS 10303-1266: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

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 Resource management 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 Resource_management_arm schema and identifies the necessary external references.

EXPRESS specification:

*)
SCHEMA Resource_management_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 Location_assignment_arm;    --  ISO/TS 10303-1277

USE FROM Required_resource_arm;    --  ISO/TS 10303-1267

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
Location_assignment_arm ISO/TS 10303-1277
Required_resource_arm ISO/TS 10303-1267
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 managed_resource_location_assignment_select   EXPRESS-G

The managed_resource_location_assignment_select type is an extension of the location_assignment_select type. It adds the data type Managed_resource 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.

The place where the managed resource is found or stored.

EXAMPLE    The location of a managed resource can be a shelf in a warehouse, an organizational unit, or a serialized product that can be cannibalized.

EXPRESS specification:

*)
TYPE managed_resource_location_assignment_select = EXTENSIBLE GENERIC_ENTITY SELECT BASED_ON location_assignment_select WITH
   (Managed_resource);
END_TYPE;
(*

4.2.2 resource_management_classification_item   EXPRESS-G

The resource_management_classification_item type is an extension of the classification_item type. It adds the data types Managed_resource, Managed_resource_relationship, Resource_event, Resource_event_correspondence_relationship and Resource_event_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 resource_management_classification_item = EXTENSIBLE GENERIC_ENTITY SELECT BASED_ON classification_item WITH
   (Managed_resource,
    Managed_resource_relationship,
    Resource_event,
    Resource_event_correspondence_relationship,
    Resource_event_relationship);
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 Decreasing_resource_event   EXPRESS-GMapping table

A Decreasing_resource_event is a type of Resource_event that decreases the balance of a managed resource.

EXAMPLE    Filling a requisition reduces an inventory.

EXPRESS specification:

*)
ENTITY Decreasing_resource_event
  SUBTYPE OF (Resource_event);
END_ENTITY;
(*

4.3.2 Increasing_resource_event   EXPRESS-GMapping table

A Increasing_resource_event is a type of Resource_event that increases the balance of a managed resource.

EXAMPLE    Purchasing new stock increases an inventory.

EXPRESS specification:

*)
ENTITY Increasing_resource_event
  SUBTYPE OF (Resource_event);
END_ENTITY;
(*

4.3.3 Managed_resource   EXPRESS-GMapping table

A Managed_resource is a representation of a resource that is provided with resource management capabilities. The role of a managed resource is determined by classification.

EXAMPLE    A managed resource can be classified as "Stock line".

EXPRESS specification:

*)
ENTITY Managed_resource;
  name : STRING;
  description : OPTIONAL STRING;
  quantity : OPTIONAL Value_with_unit;
  item : Resource_item;
END_ENTITY;
(*

Attribute definitions:

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

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

quantity: the measure of the amount of the resource that is avaialable at a given location. The value of this attribute need not be specified.

item: the reference to a resource that can occur in the role of a managed resource within the application context.

NOTE    an item can refer to an actual resource as well as to a type of resource.

4.3.4 Managed_resource_relationship   EXPRESS-GMapping table

A Managed_resource_relationship is an association between two managed resources. The meaning of the relationship is determined by classification.

EXAMPLE    A managed resource relationship can be classified as "Alternative" or "Prefered".

EXPRESS specification:

*)
ENTITY Managed_resource_relationship;
  name : STRING;
  description : OPTIONAL STRING;
  relating : Managed_resource;
  related : Managed_resource;
END_ENTITY;
(*

Attribute definitions:

name: the words by which the managed resource relationship is known.

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

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

related: the other instance of Managed_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.5 Resource_event   EXPRESS-GMapping table

A Resource_event is an event or action that affects the balance or availability of a managed resource. The role of a resource event is determined by classification.

EXAMPLE    A resource event can be classified as "Planned" or "Actual".

EXPRESS specification:

*)
ENTITY Resource_event
  ABSTRACT SUPERTYPE ;
  name : STRING;
  description : OPTIONAL STRING;
  quantity : OPTIONAL Value_with_unit;
  resource : Managed_resource;
END_ENTITY;
(*

Attribute definitions:

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

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

quantity: the measure of the amount of resource affected by the change. The value of this attribute need not be specified.

resource: the managed resource that is affected by the resource event.

4.3.6 Resource_event_correspondence_relationship   EXPRESS-GMapping table

A Resource_event_correspondence_relationship is an association of a resource event and a corresponding statement of Required_resource. The meaning of the relationship is determined by classification.

NOTE    A resource event can be planned or recorded without having a corresponding resource requirement statement.

EXAMPLE    A resource event correspondence relationship can be classified as "Designated for".

EXPRESS specification:

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

Attribute definitions:

name: the words by which the Resource_event_correspondence_relationship is known.

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

relating: the instance of Resource_event that is a part of the relationship.

related: the instance of Required_resource being related.

4.3.7 Resource_event_relationship   EXPRESS-GMapping table

A Resource_event_relationship is a specification of how an Resource_event may be associated with another Resource_event. The meaning of the relationship is determined by classification.

EXAMPLE    A managed resource relationship can be classified as "realized by" or "replaces".

EXPRESS specification:

*)
ENTITY Resource_event_relationship;
  name : STRING;
  description : OPTIONAL STRING;
  relating : Resource_event;
  related : Resource_event;
END_ENTITY;
(*

Attribute definitions:

name: the words by which the relationship is known.

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

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

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



*)
END_SCHEMA;  -- Resource_management_arm
(*


© ISO 2004 — All rights reserved