List of baggage related terms

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.

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 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.

BagPlannedBin indicates the bin that was the planned bin for this bag.

Standard IATA baggage information codes as defined in IATA Recommended Practice 1745, attachment A.

The AOBT for the flight the bag departed on. The flight is defined by BagDepartureFlightId. Always UTC.

The FlightId for the flight the bag arrived on.

The OperatingAirlineIATA of the BagArrivalFlightId the bag arrived on.

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 "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 "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 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 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.

"Bag BHS Transport Time" is the duration the bag has spent being transported in the baggage handling system (BHS).
Calculation: BagBhsTransportTime = BagTotalTimeInBhs - (BagTotalTimeInMcs + BagTotalTimeInEbs + BagTimeAtManSecScreen + BagBhsDeliveryAttemptsTime)

BagBsmWasProblem indicates that there were a problem with a BSM at least once. Often this will be a missing BSM.

• true - There were a problem with a BSM at least once.
• false - No BSM related problems noticed.

BagCanBeLoaded indicates if the bag is can be loaded (onto an aircraft) or not.

• true - The bag can be loaded.
• false - Default value. It is not known that the bag can be loaded.

The number of bags that can be loaded onto this aircraft on this airport. This includes local bags, and expected transfer bags.

BagCanBeTransported indicates the bag can be transported.

• true - The bag can be transported.
• false - Default value. It is not known that the bag can be transported.

The category ("CheckIn", "Transfer", "Final") this bag belongs to.

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.

A codes indicating the status of a bag check in attempt. Legal values are system specific.

Indicates how the bag was checked in. This can typically be derived from BagEventLocation.

The FlightDepartureDate of the flight the bag is planned to depart on from a given airport. Always DateUTC. 

The FlightId for the flight the bag is supposed to depart on.

The OperatingAirlineIATA of the BagDepartureFlightId the bag departs on.

The scheduled date and time that the aircraft a bag is planned to depart from its parking position. Always DateTimeUTC. 

Uniquely identifies a bag drop unit on an airport. 

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:

• BagEventCode
• BagEventTimestamp
• BagEventDescription
• BagEventLocation

The AirportIATA code associated with the BagEventLocation where a BagEventCode occurred.

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.

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.

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 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.

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.

Timestamp defining when a BagEventCode occurred.

The AirportIATA code for the final airport the bag should be sent to.

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 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 number of bags in some context.

Weight in kilos of all baggage actually on board the aircraft.

A GUID identifying a bag in some context.

The HandlerCode for the Handler that is responsible for handling the baggage.

The HandlerCode for the Handler that are responsible for handling the baggage at arrival.

The HandlerCode for the Handler that are responsible for handling the baggage at departure.

BagHasLoadedEvent indicates that the bag was loaded onto an aircraft. In practice this means that at least one BagLoaded event has been registered.

• true - The bag has at least one BagLoaded event
• false - No BagLoaded event has been registered for this bag. It might still be loaded onto the aircraft, but it is (much) less likely

One image of an bag. This would typically be part of the bag check-in process, or at arrival scanning. A BagImage will typically be implemented as an entity with MediaType and Image.

