Template:— zone (zne)
Context:— UK_Defence |
Date: 2009/04/17 12:50:55
Revision: 1.2
|
This section specifies the template zone.
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 breakdown element
in terms of PLCS model elements (templates, entities, and reference data).
This information object represents a zone or space in a product.
This information object represents a zone or space in a product.
Figure 1 — Graphical Representation for Business Object Zone
|
Attribute name
|
Attribute description
|
Attribute type
|
Optionality
|
| id |
This attribute provides the identification of the breakdown item. |
Intrinsic |
Mandatory |
| Identifier.id |
This is the value of the id attribute of the Identifier applied to the Physical Breakdown Item. |
intrinsic |
Mandatory |
| Identifier.type |
This attribute is the type associated with the id of the Identifier given to the product Physical Breakdown Item. This must
be one of the classes provided.
|
Physical_element_identification_code |
Mandatory |
| Identifier.source_organization |
This attribute is the value representing the source organization that provides the id of the Identifier given to the Physical
Breakdown Item. This value is assumed to be a type of Organization_identification_code.
|
Organization_identification_code |
Mandatory |
| description |
This attribute provides the description of the item. |
Intrinsic |
Mandatory |
| name |
This attribute provides the name of the breakdown item. |
Intrinsic |
Mandatory |
| type |
This optional attribute indicates the type of physical items covered by the breakdown. |
Intrinsic |
Mandatory |
| version |
This attribute provides the version of the breakdown item. |
Intrinsic |
Mandatory |
| contained_by_breakdown |
This is the reference to the breakdown within which, this item is contained. |
Zone breakdown |
Mandatory |
Table 1 — Zone attribute details
The EXPRESS-G diagram in
Figure
2
shows the templates and EXPRESS entities that are required
to represent the template
"zone".
The text highlighted in blue shows the template parameters.
Figure 2 — An EXPRESS-G representation of the Information model for zone
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 zone template
The following input parameters are defined for this template:
The identifier of the zone.
The description of the zone.
The name of the function.
The organization or information system that created the associated identifier. Alternatively this could be set to /NULL and
when Person or Information System is the source; see Identifier template characterizations.
type (Default=Zone_type,Type='CLASS')
The type of the zone. Note:- sub-classifications of Zone types should be identified by and between organizations (if necessary)
depending upon the business requirements. Some example types have been provided.
The identifier of the zone version.
The breakdown version that contains this element.
The following reference parameters are defined for this template:
Allow the
Zone_element
entity instantiated in this path to be referenced when this template is used.
Note: The
Zone_element
entity can be referenced in a template path by:
%^target = $zone.zone_elem%
where
target
is the parameter to which the
Zone_element
is bound.
Allow the
Zone_element_version
entity instantiated in this path to be referenced when this template is used.
%^target = $zone.zone_elem_vn%
%^target = $zone.zone_elem_def%
%^target = $zone.vew_def_cntxt%
Allow the
Zone_breakdown_context
entity instantiated in this path to be referenced when this template is used.
%^target = $zone.zone_cntxt%
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_element(
id=@id,
id_class_name='Zonal_element_identification_code',
id_ecl_id='urn:plcs:rdl:uk_defence',
id_owner=@source_organization,
id_owner_class_name='Organization_identification_code',
id_owner_ecl_id='urn:plcs:rdl:uk_defence',
vn_id=@version,
vn_id_class_name='Version_identification_code',
vn_id_ecl_id='urn:plcs:rdl:uk_defence',
vn_id_owner=@source_organization,
vn_id_owner_class_name='Organization_name',
vn_id_owner_ecl_id='urn:plcs:rdl:uk_defence',
life_cycle_stage='Support_stage',
life_cycle_stage_ecl_id='urn:plcs:rdl:uk_defence',
domain='Product_life_cycle_support',
domain_ecl_id='urn:plcs:rdl:uk_defence')/
-- assign ref parameters %^zone_elem = $representing_zone_element.zone_elem%
%^zone_elem_vn = $representing_zone_element.zone_elem_vn%
%^zone_elem_def = $representing_zone_element.zone_elem_def%
%^def_cntxt = $representing_zone_element.def_cntxt%
%^zone_cntxt = $representing_zone_element.zone_cntxt%
^zone_cntxt.breakdown ->
@contained_by_breakdown-- name /
assigning_identification(
items=^zone_elem,
id=@name,
id_class_name='Zone_breakdown_element_name',
id_ecl_id='urn:plcs:rdl:uk_defence',
org_id=@source_organization,
org_id_class_name='Organization_identification_code',
org_id_ecl_id='urn:plcs:rdl:uk_defence')/
-- type /
assigning_reference_data(
items=^zone_elem,
class_name=@type,
ecl_id='urn:plcs:rdl:uk_defence')/
-- description /
assigning_descriptor(
descr=@description,
class_name='zone_description',
ecl_id='urn:plcs:rdl:uk_defence',
is_assigned_to=^zone_elem)/
The instance diagram in Figure
4
shows an example of the EXPRESS entities and templates that are instantiated by the template:
/zone(id='88372', description='propulsion fuel storage tank', name='fuel_tank', type='Tank', source_organization='96412', version='issue 3a')/
(an illustration of the consolidated zone template is shown in
Figure
5 below.)
Figure 4 — Entities instantiated by zone 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:
/zone(id='88372', description='propulsion fuel storage tank', name='fuel_tank', type='Tank', source_organization='96412', version='issue 3a')/
Figure 5 — Instantiation of zone template
Characterizations
No common characterizations of the template
zone
have been identified. However, the ISO 10303-239 EXPRESS model
may enable other assignments to the entities instantiated by the template.
![[warning:]](../../../../../../images/dex/warning.gif){kind=small}
Error RDL4: The URI urn:plcs:rdl:uk_defence is not listed in dexlib/data/refdata/rdl_index.xml
