Overview of Integration
System Descriptions
Partner: Traxxall - Aircraft Maintenance Management and Tracking Software
Integration Summary: Synchronizes maintenance data between Traxxall and TechLog, enabling comprehensive maintenance management across both platforms
Integration Type: Bidirectional
Objectives & Benefits
Streamlined maintenance data flow between aircraft tracking and electronic tech log systems
Automated synchronization of defects, scheduled maintenance items, and workpacks
Real-time aircraft utilization data sharing for accurate maintenance planning
Reduced manual data entry and improved data accuracy across systems
Functionality Overview
The Traxxall integration operates on standard polling intervals, currently set to every 5 minutes. The integration provides comprehensive maintenance data synchronization with the following capabilities:
Defects Management
Note: In Traxxall defects are named as snags. This document will refer to defects as this is the naming convention inside of Tech Log.
Defects created in Traxxall are automatically synchronized to Tech Log. The integration handles various defect severity levels and categories, mapping them appropriately to Tech Log's defect classification system.
Scheduled Maintenance Items
Note: In Traxxall scheduled maintenance items are pulled from Due Lists which contain a list of all maintenance due on an aircraft.
Due lists created in Traxxall are synchronized to Tech Log as scheduled maintenance items, ensuring proper maintenance scheduling and compliance tracking.
Workpacks Management
Note: In Traxxall workpacks are named as workplanners. This document will refer to workpacks as this is the naming convention inside of Tech Log.
Workpacks created in Traxxall are synchronized to Tech Log, including all associated tasks and maintenance items. The integration ensures proper status mapping and maintains task relationships.
Aircraft Utilization Data (Totals)
Aircraft totals from Tech Log are pushed to Traxxall as "Actuals" to support accurate maintenance interval calculations and planning.
Data Flow Diagrams
Entity Mappings
| TechLog Entity | Direction | Traxxall Entity | Description |
| Defects | <- | Snags | Maintenance defects and discrepancies synchronized from Traxxall to Tech Log |
| Scheduled Maintenance Items | <- | Due Lists | Scheduled maintenance checks and inspections due on aircraft |
| Workpacks | <- | Workplanners | Maintenance work packages containing multiple tasks and items |
| Aircraft Utilization Data (Totals) | -> | Actuals | Flight hours, cycles, landings, and other utilization metrics sent to Traxxall |
Detailed Functionality
Data Exchange Overview
Aircraft Context
The integration operates within the context of aircraft that must exist in both systems. Aircraft records are not automatically created and must be configured in both Traxxall and Tech Log prior to data synchronization.
Defect Processing
Each defect synchronization request from Traxxall returns all defects for the specified aircraft or fleet. The integration filters out defects that have not changed since the last synchronization to ensure only new or modified defects are processed in Tech Log.
Workpack Task Handling
When importing a workpack, the integration checks if constituent items already exist in Tech Log. If items exist, their identifiers are retrieved and linked. If items do not exist, they are created according to their task type classification: Snag and Airworthiness Directive task types are created as defects, while Part and Inspection task types are created as scheduled maintenance items.
Frequency of Data Sync
The integration operates on standard polling intervals, currently set to every 5 minutes. Synchronization also includes automatic retry mechanisms for failed operations.
Error Handling and Logging
The integration includes comprehensive error handling with automatic retry for transient failures. Authentication errors and data validation failures are logged but not retried automatically. Detailed error logs are maintained for troubleshooting and operational monitoring.
Other Implementation Details
User Assignment
The integration attempts to match users between systems based on name matching within the same organization. When a defect is reported by a user in Traxxall, the integration searches for Tech Log users with the same name and links to their account when found.
Data Mapping
The field mappings are organized by entity type based on the data flow shown in the Data Flow Diagrams section. Each entity has specific field mappings configured for synchronization between systems.
Defects (Traxxall Snags) - Unidirectional Sync
Traxxall to Tech Log
| Traxxall | Tech Log | Notes |
| description | itemDescription, details | Defect description used for both item description and details fields |
| referenceNo | number | Defect reference number |
| recordedDate | raisedAt | Date and time when defect was recorded |
| ata | ataChapter | ATA chapter classification |
| subAta | ataSection | ATA section classification |
| Reported By | ReportedById | User search by name within organization for account linking |
| reportedTitle | reportedByType | Reporter type mapped according to reported title mapping table below |
| snagCategory | defectType | Defect type mapped according to defect category mapping table below |
| snagCategory | rectificationCategory | Rectification category mapped according to defect category mapping table below |
| snagCategory | deferred | Deferral status mapped according to defect category mapping table below |
| estimatedDueDate | dueDate | Due date for defect rectification |
Defect Category Mapping
Defect categories in Traxxall are mapped to Tech Log defect types and rectification categories as follows:
| Traxxall Category | TL defectType | TL rectificationCategory | TL Deferred |
| Not Set | "" | "" | false |
| AOG | Other | "" | false |
| NEF | NEF | ADVISORYONLY | true |
| CDL | CDL | ADVISORYONLY | true |
| MEL - Cat. A | MEL | A | true |
| MEL - Cat. B | MEL | B | true |
| MEL - Cat. C | MEL | C | true |
| MEL - Cat. D | MEL | D | true |
| Fly-On | Other | ADVISORYONLY | true |
Reported Title Mapping
Reported titles from Traxxall are mapped to Tech Log's reporter type categories:
| Traxxall Reported Title | TL ReportedByType |
| Pilot | Pilot |
| Steward | Cabin |
| Technician, Inspector, RII Inspector, Administrator, Coordinator, Engineer, Director of Maintenance, CAMO, Non Certified Mechanic, Other | Maintenance |
Scheduled Maintenance Items (Traxxall Due Lists) - Unidirectional Sync
Traxxall to Tech Log
| Traxxall | Tech Log | Notes |
| description | name | Maintenance item name |
| description | details | Maintenance item details |
| nextDueDate | dueDate | Due date parsed from DD-MM-YYYY format |
| estimatedDueDate | estimatedDate | Estimated completion date |
| nextDue (hours) | dueFlightSeconds | Due flight hours converted to seconds |
| nextDue (cycles) | dueCycles | Due flight cycles |
| nextDue (APU hours) | dueAPUSeconds | Due APU hours converted to seconds |
| nextDue (landings) | dueLandings | Due landings count |
| ma + taskType | mxType | Maintenance type mapped according to maintenance type mapping table below |
| draft status | draft | Draft status for maintenance item |
| source | source | Origin system identifier |
Maintenance Type Mapping
Maintenance items are created based on the major assembly and task type combination:
| Major Assembly | Task Type | TL Maintenance Type |
| Engine 1 | Part, Inspection | engine_1_scheduled |
| Engine 1 | Snag, Airworthiness Directive | engine_1_oop |
| Engine 2 | Part, Inspection | engine_2_scheduled |
| Engine 2 | Snag, Airworthiness Directive | engine_2_oop |
| Engine 3 | Part, Inspection | engine_3_scheduled |
| Engine 3 | Snag, Airworthiness Directive | engine_3_oop |
| Engine 4 | Part, Inspection | engine_4_scheduled |
| Engine 4 | Snag, Airworthiness Directive | engine_4_oop |
| Airframe | Part, Inspection | airframe_scheduled |
| Airframe | Snag, Airworthiness Directive | airframe_oop |
| APU 1 | Part, Inspection | apu_scheduled |
| APU 1 | Snag, Airworthiness Directive | apu_oop |
| Default (any other combination) | Any | airframe_scheduled |
Workpacks (Traxxall Workplanners) - Unidirectional Sync
Traxxall to Tech Log
Traxxall |
Tech Log |
Notes |
|---|---|---|
Description&Notes |
description |
Workpack description |
WpNumber |
poNumber, reference |
Workpack number used as both PO number and reference |
WpStatus |
status |
Status mapped according to workpack status mapping table below |
Notes |
notes |
Additional workpack notes |
Workpack Status Mapping
Traxxall Status |
TL Status |
|---|---|
Opened |
active |
InProgress |
active |
Completed |
complete |
Cancelled |
complete |
Draft |
draft |
Workpack Task Type Mapping
Workpack tasks in Traxxall are mapped to appropriate Tech Log entities:
Traxxall Task Type |
TL Entity Type |
|---|---|
Airworthiness Directive |
Defect |
Inspection |
Scheduled Maintenance Item |
Part |
Scheduled Maintenance Item |
Snag |
Defect |
Service Bulletin |
Ignored |
Aircraft Utilization Data (Totals) - Unidirectional Sync
Tech Log to Traxxall
| TL API Value | Traxxall Unit of Measure | Description |
| airframeSeconds | Hrs | Airframe flight hours converted to hours from TechLog's airframeSeconds |
| airframeLandings | Ldg | Airframe landings count |
| airframeFlights | Flt | Airframe flight count |
| airframeCycles | FLCY | Airframe flight cycles |
| engine1Seconds, engine2Seconds, engine3Seconds, engine4Seconds | Hrs | Engine operating hours converted to hours from TechLog's engineSeconds |
| engine1Cycles, engine2Cycles, engine3Cycles, engine4Cycles | Enc | Engine operating cycles |
| prop1Seconds, prop2Seconds, prop3Seconds, prop4Seconds | Hrs | Propeller operating hours converted to hours from TechLog's propSeconds |
| apuSeconds | Hrs | APU operating hours converted to hours from TechLog's apuSeconds |
| apuCycles | APUS | APU start cycles |
Integration Setup & Configuration
Step-by-Step Setup Guide
The ability to enable the Traxxall integration can be granted by a TrustFlight Administrator, allowing the customer to create the link between Tech Log and Traxxall. The integration must be enabled separately for each operator (e.g., AOC) that you manage.
Enabling the Integration (TrustFlight)
-
Navigate to the Settings section within the TrustFlight Dashboard.
-
Select Integrations and locate the Traxxall integration under the relevant operator.
-
Click Enable underneath the Traxxall integration.
Enter your Traxxall API Key and API Password and select ‘Link’.
Limitations & Constraints
Known Limitations
- Aircraft must exist in both Traxxall and Tech Log before data synchronization can begin. The integration does not automatically create aircraft records in either system.
- Defects in Traxxall can be raised with flight and leg numbers, but since trips/sectors are not currently imported from Traxxall, linking defects to specific trips/sectors is not supported.
- Due date calculations are recalculated by Tech Log based on standard maintenance intervals, overriding any custom due date modifications made in Traxxall (e.g., changing a CAT B defect from 3 days to 50 days). This is a known limitation where Traxxall allows overriding of standard due dates for maintenance items, but when these items are imported into Tech Log, the backend recalculates the due date based on standard maintenance intervals.
- Return to Service (RTS) functionality from Traxxall is not currently supported in Tech Log. Traxxall supports RTS functionality on maintenance items which marks an item as returned to service for 7 days. Tech Log does not currently have a corresponding process for handling RTS status, so items marked as RTS will continue to show as overdue until completion.
Operational Constraints
- The integration processes all defects for an aircraft/fleet with each synchronization request due to Traxxall API limitations. Filtering occurs to process only new or modified defects.
- Service Bulletins from Traxxall workpack tasks are ignored and not synchronized to Tech Log.
- User matching between systems relies on name-based searching within the same organization, which may result in incorrect assignments if multiple users share the same name.
- Defect severity levels from Traxxall are not mapped to Tech Log as Tech Log does not have an equivalent severity concept. Deferral status is determined from the defect category instead.
Workarounds and Mitigation Strategies
For items showing incorrect due dates due to Tech Log's recalculation of maintenance intervals, operators should verify due dates against their maintenance program and manually adjust in Tech Log if necessary.
To handle Return to Service items showing as overdue, operators should monitor RTS items in Traxxall and manually complete them in Tech Log when the RTS period expires.
For user assignment issues due to name matching conflicts, ensure unique names are used across both systems or manually reassign defects to the correct users in Tech Log after synchronization.
To avoid issues with ignored Service Bulletins, operators should track these separately in Tech Log if needed for maintenance planning and compliance.
Cost and Licensing
Pricing Information
The Traxxall integration incurs an additional cost per tail. Please contact your TrustFlight account manager for more information on pricing and to ensure that the integration is added to your contract before proceeding with its activation.
Change Management
Process for Requesting Changes or Enhancements
As the Traxxall integration continues to evolve, new features and enhancements may be developed based on customer feedback and operational needs.
If your organization requires additional functionality that is not currently covered by the existing integration, please contact TrustFlight support at support@trustflight.com to discuss possible improvements or customizations.