The table below contains all terms that have been labeled with "baggage", and this should be all baggage related terms. List of text codes indicating valid type(s) of identification that may be required for the specified carrier. Typically used to identify passengers when dropping a bag at a self serve bag drop station. Legal values are system specific. Identifies a load unit type aircrafts. Typically used for baggage and cargo. Identifies an actual load unit, ref. LoadUnitType. Estimated arrival time for something at the relevant location. The maximum weight, in Gram, a bag can be before it must be sent as special (oversize, overweight) baggage. The weight of any BHS tub used. To compensate for total weight at airports where tub is used. The BhsTubWeight will be substracted from the bag weight. Weight tolerance margin (gram) between subsequent weight requests. The different measurements must be within BhsStableWeightTolerance to be accepted. Number of weight requests to provide stable weight (will be 1 if bag drop scale always delivers stable weight). Weight tolerance margin (gram) to be subtracted from measured stable weight. The interval (duration) between multiple (BhsStableWeightRequests) weight requests to provide stable weight. The BagLocation where this batch is to be loaded. Unique identifier, for a given period of time, that identifies a batch of bags on a given airport. TimestampUTC when the relevant BHS batch event occurred. Descriptive text for an event (BhsBatchEventCode) that happened to a BHS batch. The descriptions are system specific, and there can be multiple descriptions for the same BhsBatchEventCode. Code for an event that happened to a BHS batch, typically identified with BhsBatchId. Some events are predefined, see "Legal values" below. Other, system specific, events can be added as needed. The number of bags in a batch, at a given point in time. The precise weight, in Gram, of a bag. The FlightDepartureDate of the flight the bag is planned to depart on from a given airport. Always DateUTC. A codes indicating the status of a bag check in attempt. Legal values are system specific. The maximum bag weight, one individual bag, this carrier supports. A GUID identifying a a transaction in some context. This will often be multiple operations that are related in some way. A GUID identifying a passenger in some context. Is the relevant DCS supported in some context. Is a DCS that is supported (DcsIsSupported) actually available at the current time. A GUID identifying a bag in some context. ?? The maximum weight the BHS can accept. The minimum weight the BHS can accept. Uniquely identifies a bag drop unit on an airport. The AirportIATA code for the next airport the bag should be sent to. Estimated time for BeltFirstBag. The number of bags in some context. The scheduled date and time that the aircraft a bag is planned to depart from its parking position. Always DateTimeUTC. The number of bags that can be loaded onto this aircraft on this airport. This includes local bags, and expected transfer bags. "Bag BHS Transport Time" is the duration the bag has spent being transported in the baggage handling system (BHS). 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. 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. The "Bag BHS SLA Time" is the duration a given BHS has, according to any SLA, to process the bag. Usually this is from the passenger checks in the bag to when the bag is delivered in a baggage bin and available to the handler. The SLA time will vary from BHS to BHS, and might also vary based on business rules. Used to calculate BagBhsTimeExceededBy. 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. The "Bag To Passenger Time Estimate" is the DateTimeUTC when the bag is estimated to be made directly available to the passenger. This is an estimate of when the BagEventCode "BagToPassenger" will occur. This is an estimate of the timestamp BTPAT. Always UTC. 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. The "Bag To Transfer Time" is the DateTimeUTC when the bag is delivered to transfer processing. This corresponds to the BagEventCode "BagToTransfer". Always UTC. 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. 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 "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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. Code/string defining which baggage segregation that are associated with the relevant Bin. Codes are system/handler specific. A baggage bin. Typically where a baggage handling system places the bags that are sorted. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. The Bag Estimate To Passenger Time is the DateTimeUTC when the bag is estimated to be ready to be picked up by the passenger. This is an estimate for the BagEventCode "BagToPassenger". Always UTC. The Bag Estimated BHS Finish Time is the DateTimeUTC when the baggage handling system estimates that the bag will be finished and ready for further handling. This will typically be, for baggage handling systems with sorting, when the bag is placed in a bin. This is an estimate for the BagEventCode "BagToBhsBin". Always UTC. 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. BagWasSentToProblemBin indicates that the bag was sent to a problem bin. There are many possible reasons for this. 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. BagWasRejected indicates if the bag was rejected one or more times during checkin/delivery of the bag. 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. 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. 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. 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. 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. 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. 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. 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 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 The "Bag Total Time In BHS" is the duration the bag has spent in the baggage handling system. BagTotalTimeInBhs = BTBBT - BACIT The "Bag Total Time At Security Screening" is the total duration the bag has spent at security screening. BagTotalTimeAtSecScreen = BFLST - BTFST The BagToMcsCount is the number of times a bag has been to a manual coding station on one airport. The "Bag Time At Manual Security Screening" is the duration the bag has spent at manual security screening. BagTimeAtManSecScreen = BFMST - BTMST The "Bag Time At Automatic Security Screening" is the duration the bag has spent at automatic security screening. BagTimeAtAutSecScreen = BFAST - BTAST 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. A unique bag identifier to make statistics and business intelligence easier. Solves the problem that the BagTagNumber is reused quite often. The identifier is 10 characters to make it the same length as the BagTagNumber, but clearly something else. The status of a "Bag Tag" on one airport. Normally the number of bag tags generated for one flight leg on one airport, but can be for other "things" as well (a printer). The location where the bag tag was printed. The location is identified with a text string that is meaningful in the context it is used. The way/codes to identify a location will typically vary across the different implementations. Use the same values as used by BagEventLocation for the BagTagGenerated event - if this represented printing of a bag tag. A 10 digit bag tag number compliant with GDPR. This means that the BagTagSerialNumber part is replaced by a "meaningless" number. The BagTagLeadingDigit and BagTagIssuerCode are not changed. See also BagTagNumber. The 10 digit bag tag (licence plate) number as defined by IATA. The BagTagNumber is a concatenation of BagTagLeadingDigit, BagTagIssuerCode and BagTagSerialNumber. The AirlineIATA code corresponding to the BagTagIssuerCode. The SOBT for the flight the bag departed/is supposed to depart on. The flight is defined by BagDepartureFlightId. Always UTC. Indication if baggage is unconventional size or weight. The number of bags delivered to a problem bin for one flight, and not the bin(s) allocated to one flight. The number of bags delivered to the bin(s) allocated to one flight. 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. A bag might get a new BagTagNumber for different reasons, see BagNewTagNumber. For a bag with a new tag, this is the previous BagTagNumber for the bag. The AirportIATA code for the airport the bag came from. Not relevant for bags that start their journey on "this" airport. The bin/location where the bag is planned to be delivered to by the baggage handling system. The location is identified with a text string that is meaningful in the context it is used. The way/codes to identify a location will typically vary across the different implementations. Use the same values as used by BagEventLocation for the BagToBhsBin event. A bag that becomes "lost" will in some cases get a new bag tag. Bags might also get new tags for different reasons. This is the new BagTag for the bag. See also BagPreviousTagNumber. 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 The BagIrregularityCode associated with the bag being registered as lost. The FlightId for the flight where the bag became lost. Not guaranteed to be correct, best effort value. The date the bag was lost. Mainly to help make the BagTagNumber unique on the BagLostAirportIATA. Not guaranteed to be correct, best effort value. Always UTC. Open ended string containing JSON formatted data. Contains any additional information about the lost bag as name:value pairs. For example: Text string that defines the location of a bag in some way. The location string that is meaningful in the context it is used. The way/codes to identify a location will typically vary across the different implementations. BagIsRush indicates if the bag is a RUSH bag or not. A RUSH bag is an unaccompanied (expedited) bag as specified in IATA Resolution 740, attachment 'K' and 'L'. BagIsPriority indicates if the bag is a priority bag or not. BagIsCrew indicates if the bag is a crew bag or not. 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. A standard IATA baggage information message as a text string. Start and end token ("BSM"/ENDBSM, BPM/ENDBPM, ....") included. BagHasLoadedEvent indicates that the bag was loaded onto an aircraft. In practice this means that at least one BagLoaded event has been registered. The HandlerCode for the Handler that are responsible for handling the baggage at departure. The HandlerCode for the Handler that are responsible for handling the baggage at arrival. The HandlerCode for the Handler that is responsible for handling the baggage. Weight in kilos of all baggage actually on board the aircraft. The reason for the first rejection of a check in attempt for the bag. This would typically be at a self service baggage drop (SBD). The reason would typically come from the BagEventDescription of the first BagRejected event. The AirportIATA code for the final airport the bag should be sent to. Timestamp defining when a BagEventCode occurred. The location where a BagEventCode occurred. The location is identified with a text string that is meaningful in the context it is used. The way/codes to identify a location will typically vary across the different implementations. The relevant error code for events that indicate some form of failure, for instance BagRejected, BagSecScreenRejected and BagToBhsBinProblem. Having the error code in a separate element makes it easier to process the different errors. Any description of the error should be in BagEventDescription. Descriptive text for an event (BagEventCode) that happened to a bag (Baggage). The descriptions are system specific, and there can be multiple descriptions for the same BagEventCode. 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. The AirportIATA code associated with the BagEventLocation where a BagEventCode occurred. An event that happened to a bag (Baggage). The elements used to describe a bag event is system specific, but will typically consist of at least: Indicates how the bag was checked in. This can typically be derived from BagEventLocation. The location where a bag was checked in. This will typically be the BagEventLocation of the BagChecked event. The BagCheckinLocation must correspond to the BagCheckinType. For instance, if the BagCheckinType = "SBD" then the location should be one of the self service baggage drop locations. The category ("CheckIn", "Transfer", "Final") this bag belongs to. BagCanBeTransported indicates the bag can be transported. BagCanBeLoaded indicates if the bag is can be loaded (onto an aircraft) or not. BagBsmWasProblem indicates that there were a problem with a BSM at least once. Often this will be a missing BSM. 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. 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. The FlightId for the flight the bag arrived on. The AOBT for the flight the bag departed on. The flight is defined by BagDepartureFlightId. Always UTC. Standard IATA baggage information codes as defined in IATA Recommended Practice 1745, attachment A. BagPlannedBin indicates the bin that was the planned bin for this bag. 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. 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. Weight in kilos of all cabin baggage actually on board the aircraft. . Standard IATA baggage irregularity codes as defined in IATA Recommended Practice 1743. Weight in Kilos of all equipment unloaded. Weight in kilos of cabin baggage unloaded. The "Bag First Event Date" is the date of the first bag event for a given bag tag on a given airport. NB! Tighten description.What is the first event on an airport as opposed to the first event for a bag The serial number part of a BagTagNumber, allocated by the issuing organization (identified by BagTagIssuerCode). The 3-digit IATA allocated code identifying the airline that has issued the bag tag. See BagTagNumber for information about the other parts, and AirlineIATAThreeNumeric for more information about the 3-digit IATA code. The leading digit of a BagTagNumber. The leading digit typically says something about how the bag tag was generated, but is not required to do so by IATA. Airlines are free to use the leading digit differently. Please see BagTagNumber for more details. Bag tags, also known as baggage tags, baggage checks or luggage tickets, have traditionally been used by bus, train, and airline carriers to route checked luggage to its final destination. The passenger stub is typically handed to the passenger or attached to the ticket envelope. Airline bag tags are identified by BagTagNumber. The number of bags that has been checked in at the same time. Indicator set to true if the passenger has weapons, ammunition or explosives in checked baggage. Indicator set to true if the passenger has pets in the cabin. Indicator set to true if the passenger has animals in checked baggage. The width (in Centimeter) of one bag. The weight (in kilos) of one bag. Indication if baggage contains special goods. The time a bag scan operation occurred. Always UTC. The location where a bag scan operation occurred. The location is identified with a text string that is meaningful in the context it is used. The way/codes to identify a location will typically wary across the different implementations. A BagScanAction will typically occur at the location. The geographical location where a bag scan operation occurred. The location is typically identified by an entity containing at least Latitude and Longitude, and most likely Elevation. More detailed information about this bag scan. The airport, IATA code, where a bag scan operation occurred. The action being done when a bag scan operation occurred. The action is identified with a text string that is meaningful in the context it is used. The way/codes to identify an action will typically wary across the different implementations. A number indicating the sequence a bag is loaded into "something". The length (in Centimeter) of one bag. The height (in Centimeter) of one bag. A number identifying a group of persons which have their baggage pooled. The number is unique within the flight. (I.e. all persons belonging to this group have the same BaggagePoolId). Note! BaggagePoolId should not be confused with the term "PassengerGroupId" which is used to group passengers for seating purposes. The dimensions of one bag. Typically an entity containing BagLength, BagWidth and BagHeight. A precise identification of the container where the bag currently is, for instance a serial number. Can also be the aircraft compartment where the bag is loaded. As BeltFirstBag, but local time. Weight in kilos of baggage unloaded off an aircraft. Weight in kilos of baggage loaded onto an aircraft. Description or name of the BaggageClaimUnit. Number of bags loaded onto an aircraft. Number of bags unloaded off an aircraft. Baggage belt (carousel) onto which passenger bags are loaded for collection by passengers on arrival flights. Checked in passenger baggage. UTC time the last passenger bag was loaded onto baggage a belt (carousel) UTC time the first passenger bag was loaded onto a baggage belt (carousel).Term Description Status XML type Labels PassengerIdentificationRequirement Approved 2023-05-19 string (16) LoadUnitType
See https://vrr.aero/knowledge-center/uld-info/uld-id-code/ and https://en.wikipedia.org/wiki/Unit_load_device for details.Approved 2023-05-19 string (8) LoadUnitId Approved 2023-05-19 string (16) EstimatedArrAtLocation Approved 2023-05-19 DateTimeUTC CarrierBagHeavyWeightLimit Approved 2023-05-19 Gram BhsTubWeight Approved 2023-05-19 Gram BhsStableWeightTolerance Approved 2023-05-19 Gram BhsStableWeightRequests Approved 2023-05-19 Count BhsStableWeightMargin Approved 2023-05-19 Gram BhsStableWeightInterval Approved 2023-05-19 duration BhsBatchLoadLocation Approved 2023-05-19 BagLocation BhsBatchId Approved 2023-05-19 GUID BhsBatchEventTimestamp Approved 2023-05-19 TimestampUTC BhsBatchEventDescription Approved 2023-05-19 string (128) BhsBatchEventCode Approved 2023-05-19 string (24) BhsBatchBagCount Approved 2023-05-19 Count BagWeightPrecise Approved 2023-05-19 Gram BagDepartureFlightDepartureDate Approved 2023-05-19 DateUTC BagCheckInStatus Approved 2023-05-19 string (8) CarrierMaximumWeight Deprecated Gram TransactionId Approved 2022-12-16 GUID PassengerGuid Approved 2022-12-16 GUID DcsIsSupported Approved 2022-12-16 boolean DcsIsAvailable Approved 2022-12-16 boolean BagGuid Approved 2022-12-16 GUID BhsHeavyWeightLimit Proposal Gram BhsMaximumWeight Proposal Gram BhsMinimumWeight Proposal Gram BagDropUnit Approved 2022-05-20 string (16) BagNextAirportIATA Approved 2018-11-13 AirportIATA BeltFirstBagEstimate Approved 2022-01-14 DateTimeUTC BaggageCount Approved 2022-01-14 Count BagDepartureSOBT Approved 2022-01-14 DateTimeUTC BagCanBeLoadedCount Approved 2022-01-14 Count BagBhsTransportTime
Calculation: BagBhsTransportTime = BagTotalTimeInBhs - (BagTotalTimeInMcs + BagTotalTimeInEbs + BagTimeAtManSecScreen + BagBhsDeliveryAttemptsTime)Approved 2022-01-14 duration BagBhsTimeExceededGroup Approved 2022-01-14 string(16) BagBhsTimeExceededBy Approved 2022-01-14 duration BagBhsSlaTime Approved 2022-01-14 duration BUNLT Approved 2018-10-01 DateTimeUTC BTPATE Approved 2018-10-01 DateTimeUTC BTPAT Approved 2018-10-01 DateTimeUTC BTOTT Approved 2018-10-01 DateTimeUTC BTMST Approved 2018-10-01 DateTimeUTC BTMCT Approved 2018-10-01 DateTimeUTC BTL5T Approved 2018-10-01 DateTimeUTC BTL4T Approved 2018-10-01 DateTimeUTC BTL3T Approved 2018-10-01 DateTimeUTC BTL2T Approved 2018-10-01 DateTimeUTC BTL1T Approved 2018-10-01 DateTimeUTC BTGRT Approved 2019-03-12 DateTimeUTC BTFST Approved 2019-03-12 DateTimeUTC BTEBT Approved 2019-03-12 DateTimeUTC BTBBT Approved 2019-03-12 DateTimeUTC BTAST Approved 2019-03-12 DateTimeUTC BLRET Approved 2019-03-12 DateTimeUTC BLOAT Approved 2019-03-12 DateTimeUTC BinSegregationCode Approved 2020-01-28 string (16) Bin Approved 2020-01-28 BagLocation BFRET Approved 2019-03-12 DateTimeUTC BFMST Approved 2019-03-12 DateTimeUTC BFMCT Approved 2019-03-12 DateTimeUTC BFLST Approved 2019-03-12 DateTimeUTC BFL5T Approved 2019-03-12 DateTimeUTC BFL4T Approved 2019-03-12 DateTimeUTC BFL3T Approved 2019-03-12 DateTimeUTC BFL2T Approved 2019-03-12 DateTimeUTC BFL1T Approved 2019-03-12 DateTimeUTC BFEBT Approved 2019-03-12 DateTimeUTC BFCAT Approved 2019-03-12 DateTimeUTC BFBBT Approved 2019-03-12 DateTimeUTC BFAST Approved 2019-03-12 DateTimeUTC BETPT Approved 2019-03-12 DateTimeUTC BeltLastBagLocal
As BeltLastBag, but local time.Approved 2013-04-04 DateTimeLocal BEBFT Approved 2019-03-26 DateTimeUTC BAOBT Approved 2019-03-12 DateTimeUTC BagWasSentToProblemBin Approved 2018-11-13 boolean BagWasSentToMcs Approved 2018-11-13 boolean BagWasRejected Approved 2018-11-13 boolean BagWasLost Approved 2018-11-13 boolean BagWasDeliveredToBhsTooLate Approved 2019-03-12 boolean BagWasDeliveredToBhsLate Approved 2019-03-12 boolean BagWasDeliveredToBhsInTime Approved 2019-03-12 boolean BagWasDeliveredFromBhsTooLate Approved 2019-08-13 boolean BagWasDeliveredFromBhsLate Approved 2019-08-13 boolean BagWasDeliveredFromBhsInTime Approved 2019-08-13 boolean BagTotalTimeInMcs Approved 2019-08-13 duration BagTotalTimeInEbs Approved 2019-08-13 duration BagTotalTimeInBhs
If the bag is rejected for technical reasons BagTotalTimeInBhs should be reset.Approved 2019-08-13 duration BagTotalTimeAtSecScreen Approved 2019-08-13 duration BagToMcsCount Approved 2019-08-13 Count BagTimeAtManSecScreen Approved 2019-08-13 duration BagTimeAtAutSecScreen Approved 2019-08-13 duration BagTagWasNotSeenInBhs Approved 2019-08-13 boolean BagTagUnique Approved 2019-10-15 string (10) BagTagStatus Proposal string(16) BagTagsGenerated Approved 2019-08-13 Count BagTagPrintedLocation Approved 2018-09-24 BagLocation BagTagNumberGDPR Approved 2019-10-15 string (10) BagTagNumber Approved 2017-05-16 string (10) BagTagIssuerAirlineIATA Approved 2019-08-13 AirlineIATA BagSOBT Approved 2019-08-13 DateTimeUTC BagSizeIndicator Approved 2017-03-16 string (3) BagsDeliveredToBhsProblemBin Approved 2018-11-13 Count BagsDeliveredToBhsFlightBin Approved 2018-11-13 Count BagsCheckedIn Approved 2018-11-13 Count BagPreviousTagNumber Approved 2019-11-12 BagTagNumber BagPreviousAirportIATA Approved 2018-11-13 AirportIATA BagPnrCodeGDPR Approved 2019-10-15 PnrCodeGDPR BagPnrCode Approved 2018-11-13 PnrCode BagPlannedBin Approved 2018-09-24 BagLocation BagNewTagNumber Approved 2019-11-12 BagTagNumber BagNetTimeInBhs Approved 2019-11-12 duration BagLostIrregularityCode Approved 2019-11-12 BagIrregularityCode BagLostFlightId Approved 2019-11-12 FlightId BagLostDate Approved 2019-11-12 DateUTC BagLostAirportIATA
The AirportIATA code where the bag is reported to have been lost.Approved 2019-11-12 AirportIATA BagLostAdditionalData
{
"CARRIER_CD ": "XX",
"ROUTING": "PUS/PEK/CPH/OSL"
}
Approved 2019-11-12 JsonData BagLocation ADD group meeting 2018-09-24 string(32) BagIsRush Approved 2019-11-12 boolean BagIsPriority Approved 2019-11-12 boolean BagIsCrew Approved 2019-11-12 boolean BagInfoMsgCount Approved 2020-01-28 Count BagInfMsg Approved 2020-01-28 string BagImage Approved 2018-11-13 entity BagHasLoadedEvent Approved 2020-01-28 boolean BagHandlerCodeDeparture Approved 2020-01-28 HandlerCode BagHandlerCodeArrival Approved 2020-01-28 HandlerCode BagHandlerCode Approved 2018-11-13 HandlerCode BaggageWeightOnBoard Approved 2020-03-24 Kilo BagFirstRejectReason Approved 2020-01-28 string (32) BagFinalAirportIATA Approved 2018-11-13 AirportIATA BagEventTimestamp Approved 2018-09-24 TimestampUTC BagEventLocation Approved 2018-09-24 BagLocation BagEventErrorCode Approved 2020-03-24 string (8) BagEventDescription Approved 2018-09-24 string (128) BagEventCount Approved 2018-11-13 Count BagEventCode Approved 2018-10-01 string (24) BagEventAirportIATA Approved 2018-09-24 AirportIATA BagEvent Approved 2018-08-27 entity BagDepartureOperatingAirlineIATA
The OperatingAirlineIATA of the BagDepartureFlightId the bag departs on.Approved 2018-08-27 OperatingAirlineIATA BagDepartureFlightId
The FlightId for the flight the bag is supposed to depart on.Approved 2018-08-27 FlightId BagCheckinType Approved 2018-08-27 string(8) BagCheckinLocation Approved 2018-09-24 BagLocation BagCategory Approved 2018-11-13 string(8) BagCanBeTransported Approved 2020-01-28 boolean BagCanBeLoaded Approved 2020-01-28 boolean BagBsmWasProblem Approved 2020-01-28 boolean BagBhsDeliveryAttemptsTime Approved 2020-03-24 duration BagBhsBinDeliveryAttempts Approved 2019-10-15 Count BagArrivalOperatingAirlineIATA
The OperatingAirlineIATA of the BagArrivalFlightId the bag arrived on.Approved 2018-08-27 OperatingAirlineIATA BagArrivalFlightId Approved 2018-08-27 FlightId BagAOBT Approved 2019-10-15 DateTimeUTC BagAdditionalInfoCode Approved 2018-11-13 string (6) BagActualBin
The bin/location where the bag actually was delivered by the baggage handling system. The location is identified with a text string that is meaningful in the context it is used. The way/codes to identify a location will typically vary across the different implementations. Use the same values as used by BagEventLocation for the actual BagToBhsBin event for this bag.ADD group meeting 2018-09-24 BagLocation BACIT Approved 2019-03-12 DateTimeUTC BABBT Approved 2019-03-12 DateTimeUTC CabinBaggageWeightOnBoard Approved 2019-01-15 Kilo BagTagsActive Proposal Count BagIrregularityCode Approved 2020-01-28 string (2) EquipmentWeightUnloaded Approved 2019-03-26 Kilo CabinBaggageWeightUnloaded Approved 2019-03-26 Kilo BagFirstEventDate Proposal DateUTC BagTagSerialNumber Approved 2017-03-16, update Approved 2017-05-16 string (6) BagTagIssuerCode Approved 2017-03-16, update Approved 2017-05-16 AirlineIATAThreeNumeric BagTagLeadingDigit Approved 2017-05-16 string (1) BagTag Approved 2017-05-16 entity BagSequenceCount Approved 2017-03-16 Count PassengerHasWeaponsInBaggage Approved 2017-03-16 boolean PassengerHasPetsInCabin Approved 2017-03-16 boolean PassengerHasAnimalsInBaggage Approved 2017-03-16 boolean BagWidth Approved 2017-03-16 Centimeter BagWeight Approved 2017-03-16 Kilo BagTypeIndicator Approved 2017-03-16 string (3) BagScanTimestamp Approved 2017-03-16 TimestampUTC BagScanLocation Approved 2017-03-16 string (32) BagScanGeoLocation Approved 2017-03-16 entity BagScanDetailedInfo Approved 2017-03-16 string (64) BagScanAirportIATA Approved 2017-03-16 AirportIATA BagScanAction Approved 2017-03-16 string (32) BagLoadSequenceNumber Approved 2017-03-16 SequenceNumber BagLength Approved 2017-03-16 Centimeter BagHeight Approved 2017-03-16 Centimeter BaggagePoolId Approved 2017-03-16 string (3) BagDimension Approved 2017-03-16 entity BagContainerId Approved 2017-03-16 string (32) BeltFirstBagLocal Approved 2013-04-04 DateTimeLocal BaggageWeightUnloaded Approved 2013-04-04 Kilo BaggageWeightLoaded Approved 2013-04-04 Kilo BaggageClaimUnitName Approved 2013-04-04 string (30) BaggageCountLoaded Approved 2013-04-04 Count BaggageCountUnloaded Approved 2013-04-04 Count BaggageClaimUnit
There are a set of BaggageClaimUnits for each airport.Approved 2013-04-04 string (8) Baggage Approved 2013-04-04 entity BeltLastBag Approved 2013-04-04 DateTimeUTC BeltFirstBag Approved 2013-04-04 DateTimeUTC
Overview
Content Tools