The process
IATA has the following figure which describes the baggage process at a high level.
The figure is a good description of the high level process. However, to understand what happens inside a baggage handling system (BHS) it is necessary with a more detailed understanding of the steps 2, 3, 4 and 5.
Events and timestamps
It is necessary to collect data about a bag from many places in the baggage process to be able to:
- to document what actually happened to a bag, including finding it if it became lost.
- predict in real time if a bag is likely to become a problem bag, which makes it possible to avoid it.
- analyze the baggage processes to find problem areas and to document conformance to any service level agreement.
To easily understand the collected data the data elements need to be strictly defined and the same set of data definitions used from all data sources. The data sources might send data using different formats. All formats should then be transformed to the common format.
All further discussion here is based on data elements defined by the Airport Data Dictionary, Mapping from IATA data formats are documented here: Mapping of IATA baggage data formats to ADD
| IATA Process step | Event (BagEventCode) | Timestamp | Comment |
|---|---|---|---|
| 1 | BagTagPrinted | BTPRT | Not all bag tags printed are actually used on baggage that are checked |
| 1 | BagManualChecked | BACIT | The "Bag Actual Checked In Time" is the DateTimeUTC when the bag was checked and delivered to the baggage handling system. This corresponds to the BagEventCode "BagChecked". This should occur when it is impossible for the passenger to decide not to check the baggage after all. It is however possible for the bag to be rejected for technical reasons (too long). Always UTC. |
| 1 | BagSbdChecked | BACIT | As above. |
| 1 | BagRejected | Can happen several times for a bag, typically from a self service baggage drop (SBD). | |
| 1 | BhsAcceptBag | BAABT | |
| 2 | BhsSecScanStart | BSSST | With multi level security this event can occur several times. The timestamp will stay the same. |
| 2 | BhsSecScanFinished | With multi level security this can occur several times. | |
| 2 | BhsSecScanRejected | With multi level security this can occur several times. | |
| 2/3 | BhsBagToMCS | BTMCT | The "Bag To Manual Coding station Time" is the DateTimeUTC when the bag first enters a manual coding station (MCS). This corresponds to the BagEventCode "BagToMCS". Multiple visits to MCS by a bag is possible, but will not change BTMCT. Always UTC. The event can occur several times, but will not update the timestam. |
| 2/3 | BhsBagFromMCS | BFMCT | The "Bag From Manual Coding station Time" is the DateTimeUTC when the bag enters a manual coding station (MCS) for the last time. This corresponds to the last BagEventCode "BagFromMCS". Multiple visits to MCS by a bag is possible. Each visit will update the BFMCT. Always UTC. This can occur several times. The timestamp is updated each time. |
| 4 | BhsBagToEBS | Most likely only once. | |
| 4 | BhsBagFromEBS | Most likely only once. | |
| 5 | BhsDeliverBag | BABFT | |
| 5/6 | BagFromBHS | ||
| 7 | BagOnAircraft | BAOAT | |
| 8 | BagOffAircraft | BAUAT | |
| 10 | BagToTransfer | BATTT | |
| 11 | BagOnBelt | BAOBT | The Bag Actual On Belt Time is the DateTimeUTC when the bag actually is placed on the baggage belt/carousel and soon will be ready for pick up by the passenger. This corresponds to the BagEventCode "BagOnBelt". Always UTC. |
| 12 | BagToPassenger | BATPT | It is rare to have this timestamp. |
| 1-10 | BagInfoReceived | ||
| 1-10 | BagTagScanned |
Durations
Based on the events and timestamps above the following durations have been defined.
| Duration | Description | ||
|---|---|---|---|
| BIMCD | |||