This article will cover:

  • The functionality of the maintenance integrations
  • How to setup the integration within the aircraft profile
  • How to test the integration



Avianis offers integrations with CAMP/Gulfstream CMP and Flightdocs. These integrations allow users to pull due items into Avianis and push current aircraft times to the various tracking systems. An automatic sync for aircraft times and inspection items between Avianis and the third party provider is conducted daily. This process can also be done manually, if needed, by the user. To push aircraft times and cycles the user would access the Maintenance > Integration page and to manually pull the current due items the user would access the Maintenance > Inspections page.

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. At this time they will provide a username and password to be inputted into Avianis within the MX Module on the aircraft profile page.

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

Gulfstream CMP - Contact the Service Desk at or 912-298-1280.

Flightdocs - While the login credentials utilized for this integration are the same ones used to access the Flightdocs system directly, it is necessary to confirm with the Flightdocs representative that the user has access to the aircraft within the third-party provider. If not, the user will be unable to successfully sync the two systems. Additionally, if the Avianis account is on a dedicated instance advise Flightdocs of the URL.

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



Access the aircraft profile for the tail number that will be utilizing the integration. Click the Maintenance Tab and select MX Integration.

Select the 3rd party system that will be use to track the aircraft.

Next, select the thresholds that will be considered as warning and critical based on the various frequencies. For example, if the warning value is set at 10 hours with a critical value at 5 hours and an inspection item is pulled in that is 7 hours from being due the item will show as a warning within the trip snapshot for operations.

Filters will need to be setup to limit the results that come back when a list of inspection items are pulled. In the example below, only items that are due within 1 month will pull back.

NOTE: The CAMP integration gives the user the ability to include tolerances when calculating the next due items. CAMP sends two different due dates to Avianis: one including tolerances and one excluding tolerances. The next due date of the items that are imported to Avianis will depend on the selection made here.

The user will then need to 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 LEGS is selected, the leg status must be set to verified within the trip in addition to the leg being logged for the flight time to be included in the accumulative time.

NOTE: If the integration is set to only send VERIFIED times, when reviewing the aircraft times within Maintenance > Integration the only times displayed will be from leg statues that reflect VERIFIED.

Lastly, once the the username and password provided by the tracking system have been entered click "Save". This username and password is separate from the login used to access Avianis and the Maintenance Tracking site. Once all steps are completed, the integration should resemble the below.

DELETE ----- Note: The current airframe 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 NOT receive any engine data.



To confirm that the integration is setup correctly the user will need to access the Maintenance > Inspections page. All tail numbers with active maintenance integrations should appear in the "Get Due List" drop down.

The integration can also be tested by the manual push of times from Avianis to the third-party maintenance system. By accessing the Maintenance > Integrations page, all tail numbers with active maintenance integrations should appear as an option from within the drop down.

If the integration is not working properly, below are a few ways the user can troubleshot to resolve the issue.

  1. Confirm that the following items match identically - including all spaces, case sensitivity and special characters - between Avianis and the third-party system: tail number, serial number for the airframe, engines and APU (Only when the APU Component is entered and the times/cycles are being tracked within Avianis), and sequence numbers on engines.
  2. Make sure the username and password being utilized are correct and active.
  3. Verify that the thresholds and parameters are all entered within the integration on the aircraft profile. NOTE: These values need to be in whole numbers, decimals are not valid.
  4. Confirm that the aircraft is active and turned on to sync with Avianis within the third-party maintenance tracking software.

Ref: I-S02

Did this answer your question?