Types

Before you move on to creating a scheme, it's important to select the right type for your needs. Let's take a look at the various scheme types and their individual characteristics.

How to choose the right scheme type

The scheme type defines its functionality and the objects it works with — PNRs, tickets, or EMDs. It also determines how the scheme collects objects for processing and what actions are available inside it.

The objects of processing

The primary object in Trava is the PNR, which may include tickets and EMDs. Tickets and EMDs can also be processed separately — without loading the full PNR. The scheme type determines which object is the primary one and what actions are available for it.

Scheme types by their purposes

Analyze the process you want to automate. Clearly define the tasks and main objects involved — whether it's the entire PNR, individual tickets, EMDs, or data from a client database.

PNR processing

PNR processing schemes are primarily used for queue management, client communication, and other non-calculation processes.

Available capabilities:

• Adding, deleting, and reading FOP and various remarks (SSR, OSI, RM) in PNRs
• Issuing, revalidating, fully refunding, and canceling tickets
• Canceling bookings
• Placing and removing PNRs from the queue
• Sending notifications via email and HTTP
• Configuring interactions with other schemes
• Adding and removing tags
• Canceling EMD
• Refunding EMD (only for 1A)
• Restoring segments (only for 1S and 1G)
• Integration with virtual cards (Pliant, Wex)*
• Connecting with Mid Office*
• Voluntary ticket refund – reading category 16 (with restrictions for 1A)

Processed PNR data will be stored on the Reservation Processing page.

ℹ Note: requires additional connection. * connects in GDS.

PNR pricing

The main purpose of this scheme is to optimize fares — searching for and rebooking to lower fares — as well as issuing tickets.

Upon receiving a PNR for processing, the system performs an extensive analysis at the Start step: checking the status of segments, fares, and other parameters.

The capabilities largely repeat those of PNR processing schemes. They also include:

• Advanced configuration of the Start for PNR assessment
• Searching for the lowest fare on booked segments
• Forecasting ticket prices for the next day
• Processing different fare types and baggage conditions

Limitations:

• There is a limitation on the functionality of the HX segments recovery. Recovery of segments is only possible in the settings of the Start element (only for 1S and 1G).
• The Accept schedule changes action is unavailable. This condition will change the original state of segments during processing, resulting in incorrect calculations at the Start step.
• Processing a PNR with schedule changes and absent flight segments will be rejected.

ℹ Note: For one office (or a group of offices), we recommend having only one PNR pricing scheme. If one booking is processed by two pricing schemes simultaneously, errors may occur.

Processed PNR data will be stored on the Reservation Processing page.

PNR redirector

The PNR redirector is designed to process PNRs from GDS queues and other schemes. It reads specific parameters within the PNR and redirects it to other schemes based on defined conditions.

This type of scheme is especially useful for queue tracking. Unlike others, it can handle grouped PNRs (for GDS Amadeus — up to 50 PNRs simultaneously).

Available capabilities:

• Reading PNR
• Cancelling PNR
• Adding and removing remarks
• Working with queues (putting in / removing from the queue)
• Adding and removing tags
• Redirecting PNR to another scheme
• Stopping the processing of PNR by another scheme
• Sending notifications via email and HTTP

Processed PNR data will be stored on the Reservation Processing page.

Ticket processing

These schemes are used to process tickets, including automated refunds. The primary object of processing is the ticket itself.

Available capabilities:

• Reading the ticket
• Canceling the ticket
• Reading the refund rules for the ticket
• Tracking itinerary changes based on specified parameters
• Processing a full refund for the ticket (forced refund)
• Refunding airport fees associated with the ticket
• Adding and removing tags
• Processing / checking the handling of the ticket by another system
• Sending notifications via email and HTTP

Schemes of this type operate with or without PNR loading. The listed capabilities pertain to working with tickets without PNR loading.

With PNR loading, the list of capabilities is broader — it includes exchanges with revalidation, remarks, and queues.

Processed ticket data will be stored on the Document Processing page.

EMD processing

For this type of scheme, the EMD is the primary object of processing. The EMD number is required.

Available capabilities:

• Reading EMD
• Adding and removing tags
• Redirecting to another scheme
• Sending notifications via email and HTTP
• Processing full EMD refunds (only for 1A)

Processed EMD data will be stored on the Document Processing page.

ℹ Note: Schemes of this type can operate with or without PNR loading. The listed capabilities apply to cases where the EMD is processed without PNR loading.

Mid-office processing

Schemes of this type process PNR data from client databases using the Transfer program. Data exchange is carried out based on predefined parameters.

Available capabilities:

• Reading objects from the client's database
• Creating invoice
• Adding and removing tags
• Sending notifications via email and HTTP
• Retrieving specific data from the PNR
• Checking if the PNR or ticket is being processed by other schemes

Data about the processed PNR will be stored on the Reservation Processing page.

Choosing the scheme type

Click New Scheme on the Schemes page. A dialog window will open, prompting you to choose the type of scheme.

⚠ Important: Once the type of scheme is selected, it cannot be changed.

When you're done choosing the scheme type, proceed to configuring its properties.