To utilize the Wyvern integration with Avianis, first create dedicated Wyvern credentials for Avianis in Wyvern, then turn the Wyvern syncing on in Avianis.
This article covers:
Connecting the Integration
Wyvern Integration information
Crew Requirement Types and Wyvern Fields
For questions concerning Wyvern, please contact Wyvern Product Support at: 1-800-WINGMAN [946-4626] / support@wyvernltd.com
2. Enter the following information and Save
Username/password credentials from Wyvern. This user must be the API user setup in the Wyvern account.
Who should receive notifications of a Wyvern sync
What time each day you would like the integration to run (this is zulu)
Designate if flight crew information is sent based on their listed regulatory type. For example, if crew with the 135 regulatory designation on their personnel profile is required to sync select ‘Part 135’.
Set the applicable training item for proficiency check (293), instrument (297) check and line/sector (299) check. Helpful Hint: These should not be aircraft specific. (See Quick Start Guide: Crew Records for more on creating the programs and training items.)
3. Select the 'Aircraft Model Mapping' tab and select the Wyvern Model Type Code for each aircraft in Avianis.
4. Select the Personnel and enable each personnel you would like to sync to Wyvern. This must be Enabled for the manual sync to function.
To test the sync, access the personnel profile and do a manual sync by selecting the applicable system in the dropdown.
Refer to the detail table: Syncing Info to ARGUS and Wyvern
Wyvern will also sync the following information from a pilot's Personnel page:
From the Profile tab:
Homebase
DOB
From the Employment tab:
Employment status
Hire date
From the Crew Info tab:
Certificate information: number, type, and issue date
Medical certificate information: class and last completed
Aircraft type ratings
Several Wyvern fields are filled from a crew member's completed Crew Requirements. Wyvern identifies each one by the Requirement Type set on the requirement, not by its name. If a requirement does not have the correct Requirement Type, the matching Wyvern field is sent blank. In every case the most recently completed log for that Requirement Type is used.
| Crew Requirement Type | Wyvern field(s) | Notes |
|---|---|---|
| Medical (1st Class) | Medical Class (Class 1) and Medical Date | The most recent completed medical of either class is used. The Requirement Type determines the class sent to Wyvern. |
| Medical (2nd Class) | Medical Class (Class 2) and Medical Date | Same as above. |
| Line Check | Line Check Date and Line Check Base Month | Base Month is the three-letter month from the requirement's base month. |
| Instrument Check | Instrument Proficiency Check (IPC) Date and IPC Base Month | Base Month is the three-letter month from the requirement's base month. |
| Company Indoc | Indoctrination Date | |
| International Procedures | International Procedures Date | |
| Proficiency Check (Initial level) | Type Rating: Competency Check Date and Base Month | Sent per type rating. The requirement must be tied to that aircraft type rating. If no Initial-level log exists, the newest non-recurrent log is used. |
| Proficiency Check (Recurrent level) | Type Rating: Recurrent Training Date and Base Month | Sent per type rating. The requirement must be tied to that aircraft type rating. |
| Simulator Part 142 | Type Rating: Simulator Training Date, Full Motion Simulator, and Simulator Training Vendor | Sent per type rating. Full Motion Simulator is marked Yes when a log exists, and the vendor is the training organization on the log (“Unknown” if none is entered). |
Ref: I-W02