Business overview

This section provides a business level overview of this capability.

When engineers speak generally of "resources", they may be considering the requirement for a resource:

The Resource_as_realized entity is used to represent tokens of resources that are actually used or consumed or that are intended for use or consumption. This caveat reflects that fact that the equipment assigned to a particular task may be faulty or whatever and alternative equipment may actually be used. In both cases, Assuming complete records were kept) the items of equipment would be represented by use of the Resource_as_realized entity.

Relating realized resources to actual activities

Information model overview

This section provides an overview of the information model that supports this capability.

The EXPRESS-G for the representing resource as realized is shown in Figure 1 below and explained in the following sections.

NOTE 1   The EXPRESS-G is not complete. For the complete EXPRESS see the module: Resource as realized and

Figure 1 —  Representing resource EXPRESS-G

Relating realized resources to activities and events

Realized resources may be related to event or activities that consume, or are expected to consume those resources.

Figure 2 —  Realized resources and activities

The Resource_as_realized_assignment allows a Resource_as_realized to be related to:

• Activity_actual;
• Applied_activity_assignment;
• Event; or
• Relative_event.

Relating realized resources to resource items

Realized resources may be related to the resource types that they realize.

Figure 3 —  Realized resources and resource items

The Resource_as_realized_resource_item allows a Resource_as_realized to be related to:

• Resource_item.

Relating realized resources to resource requirements

Realized resources may be related to the resource requirements which may be descrived in a variety of ways.

Figure 4 —  Realized resources and resource items

The Resource_as_realized_relationship allows a Resource_as_realized to be related to:

• Decreasing_resource_event;
• Increasing_resource_event;
• Required_resource_by_item; or
• Required_resource_by_specification.

Model Characterization

This section specifies how the information model can be further characterized by the assignment of additional information such as dates, approvals and people or organizations.

The following characterizations may apply.

Characterization: general (Optional)

Most of the constructs shown in Figure 1 can be characterized; which is to say that they may have approvals, classifications, conditions, dates or times, identifiers, justifications, persons or organizations, or properties assigned to them. The following sections detail the characterization of resource objects.

Characterization: Assigning approvals (Optional)

Approvals of realized resources or of resource assignments are represented by the assignment of Approval objects to Resource_as_realized, Resource_as_realized_assignment, and Resource_as_realized_resource_item, objects using Approval_assignment objects.

NOTE 10   The assignment of approvals is described in the capability: C019: assigning_approvals.

Characterization: Assigning classifications (Optional)

The classification of realized resources or of resource assignments or of required resource relationships is represented by the assignment of Classification_assignment objects to Resource_as_realized, Resource_as_realized_assignment, Resource_as_realized_resource_item, and Resource_as_realized_relationship objects using Approval_assignment objects.

Capability templates

The following sections define a set of templates for the capability, where a template is a specification of a set of entities that need to be instantiated to represent a given set of information.

This section specifies the template assigning_realized_resource.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Figure 1 —  An EXPRESS-G representation of the Information model for assigning_realized_resource

Figure 2 —  The graphical representation of the assigning_realized_resource template

Figure 3 —  Entities instantiated by assigning_realized_resource template

          #1 = ACTIVITY_ACTUAL('/IGNORE','/IGNORE','/IGNORE',$);
          #2 = RESOURCE_AS_REALIZED_RESOURCE_ITEM('/IGNORE','/IGNORE',#5,#7);
          #3 = RESOURCE_AS_REALIZED_ASSIGNMENT(#2,#1);
          #4 = PART('/IGNORE','/IGNORE','/IGNORE');
          #7 = RESOURCE_ITEM('/IGNORE','/IGNORE',(#4));
          #9 = IDENTIFICATION_ASSIGNMENT('ABC123','/IGNORE','/IGNORE',(#7));
          #11 = CLASSIFICATION_ASSIGNMENT(#12,(#9),'/IGNORE');
          #12 = EXTERNAL_CLASS('/NULL','Resource_item_identification_code','/IGNORE',#13);
          #13 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std','/IGNORE');
          #16 = ORGANIZATION('/IGNORE','/IGNORE');
          #18 = IDENTIFICATION_ASSIGNMENT('ACME Inc','/IGNORE','/IGNORE',(#16));
          #20 = CLASSIFICATION_ASSIGNMENT(#21,(#18),'/IGNORE');
          #21 = EXTERNAL_CLASS('/NULL','Organization_name','/IGNORE',#13);
          #23 = ORGANIZATION($,$);
          #24 = ORGANIZATION_OR_PERSON_IN_ORGANIZATION_ASSIGNMENT(#23,'/IGNORE',(#9));
          #26 = CLASSIFICATION_ASSIGNMENT(#27,(#24),'/IGNORE');
          #27 = EXTERNAL_CLASS('/NULL','Owner_of','/IGNORE',#13);
          #30 = CLASSIFICATION_ASSIGNMENT(#31,(#3),'/IGNORE');
          #31 = EXTERNAL_CLASS('/NULL','Resource_as_realized_employed_by','/IGNORE',#32);
          #32 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std','/IGNORE');
        

Figure 4 —  Instantiation of assigning_realized_resource template

Figure 5 —  Characterizations of assigning_realized_resource

Model reference data

The following classes of reference data are required for this capability:

© OASIS 2010 — All rights reserved