BlueOne User Guide

Overview of Integration

The integration between TrustFlight Tech Log and BlueOne is designed to streamline the flow of data between the two systems. This bidirectional integration automates the import of Trip, Flight, and Crew details from BlueOne into the Tech Log and, once a flight is complete, updates BlueOne with journey report data.

This document covers the functionality of the integration, its limitations, and its configuration. Enabling the integration requires very few process changes with minimal disruption to current workflows within the operator and helps automate data synchronization for enhanced operational efficiency.

Once the integration has been added to your agreement, the visibility to enable the integration can then be enabled by a TrustFlight Administrator, allowing you to create the link between Tech Log and BlueOne on the integrations page of the TrustFlight Dashboard.

 

System Descriptions

Partner: BlueOne - Aircraft and Crew Management

Integration Summary: Synchronizes flight scheduling and operational data between BlueOne and TechLog, automatically creating trips and flights while sending completed journey reports back to BlueOne

Integration Type: Bidirectional

 

Objectives & Benefits

• Automated flight scheduling synchronization reduces manual data entry
• Real-time post-flight data transfer improves operational efficiency
• Seamless crew assignment integration streamlines flight operations
• Enhanced operational oversight through synchronized journey reporting

 

Functionality Overview

The integration operates on standard polling intervals, currently set to every 5 minutes. Synchronization also includes automatic retry mechanisms for failed operations. The following capabilities are supported:

• Pull the Scheduled Trip, Flights from BlueOne to TechLog
• Push the Actual Journey Report data from TechLog to BlueOne
• Create Crew assigned to a BlueOne flight in TechLog

 

Aircraft

When enabling the integration, aircraft can be selected on setup. Aircraft must exist in TechLog before flights can be synchronized from BlueOne.

 

Syncing Trips & Flights

The system fetches flights up to 48 hours in advance from BlueOne and synchronizes them with TechLog based on the configured aircraft registrations.

 

Importing Data to TrustFlight

Trip Data

The following fields from BlueOne, are mapped as trip data in TechLog:

• Trip Date: From std
• PIC and SIC: From crew_compo.crew_member
• Aircraft Registration: From aircraft_reg
• Callsign: From call_sign_code + call_sign_number

 

Flight Data

Flight data from BlueOne is mapped to the corresponding fields in TechLog:

• Departure: Departure on the TechLog Preflight Tab
• Destination: Arrival on the TechLog Preflight Tab
• STD: Take off time on the TechLog Postflight Tab
• STA: Landing time on the TechLog Postflight Tab
• CA: PIC in the Preflight tab
• FO: SIC in the Preflight tab

 

Crew

Crew members are automatically linked to TechLog based on their email addresses. If a crew member does not exist in TechLog or no email address is provided, they will be ignored during synchronization. CA (Captain) positions from BlueOne are mapped to PIC (Pilot in Command) in TechLog, while FO (First Officer) positions are mapped to SIC (Second in Command).

 

Passengers and Fluids

Passenger numbers must be entered manually into TechLog. Fluid data (fuel, oil, hydraulic) must also be recorded in TechLog, as it is not imported from BlueOne.

 

Pushing Data to BlueOne

Once the postflight has been signed off in TechLog, the data will automatically sync back to the corresponding trip/flight in BlueOne. This completed data is passed through the API as Journey Log entries containing post-flight operational data including fuel consumption, timings, and crew assignments.

 

Data Flow Diagrams

Entity Mappings

TechLog Entity	Direction	BlueOne Entity	Description
Sectors	<->	Flights	Individual flight segments with schedule data synced from BlueOne and post-flight data sent back
Trips	<-	Trips	Flight groupings based on date and aircraft registration
Journey Reports	->	Journey Reports	Completed flight data including timings, fuel consumption, and crew assignments sent to BlueOne

 

 

---

 

Detailed Functionality

Data Exchange Overview

Aircraft

The integration operates within the context of configured aircraft registrations. Aircraft must exist in both systems for data to transfer, as they will not be created automatically in either system. The integration is configured for specific aircraft registrations during setup.

 

Flight Grouping

Each BlueOne flight creates a separate TechLog trip. The integration does not support multi-leg trip grouping, meaning that multi-sector journeys in BlueOne will be split into individual trips in TechLog, each containing a single flight.

 

Crew

Crew members are linked between systems based on email addresses. If a crew member exists in BlueOne but does not have a valid email address, they cannot be assigned to the flight in TechLog and will not be synchronized. Only pilot positions (CA - Captain and FO - First Officer) are synchronized between systems. The system supports both PIC (Pilot in Command) and SIC (Second in Command) crew assignments.

 

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. The system fetches flights up to 48 hours in advance from the last synchronization date.

 

