Maintenance Tracking: Use
Once a maintenance tracking partner is connected to Avianis, data push and pulls. This guide outlines:
how to manage inspection items;
how to override inspection items; and
how exclude items from pulling into Avianis
See Related Articles:
MANAGE INSPECTION ITEMS
Go to Maintenance > Inspections to view inspection items pulled into Avianis from the connected maintenance tracking partner. Inspection items are to be managed in the tracking system.
Below is the information that pulls in and populates in an inspection item:
The name of the item, aircraft, engine, or prop (if applicable) and frequencies, including the Estimated Due Date, come into Avianis.
The Estimated Due Date is being populated for items coming back from the maintenance tracking systems. It is a date provided that represents when the item is estimated to be due based on the tracking system's own utilization data.
The profile type set from the maintenance tracking provider in the inspection item is what supports the next due calculations. The profile types that are functional are airframe, engine, propeller, and APU.
HOW TO OVERRIDE INSPECTION ITEMS
There is an override option available on each inspection item. This setting prevents the item from being updated in the automatic pull and/or manual pull.
Access the inspection item
Set Override to Yes
Input the sync until date. The item will not be updated again until the sync date is met.
EXCLUDE ITEMS FROM PULLING IN
Refer to the maintenance tracking provider for specific functionality when needing to exclude items from pulling into Avianis. Below lists options depending on the maintenance provider:
When connected to CAMP if the discrepancy value of RTSState comes back in the API, those items can be excluded in the sync and/or will be marked as closed.
When connected to Flightdocs if the task is no longer applied due to part number installed or SB accomplishment, the interval can be removed preventing the task from coming into Avianis.
Related Articles
Maintenance Tracking: Setup
Avianis offers integrations with CAMP and Flightdocs. This guide outlines: the functionality of the maintenance integrations; how to setup the integration; overview of all settings; and how to test the integration See related articles: Aircraft ...Custom Aircraft Roles: Use Cases
There are various use cases for creating Custom Roles related to aircraft access. This guide will outline some examples. This feature can be used when the user has either a Flight Crew License or Business User License in conjunction with other roles. ...Enable 3rd Party Cookies and Cross-Tracking
Many of the integrated services with Avianis use third party cookies and cross-tracking, which must be enabled in your browser to work successfully. If you see an error with FulerLinx, error with FlightBridge, error with FlightAware, or error with ...Case Management: Creating & Use Case Examples
Cases can be created through a trip or a flight log and are a way to document service issues. This article will detail: How to create a case What the most common use cases are How to manage/resolve a case Where to locate a list of all submitted cases ...Maintenance Offline Types
Creating various offline types allows an operation to track maintenance events by what type of offline event occurred. This article explains the following Where to create and manage offline types where to add offline types to the job card/offline ...