Template:— organizational_unit_non_standard_location (org_unit_non_std_loc)
Context:— UK_Defence

Date: 2009/04/17 10:13:35
Revision: 1.4

Cover Contents Description Bus. obj.Model diags.Input params.Ref. params.Instantiation path Instance diags.Characterizations Issues in situ

This section specifies the template organizational_unit_non_standard_location.

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 the relationship between an organizational unit and the planned or actual locations in which it may be deployed at specific times.

Business object definition

Figure 1 — Graphical Representation for Business Object organizational_unit_non_standard_location

organizational_unit_non_standard_location

The definition of an organizational_unit_non_standard_location object is: This information object represents the relationship between an organizational unit and the planned or actual locations in which it may be deployed at specific times.

Attribute name	Attribute description	Attribute type	Optionality
Actual end date	This is the actual end date of the period the business unit is at this location.	intrinsic	Mandatory
Actual start date	This is the actual start date of the period the business unit is at this location.	intrinsic	Mandatory
ID	This is the identifier of the non-standard location.	Identifier	Mandatory
Identifier.id	This is the value of the id attribute of the Identifier applied to the non-standard location.	intrinsic	Mandatory
Identifier.type	This attribute is the type associated with the id of the Identifier given to the non-standard location.	non_standard_location_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 non-standard location. This value is assumed to be a type of Organization_identification_code.	Organization_identification_code	Mandatory
Location	This is a reference to the related location.	Relationship to Location	Mandatory
Organizational unit	This is a reference to the organizational unit for which the non standard location has been defined.	Relationship to Organizational Unit	Mandatory
Plannned end date	This is the planned end date of the period the business unit is at this location.	intrinsic	Mandatory
Planned start date	This is the planned start date of the period the business unit is at this location.	intrinsic	Mandatory

Table 1 — organizational_unit_non_standard_location attribute details

Model diagrams

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

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

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 organizational_unit_non_standard_location template

Input parameters

The following input parameters are defined for this template:

actual_end_date (Type= 'SELECT (date_or_date_time_select)' )

The actual end date of the Organizational Unit at the Location.

actual_start_date (Type= 'SELECT (date_or_date_time_select)' )

The actual start date of the Organizational Unit at the Location.

id (Type='STRING')

This is the identifier of the relationship between the Organizational Unit and Location.

source_organization (Type='STRING')

The organization or information system that created the associated identifier. Alternatively this could be set to /NULL when Person or Information System is the source; see Identifier template characterizations.

location (Type= 'ENTITY (Location)' )

This is the relationship to the Location.

organizational_unit (Type= 'SELECT (location_assignment_select)' )

This is the relationship to the Organizational Unit.

planned_end_date (Type= 'SELECT (date_or_date_time_select)' )

The planned end date of the Organizational Unit at the Location.

planned_start_date (Type= 'SELECT (date_or_date_time_select)' )

The planned start date of the Organizational Unit at the Location.

Reference parameters

The following reference parameters are defined for this template:

location_asst(Type='ENTITY (Location_assignment)')

Allow the Location_assignment entity instantiated in this path to be referenced when this template is used.

Note: The Location_assignment entity can be referenced in a template path by:

%^target = $organizational_unit_non_standard_location.location_asst%

where target is the parameter to which the Location_assignment is bound.

actual_end_date(Type='ENTITY (Date_or_date_time_assignment)')

Allow the Date_or_date_time_assignment entity instantiated in this path to be referenced when this template is used.

Note: The Date_or_date_time_assignment entity can be referenced in a template path by:

%^target = $organizational_unit_non_standard_location.actual_end_date%

where target is the parameter to which the Date_or_date_time_assignment is bound.

actual_start_date(Type='ENTITY (Date_or_date_time_assignment)')

Allow the Date_or_date_time_assignment entity instantiated in this path to be referenced when this template is used.

Note: The Date_or_date_time_assignment entity can be referenced in a template path by:

%^target = $organizational_unit_non_standard_location.actual_start_date%

where target is the parameter to which the Date_or_date_time_assignment is bound.

planned_end_date(Type='ENTITY (Date_or_date_time_assignment)')

Allow the Date_or_date_time_assignment entity instantiated in this path to be referenced when this template is used.

Note: The Date_or_date_time_assignment entity can be referenced in a template path by:

%^target = $organizational_unit_non_standard_location.planned_end_date%

where target is the parameter to which the Date_or_date_time_assignment is bound.

planned_start_date(Type='ENTITY (Date_or_date_time_assignment)')

Allow the Date_or_date_time_assignment entity instantiated in this path to be referenced when this template is used.

Note: The Date_or_date_time_assignment entity can be referenced in a template path by:

%^target = $organizational_unit_non_standard_location.planned_start_date%

where target is the parameter to which the Date_or_date_time_assignment is bound.

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.

Location_assignment
Location_assignment.location_for_assignment -> @location
Location_assignment.entity_for_location -> @organizational_unit

-- assign ref parameters
%^location_asst = Location_assignment%

-- ID
/identifier(
    ID=@id,
    source_organization=@source_organization,
    type='non_standard_location_id_code',
    items=^location_asst)/

-- actual end date
Date_or_date_time_assignment
%^actual_end_date = Date_or_date_time_assignment%
^actual_end_date.assigned_date -> @actual_end_date
^actual_end_date.role = 'non_standard_location_actual_end_date'
^actual_end_date.items -> ^location_asst

-- actual start date
Date_or_date_time_assignment
%^actual_start_date = Date_or_date_time_assignment%
^actual_start_date.assigned_date -> @actual_start_date
^actual_start_date.role = 'non_standard_location_actual_start_date'
^actual_start_date.items -> ^location_asst

-- planned end date
Date_or_date_time_assignment
%^planned_end_date = Date_or_date_time_assignment%
^planned_end_date.assigned_date -> @planned_end_date
^planned_end_date.role = 'non_standard_location_planned_end_date'
^planned_end_date.items -> ^location_asst

-- planned start date
Date_or_date_time_assignment
%^planned_start_date = Date_or_date_time_assignment%
^planned_start_date.assigned_date -> @planned_start_date
^planned_start_date.role = 'non_standard_location_planned_start_date'
^planned_start_date.items -> ^location_asst

The following entities are instantiated with attributes as specified:

Entity in path	Value	Inherited from
Date_or_date_time_assignment.role	'non_standard_location_actual_end_date'	—
Date_or_date_time_assignment.role	'non_standard_location_actual_start_date'	—
Date_or_date_time_assignment.role	'non_standard_location_planned_end_date'	—
Date_or_date_time_assignment.role	'non_standard_location_planned_start_date'	—

Instance diagrams

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

/organizational_unit_non_standard_location(actual_end_date='#77', actual_start_date='#82', id='org_unit_non_std_loc_1', source_organization='6421', location='#43', organizational_unit='#27', planned_end_date='#87', planned_start_date='#92')/

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

Figure 4 — Entities instantiated by organizational_unit_non_standard_location 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:

Figure 5 — Instantiation of organizational_unit_non_standard_location template

Characterizations

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