Template:— support_node (supt_node)
Context:— UK_Defence
Date: 2009/04/17 11:58:03
Revision: 1.4

This section specifies the template support_node.

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.

Description

This template describes how to represent an organisational node at a specific location within the support system.

Business perspective

The support node business object is used by those UK_Defence Data Exchange Specifications that require information about an organisational node at a specific location within the support system.

Business object definition


Figure 1 —  Graphical Representation for Business Object Support Node

Figure 1 —  Graphical Representation for Business Object Support Node

Support Node:

The definition of an Support Node object is: Data about an organisational node at a specific location within the support system.

Attribute name

Attribute description

Attribute type

Optionality

ID This is the Identifier of the support node. Identifier Mandatory
Located at This is the reference to the location at which the support node is located. Relationship to Located Mandatory
Name This is the name of the support node. Intrinsic Mandatory
Responsibility of This is the reference to the organization that has responsibility for the support node. Relationship to Organization Mandatory

Table 1 — Support Node attribute details

Model diagrams
The EXPRESS-G diagram in Figure 2 shows the templates and EXPRESS entities that are required to represent the template "support_node". The text highlighted in blue shows the template parameters.


Figure 2 —  An EXPRESS-G representation of the Information model for support_node

Figure 2 —  An EXPRESS-G representation of the Information model for support_node

The graphic for the template to be used in other EXPRESS-G diagrams is shown in Figure  3 below.


Figure 3 —  The graphical representation of the support_node template

Figure 3 —  The graphical representation of the support_node template

Input parameters
The following input parameters are defined for this template:
ID (Type='STRING')
This is the identifier of the support node.
source_organization (Type='STRING')
The organization that created the associated identifier. Additionally a Person or Information System could be defined when either of these are the source; see Identifier template.
located_at (Type= 'ENTITY (Location)' )
This is the reference to the location at which the support node is located.
name (Type='STRING')
This is the name of the support node.
responsibility_of (Type= 'ENTITY (Organization)' )
This is the reference to the organization that has responsibility for the support node.
Reference parameters
The following reference parameters are defined for this template:
support_node(Type='ENTITY (Organization)')
Allow the Organization entity instantiated in this path to be referenced when this template is used.
Note: The Organization entity can be referenced in a template path by:
%^target = $support_node.support_node%
where target is the parameter to which the Organization is bound.
Uniqueness constraints

The following parameter combinations specify a uniqueness constraint:
Unique constraint: Support_node
Each instance of the entity (Organization) within the data set shall be uniquely identified by a combination of the following parameters on this template (support_node) namely: ID, name, responsibility_of.
The instance is referenced by the following template parameter: support_node.
Instantiation path
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.
-- Instantiate an organization
/organization(
    ID=@ID,
    source_organization=@source_organization,
    address='/IGNORE',
    description='/IGNORE',
    end_date='/IGNORE',
    name=@name,
    short_name='/IGNORE',
    start_date='/IGNORE')/
%^support_node = $organization.organization%

-- Instantiate an assignment to the location
Location_assignment
Location_assignment.entity_for_location -> ^support_node
Location_assignment.location_for_assignment -> @located_at
Location_assignment.description = '/IGNORE'
Location_assignment.role = '/IGNORE'

-- Instantiate an Organization_relationship
Organization_relationship
Organization_relationship.relation_type = '/IGNORE'
Organization_relationship.description = '/IGNORE'
Organization_relationship.relating_organization -> @responsibility_of
Organization_relationship.related_organization -> ^support_node
The following entities are instantiated with attributes as specified:
Entity in path Value Inherited from
Location_assignment.description '/IGNORE'
Location_assignment.role '/IGNORE'
Organization_relationship.relation_type '/IGNORE'
Organization_relationship.description '/IGNORE'
Instance diagrams
The instance diagram in Figure  4 shows an example of the EXPRESS entities and templates that are instantiated by the template:
/support_node(ID='SN123', source_organization='UK_Defence', located_at='@73', name='RAF Wyton', responsibility_of='@226')/
(an illustration of the consolidated support_node template is shown in Figure 5 below.)


Figure 4 —  Entities instantiated by support_node template

Figure 4 —  Entities instantiated by support_node template

The instance diagram in Figure 5 shows the graphic symbol for the template that is to be used in other instance diagrams. The example template is:
/support_node(ID='SN123', source_organization='UK_Defence', located_at='@73', name='RAF Wyton', responsibility_of='@226')/


Figure 5 —  Instantiation of support_node template

Figure 5 —  Instantiation of support_node template

Characterizations
No common characterizations of the template support_node have been identified. However, the ISO 10303-239 EXPRESS model may enable other assignments to the entities instantiated by the template.

© UK MOD 2010 — All rights reserved