Error Handling and Logging

The integration includes comprehensive validation and error handling:

• Flight Timing Validation: Ensures takeoff time occurs before landing time
• Fuel Data Validation: Validates fuel quantities with pre/post uplift values required, and total uplifts plus pre-fuel must approximate post-fuel within 100 unit tolerance
• Crew Validation: Verifies crew member email addresses exist and proper assignments. If email addresses don't exist, crew members will be ignored during synchronization
• Aircraft Registration Check: Verifies aircraft exists in TechLog before syncing flights
• Automatic Retry: We automatically retry data synchronization when facing errors related to server downtimes, but authentication failures and configuration errors will not be retried

 

Other Implementation Details

Signed Data Protection

Once a preflight or postflight has been signed within the TechLog system, no further data from BlueOne will be updated for that specific flight or trip. This safeguard preserves the integrity and immutability of signed records, ensuring compliance with operational and regulatory requirements.

 

Airport Handling

Airports are linked to flights based on 4-letter ICAO codes. In cases where an airport is missing from TechLog, the system assigns the placeholder code "ZZZZ" to maintain flight operations while users can contact support to add the missing airport.

 

Journey Report Submission

Post-flight data is automatically sent to BlueOne as journey reports once the postflight is signed off in TechLog. This includes detailed flight timings, fuel consumption data, crew assignments, and operational metrics. All times are stored in ISO8601 format with airport time offsets considered in calculations.

 

---

 

Data Mapping

BlueOne to TechLog (Trip)

These are the fields transferred from BlueOne to TechLog when a trip is created or updated:

BlueOne Field	TechLog Field	Notes
std	Date	Flight scheduled time of departure
aircraft_reg	AircraftId	Fetched via aircraft registration lookup
uid	FlightId	BlueOne unique identifier
call_sign_code + call_sign_number	Callsign	Concatenated from two fields
CA crew_member	PilotInCommandId	From crew_compo.crew_member where position_short = 'CA'
FO crew_member	SecondInCommandId	From crew_compo.crew_member where position_short = 'FO'

 

BlueOne to TechLog (Flight)

These are the fields transferred from BlueOne to TechLog when a flight is created or updated:

BlueOne Field	TechLog Field	Notes
uid	FlightId	BlueOne unique identifier
number	FlightNumber	Flight number
apt_dep.icao	DepartureAirportId	Fetched via airport ICAO lookup
apt_arr_actual.icao OR apt_arr_planned.icao	ArrivalAirportId	Uses actual if available, else planned
std	TakeoffTime	Flight scheduled time of departure
sta	LandingTime	Flight scheduled time of arrival
CA crew_member	PilotInCommandId	From crew_compo.crew_member where position_short = 'CA'
FO crew_member	SecondInCommandId	From crew_compo.crew_member where position_short = 'FO'

 

TechLog to BlueOne

These are the fields transferred from TechLog to BlueOne after a flight is completed:

TechLog Field	BlueOne Field	Notes
Date	flt_day_of_operation	ISO8601 FORMAT
OffblocksTime	flt_crep_db	ISO8601 FORMAT - Off blocks time
TakeoffTime	flt_crep_dt	ISO8601 FORMAT - Take off time
LandingTime	flt_crep_al	ISO8601 FORMAT - Landing time
OnblocksTime	flt_crep_ab	ISO8601 FORMAT - On blocks time
Cycles.airframe	flt_nb_cycles	Defaults to 1 if undefined
FlightType	flt_etops	'Y' if IFR, 'N' if not
FlightType	flt_low_vis	'Y' if IFR, 'N' if not
PreUpliftFuel	fuel.on_board_before_fueling	Fuel quantity before uplift
PostUpliftFuel	fuel.on_board_after_fueling	Fuel quantity after uplift
PostUpliftFuel	fuel.off_block	Fuel quantity at departure (post-fueling, prior to taxi). TechLog does not track APU burn or other minor fuel consumption between refueling and brake release
RemainingFuel	fuel.landing	Fuel on board at gate after flight completion; taxi-in burn not separately tracked.
RemainingFuel	fuel.on_block_actual	Fuel on board at gate after flight completion.
PilotPerformingTakeoffId	cockpitcrew.asg.take_off	'Y' if matches crew ID, 'N' if not
PilotPerformingLandingId	cockpitcrew.asg.landing	'Y' if matches crew ID, 'N' if not
PilotInCommandId	cockpitcrew.asg.as_commander	'Y' if matches crew ID, 'N' if not

 

 

