
Traditional path & GDS NDC path: Data flows through the agency desktop or OBT back to the GDS.
Traveler chooses a flight.
Profiled corporate traveler initiates a travel request through an online booking tool or by calling the agency.
Agency profile management system identifies traveler and applies known preferences, requirements and policy.
Request could take multiple routes: to the global distribution system, to an aggregator or direct connect to carriers.
NDC Path: The TMC directly pings the airlines
Traditional Path: ATPCO & OAG send their respective data to the GDS, which constructs and returns the offers to the TMC
The agent or OBT aggregates and communicates the options to the traveler, flagging or blocking nonpreferred options based on the corporate travel program’s configurations.
NDC paths: Airline registers the booking, potentially settles the transaction and sends the data to ARC/BSP; integration with midoffice and back-office systems currently is unsolved.
Traditional path: ARC/BSP settles payment and returns data to the agency back office and to the airline. NDC path: ARC/BSP settles payment if airline has not and returns the data to the agency back office and to the airline. If airline has settled, ARC/BSP acts as a pass-through to the agency back office.
Airline registers the booking and removes that content from the shelf.
Traditional Path: The GDS simultaneously pings ATPCO & OAG NDC Path: The GDS pings an aggregator or directly pings airlines
NDC Path: Aggregator pings an aggregator
NDC Path: The airlines construct the offers and return them either directly to the TMC or via an aggregator or GDS
NDC Paths: The data flows directly through the agency or OBT back to the airlines
Traditional path: GDS registers the booking and sends it to the agency midoffice/back office and to the Airlines Reporting Corp. or IATA’s Billing & Settlement Plan.