Special case: visibility at transfer hand-over

Description

This use case illustrates how parties can collaborate to dynamically allocate location of hand-over in a transfer

Note how a plan by handler is conveyed by dropping SubSubProcess population

Preconditions

Bag is loaded on flight and destined for transfer to other airline at upcoming station

Main Flow

#	Message	Intent
	BagRQ	Airline instructed inbound handlers to anticipate a bag
52	BagRS	Inbound handler advises planned hand-over facility As this is plan (not completion of task) the handler only populates BusinessProcess and BusinessSubProcess
53	BagRS	Inbound handler may update planned location (e.g. if inbound flight is in delay)
54	BagRS	Inbound handler reports presentation of bag at Transfer hand-over location
55	BagNotifRQ	Inbound airline advises outbound airline on transfer location (advice may be repeated, and includes the presentation notice)
56	BagRQ	Outbound airline advises outbound handler where to anticipate acquisition of transfer bag
57	BagRS	Outbound handler reports acquisition of bag at transfer hand-over location

Post Conditions

Bag is removed from custody of inbound airline and acquired into custody of outbound airline. Bag is under control of outbound handler after acquisition at transfer hand-over location

Data Elements

Bag Segment in BagRQ, BagRS, BagNotifRQ identifies the bag (bag tag) and the segment for which bag sees transportation.

Transfer Hand-over Visibility

Contents