Business Requirements Document Interline Ancillary Shopping

Transcription

1 Business Requirements Document Interline Ancillary Shopping 11 June 2014 Document Status: Version 1.3 FINAL Workgroup members or interested parties should send their comments and requests to DDX Interline Taskforce at and to DDX Steering Group at

2 Revision History Version Date Name Description of Change Dec-13 Amy Sexton Initial Draft Jan-14 Amy Sexton Cleaning up the doc from the great input by all the team members Jan-14 Amy Sexton Import data descriptions (section 6) Jan-14 Amy Sexton Updates from review with XML TaskForce Feb-14 Amy Sexton Updates from review with all Task Force leaders. Noticed the diagrams were wrong updated those, too Feb-14 Amy Sexton Updates with new use cases (text and/or diagrams) from team submissions. Prep for work at February, 2014 F2F and DDXWG/ Feb-14 Team Results of F2F prior to DDXWG/ Feb-14 Amy Sexton Added new use case diagrams. General clean-up. Awaiting: 1 Input on new schema (ShopProductRQ/RS?) 2 Input from B. Lowell - New data element in ServiceListRQ = send only flight-related ancillaries 3 Input from B. Lowell Why was journey elements removed from AirShoppingRQ/RS? Feb-14 Amy Sexton and David Shattuck Consolidate work from task force during DDXWG/06 and submission to PADIS April-14 Amy Sexton Changes requested from review by PADIS. IATA is also making a determination whether the legal direction we received is appropriate to include in this document. IATA is going to determine the legality of the ORA proposing a price to the POA in the RQ messages 1 Additional changes to UC s to reflect discussion on service price and taxes during meeting April-14 Andrei Grintchenko June-14 Andrei Grintchenko Formatting changes, PADIS review version Post-PADIS Review Call (12 and 14 May 2014) clean-up, minor on-site updates, updated terms and definitions (common through all NDC BRDs). Final version and PDF version. 1 Legal assumptions and direction were agreed to be not appropriate in the schema business requirements document, as they do not add specific value in facilitating schema design and development, and relate to implementation and deployment of the standard. They may be considered to be included as required the applicable sections of the Implementation Guide, as it is being developed, and reviewed by Legal. IATA legal indicated to the Interline group that there is generally no issue of ORA proposing a price to POA. Business Requirements Document NDC Interline Ancillary Shopping 2

3 Table of Contents 1 Introduction Scope Field of Application Recommended Messages Principles References Terms and Definitions Functional Requirements Functional Requirement Description Message Sequence Flows Data Description RQ: ORA to POA RS: POA to ORA Message Models Non-Functional Requirements Code Lists Appendix A: List of Use Cases

4 NDC Interline Messaging Requirements for Point to Point Ancillaries 1 Introduction IATA Resolution 787, passed in Oct 2012, recognised that the industry will benefit from the introduction of a standard process for airlines to distribute product offers created within their own systems and to manage the resulting orders. This standard Application Programming Interface (API) is called the New Distribution Capability (NDC) API. This BRD documents the NDC business requirements for interline Shopping for leg-based or standalone Ancillary Services. The scope of the BRD does not cover under which situations a carrier should or should not use these messages to conform to competition law. 2 Scope 2.1 Field of Application The full NDC context is shown in the following diagram with the scope of this BRD indicated. The scope covered by this BRD for NDC Interline Ancillary Shopping is: In Scope: Leg-based ancillary services (e.g. meal) Business Requirements Document NDC Interline Ancillary Shopping 4

5 Out of Scope: Standalone ancillary services (e.g. lounge pass) Request ancillary offer(s) from NDC interline partners acting as POA Response to ORA of POA offer(s) The remaining proposed standards resulting from the NDC project are out of scope of this document, i.e.: Airline Profile distribution and usage. Ancillary services over multiple legs (e.g. through ancillary charge) Aggregation of POA offer(s) by the ORA into final offer(s) Baggage will be covered in a later BRD Non-airline POAs are not covered in this version but may be covered at a later date Ancillaries associated to fares (e.g. branded) are not covered in this version but may be covered at a later date 2.2 Recommended Messages AirShoppingRQ/RS Message Pair: AirShoppingRQ/ AirShoppingRS The AirShopping transaction set supports both demanding and flexible shopping experiences for anonymous or personalized shopping. The combination of functionally - rich attribute and affinity shopping support date range or specific month (calendar) shopping as an example. The response returns offers which may include branded offers or itinerary-priced offers with or without ancillary services. It also returns applicable rules for the integrated offers as well as for each service identified in the offer. SeatAvailabilityRQ/RS ServiceListRQ/RS The message returns reference to multi-media content at message level as well as at the individual offer and even service levels identified in the offer. Message Pair: SeatAvailabilityRQ/ SeatAvailabilityRS The SeatAvailability transaction set returns data on all seats associated with a selected flight. It may indicate which seats are already selected, and which are still available. It also returns data on fees for seats. This data may be used to construct seat maps. The message also returns multi-media content at both the message and individual service level. Message Pair: ServiceListRQ/ ServiceListRS The ServiceList transaction set returns a list of all applicable ancillary services that meet request qualifiers and flights. 5

6 The message supports shopping for additional a la carte services to complement any selected offer, as well as shopping for specialty service items not generally included in an initial offer but rather based on service search filters, e.g. sports equipment specialty baggage and unaccompanied minor fees. The message also returns multi-media content at both the message and individual service levels identified in the offer. ServicePriceRQ/RS Message Pair: ServicePriceRQ/ ServicePriceRS The ServicePrice transaction set allows individual seats and/or known à la carte ancillary services to be priced on demand. The response message returns pricing of seat/services meeting the request qualifiers. The message also returns multi-media content at message level as well as at the individual service level. ShopProductRQ/RS Message Pair: ShopProductRQ/ ShopProductRS This is a new pair of messages required in scope of NDC Airline Shopping SimpleTypes CommonTypes The SimpleTypes schema promotes NDC type reuse as it contains common SimpleTypes, attributes and attribute Groups used in two or more NDC Phase 1 Shopping/ Pricing schema. It is included in the CommonTypes schema file via an xsd: include mechanism. Common definitions, used by the majority of NDC transactions, that provides a common representation of key data sets and promote reuse within the specification. 2.3 Principles Data exchange will take place on a bilateral basis These transactions will take place between parties that are covered by a settlement agreement. Regardless of the type of message, complete flight details will be sent in the request if the service is applicable to a specific flight (e.g. flight number, date, cabin, class) Acknowledge and Reject processing is determined on the basis of a bilateral agreement. Parties using the API shall ensure their own compliance with all applicable laws and regulations. 6

