Figure 2 shows the templates required to represent a message recording a symptom. 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 a symptom using ISO 10303 239 PLCS is provided in Aviation Maintenance DEX: Representing state of a reportable item - PLCS representation - Symptom.

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 MoDAvDEX.symptom

the template: #4 MoDAvDEX.symptom (Figure 2) is used to represent the symptom on the reportable item.

Template: #5 assigning_organization

the template: #5 assigning_organization (Figure 2) is used to represent the organization that identified the symptom.

Template: #6 assigning_reference_data

the template: #6assigning_reference_data (Figure 2) is used to represent the perceived effect on flight safety.

Template: #7 assigning_reference_data

the template: #7assigning_reference_data (Figure 2) is used to represent the system on which the code was observed.

Template: #8 assigning_reference_data

the template: #6assigning_reference_data (Figure 2) is used to represent when/how code indicating how the symptom was discovered,

Template: #9 assigning_reference_data

the template: #9assigning_reference_data (Figure 2) is used to represent effect on operation the recorded symptom had on the phase of operation.