---

 

Integration Setup & Configuration

Step-by-Step Setup Guide

Enabling the Integration (TrustFlight)

Enabling the BlueOne integration can be done by users at the organisation who are administrators once they've agreed to and paid the additional fee via the integration.

 

1. Navigate to the Settings section within the TrustFlight Dashboard.

 

2. Select Integrations and locate the BlueOne integration under the relevant operator.

 

3. Click Enable underneath the BlueOne integration.

 

4. Enter your BlueOne credentials, select the relevant aircraft registrations and select ‘Link’

 

 

The BlueOne integration requires usernames and passwords for each route on the API. The fields requires from BlueOne to connect the integration are:

1. Flight Username - Username for the Flight route on the BlueOne API
2. Flight Password - Password for the Flight route on the BlueOne API
3. Journey Username - Username for the Journey route on the BlueOne API
4. Journey Password - Password for the Journey route on the BlueOne API
5. BlueOne URL - URL of the API to connect to
6. Aircraft Registrations - List of registration to send to BlueOne

Connecting optional fields within BlueOne to Tech Log requires configuration by our development team, please contact support@trustflight.com to discuss this further.

 

Flight Grouping

One trip, one flight - One trip and flight in BlueOne will be reflected as one trip and sector in Tech Log

 

 

 

---

 

Limitations & Constraints

Known Limitations

• It is currently not possible to group multiple flights by date into one single trip
• One trip with multiple legs in BlueOne will be split into separate trips, each with one flight in TechLog
• Deletions in either software (BlueOne and TechLog) are not detected and will need to be manually deleted in the other product
• Aircraft must exist in TechLog before flights can be synchronized from BlueOne. The integration will not automatically create aircraft records in either system, requiring manual setup of aircraft configurations prior to data synchronization
• Crew members are linked between systems based on email addresses only. If a crew member exists in BlueOne but not in TechLog, they will be ignored during synchronization
• Only pilot positions (CA - Captain and FO - First Officer) are synchronized between systems. Other crew positions are ignored during synchronization
• The integration fetches flights up to 48 hours in advance, which may limit visibility for longer-term scheduling changes

 

Operational Constraints

• Flight timing validation requires takeoff time to occur before landing time for successful journey report submission
• Fuel data validation requires pre/post uplift fuel values to not be null, and total uplifts plus pre-fuel must approximate post-fuel within 100 unit tolerance to prevent data submission errors
• Post-flight updates can only be sent back to BlueOne for flights that were previously synchronized from BlueOne to TechLog. Manually created flights in TechLog cannot receive post-flight data updates
• Crew email addresses are required for user creation in TechLog - crew members without valid email addresses cannot be assigned to flights
• BlueOne crew data must exist in the sync mapping for reverse journey report submission to include proper crew assignments

 

Workarounds and Mitigation Strategies

• In cases where an airport is missing from TechLog, the system assigns the placeholder code "ZZZZ" to maintain flight operations. Users can contact support to add missing airports for accurate future flight data
• When crew members exist in BlueOne but not in TechLog, manual user creation in TechLog with matching email addresses enables proper crew assignment synchronization
• For multi-leg trips in BlueOne that split into separate TechLog trips, operators can maintain operational continuity by tracking related flights through callsign or aircraft registration references
• To prevent journey report submission failures, ensure all required fuel data is entered and flight timings are chronologically correct before signing off postflight records
• For flights requiring longer-term planning beyond the 48-hour sync window, manual flight creation in TechLog may be necessary until the flights fall within the automatic sync timeframe

 

---

 

Cost and Licensing

Pricing Information

The BlueOne 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 BlueOne 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.

 

 

---

 

Appendices

Appendix A: Glossary and Terminology

Term	Definition
BlueOne	A flight scheduling and management system used by aviation operators.
Tech Log	TrustFlight's electronic technical logbook system that tracks aircraft operations and maintenance.
Trip	A series of flights or a single flight planned and operated within BlueOne, transferred to Tech Log for operational data.
Flight	A single flight sector, with detailed data on departure, arrival, crew, and aircraft performance.
PIC	Pilot in Command—the main pilot responsible for operating the flight.
SIC	Second in Command—the co-pilot assisting the PIC.
Journey Log (JL)	A record of a flight's details, synced from Tech Log back to BlueOne after the flight.
STD	Scheduled Time of Departure—the planned takeoff time of the flight.
STA	Scheduled Time of Arrival—the planned landing time of the flight.