7 The ORA and the seller/aggregator will have a valid commercial agreement in place between them and have take steps to ensure that they are compliant with any applicable competition law or regulation. The POA may have the capability to refuse the ORA request based upon any number of factors including the identity of the seller/aggregator. (pass this SG for input) 3 References IATA Resolution 787 NDC Airline Shopping (Oct 2013) NDC Payment and Ticketing BRD (Feb 2014) IATA s Airline Coding Directory (ACD) IATA s Passenger and Airport Data Interchange Standards (PADIS) IATA s XML Data Dictionary IATA s XMLWG Best Practices 4 Terms and Definitions Term and Definitions identified in this document and in other NDC Business Requirements Documents (ie. Airline Shopping, etc.) are maintained in a separate document NDC Terms and Definitions, owned by DDXWG Steering Group. Terms and definitions are included in this document as an excerpt from NDC Terms and Definitions v.1.2 for easier reading and referencing. Term Definition BRD Reference Accountable Document Acknowledgement Affinity Shopping Aggregator Validated official document (such as any type of an airline ticket, or a Standard Traffic Document (STD) or payment voucher) that has a value and must be accounted for. Acknowledges the receipt of a message but does not imply acceptance of the message content A wide search defining a range of criteria including specific interest, destination attributes and defined budget plus date and destination ranges. The business function of distributing a Seller s shopping request to multiple Airlines and aggregating the subsequent responses. Order Management Order Management Airline Shopping Airline Shopping; Payment and Ticketing 7

