Term | BagEventCode |
---|
Business term | Bag Event (Code) |
---|
Description | Code for an event that happened to a bag (Baggage). Often the event will really be for a BagTag as that is what is scanned, and it is "assumed" that a bag is associated with it. Some events are predefined, see "Legal values" below. Other, system specific, events can be added as needed. |
---|
Legal values | The following is a predefined set of event strings. Others can be added. - BagTagGenerated
A BagTag is generated (usually printed). It is however not guaranteed to be used. This event will typically be the result of the first BSM received for a bag tag. Timestamp: BTGRT - BagCheckInAttempt
The bag is tried checked in at some location, typically a SBD (Self service Baggage Drop). This event will typically be followed by a BagChecked or BagRejected event. Related timestamp: BFCAT - BagChecked
The bag is checked in at some location. BagEventLocation can typically be used to determine if BagCheckinType is "Manual" or "SBD". Timestamp: BACIT. That the bag is checked means that it is accepted by the airline, typically a DCS. The bag might still be rejected (BagRejected) by the baggage handling system, for instance due to size. Also, the passenger might still grab the bag. It is when the BagAcceptedByBhs event occurs that the bag is unavailable to passengers and irreversibly on it's way. - BagRejected
The bag was rejected at some point, typically a SBD (Self service Baggage Drop). It is possible for a bag to be rejected several times and then accepted. - BagAcceptedByBhs
The baggage handling system (BHS) has accepted the bag and controls it until it is delivered somewhere. Timestamp: BABBT. The bag is no longer accessible for passengers and is irreversibly on its way.
- BagToSecScreen
The bag is entering security screening, automated or manual, in the baggage handling system. Multi level security screening will often result in several events of this type. BagEventLocation and/or BagEventDescription can be used to derive which security screening actually occurred. Relevant timestamps: BTFST, BTAST, BTMST, BTL1T, BTL2T, BTL3T, BTL4T, BTL5T - BagFromSecScreen
The bag is leaving security screening. Relevant timestamp: BFLST, BFAST, BFMST, BFL1T, BFL2T, BFL3T, BFL4T, BFL5T - 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.
BagToMCS The bag arrives at a manual coding station (MCS). Timestamp: BTMCT BagFromMCS The bag leaves a manual coding station (MCS). Timestamp: BFMCT
- BagToEBS
The bag arrives at early bag storage (EBS). Timestamp: BTEBT BagFromEBS The bag is retrieved from early bag storage (EBS). Timestamp: BFEBT
BagToBhsBin The baggage handling system has processed the bag and have delivered to a handler. The bag is placed it somewhere accessible, typically in a bin. Relevant timestamps: BEBFT, BTBBT
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.
- BagFromBhsBin
The bag has been removed from the baggage handling system (BHS) bin, typically to be placed in carts or containers. Timestamp: BFBBT
- 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.
- BagLoaded
The bag is loaded onto the aircraft, or into a container. BagEventDescription will typically be used to indicate where. BagLoaded can occur twice if the bag first is loaded into a container, and the container then is loaded into an aircraft. Relevant timestamp: BLOATValues for BagEventDescription to indicate where the bag was loaded: - "Aircraft"
- "Container"
- "Unknown"
- BagUnloaded
The bag has been unloaded from the aircraft/container. Relevant timestamp: BUNLT
- BagToTransfer
The bag has been delivered to the transfer process. Relevant timestamp: BTOTT
- BagOnBelt
The bag has been placed on the baggage belt (BaggageClaimUnit). Timestamp: BAOBT - BagToPassenger
The bag has been delivered to a place where it is directly accessible to the passenger. This will typically be a belt/carousel the passenger can access. Relevant timestamps: BTPATE, BTPAT
- 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.
- BagTagScanned
The bag tag was scanned at some location, either manually or automatic.
- BagLost
The bag is reported lost. This will most often mean that it is reported to SITA WorldTracer.
- BagTagDeleted
The bag tag was deleted.
|
---|
Comments | BagTagDeleted added 2019-06-30 |
---|
Status | Approved 2018-10-01 |
---|
XML type | string (24) |
---|
Ref from |
-
BABBT
,
-
BACIT
,
-
BagCheckInData
,
-
BagEvent
,
-
BagEvent
,
-
BagEventAirportIATA
,
-
BagEventData
,
-
BagEventData
,
-
BagEventDescription
,
-
BagEventLocation
,
-
BagEventTimestamp
,
-
Baggage process and data elements - airport perspective
,
-
BagScanData
,
-
BAOBT
,
-
BEBFT
,
-
BETPT
,
-
BFAST
,
-
BFBBT
,
-
BFCAT
,
-
BFEBT
,
-
BFLST
,
-
BFMCT
,
-
BFMST
,
-
BhsEventData
,
-
BLOAT
,
-
BTAST
,
-
BTBBT
,
-
BTEBT
,
-
BTFST
,
-
BTL1T
,
-
BTL2T
,
-
BTL3T
,
-
BTL4T
,
-
BTL5T
,
-
BTMCT
,
-
BTMST
,
-
BTOTT
,
-
BTPAT
,
-
BTPATE
,
-
BUNLT
,
-
Example mapping from IATA BagXML to ADD
,
-
Mapping of IATA (telex) baggage data formats to ADD
,
-
SubmitBagEventData
,
-
SubmitBagEventData
,
-
test
|
---|
Labels | |
---|