Template:— required_pse_constituent_usage_role (rpse_cusr)
Context:— UK_Defence		 Date: 2009/04/17 11:32:31
Revision: 1.5
CoverContentsDescriptionBus. obj.Model diags.Input params.Ref. params.Instantiation pathInstance diags.CharacterizationsIssuesin situ

This section specifies the template required_pse_constituent_usage_role.

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.

Description

This template describes how to represent the operational usage, availability and maintainability requirements for a PSE constituent within a defined role.

Business object definition


Figure 1 —  Graphical Representation for Business Object required_pse_constituent_usage_role

Figure 1 —  Graphical Representation for Business Object required_pse_constituent_usage_role

The definition of a required_pse_constituent_usage_role object is: This information object represents information about the operational usage, availability and maintainability requirements for a PSE constituent within a defined role.

Attribute name

Attribute description

Attribute type

Optionality
Achieved availability This is the required probability that the item will operate satisfactorily when required: a) under nominal conditions; b) with all required resources; c) including standby and preventive maintenance downtime; d) excluding downtime due to supply and administration. intrinsic Optional (See Conditional_availability)
Annual missions This is the average number of missions the item shall be required to accomplish annually. intrinsic Optional
Annual operating days This is the average number of days per year on which the item shall be required to perform a mission. intrinsic Optional
Annual standby time This is the time (per calendar year) that the item is expected to be on standby. Measure with unit Optional
Average logistic delay time This is the permissable average time for delays in maintenance attributable to administration and logistics. Measure with unit Optional
ID This is the identifier of the required usage. Identifier Mandatory
Identifier.id This is the value of the id attribute of the Identifier applied to the This is the identifier of the required usage. intrinsic Mandatory
Identifier.type This attribute is the type associated with the id of the Identifier given to the required usage. item_of_supply_id Mandatory
Identifier.source_organization This attribute is the value representing the source organization that provides the id of the Identifier given to the required usage. This value is assumed to be a type of Organization_identification_code. Organization_identification_code Mandatory
Inherent availability This is the probability that the item will operate satisfactorily when required: a) under nominal conditions; b) with all required resources; c) excluding standby and preventive maintenance downtime; and d) excluding downtime due to supply and administration. intrinsic Optional (See Conditional_availability)
Maximum administrative and logistic delay This is the maximum time permitted for delays due to administration and logistics only. Measure with unit Optional
Maximum duration intrinsic Mandatory
Maximum time to repair This is the maximum time within which all corrective maintenance task shall be completed. intrinsic Optional
Mean duration intrinsic Mandatory
Mean mission duration This is the average elapsed time of a single mission for the item. Measure with unit Optional
Operating personnel This is the number of personnel that will be used by the organisation stating the usage requirement, to operate the item. intrinsic Optional
Operational availability This is the probability that the item will operate satisfactorily when required: a) under nominal conditions; b) with all required resources; c) including standby and preventive maintenance downtime; and d) including downtime due to supply and administration. intrinsic Optional (See Conditional_availability)
Payload intrinsic Mandatory
Related PSE constituent Relationship to Platform System Equipment Constituent Mandatory
Related usage scenario This is the category of usage scenario within which the usage is required. EXAMPLES (From DEF STAN 00-60, DED 275, operational requirement indicator) include: "wartime", "peacetime". New scenarios defined in SDR are (from PREVIEW, 10 July 1998): "peacetime security", "overseas territories", "defence diplomacy", "wider British interest", "peace support and humanitarian operations", "regional conflict outside NATO", "NATO regional conflict", "strategic attack on NATO". intrinsic Mandatory
Role name This is the name of the role. Examples include: "Training", "Bombing", "Reconnaissance". intrinsic Mandatory
Technical mean active maintenance downtime This is the required average elapsed time for all maintenance tasks performed to mitigate or correct technical failures. Measure with unit Optional
Technical mean time to repair This is the required average duration of any repair procedure on the item where maintenance is required due to failures which do not effect the operational mission. NOTE: This includes Administrative and Logistic Delay Time (ALDT). Measure with unit Optional

