Template:— recommended_facilities (recomm_facilities) Context:— UK_Defence |
Date: 2010/02/17 17:09:24 Revision: 1.6
|
This section specifies the template recommended_facilities.
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 recommended facilities in terms of PLCS
model elements (templates, entities, and reference data).
This information object identifies the recommended facilities required, over a defined period of time, to support the Platform,
system and equipment for which the associated Support Solution Definition was developed.
This information object identifies the recommended facilities required, over a defined period of time, to support
the Platform, system and equipment for which the associated Support Solution Definition was developed.
Figure 1 — Graphical Representation for Business Object Recommended Facilities
Attribute name
|
Attribute description
|
Attribute type
|
Optionality
|
Assumptions |
This is a reference to the assumptions on which the facility recommendations are based. |
Relationship to Assumption. |
Optional (0:?) |
Constraints |
This is a reference to the constraints on which the facility recommendations are based. |
Relationship to Constraint. |
Optional (0:?) |
Facilities |
This is a reference to the facilities that are recommended for the support of the Platform, system and equipment. |
Relationship to Facility. |
Optional (0:?) |
Facility Types |
This is a reference to the facility types that are required for the support of the Platform, system or equipment. |
Relationship to Recommended Facility Type. |
Optional (0:?) |
ID |
This is the identifier of the recommended facilities. |
Identifier |
Mandatory |
Identifier.id |
This is the value of the id attribute of the Identifier applied to the recommended facilities. |
intrinsic |
Mandatory |
Identifier.type |
This attribute is the type associated with the id of the Identifier given to the recommended facilities. |
Recommended_facilities_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 recommended
facilities. This value is assumed to be a type of Organization_identification_code.
|
Organization_identification_code |
Mandatory |
Name |
This is the name of the facility recommendations. |
intrinsic |
Mandatory |
Related schedules |
This is the reference to any related schedules that have already been developed, which will influence the facility recommendations.
EXAMPLE: If a dry docking schedule has been developed for a new ship, then this may infuence which facilities
are recommended.
|
Relationship to Schedule. |
Optional (0:?) |
Related support solution |
This is the reference to the support solution for which the recommended facilities have been derived.
|
Relationship to Support Solution Definition. |
Mandatory |
Time Period |
This is the time period for which the facility recommendations are made. |
intrinsic |
Mandatory |
Version |
This is the version of the facility recommendations. |
intrinsic |
Mandatory |
Table 1 — Recommended Facilities attribute details
The EXPRESS-G diagram in
Figure
2
shows the templates and EXPRESS entities that are required
to represent the template
"recommended_facilities".
The text highlighted in blue shows the template parameters.
Figure 2 — An EXPRESS-G representation of the Information model for recommended_facilities
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 recommended_facilities template
The following input parameters are defined for this template:
The recommended facilities.
The required recommended facility type.
The identifier applied to the recommended facilities.
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 facility recommendations.
The related support solution.
The time period of the recommendation.
The time for which the resource is allocated to the activity.
The following classes and their sub-classes can be used:
The version of the recommendation.
The following reference parameters are defined for this template:
%^target = $recommended_facilities.facility_req_res_spec%
%^target = $recommended_facilities.facility_req_res_item%
Allow the
Resource_item
entity instantiated in this path to be referenced when this template is used.
Note: The
Resource_item
entity can be referenced in a template path by:
%^target = $recommended_facilities.facility_res_item%
where
target
is the parameter to which the
Resource_item
is bound.
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.
-- required resource Required_resource_by_specification%^facility_req_res_spec =
Required_resource_by_specification%
-- facilities /
representing_resource_item_realization(
res_item_id='',
res_item_id_class='',
res_item_id_ecl_id='urn:plcs:rdl:std',
res_item_id_org_id='',
res_item_id_org_id_class='',
res_item_id_org_id_ecl_id='urn:plcs:rdl:std',
res_item_items=@facilities)/
%^facility_res_item = $representing_resource_item_realization.res_item%
-- required resource resource item Required_resource_by_resource_itemRequired_resource_by_resource_item.resource_item ->
^facility_res_item
%^facility_req_res_item =
Required_resource_by_resource_item%
-- relate required resources specification and resource item /
representing_required_resource_relationship(
req_res_rel_class_name='Required_resource_relationship',
req_res_rel_ecl_id='urn:plcs:rdl:std',
relating_req_res=^facility_req_res_spec,
related_req_res=^facility_req_res_item)/
-- [Optional assumptions 0:?] /
assigning_document(
doc_ass_role='Related_assumption',
doc_ar_ecl_id='urn:plcs:rdl:std',
assigned_document=@assumptions,
is_assigned_to=^facility_req_res_spec)/
-- [Optional constraints 0:?] Requirement_assignmentRequirement_assignment.assigned_requirement ->
@constraintsRequirement_assignment.assigned_to ->
^facility_req_res_spec
-- related_support_solution /
assigning_document(
doc_ass_role='Related_support_solution_definition',
doc_ar_ecl_id='urn:plcs:rdl:std',
assigned_document=@related_support_solution,
is_assigned_to=^facility_req_res_spec)/
-- [Optional recommended_facility_types [0:?]] /
representing_required_resource_relationship(
req_res_rel_class_name='Required_resource_relationship',
req_res_rel_ecl_id='urn:plcs:rdl:std',
relating_req_res=^facility_req_res_spec,
related_req_res=@facility_types)/
-- [Optional related_schedules 0:?] Scheme_subject_assignmentScheme_subject_assignment.items ->
^facility_req_res_spec
Scheme_subject_assignment.assigned_activity_method ->
@related_schedules-- provide the role of the required_resource /
assigning_reference_data(
items=^facility_req_res_spec,
class_name='recommended',
ecl_id='urn:plcs:rdl:uk_defence')/
-- id /
identifier(
ID=@id,
source_organization=@source_organization,
type='Recommended_facilities_id_code',
items=^facility_req_res_spec )/
-- name /
identifier(
ID=@name,
source_organization=@source_organization,
type='Recommended_facilities_name',
items=^facility_req_res_spec )/
-- version /
assigning_descriptor(
descr=@version,
class_name='Recommended_facilities_version',
ecl_id='urn:plcs:rdl:uk_defence',
is_assigned_to=^facility_req_res_spec)/
-- time period /
assigning_resource_property(
property_class_name='Estimated_time',
property_ecl_id='urn:plcs:rdl:uk_defence',
described_element=^facility_req_res_spec)/
%^property_time_period = $assigning_resource_property.property%
/
resource_property_numeric(
value=@time_period,
unit=@time_period_unit,
unit_ecl_id='urn:plcs:rdl:uk_defence',
si_unit='false',
context='Numerical_representation_context',
context_ecl_id='urn:plcs:rdl:uk_defence',
property=^property_time_period)/
The instance diagram in Figure
4
shows an example of the EXPRESS entities and templates that are instantiated by the template:
/recommended_facilities(assumptions='#279', constraints='#359', facilities='#154', facility_types='#231', id='fac_1', source_organization='6421', name='Dry dock', related_schedules='#111', related_support_solution='#579', time_period='24', time_period_units='Hour', version='1')/
(an illustration of the consolidated recommended_facilities template is shown in
Figure
5 below.)
Figure 4 — Entities instantiated by recommended_facilities 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:
/recommended_facilities(assumptions='#279', constraints='#359', facilities='#154', facility_types='#231', id='fac_1', source_organization='6421', name='Dry dock', related_schedules='#111', related_support_solution='#579', time_period='24', time_period_units='Hour', version='1')/
Figure 5 — Instantiation of recommended_facilities template
Characterizations
No common characterizations of the template
recommended_facilities
have been identified. However, the ISO 10303-239 EXPRESS model
may enable other assignments to the entities instantiated by the template.