This is an old revision of the document!
We have introduced the following new features:
It is possible to assign requests to bases.
This feature only applies to operators that have more that one base. For the operators with one base only this functionality will not apply.
Bases can be defined in General Settings section.
Once the bases are added, it is possible to assign one to a user, Client or directly to the request.
Operator bases can be assigned as follow:
If the base is assigned to a Client, the trip requested by this particular Client will automatically be assigned to the Client's base.
Once this request is edited by a user with base assigned then this request will get assigned to the user base automatically.
It is also possible to assign or change original base, including base initially assigned to a Client, without having to assign a specific user.
The 'Requests/Quotes' list includes all the requests including the ones without bases assigned.
If you select a particular base in the operator selection dropdown (top-right corner of Leon), the Requests/Quotes list will only display the requests assigned to this particular base. See screenshot on the right.
Catering fee has been updated by an additional element called 'Min. block time'.
The additional elements that affect the Catering fee calculations are:
The example presented in the screenshot shows that if the 'Catering' minimum block time is set to 1h (as per above) and required ground time is more than 2h, Leon will calculate this as follows:
'Navigational fee' has been added to 'Airport fees.
It could be used to include the cost of Permits (overflight/landing), Slots etc.
It is calculated based on the number of departures and landings at an airport.
Example
In the screenshot on the right there is the following routing:
LTN-WAW-AMS-RKE-WAW-LTN
Considering that the 'Navigational fee' is set to €200 for each airport, the total will be calculated as per below: