NOTE The template has been defined in the context of UK_Defence. Refer to the business context for details of related templates.

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

This template describes how to represent the response that is given to an inventory item demand.

An Inventory Item Demand Response is the response to an inventory item demand.

This information object represents the information about an Inventory Item Demand Response.

Figure 1 — A MOOD Business Architect representation of the Business Object: Inventory Item Demand Response

The attributes of the Inventory Item Demand Response object are tabled below.

Attribute name	Attribute description	Attribute type	Optionality
Date demand received	This is the date and time on which the demand was received from the demanding organization.	Relationship to Date_time	Mandatory
Date of response	This is the date on which the response was made.	Relationship to Date_time	Mandatory
Description	This is a description of the response, where optional comments or reasons for referral or rejection may be recorded.	intrinsic	Optional
ID	This is the identifier of the response.	intrinsic	Mandatory
Identifier.id	This is the value of the id attribute of the Identifier applied to the response.	intrinsic	Mandatory
Identifier.type	This attribute is the type associated with the id of the Identifier given to the response.	Inventory_item_demand_response_id_code	Mandatory
Identifier.source_organization	This attribute is the value representing the source organization that provides the id of the Identifier given to the response. This value is assumed to be a type of Organization_identification_code.	Organization_identification_code	Mandatory
Related demand	This is the reference to the inventory item demand for which the response is provided.	Relationship to Inventory Item Demand	Mandatory
Responding organization	This is the reference to the organizational unit that makes the response.	Relationship to Organizational Unit	Mandatory
Response	This is the response that is given. This may be: - accept (this is sometimes called a "due out") - refer (ie a decision is not possible immediately) - reject	intrinsic	Mandatory
Response to	This is the reference to the organizational unit to which the response is sent.	Relationship to Organizational Unit	Mandatory

Table 1 — Inventory Item Demand Response attribute details

The following input parameters are defined for this template:

The following reference parameters are defined for this template:

The instantiation path shown below specifies the entities that are to be instantiated by the template.

A description of templates and the syntax for the instantiation path is provided in the Templates Help/Information section.

-- demand response
Required_resource_by_resource_item

-- Item_of_supply
Required_resource_by_resource_item.resource_item -> @related_item_of_supply
%^req_res_item = Required_resource_by_resource_item%

-- date_demand_received
Date_or_date_time_assignment
%^date_demand_received = Date_or_date_time_assignment%
^date_demand_received.assigned_date -> @date_demand_received
^date_demand_received.role = 'date_demand_received'
^date_demand_received.items -> ^req_res_item

-- date_of_response
Date_or_date_time_assignment
%^date_of_response = Date_or_date_time_assignment%
^date_of_response.assigned_date -> @date_of_response
^date_of_response.role = 'date_of_response'
^date_of_response.items -> ^req_res_item

-- [optional description]
/assigning_descriptor(
    descr=@description,
    class_name='Description',
    ecl_id='urn:plcs:rdl:std',
    is_assigned_to=^req_res_item)/

-- id
/identifier(
    ID=@id,
    source_organization=@source_organization,
    type='Inventory_item_demand_response_id_code',
    items=^req_res_item )/

-- related_demand
Required_resource_assignment
Required_resource_assignment.assigned_resource -> ^req_res_item
Required_resource_assignment.item -> @related_demand
%^req_res_asst = Required_resource_assignment%

-- responding_organization
Organization_or_person_in_organization_assignment
Organization_or_person_in_organization_assignment.role = '/IGNORE'
Organization_or_person_in_organization_assignment.items -> ^req_res_item
Organization_or_person_in_organization_assignment.assigned_entity -> @responding_organization

-- response
/assigning_descriptor(
    descr=@response,
    class_name='response',
    ecl_id='urn:plcs:rdl:uk_defence',
    is_assigned_to=^req_res_item)/

-- response_to
Organization_or_person_in_organization_assignment
Organization_or_person_in_organization_assignment.role = '/IGNORE'
Organization_or_person_in_organization_assignment.items -> ^req_res_item
Organization_or_person_in_organization_assignment.assigned_entity -> @response_to

The following entities are instantiated with attributes as specified:

Entity in path	Value	Inherited from
Date_or_date_time_assignment.role	'date_demand_received'	—
Date_or_date_time_assignment.role	'date_of_response'	—
Organization_or_person_in_organization_assignment.role	'/IGNORE'	—
Organization_or_person_in_organization_assignment.role	'/IGNORE'	—

The instance diagram in Figure 4 shows an example of the EXPRESS entities and templates that are instantiated by the template:

/inventory_item_demand_response(date_demand_received='#430', date_of_response='#435', id='demand_response_123', source_organization='6421', related_demand='#440', responding_organization='#50', response='reject', description='faulty', response_to='#149', related_item_of_supply='#248')/

(an illustration of the consolidated inventory_item_demand_response template is shown in Figure 5 below.)