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

Figure 2 shows the templates required to represent a deferred scheduled maintenance activity message. The templates shown in yellow in Figure 2 are standard OASIS template. Those shown in light green are business templates developed specifically for the MoDAvDEX context.

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

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

Template: #0 MoDAvDEX.MoDAvDEXmessage: The template: #0 MoDAvDEX.MoDAvDEXmessage (Figure 2) is used to represent the message meta data.
Template: #1 MoDAvDEX.work_order: The template: #1 MoDAvDEX.work_order (Figure 2) 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 2) is used to identify the standard maintenance task that has been deferred.
Template: #4 MoDAvDEX.life_deferment: The template: #4 MoDAvDEX.life_deferment (Figure 2) is used to represent the deferred life of the reportable item. The life property values that will will trigger the deferred activity.
Template: #6 assigning_asserted_state: The template: #6 assigning_asserted_state (Figure 2) is used to represent the deferred state of the Directed_activity instantiated by the MoDAvDEX.work_order.

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

The identifier of the message.

Calendar_date year_component of the date that the message was sent.

Calendar_date month_component of the date that the message was sent.

Calendar_date day_component of the date that the message was sent.

Local_time hour_component of the date and time that the message was sent.

Local_time minute_component of the date and time that the message was sent. This parameter is optional. If not given, it will remain unset.

Local_time second_component of the date and time that the message was sent. This parameter is optional. If not given, it will remain unset.

The name or identifier of the sending organization.

The name or identifier of the receiving organization.

The name or identifier of the contract.

Calendar_date year_component of the date that the information in the message was extracted from the sending system.

Calendar_date month_component of the date that the information in the message was extracted from the sending system.

Calendar_date day_component of the date that the information in the message was extracted from the sending system.

Local_time hour_component of the date that the information in the message was extracted from the sending system.

Local_time minute_component of the date that the information in the message was extracted from the sending system. This parameter is optional. If not given, it will remain unset.

Local_time day_component of the date and time the message is extracted. This parameter is optional. If not given, it will remain unset.

The name of the class being used to classify the security level. (Security_classification_assignment)

The identifier of the work_order.

Calendar_date year_component of date the work order is issued.

Calendar_date month_component of date the work order is issued.

Calendar_date day_component of date the work order is issued.

Local_time hour_component of the date and time the work order is issued.

Local_time month_component of the date and time the work order is issued. This parameter is optional. If not given, it will remain unset.

Local_time second_component of the date and time the work order is issued. This parameter is optional. If not given, it will remain unset.

The type of work order.

The status of the work order

The task identifier.

The task version identifier.

The serial_number of the reportable item that is input to the activity.

The part_number of the reportable item that is input to the activity.

The supplier of the reportable item that is input to the activity.

The NSN of the reportable item that is input to the activity.

The class name corresponding to the property name.

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

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

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

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

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

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

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

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

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

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

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

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 name or identifier of the organization declaring the property.

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

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

%^target = $MoDAvDEXmessage_asset_lifing_extension.message%

where target is the parameter to which the Message is bound.

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

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

%^target = $MoDAvDEXmessage_asset_lifing_extension.rep_item_pai%

where target is the parameter to which the Product_as_individual is bound.

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

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

%^target = $MoDAvDEXmessage_asset_lifing_extension.rep_item_par%

where target is the parameter to which the Product_as_realized is bound.

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

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

%^target = $MoDAvDEXmessage_asset_lifing_extension.rep_item_view%

where target is the parameter to which the Product_as_individual_view is bound.

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

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

%^target = $MoDAvDEXmessage_asset_lifing_extension.act_method%

where target is the parameter to which the Activity_method is bound.

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 = $MoDAvDEXmessage_asset_lifing_extension.task_method_version%

where target is the parameter to which the Task_method_version is bound.

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

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

%^target = $MoDAvDEXmessage_asset_lifing_extension.work_order%

where target is the parameter to which the Work_order is bound.

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

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

%^target = $MoDAvDEXmessage_asset_lifing_extension.dir_act%

where target is the parameter to which the Directed_activity is bound.

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

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

%^target = $MoDAvDEXmessage_asset_lifing_extension.appl_act%

where target is the parameter to which the Applied_activity_assignment is bound.

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

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

%^target = $MoDAvDEXmessage_asset_lifing_extension.deferred_state%

where target is the parameter to which the State_observed is bound.

Template #7 (Figure 2): usage_limitation Hide template parameters Hide all template parameters Show all template parameters
Description
Parameter name:	Parameter value:	Parameter description:
organization	?organization?	The name or id of organization setting the limitation.
deferred_state	State_observed	The deferred state (State_observed) that is the reason for the limitation
approval_status	?approval_status?	The approval status of the lmitation
description	?description?	A description of the limitation
par	Product_as_realized	The reportable item (Product_as_realized)