User guide Leon Software integration with MyFlight Connect
Leon Software integration with MyFlight Connect
User guide
CONTENT:
I. System security and setting requirements
II. Status correspondence and synchronization launch with MyFlight Connect
III. Ground handling order workflow
IV. Slot management workflow
V. Previous – Next flight synchronisation
VI. Synchronized flight changes
VII. Synchronized flight cancellation
VIII. Flight change use cases requiring new flight creation
IX. Synchronized flight without synchronized Handling orders
X. Frequently asked questions
MyFlight Connect integration is a complementary and streamlined extension to Leon Software, enabling flight schedule with order generation for Handlers and change management through instantaneous data synchronization. MyFlight Connect workflows, designed to orchestrate multiple providers around a flight, manage the change impact.
System security and initial settings
1.1: OAuth2 connection: API data transmission with Leon Software is secured by OAuth2 connection, established for every Aircraft Operator. It must be activated from the operator’s MyFlight Connect main organization account. The connection:
Must be activated by authorized Leon Admin User – Leon emails a connection set up confirmation.
Must be activated by MyFlight Connect Administrator (activation checkbox indicator).
Connection failure is indicated on the Organization-External API page, in case of system problem.
Leon Software sends an email message to warn the Admin user about a connection failure.
The token authentication renewal process with Leon is permanent. Connection setting action could be required only in case of unexpected failure.
2.1: MyFlight Connect initial account settings
To enable flight and order synchronization, the following settings must be implemented in MyFlight Connect:
The aircraft fleet must be created under each Operator’s organization before starting the flight synchronization (subsidiary & AOC). Matching parameters: Aircraft registration + ICAO type, (default parameter Call Sign+ICAO type).
Main organization must be assigned to all subsidiaries synchronizing with Leon Software.
/!\ There is only one OAuth2 authorization per Aircarft Operator provided by Leon, MyFlight Connect assigns the flight under the right subsidiary owning the aircraft registration.
The Operations contact (under Organization/Main information) must have full user rights on flight and order management: VIEW/CREATE/MODIFY/DELETE
Status correspondence and synchronization launch with MyFlight Connect
2.1: Status correspondence: Leon Flight Support API – OPS Checklist – MyFlight Connect.
The Leon API structure offers 7 status designations, 5 of them are used by MyFlight Connect to match with the workflows (1 to 5 below).
/!\ the API Service and OPS Checklist status equivalence is entirely managed by Leon, 3rd party integrations could only settle the API choices.
2.2: Synchronization launch with MyFlight Connect
MyFlight Connect module (1) is available in OPS checklist +ADD ITEM menu. It could be permanently added to the OPS deck.
MyFlight Connect Services checklist (2) is the channel to initiate flight and handling order synchronization. A flight with order is instantaneously created in MyFlight Connect (*when the selected Handler is available in MyFlight Connect).
“via MyFlight Connect” (3) indication appears under each synchronized service.
The eligible Handlers (4) could be referenced from the Leon Handlers’ Directory.
Flight synchronization indicators (5):
The flight synchronization is tracked by MyFlight Connect {EDIT} service, returning the status:
REQUESTED for: flight synchronized in MyFlight Connect.
The Note field provides in addition:
Flight update confirmation (date UTC when applied to MyFlight Connect).
MyFlight Connect url trip link for quick access (copy/paste in the browser)
Warnings in some specific cases
REJECTED for: flight not synchronized in MyFlight Connect.
The NOTE field returns the reason.
The flight has not been created in MyFlight Connect, because:
The aircraft does not exist under MyFlight Connect organization
The Operations contact user doesn’t have sufficient User rights
An airport doesn’t match (technical use case)
The flight has been cancelled in MyFlight Connect.
Active url link launches the MyFlight Connect order dashboard from Leon OPS checklist.
Ground handling order workflow
3.1: Possible order workflows Leon - MyFlight Connect
Ground Handling Order workflow (1) launches a synchronization on flight with services submission and updates, sends back the Handler confirmation to Leon. Only few specific actions remain locally managed in MyFlight Connect, when requested by the Handler (like payment guarantee, claim for refund).
/!\ To generate a Ground Handling order, the Handler must exist as organization in MyFlight Connect. The Handler match is made on the name, location and email address.
Service list: currently assigned to MyFlight Connect checklist module.
Specific service order (2): it remains possible to manage specific service orders, under the same synchronized with Leon flight, directly in MyFlight Connect, useful when the Service Provider is different from the selected in Leon Handler. All order management rules with dependencies on flight will apply to those orders (flight change and cancellation).
3.2: Ground handling order workflow status correspondence with Leon
HANDLING_ADEP/ADES services support the Handler match and order synchronisation with MyFlight Connect.
Main synchronization state indicators:
REQUESTED (PENDING) : indicates that GH Order has been created and updated in MyFlight Connect
NOT APPLICABLE (NOT REQUIRED): indicates that GH Order has not been created in MyFlight Connect, the Handler has not been matched
REJECTED (CANCELLED): the order has been cancelled, no longer synchronized
Note: returns the Order # and status in MyFlight Connect, plus warnings
All other services, checked with HANDLING_ADEP and HANDLING_ADES, are submitted with the Handling order and synchronize with the same workflow (*except SLOT service).
3.3: Ground handling order content
When Ground handling order is created through HANDLING_ADEP & HANDLING_ADES service selection, all other services under the same airport enter as quote lines in the same Order created with the same Handler.
The Ground Handling order is created “On quote”, composed of service quote lines at zero price value, waiting for Seller completion.
The service checklist note field is a transmission channel to the order for details.
3.4: Service change management
For Order status: Awaiting quote
MyFlight Connect order is still modifiable while in Awaiting quote state. If the operator modifies the service checklist, the change will be applied to the GH request:
New services added – returned status REQUESTED
Unchecked services - deleted quote lines from the original order
Order notes amended - returned status REQUESTED
/!\ If the Handling order has been Acknowledged in MyFlight Connect (returned Leon status = CONFIRMED), the initial confirmation will be cancelled, back to status REQUESTED if one of the 3 modification cases occurs.
For Order status: Awaiting customer confirmation, Order in progress, Delivered
The original order cannot be any longer amended from Leon:
New added services cannot be synchronized – returned status NOT APPLICABLE
Unchecked services cannot be deleted from the original order – returned status REJECTED (as unchecked)
Order notes cannot be amended – not applied to the original order
Synchronized Order cancellation
The order could be cancelled from OPS checklist - MyFlight Connect services module by:
Unchecking all services for one airport, returned status REJECTED, flight maintained.
Unchecking all services for the two airports, returned status REJECTED, flight cancelled.
Submitting newly configured service request will create a new synced GH order.
/!\ The order cannot be cancelled in the following cases: 1) has the status DELIVERED; 2) has payment status SUCCEEDED (a refund must be claimed in MyFlight Connect).
Slot management workflow
The slot workflow is launched by submitting SLOT_ADEP / SLOT_ADES with the Ground Handling order and slot service could be only assigned to the chosen Handler.
Leon status indicators returned from MyFlight Connect:
NOT APPLICABLE: the slot service has not been synchronized (not included in the order)
NOT APPLICABLE: Slot Not Required for airport without slot requirement in MyFlight Connect (from database). If slot obligation is temporarily settled, the Handler could still launch the process by submitting slot confirmation.
REQUESTED: Slot service workflow has been synchronized. The note field remains empty with the initial submission status.
REQUESTED: Slot Proposal has been submitted by the Handler in MyFlight Connect, the start at time UTC doesn’t match the flight request. The Note field returns the slot details. The Operator can accept the proposal by simply updating the arrival or departure UTC time (from Leon or in MyFlight Connect).
CONFIRMED: Slot Approved in MyFlight Connect
REJECTED: Slot cancellation, service unchecked from Leon deck.
Note: Slot #, Provider, time, status from MyFlight Connect
/!\ Leon Front interface needs some time to fetch the incoming updates. After submission, click out the flight and back in to refresh the displayed status with notes.
Previous – Next flight synchronization
MyFlight Connect is integrated with previous / next flight mapping functionality and the connecting movement could be automatically matched based on time and airport continuity for a given aircraft.
The flight information is synchronized to MyFlight Connect through the main flight, even without submitting it to MyFlight Connect.
To become visible for MyFlight Connect, the correspondent previous-next flight must have a CONFIRMED status in Leon.
Synchronized flight changes
The flight changes in Leon are simultaneously applied to MyFlight Connect.
All possible from Leon change use cases are managed.
The EDIT TRIP functionality sets date UTC time (1), airports (2), PAX & CREW (3) and aircraft (6) changes.
The Flight type (4) and mission (5) are received from OPS checklist – TRIP tab.
/!\ The “ferry” checkbox is a Leon Front end functionality to empty the PAX number field and does not send a ferry flight confirmation to MyFlight Connect.
/!\ Only flights in the future could be rescheduled in MyFlight Connect
MyFlight Connect handles the trip management use cases on orders. Hereunder a guide link on managed order workflow:
In a nutshell:
Only future flights could be updated (arrival date UTC is a future event).
PAX, Crew, flight type or mission change: doesn’t cancel service requests or orders
UTC time change: doesn’t cancel service requests or orders
Flight date change:
cancels only committed orders “Order in progress”, not delivered and not paid.
reconducts requests with status “Awaiting quote” or “Awaiting Customer confirmation” as not committed yet and modifiable by the Service Provider (*acknowledgement recalled).
If the Order status is “Delivered”, cannot be cancelled
If the Order payment status is “Succeeded” or “claimed”, cannot be cancelled
Synchronized flight Cancellation
Flight cancellation automatically sends MyFlight Connect flight and related orders to cancellation. The returned status to Leon is REJECTED (CANCELLED) for flight and services.
To cancel a flight from Leon OPS checklist:
Uncheck all services ADEP and ADES from MyFlight Connect checklist and submit
Cancel the flight from Leon OPS checklist “DELETE FLIGHT”
/!\ MyFlight Connect service DELETE icon in OPS checklist doesn’t cancel the flight, the synchronization doesn’t stop.
Flight change use cases requiring new flight creation
All flight parameters remain modifiable from Leon OPS checklist at any time, the main purpose of use being the change management through emailing. All functional use cases are managed to secure continuity and robust data synchronization with MyFlight Connect.
There are 3 MyFlight Connect use cases that automatically cancel the flight and related orders, because the change requires new flight creation. A simple service checklist submission launches again a new flight with the same Leon flightNid and the order synchronization.
This logic is compliant with Leon OPS checklist, suspending status to “?” (question mark) requiring action.
The change use cases listed below cancel the flight with orders, all OPS checklist status become REJECTED (CANCELLED) and the reason is sent under MyFlight Connect Note field:
Aircraft change: the aircraft is a sizing argument for the orders and all necessary data transmitted to Providers.
Handler change when orders engaged: when a request is submitted from Leon, the Handler receiving the order is assigned to the flight event and cannot be replaced. This enables the request management without leaving Leon.
Airport change where orders engaged: once a Provider invited to collaborate into a flight, it remains shared for all changes, even though orders could be cancelled. The flight recreation allows to cut the collaborative space with the former Provider.
The initial flight is not cancelled if:
ADES airport changes, without order engaged – Leon automatically applies REJECTED and unchecks the service list for ADES (Handler field is empty).
ADEP airport changes, without order engaged – Leon applies REJECTED to both ADEP, ADES and unchecks the service list for ADEP (Handler field empty).
Synchronized flight without synchronized Handling orders
Leon OPS checklist communicates with selected Handlers receiving the Handling request. The flight synchronization remains possible and independent from the Handler, in case the Provider doesn’t exist in MyFlight Connect, doesn’t match. This capability serves the cases where other orders still need to be managed around a synchronized flight (direct hangar rental, fuel etc).
The returned status in case of Handler not matched will be NOT APPLICABLE for all selected services. Then manual service status update can be applied on still synchronized flight schedule transmitted to the Provider.
The order synchronization could be launched AFTER the flight creation, by assigning a Handler to HANDLING_ADEP / HANDING_ADES.
Frequently asked questions
/!\ Usually, the warning “Integration with MyFlight Connect is not active” shows up in Leon when the system authentication is not set up. If there is no system response when submitting MyFlight Connect service checklist, the system connection must be checked.
/!\ Leon automatically applies “?” or “REJECTED” status to indicate that action is required when flight parameters or Handler are modified.
/!\ The Flight schedule is updated only one way, from Leon Software into MyFlight Connect. The opposite flow is not allowed.
/!\ Flight data could be adjusted directly into MyFlight Connect by the operator, but the next coming update from Leon will override the update.
/!\ In case of synchronization problem, MyFlight Connect will go back to fetch missed data when the connection is working again. However, all locally made updates on Flight (date, UTC time, airports, Pax, Crew, Flight type and mission etc) will be replaced by Leon’s data. The flight data between both systems will be aligned again.
/!\ Only flights in the future could be rescheduled in MyFlight Connect