Template:— physical_breakdown_item (phys_brkd_itm)
Context:— UK_Defence
Date: 2009/04/17 10:29:33
Revision: 1.2

This section specifies the template physical_breakdown_item.

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 UK_Defence concept of a physical breakdown element in terms of PLCS model elements (templates, entities, and reference data).

Business perspective

This information object represents the identification of, and the reference to, a physical components in a breakdown.

Business object definition

This information object represents the identification of, and the reference to, a physical components in a breakdown.



Figure 1 —  Graphical Representation for Business Object Physical Breakdown Item

Figure 1 —  Graphical Representation for Business Object Physical Breakdown Item

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. Physical breakdown Mandatory

Table 1 — Physical Breakdown Item attribute details

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


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

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

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

Figure 3 —  The graphical representation of the physical_breakdown_item template

Input parameters
The following input parameters are defined for this template:
id (Type='STRING')
The identifier of the physical breakdown item.
description (Type='STRING', Optional)
The description of the physical breakdown item.
name (Type='STRING')
The name of the physical breakdown item.
source_organization (Type='STRING')
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=Physical_breakdown_item_type,Type='CLASS', Optional)
The type of the physical breakdown item. Sub-classifications of Physical_breakdown_item_type should be identified by and between organizations as necessary to match the business requirements.
The following classes and their sub-classes can be used:
classifications: [Physical_breakdown_item_type]
[warning:]Error RDL4: The URI urn:plcs:rdl:uk_defence is not listed in dexlib/data/refdata/rdl_index.xml
version (Type='STRING')
The identifier of the physical breakdown item version.
contained_by_breakdown (Type= 'ENTITY (Physical_breakdown_version)' )
The breakdown version that contains this element.
Reference parameters
The following reference parameters are defined for this template:
phys_item(Type='ENTITY (Physical_element)')
Allow the Physical_element entity instantiated in this path to be referenced when this template is used.
Note: The Physical_element entity can be referenced in a template path by:
%^target = $physical_breakdown_item.phys_item%
where target is the parameter to which the Physical_element is bound.
phys_item_vn(Type='ENTITY (Physical_element_version)')
Allow the Physical_element_version entity instantiated in this path to be referenced when this template is used.
Note: The Physical_element_version entity can be referenced in a template path by:
%^target = $physical_breakdown_item.phys_item_vn%
where target is the parameter to which the Physical_element_version is bound.
phys_item_def(Type='ENTITY (Physical_element_definition)')
Allow the Physical_element_definition entity instantiated in this path to be referenced when this template is used.
Note: The Physical_element_definition entity can be referenced in a template path by:
%^target = $physical_breakdown_item.phys_item_def%
where target is the parameter to which the Physical_element_definition is bound.
phys_item_def_cntxt(Type='ENTITY (View_definition_context)')
Allow the View_definition_context entity instantiated in this path to be referenced when this template is used.
Note: The View_definition_context entity can be referenced in a template path by:
%^target = $physical_breakdown_item.phys_item_def_cntxt%
where target is the parameter to which the View_definition_context is bound.
phys_item_cntxt(Type='ENTITY (Physical_breakdown_context)')
Allow the Physical_breakdown_context entity instantiated in this path to be referenced when this template is used.
Note: The Physical_breakdown_context entity can be referenced in a template path by:
%^target = $physical_breakdown_item.phys_item_cntxt%
where target is the parameter to which the Physical_breakdown_context 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.
/representing_physical_element(
    id=@id,
    id_class_name='Physical_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_owner=@source_organization,
    vn_id_owner_class_name='Organization_identification_code',
    vn_id_ecl_id='urn:plcs:rdl:uk_defence',
    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
%^phys_item = $representing_physical_element.phys_elem%
%^phys_item_vn = $representing_physical_element.phys_elem_vn%
%^phys_item_def = $representing_physical_element.phys_elem_def%
%^phys_item_def_cntxt = $representing_physical_element.def_cntxt%
%^phys_item_cntxt = $representing_physical_element.phys_cntxt%
^phys_item_cntxt.breakdown -> @contained_by_breakdown

-- name
/identifier(
    ID=@name,
    source_organization=@source_organization,
    type='Physical_breakdown_element_name',
    items=^phys_item)/

-- type
/assigning_reference_data(
    items=^phys_item,
    class_name=@type,
    ecl_id='urn:plcs:rdl:uk_defence')/

-- description
/assigning_descriptor(
    descr=@description,
    class_name='physical_breakdown_item_description',
    ecl_id='urn:plcs:rdl:uk_defence',
    is_assigned_to=^phys_item)/
Instance diagrams
The instance diagram in Figure  4 shows an example of the EXPRESS entities and templates that are instantiated by the template:
/physical_breakdown_item(id='P301 451', description='support bracket', name='bracket', type='Physical_breakdown_item_type', source_organization='6421', version='issue 4b', is_contained_by='@74')/
(an illustration of the consolidated physical_breakdown_item template is shown in Figure 5 below.)


Figure 4 —  Entities instantiated by physical_breakdown_item template

Figure 4 —  Entities instantiated by physical_breakdown_item 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:
/physical_breakdown_item(id='P301 451', description='support bracket', name='bracket', type='Physical_breakdown_item_type', source_organization='6421', version='issue 4b', is_contained_by='@74')/


Figure 5 —  Instantiation of physical_breakdown_item template

Figure 5 —  Instantiation of physical_breakdown_item template

Characterizations
No common characterizations of the template physical_breakdown_item 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