Skip to content
  • There are no suggestions because the search field is empty.

Creating New Compliance Items (Maintenance Tracking)

This article covers all three methods and provides guidance on best practices, including how to set up a “template aircraft” for efficient onboarding and how to avoid common spreadsheet import errors.

EBIS offers three primary ways to create Compliance Items — manually for a single aircraft, by copying from a template or existing aircraft, or via a spreadsheet import. Each method is designed to streamline your setup and ensure recurring maintenance items are consistently tracked across your fleet.

This article covers all three methods and provides guidance on best practices, including how to set up a “template aircraft” for efficient onboarding and how to avoid common spreadsheet import errors.

 

Creating a Single Compliance Item from the Aircraft

To manually create a new Compliance Item:

  1. Go to the Aircraft Module
  2. Click into a specific aircraft
  3. Select the Compliance tab
  4. Click the + Add Compliance Item button in the top right
  5. Select a Compliance Type from the dropdown and enter a name
  6. Click Add and Go To to configure intervals, actions, and details

💡 The available fields will change based on the System Type defined by the selected Compliance Type (e.g., Component or Inspection).

📘 Component types allow part number/serial number tracking, while Inspection types support recurring inspection records.

📘 For a full explanation of System Types and how they affect Compliance Items, see the related article: Understanding Compliance Type Configuration.

 

Copying Compliance Items from One Aircraft to Another

For fleet consistency and efficiency, EBIS allows you to copy existing Compliance Items from one aircraft to another.

  1. Go to the Aircraft Module
  2. Select the aircraft you want to copy to
  3. Click the Compliance tab
  4. Click the Copy Items from Another Aircraft button (two arrows icon)
  5. Choose the source aircraft from the dropdown
  6. Select the items to copy
  7. Click " + " Copy Selected Components to This Aircraft

⚠️ The source and target aircraft must share the same Meter Profile to be eligible for copying.

Recommended: Create a Template Aircraft

Many users create a "template" aircraft with a complete, standardized set of Compliance Items.

Use case:

  • Create a tail number like TEMPLATE-SR22
  • Add all baseline compliance items (ADs, SBs, inspections)
  • Use this as a source aircraft when adding new Cirrus SR22s to your fleet

This ensures consistency across the fleet and minimizes setup time.

 

Bulk Importing Compliance Items Using the Data Import Tool

If you're onboarding a large number of aircraft or items, use the Import Data tool for bulk entry.

Step-by-step:

  1. Go to Config > Import Data
  2. Under Action, select Import Data from File
  3. For Import Type, select Compliance
  4. Download the provided XLS template
  5. Fill out your items in the spreadsheet using your existing aircraft and configuration setup.
  6. Choose Insert New Records under Update Type.
  7. Upload your completed spreadsheet, select the import file under the Select an Existing Uploaded Import File section, and click Continue.
  8. Map the fields under the Match Columns section. System Name reflects what EBIS calls this field, and Your Column shows which column in the imported spreadsheet will map to that EBIS field.
  9. Click Import

Key Template Fields:

  • reg_number – Must match an existing tail number
  • type – Links to a configured Compliance Type
  • item_type and action – Match the dropdowns set in Config > Lists
  • interval_hours, interval_months, start_install_date, etc.

📘 Be sure to enter interval values in the correct set of columns depending on the item’s System Type (Component vs. Inspection).

Common Import Errors:

  • Mismatch of intervals and system type:
    • If a Component type uses inspect_interval_hours, the item may fail to import
    • Component types must use fields that begin with interval_ — for example, an hourly interval should go in the interval_hours column
    • Inspection types must use fields that begin with inspect_ — for example, an hourly interval should go in the inspect_interval_hours column
    • Using the wrong set of interval fields for the given System Type is one of the most common causes of import failure
  • Reg Number Not Found: The tail number in the sheet must already exist in EBIS
  • Compliance Type or Action mismatch: Must match existing config settings exactly (case-sensitive)
  • Meter reading date mismatch: If a referenced start_install_date doesn’t have a matching reading, the item may not calculate intervals correctly

💡 After import, always check for errors in the Data Sync Logs and verify imported items by viewing the aircraft’s Compliance tab.

 

Related Articles

 

Keywords: Compliance Setup, Copying Items, Compliance Import, Maintenance Tracking Import Audience: Admins, Implementation Teams, Maintenance Coordinators Article Type: Setup / Configuration