Template:— life_deferment (life_def)
Context:— MoDAvDEX

Date: 2008/02/03 07:53:26
Revision: 1.6

Cover Contents Description Model diags.Input params.Ref. params.Instantiation path Characterizations Issues in situ

This section specifies the template life_deferment.

NOTE The template has been defined in the context of MoDAvDEX. 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 deferral of a maintenance activity until the life properties of the reportable item reach a given value.

Model diagrams

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

Figure 1 shows the templates required to represent the deferral of a maintenance activity to a set of life properties. The templates shown in yellow in Figure 1 are standard OASIS template. Those shown in light green are business templates developed specifically for the MoDAvDEX context.

Further details of how to represent a deferred maintenance activity using ISO 10303 239 PLCS is provided in Aviation Maintenance DEX: Representing deferred activities - PLCS representation.

The following mandatory templates are shown in Figure 1 and used to represent different aspects of the scheduled maintenance activity.

Template: #1 MoDAvDEX.work_order: The template: #1 MoDAvDEX.work_order (Figure 1) is used to represent the maintenance work order and planned activity that has been deferred.
Template: #2 MoDAvDEX.referencing_maintenance_task: The template: #2 MoDAvDEX.referencing_maintenance_task (Figure 1) is used to identify the standard maintenance task that has been deferred.
Template: #3 MoDAvDEX.reportable_item: The template: #3 MoDAvDEX.reportable_item (Figure 1) is used to identify the reportable_item for which the activity has been deferred.
Template: #4 assigning_condition: The template: #4 assigning_condition (Figure 1) is used to represents the trigger or condition for undertaking the deferred activity. The target property that will trigger the activity is represented by an Independent_property, and its value represented by template #11 representing_numeric_property. This target is compared to the life property value represented by the template #8 MoDAvDEX.reportable_item_property
Template: #6 assigning_asserted_state: The template: #6 assigning_asserted_state (Figure 1) is used to represent the deferred state of the Directed_activity instantiated by the MoDAvDEX.work_order.

Figure 1 — An EXPRESS-G representation of the Information model for life_deferment

The graphic for the template to be used in other EXPRESS-G diagrams is shown in Figure 2 below.

Figure 2 — The graphical representation of the life_deferment template

Input parameters

The following input parameters are defined for this template:

property_name (Type='CLASS')

The class name corresponding to the property name.

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

classifications: [ModAvDEX_Product_property]

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

property_value (Type= 'TYPE (any_number_value)' )

The current value of the life property. The data type must also be indicated in this parameter, e.g. "ANY_NUMBER_VALUE(5)".

property_unit (Type='CLASS')

The class name of the unit in which the value is expressed.

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

classifications: [ModAvDEX_Unit]

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

unit_ecl_id (Default=urn:plcs:rdl:LITS,Type='URN', Optional)

The identifier of the External_class_library storing the definition of the class referenced by the parameter @unit_class_name.

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

property_year (Type= 'TYPE (year_number)' )

The year component of the date the property value was measured.

property_month (Type= 'TYPE (month_in_year_number)' )

The month component of the date the property value was measured.

property_day (Type= 'TYPE (day_in_month_number)' )

The day component of the date the property value was measured.

property_hour (Type= 'TYPE (hour_in_day)' )

The hour component of the date the property value was measured.

property_minute (Type= 'TYPE (minute_in_hour)' , Optional)

The minute component of the date the property value was measured. This parameter is optional. If not given, it will remain unset.

property_second (Type= 'TYPE (second_in_minute)' , Optional)

The second component of the date the property value was measured. This parameter is optional. If not given, it will remain unset.

property_value_type (Type='CLASS')

meter_reading - the value measured on the meter; cumulative - the cumulative value taking into account the changing of meters; sortie - the value of sortie related data not use for calculating life. E.g fuel consumed.

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

classifications: [meter_reading_value]

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

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

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

property_org_id (Type='STRING')

The name or identifier of the organization declaring the property.

deferred_value (Type= 'TYPE (any_number_value)' )

The deferred value of the property. I.e. the value that will trigger the activity. The data type must also be indicated in this parameter, e.g. "ANY_NUMBER_VALUE(5)".

par (Type= 'ENTITY (Product_as_realized)' )

The reportable item whose life property is being measured in order to trigger the activity.

appl_act (Type= 'ENTITY (Applied_activity_assignment)' )

The assignment of the deferred activity to the reportable item.

Reference parameters

The following reference parameters are defined for this template:

condition(Type='ENTITY (Condition)')

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

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

%^target = $life_deferment.condition%

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

Independent_property
%^ind_prop = Independent_property%
Independent_property.id = '/IGNORE'
Independent_property.description = '/IGNORE'
Independent_property.property_type = '/IGNORE'
/assigning_reference_data(
    items=^ind_prop,
    class_name='periodicity',
    ecl_id='urn:plcs:rdl:std')/
/representing_numeric_property(
    value=@deferred_value,
    unit=@property_unit,
    unit_ecl_id=@unit_ecl_id,
    si_unit=@si_unit,
    context='Numerical_representation_context',
    context_ecl_id='urn:plcs:rdl:std')/
%^rep = $representing_numeric_property.representation%
/assigning_condition(
    cond_item=@appl_act,
    cond_asg_class='Deferred_activity_assignment',
    cond_asg_ecl_id='urn:plcs:rdl:std',
    cond_class='Deferred_life_condition',
    cond_ecl_id='urn:plcs:rdl:std',
    cond_para_item=^ind_prop)/
%^condition = $assigning_condition.cond%
/reportable_item_property(
    property_name=@property_name,
    property_value=@property_value,
    property_unit=@property_unit,
    si_unit=@si_unit,
    year=@property_year,
    month=@property_month,
    day=@property_day,
    hour=@property_hour,
    minute=@property_minute,
    second=@property_second,
    org_id=@property_org_id,
    value_type=@property_value_type,
    described_element=@par)/
%^prop_val_rep = $reportable_item_property.prop_val_rep%
Condition_parameter
Condition_parameter.name = '/IGNORE'
Condition_parameter.description = '/IGNORE'
Condition_parameter.condition -> ^condition
Condition_parameter.parameter -> ^prop_val_rep
Independent_property_representation
Independent_property_representation.description = '/IGNORE'
Independent_property_representation.role = '/IGNORE'
Independent_property_representation.property -> ^ind_prop
Independent_property_representation.rep -> ^rep

The following entities are instantiated with attributes as specified:

Entity in path	Value	Inherited from
Independent_property.id	'/IGNORE'	—
Independent_property.description	'/IGNORE'	—
Independent_property.property_type	'/IGNORE'	—
Condition_parameter.name	'/IGNORE'	—
Condition_parameter.description	'/IGNORE'	—
Independent_property_representation.description	'/IGNORE'	—
Independent_property_representation.role	'/IGNORE'	—

Characterizations

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