Understanding Inbound Interoperability for Condition-Based Maintenance

You run the Inbound Flat File Conversion program (R47002C) to copy the data from an external text file into the Unedited Condition-Based Alerts table (F1310Z1). The Inbound Flat File Conversion program validates the text file against the F1310Z1 table and the data dictionary specifications for the table. If the text file passes this validation, the system adds the data to the F1310Z1 table.

You can use the Unedited Condition-Based Alert Revisions program (P1310Z1) to add, update, and review the transactions in the F1310Z1 table.

You run the Inbound Condition-Based Alerts Processor program (R1310Z1I) to copy the information from the F1310Z1 table to the Condition-Based Alerts table (F1310).

The Inbound Condition-Based Alerts Processor program (R1310Z1I) performs these functions:

  • Processes the inbound condition-based alerts transactions.

  • Updates the F1310 table.

  • Initiates any required downstream processing that is based on the transaction information or the alert action rules by running a version of the Condition-Based Maintenance Alerts program (R1312).

The report displays the transaction information, including whether the transaction was successful; user ID; batch number; transaction number; equipment number; description; alert level; event date; event time; and time zone. After the alert has been successfully processed, you can use the Condition-Based Alerts program (P1310) to review and process the alert.

The Inbound Condition-Based Alerts Processor program (R1310Z1I) requires that the F1310Z1 interface table have data in these fields:

  • Asset Number (NUMB), Unit Number (APID), or Serial Number (ASID).

  • Product Model (PRODM).

  • Automated Response Type (TYRP).

  • Description (DL01).

  • Event Date (EVTDT).

  • Event Time (EVTTM).

    You can enter the event date and time using the Coordinated Universal Time (UTC) or the local date and time with time zone.

  • Alert Level (PDFL).

These fields are frequently used, but are optional:

  • Measurement Location (MELC).

  • Time Zone (TIMEZONES).

  • Daylight Savings Rule Name (DSAVNAME).

  • Send Notification Message (SNDN).

  • Notification Recipient (NOTR).

  • Notification Structure Type (NSTT).

  • Investigation Recipient (INVR).

  • Investigation Structure Type (ISTT).

  • Model Work Order (DOCO).

  • Service Type (SRVT).

You can use a number of setup applications within the Condition-Based Maintenance system to define rules based on the equipment coding in order to supply default values for some of the optional fields if they are not populated by the import process. These setup applications include:

  • Condition-Based Maintenance Message Sequences (P1315).

  • Condition-Based Maintenance Message Rules (P1316).

  • Condition-Based Maintenance Alert Action Sequences (P1317).

  • Condition-Based Maintenance Alert Action Rules (P1318).