8 Airline Airline currency Ancillary Services or Optional Services Anonymous Shopping Supplies product offers in response to receiving a request from a Seller. Airline refers to itself and any subcontracted entity providing a service to the airline Miles, vouchers, residual value EMD, airline issued gift/cash card Ancillary Services are defined in PSC Resolution 787 as anything outside of product attributes (optional or discounted). Ancillary Services may be bundled in the product offer, or offered as additional, a la cart services. For the purposes of this document the term Ancillary Services is sometimes used interchangeably with the term Optional Services. No traveller personal data in the shopping request Airline Shopping; Payment and Ticketing Payment and Ticketing Airline Shopping; Interline Ancillary Shopping; Payment and Ticketing Airline Shopping API Application Programming Interface Airline Shopping; Payment and Ticketing Attribute Shopping Authentication Bilateral Interface Agreement Bilateral Time Limit A search specifying one or more attributes to get more focused results (eg equipment types, Seat types and characteristics, baggage allowance, meals, etc. The process by which a system identifies an individual or a business entity to make sure that the user or the business entity is who they claim to be, based on attributes that are sent in a message. A documented agreement made between the sender and receiver as the basis of the data exchange between systems This agreement defines a number of features which are mandatory or optional within the specification (time outs, message order processing, reject processing) A generic structure for time limits, that is subject to bilateral agreements between parties. Airline Shopping Airline Shopping; Payment and Ticketing Interline Ancillary Shopping Airline Shopping (requires a change) and Order Management 8

9 Booking Time Limit Booking time limit is the amount of time within which the booking transaction must be completed (does not include ticketing). NOTE: This definition in Airline Shopping is superseded with the revised definition of Offer Time Limit (revised) as provided in Order Management BRD Airline Shopping (requires change) Cabin A compartment where passenger seats are installed Interline Ancillary Shopping Campaign Identifier Card payment* Cash payment Campaign ID is a tracking code used by the airline s advertising analytics system to monitor and optimize the paid advertising by the airline across interactive marketing channels. By including the Campaign ID with shopping requests the online media publisher (MSE, OTA, affiliate partner, booking widget, etc.) can help guide the airline so that the airlines personalization of offers can align with any paid advertising that may be present on the publisher s display. Various forms of payment that include: credit card (includes UATP), debit card (PIN based or signature based), pre-paid debit/bank/gift card, cash card where the Airline is the merchant. Refer to IATA Resolution 728 Attachment A for full details on card types and codes. Any payment that is collected by the agent and settled between the Airline and the agent. Refer to IATA Resolution 728 Attachment A for full details on card types and codes. Order Management Payment and Ticketing Payment and Ticketing CBT Corporate Booking Tool Airline Shopping Check/Cheque* Commercial Agreement ID Corporate ID Personal or bank issued order for transfer of money. Refer to IATA Resolution 728 Attachment A. Code or ID referenced by ORA or POA in message exchange which refers to a previously created bilateral agreement. A SPA is an example. An ID provided by an airline to uniquely identify a corporate location for which a commercial arrangement exists. Payment and Ticketing Interline Ancillary Shopping Order Management, plus change to Airline Shopping 9

10 Deposit Time Limit Time by which a deposit must be paid for an Order. Airline Shopping (requires change) and Order Management Distribution Channel Provider An entity that has the capability to interface with an airline s dynamic shopping API enabling distribution of airline product offers across one or multiple channels. For the purposes of this document it is assumed that such provider shall use industry standard NDC XML messages to communicate with airlines dynamic shopping API, and may act as a content aggregator. Airline Shopping FQTV Frequent Traveler Airline Shopping Group Booking Inventory Guarantee Time Limit Inventory Guarantee Identifier Leg Marketing Carrier Meta Search deep link Meta Search shallow link An Order made under a group name without individual passenger names at the point of creation The time that inventory for a specified product offer is guaranteed as available. The inventory held must be converted into a completed order before the time limit expires otherwise the guarantee is lost. Held Inventory is referenced by an Inventory Guarantee identifier (equivalent in business terms to the legacy ITAREQ Conversation ID ). In the context of Interline Ancillary Shopping, this term is defined as the time window (or final date) identified by the ORA or POA where inventory will be held prior to booking. An unique identifier issued by an Airline to reference that inventory for a specified offer will be guaranteed as available for a period The operation between a departure station and the next arrival station The carrier that sells with its own code as part of a code share agreement on a flight that is actually operated by another carrier. A link to an airline's or OTA's itinerary purchase page enabling the user to purchase a specific itinerary offer. A link to an airline's or OTA's shopping results page listing multiple flight options for a pre-specified city pair and dates, as well as upsell / cross-sell products Order Management Order Management; Interline Ancillary Shopping Order Management Interline Ancillary Shopping Interline Ancillary Shopping Airline Shopping Airline Shopping 10

11 MSE ( Meta search Engines) MSE redirect their users to an airline or Online Travel Agent for the creation of an Airline Order. A MSE is not involved in servicing the resulting order - this is done by the OTA or Airline. Order Management Multi Leg Flight A flight comprised of more than one leg Interline Ancillary Shopping Naming Time Limit Time by which an Order, must be completed with individual passenger names. Order Management OAL Other AirLine Airline Shopping Offer ID Offer item Offer Responsible Airline (ORA) Offer Time Limit Offer Time Limit Offer ID facilitates the tracking and verification of individually priced offer(s) selected from the shopping response. Only the Offer IDs of the ORA (Offer Responsible Airline) are returned in shopping responses. Offer ID is unique to each individually priced offer in the shopping response even if the offer price is zero. OfferID may be specific to individual passengers in the offer, and may be associated with a segment or a journey. The set of Offer IDs returned in a response are referenced by a Shopping Response ID. One or more products that has one price, eg a product bundle Offer Responsible Airline: The airline responsible for returning a combined offer, including participating airline offers, to the requesting entity Offer Time Limit is the amount of time within which offers in a shopping response maybe reserved. Upon expiring, a new shopping request must be sent. NOTE: This definition in Airline Shopping is superseded with the revised definition of Offer Time Limit (revised) as provided in Order Management BRD The time within which offers must be converted into completed Orders. On expiry a new shopping Airline Shopping; Payment and Ticketing Order Management Airline Shopping; Interline Ancillary Shopping; Payment and Ticketing Airline Shopping (requires change) Order Management; Interline Ancillary 11

12 (revised) Operating Carrier Order transaction is required. This definition supersedes both Offer and Booking Time Limit definitions in the Shopping BRD. Offer Time Limit is mandatory. The carrier that holds the Air Operator s Certificate for the aircraft used for that flight An Order is a uniquely identified record of the agreement of one party with another to receive products and services under specified terms and conditions. Order supports the sale of a flexible range of airline products and services that are not necessarily journey based (eg subscription services). A PNR, super PNR and ticket are all today s versions of airline implementations of aspects of an Order. An Order will contain 1 or more Order Items each with an identifier that is unique within an Airline s Order Management system. An Order may support nonhomogeneity, ie each passenger in an Order may hold different sets of order items at different prices. Shopping; Payment and Ticketing Interline Ancillary Shopping Order Management; Payment and Ticketing Order item A selected Offer item. Order Management Order Management Order Management is the process of taking, amending, tracking and fulfilling requests for an airline s products and services. Order Management OSI Other Service Information Airline Shopping OTA Online Travel Agency Airline Shopping Participating Offer Airline (POA) Payment Time Limit Participating Offer Airline: An airline other than the Offer Responsible Airline involved in a product offer The deadline by which a commitment to pay must be made for the items in the order. This includes ticketless transactions and other accountable documents (ie EMD. Payment Time Limit and Ticket Time Limit may be the same in most cases; however, Payment Time Limit expands to include ticketless transactions and other accountable documents. Payment Time Limit is mandatory. Airline Shopping; Interline Ancillary Shopping; Payment and Ticketing Order Management; Interline Ancillary Shopping; Payment and Ticketing 12

13 Personalised Shopping Traveller consents to include personal data in the shopping request Airline Shopping PNR Passenger Name Record Airline Shopping; Payment and Ticketing Price Guarantee Time Limit Product Bundle Referrer Identity Seller Service Item Period for which an Offer price is guaranteed. On expiry an Offer may be re-priced up to the point an accountable document is issued. A Price Guarantee cannot extend beyond the Offer Time Limit unless the Order has been created. Where several products are offered for sale as one product. NOTE: This definition has evolved in Order Management BRD, and has the same meaning as Offer Item Identifies to the aggregator or the airline, the specific commercial contract under which a particular message should be tracked; for example, is the message related to (A) the x cents per click for traffic from Indonesia or (B) the y % per ticket for each booking that originates from Japan. Creates shopping requests to Airlines on behalf of a customer and displays the subsequent product responses for review An airline service item is a product or a service that can be separately delivered and uniquely described by an airline. It is referenced by an ID that is unique within an airline. A service may be sold separately in a single offer/ order item or sold bundled with other service items in a single offer/order item (eg a return price consisting of inbound and outbound services). Airline Shopping (requires change) and Order Management Airline Shopping Order Management Airline Shopping; Payment and Ticketing Order Management Service Time Limit Settlement providers Time limit for EMD creation. May be different from Payment Time Limit Third parties that provide settlement services between agent and airlines. Could include ARC, BSP, TCH, MoneyDirect, eenet, etc. Interline Ancillary Shopping Payment and Ticketing 13

14 Shopping Shopping Basket Shopping Response ID A process whereby a Seller is able to request offers from the airlines (ie flight and ancillaries) based on its desired search criteria and receive offers corresponding to its request. There are various types of shopping, including, for example, Personalized/ Anonymous and Attribute/ Affinity shopping types as defined in this document. A Shopping Basket is e-commerce software that allows visitors to an internet site to select items for eventual purchase Shopping Response ID facilitates the tracking of what was offered and is an identifier unique to the source airline for a set of product offers returned in response to a shopping request. Shopping Response ID may be comprised of an Offer ID corresponding to an individual flight and/or ancillary service product offer that make up the offer. See Appendix D for scenarios illustrating use of this identifier. Airline Shopping Airline Shopping Airline Shopping SSR Special Service Request Airline Shopping Ticket Time Limit Ticketing Ticket Time Limit is the amount of time which the booking maybe held until it must be ticketed or other accountable documents issued (eg EMD). The process of issuing any type of an accountable document to fulfil an airline order. Airline Shopping Payment and Ticketing TMC Travel Management Company Airline Shopping XML Extensible Markup Language Airline Shopping 14

15 5 Functional Requirements 5.1 Functional Requirement Description Interline Ancillary Shopping Request Ref # Requirements 1.1 Provide capability to allow a shopping request to be made from the ORA to the POA for ancillaries. Including (but not limited to): Complete point of sale information Available traveler information (e.g. tier level, frequent flyer number, corporate ID, passenger ID, etc.) Commercial agreement ID Flight related ancillaries Non-flight related ancillaries 3 rd -party fulfilled ancillaries on behalf of the POA 1.2 Provide capability to shop for bundled ancillaries. See list for Provide capability to shop for a la carte ancillaries. See list for Provide capability to propose or request a price (e.g. request a free extra leg room seat for top tier). See list for Provide capability to request a price for a specific service. See list for 1.1. Messages* ServiceListRQ AirShoppingRQ ShopProductRQ ServiceListRQ AirShoppingRQ ShopProductRQ ServiceListRQ AirShoppingRQ ShopProductRQ ServiceListRQ AirShoppingRQ ShopProductRQ ServicePriceRQ ShopProductRQ 1.6 Provide capability to shop for ancillaries for a previously booked itinerary (NDC Order or non-ndc PNR) See list for 1.1. ServiceListRQ AirShoppingRQ ShopProductRQ 15

16 RQ: ORA to POA (cont.) Ref # Requirements Messages* 1.7 Provide capability to shop for ancillaries without a previously booked itinerary. See list for 1.1. ServiceListRQ AirShoppingRQ ShopProductRQ 1.8 Provide capability to shop for ancillaries within a specific date range. See list for 1.1. ServiceListRQ AirShoppingRQ ShopProductRQ 1.9 Provide capability to shop for ancillaries within a specific time range. See list for 1.1. ServiceListRQ AirShoppingRQ ShopProductRQ 1.10 Provide capability to request ancillaries priced using award miles. This assumes the passenger has proactively provided their loyalty program information for the purposes of this shopping request. See list for Provide capability to shop for a seat assignment. See list for 1.1 ServiceListRQ AirShoppingRQ ShopProductRQ SeatAvailabilityRQ 1.12 Provide capability to request a seat map. SeatAvailabilityRQ 1.13 Provide capability for all messages from ORA to POA to include: ServiceListRQ Proposed validating carrier AirShoppingRQ The entire proposed itinerary, if known and if applicable (e.g. all carriers, all flights) The true ORA ShopProductRQ SeatAvailabilityRQ Seller/Aggregator 16

17 Ref # Seller/Aggregator Information Requirements Messages* 1.14 Provide capability for the ORA to provide time limit(s) as applicable in messages to the POA ServiceListRQ AirShoppingRQ ShopProductRQ *Unsure if these are the complete/correct list of messages Interline Ancillary Shopping Response Ref # Requirements 1.1 Provide capability to allow a shopping response to be made from the POA to the ORA for ancillaries. The response should include (but is not limited to): Offer(s) based on information provided in the request, such as: o Complete point of sale information o Available traveler information (e.g. tier level, frequent flyer number, corporate ID, passenger ID, etc.) o Commercial agreement ID Flight related ancillaries Non-flight related ancillaries 3 rd -party fulfilled ancillaries on behalf of the POA Messages* ServiceListRS AirShoppingRS ShopProductRS 1.2 Provide capability to respond to a shopping request for bundled ancillaries. See list for 1.1. ServiceListRS AirShoppingRS ShopProductRS 1.3 Provide capability to respond to a shopping request for a la carte ancillaries. See list for 1.1. ServiceListRS AirShoppingRS ShopProductRS 17

18 Ref # Requirements Messages* 1.4 Provide capability to respond to a shopping request that proposed or requested a price (e.g. request a free extra leg room seat for top tier). See list for 1.1. ServiceListRS AirShoppingRS ShopProductRS 1.5 Provide capability to respond with a price for a specific service. See list for 1.1. ServicePriceRS ShopProductRS 1.6 Provide capability to respond to a shopping request for ancillaries for a previously booked itinerary (NDC or non-ndc) See list for 1.1. ServiceListRS AirShoppingRS ShopProductRS 1.7 Provide capability to respond to a shopping request shop for ancillaries without a previously booked itinerary. See list for 1.1. ServiceListRS AirShoppingRS ShopProductRS 1.8 Provide capability to respond to a shopping request for ancillaries within a specific date range. See list for 1.1. ServiceListRS AirShoppingRS ShopProductRS 1.9 Provide capability to respond to a shopping request for ancillaries within a specific time range. See list for 1.1. ServiceListRS AirShoppingRS ShopProductRS 18

19 Ref # Requirements Messages* 1.10 Provide capability to respond to a shopping request for ancillaries priced using award miles. This assumes the passenger has proactively provided their loyalty program information for the purposes of this shopping response. See list for Provide capability to respond to a shopping request for a seat assignment. See list for 1.1 ServiceListRS AirShoppingRS ShopProductRS SeatAvailabilityRS 1.12 Provide capability to respond to a request for a seat map. SeatAvailabilityRS 1.13 Provide capability to respond with Offer Guarantee Time. The Offer Guarantee Time specifies the time by which the offer must be accepted to secure the price. Inventory may not be guaranteed Provide capability to respond with Inventory Guarantee Time. The Inventory Guarantee Time specifies how long the airline will guarantee inventory that is associated with the offer. This may or may not coincide with the Offer Time Limit or Payment Time Limit. For example a setting of 0 means the inventory is not guaranteed (inventory associated with the offer is subject to availability) Provide capability to respond with Payment Time Limit. The Payment Time Limit specifies the time by which payment must be received for the Order. If the Order is not filled within the Payment Time Limit, then the Order is subject to cancellation XML schema shall provide the flexibility to fully detail the product offering (ancillary) in the offer response. For example: o more leg room vs. pitch=37 inches o seat near galley o power port ServiceListRS AirShoppingRS SeatAvailabilityRS ShopProductRS ServiceListRS AirShoppingRS SeatAvailabilityRS ServiceListRS AirShoppingRS SeatAvailabilityRS ShopProductRS ServiceListRS AirShoppingRS ShopProductRS 19

20 Ref # o o o o o o o o Requirements over-ear head phone vs. ear bud Heads-up display unit rental extra recline social media access tablet in seat back spa pedicure vs. pedicure massage pre-reserved shower time vs. arrivals lounge shower reservation Messages* 20

21 RQ: ORA to POA (cont.) 5.2 Message Sequence Flows NOTE: Message Sequence Flow diagrams are provided for illustration purposes only. These diagrams are not intended to recommend any particular business process workflow and do not cover all possible scenarios and workflows as there can be an infinite number of possible constructions. Workflows will depend on the business process users will implement, and may be different from one implementation to another. Message pairs are atomic. 21

22 5.2.1 Use Case 0: Legacy Interline PNR booked, NDC interline ancillary shopping Flow Explanation Principal actors (with roles): Offer Responsible Airline (ORA) The airline initiating the interline ancillary shopping request on behalf of an ultimate end user which may be presented by a travel agent or other intermediary. Participating Offer Airline (POA) - The airline responding to an interline ancillary shopping request from an ORA. There may be one or multiple POAs in receipt of the shopping query. Customer (Traveller) The person shopping for ancillary services who may or may not be travelling. The traveller may communicate directly with the ORA via a web site or call centre. Alternatively s/he may use the services of an intermediary The Seller. Seller/Aggregator Intermediary such as a travel agent who may be involved in presenting the travellers requirements to the ORA and receiving the final offer on behalf of the traveller 22

23 Preconditions/Assumptions: Description: Precondition: An interline flight itinerary has already been booked using traditional industry methods and a Passenger Name Record (PNR) resides in the reservations system used by the ORA. This is the master PNR for the journey. Precondition: The PNR was created via the ORA s customer website or call center or ORA has a complete PNR itinerary provider by a GDS The ORA and all POAs have valid commercial agreements in place between them and have taken steps to ensure that they are compliant with any applicable competition law or regulation. This Use Case describes the process flow of requesting an offer of ancillary services that are available in conjunction with an existing flight itinerary. Steps to follow in the process: 1. The ORA receives a request for ancillary services from a seller/aggregator. 2. The ORA generates a list of POAs that may have valid product offerings that meet the Customer s needs and are able to respond to an NDC query. The list may be generated using the Airline Profile but this is not mandatory. The ORA may choose to generate its list using internal data. The ORA validates that appropriate commercial agreements exist with the POAs in the generated list The ORA performs a check that the request does not generate any violations of appropriate competition laws or regulations. 3. The ORA generates and sends an AirShoppingRQ or ServiceListRQ message to the POA(s) The request may seek information on Flight specific ancillaries, eg special meals Ancillaries available within a specific date or time range For non-flight ancillaries, ShopProductRQ will be used The message will include: Proposed validating carrier The entire proposed itinerary (e.g. all carriers, all flights) The true ORA Seller/Aggregator Information Point of Sale (point of payment/purchase) 4. Each POA receives the AirShoppingRQ, ServiceListRQ, or ShopProductRQ message and performs its own validation that the request conforms with commercial agreements and is not in contravention of competition law or regulation 23

24 5. Each POA determines what, if any, product offerings it wishes to return to the ORA. Such product offerings may or may not meet all of the criteria set out in the request. 6. Each POA formats and sends an AirShoppingRS, ServiceListRS, ShopProductRS message to the ORA which includes all of the ancillary product offers it wishes to make in response to the original request. This will include: Service Price to the ORA (i.e. the expected settlement value) per service. It is assumed the ORA will create a separate EMD coupon for each service. This is to support the settlement and revenue accounting processes. Tax Information per service unless the POA chooses to defer to ORA s tax application. 7. The ORA receives the response messages from all the POAs The ORA system determines which (if any) of the POA offers it wishes to include in its response to the seller/aggregator The ORA aggregates responses from all the POAs into unified offer(s) to the seller/aggregator 8. The ORA transmits its consolidated offer(s) to the seller/aggregator. 9. Post Conditions: The Customer, or the Seller acting on behalf of the Customer, is in receipt of a comprehensive, priced set of offers for ancillary services associated with his/her pre-existing flight itinerary. 24

25 5.2.2 Use Case 1: Interline NDC Order created, NDC ancillary shopping Flow Explanation Principal actors (with roles): Offer Responsible Airline (ORA) The airline initiating the interline ancillary shopping request on behalf of an ultimate end user which may be presented by a travel agent or other intermediary. Participating Offer Airline (POA) - The airline responding to an interline ancillary shopping request from an ORA. There may be one or multiple POAs in receipt of the shopping query. Customer (Traveller) The person shopping for ancillary services who may or may not be travelling. The traveller may communicate directly with the ORA via a web site or call centre. Alternatively s/he may use the services of an intermediary The Seller. Seller/Aggregator Intermediary such as a travel agent who may be involved in presenting the travellers requirements to the ORA and receiving the final offer on behalf of the traveller 25

26 Preconditions/Assumptions: Description: Precondition: An interline flight itinerary has already been booked and an Order resides in the reservations system used by the ORA. The ORA and all POAs have valid commercial agreements in place between them and have taken steps to ensure that they are compliant with any applicable competition law or regulation. This Use Case describes the process flow of requesting an offer of ancillary services that are available in conjunction with an existing flight itinerary. Steps to follow in the process: 1. The ORA receives a request for ancillary services from a seller/aggregator. 2. The ORA generates a list of POAs that may have valid product offerings that meet the Customer s needs and are able to respond to an NDC query. The list may be generated using the Airline Profile but this is not mandatory. The ORA may choose to generate its list using internal data. The ORA validates that appropriate commercial agreements exist with the POAs in the generated list The ORA performs a check that the request does not generate any violations of appropriate competition laws or regulations. 3. The ORA generates and sends an AirShoppingRQ or ServiceListRQ message to the POA(s) The request may seek information on Flight specific ancillaries, eg special meals Ancillaries available within a specific date or time range For non-flight related ancillaries, ShopProductRQ will be used The message will include: Proposed validating carrier The entire proposed itinerary (e.g. all carriers, all flights) The true ORA Seller/Aggregator Information Point of Sale (point of payment/purchase) 4. Each POA receives the AirShoppingRQ, ServiceListRQ, or ShopProductRQ message and performs its own validation that the request conforms with commercial agreements and is not in contravention of competition law or regulation 5. Each POA determines what, if any, product offerings it wishes to return to the ORA. Such product offerings may or may not meet all of the criteria set out in the request. 26

27 6. Each POA formats and sends an AirShoppingRS, ServiceListRS, or ShopProductRS message to the ORA which includes all of the ancillary product offers it wishes to make in response to the original request. This will include: Service Price to the ORA (i.e. the expected settlement value) per service. It is assumed the ORA will create a separate EMD coupon for each service. This is to support the settlement and revenue accounting processes. Tax Information per service unless the POA chooses to defer to ORA s tax application. 7. The ORA receives the response messages from all the POAs The ORA system determines which (if any) of the POA offers it wishes to include in its response to the seller/aggregator The ORA aggregates responses from all the POAs into unified offer(s) to the seller/aggregator 8. The ORA transmits its consolidated offer(s) to the seller/aggregator. 9. Post Conditions: The Customer, or the Seller acting on behalf of the Customer, is in receipt of a comprehensive, priced set of offers for ancillary services associated with his/her pre-existing flight itinerary. 27

28 5.2.3 Use Case 2: Request a list of services and shop from the list. No pre-existing booking or order. Flow Explanation Principal actors (with roles): Offer Responsible Airline (ORA) The airline initiating the interline ancillary shopping request on behalf of an ultimate end user which may be presented by a travel agent or other intermediary. Participating Offer Airline (POA) - The airline responding to an interline ancillary shopping request from an ORA. There may be one or multiple POAs in receipt of the shopping query. Customer (Traveller) The person shopping for ancillary services who may or may not be travelling. The traveller may communicate directly with the ORA via a web site or call centre. Alternatively s/he may use the services of an intermediary The Seller. 28

29 Seller/Aggregator Intermediary such as a travel agent who may be involved in presenting the travellers requirements to the ORA and receiving the final offer on behalf of the traveller Preconditions/Assumptions: Description: A NDC order or legacy PNR does not exist for the customer An AirShopping session may be in progress where the seller/aggregator is in possession of an offer from ORA The ORA and all POAs have valid commercial agreements in place between them and have taken steps to ensure that they are compliant with any applicable competition law or regulation. This Use Case describes the process flow of requesting an offer of ancillary services that are available for a specified route. The specified route may be an origin and destination data taken from an AirShoppingRS. Steps to follow in the process: 1. The ORA receives a request for ancillary services from a seller/aggregator. 2. The ORA generates a list of POAs that may have valid product offerings that meet the Customer s needs and are able to respond to an NDC query. The list may be generated using the Airline Profile but this is not mandatory. The ORA may choose to generate its list using internal data. The ORA validates that appropriate commercial agreements exist with the POAs in the generated list The ORA performs a check that the request does not generate any violations of appropriate competition laws or regulations. 3. The ORA generates and sends a ServiceListRQ message to the POA(s) The request may seek information on Flight specific ancillaries, eg special meals Flight specific ancillaries available within a specific date or time range The message will include: Proposed validating carrier The entire proposed itinerary (e.g. all carriers, all flights) The true ORA Seller/Aggregator Information Point of Sale (point of payment/purchase) 29

30 4. Each POA receives the ServiceListRQ message and performs its own validation that the request conforms with commercial agreements and is not in contravention of competition law or regulation 5. Each POA determines what, if any, product offerings it wishes to return to the ORA. Such product offerings may or may not meet all of the criteria set out in the request. 6. Each POA formats and sends a ServiceListRS message to the ORA which includes all of the ancillary product offers it wishes to make in response to the original request. This will include: Service Price to the ORA (i.e. the expected settlement value) per service. It is assumed the ORA will create a separate EMD coupon for each service. This is to support the settlement and revenue accounting processes. Tax Information per service unless the POA chooses to defer to ORA s tax application. 7. The ORA receives the response messages from all the POAs The ORA system determines which (if any) of the POA offers it wishes to include in its response to the seller/aggregator The ORA aggregates responses from all the POAs into unified offer(s) to the seller/aggregator 8. The ORA transmits its consolidated offer(s) to the seller/aggregator. 9. Post Conditions: The Customer, or the Seller acting on behalf of the Customer, is in receipt of a comprehensive, priced set of offers for flight-specific ancillary services. 30

31 5.2.4 Use Case 3: Shopping response for inventory controlled ancillaries where the inventory is guaranteed for a specified period of time Flow Explanation Principal actors (with roles): Offer Responsible Airline (ORA) The airline initiating the interline ancillary shopping request on behalf of an ultimate end user which may be presented by a travel agent or other intermediary. Participating Offer Airline (POA) - The airline responding to an interline ancillary shopping request from an ORA. There may be one or multiple POAs in receipt of the shopping query. Customer (Traveller) The person shopping for ancillary services who may or may not be travelling. The traveller may communicate directly with the ORA via a web site or call centre. Alternatively s/he may use the services of an intermediary The Seller. Seller/Aggregator Intermediary such as a travel agent who may be involved in presenting the travellers requirements to the ORA and receiving the final offer on behalf of the traveller 31

32 Preconditions/Assumptions: Description: The ORA and all POAs have valid commercial agreements in place between them and have taken steps to ensure that they are compliant with any applicable competition law or regulation. An NDC Order may or not exist prior to ancillary shopping This Use Case describes the process flow of requesting an offer of inventory controlled ancillary services that are available where the inventory is guaranteed for a specified period of time. Steps to follow in the process: 1. The ORA receives a request for ancillary services from a seller/aggregator. 2. The ORA generates a list of POAs that may have valid product offerings that meet the Customer s needs and are able to respond to an NDC query. The list may be generated using the Airline Profile but this is not mandatory. The ORA may choose to generate its list using internal data. The ORA validates that appropriate commercial agreements exist with the POAs in the generated list The ORA performs a check that the request does not generate any violations of appropriate competition laws or regulations. 3. The ORA generates and sends an AirShoppingRQ or ServiceListRQ message to the POA(s) The request may seek information on Flight specific ancillaries, eg special meals Ancillaries available within a specific date or time range For non-flight related ancillaries, ShopProductRQ will be used The message will include: Proposed validating carrier The entire proposed itinerary (e.g. all carriers, all flights) The true ORA Seller/Aggregator Information Point of Sale (point of payment/purchase) 4. Each POA receives the AirShoppingRQ, ServiceListRQ or ShopProductRQ message and performs its own validation that the request conforms with commercial agreements and is not in contravention of competition law or regulation 5. Each POA determines what, if any, product offerings it wishes to return to the ORA. Such product offerings may or may not meet all of the criteria set out in the request. Determine if inventory is available and inventory guarantee time 32

33 RQ: ORA to POA (cont.) 6. Each POA formats and sends an AirShoppingRS, ServiceListRS, or ShopProductRS message to the ORA which includes all of the ancillary product offers it wishes to make in response to the original request. This will include: Service Price to the ORA (i.e. the expected settlement value) per service. It is assumed the ORA will create a separate EMD coupon for each service. This is to support the settlement and revenue accounting processes. Tax Information per service unless the POA chooses to defer to ORA s tax application. Including the inventory guarantee time 7. The ORA receives the response messages from all the POAs The ORA system determines which (if any) of the POA offers it wishes to include in its response to the seller/aggregator The ORA aggregates responses from all the POAs into unified offer(s) to the seller/aggregator The ORA may communicate the POA s inventory guarantee time as part of the offer(s). If so, it shall be less than or equal to the POA guarantee time. 8. The ORA transmits its consolidated offer(s) to the seller/aggregator. 9. Post Conditions: The Customer, or the Seller acting on behalf of the Customer, is in receipt of a comprehensive, priced set of offers for ancillary services associated with his/her pre-existing flight itinerary. 33

34 5.2.5 Use Case 4: Shopping for ancillaries on multiple POAs Flow Explanation Principal actors (with roles): Offer Responsible Airline (ORA) The airline initiating the interline ancillary shopping request on behalf of an ultimate end user which may be presented by a travel agent or other intermediary. Participating Offer Airline (POA) - The airline responding to an interline ancillary shopping request from an ORA. There may be one or multiple POAs in receipt of the shopping query. Customer (Traveller) The person shopping for ancillary services who may or may not be travelling. The traveller may communicate directly with the ORA via a web site or call centre. Alternatively s/he may use the services of an intermediary The Seller. Seller/Aggregator Intermediary such as a travel agent who may be involved in presenting the travellers requirements to the ORA and receiving the final offer on behalf of the traveller Preconditions/Assumptions: Precondition: An interline NDC order for the following flight itinerary has already been created, and an Order exists in the ORA s system: LON-XX-SIN-YY-SYD-ZZ-BKK-XX-LON 34

35 XX receives a request for a pre-reserved seat assignment for all travel on the itinerary. XX becomes the ORA. XX cannot fulfill the request for SIN-SYD or SYD-BKK and must send a request to YY and ZZ respectively. YY and ZZ become POAs The ORA and all POAs have valid commercial agreements in place between them and have taken steps to ensure that they are compliant with any applicable competition law or regulation. Description: This use case describes the process of the ORA shopping for ancillaries on multiple POAs using direct NDC communication between the ORA and each POA. Steps to follow in the process: 1. The ORA (XX) receives a request for a pre-reserved seat assignment from a seller/aggregator. XX cannot fulfill the request on the SIN-SYD and SYD-BKK sectors. 2. The ORA (XX) generates a list of POAs that may have valid product offerings that meet the Customer s needs and are able to respond to an NDC query. The list may be generated using the Airline Profile but this is not mandatory. The ORA may choose to generate its list using internal data. The ORA validates that appropriate commercial agreements exist with the POAs in the generated list The ORA performs a check that the request does not generate any violations of appropriate competition laws or regulations. 3. Airlines YY and ZZ are validated as POAs who will accept NDC requests for pre-reserved seat assignments for SIN-SYD and SYD-BKK respectively. 4. The ORA generates and sends a separate SeatAvailabilityRQ, AirShoppingRQ or ServiceListRQ message to each POA: YY for SIN-SYD; and ZZ for SYD-BKK The request may seek information on o Flight specific ancillaries, eg special meals o Ancillaries available within a specific date or time range o For non-flight related ancillaries, the ShopProductRQ will be used The message will include: o Proposed validating carrier o The entire proposed itinerary (e.g. all carriers, all flights) o The true ORA o Seller/Aggregator o Point of Sale (point of payment/purchase) 35

36 5. Each POA receives the SeatAvailabilityRQ, AirShoppingRQ, ServiceListRQ or ShopProductRQ message and performs its own validation that the request conforms with commercial agreements and is not in contravention of competition law or regulation. 6. Each POA determines what, if any, product offerings it wishes to return to the ORA. Such product offerings may or may not meet all of the criteria set out in the request. YY (POA) searches for pre-reserved seat assignment products for SIN-SYD and any other products they want to offer ZZ (POA) searches for pre-reserved seat assignment products for SYD-BKK and any other products they want to offer 10. Each POA formats and sends a SeatAvaliabilityRS, AirShoppingRS, ServiceListRS or ShopProductRS message to the ORA (XX) which includes all of the ancillary product offers it wishes to make in response to the original request. This will include: Service Price to the ORA (i.e. the expected settlement value) per service. It is assumed the ORA will create a separate EMD coupon for each service. This is to support the settlement and revenue accounting processes. Tax Information per service unless the POA chooses to defer to ORA s tax application. YY (POA) sends a response with an offer for a pre-reserved seat assignment for SIN-SYD and any other ancillary product offers they want to make in response to XX s request ZZ (POA) sends a response with an offer for a pre-reserved seat assignment for SYD-BKK and any other ancillary product offers they want to make in response to XX s request 7. The ORA (XX) receives the response messages from all the POAs The ORA system determines which (if any) of the POA offers it wishes to include in its response to the seller/aggregator The ORA aggregates responses from all the POAs into unified offer(s) to the seller/aggregator 8. The ORA transmits its consolidated offer(s) to the seller/aggregator. 9. Post Conditions: The Customer, or the Seller acting on behalf of the Customer, is in receipt of a comprehensive, priced set of offers for ancillary services associated with his/her preexisting flight itinerary. 36

37 5.2.6 Use Case 5: Shopping response for inventory controlled ancillaries where the inventory is not guaranteed Flow Explanation Principal actors (with roles): Offer Responsible Airline (ORA) The airline initiating the interline ancillary shopping request on behalf of an ultimate end user which may be presented by a travel agent or other intermediary. Participating Offer Airline (POA) - The airline responding to an interline ancillary shopping request from an ORA. There may be one or multiple POAs in receipt of the shopping query. Customer (Traveller) The person shopping for ancillary services who may or may not be travelling. The traveller may communicate directly with the ORA via a web site or call centre. Alternatively s/he may use the services of an intermediary The Seller. 37

38 Seller/Aggregator Intermediary such as a travel agent who may be involved in presenting the travellers requirements to the ORA and receiving the final offer on behalf of the traveller Preconditions/Assumptions: Description: The ORA and all POAs have valid commercial agreements in place between them and have taken steps to ensure that they are compliant with any applicable competition law or regulation. An NDC Order may or not exist prior to ancillary shopping This Use Case describes the process flow of requesting an offer of inventory controlled ancillary services that are available where the inventory is not guaranteed. Steps to follow in the process: 1. The ORA receives a request for ancillary services from a seller/aggregator. 2. The ORA generates a list of POAs that may have valid product offerings that meet the Customer s needs and are able to respond to an NDC query. The list may be generated using the Airline Profile but this is not mandatory. The ORA may choose to generate its list using internal data. The ORA validates that appropriate commercial agreements exist with the POAs in the generated list The ORA performs a check that the request does not generate any violations of appropriate competition laws or regulations. 3. The ORA generates and sends an AirShoppingRQ or ServiceListRQ message to the POA(s) The request may seek information on Flight specific ancillaries, eg special meals Ancillaries available within a specific date or time range For non-flight related ancillaries, ShopProductRQ will be used The message will include: Proposed validating carrier The entire proposed itinerary (e.g. all carriers, all flights) The true ORA Seller/Aggregator Point of Sale (point of payment/purchase) 4. Each POA receives the AirShoppingRQ, ServiceListRQ or ShopProductRQ message and performs its own validation that the request conforms with commercial agreements and is not in contravention of competition law or regulation 38

39 RQ: ORA to POA (cont.) 5. Each POA determines what, if any, product offerings it wishes to return to the ORA. Such product offerings may or may not meet all of the criteria set out in the request. POA may determine if the product is available for sale 6. Each POA formats and sends an AirShoppingRS, ServiceListRS, or ShopProductRS message to the ORA which includes all of the ancillary product offers it wishes to make in response to the original request. This will include: Service Price to the ORA (i.e. the expected settlement value) per service. It is assumed the ORA will create a separate EMD coupon for each service. This is to support the settlement and revenue accounting processes. Tax Information per service unless the POA chooses to defer to ORA s tax application. Including the inventory guarantee time equals zero (subject to availability) 7. The ORA receives the response messages from all the POAs The ORA system determines which (if any) of the POA offers it wishes to include in its response to the seller/aggregator The ORA aggregates responses from all the POAs into unified offer(s) to the seller/aggregator The ORA shall communicate the POA s ancillary guarantee is zero (subject to availability) 8. The ORA transmits its consolidated offer(s) to the seller/aggregator. 9. Post Conditions: The Customer, or the Seller acting on behalf of the Customer, is in receipt of a comprehensive, priced set of offers for ancillary services associated with his/her pre-existing flight itinerary. 39

40 5.2.7 Use Case 6: Initial POA becomes Sub-ORA by cascading to another airline Description: Airline ZZ receives shopping request for extra-legroom seat on a JFK-ZZ-ZRH-YY-BKK-YY*/XX-HKT, therefore Airline ZZ becomes ORA (Offer Responsible Airline). As the ORA cannot fulfil the seat request for ZRH-YY-BKK-YY*/XX-HKT, it needs to request from Airline YY which will become a POA (Participating Offer Airline). The POA itself is only marketing but not the operating carrier on the BKK-YY*/XX-HKT route, therefore it needs to cascade the request to airline XX, i.e. another POA (Sub-POA). Therefore the initial POA will become or gets the role of another ORA. Although this example shows a codeshare relationship between YY and XX, this could also apply to the situation where YY and XX are interline partners and the BKK-HKT flight is marketed and operated by XX. Principal actors (with roles): Offer Responsible Airline (ORA) Sub-ORA - Initial Participating Offer Airline (POA) which assumes the role of a Sub-ORA Sub-POA Participating Offer Airline (POA) which receives requests from a Sub-ORA 40

41 Preconditions/Assumptions: The ORA and all POAs have valid commercial agreements in place between them and have taken steps to ensure that they are compliant with any applicable competition law or regulation. Steps to follow in the process 1. The ORA receives a request for ancillary services from a seller/aggregator. 2. The ORA generates a list of POAs that may have valid product offerings that meet the Customer s needs and are able to respond to an NDC query. The list may be generated using the Airline Profile but this is not mandatory. The ORA may choose to generate its list using internal data. The ORA validates that appropriate commercial agreements exist with the POAs in the generated list The ORA performs a check that the request does not generate any violations of appropriate competition laws or regulations. 3. The ORA generates and sends an AirShoppingRQ or ServiceListRQ message to the POA(s) The request may seek information on Flight specific ancillaries, eg seat request Ancillaries available within a specific date or time range The message will include: Proposed validating carrier The entire proposed itinerary (e.g. all carriers, all flights) The true ORA The seller/ aggregator Point of Sale (point of payment/purchase) 4. Each POA receives the AirShoppingRQ or ServiceListRQ message and performs its own validation that the request conforms with commercial agreements and is not in contravention of competition law or regulation 5. Each POA determines it is unable to fulfill the offer on the full itinerary proposed but is willing to respond with NDC offer. Such product offerings may or may not meet all of the criteria set out in the request. 6. The POA generates a list of Sub-POAs that may have valid product offerings that meet the Customer s needs for the portion of the itinerary that they are unable to fulfill. The list may be generated using the Airline Profile but this is not mandatory. The POA may choose to generate its list using internal data. The POA validates that appropriate commercial agreements exist with the Sub-POAs in the generated list The POA performs a check that the request does not generate any violations of appropriate competition laws or regulations. 41

42 7. The POA, acting as a Sub-ORA, generates and sends an AirShoppingRQ or ServiceListRQ message to the Sub-POA(s) The message will include: Proposed validating carrier The entire proposed itinerary (e.g. all carriers, all flights) The true ORA The seller/ aggregator Point of Sale (point of payment/purchase) 8. Each Sub-POA receives the AirShoppingRQ or ServiceListRQ message and performs its own validation that the request conforms with commercial agreements and is not in contravention of competition law or regulation 9. Each Sub-POA formats and sends an AirShoppingRS or ServiceListRS message to the Sub-ORA which includes all of the ancillary product offers it wishes to make in response to the original request The message will include: The Sub-POAs service price and tax information Service Price to the POA (i.e. the expected settlement value) per service. It is assumed the ORA will create a separate EMD coupon for each service. This is to support the settlement and revenue accounting processes. Tax Information per service unless the POA chooses to defer to POA s tax application 10. The Sub-ORA receives the response messages from all the Sub-POAs The Sub-ORA system determines which (if any) of the Sub-POA offers it wishes to include in its response to the true ORA The Sub-ORA aggregates responses from all the Sub-POAs into unified offer(s) to the true ORA The Sub-ORA formats and sends an AirShoppingRS or ServiceListRS message to the true ORA which includes all of the ancillary product offers it wishes to make in response to the original request The message will include: The Sub-POAs service price and tax information Service Price to the ORA (i.e. the expected settlement value) per service. It is assumed the ORA will create a separate EMD coupon for each service. This is to support the settlement and revenue accounting processes. Tax Information per service unless the POA chooses to defer to ORA s tax application 11. The ORA receives the response messages from all the POAs The ORA system determines which (if any) of the POA offers it wishes to include in its response to the seller/aggregator The ORA aggregates responses from all the POAs into unified offer(s) to the seller/aggregator 12. The ORA transmits its consolidated offer(s) to the seller/aggregator. 13. Post Conditions: 42

43 The Customer, or the Seller acting on behalf of the Customer, is in receipt of a comprehensive, priced set of offers for ancillary services associated with his/her pre-existing flight itinerary Use Case 7: Non-flight related ancillary shopping where ORA and POA have ATI Flow Explanation Principal actors (with roles): Offer Responsible Airline (ORA) The airline initiating the interline ancillary shopping request on behalf of an ultimate end user which may be presented by a travel agent or other intermediary. Participating Offer Airline (POA) - The airline responding to an interline ancillary shopping request from an ORA. There may be one or multiple POAs in receipt of the shopping query. 43

44 Customer (Traveller) The person shopping for ancillary services who may or may not be travelling. The traveller may communicate directly with the ORA via a web site or call centre. Alternatively s/he may use the services of an intermediary The Seller. Seller/Aggregator Intermediary such as a travel agent who may be involved in presenting the travellers requirements to the ORA and receiving the final offer on behalf of the traveller Preconditions/Assumptions: Description: Precondition: The ORA has Antitrust Immunity with the POA(s) It is the responsibility of the ORA and POA to ensure that these non-flight-specific ancillaries are only sold in conjunction with journeys where they have Antitrust Immunity (ATI) per IATA legal guidelines. This Use Case describes the process flow of requesting an offer of non-flight-specific ancillary services. Steps to follow in the process: 1. The ORA receives a request for ancillary services from a seller/aggregator. 2. The ORA generates a list of POAs that may have valid product offerings that meet the Customer s needs and are able to respond to an NDC query. The list may be generated using the Airline Profile but this is not mandatory. The ORA may choose to generate its list using internal data. The ORA validates that appropriate commercial agreements exist with the POAs in the generated list The ORA performs a check that the request does not generate any violations of appropriate competition laws or regulations, based on point of sale or other business rules. 3. The ORA generates and sends an ShopProductRQ message to the POA(s) The request may seek information on Non flight specific ancillaries eg lounge access Ancillaries available within a specific date or time range The message will include: Proposed validating carrier The true ORA Seller/Aggregator Information Point of Sale (point of payment/purchase) 4. Each POA receives the ShopProductRQ message and performs its own validation that the request conforms with commercial agreements and is not in contravention of competition law or regulation, based on point of sale or other business rules. 44

45 5. Each POA determines what, if any, product offerings it wishes to return to the ORA. Such product offerings may or may not meet all of the criteria set out in the request. 6. Each POA formats and sends an ShopProductRS message to the ORA which includes all of the ancillary product offers it wishes to make in response to the original request. This will include: Service Price to the ORA (i.e. the expected settlement value) per service. It is assumed the ORA will create a separate EMD coupon for each service. This is to support the settlement and revenue accounting processes. Tax Information per service unless the POA chooses to defer to ORA s tax application 7. The ORA receives the response messages from all the POAs The ORA system determines which (if any) of the POA offers it wishes to include in its response to the seller/aggregator The ORA aggregates responses from all the POAs into unified offer(s) to the seller/aggregator 8. The ORA transmits its consolidated offer(s) to the seller/aggregator. 9. Post Conditions: The Customer, or the Seller acting on behalf of the Customer, is in receipt of a comprehensive, priced set of offers for non-flight specific ancillary services. 45

46 5.2.9 Use Case 8: Ancillary Service Shopping where ORA proposes a specific price for a flightspecific ancillary Flow Explanation Principal actors (with roles): Offer Responsible Airline (ORA) The airline initiating the interline ancillary shopping request on behalf of an ultimate end user which may be presented by a travel agent or other intermediary. Participating Offer Airline (POA) - The airline responding to an interline ancillary shopping request from an ORA. There may be one or multiple POAs in receipt of the shopping query. Customer (Traveller) The person shopping for ancillary services who may or may not be travelling. The traveller may communicate directly with the ORA via a web site or call centre. Alternatively s/he may use the services of an intermediary The Seller. Seller/Aggregator Intermediary such as a travel agent who may be involved in presenting the travellers requirements to the ORA and receiving the final offer on behalf of the traveller 46