Structure of the Invol Servicing
  • Updated on 19 May 2020
  • 2 minutes to read
  • Contributors
  • Print
  • Dark
    Light

Structure of the Invol Servicing

  • Print
  • Dark
    Light

Use Cases

Airline (ORA) performs Planned Schedule Change

“The Airline (ORA) performs Planned Schedule Change. The Airline (ORA) needs to communicate the changes to the Order. The Airline (ORA) notifies the following indicators/data: Airline URI, whether an acceptance is needed, a time limit to accept the changes, consequence of inaction, and FareWaiver Code details (if applicable).”

In this use case, the following scenarios are covered:

  • Notification of flight segment time changes (Planned Schedule Change)
  • Notification of flight segment number changes (Planned Schedule Change)
  • Notification of flight segment arrival and/or departure changes (Planned Schedule Change)
  • Notification of flight equipment changes (Planned Schedule Change)
  • Notification of flight cancellation (Planned Schedule Change)
  • Notification of flight changes (Planned Schedule Change)
  • Notification of Airline URI
  • Notification of Planned Schedule Change acceptance
  • Notification of Planned Schedule Change time limit
  • Notification of Planned Schedule Change consequence of inaction
  • Notification of Planned Schedule Change FareWaiver code (if applicable)

Seller is informed of the Airline (ORA) Planned Schedule Change

“After the Airline (ORA) performs the Planned Schedule Change, the Seller is informed (and aware) that a Planned Schedule Change has occurred and requires acceptance.”

In this use case, the following scenarios are covered:

  • Seller is informed that an Order has undergone a Planned Schedule Change
  • Seller is informed a Planned Schedule Change acceptance is needed

Seller accepts Airline (ORA) Planned Schedule Change

“After receiving the notification of Planned Schedule Change from Airline (ORA) and if an acceptance is required, the Seller is able to accept the Planned Schedule Change.”

In this use case, the following scenario is covered:

  • Seller can accept a Planned Schedule Change

Seller rejects Airline (ORA) Planned Schedule Change

After receiving the notification of Planned Schedule Change from Airline (ORA), the Seller is able to reject the Planned Schedule Change and reshop for alternate solutions with the FareWaiver Code.”

In this use case, the following scenarios are covered:

  • Seller can transmit the FareWaiver Code details during reshop
  • Seller can reshop with FareWaiver Code and Airline (ORA) can respond accordingly
  • Seller can cancel with FareWaiver Code and Airline (ORA) can respond accordingly
  • Seller can view the Order after accepting a reshop Offer

Business Functions

01. Inform Seller of Planned Schedule Change and any required follow up actions

02. Acceptance of a Planned Schedule Change

03. Reshop following a Planned Schedule Change

04. Cancellation following a Planned Schedule Change

Message Flow

image.png