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

This information object represents the prescribed sequence for the conduct of activities.

The definition of the schecule object is: This information object represents the instantiation of the planned schedule, detailing specific dates for the performance of tasks on specific products using specific resources.

Figure 1 — Graphical Representation for Business Object schedule

Attribute name	Attribute description	Attribute type	Optionality
Category	This attribute provides the type of schedule.	Intrinsic	Mandatory
Comprised of	Relation to Task, Schedule or Task_list	Intrinsic	Mandatory
Derived from	This is the item from which the schedule was derived.	Select, task, task_list, Plan	Mandatory
Description	This attribute provides the description of the schedule.	Intrinsic	Mandatory
End Date	This attribute provides the date for the schedule	Intrinsic	Mandatory
End Time	This attribute provides the time for the schedule	Intrinsic	Mandatory
ID	This attribute provides the identification of the schedule.	Identifier	Mandatory
Identifier.id	This is the value of the id attribute of the Identifier applied to the schedule.	intrinsic	Mandatory
Identifier.type	This attribute is the type associated with the id of the Identifier given to the Schedule. This must be one of the classes provided, it is intended that business users will add types of schedule as appropriate.	Scheme_type	Mandatory
Identifier.source_organization	This attribute is the value representing the source organization that provides the id of the Identifier given to the schedule This value is assumed to be a type of Organization_identification_code.	Organization_identification_code	Mandatory
Location	This is the reference to the location at which the schedule is required to be executed.	Location	Optional
Name	This attribute provides the name of the Schedule.	Intrinsic	Mandatory
Start Date	This attribute provides the start date for the schedule.	Intrinsic	Mandatory
Start Time	This attribute provides the start time for the schedule.	Intrinsic	Mandatory

Table 1 — Schedule attribute details

The following input parameters are defined for this template:

The following classes and their sub-classes can be used:

classifications: [Scheme_type]

Error RDL4: The URI urn:plcs:rdl:uk_defence is not listed in dexlib/data/refdata/rdl_index.xml
[Through_Life_Information_Management_Plan]

Error RDL4: The URI urn:plcs:rdl:uk_defence is not listed in dexlib/data/refdata/rdl_index.xml
[Through_Life_Management_Plan]

Error RDL4: The URI urn:plcs:rdl:uk_defence is not listed in dexlib/data/refdata/rdl_index.xml

The following reference parameters are defined for this template:

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_scheme(
    scheme_id=@schedule_id,
    scheme_id_class_name=@category,
    scheme_id_ecl_id='urn:plcs:rdl:uk_defence',
    scheme_org_id=@releasing_authority,
    scheme_org_id_class_name='Organization_identification_code',
    scheme_org_id_ecl_id='urn:plcs:rdl:uk_defence',
    scheme_vn_id=@schedule_version,
    scheme_vn_id_class_name='Version_identification_code',
    scheme_vn_id_ecl_id='urn:plcs:rdl:std',
    scheme_vn_org_id=@releasing_authority,
    scheme_vn_org_id_class_name='Organization_identification_code',
    scheme_vn_org_id_ecl_id='urn:plcs:rdl:uk_defence')/

-- assign ref parameters
%^scheme = $representing_scheme.scheme%
%^scheme_vn = $representing_scheme.scheme_vn%

-- subject
Scheme_subject_assignment
Scheme_subject_assignment.assigned_activity_method -> ^scheme
Scheme_subject_assignment.items -> @subject

-- description
/assigning_descriptor(
    descr=@description,
    class_name='Description',
    ecl_id='urn:plcs:rdl:uk_defence',
    is_assigned_to=^scheme)/

-- schema name
/identifier(
    ID=@name,
    source_organization=@releasing_authority,
    type='name',
    items=^scheme)/

-- start date
Date_or_date_time_assignment.assigned_date -> @start_date_time
Date_or_date_time_assignment.items -> ^scheme_vn

-- end date
Date_or_date_time_assignment.assigned_date -> @end_date_time
Date_or_date_time_assignment.items -> ^scheme_vn

-- Comprises of
Scheme_version_assignment
Scheme_version_assignment.assigned_activity_method -> ^scheme_vn
Scheme_version_assignment.items -> @comprised_of

-- Location
Scheme_version_assignment
Scheme_version_assignment.assigned_activity_method -> ^scheme_vn
Scheme_version_assignment.items -> @implementation_location_id

-- Derived_from
Scheme_version_assignment
Scheme_version_assignment.assigned_activity_method -> ^scheme_vn
Scheme_version_assignment.items -> @derived_from

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

/schedule(derived_from='@326', comprised_of='@124', subject='@251', description='Tank Cleaning', name='Bilge zone maintenance schedule', start_date_time='@80', schedule_id='MK421', category='Through_Life_Management_Plan', releasing_authority='6421', implementation_location_id='@90', end_date_time='@85', schedule_version='1.0')/

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

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: