What are FWB, FHL, FSU and FFM messages in air cargo, and how does terminal software handle them?

FWB, FHL, FSU and FFM are electronic messages that carry cargo data in a standard format between airlines, ground handlers and agents in air cargo. FWB carries the air waybill (AWB) data, FHL the list of house waybills (HAWB) in a consolidated shipment, FSU the status changes of the cargo, and FFM the flight manifest of the cargo loaded on the aircraft. Air cargo terminal software generates these messages from real operational events and imports incoming messages without manual data entry.

Why are the messages standardised?

On its journey a shipment passes through the systems of several organisations: the agent, the airline, the terminal operator and the ground handler at destination. Since each one runs its own software, the same information has to be sent in a common format that everyone can read. In air cargo this is done with messages in defined formats, mostly transmitted over the SITA network. The three letters in a message name indicate its type.

The main message types

• FWB: Electronic data of the master air waybill (MAWB); it carries shipper, consignee, routing, pieces, weight and nature of goods.
• FHL: The list and details of the house waybills (HAWB) under a master waybill; used for consolidated shipments.
• FSU: A status update for the cargo. The status code in the message identifies the event; for example RCS means the cargo was received, FOH that it is on hand at the terminal, DEP that the aircraft has departed and DLV that the cargo was delivered to the consignee.
• FFM: The flight manifest; it shows which cargo travels on which flight and in which pallet or container (ULD).

When are messages sent in export?

In terminal software a message is only as good as its timing and data. In carGObis messages are not a separate task for the user but the natural result of operational steps. At document acceptance, an RCS message is sent automatically when the master AWB entry is complete; sending FWB and FHL can be enabled as an option. When acceptance staff enter dimensions, pieces and weight per MAWB and HAWB on the handheld terminal, an FSU/FOH message goes out over SITA on its own.

When build-up and aircraft operations are finished, the user marks the flight as "Flight Departed". This sends the FFM, FWB, FHL and DEP loading messages over SITA, and cargo covered by the FFM is released from the export bonded warehouse at the same time. For special cargo linked to the manifest, a pre-alert message is sent automatically to the SITA and email addresses at the relevant destinations.

How are incoming messages used in import?

In import the direction is reversed. FWB and FHL messages from the airline are imported into the cargo management system automatically, so the expected record is ready before the cargo leaves the aircraft. If the pallet number arriving from the aircraft matches the message, it is confirmed on the handheld terminal; if not, a warning is raised in the system. For bulk cargo, the piece count is compared with the message, and overages, shortages, damage or off-manifest items are recorded. At release, once the piece count on the invoice is reached a DLV message is sent automatically; if the counts do not match, the system warns the user.

Integration and record keeping

Reliable messaging needs traceability as much as transmission. The carGObis SITA integration runs as a service and logs every transaction. For each outgoing and incoming message it records the sending host name, Windows user name, application user, date and time. Message formats can be updated for each message type by the admin user. In addition to messages, an automatic email goes to operations and the airline when the aircraft manifest is created.

Summary

FWB carries the air waybill data, FHL the house waybills, FSU status changes and FFM the flight manifest. Good air cargo terminal software ties these messages to real operational events captured on handheld terminals, checks incoming messages without manual entry and records who sent each message and when. carGObis runs this flow on the same structure across export, import and domestic operations.