Table 1 — required_pse_constituent_usage_role attribute details

Model diagrams
The EXPRESS-G diagram in Figure 2 shows the templates and EXPRESS entities that are required to represent the template "required_pse_constituent_usage_role". The text highlighted in blue shows the template parameters.


Figure 2 —  An EXPRESS-G representation of the Information model for required_pse_constituent_usage_role

Figure 2 —  An EXPRESS-G representation of the Information model for required_pse_constituent_usage_role

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 required_pse_constituent_usage_role template

Figure 3 —  The graphical representation of the required_pse_constituent_usage_role template

Input parameters
The following input parameters are defined for this template:
id (Type='STRING')
This is the identifier of the item of supply.
source_organization (Type='STRING')
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.
annual_missions (Type='INTEGER', Optional)
This is the average number of missions the item shall be required to accomplish annually.
annual_operating_days (Type='INTEGER', Optional)
This is the average number of days per year on which the item shall be required to perform a mission.
annual_standby_time (Type='REAL', Optional)
This is the time per year where the product has been on standby.
average_logistic_delay_time (Type='REAL', Optional)
This is the average time per year where the product has been on standby.
average_logistic_delay_time_unit (Type='CLASS')
The class name of the unit in which the mean time to repair value is expressed, probably days or years.
The following classes and their sub-classes can be used:
classifications: "Context_dependent_unit" (urn:plcs:rdl:std:Context_dependent_unit)
average_logistic_delay_time_si_unit (Type='BOOLEAN')
Value should be set to true if the unit is a SI base unit defined by ISO, i.e. kilogram (kg) for Mass, second (s) for Time, metre (m) for Displacement, ampere (A) for Electrical current, kelvin (K) for Temperature, mole (mol) for Amount of substance, and candela (cd) for Luminous intensity. If this is not the case it should be set to false.
Note that the representation of true and false depends on exchange format. In Part 11 (a STEP file) true is represented by the string ".T.", and false by ".F.", while in Part 28 (XML) they are represented by text strings "true" and "false".
maximum_admin_and_logistic_delay (Type='REAL', Optional)
This is the average time per year where the product has been on standby.
maximum_admin_and_logistic_delay_unit (Type='CLASS')
The class name of the unit in which the mean time to repair value is expressed, probably days or years.
The following classes and their sub-classes can be used:
classifications: "Context_dependent_unit" (urn:plcs:rdl:std:Context_dependent_unit)
maximum_admin_and_logistic_delay_si_unit (Type='BOOLEAN')
Value should be set to true if the unit is a SI base unit defined by ISO, i.e. kilogram (kg) for Mass, second (s) for Time, metre (m) for Displacement, ampere (A) for Electrical current, kelvin (K) for Temperature, mole (mol) for Amount of substance, and candela (cd) for Luminous intensity. If this is not the case it should be set to false.
Note that the representation of true and false depends on exchange format. In Part 11 (a STEP file) true is represented by the string ".T.", and false by ".F.", while in Part 28 (XML) they are represented by text strings "true" and "false".
maximum_duration (Type='REAL', Optional)
This is the average time per year where the product has been on standby.
maximum_duration_unit (Type='CLASS')
The class name of the unit in which the mean time to repair value is expressed, probably days or years.
The following classes and their sub-classes can be used:
classifications: "Context_dependent_unit" (urn:plcs:rdl:std:Context_dependent_unit)
maximum_duration_si_unit (Type='BOOLEAN')
Value should be set to true if the unit is a SI base unit defined by ISO, i.e. kilogram (kg) for Mass, second (s) for Time, metre (m) for Displacement, ampere (A) for Electrical current, kelvin (K) for Temperature, mole (mol) for Amount of substance, and candela (cd) for Luminous intensity. If this is not the case it should be set to false.
Note that the representation of true and false depends on exchange format. In Part 11 (a STEP file) true is represented by the string ".T.", and false by ".F.", while in Part 28 (XML) they are represented by text strings "true" and "false".
maximum_time_to_repair (Type= 'TYPE (any_number_value)' )
The value of mean time to repair. The data type must also be indicated in this parameter, e.g. "ANY_NUMBER_VALUE(5)".
maximum_time_to_repair_unit (Type='CLASS')
The class name of the unit in which the mean time to repair value is expressed, probably days or years.
The following classes and their sub-classes can be used:
classifications: "Context_dependent_unit" (urn:plcs:rdl:std:Context_dependent_unit)
maximum_time_to_repair_si_unit (Type='BOOLEAN')
Value should be set to true if the unit is a SI base unit defined by ISO, i.e. kilogram (kg) for Mass, second (s) for Time, metre (m) for Displacement, ampere (A) for Electrical current, kelvin (K) for Temperature, mole (mol) for Amount of substance, and candela (cd) for Luminous intensity. If this is not the case it should be set to false.
Note that the representation of true and false depends on exchange format. In Part 11 (a STEP file) true is represented by the string ".T.", and false by ".F.", while in Part 28 (XML) they are represented by text strings "true" and "false".
mean_duration (Type='REAL', Optional)
This is the average time per year where the product has been on standby.
mean_duration_unit (Type='CLASS')
The class name of the unit in which the mean time to repair value is expressed, probably days or years.
The following classes and their sub-classes can be used:
classifications: "Context_dependent_unit" (urn:plcs:rdl:std:Context_dependent_unit)
mean_duration_si_unit (Type='BOOLEAN')
Value should be set to true if the unit is a SI base unit defined by ISO, i.e. kilogram (kg) for Mass, second (s) for Time, metre (m) for Displacement, ampere (A) for Electrical current, kelvin (K) for Temperature, mole (mol) for Amount of substance, and candela (cd) for Luminous intensity. If this is not the case it should be set to false.
Note that the representation of true and false depends on exchange format. In Part 11 (a STEP file) true is represented by the string ".T.", and false by ".F.", while in Part 28 (XML) they are represented by text strings "true" and "false".
mean_mission_duration (Type='REAL', Optional)
This is the average time per year where the product has been on standby.
mean_mission_duration_unit (Type='CLASS')
The class name of the unit in which the mean time to repair value is expressed, probably days or years.
The following classes and their sub-classes can be used:
classifications: "Context_dependent_unit" (urn:plcs:rdl:std:Context_dependent_unit)
mean_mission_duration_si_unit (Type='BOOLEAN')
Value should be set to true if the unit is a SI base unit defined by ISO, i.e. kilogram (kg) for Mass, second (s) for Time, metre (m) for Displacement, ampere (A) for Electrical current, kelvin (K) for Temperature, mole (mol) for Amount of substance, and candela (cd) for Luminous intensity. If this is not the case it should be set to false.
Note that the representation of true and false depends on exchange format. In Part 11 (a STEP file) true is represented by the string ".T.", and false by ".F.", while in Part 28 (XML) they are represented by text strings "true" and "false".
operating_personnel (Type='INTEGER')
This is the average time per year where the product has been on standby.
payload (Type='REAL', Optional)
This is the average time per year where the product has been on standby.
payload_unit (Type='CLASS')
The class name of the unit in which the mean time to repair value is expressed, probably days or years.
The following classes and their sub-classes can be used:
classifications: "Context_dependent_unit" (urn:plcs:rdl:std:Context_dependent_unit)
payload_si_unit (Type='BOOLEAN')
Value should be set to true if the unit is a SI base unit defined by ISO, i.e. kilogram (kg) for Mass, second (s) for Time, metre (m) for Displacement, ampere (A) for Electrical current, kelvin (K) for Temperature, mole (mol) for Amount of substance, and candela (cd) for Luminous intensity. If this is not the case it should be set to false.
Note that the representation of true and false depends on exchange format. In Part 11 (a STEP file) true is represented by the string ".T.", and false by ".F.", while in Part 28 (XML) they are represented by text strings "true" and "false".
technical_mean_active_maintenance_downtime (Type='REAL', Optional)
This is the average time per year where the product has been on standby.
technical_mean_active_maintenance_downtime_unit (Type='CLASS')
The class name of the unit in which the mean time to repair value is expressed, probably days or years.
The following classes and their sub-classes can be used:
classifications: "Context_dependent_unit" (urn:plcs:rdl:std:Context_dependent_unit)
technical_mean_active_maintenance_downtime_si_unit (Type='BOOLEAN')
Value should be set to true if the unit is a SI base unit defined by ISO, i.e. kilogram (kg) for Mass, second (s) for Time, metre (m) for Displacement, ampere (A) for Electrical current, kelvin (K) for Temperature, mole (mol) for Amount of substance, and candela (cd) for Luminous intensity. If this is not the case it should be set to false.
Note that the representation of true and false depends on exchange format. In Part 11 (a STEP file) true is represented by the string ".T.", and false by ".F.", while in Part 28 (XML) they are represented by text strings "true" and "false".
technical_mean_time_to_repair (Type= 'TYPE (any_number_value)' )
The value of mean time to repair. The data type must also be indicated in this parameter, e.g. "ANY_NUMBER_VALUE(5)".
technical_mean_time_to_repair_unit (Type='CLASS')
The class name of the unit in which the mean time to repair value is expressed, probably days or years.
The following classes and their sub-classes can be used:
classifications: "Context_dependent_unit" (urn:plcs:rdl:std:Context_dependent_unit)
technical_mean_time_to_repair_si_unit (Type='BOOLEAN')
Value should be set to true if the unit is a SI base unit defined by ISO, i.e. kilogram (kg) for Mass, second (s) for Time, metre (m) for Displacement, ampere (A) for Electrical current, kelvin (K) for Temperature, mole (mol) for Amount of substance, and candela (cd) for Luminous intensity. If this is not the case it should be set to false.
Note that the representation of true and false depends on exchange format. In Part 11 (a STEP file) true is represented by the string ".T.", and false by ".F.", while in Part 28 (XML) they are represented by text strings "true" and "false".
related_scenario (Type='CLASS')
The name of the class used to classify the Activity_method that represents the mission type. The classes need to be agreed by the exchange partners.
The following classes and their sub-classes can be used:
classifications: [Scenario]
[warning:]Error RDL4: The URI urn:plcs:rdl:uk_defence is not listed in dexlib/data/refdata/rdl_index.xml
role_name (Type='CLASS')
The name of the class used to specify the role of the required pse constituent usage role.
The following classes and their sub-classes can be used:
classifications: [pse_constituent_usage_role]
[warning:]Error RDL4: The URI urn:plcs:rdl:uk_defence is not listed in dexlib/data/refdata/rdl_index.xml
related_pse_constituent (Type= 'ENTITY (Product_group_membership)' )
This is the reference to the platform, system and equipment constituent for which the related usage profiles are defined.
related_profile_for_role (Type= 'ENTITY (Task_method)' )
This is the reference to the required pse constituent usage profile for which the usage role is defined.
Reference parameters
The following reference parameters are defined for this template:
required_pse_usage_role(Type='ENTITY (Task_method_version)')
Allow the Task_method_version entity instantiated in this path to be referenced when this template is used.
Note: The Task_method_version entity can be referenced in a template path by:
%^target = $required_pse_constituent_usage_role.required_pse_usage_role%
where target is the parameter to which the Task_method_version is bound.
Instantiation path
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.
-- create the task method version to represent the required_pse_usage_role
Task_method_version
Task_method_version.name = '/IGNORE'
Task_method_version.purpose = '/IGNORE'
%^required_pse_usage_role = Task_method_version%

