Enhancements to integration with other applications

Jeppesen has enhanced FliteBrief integration with other applications.

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

FliteFolder mobile app

The following fields are now available within the Departure module of FliteFolder mobile app:
  • Nature of Flight: Select from a list of preconfigured codes that denote the nature of the flight.
    Note: You can configure the codes within the Codes Admin module of FliteBrief.
  • Security Check: Enter the time and date, or tap Now to automatically enter the current date and time.
  • Thrust Setting: Select from a list of preconfigured thrust values for an organization's aircraft.

During transmission of flight data, values entered for any of the previous fields are shown within the Departure tab of the Flight Data Summary page in FliteBrief.

The following fields are now available within the Arrival module of FliteFolder mobile app now accept numeric values:
  • Go-around
  • Touch and Go
During transmission of flight data, values entered for any of the previous fields are shown within the Arrival tab of the Flight Data Summary page in FliteBrief.

Osprey Flight Solutions (OFS) integration

FliteBrief can now integrate with OFS to receive and forward ATC messages. ATC messages are sent to the AFTN address of FliteBrief. Upon receipt of the ATC message, FliteBrief identifies the message type and the Osprey customer, and then forwards the message to the OFS web service.

FliteBrief accepts the following message types:
  • FPL: Filed Flight Plan message
  • DLA: Delay message
  • CNL: Flight Plan Cancellation message
  • CHG: Modification message
  • DEP: Departure message
  • ARR: Arrival message

DP2 X12 ARINC633-2 OFP parser

The X12 ARINC633-2 OFP parser is now integrated with the FliteBrief JSI workflow.

This integration makes sure that:
  • Upon receipt of a DP002/X12 message, FliteBrief automatically generates the ARINC633-2 OFP.xml file and then associates it with the correct flight sector.
  • BT001 messages are removed from the processing of flights.

Enhanced integration with PPS flight planning

FliteBrief now retrieves more documents from PPS flight planning software. Documents are in .PDF format and include GENDEC, NOTOC, and so on.
Note: This retrieval is an automatic process and the documents are retrieved regardless of any naming convention.
FliteBrief retrieves documents from PPS flight planning software into the sector-attachments area of Flight Data Summary. FliteBrief uploads the documents to the sector attachments area of the FliteFolder mobile app.

Enhanced AIMS integration

In version 1.26, FliteBrief integrates with AIMS only for certain users who use the system for their schedule and crew information.

In version 1.27, the AIMS interface supports multiple customers.

DP002 - enroute alternates from SupportDocs element

In version 1.26, FliteBrief extracts information about dispatcher-defined enroute alternates from the <freetalk> element of DP002 messages.

In version 1.27, FliteBrief also extracts this information from the <supportDocs docName="PlanningInfo"> element of DP002 messages.