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 service 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.

The attributes of the Service object are tabled below.

Attribute name	Attribute description	Attribute type	Optionality
ID	This is the identification of the service.	intrinsic	Mandatory
Identifier.id	This is the value of the id attribute of the Identifier applied to the service.	intrinsic	Mandatory
Identifier.type	This attribute is the type associated with the id of the Identifier given to the service.	service_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 service. This value is assumed to be a type of Organization_identification_code.	Organization_identification_code	Mandatory
Performed tasks and activities	This is the reference to the set of tasks and / or activities that define the service to be provided.	Relationship to Task or Activity	Mandatory (1:M)
Provider	This is the reference to the organization that provides the service.	Relationship to Organization	Mandatory

The following input parameters are defined for this template:

The following reference parameters are defined for this template:

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

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

%^target = $service.service%

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

Activity_method
Activity_method.name = '/IGNORE'
Activity_method.description = '/IGNORE'
Activity_method.consequence = '/IGNORE'
Activity_method.purpose = '/IGNORE'
Activity_actual
Activity_actual.chosen_method -> Activity_method
%^service = Activity_actual%

-- ID
/identifier(
    ID=@ID,
    source_organization=@source_organization,
    type='service_id_code',
    items=^service)/

-- relationship to performed_tasks_and_activities
/assigning_activity(
    role_class_name='performed_tasks_and_activities',
    role_ecl_id='urn:plcs:rdl:uk_defence',
    assigned_activity=^service,
    items=@performed_tasks_and_activities)/

-- relationship to provider
Organization_or_person_in_organization_assignment
Organization_or_person_in_organization_assignment.role = '/IGNORE'
Organization_or_person_in_organization_assignment.items -> ^service
Organization_or_person_in_organization_assignment.assigned_entity -> @provider
%^provider = Organization_or_person_in_organization_assignment%
/assigning_reference_data(
    items=^provider,
    class_name='Provider',
    ecl_id='urn:plcs:rdl:uk_defence')/

The following entities are instantiated with attributes as specified:

Entity in path	Value	Inherited from
Activity_method.name	'/IGNORE'	—
Activity_method.description	'/IGNORE'	—
Activity_method.consequence	'/IGNORE'	—
Activity_method.purpose	'/IGNORE'	—
Organization_or_person_in_organization_assignment.role	'/IGNORE'	—