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

Figure 2 shows the templates required to represent sortie feedback. The templates shown in yellow are standard OASIS template. Those shown in light green are business templates developed specifically for the MoDAvDEX context.

Further details of how to represent sortie feedback using ISO 10303 239 PLCS is provided in Aviation Maintenance DEX: Representing a reportable item usage activity - PLCS representation.

The following mandatory templates are shown in Figure 2 and used to represent different aspects of the sortie feedback.

Template: #1 MoDAvDEX.MoDAvDEXmessage: The template: #1 MoDAvDEX.MoDAvDEXmessage (Figure 2) is used to represent the message meta data.
Template: #2 MoDAvDEX.reportable_item_usage: the template: #2 MoDAvDEX.reportable_item_usage (Figure 2) is used to represent the sortie that was flown.
Template: #3 MoDAvDEX.reportable_item: the template: #3 MoDAvDEX.reportable_item (Figure 2) is used to represent the reportable item (normally an aircraft) that has flown the sortie.
Template: #4 assigning_time: the template: #4 assigning_time (Figure 2) is used to represent the time when the sortie finished.
Template: #5 assigning_location: the template: #5 assigning_location (Figure 2) is used to represent the take off location.
Template: #6 assigning_location: the template: #6 assigning_location (Figure 2) is used to represent the landing location.
Template: #7 MoDAvDEX.activity_property: the template: #7 MoDAvDEX.activity_property (Figure 2) is used to represent the duration of the sortie.
Template: #8 MoDAvDEX.reportable_item_property: the template: #8 MoDAvDEX.reportable_item_property (Figure 2) is used to represent the life property of the reportable item that has been increased by the sortie. Normally flying hours.
Template: #9 assigning_justification_support_item: the template: #9 assigning_justification_support_item (Figure 2) is used to establish the relationship between the life property and the sortie to record the reason for the increase in property value.
Template: #10 assigning_justification: the template: #10 assigning_justification (Figure 2) is used to establish the relationship between the life property and the sortie to record the reason for the increase in property value.

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 serial_number of the reportable item that undertook the activity.

The part_number of the reportable item that undertook the activity.

The supplier of the reportable item that undertook the activity.

The NSN of the reportable item that undertook the activity.

The identifier of the activity.

Calendar_date year_component of the date the activity was started.

Calendar_date month_component of the date the activity was started.

Calendar_date day_component of the date the activity was started.

Local_time hour_component of the date and time the date the activity was started.

Local_time minute_component of the date and time the activity started. This parameter is optional. If not given, it will remain unset.

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

The identification of the type of sortie activity.

Calendar_date year_component of the date the activity finished.

Calendar_date month_component of the date the activity finished.

Calendar_date day_component of the date the activity finished.

Local_time hour_component of the date and time the date the activity finished.

Local_time minute_component of the date and time the activity finished. This parameter is optional. If not given, it will remain unset.

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

The take off location for the activity.

The landing location for the activity

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

The class name corresponding to the property name.

The value of the property. The datatype 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.

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 creation date of the property value.

The month component of the creation date of the property value.

The day component of the creation date of the property value.

The hour component of the creation date of the property value.

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

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

The name or identifier of the organization declaring the property.

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.

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_sortie_feedback.message%

where target is the parameter to which the Message 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_sortie_feedback.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_sortie_feedback.view%

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

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 = $MoDAvDEXmessage_sortie_feedback.act_act%

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

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

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

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

%^target = $MoDAvDEXmessage_sortie_feedback.act_property%

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

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

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

%^target = $MoDAvDEXmessage_sortie_feedback.act_prop_val_rep%

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

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

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

%^target = $MoDAvDEXmessage_sortie_feedback.property%

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

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

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

%^target = $MoDAvDEXmessage_sortie_feedback.prop_val_rep%

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

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

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

%^target = $MoDAvDEXmessage_sortie_feedback.part%

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

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

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

%^target = $MoDAvDEXmessage_sortie_feedback.part_version%

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

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

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

%^target = $MoDAvDEXmessage_sortie_feedback.justification%

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

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

/MoDAvDEXmessage_sortie_feedback(msg_identifier='Msg_sortie_1', sent_year='2007', sent_month='12', sent_day='20', sent_hour='20', sent_minute='20', sent_second='0', sender_organization='BigAirways Ltd', receiver_organization='AircraftRepairs Ltd', contract_identifier='Ct-1', extract_year='2007', extract_month='12', extract_day='20', extract_hour='20', extract_minute='18', extract_second='0', security_class='unclassified', end_serial_number='FastJet-00001', end_part_number='FastJet', end_supplier='PlaneMaker Ltd', end_NSN='NSN-FastJet', sortie_identification='Sortie-1', start_time_year='2007', start_time_month='12', start_time_day='20', start_time_hour='5', start_time_minute='30', start_time_second='0', profile_code='sortie_profile_002', end_time_year='2007', end_time_month='12', end_time_day='20', end_time_hour='6', end_time_minute='30', end_time_second='0', take_off_location='HomeBase', landing_location='HomeBase', duration_value='1', property_name='Flying_hours_property', property_value='2000', property_unit='Flying_hours', si_unit='false', year='2007', month='12', day='20', hour='6', minute='40', second='0', org_id='BigAirways Ltd', value_type='cumulative_value')/

The instance model in STEP ASCII exchange file format (ISO 10303 Part 21 syntax) is provided in the file MoDAvDEXmessage_sortie_feedback_inst.p21. The instance model in STEP ASCII exchange file format (ISO 10303 Part 28 syntax) provided in the file MoDAvDEXmessage_sortie_feedback_inst.xml.