Slot process & Prior Permission Request for FBO

PPR (Prior Permission Request) and slot assignment process launch:

1. The customer will first configure his flight and validate the ETD / ETA airports. An indication if “Slot Required” or “Slot: Not Required” for each airport will appear.

2. The slot process opening is pending on the FBO selection through a ground handling request. The customer has to submit a “Mandatory Ground Handling” request to the Vendor. The request submission opens the flight leg schedule to the FBO and he is “invited” to collaborate into the customer’s project. The PPR (Prior Permission Request) document appears downloadable in PDF format (1).

3. It is recommended to use the Chat channel from the request for quotation panel (2) & (3), in order to validate a suitable slot proposal. The FBO could make suggestions to the Aircraft Operator, in order to update his time schedule prior to the order submission. In case of slot unavailability, the Vendor will simply decline the handling request.

The slot channel will be opened only after customer order submission to the chosen FBO (4). Send your quotation to the customer to receive the order. The slot channel serves to identify the FBO handling the slot treatment and a parallel slot request could not be passed to another FBO in the same airport. From now on, the flight schedule and the slot status management are synchronized.

Slot assignment:

The FBO will send back a Slot assignment that could have the following status:

1. Doesn’t require any action as the status is already “Approved”, that means fully compliant with the requested Date slot Start – End UTC.

2. Comes with a status “Proposal”, if there is a difference between the slot Start-End UTC that has been requested and the submitted slot. The “SLOT PROPOSAL” changes the flight timeline (5), but not the customer flight leg schedule details (6). After customer acceptance, the Slot status changes to “Approved” and the flight schedule is automatically updated with the new slot Date Start-End UTC. (7), (8)

3. Comes with a status “Proposal”, in case there is a time difference between the initial request and the slot assignment. The customer could DECLINE the proposal by rescheduling the flight. The slot status will go back to “Required” and new slot assignment must be made.

Note: slot availability where airports connected to MyFlight Connect.

Slot schedule change impacts on order management:

1. Flight schedule update following new slot proposal by FBO: there is no impact on the already passed orders if new FBO slot proposal has been accepted. The flight schedule will be updated without any consequence after the new proposal acceptance by the Aircraft Operator. An email “New slot proposal” will be automatically distributed to notify and follow the change.

The slot status workflow for a) could be:

FBO: “SLOT PROPOSAL” => FBO: new “SLOT PROPOSAL” => Customer: “SLOT APPROVED”

Customer: “SLOT APPROVED” => FBO: new “SLOT PROPOSAL” => Customer: “SLOT APPROVED”

FBO: “SLOT APPROVED” => FBO: new “SLOT PROPOSAL” => Customer: “SLOT APPROVED”

1. Slot tart-End UTC hour change by Aircraft Operator without flight date shift: the orders and requests for quotation (RFQ) will be maintained the slot status will go back to “SLOT REQUIRED” and the previously assigned slot will be cancelled (Cancelled slots dashboard). Notification email is sent to FBO to follow on slot change request.

2. Slot date start-End UTC change by Aircraft Operator: in case of a date change, the RFQ will be maintained. The already passed orders without payment and with different status than “delivered” will be automatically cancelled. New orders have to be raised for the rescheduled flight. For already paid and delivered orders, a refund could be requested through the CLAIM PROCESS during the 7 days following the payment. The slot status will go back to “SLOT: REQUIRED” and the previously assigned slot will be cancelled (Cancelled slots dashboard). Notification email is sent to FBO to follow on slot change request.

The slot workflow for b) and c) could be:

Customer: “SLOT APPROVED” => Customer “SLOT REQUIRED”

FBO: “SLOT PROPOSAL” => Customer “SLOT REQUIRED”

Customer: “SLOT REQUIRED” => Customer “SLOT REQUIRED”

SLOT management dashboards

The slot consolidation is split in two tables “ACTIVE SLOTS” and “CANCELLED SLOTS”

1. ACTIVE SLOTS table tracks all the slots with status REQUIRED, PROPOSAL and APPROVED. The flight could be accessed through the ACTIONS button. The slot number is assigned by the FBO.

2. CANCELLED SLOTS table tracks all the slots that have been cancelled following a flight cancellation or declined slot proposal. Only the slots with assigned slot numbers are tracked as cancelled. If slot number has not been assigned, only status change will be applied in the Active slots table.