Using BagDropService and only scan the bag tag - no scan of boarding pass

Configuration and regular status checks while the SBD is idle is described here: Configuration and status checking.

BagDropService is responsible for managing all aspects of the DCS communication.

NB! All calls to BagDropService related to one bag delivery process must use the same TransactionId. See also Use of TransactionId.


  1. The passenger initiates the bag drop by scanning the bag tag.

  2. The SBD must call GetOperatingCarrier to get the actual operating carrier. This also informs the bag drop service that a new bag drop has started.

  3. The SBD calls BaggageConformanceIdentify. This will result in a DCS request from the Bag Drop Service to get information about the bag, the passenger and the flight the bag should leave on.

  4. As there is no scan of boarding pass in this use case the SBD calls PassengerConformanceIdentify with the passenger and flight data received from BaggageConformanceIdentify.
      
  5. The SBD must call LocalVerifyBag to ensure that the bag is acceptable for the airport. This also indicates to the bag drop service that the bag is (close to) accepted by the SBD.

  6. The SBD calls BaggageConformanceVerify with basically the data received from BaggageConformanceIdentify. In addition bag weight must be added, and bag size can be added. The Bag Drop Service will then verify with the DCS that the bag can be sent.

  7. The SBD must call BagNotify to notify the bag drop service that the bag has been sent on to the baggage handling system at the airport.

Using BagDropService and scan of bag tag and scan of boarding pass

Configuration and regular status checks while the SBD is idle is described here: Configuration and status checking.

BagDropService is responsible for managing all aspects of the DCS communication.

NB! All calls to BagDropService related to one bag delivery process must use the same TransactionId. See also Use of TransactionId.

  1. The passenger initiates the bag drop by scanning the bag tag.

  2. The SBD must call GetOperatingCarrier to get the actual operating carrier. This also informs the bag drop service that a new bag drop has started.

  3. The passenger is requested to scan the boarding pass. Result is made available to the SBD.

  4. The SBD calls PassengerConformanceIdentify with data from the boarding pass. This data set is sent to the DCS and the DCS validates the passenger and that the bag is acceptable for the passenger.

  5. The SBD calls BaggageConformanceIdentify. This will result in a DCS request from the Bag Drop Service to get information about the bag, the passenger and the flight the bag should leave on.

  6. The SBD must call LocalVerifyBag to ensure that the bag is acceptable for the airport. This also indicates to the bag drop service that the bag is (close to) accepted by the SBD.

  7. The SBD calls BaggageConformanceVerify with basically the data received from BaggageConformanceIdentify. In addition bag weight must be added, and bag size can be added. The Bag Drop Service will then verify with the DCS that the bag can be sent.

  8. The SBD must call BagNotify to notify the bag drop service that the bag has been sent on to the baggage handling system at the airport.
  • No labels