IATA RP 1746: Baggage System Interface (BSI) – The Middleware Standard That Connects Airline IT to Airport Baggage Hardware

Introduction

An automated baggage handling system can sort thousands of bags per hour, yet it remains blind without timely, correctly formatted instructions from the airline. Conversely, an airline’s Departure Control System or baggage-reconciliation application cannot track or control a bag unless the physical sorter reports every scan and load event in a language the airline understands. Without a common interface, each airport or vendor would impose proprietary protocols, forcing costly custom integrations and creating points of failure.

IATA Recommended Practice 1746 closes that gap. It specifies the standard messaging and connectivity layer—known as the Baggage System Interface (BSI)—that enables one or more users to exchange baggage messages with one or more automated baggage systems. By defining message formats, addressing conventions, acknowledgements, retries and physical connection methods, RP 1746 ensures that carriers, ground handlers and airports share a single, reliable “language” for every baggage event from check-in to loading.

Origin and Publication History

The current RP 1746 designation first appeared in the June 2010 (30th edition) Passenger Services Conference Resolutions Manual. The 2010 edition explicitly records that the Baggage System Interface was a “complete re-write of guidelines to modernize the language and delete items no longer relevant.” Earlier interface guidance had existed under different numbering (for example RP 1797b in the 2007 manual), but the 2010 text constituted a thorough modernization.

As with all IATA Recommended Practices, RP 1746 is member-controlled intellectual property. Amendments are adopted by formal PSC vote or mail ballot and published in subsequent editions of the Resolutions Manual or associated circulars. Public sources indicate that the practice has remained in force through successive PSC cycles with only editorial or clarifying updates; no major public overhaul has been announced since the 2010 rewrite.

Purpose and Scope

The purpose of RP 1746 is interoperability. It removes the need for each airline–airport pair to invent its own message formats or connection methods. The recommended practice defines:

• Which messages (principally the Type-B baggage messages specified in RP 1745—BSM, BPM, BUM, BTM, etc.) are exchanged across the interface.
• How those messages are addressed so that sender and receiver are unambiguously identified.
• Communication protocols and physical connection methods (TCP/IP sockets, dedicated serial links, or network services).
• Handshake, acknowledgement (ACK/NACK) and retry rules that guarantee reliable delivery.
• Consistent treatment of the 10-digit license-plate bag tag, timestamps and event codes.

By enforcing one set of rules, RP 1746 prevents data mismatches and allows any compliant DCS, Baggage Reconciliation System, Airport Operational Database or sorter controller to participate in the same information flow.

Technical Structure

In operational terms a BSI is middleware—software or a gateway that sits between airline IT systems and the baggage handling system. It performs three core functions:

1. Message transport and routing – delivering each message to the correct destination system.
2. Protocol conversion – translating between airline messaging conventions (Type-B, XML, etc.) and the protocols used by conveyor controllers.
3. Format conversion and validation – ensuring that bag-tag numbers, timestamps and status codes conform to the agreed dictionary.

The BSI typically acts as a message broker. When a passenger checks in, the DCS generates a Baggage Source Message (BSM). The BSI receives that message, validates it, and forwards it to the sortation system, which then routes the physical bag. As the bag moves through screening, sortation or loading, the BHS generates status messages (BPM, BUM, etc.); the BSI returns those messages to the airline’s systems. Centralised handling of timeouts, retries and acknowledgements keeps the exchange robust even when individual links are momentarily unavailable.

Implementation Guidelines

Although the full proprietary text resides in the PSC Resolutions Manual, practical implementation follows a consistent set of principles:

• All messages conform to the Type-B formats defined in RP 1745.
• Bag identification uses the 10-digit license-plate number prescribed by Resolution 740.
• Connection methods (TCP/IP, serial, or network services such as SITA BagMessage) are agreed and tested.
• Heartbeats or keep-alive signals detect link failures promptly.
• Unacknowledged messages trigger defined retry sequences or are logged for investigation.
• Message queues and, where required, hot-standby BSI instances provide resilience.
• Disaster-recovery procedures ensure continuity if the primary interface becomes unavailable.

Airlines and system vendors obtain the detailed clauses through official IATA publications and incorporate them into interface specifications and acceptance-test plans.

Operational Workflow

1. At bag drop or check-in the airline DCS creates a BSM and sends it into the BSI.
2. The BSI validates addressing and content, then delivers the message to the BHS.
3. The sorter acts on the instruction and, as the bag progresses, generates BPM or BUM messages.
4. Those status messages travel back through the BSI to the airline’s reconciliation or tracking applications.
5. Special instructions (hold, priority, security) are conveyed by Baggage Control Messages under the same interface rules.
6. Any transmission failure is handled by the ACK/NACK and retry mechanisms defined in RP 1746, ensuring the event is not silently lost.
7. The complete sequence of time-stamped messages forms the electronic record used for tracking, reconciliation and audit.

Benefits for Airlines and Airports

A standardized Baggage System Interface delivers flexibility, integrability and connectivity. Airlines can introduce new self-service bag-drop kiosks, replace a sorter, or add a third-party reconciliation engine without redesigning their core IT interfaces; the BSI absorbs the integration work. Airports and ground handlers can offer common-use infrastructure that serves multiple carriers under a single interface standard.

