Template:— zonal_relationship (znl_reln) Context:— UK_Defence |
Date: 2009/04/17 12:50:02 Revision: 1.2
|
This section specifies the template zonal_relationship.
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 UK_Defence concept of a zonal relationship
in terms of PLCS model elements (templates, entities, and reference data).
This information object identifies the relationship between zones in a breakdown. It is essentially used to establish
the parent child relationships between zones.
This information object identifies the relationship between zones in a breakdown. It is essentially used to establish
the parent child relationships between zones.
Figure 1 — Graphical Representation for Business Object Zonal Relationship
Attribute name
|
Attribute description
|
Attribute type
|
Optionality
|
child |
This attribute identifies the child node in a hierarchical relationship. |
Zone |
Mandatory |
ID |
This attribute provides the identifier of the zone relationship. |
Identifier |
Mandatory |
Identifier.id |
This is the value of the id attribute of the Identifier applied to the zonal relationship. |
intrinsic |
Mandatory |
Identifier.type |
This attribute is the type associated with the id of the Identifier given to the zonal relationship. This must be one of the
classes provided.
|
Zone_element_usage_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 zonal
relationship. This value is assumed to be a type of Organization_identification_code.
|
Organization_identification_code |
Mandatory |
name |
This attribute provides the name of the zonal relationship. |
Intrinsic |
Mandatory |
parent |
This attribute specifies the parent or upper node in a hierarchical relationship. |
Zone |
Mandatory |
version |
This attribute provides the version of the zone relationship. |
Intrinsic |
Mandatory |
Table 1 — Zonal Relationship attribute details
The EXPRESS-G diagram in
Figure
2
shows the templates and EXPRESS entities that are required
to represent the template
"zonal_relationship".
The text highlighted in blue shows the template parameters.
Figure 2 — An EXPRESS-G representation of the Information model for zonal_relationship
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 zonal_relationship template
The following input parameters are defined for this template:
The identifier of the zonal relationship.
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.
The name of the zonal relationship.
The version identifier of the zonal relationship.
The parent zone element definition.
The child zone element definition.
The following reference parameters are defined for this template:
Allow the
Zone_element_usage
entity instantiated in this path to be referenced when this template is used.
%^target = $zonal_relationship.zne_relationship%
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.
/
representing_zone_structure(
rel_type_name='Zone_element_usage',
rel_ecl_id='urn:plcs:rdl:uk_defence',
parent=@parent,
child=@child)/
-- assign ref parameters %^zne_relationship = $representing_zone_structure.usage%
-- id /
identifier(
ID=@id,
source_organization=@source_organization,
type='Zone_element_usage_id_code',
items=^zne_relationship)/
-- name /
identifier(
ID=@name,
source_organization=@source_organization,
type='Zone_element_usage_name',
items=^zne_relationship)/
-- version /
identifier(
ID=@version,
source_organization=@source_organization,
type='Zone_element_usage_version_id_code',
items=^zne_relationship)/
The instance diagram in Figure
4
shows an example of the EXPRESS entities and templates that are instantiated by the template:
/zonal_relationship(id='ZP12', source_organization='6421', name='Hold access', version='vn 5', parent='@124', child='@70')/
(an illustration of the consolidated zonal_relationship template is shown in
Figure
5 below.)
Figure 4 — Entities instantiated by zonal_relationship 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:
/zonal_relationship(id='ZP12', source_organization='6421', name='Hold access', version='vn 5', parent='@124', child='@70')/
Figure 5 — Instantiation of zonal_relationship template
Characterizations
No common characterizations of the template
zonal_relationship
have been identified. However, the ISO 10303-239 EXPRESS model
may enable other assignments to the entities instantiated by the template.