• Print
  • Dark
    Light

Overview

  • Updated on 27 Nov 2018
  • 1 minute to read
  • Contributors

Introduction

Special Service Requests (SSR) are best described as snippets or strings of information in an Airline Reservations System that are formatted for programmatic use and ingestion to describe a service or additional piece of information that is required about the passenger. Initially SSR’s were used for special requests (such as a wheelchair request) at the Airport and are only sent to carriers participating in the Itinerary prior to travel. However, their flexibility has lead them to be used for a variety of purposes over the years and are used to store non service related items, such as email addresses, postal address, GST information, disabled information etc. In the move to distribution over XML using the standards set forth by the Offers and Orders Groups, the notion of a traditional ‘SSR’ as a formatted string does not conform to the transmission standards of today where XML, JSON or other is being used.

This section describes how the SSR information should be modelled and carried through new distribution messages.

The benefit of mapping the SSR information into the model allows for:

  • A standardized way for Sellers to request and receive services
  • A richer model for information to be broadcast and received
  • The ability for a Seller to interact with a carrier using a PSS and SSRs and a Carrier using an Order Management system in the same manor
  • Minimal impact for a Seller if an airline changes their internal service delivery fulfilment.

This section will detail how SSR’s that are used today and how they should be mapped to an XML message for Sellers and interline parties to understand and use. The use of an SSR within the context of an XML message will enable the reconstruction of an SSR on either side. There is no loss of information, but a standardized way to communicate this information across parties.

image.png