Load a Bag to Aircraft at Origin (L)
Description
This use case illustrates messaging for a simple departure with held bag
Preconditions
Passenger and bag are checked in and bag has been tagged
Main Flow
# | Message | Business meaning |
BagRQ | Airline instructed handlers to anticipate a bag | |
BagRS | BHS acquired the bag | |
BagRS | BHS screened the bag | |
BagRS | BHS delivered the bag to Ground Handler | |
BagRS | Ground Handler packed the bag in ULD | |
ULD_RS | Ground Handler loaded the ULD in aircraft | |
BagRQ | Airline reported passenger as boarded which grants authorization to load for the bag | |
Exception: | BagRS | Ground Handler reported bag reconciles for departure with an incident (left behind) |
Note: above flow is for illustration. Some steps in flow may skip messaging as parties often agree to only “report by exception”. Step 8 (negative acknowledgement on reconcile by handler) is an example of such exception as may be reported in RP1745 messaging
Post Conditions
Bag is authorized to be loaded and stowed in aircraft, ready for take-off
Data Elements
Bag Segment in BagRQ, BagRS identifies the bag (bag tag) and the segment for which bag sees transportation
ULD Allocation in BagRS, ULD_RS identifies the ULD in which bag is packed for transport