This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
leon:integrations [2021/11/30 12:41] rafal [FlightDocs] |
leon:integrations [2021/12/20 15:26] rafal [ARINCDirect] |
||
---|---|---|---|
Line 9: | Line 9: | ||
* **AeroCRS** - flight reservation and operation software | * **AeroCRS** - flight reservation and operation software | ||
* **Airport Charges** - airport charges library | * **Airport Charges** - airport charges library | ||
+ | * **ARINCDirect** - flight planning software | ||
* **Avinode** - charter sales management system | * **Avinode** - charter sales management system | ||
* **CAMP** - maintenance software | * **CAMP** - maintenance software | ||
Line 109: | Line 110: | ||
Once the integration is active you will see additional ' | Once the integration is active you will see additional ' | ||
--------------- | --------------- | ||
+ | |||
+ | ===== ARINCDirect ===== | ||
+ | |||
+ | **ARINCDirect** is the world leader in business aviation solutions, including flight planning, weather, communications, | ||
+ | |||
+ | More information about ARINCDirect can be found [[https:// | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | **How to integrate** | ||
+ | |||
+ | In order to integrate with ARINCDirect, | ||
+ | |||
+ | Once the integration is activated, the ARINCDirect export option will appear in the ' | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | **How it works** | ||
+ | |||
+ | The integration allows sending planned flights to ARINCdirect. | ||
+ | |||
+ | After clicking on the ' | ||
+ | |||
+ | It is possible to only send the flights with the aircraft registration assigned and without the Journey Log filled in (including partial Journey Logs). | ||
+ | |||
+ | Currently, it is only possible to **send one flight ar a time**. Leon will not allow sending multiple flights at one time. | ||
+ | |||
+ | Flights have to be **sent manually** from the OPS section. Currently, no automation is available. | ||
+ | |||
+ | |||
+ | ----------- | ||
===== Avinode ===== | ===== Avinode ===== | ||
Line 139: | Line 171: | ||
==== Export ==== | ==== Export ==== | ||
- | First step the export aircraft availability is integrating Leon with Avinode. This process is explained [[leon: | + | In order to allow buyers to search available aircraft for requested trips, Avinode requires a precise aircraft schedule from aircraft operators. |
+ | |||
+ | Leon allows automatic schedule export to Avinode for selected aircraft. All aircraft for which the schedule is sent automatically to Avinode should be configured in Avinode for receiving data from Leon. | ||
+ | |||
+ | The first step in the export aircraft availability is integrating Leon with Avinode. This process is explained [[leon: | ||
If you want to receive messages after each export of flights to Avinode, type your code or first letters of your name in the field **Recipients**. | If you want to receive messages after each export of flights to Avinode, type your code or first letters of your name in the field **Recipients**. | ||
Line 145: | Line 181: | ||
Once all has been set up tick aircraft of which flights you want to be exported. | Once all has been set up tick aircraft of which flights you want to be exported. | ||
- | Apart from **automatic** export to Avinode, in this section you can also send flights **manually** by clicking on ' | ||
+ | |||
+ | < | ||
+ | <span style=" | ||
+ | </ | ||
+ | |||
+ | Before sending the data to Avinode there are steps required to be done: | ||
+ | |||
+ | * The aircraft needs to be active in Avinode Marketplace with the status: Fully Active. | ||
+ | * An API connection needs to be set up in the Avinode Marketplace for the company marketing the aircraft in the Avinode Marketplace. This company is usually the operator, but it can also be a different company (i.e. not the operator holding the AOC for the aircraft) marketing the aircraft. API Connections can only be set up by Avinode staff and is usually done by product specialists (support@avinode.com) upon request from the company marketing the aircraft. | ||
+ | * The aircraft must be configured in the Avinode Marketplace to receive automatic schedule updates (i.e. Aircraft Schedule Update Type = Integrated). This can only be configured by Avinode staff and is usually done by our product specialists (support@avinode.com). | ||
+ | * The company marketing the aircraft should have Activity Type Mappings configured in their Avinode Marketplace account. More information below | ||
< | < | ||
- | <span style=" | + | <span style=" |
</ | </ | ||
+ | Leon sends a schedule for all configured aircraft **every 15 minutes**. It is also possible to make manual exports from the Avinode Add-on control panel. | ||
- | Avinode will get schedule | + | < |
+ | <span style=" | ||
+ | </ | ||
+ | |||
+ | |||
+ | Leon sends all activities | ||
+ | |||
+ | The schedule for each aircraft has a form of a continuous timeline. Spaces between activities in the exported period are filled with special ONGROUND activities. | ||
+ | |||
+ | < | ||
+ | <span style=" | ||
+ | </ | ||
+ | |||
+ | |||
+ | Aircraft activities prepared to send are mapped on codes corresponding to available Avinode activity types. However, operator doesn’t have to configure the Avinode side with the same corresponding codes (see the section | ||
+ | |||
+ | **There | ||
+ | |||
+ | * **FLIGHT** – every flight with PAX | ||
+ | * **EMPTY** – every ferry flight and opportunity flight | ||
+ | * **MAINT** – every reservation and maintenance is mapped to this code | ||
+ | * **OPTION** – every flight option (if the export is configured to send options) | ||
+ | * **ONGROUND** – every space between the above activities is filled with this activity (this include time before first activity and after the last activity if reposition to homebase after hours is configured)) | ||
+ | |||
+ | < | ||
+ | <span style=" | ||
+ | </ | ||
+ | |||
+ | |||
+ | Activities exported from Leon can be mapped to one of Avinode' | ||
+ | |||
+ | __**Empty Leg Availability**__ | ||
+ | |||
+ | All activities mapped to this type will be considered empty leg availability and posted in the Empty Legs list in the Avinode System. | ||
+ | |||
+ | __**Ferry Availability**__ | ||
+ | |||
+ | Activities mapped to this type will be considered available. This option will not post an Empty Leg as the aircraft is assumed available until occupied for the " | ||
+ | |||
+ | __**Flight Occupied**__ | ||
+ | |||
+ | Aircraft will be considered occupied and will not show when searches are performed in the Avinode System. This option should be used for all flight-related occupancy e.g. 135 trips, 91 trips, etc. | ||
+ | |||
+ | __**Occupied**__ | ||
+ | |||
+ | Aircraft will be considered occupied and will not show when searches are performed in the Avinode System. This option should be used for all non-flight occupancy e.g Maintenance. | ||
+ | |||
+ | __**Onground Availability**__ | ||
+ | |||
+ | Aircraft will be considered available on-ground. This option can be used to indicate transient (away from home base) availability. This will price the aircraft from the indicated airport, rather than the home base. | ||
+ | |||
+ | __**Option Availability**__ | ||
+ | |||
+ | This is an “information only” type. Activities mapped to this type will be shown in the Schedule for the aircraft, but do in no way affect the schedule when searches are performed in the Avinode System as the aircraft is still considered available. This can be used for non-confirmed trips. | ||
[{{ : | [{{ : | ||
- | - The aircraft needs to be active in Avinode | + | **Default |
- | | + | |
- | - The aircraft | + | |
- | - The company marketing the aircraft | + | * **EMPTY** – Empty Leg Availability |
+ | * **MAINT** – Occupied | ||
+ | * **OPTION** – Option Availability | ||
+ | * **ONGROUND** – Onground Availability | ||
+ | |||
+ | Operators can manually change mapping settings | ||
+ | |||
+ | < | ||
+ | <span style=" | ||
+ | </ | ||
+ | |||
+ | __**Send Options**__ | ||
+ | |||
+ | If this setting | ||
+ | |||
+ | __**Send Opportunities**__ | ||
+ | |||
+ | If this setting is configured Leon also exports flights with opportunity status. Opportunities are sent to Avinode | ||
+ | |||
+ | __**Continuous availability | ||
+ | |||
+ | This option changes normal schedule export and exports only one activity for each aircraft indicating ONGROUND status of aircraft in it’s homebase airport. This artificial activity is an only day long and the Avinode | ||
+ | Note that Leon in that mode doesn’t send any real activity for all aircraft. | ||
+ | |||
+ | __**Auto reposition availability | ||
+ | |||
+ | It is possible | ||
+ | |||
+ | This option is disabled when set to 0. | ||
+ | |||
+ | | ||
==== Import ==== | ==== Import ==== |