Value Chain, Stakeholders and Decision Rights
5 min read
Lesson objectives
- Map physical, information and decision flows, locating a service handoff.
- Distinguish airport operator, airline, handler and public-agency roles without a universal legal claim.
- Diagnose a simplified baggage bottleneck and propose an action and verification measure.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
Imagine a flight arriving on time while its passengers wait a long time for bags. “The airport was late” is too broad to locate the fault: the journey is delivered by several organizations. The airport operator manages shared facilities such as the terminal, gates and apron under local arrangements. The airline sets its schedule and carries passengers; a contracted ground handler may service the aircraft and move bags. Air navigation, security and border agencies also have distinct powers that vary by country. The first management task is to map the service journey and ask at which handoff information, a bag or responsibility moved from one party to another.
Separate the value a traveller experiences from the activity each operator provides. A traveller does not purchase a runway in isolation; they need a safe, intelligible and timely journey. An airline uses runway, stand and gate capacity within a broader transport service. The airport operator makes infrastructure available and may develop retail, parking and other services. This is an analytical map, not a universal legal allocation. Actual contracts and local authorities determine ownership, operation, charging and escalation. A passenger outcome should therefore not automatically be assigned to the organization whose name appears on the terminal.
Map the chain in three layers. The physical flow runs from aircraft arrival and stand allocation through bag unloading, transport and reclaim. The information flow includes expected arrival time, flight number, unloading start, belt announcement and missing-bag report. The decision flow asks who can reassign a stand or belt, who prioritizes aircraft service, and who communicates with passengers. These flows may overlap without belonging to one organization. Changing only a belt announcement can improve information while the physical bottleneck remains. Adding staff without reliable arrival information can leave capacity idle.
The reasoning matters: identify the shared resource, compare demand and throughput over the same interval, then separate an information action from a flow action. Do not call 170 divided by 60 the waiting time of each passenger. It is about 2.83 operating intervals: theoretically, processing all bags needs more than two but fewer than three 15-minute intervals if bags are ready and the belt never stops. The final bag may take longer because of batch order. A useful record captures the first- and last-bag time for each flight and the count of passengers given an incorrect status. That evidence distinguishes a service improvement from a cosmetic message change.
A management report should not declare “the handler is responsible” before testing the handoff. Obtain aircraft arrival time, unloading start, first-batch transfer into the baggage system and first-bag appearance on the belt. A long interval before transfer points toward staffing or equipment questions for the handler under its agreement; a long interval after transfer points toward belt, transport or allocation questions for the operator. Both sides may contribute. This diploma does not replace safety procedures or a formal investigation; the case teaches preliminary service diagnosis and documented escalation within assigned authority.
Lesson summary
A flight service combines physical flows, information and decisions across organizations. Handoff timestamps and capacity locate bottlenecks; do not assign blame or promise a time before measuring them.