Industry problems

How do airline ground crews handle data on the ramp?

Airline ground crews record the turnaround as it happens, including baggage scans, loading, checks and timings, under policies and procedures from IATA's Airport Handling Manual and Ground Operations Manual. Some of that data is evidence of a handover, such as IATA Resolution 753's baggage tracking at acceptance, loading, transfer and arrival. When a device cannot reach the airline's systems, apps have to keep each record on the device with its original time and deliver it later exactly once.

TL;DR

A ramp record can prove responsibility moved between parties, so an offline app must not lose it, mistime it or record it twice. Saving scans to the device first, each with its event time and an operation ID, and showing what waits to upload keeps the audit trail intact. Device-to-device sharing keeps crew at one aircraft on the same checklist.

Learning objectives

After reading this article you will be able to:

  • Describe the IATA manuals and audit programme that shape ramp data
  • Explain why lost, mistimed and duplicated ramp records each damage the audit trail
  • Compare lazy, queued and online-only writes for scans and checks on the ramp

Ground crew turnaround data

Ground crews record data from each part of the turnaround. Bags are tracked through their journey from acceptance to arrival. Loading feeds load control. Aircraft movement messages report what the aircraft did and when, and delays are recorded with standard codes.

IATA describes ramps as busy, confined areas in which aircraft, ground support equipment and people are in constant motion in all weathers. Ground handling during a turnaround spans areas such as passenger services, aircraft loading, load control and cargo, the subjects IATA’s Airport Handling Manual covers, and each of these produces data.

IATA standards for ground handling data

Three IATA programmes set the shape of this work: the Airport Handling Manual, the IATA Ground Operations Manual and ISAGO.

  • Airport Handling Manual (AHM). The AHM gives industry-approved policies and standards for ground handling. IATA calls it policy driven, “what to do”. Its contents include delay code procedures and aircraft movement messages.
  • IATA Ground Operations Manual (IGOM). The companion manual is procedure driven, “how to do”. IATA calls for the ground handling industry to adopt it globally for consistent and safe operations.
  • ISAGO. The IATA Safety Audit for Ground Operations assesses how ground handling service providers implement their management systems and standardised operating procedures.

Baggage has its own rule. IATA Resolution 753 requires member airlines to track baggage at four points: acceptance, loading, transfer and arrival. IATA describes the result as a verifiable audit trail for the acquisition and handover of baggage, and airlines must share tracking information with interline partners. IATA also notes that adoption has been slower than expected, citing differences in airport infrastructure maturity, technological readiness and investment.

A lost network link can lose a ramp record, give it the wrong time, or duplicate it, and a ramp record can be evidence that responsibility moved from one party to another: the bag was loaded, the hold was closed, the check was done. That makes those three failure modes serious.

The first is losing the record. If a scanner cannot reach the system and the app does not keep the scan, the audit trail has a hole. The second is giving it the wrong time. A scan uploaded late must still show when the bag was loaded, not when the upload arrived, or the record tells the wrong story. The third is the duplicate. If a device sends a scan, the confirmation is lost on the way back, and the device sends it again, the system must recognise the second copy rather than record a second event. What happens to a write made offline? covers the general case.

Offline writes for ramp scans and checks

Scans and completed checks fit lazy writes, which save to the device first and queue the change for the network. Android’s offline-first guidance describes three ways to write data, and a ramp app can use all three:

  • Lazy writes save to the device first and queue the change for the network at the earliest opportunity. The guidance calls this the correct choice when data is critical to the app, which fits scans and completed checks.
  • Queued writes go into a queue drained with exponential backoff, for data that is not time sensitive, such as analytics and logs.
  • Online-only writes succeed only if the network accepts them, for actions that must happen in near real time. The guidance’s example is a bank transfer. On the ramp, whether an action belongs here is a procedural decision set by the airline’s manuals, not by the app.

Two details make lazy writes safe. Each record carries the time it happened and an operation ID, so a retried upload is recognised and applied once. And the app shows plainly what is still waiting to upload, so a crew lead can see whether a gap is in the work or only in the network.

Shared turnaround checklists between handhelds

With device-to-device software, handhelds within radio range can keep a shared replicated document, such as the turnaround checklist, and merge edits when they reconnect. Queuing solves the link between one device and the airline’s systems, but it does not help two crew members at the same aircraft see each other’s progress when neither can reach those systems.

That is a local problem. Fields that can only have one correct value, such as who signed off a check, need a rule decided in advance, because a merge picks a result but does not know the procedure. The airline’s systems stay the record. Local sharing keeps the crew working from the same picture until the data reaches them.

Frequently asked questions

Which ramp records can be captured offline?

That is a procedural decision for the airline and its handlers, not the app. Records that document something that has already happened, such as a scan or a completed check, can be captured and delivered later with their original time. Actions that must use current information can be built so they require a live connection.

What is IATA Resolution 753?

It requires member airlines to track baggage at four points, acceptance, loading, transfer and arrival. IATA describes the result as a verifiable audit trail for the acquisition and handover of baggage, and airlines must share tracking information with interline partners.

What is the difference between the IATA AHM and IGOM?

The Airport Handling Manual is policy driven, what to do, and gives industry-approved policies and standards for ground handling. Its companion, the IATA Ground Operations Manual, is procedure driven, how to do.

What is ISAGO?

The IATA Safety Audit for Ground Operations assesses how ground handling service providers implement their management systems and standardised operating procedures.

How do you stop a retried baggage scan from being recorded twice?

Give each record an operation ID along with the time it happened, so a retried upload is recognised and applied once rather than recorded as a second event.

What time should a late-uploaded ramp scan show?

The time the event happened. A scan uploaded late must still show when the bag was loaded, not when the upload arrived, or the record tells the wrong story.

Sources

Build it with Offline Protocol

The shared state guide shows how devices keep a replicated document, such as a checklist, in step with each other over a local link, which merge rule applies to each kind of field, and how to test edits made while devices are apart.

Read the shared state guide