-- create the relationship to link the related profile
Task_method_version.of_task_method -> @related_profile_for_role

-- create the assignment to link the pse constituent
Task_method_version_assignment
Task_method_version_assignment.role = '/IGNORE'
Task_method_version_assignment.assigned_activity_method -> ^required_pse_usage_role
Task_method_version_assignment.items -> @related_pse_constituent

-- identifier
/identifier(
    ID=@id,
    source_organization=@source_organization,
    type='required_pse_usage_role_id',
    items=^required_pse_usage_role)/

-- Annual Operating Days
/assigning_process_property(
    property_class_name='annual_operating_days',
    property_ecl_id='urn:plcs:rdl:tlss',
    described_element=^required_pse_usage_role)/

-- Assign reference parameter
-- not sure if needed - can we not substitute this string inside the call to process property?
%^annual_operating_days = $assigning_process_property.property%

-- Value and Unit
/process_property_numeric(
    value=@annual_operating_days,
    unit='day',
    unit_ecl_id='urn:plcs:rdl:std',
    si_unit='.F.',
    context='Constituent_usage_role',
    context_ecl_id='urn:plcs:rdl:std',
    property=^annual_operating_days)/

-- Annual Missions
/assigning_process_property(
    property_class_name='annual_missions',
    property_ecl_id='urn:plcs:rdl:tlss',
    described_element=^required_pse_usage_role)/

