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 (telex) baggage data formats to ADD
IATA Process step | Event (BagEventCode) | Named timestamp | Named timestamp description / Comment | To: Baggage data analytics row - bag oriented | |
---|---|---|---|---|---|
1 | 1 | BagTagGenerated | BTGRT | The "Bag Tag Generated Time" is the DateTimeUTC when the bag tag was generated (printed). This will typically result in the generation of a bag source message (BSM). BTGRT corresponds to the BagEventCode "BagTagGenerated". Always UTC. | Yes |
2 | 1 | BagCheckInAttempt BagChecked | BFCAT | The "Bag First Check in Attempt Time" is the DateTimeUTC when the bag first was attempted checked in. For most bags this will be the same as BACIT as they do not experience a BagRejected event. This corresponds to the first "BagChecked" or "BagCheckInAttempt" BagEventCode. Always UTC. | |
3 | 1 | BagChecked | 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. | |
4 | 1 | BagRejected | The time the bag was first rejected. This will typically be by an SBD (self service baggage drop). Common reasons are too heavy and too big. Always UTC. | ||
5 | 1 | BagRejected | BLRET | The time the bag was last rejected. This will typically be by an SBD (self service baggage drop). Often the same as BFRET. Always UTC. | |
6 | 1 | BagAcceptedByBhs | BABBT | The "Bag Accepted By BHS Time" is the DateTimeUTC when the bag was checked and delivered to the baggage handling system (BHS). This corresponds to the BagEventCode "BagAcceptedByBhs". The bag is now under the control of the BHS and can't be accessed by the passenger. Always UTC. | |
7 | 2 | BagToSecScreen | BTFST | The "Bag To First Security screening Time" is the DateTimeUTC when the first security screening of the bag started. This corresponds to the first BagEventCode "BagToSecScreen". Multiple security screenings of a bag is possible, but will not change BTFST. Always UTC. | |
8 | 2 | BagToSecScreen | BTAST | The "Bag To Automatic Security screening Time" is the DateTimeUTC when the (first) automatic security screening of the bag started. This corresponds to the (first) BagEventCode "BagToSecScreen" for an automatic security screening. Multiple security screenings of a bag is possible, but will not change BTAST. Always UTC. | |
9 | 2 | BagToSecScreen | BTMST | The "Bag To Manual Security screening Time" is the DateTimeUTC when the (first) manual security scan of the bag started. This corresponds to the (first) BagEventCode "BagToSecScreen" for a manual security screening. Multiple security screenings of a bag is possible, but will not change BTMST. Always UTC. | |
10 | 2 | BagToSecScreen | BTL1T | The "Bag To L1 security screening Time" is the DateTimeUTC when the Level 1 security scan of the bag started. This corresponds to the BagEventCode "BagToSecScreen", with some additional information (typically BagEventLocation) identifying it as a Level 1 security screening. Always UTC. | |
11 | 2 | BagToSecScreen | BTL2T | The "Bag To L2 security screening Time" is the DateTimeUTC when the Level 2 security scan of the bag started. This corresponds to the BagEventCode "BagToSecScreen", with some additional information (typically BagEventLocation) identifying it as a Level 2 security screening. Always UTC. | |
12 | 2 | BagToSecScreen | BTL3T | The "Bag To L3 security screening Time" is the DateTimeUTC when the Level 3 security scan of the bag started. This corresponds to the BagEventCode "BagToSecScreen", with some additional information (typically BagEventLocation) identifying it as a Level 3 security screening. Always UTC. | |
13 | 2 | BagToSecScreen | BTL4T | The "Bag To L4 security screening Time" is the DateTimeUTC when the Level 4 security scan of the bag started. This corresponds to the BagEventCode "BagToSecScreen", with some additional information (typically BagEventLocation) identifying it as a Level 4 security screening. Always UTC. | |
14 | 2 | BagToSecScreen | BTL5T | The "Bag To L5 security screening Time" is the DateTimeUTC when the Level 5 security scan of the bag started. This corresponds to the BagEventCode "BagToSecScreen", with some additional information (typically BagEventLocation) identifying it as a Level 5 security screening. Always UTC. | |
15 | 2 | BagFromSecScreen | BFLST | The "Bag From Last Security screening Time" is the DateTimeUTC when the security screening of the bag is finished. This corresponds to the last BagEventCode "BagFromSecScreen". Multiple security scans of a bag is possible, all should update BFLST. Always UTC. | |
16 | 2 | BagFromSecScreen | BFAST | The "Bag From Automatic Security screening Time" is the DateTimeUTC when the (last) automatic security screening of the bag finished. This corresponds to the (last) BagEventCode "BagFromSecScreen" for automatic security screening. Multiple security screenings of a bag is possible, all should update BFAST. Always UTC. | |
17 | 2 | BagFromSecScreen | BFMST | The "Bag From Manual Security screening Time" is the DateTimeUTC when the (last) manual security screening of the bag finished. This corresponds to the (last) BagEventCode "BagFromSecScreen" for a manual security screening. Multiple manual security screenings of a bag is possible, all should update BFMST. Always UTC. | |
18 | 2 | BagFromSecScreen | BFL1T | The "Bag From L1 security screening Time" is the DateTimeUTC when the Level 1 security scan of the bag finished. This corresponds to the BagEventCode "BagFromSecScreen", with some additional information (typically BagEventLocation) identifying it as a Level 1 security screening. Always UTC. | |
19 | 2 | BagFromSecScreen | BFL2T | The "Bag From L2 security screening Time" is the DateTimeUTC when the Level 2 security scan of the bag finished. This corresponds to the BagEventCode "BagFromSecScreen", with some additional information (typically BagEventLocation) identifying it as a Level 2 security screening. Always UTC. | |
20 | 2 | BagFromSecScreen | BFL3T | The "Bag From L3 security screening Time" is the DateTimeUTC when the Level 3 security scan of the bag finished. This corresponds to the BagEventCode "BagFromSecScreen", with some additional information (typically BagEventLocation) identifying it as a Level 3 security screening. Always UTC. | |
21 | 2 | BagFromSecScreen | BFL4T | The "Bag From L4 security screening Time" is the DateTimeUTC when the Level 4 security scan of the bag finished. This corresponds to the BagEventCode "BagFromSecScreen", with some additional information (typically BagEventLocation) identifying it as a Level 4 security screening. Always UTC. | |
22 | BagFromSecScreen | BFL5T | The "Bag From L5 security screening Time" is the DateTimeUTC when the Level 5 security scan of the bag finished. This corresponds to the BagEventCode "BagFromSecScreen", with some additional information (typically BagEventLocation) identifying it as a Level 5 security screening. Always UTC. | ||
23 | 2 | BagSecScreenRejected | The security screening in the baggage handling system has rejected the bag for some reason. This might happen several times depending on BHS design and reject reason. The bag will then most often pass on to a new, higher "level" security screening. | ||
24 | 2/3 | BagToMCS | 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. | |
25 | 2/3 | BagFromMCS | 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. | |
26 | 4 | BagToEBS | BTEBT | The "Bag To Early Bag storage Time" is the DateTimeUTC when the bag first enters an early bag store (EBS). This corresponds to the first BagEventCode "BagToEBS". Multiple visits to EBS by a bag is unlikely, and will not change BTEBT. Always UTC. | |
27 | 4 | BagFromEBS | BFEBT | The "Bag From Early Bag Store Time" is the DateTimeUTC when the bag left the early bag store (EBS) for the last time. This corresponds to the (last) BagEventCode "BagFromEBS". Multiple visits to EBS is unlikely, but when leaving all should update BFEBT. Always UTC. | |
28 | 5 | BagToBhsBin | BTBBT | The "Bag To BHS BinTime" is the DateTimeUTC when the baggage handling system actually delivered the bag for further handling. This will typically be, for baggage handling systems with sorting, when the bag is placed in a bin. This corresponds to the BagEventCode "BagToBhsBin". Always UTC. An estimate of this timestamp is defined by BEBFT. | |
29 | 5 | BagToBhsBinProblem | The bag could not be delivered (to a bin), and had to do something else. Typically circulate the bag until the problem is resolved. | ||
30 | 5/6 | BagFromBhsBin | BFBBT | The "Bag From BHS BinTime" is the DateTimeUTC when the bag is removed from the BHS bin (or any other place a BHS might have delivered the bag). This will typically be when a handler places the bag in a cart or a container. This corresponds to the BagEventCode "BagFromBhsBin". Always UTC. | |
31 | 7 | BagLoaded | BLOAT | The "Bag Loaded Time" is the DateTimeUTC for the last BagLoaded event. The timestamp can indicate when the bag was loaded into a container, or when it was loaded onto an aircraft. This corresponds to the last BagEventCode "BagLoaded". Always UTC. | |
32 | 8 | BagUnloaded | BUNLT | The "Bag Unloaded From Aircraft Time" is the DateTimeUTC when the bag was unloaded from the aircraft. This corresponds to the BagEventCode "BagUnloaded". Always UTC. | |
33 | 10 | BagToTransfer | BTOTT | The "Bag To Transfer Time" is the DateTimeUTC when the bag is delivered to transfer processing. This corresponds to the BagEventCode "BagToTransfer". Always UTC. | |
34 | 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. | |
35 | 12 | BagToPassenger | BTPAT | The "Bag To Passenger Time" is the DateTimeUTC when the bag is made directly available to the passenger. This corresponds to the BagEventCode "BagToPassenger". Always UTC. An estimate of this timestamp is defined by BTPATE. | |
36 | |||||
37 | 1-13 | BagInfoReceived | Information about a bag has been received. This will typically be from an airline/handler and in the form of a BSM. NB! This is not an event that actually happened to a bag. The first BSM received will typically result in a BagTagGenerated event. | ||
38 | 1-13 | BagTagScanned | The bag tag was scanned at some location, either manually or automatic. | ||
39 | 1-13 | BagBhsEvent | The baggage handling system (BHS) generated a bag event that doesn't fit any of the specific events. BagEventLocation and/or BagEventDescription can be used to derive what really happened. |
Durations
Based on the events and timestamps above the following durations have been defined.
Duration | Description | To: Baggage data analytics row - bag oriented |
---|---|---|
The "Bag Total Time In BHS" is the duration the bag has spent in the baggage handling system. BagTotalTimeInBhs = BTBBT - BACIT | Yes | |
BagNetTimeInBhs | The "Bag Net Time In BHS" is the duration the bag has spent in the baggage handling system, excluding time spent in early bag storage. BagNetTimeInBhs = BagTotalTimeInBhs - BagTotalTimeInEbs | Yes |
BagTotalTimeInMcs | The "Bag Total Time In MCS" is the duration the bag has spent in a manual coding station (MCS) in total. Multiple visits to MCS by a bag is possible and must be added to provide a correct BagTotalTimeInMcs. If the bag is only once in MCS then BagTotalTimeInMcs = BFMCT - BTMCT | Yes |
BagTotalTimeAtSecScreen | The "Bag Total Time At Security Screening" is the total duration the bag has spent at security screening. BagTotalTimeAtSecScreen = BFLST - BTFST | Yes |
BagTimeAtAutSecScreen | The "Bag Time At Automatic Security Screening" is the duration the bag has spent at automatic security screening. BagTimeAtAutSecScreen = BFAST - BTAST | Yes |
BagTimeAtManSecScreen | The "Bag Time At Manual Security Screening" is the duration the bag has spent at manual security screening. BagTimeAtManSecScreen = BFMST - BTMST | Yes |
BagTotalTimeInEbs | The "Bag Total Time In EBS" is the duration the bag has spent in an EBS in total. Multiple visits to EBS by a bag is rare, but possible and must be added to provide a correct BagTotalTimeInEbs. If the bag is only once in EBS then BagTotalTimeInEbs = BFEBT - BTEBT | Yes |
BagBhsDeliveryAttemptsTime | The "Bag BHS Delivery Attempts Time" is the duration the bag has spent trying to be delivered to a bin. Typically this is because the bin is full, or some other BagToBhsBinProblem. | Yes |
BagBhsTransportTime | "Bag BHS Transport Time" is the duration the bag has spent being transported in the baggage handling system (BHS). | Yes |
BagBhsTimeExceededBy | The "Bag BHS Time Exceeded By" is the duration the bag has spent in the baggage handling system exceeding any service level agreement (SLA) giving the maximum allowed time (BagBhsSlaTime). The maximum allowed time will vary from BHS to BHS, and might also vary based on business rules. | Yes |
BagBhsTimeExceededGroup | The "Bag BHS Time Exceeded Group" is a grouping, based on business rules, of bags that have spent too much time in the BHS. Grouping is business/airport specific. | Yes |
Counts
The following baggage related counts have been defined:
Count | Description | To: Baggage data analytics row - bag oriented |
---|---|---|
BagEventCount | The BagEventCount is normally for one bag on one airport, but can be for one bag on all airports, for one flight or for any given period. | Yes, per bag per airport |
BagInfoMsgCount | The number for BagInfoReceived events for a bag on an airport. This would normally correspond to the number of BIMs received for one bag on one airport, minus one. The first BIM received would normally be a BSM that will trigger a BagTagGenerated event. | Yes, per bag per airport |
BagTagsGenerated | Normally the number of bag tags generated for one flight leg on one airport, but can be for other "things" as well (a printer). | No |
BagsCheckedIn | Normally the number of bags checked in for one flight leg from one airport. Should be equal or higher than BaggageCountLoaded, unless rush bags mess up the loaded count. | No, pr. flight |
BagToMcsCount | The BagToMcsCount is the number of times a bag has been to a manual coding station on one airport. | Yes |
BagsDeliveredToBhsFlightBin | The number of bags delivered to the bin(s) allocated to one flight. | No, pr. flight |
BagsDeliveredToBhsProblemBin | The number of bags delivered to a problem bin for one flight, and not the bin(s) allocated to one flight. | No, pr. flight |
BagBhsBinDeliveryAttempts | The number of times the baggage handling system has tried to deliver a given bag to a bin. Should normally be '1', but can be much more in bin full conditions or with other BHS related problems. | Yes |
BaggageCountLoaded | Number of bags loaded onto an aircraft. | No, pr. flight |
BaggageCountUnloaded | Number of bags unloaded off an aircraft. | No, pr. flight |
Bag status indicators
The following boolean indicators have been defined:
Indicator | Description | To: Baggage data analytics row - bag oriented |
---|---|---|
BagWasRejected | BagWasRejected indicates if the bag was rejected one or more times during checkin/delivery of the bag. | Yes |
BagWasDeliveredToBhsInTime | BagWasDeliveredToBhsInTime indicates if the bag was delivered to the baggage handling system in time. The definition of "in time" is system/airport dependent, but will typically involve BagSOBT and BagBhsSlaTime.
| Yes |
BagWasDeliveredToBhsLate | BagWasDeliveredToBhsLate indicates if the bag was delivered to the baggage handling system late. The definition of "late" is system/airport dependent, but will typically involve BagSOBT and BagBhsSlaTime. Even if the bag is delivered late it might be in time to be loaded on the aircraft. | Yes |
BagWasDeliveredToBhsTooLate | BagWasDeliveredToBhsTooLate indicates if the bag was delivered to the baggage handling system too late for it to be loaded on the aircraft. The definition of "too late" is system/airport dependent, but will typically involve BagSOBT and BagBhsSlaTime. | Yes |
BagWasDeliveredFromBhsInTime | BagWasDeliveredFromBhsInTime indicates if the bag was delivered from the baggage handling system in time (to be loaded). The definition of "in time" is system/airport dependent, but will typically involve BagSOBT. | Yes |
BagWasDeliveredFromBhsLate | BagWasDeliveredFromBhsLate indicates if the bag was delivered from the baggage handling system late, and is in danger of not being loaded. The definition of "late" is system/airport dependent, but will typically involve BagSOBT. | Yes |
BagWasDeliveredFromBhsTooLate | BagWasDeliveredFromBhsTooLate indicates if the bag was delivered from the baggage handling system too late, and will not be loaded. The definition of "too late" is system/airport dependent, but will typically involve BagSOBT. | Yes |
BagWasSentToMcs | BagWasSentToMcs indicates that the bag was sent to a manual coding station (MCS) at least once. This will often be because the bag tag couldn't be read automatically. Other reasons are also possible. | Yes |
BagWasSentToProblemBin | BagWasSentToProblemBin indicates that the bag was sent to a problem bin. There are many possible reasons for this. | Yes |
BagBsmWasProblem | BagBsmWasProblem indicates that there were a problem with a BSM at least once. Often this will be a missing BSM. | Yes |
BagTagWasNotSeenInBhs | BagTagWasNotSeenInBhs indicates that the bag tag generated (printed), but wasn't registered in the BHS. There might be several reasons for this, including tag not used by passenger, bag moved tail to tail, bag brought to gate by passenger with tag printed at gate. | Yes |
BagHasLoadedEvent | BagHasLoadedEvent indicates that the bag was loaded onto an aircraft. In practice this means that at least one BagLoaded event has been registered. | Yes |
BagWasLost | BagWasLost indicates that the bag has been registered as lost in SITA WorldTracer, or that it is known by other means that the bag was not loaded onto the correct aircraft. A lost bag is a bag that isn't on the same aircraft as the owner. | Yes |