Enhancements to interfaces and integration

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

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

Mapping of values in OFP.xml file

The mapping of values in the FliteBrief OFP.xml file is now enhanced to make sure that Aviator correctly processes the OFP.xml file. The following steps define the workflow:
  1. The flight plan (in XML format) is converted into the ARINC 633 format with a human-readable OFP (in PDF format).
  2. The XML flight plan file and the OFP PDF file are used to create the ARINC 633 formatted EFF.
  3. The ARINC 633 formatted EFF file is processed to produce a validated XML file (with correctly mapped values).
  4. The validated XML file is processed and used by Aviator.

Integration with Jeppesen Operator

You can now integrate FliteBrief with Jeppesen Operator to send an updated PDF Briefing Pack from FliteBrief to Jeppesen Operator.

Integration with FlightAware FlightXML ADS-B data feed

The live location of in-flight aircraft in the Flight Following module of FliteBrief is now enhanced by the FlightAware FlightXML ADS-B data feed.

SFTP for certain third-party EFB applications

FliteBrief now provides SSH File Transfer Protocol (SFTP) services for certain third-party EFB applications. EFF packages are sent and received by using the SFTP service.