You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 28 Next »


TermBagEventCode
Business termBag 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 events. 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
  • 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.
  • BagSbdChecked

    Error rendering macro 'excerpt-include'

    No link could be created for 'BagSbdChecked'.

  • 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

  • BagDeliveredFromBHS

    Error rendering macro 'excerpt-include'

    No link could be created for 'BagDeliveredFromBHS'.


  • BagDeliveredFromBHSProblem

    Error rendering macro 'excerpt-include'

    No link could be created for 'BagDeliveredFromBHSProblem'.



  • BagRemovedFromBHS

    Error rendering macro 'excerpt-include'

    No link could be created for 'BagRemovedFromBHS'.



  • BagLoadedOnAircraft

    Error rendering macro 'excerpt-include'

    No link could be created for 'BagLoadedOnAircraft'.

  • BagUnloadedOffAircraft

    Error rendering macro 'excerpt-include'

    No link could be created for 'BagUnloadedOffAircraft'.



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

 

StatusProposal
XML typestring (24)
Ref from
Labels
  • No labels