Template:— physical_breakdown_item_realization (phy_bkdn_rlzn) Context:— UK_Defence |
Date: 2009/04/17 10:29:33 Revision: 1.2
|
This section specifies the template physical_breakdown_item_realization.
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 reference the design realized by a physical item.
This information object represents the method by which a Physical Breakdown Item realizes Product_design(s), specification(s)
and assembly_items.
This information object represents the relationship between a physical breakdown item and the product designs and
/ or product specifications that can be used to fulfil its requirement.
Figure 1 — Graphical Representation for Business Object physical_breakdown_item_realization.
Attribute name
|
Attribute description
|
Attribute type
|
Optionality
|
ID |
This attribute provides the identification of the breakdown item. |
Identifier |
Mandatory |
Identifier.id |
This is the value of the id attribute of the Identifier applied to the Physical Breakdown Item Realization. |
intrinsic |
Mandatory |
Identifier.type |
This attribute is the type associated with the id of the Identifier given to the Physical Breakdown Item Realization. This
must be one of the classes provided.
|
Physical_breakdown_element_realization_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 Realization. This value is assumed to be a type of Organization_identification_code.
|
Organization_identification_code |
Mandatory |
realized_by |
This mandatory attribute provides the reference to the product design or product specification that realizes the related physical
breakdown item.
|
Product Design, Product Specification, Assembly Item
SELECT
|
Mandatory |
realizes |
This Mandatory attribute identifies the physical breakdown item that is to be realized. |
Physical Breakdown Item |
Mandatory |
Table 1 — Physical_breakdown_item_realization attribute details
The EXPRESS-G diagram in
Figure
2
shows the templates and EXPRESS entities that are required
to represent the template
"physical_breakdown_item_realization".
The text highlighted in blue shows the template parameters.
Figure 2 — An EXPRESS-G representation of the Information model for physical_breakdown_item_realization
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_realization template
The following input parameters are defined for this template:
This is the identifier of the physical breakdown item functionality relationship
This attribute is provides the type associated with the id of the Identifier given to the relationship. This must
be one of the classes provided.
The following classes and their sub-classes can be used:
classifications: [Physical_realization_identification_code]
Error RDL4: The URI urn:plcs:rdl:uk_defence is not listed in dexlib/data/refdata/rdl_index.xml
The identifier of the organization that owns the id. It is assumed that this will be of type Organization_identification_code
and not an Organization name.
This is the physical breadkdown element definition that is realizing the system.
The part view definition being realized.
The following reference parameters are defined for this template:
Allow the
View_definition_usage
entity instantiated in this path to be referenced when this template is used.
%^target = $physical_breakdown_item_realization.realization_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_breakdown_element_realization(
breakdown=@realizes,
product=@realized_by,
class_name='Physical_realization',
class_ecl_id='urn:plcs:rdl:uk_defence')/
%^realization_relationship = $representing_breakdown_element_realization.bkdn_elem_real%
-- assign name to breakdown_element /
assigning_identification(
id=@realization_id,
id_class_name=@realization_id_type,
id_ecl_id='urn:plcs:rdl:uk_defence',
org_id=@id_source_organization,
org_id_class_name='Organization_identification_code',
org_id_ecl_id='urn:plcs:rdl:uk_defence',
items=^realization_relationship)/
The instance diagram in Figure
4
shows an example of the EXPRESS entities and templates that are instantiated by the template:
/physical_breakdown_item_realization(realization_id='PR451', realization_id_type='Physical_realization_identification_code', id_source_organization='6421', realizes='@89', realized_by='@1')/
(an illustration of the consolidated physical_breakdown_item_realization template is shown in
Figure
5 below.)
Figure 4 — Entities instantiated by physical_breakdown_item_realization 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_realization(realization_id='PR451', realization_id_type='Physical_realization_identification_code', id_source_organization='6421', realizes='@89', realized_by='@1')/
Figure 5 — Instantiation of physical_breakdown_item_realization template
Characterizations
No common characterizations of the template
physical_breakdown_item_realization
have been identified. However, the ISO 10303-239 EXPRESS model
may enable other assignments to the entities instantiated by the template.