Avianis offers integrations with CAMP/AvTrak/Gulfstream CMP and Flightdocs. These integrations allow users to pull due items into Avianis and push current aircraft times to the various tracking systems. Pushing the times from Avianis to the 3rd party maintenance integration is an automatic sync each night. The times can also be pushed manually in Maintenance > Integration. Once the integration is connected, the inspections pull from the tracking software to Avianis daily. If needed, the user can pull manually in between. 

Prerequisite: Before the aircraft can be configured in Avianis, reach out to the provider (see contact information below) and have them turn on the integration for the operation and the specific aircraft. They will provide a username and password. The credentials are to be inputted when setting up the Mx Module in Avianis.

Note: If the Avianis account is on a dedicated instance, advise Flightdocs the URL. 

CAMP/AvTrak - Ellen Lepore or Mateen Abedi (877-411-2267 ext. 2211). Their email is support@campsystems.com

Gulfstream CMP - Contact the Service Desk at mycmp.support@campsystems.com

Flightdocs - The user doesn't need to reach out to a representative. The required credentials are the same used to log into Flightdocs website. The user does need to confirm their Flightdocs login has access to the aircraft on the Flightdocs side if entering the credentials on the aircraft on the Avianis side.  

Once the integration is enabled with each of the providers and they have provided you with a username and password you can setup the integrations within Avianis.

  1. Access the aircraft profile. Access Maintenance > Mx Integration 

2. Select the 3rd party system you use to track that aircraft
   
3. Select the thresholds you want to consider warning and critical based on the various frequencies. For example, if you set the warning value at 10 hours and critical at 5 and you pull back an inspection item that is 7 hours from being due and it will show as a warning in the trip snapshot for operations.
   
4. Setup filters to limit the results that come back when you pull a list of inspection items. In the example below, only items that are due within 1 Month will pull back.

5. Set whether times should be sent in hours or hobbs and if it's dependent on leg status. If ALL is selected, any leg that has been logged will be included in the total time. If VERIFIED is selected, the leg status must be set to verified for the flight time to be included in the accumulative time.

Note: If VERIFIED is set, when reviewing the total times in Maintenance > Integrations, the time will only be included in the values displaying at the top if the leg statuses are set to verified.

6. Enter the username and password provided to you by the tracking system and click "Save" (this is a separate username and password than what you use to login into the Mx Tracking site and Avianis). 

Here is an example of the setup:

Note: The current air frame and engine times on an aircraft will only sync over to the various tracking systems if they have changed since the last time they were pushed over. Additionally, engine serial numbers do not match, CMP does not provide an error. It will appear to be syncing, but they will receive any engine data. 

Test the Integration
To confirm the integration is setup properly, go to Maintenance > Inspections. Enter a tail number(s) and click Get Due List.

Make sure additional searches are not entered limiting the results of the inspection     items. Confirm active is the only box selected.            


If the integration is not working properly, here are some items to review:

1.) Do the following items match identically (3rd party mx tracking = Avianis)
         Tail #
         Serial # on air frame, engines and APU (APU if entered, not required)
         Sequence # on engines
2.) Is the username and password correct?
3.) Are the thresholds and parameters all entered in the Avianis Mx Module Setup? Note: they must be whole numbers, no decimal values.
4.) Is the aircraft active in the 3rd party mx software and set to be on the integration? 

Did this answer your question?