Configure the Turn Data Sync Buffer Size

Explanation

The amount of data that should be synchronized from the Maintenance Execution server to the mobile application is determined by the turn data synchronization window, which is a time interval specified by the values of the Display Inbound Turns for the Next (Hours) and Display All Turns for the Last (Hours) fields on the Airport page.

Changes to entities (e.g., changes made to flights, work packages, faults, and tasks) occurring outside of the turn data synchronization window are not immediately pushed to the device, as they don't impact the technician's immediate tasks. Instead, they are scheduled to be sent to the device later through batch jobs. By default, these batch jobs run approximately every 15 minutes for most Line Maintenance Execution entities. This approach helps maintain efficiency by avoiding unnecessary data synchronization.

As time progresses, the turn data synchronization window moves forward, displaying newer data while hiding older information. Consequently, there can be a delay of 1 to 15 minutes before the next batch job updates the device. To address this gap, it's essential that when the batch job runs, it synchronizes at least 15 minutes' worth of data ahead of the current synchronization window. This additional data is referred to as the turn data sync buffer, which is specified by the TURN_DATA_SYNC_BUFFER_SIZE parameter in the Maintenance Execution Parameters page.

This parameter is expressed as a multiplier of the value for the Show Inbound Turns for the Next (Hours) field on the Airport page. This data is not visible to users.

For example, if the Show Inbound Turns for the Next (Hours) field value is set to 3 and the TURN_DATA_SYNC_BUFFER_SIZE parameter is set to 1.5 (default value), Line Maintenance Execution synchronizes 4.5 hours (3 x 1.5) of turn data after the turn data synchronization window.

Prerequisites

System Effects