-- Assign Annual Missions reference parameter
-- not sure if needed
%^annual_missions = $assigning_process_property.property%

-- Annual Missions Value and Unit
/process_property_numeric(
    value=@annual_missions,
    unit='number_of_missions',
    unit_ecl_id='urn:plcs:rdl:tlss',
    si_unit='.F.',
    context='Constituent_usage_role',
    context_ecl_id='urn:plcs:rdl:tlss',
    property=^annual_missions)/

-- Annual_standby_time
/assigning_process_property(
    property_class_name='annual_standby_time',
    property_ecl_id='urn:plcs:rdl:tlss',
    described_element=^required_pse_usage_role)/

-- Assign Annual_standby_time reference parameter
-- not sure if needed
%^annual_standby_time = $assigning_process_property.property%

-- Annual_standby_time Value and Unit (opted for hours - as couldn't see cbis definition
/process_property_numeric(
    value=@annual_standby_time,
    unit='hour',
    unit_ecl_id='urn:plcs:rdl:tlss',
    si_unit='.T.',
    context='Constituent_usage_role',
    context_ecl_id='urn:plcs:rdl:tlss',
    property=^annual_standby_time)/

-- Average logistic delay time
/assigning_process_property(
    property_class_name='average_logistic_delay_time',
    property_ecl_id='urn:plcs:rdl:tlss',
    described_element=^required_pse_usage_role)/

-- Assign average logistic delay time reference parameter
-- not sure if needed
%^average_logistic_delay_time = $assigning_process_property.property%

-- Average logistic delay time Value and Unit (opted for hours - as couldn't see cbis definition
/process_property_numeric(
    value=@average_logistic_delay_time,
    unit=@average_logistic_delay_time_unit,
    unit_ecl_id='urn:plcs:rdl:tlss',
    si_unit=@average_logistic_delay_time_si_unit,
    context='Constituent_usage_role',
    context_ecl_id='urn:plcs:rdl:tlss',
    property=^average_logistic_delay_time)/

-- availability_value is now assigned to the required_pse_usage_role, not part of it.
-- Maximum_admin_and_logistic_delay
/assigning_process_property(
    property_class_name='maximum_admin_and_logistic_delay',
    property_ecl_id='urn:plcs:rdl:tlss',
    described_element=^required_pse_usage_role)/

-- Assign Maximum_admin_and_logistic_delay reference parameter
-- not sure if needed
%^maximum_admin_and_logistic_delay = $assigning_process_property.property%

-- Maximum_admin_and_logistic_delay Value and Unit (opted for hours - as couldn't see cbis definition
/process_property_numeric(
    value=@maximum_admin_and_logistic_delay,
    unit=@maximum_admin_and_logistic_delay_unit,
    unit_ecl_id='urn:plcs:rdl:tlss',
    si_unit=@maximum_admin_and_logistic_delay_si_unit,
    context='Constituent_usage_role',
    context_ecl_id='urn:plcs:rdl:tlss',
    property=^maximum_admin_and_logistic_delay)/

-- Maximum_duration
/assigning_process_property(
    property_class_name='maximum_duration',
    property_ecl_id='urn:plcs:rdl:tlss',
    described_element=^required_pse_usage_role)/

-- Assign Maximum_duration reference parameter
-- not sure if needed
%^maximum_duration = $assigning_process_property.property%

-- Maximum_duration Value and Unit (opted for hours - as couldn't see cbis definition
/process_property_numeric(
    value=@maximum_duration,
    unit=@maximum_duration_unit,
    unit_ecl_id='urn:plcs:rdl:tlss',
    si_unit=@maximum_duration_si_unit,
    context='Constituent_usage_role',
    context_ecl_id='urn:plcs:rdl:tlss',
    property=^maximum_duration)/

-- Maximum_duration
/assigning_process_property(
    property_class_name='maximum_time_to_repair',
    property_ecl_id='urn:plcs:rdl:tlss',
    described_element=^required_pse_usage_role)/

-- Assign Maximum_duration reference parameter
-- not sure if needed
%^maximum_time_to_repair = $assigning_process_property.property%

-- Maximum_time_to_repair Value and Unit (opted for hours - as couldn't see cbis definition
/process_property_numeric(
    value=@maximum_time_to_repair,
    unit=@maximum_time_to_repair_unit,
    unit_ecl_id='urn:plcs:rdl:tlss',
    si_unit=@maximum_time_to_repair_si_unit,
    context='Constituent_usage_role',
    context_ecl_id='urn:plcs:rdl:tlss',
    property=^maximum_time_to_repair)/

-- Mean_duration
/assigning_process_property(
    property_class_name='mean_duration',
    property_ecl_id='urn:plcs:rdl:tlss',
    described_element=^required_pse_usage_role)/

-- Assign Mean_duration reference parameter
-- not sure if needed
%^mean_duration = $assigning_process_property.property%

-- Mean_duration Value and Unit (opted for hours - as couldn't see cbis definition
/process_property_numeric(
    value=@mean_duration,
    unit=@mean_duration_unit,
    unit_ecl_id='urn:plcs:rdl:tlss',
    si_unit=@mean_duration_si_unit,
    context='Constituent_usage_role',
    context_ecl_id='urn:plcs:rdl:tlss',
    property=^mean_duration)/

-- Mean_mission_duration
/assigning_process_property(
    property_class_name='mean_mission_duration',
    property_ecl_id='urn:plcs:rdl:tlss',
    described_element=^required_pse_usage_role)/

-- Assign Mean_duration reference parameter
-- not sure if needed
%^mean_mission_duration = $assigning_process_property.property%

-- mean_mission_duration Value and Unit (opted for hours - as couldn't see cbis definition
/process_property_numeric(
    value=@mean_mission_duration,
    unit=@mean_mission_duration_unit,
    unit_ecl_id='urn:plcs:rdl:tlss',
    si_unit=@mean_mission_duration_si_unit,
    context='Constituent_usage_role',
    context_ecl_id='urn:plcs:rdl:tlss',
    property=^mean_mission_duration)/

-- Operating Personnel
-- Annual Operating Days
/assigning_process_property(
    property_class_name='operating_personnel',
    property_ecl_id='urn:plcs:rdl:tlss',
    described_element=^required_pse_usage_role)/

-- Assign reference parameter
-- not sure if needed - can we not substitute this string inside the call to process property?
%^operating_personnel = $assigning_process_property.property%

-- Value and Unit
/process_property_numeric(
    value=@operating_personnel,
    unit='number_of_people',
    unit_ecl_id='urn:plcs:rdl:std',
    si_unit='.F.',
    context='Constituent_usage_role',
    context_ecl_id='urn:plcs:rdl:std',
    property=^operating_personnel)/

-- Payload
/assigning_process_property(
    property_class_name='payload',
    property_ecl_id='urn:plcs:rdl:tlss',
    described_element=^required_pse_usage_role)/

-- Assign payload reference parameter
-- not sure if needed
%^payload = $assigning_process_property.property%

-- payload Value and Unit (opted for hours - as couldn't see cbis definition
/process_property_numeric(
    value=@payload,
    unit=@payload_unit,
    unit_ecl_id='urn:plcs:rdl:tlss',
    si_unit=@payload_si_unit,
    context='Constituent_usage_role',
    context_ecl_id='urn:plcs:rdl:tlss',
    property=^payload)/

-- technical_mean_active_maintenance_downtime
/assigning_process_property(
    property_class_name='technical_mean_active_maintenance_downtime',
    property_ecl_id='urn:plcs:rdl:tlss',
    described_element=^required_pse_usage_role)/

-- Assign technical_mean_active_maintenance_downtime reference parameter
-- not sure if needed
%^technical_mean_active_maintenance_downtime = $assigning_process_property.property%

-- technical_mean_active_maintenance_downtime Value and Unit (opted for hours - as couldn't see cbis definition
/process_property_numeric(
    value=@technical_mean_active_maintenance_downtime,
    unit=@technical_mean_active_maintenance_downtime_unit,
    unit_ecl_id='urn:plcs:rdl:tlss',
    si_unit=@technical_mean_active_maintenance_downtime_si_unit,
    context='Constituent_usage_role',
    context_ecl_id='urn:plcs:rdl:tlss',
    property=^technical_mean_active_maintenance_downtime)/

-- technical_mean_time_to_repair
/assigning_process_property(
    property_class_name='technical_mean_time_to_repair',
    property_ecl_id='urn:plcs:rdl:tlss',
    described_element=^required_pse_usage_role)/

-- Assign technical_mean_time_to_repair reference parameter
-- not sure if needed
%^technical_mean_time_to_repair = $assigning_process_property.property%

-- technical_mean_time_to_repair Value and Unit (opted for hours - as couldn't see cbis definition
/process_property_numeric(
    value=@technical_mean_time_to_repair,
    unit=@technical_mean_time_to_repair_unit,
    unit_ecl_id='urn:plcs:rdl:tlss',
    si_unit=@technical_mean_time_to_repair_si_unit,
    context='Constituent_usage_role',
    context_ecl_id='urn:plcs:rdl:tlss',
    property=^technical_mean_time_to_repair)/

-- related scenario
/assigning_reference_data(
    class_name=@related_scenario,
    ecl_id='urn:plcs:rdl:tlss',
    items=^required_pse_usage_role)/

-- Role name
/assigning_reference_data(
    class_name='role_name',
    ecl_id='urn:plcs:rdl:tlss',
    items=^required_pse_usage_role)/
The following entities are instantiated with attributes as specified:
Entity in path Value Inherited from
Task_method_version.name '/IGNORE' Activity_method.name
Task_method_version.purpose '/IGNORE' Activity_method.purpose
Task_method_version_assignment.role '/IGNORE' Applied_activity_method_assignment.role
Instance diagrams
The instance diagram in Figure  4 shows an example of the EXPRESS entities and templates that are instantiated by the template:
/required_pse_constituent_usage_role(items='#1', class_name='Safety_critical', ecl_id='urn:plcs:rdl:std')/
(an illustration of the consolidated required_pse_constituent_usage_role template is shown in Figure 5 below.)


Figure 4 —  Entities instantiated by required_pse_constituent_usage_role template

Figure 4 —  Entities instantiated by required_pse_constituent_usage_role 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:
/required_pse_constituent_usage_role(items='#1', class_name='Safety_critical', ecl_id='urn:plcs:rdl:std')/


Figure 5 —  Instantiation of required_pse_constituent_usage_role template

Figure 5 —  Instantiation of required_pse_constituent_usage_role template

Characterizations
No common characterizations of the template required_pse_constituent_usage_role have been identified. However, the ISO 10303-239 EXPRESS model may enable other assignments to the entities instantiated by the template.

© UK MOD 2010 — All rights reserved