Operationally the result is fewer data mismatches, faster deployment of new technology, and more reliable end-to-end tracking. Because every scan and load event travels through a common, acknowledged channel, mishandling rates fall and the cost of recovery declines. Passenger experience improves through higher on-time baggage delivery and faster reunification when exceptions do occur. The same standardized messages also satisfy the data-exchange requirements of Resolution 753 (baggage tracking).

Auditability and Tracking

Every BSI message carries a unique bag license-plate number and a timestamp. The resulting log constitutes a complete electronic audit trail of the bag’s journey. Under Resolution 753, bags must be tracked at four mandatory points—acceptance, loading, transfer and arrival. The BSI is the conduit that carries the corresponding messages; auditors can therefore verify compliance simply by examining the standardized message archive. When a bag fails to arrive, investigators can reconstruct the last successful event and identify the precise point of failure. This traceability supports both internal quality programmes and regulatory or interline accountability.

Relationship to Other IATA Standards

RP 1746 is the connectivity layer that makes several related standards operational:

• RP 1745 defines the content and format of the messages that travel across the BSI.
• Resolution 740 supplies the 10-digit license-plate identifier carried in every message.
• Resolution 753 mandates the tracking points whose events are reported through the interface.
• RP 1740 series governs the physical tags that must remain scannable for the messages to be generated.
• Local rules under RP 1744 and Resolution 744 determine when and where particular messages are triggered at a given airport.

Together these instruments create a coherent chain from physical tag to electronic message to automated action.

Real-World Use Cases

• Passenger–Bag Reconciliation – When a bag is unloaded because the passenger did not board, the BHS sends a BPM through the BSI; the airline system matches the bag ID against the passenger record and prevents an unauthorized bag from flying.
• Common-use and self-service bag drops – A passenger using a multi-airline kiosk generates bag data that the BSI routes to the correct carrier’s DCS, regardless of which airline is operating the flight.
• Interline and codeshare transfers – A bag checked on Carrier A and transferring to Carrier B travels through the airport sorter; BSI messages ensure Carrier B’s systems receive the correct status without custom mapping.
• Network messaging services – Global services such as SITA BagMessage implement RP 1746 as the underlying protocol, allowing any connected airline or airport to exchange messages under a single, agreed standard.
• Off-airport bag drop – Bags accepted at hotels or rail stations enter the airport system via BSI messages that already conform to the same rules used inside the terminal.

Industry Challenges

Older BHS controllers may still rely on proprietary protocols, requiring translation layers inside the BSI. High-volume message bursts during peak banks can stress network capacity if buffering and prioritization are inadequately configured. Consistent population of optional but operationally valuable fields depends on disciplined configuration of both the DCS and the BHS. Hybrid environments that mix legacy Type-B traffic with emerging XML or API interfaces must maintain bidirectional mapping to preserve end-to-end visibility.

Future Outlook

The source material indicates that RP 1746 has undergone only limited public revision since the 2010 modernization. As airports adopt RFID, electronic bag tags and more sophisticated reconciliation engines, the same interface principles continue to apply; new message types or transport methods can be accommodated through the normal PSC amendment process. Operators are expected to consult the latest PSC Resolutions Manual or Baggage Reference Manual for the authoritative text and any recent clarifications.

Amendment Status

RP 1746 was published in its modern form in the June 2010 (30th edition) PSC Resolutions Manual as a complete rewrite of earlier interface guidelines. It remains current. Subsequent amendments, if any, appear in later manual editions or official circulars; public sources show no major structural overhaul. The practice continues to be maintained under Passenger Services Conference governance.

Key Takeaways

• RP 1746 defines the standard interface (BSI) between airline IT systems and automated baggage handling systems.
• It was published in modern form in the 2010 PSC Resolutions Manual as a complete rewrite of earlier guidance.
• Core functions include message transport, routing, protocol conversion and format validation.
• Messages conform to the Type-B formats of RP 1745 and carry the 10-digit license-plate number of Resolution 740.
• Reliable delivery is ensured by ACK/NACK sequences, retries and link-monitoring rules.
• Benefits include system flexibility, faster technology deployment, fewer data mismatches and full audit trails.
• The interface is the conduit for the tracking messages required by Resolution 753.
• Real-world applications range from passenger–bag reconciliation and common-use bag drops to interline transfers and global messaging networks.
• Implementation requires coordinated configuration of DCS, BHS and the BSI middleware itself.
• The practice remains current and is updated only through formal PSC processes.

Conclusion

RP 1746 is the quiet but essential middleware standard that allows the physical world of conveyors and sorters to speak fluently with the digital world of airline systems. By prescribing a single set of messaging, addressing and reliability rules, it turns what would otherwise be a patchwork of proprietary links into a coherent, auditable information flow. Airlines gain the freedom to innovate on either side of the interface; airports gain common-use infrastructure that serves every carrier; and passengers gain the higher on-time baggage performance that only reliable, end-to-end data exchange can deliver. In the complex ecosystem of global air travel, that standardized connection remains indispensable.