Enhancements to integration with other applications

Several enhancements have been made to the way certain features of FliteBrief integrate with other applications.

Note: For more information about application integrations, contact your FliteBrief account representative.

Aviator integration

You can now view Allowable Gross Takeoff Weight (AGTOW) and Runway-limited Takeoff Weight (RTOW) values that are contained in the Aviator OFP.xml file.

Some airlines need AGTOW and RTOW values within their fuel plans. These values are included in the human-readable OFP file and are provided by the fuel plan provider to FliteBrief. FliteBriefextracts the AGTOW and RTOW values from the human-readable OFP file and uses the A633 extension to include these values in the OFP.xmlfile. You can then view the AGTOW and RTOW values in Aviator.

Note: The original OFP provided by the fuel plan provider is saved for audit purposes.

IBM MQ integration - Aviator journey log

When an Aviator app user closes a flight, an EFF closure package is generated. This package contains any relevant journey log information entered by users. In the previous version, FliteBrief extracted the journey log information from the EFF closure file and generated an AIMS-compatible .csv file. The .csv file was sent to a user-defined secure File Transfer Protocol (SFTP) endpoint.
The integration is now enhanced to allow FliteBrief to send the journey log .csv file to an IBM (message queue) MQ queue. The IBM MQ queue is configured by an operator setting.

IBM MQ integration - OOOI information

In the previous version, pilots manually entered the OUT OFF ON IN (OOOI) information provided by the aircraft ACARS message into FliteBrief.
FliteBrief now automatically processes OOOI information contained in ACARS messages. FliteBrief accepts ACARS messages through an IBM MQ queue and the required information is attached to the relevant flight sector. The IBM MQ queue is configured by an operator setting.

Operator integration - sector attachments

It's important that some dynamic document types, such as GENDEC or Crew Itineraries, aren't duplicated and only the latest version is available in FliteBrief.

FliteBrief now replaces existing documents with the latest version of Operator-generated documents (same or different filename).

FliteBrief also replaces existing sector attachments with the latest attachments (same filename).

Note: Latest documents and attachments are included in the EFF package created for Aviator.

Operator integration - STD/STA and ETD/ETA

When the FliteBrief API sends the flight schedule to FliteBrief, the values of the STD/STA field are no longer overwritten by the values of the ETD/ETA field. FliteBrief makes sure that:
  • When an OFP is received, only the ETD/ETA fields for a scheduled flight are updated in the Dispatch module.
  • When an update for a scheduled flight is received from Operator, the STD/STA fields are updated.