Voyage Events interface

The Voyage Events interface has the following enhancements.

More information in Voyage Download event

The documents included in the payload of the Voyage Download event now contain more information.

The information is extracted, converted to JSON, and then added as one or more fileDetails elements to the payload of the Voyage Download event.

An example of the information in the document is as follows:

{
            "@title": "Flight plan",
            "Topic": {"@name": "FlightPlan/Operational"},
            "Document": [
                    {
                              "@authorProfile": "dispatcher",
                              "@captainOnly": "0",
                              "@mandatory": "0",
                              "@originalDateTime": "2020-12-16T05:45:27.148310+00:00",
                              "@priority": "0",
                              "@status": "None",
                              "@title": "OFP 1234 DEM123",
                              "@transferPending": "0",
                              "@updateDateTime": "2020-12-16T05:45:27.148310+00:00",
                              "@id": "file10",
                              "@file": "OFP_17019120.xml",
                              "@type": "text/xml",
                              "Topic": {"@name": "FlightPlan/Operational"}
                     },

Taxi and Trip Fuel in Fuel Order Voyage Event

The FliteBrief interface is now enhanced to extract Taxi and Trip fuel values from received fuel orders. The fuelOrder element receives and displays a combination of the following values:

Taxi and Trip values
No Taxi or Trip values
Taxi value only
Trip value only

Note: The Taxi and Trip fields aren't mandatory.

An example of the taxi and trip values in the fuelOrder element is as follows:

{
        "sectors": [
                {
                        "voyageId": 896637,
                        "sectorId": 3143867,
                        "fuelOrder": {
                                "amount": 10000,
                                "reason": "Want more to be safe",
                                "taxi": 250,
                                "trip": 8000
                        }
                }
        ]
}

FliteBrief notifies users of these values by using the Fuel Order Voyage Event API. An example of the taxi and trip values in the eventData element is as follows:

{
        "fileData": {
                "format": 2.1,
                "fileName": "200759-2489749-sector-sectorfuel_order-2021-04-15T09:50:47+0000.json",
                "data": {
                        "userName": "mediademon",
                        "eventType": "sector - sector fuel_order",
                        "sectorId": 2489749,
                        "voyageId": 200759,
                        "timestamp": "2021-04-15T09:50:47+0000",
                        "planNo": 6996,
                        "eventData": {
                                "amount": 9001,
                                "reason": "Testing Fuel Order",
                                "taxi": 250,
                                "trip": 6000
                        }
                }
        },
        "flight": {
                "number": "BYT005",
                "registration": "GRHTC",
                "dep": "MMTJ",
                "dest": "MMMX",
                "std": "2021-04-15T08:10:00+0000",
                "sta": "2021-04-15T10:53:00+0000",
                "etd": "2021-04-15T08:10:00+0000",
                "eta": "2021-04-15T10:53:00+0000"
        }
}

The Taxi and Trip values are:

Available in the Flight Data Summary screen of FliteBrief
Included in Fuel Order notification emails