Table of Contents
Schemes
Create a new scheme
High level:
- In the module Schemes, click New Scheme or Create from File
- Add a name and choose scheme type
- Enter scheme properties
- Build the process
- Save the scheme
- Activate the scheme
Notes:
-Create from file: upload an existing json file and modify the scheme as per you needs.
-You need one scheme per GDS you will process bookings for (eg you cannot process bookings of different GDS in the same scheme).
There are five different types of schemes
- Mid-Office
- Non-pricing
- PNR redirector
- Pricing and Ticketing
- Ticket processing
The properties of each scheme
| Properties per scheme type | Mid-Office | Non-pricing | PNR redirector | Pricing and Ticketing | Ticket processing | Description |
|---|---|---|---|---|---|---|
| Name | Y | Y | Y | Y | Y | Enter a scheme name |
| Run scheme in test mode | Y | Y | Y | Y | Y | If selected, scheme will be run in test mode without saving changes to mid-office database. |
| Reservation must be accessible in GDS for ticket processing | N/A | N/A | N/A | N/A | Y | Processing of ticket will be aborted if this option is enabled and reservation is no longer accessible in GDS. |
| Use historical flight segment data | N/A | Y | Y | N/A | Y | If no flight segments exist in the PNR, the system will use the last state of the itinerary before flight segments were removed. Not available for Apollo, Galileo or Worldspan. |
| GDS | N/A | Y | Y | Y | Y | Amadeus, Apollo, Galileo, Sabre, Worldspan |
| Operational PCC/Office ID | N/A | Y | Y | Y | Y | In which PCC/Office ID the scheme should work in |
| Ticketing City | N/A | N/A | N/A | Y | Y | Ticketing city code of your IATA/ARC ticketing office |
| Ticketing Currency | N/A | N/A | N/A | Y | Y | Ticketing currency code of your IATA/ARC ticketing office |
| Description | Y | Y | Y | Y | Y | Enter for example a description what the scheme does (optional) |
| GDS queue for error notification | N/A | Y | Y | Y | N/A | Define which PCC's/Office ID and queue it should send errors to |
| PCC/Office ID | N/A | Y | Y | Y | N/A | PCC's/Office ID it should send error PNRs to |
| Queue number | N/A | Y | Y | Y | N/A | Queue it should send error PNRs to |
| PIC-code/Category (optional) | N/A | Y | Y | Y | N/A | PIC/Category (optional) it should use for error PNRs |
| Remark | N/A | Y | Y | Y | N/A | Enter a remark to be added to the PNR to make it easier for the agent to interpret the error (optional) |
| E-mail address for error notification | Y | Y | Y | Y | Y | Email address/es it should send error PNRs to (separate addresses with a comma or semi-colon) |
| To, CC and BCC | Y | Y | Y | Y | Y | Recipient/s of the error email notifications |
| Importance | Y | Y | Y | Y | Y | Low, Normal, High. Choose urgency level. |
| Sender's name | Y | Y | Y | Y | Y | Name of the sender, for example: “TVK scheme error notification” |
| Sender's email | Y | Y | Y | Y | Y | Default is the email address in the System settings under Custom e-mail settings, but it´s possible to override it by entering any other address. |
Actions and sources available per scheme
| Sources and Actions per Scheme type | Mid-Office | Non-pricing | PNR redirector | Pricing and Ticketing | Ticket processing |
|---|---|---|---|---|---|
| Source: Database query | Y | Y | Y | Y | Y |
| Source: External start | Y | Y | Y | Y | Y |
| Source: GDS queue | N | Y | Y | Y | N |
| Source: REST | Y | Y | N | Y | N |
| Start | Y | Y | Y | Y | Y |
| Finish | Y | Y | Y | Y | Y |
| Pause | Y | Y | Y | Y | Y |
| Repeat | Y | Y | Y | Y | Y |
| Conditions | Y | Y | Y | Y | Y |
| Add retention segment | N | Y | Y | Y | N |
| Cancel itinerary | N | Y | N | Y | N |
| Cancel virtual card | N | Y | N | Y | N |
| Commit changes | N | Y | N | Y | N |
| End and Retrieve PNR (ER) | N | Y | N | Y | N |
| Enter OSI message | N | Y | Y | Y | N |
| Even Exchange | N | Y | N | Y | N |
| Find lower fare | N | N | N | Y | N |
| Full Refund | N | Y | N | Y | Y |
| Get published fares | N | N | N | Y | N |
| Http Notification | Y | Y | Y | Y | Y |
| Issue ticket | N | N | N | Y | N |
| Issue virtual card | N | Y | N | Y | N |
| Move to another queue | N | Y | Y | Y | N |
| Place to queue | N | Y | Y | Y | N |
| Process by another scheme | N | Y | Y | Y | N |
| QC remark check | N | Y | N | Y | N |
| Remove from queue | N | Y | Y | Y | N |
| Tag processing instance | Y | N | N | N | N |
| Tag reservation instance | N | Y | Y | Y | N |
| Tag ticket instance | N | N | N | N | Y |
| Remove tags from processing instance | Y | N | N | N | N |
| Remove tags from reservation instance | N | Y | Y | Y | N |
| Remove tags from ticket instance | N | N | N | N | Y |
| Revalidate ticket | N | Y | N | Y | N |
| Send e-mail | Y | Y | Y | Y | Y |
| Send for external ticketing | N | Y | Y | Y | N |
| Set FOP | N | Y | N | Y | N |
| Stop processing by another schemes | N | Y | Y | Y | N |
| Transfer ownership | N | N | Y | Y | N |
| Void ticket | N | N | N | Y | N |
| Write customer account number | N | Y | N | Y | N |
| Write data to Mid-office | Y | Y | Y | Y | N |
| Write remark | N | Y | Y | Y | N |
Updating. deleting, create a draft of a scheme
Edit
Create Draft
etc…