A standard IATA baggage information message as a text string. Start and end token ("BSM"/ENDBSM, BPM/ENDBPM, ....") included.

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.

Standard IATA baggage irregularity codes as defined in IATA Recommended Practice 1743.

BagIsCrew indicates if the bag is a crew bag or not.

• true - The bag is a crew bag.
• false - Default value. The bag is not (known to be) a crew bag.

BagIsPriority indicates if the bag is a priority bag or not.

• true - The bag is a priority bag.
• false - Default value. The bag is not (known to be) a priority bag.

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'.

• true - The bag is a RUSH bag.
• false - Default value. The bag is not (known to be) a RUSH bag.

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.

Open ended string containing JSON formatted data. Contains any additional information about the lost bag as name:value pairs. For example:

{
   "CARRIER_CD ": "XX",
   "ROUTING": "PUS/PEK/CPH/OSL"
}

The AirportIATA code where the bag is reported to have been lost.

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.

The FlightId for the flight where the bag became lost. Not guaranteed to be correct, best effort value.

The BagIrregularityCode associated with the bag being registered as lost.

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

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 AirportIATA code for the next airport the bag should be sent to.

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.

The PnrCode associated with a BagTag. This will often be the owner of the bag, but might not be.

A GDPR compliant version of the PnrCode associated with a BagTag. It can be used to "represent" the passenger associated with the bag, but not to identify the passenger.

The AirportIATA code for the airport the bag came from. Not relevant for bags that start their journey on "this" airport.

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.

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.

The number of bags delivered to the bin(s) allocated to one flight.

The number of bags delivered to a problem bin for one flight, and not the bin(s) allocated to one flight.

Indication if baggage is unconventional size or weight.

The SOBT for the flight the bag departed/is supposed to depart on. The flight is defined by BagDepartureFlightId. Always UTC.

The AirlineIATA code corresponding to the BagTagIssuerCode.

The 10 digit bag tag (licence plate) number as defined by IATA. The BagTagNumber is a concatenation of BagTagLeadingDigit, BagTagIssuerCode and BagTagSerialNumber.

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 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.

.

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 status of a "Bag Tag" on one airport.

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.

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.

• true - The bag tag was not registered in the airports BHS
• false - The bag tag has been registered in the BHS

The "Bag Time At Automatic Security Screening" is the duration the bag has spent at automatic security screening. BagTimeAtAutSecScreen = BFAST - BTAST

The "Bag Time At Manual Security Screening" is the duration the bag has spent at manual security screening. BagTimeAtManSecScreen = BFMST - BTMST

The BagToMcsCount is the number of times a bag has been to a manual coding station on one airport.

The "Bag Total Time At Security Screening" is the total duration the bag has spent at security screening. BagTotalTimeAtSecScreen = BFLST - BTFST

The "Bag Total Time In BHS" is the duration the bag has spent in the baggage handling system. BagTotalTimeInBhs = BTBBT - BACIT
If the bag is rejected for technical reasons BagTotalTimeInBhs should be reset.

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 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

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.

• true - The bag was delivered in time from the BHS.
• false - The bag was delivered late from the BHS.

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.

• true - The bag was delivered late from the BHS. It might still be loaded into the aircraft.
• false - The bag was delivered in time from the BHS (BagWasDeliveredFromBhsInTime is true").

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.

• true - The bag was delivered too late from the BHS to be loaded. This also indicate that BagWasDeliveredFromBhsLate = true.
• false - The bag was delivered late or in time from the BHS, as indicated by BagWasDeliveredFromBhsInTime and BagWasDeliveredFromBhsLate.

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.

• true - The bag was delivered in time.
• false - The bag was delivered late.

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.

• true - The bag was delivered late. It might also be too late (BagWasDeliveredToBhsTooLate is true).
• false - The bag was delivered in time, ref. BagWasDeliveredToBhsInTime.

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.

• true - The bag was delivered too late. BagWasDeliveredToBhsLate is also set to true.
• false - The bag was delivered late or in time to the BHS, as indicated by BagWasDeliveredToBhsInTime and BagWasDeliveredToBhsLate.

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.

• true - The bag is known to be lost
• false - The bag is not registered as lost

BagWasRejected indicates if the bag was rejected one or more times during checkin/delivery of the bag.

• true - The bag was rejected at least once during bag checkin/delivery.
• false - The bag wasn't rejected. Normal, problem free checkin/delivery.

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.

• true - The bag was sent to a MCS at least once. See BagToMcsCount for the number of times the bag has been to a MCS,
• false - The bag has not been to a MCS.

BagWasSentToProblemBin indicates that the bag was sent to a problem bin. There are many possible reasons for this.

• true - The bag was sent to a problem bin.
• false - The bag was (most likely) sent to a bin associated with the flight. See BagActualBin for the bin the bag actually was sent to.

The precise weight, in Gram, of a bag.

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.

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.

Estimated time for BeltFirstBag.

As BeltLastBag, but local time.

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 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 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 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 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 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 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 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 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 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 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 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 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 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 number of bags in a batch, at a given point in time.

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.

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.

TimestampUTC when the relevant BHS batch event occurred.

Unique identifier, for a given period of time, that identifies a batch of bags on a given airport. 

The BagLocation where this batch is to be loaded. 

??

The maximum weight the BHS can accept.

The minimum weight the BHS can accept.

The interval (duration) between multiple (BhsStableWeightRequests) weight requests to provide stable weight.

Weight tolerance margin (gram) to be subtracted from measured stable weight.  

Number of weight requests to provide stable weight (will be 1 if bag drop scale always delivers stable weight). 

Weight tolerance margin (gram) between subsequent weight requests. The different measurements must be within BhsStableWeightTolerance to be accepted.

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.

A baggage bin. Typically where a baggage handling system places the bags that are sorted.

Code/string defining which baggage segregation that are associated with the relevant Bin. Codes are system/handler specific.

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.

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 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 "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 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 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 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 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 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 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 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 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 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 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 Transfer Time" is the DateTimeUTC when the bag is delivered to transfer processing. This corresponds to the BagEventCode "BagToTransfer". 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 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 Unloaded From Aircraft Time" is the DateTimeUTC when the bag was unloaded from the aircraft. This corresponds to the BagEventCode "BagUnloaded". Always UTC.

Weight in kilos of all cabin baggage actually on board the aircraft.

Weight in kilos of cabin baggage unloaded.

The maximum weight, in Gram, a bag can be before it must be sent as special (oversize, overweight) baggage.

The maximum bag weight, one individual bag, this carrier supports.

Is a DCS that is supported (DcsIsSupported) actually available at the current time.

Is the relevant DCS supported in some context.

Weight in Kilos of all equipment unloaded.

Estimated arrival time for something at the relevant location.

Identifies an actual load unit, ref. LoadUnitType.

Identifies a load unit type aircrafts. Typically used for baggage and cargo.
See https://vrr.aero/knowledge-center/uld-info/uld-id-code/ and https://en.wikipedia.org/wiki/Unit_load_device for details.

A GUID identifying a passenger in some context.

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.

A GUID identifying a a transaction in some context. This will often be multiple operations that are related in some way.