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

A fleet is a named collection of products that are managed as a whole to meet an operational requirement.

This information object represents a named collection of products that are managed as a whole to meet an operational requirement.

Figure 1 — A MOOD Business Architect representation of the Business Object: Fleet

The attributes of the Fleet object are tabled below.

Attribute name	Attribute description	Attribute type	Optionality
Capability	This is a reference to the capability of the fleet components.	Relationship to Fleet Capability	Mandatory (1:?)
End date	This is the date for which the fleet ceased to exist.	intrinsic	Optional
ID	This is the identifier of the fleet.	intrinsic	Mandatory
Identifier.id	This is the value of the id attribute of the Identifier applied to the fleet.	intrinsic	Mandatory
Identifier.type	This attribute is the type associated with the id of the Identifier given to the fleet.	fleet_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 fleet. This value is assumed to be a type of Organization_identification_code.	Organization_identification_code	Mandatory
Name	This is the name of the fleet.	intrinsic	Mandatory
Operational requirement	This is the reference to the operational requirement for which the fleet is assembled.	Relationship to Requirement	Mandatory
Start date	This is the date for which the fleet was assembled.	intrinsic	Mandatory

Table 1 — Fleet attribute details

The following input parameters are defined for this template:

The following reference parameters are defined for this template:

Allow the Product_group entity instantiated in this path to be referenced when this template is used.

Note: The Product_group entity can be referenced in a template path by:

%^target = $fleet.prod_grp%

where target is the parameter to which the Product_group 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.

Product_group
%^prod_grp = Product_group%

-- ID
/identifier(
    ID=@ID,
    source_organization=@source_organization,
    type='fleet_id_code',
    items=^prod_grp)/

-- name
/identifier(
    ID=@name,
    source_organization=@source_organization,
    type='fleet_name',
    items=^prod_grp)/

-- end and start dates
/assigning_dated_effectivity(
    start_year=@start_date_year,
    start_month=@start_date_month,
    start_day=@start_date_day,
    start_hour='',
    start_minute='',
    start_second='',
    start_sense=''exact',
    start_hour_offset='',
    start_minute_offset='',
    end_year=@end_date_year,
    end_month=@end_date_month,
    end_day=@end_date_day,
    end_hour='',
    end_minute='',
    end_second='',
    end_sense=''exact',
    end_hour_offset='',
    end_minute_offset='',
    role_class_name='',
    role_ecl_id='urn:plcs:rdl:std',
    items=^prod_grp)/

-- operational requirement
/assigning_requirement(
    class_name='Fleet_operational_requirement',
    ecl_id='urn:plcs:rdl:uk_defence',
    req=@operational_requirement,
    assigned_to=^prod_grp )/

The instance diagram in Figure 4 shows an example of the EXPRESS entities and templates that are instantiated by the template:

/fleet(end_year='', end_month='', end_day='', ID='fleet_123', source_organization='6421', name='the_fleet', start_year='2009', start_month='09', start_day='01', operational_requirement='#69')/

(an illustration of the consolidated fleet template is shown in Figure 5 below.)