Mobile Application Synchronisation

Whilst the Mobile Application is Active on the device, synchronisation is triggered at four scheduled intervals: On the hour, Quarter Past, Half Past and Quarter To. Each interval handles different data sets depending on the User Type.

Each sync cycle is designed to progressively update different layers of system data throughout the hour, ensuring that core structural data, build-level data, and operational task/order data remain current while the app is in active use.

Data movement is categorised into two behaviours:

Some processes are pull-only, where the app retrieves the latest data from the server without sending any updates back.

Other processes are push-and-pull, where the app both sends locally captured updates to the server and retrieves updated data in return, ensuring full synchronisation of changes made on the device and in the system.

Active Synchronisation

On the hour, a full primary synchronisation is performed:

Operative:

• Push and Pull:
  • Work Submissions
• Pull:
  • Sites
  • Plots
  • Build Stages
  • Variations
  • Forms
  • Master Materials
  • Master Labour Items

Customer Care Engineer:

• Pull:
  • Sites
  • Plots

Contract Manager:

• Push and Pull:
  • Variations
  • User Forms
  • Pre-Orders
• Pull:
  • Sites
  • Plots
  • Build Stages
  • Forms
  • Master Materials
  • Master Labour Items

At Quarter past, build-level data is synchronised:

Operative:

• Pull:
  • Plot Materials
  • Plot Labour Items

Contract Manager:

• Pull:
  • Plot Materials
  • Plot Labour Items

At Half past, operational and transactional data is synchronised:

Operative:

• Push and Pull:
  • Tasks
• Pull:
  • Consumables
  • Plots Sales Extras
  • Users
• Push:
  • Consumable Orders
  • Orders

Contract Manager:

• Push and Pull:
  • Users
  • Tasks
• Pull:
  • Consumables
  • Plots Sales Extras
  • Engineer Tasks
• Push:
  • Consumable Orders
  • Orders

At Quarter To, Site Document data and Customer Care jobs are synchronised:

Operative:

• Pull:
  • Site Documents

Customer Care Engineer:

• Push and Pull:
  • Customer Care Jobs

Contract Manager:

• Push and Pull:
  • Customer Care Jobs
• Pull:
  • Site Documents

Suspended Synchronisation

Synchronisation can still occur while the application is running in the background (open but not currently visible to the user).

Background synchronisation timing is controlled by the device operating system and is dependent on available system resources, battery optimisation, and background processing availability. As a result, the exact time that a background synchronisation occurs cannot be guaranteed.

If a background synchronisation process exceeds 30 seconds in duration, the operating system automatically terminates the sync process. This is standard operating system behaviour designed to manage device performance and resource usage.

Application Reopen Synchronisation

When the application is reopened, various synchronisation processes are automatically triggered depending on the User Type to catch up on any data changes that may have occurred while the application was inactive or suspended.

The specific synchronisation processes that run for each user type are described below.

Operative:

• Push and Pull:
  • Work Submissions
  • Tasks
• Pull:
  • Sites
  • Plots
  • Build Stages
  • Variations
  • Forms
  • Master Materials
  • Master Labour Items
  • Plot Materials
  • Plot Labour Items
  • Consumables
  • Plots Sales Extras
  • Users
  • Site Documents
• Push:
  • Consumables Orders
  • Orders

Customer Care Engineer:

• Pull:
  • Sites
  • Plots
  • Customer Care Jobs

Contract Manager:

• Push and Pull:
  • Variations
  • User Forms
  • Pre-Orders
  • Users
  • Tasks
  • Customer Care Jobs
• Pull:
  • Sites
  • Plots
  • Build Stages
  • Forms
  • Master Materials
  • Master Labour Items
  • Plot Materials
  • Plot Labour Items
  • Consumables
  • Plots Sales Extras
  • Engineer Tasks
  • Site Documents
• Push:
  • Consumables Orders
  • Orders