Overview
Users Users have the option to integrate their Softrip system with a variety of GDS platforms. These types of integrations can vary from shopping air and land packages directly through the system, managing schedule changes with or without shopping, and the ability to import existing PNR’s into the reservation.
| Info |
|---|
...
Softrip has the ability to automate schedule changes within the Operations, however, the first step for any new user is to manage these schedule changes manually. |
Setting up Operations- Air Schedule Changes
The The below four steps are an overview of what is needed to set-up the schedule change queue in operations.
Access the Operations system
Select “Air Schedule Changes”
Fill in the schedule change filters
Set-up the Schedule Change Queue in Operations
| Info |
|---|
Note: Each GDS has different queues for schedule changes. Users will need to review their individual GDS to obtain the queue details. This is a necessary step in order to enter the correct information within Softrip. |
Defining the fields
Air Server
The The Air Server is the internal resource server that lays between Softrip and the GDS.
CRS
The The CRS correlates to the GDS that is being used by the company to pull the the data and flights from. Softrip will set-up the three letter code that correlates to the GDS that is being used.
Start Q
Enter Enter details for the GDS queue that contains unprocessed schedule changes.
| Panel |
|---|
...
| ||
Each GDS has their own queue convention. For example, schedule changes may always fall into queue 7 for Amadeus. |
Success Q
Once Once a schedule change is processed successfully, Softrip will move the PNR to the success queue.
| Panel | |
|---|---|
|
...
| |
Once schedule changes are processed successfully, users can access the success queue through the GDS to take the next appropriate business action. |
Failure Q
Based Based on the filters the user identified, schedule changes that cannot be procsesed will be placed on this GDS queue.
...
| Panel | ||
|---|---|---|
| ||
Once a schedule change fails based on the parameters set in Softrip, users will access this queue to determine the next appropriate business action such as reaching out to their customer regarding the update. |
Fail on Flight # Change
The The "fail on flight number change" is a "yes or no" prompt. Users should select the checkbox if a flight record should appear on the "failed" queue if the schedule change changes the flight number on the air record.
Flight # Change Carriers
The The "flight # change carriers" option allows users to identify specific airline carriers where a flight should fail if a flight number change occurs. By entering comma delimited airline codes into this field, the schedule change will only fail if a flight number changes on the carriers listed.
Fail on # Conn. Change
The The "fail on number of connections/connection change" option is a "yes or no" prompt. Users should select the checkbox if a schedule change should appear on the "failed" queue if a schedule change includes adding a connection city to a non-stop flight or if the number of connections change.
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Example 1: The flight initially was flying non-stop from JFK to ROM. The flight now connects in ATL. If "Y" is selected, this would fail. Example 2: The flight initially had a one stop connection: JFK to MIA to ROM. The schedule change now has a two stop connection: JFK to ORD to MIA to ROM. If "Y" is selected, this would fail. |
Fail on Max Time Diff
Enter Enter the numerical value in minutes of the time difference that a schedule change should fail on. This is set by the business.
| Panel | |
|---|---|
|
...
|
...
The flight initially departed at 9:30 AM and now the flight leaves at 12:00 PM. If the value entered in the "fail on max time difference" is equal to 120, then the above example would be considered a schedule change fail. |
Connection Check
If If selected, the application will run a GDS command to ensure the minimum legal connection times are met. The command is programmed by the GDS.
| Panel | |
|---|---|
|
...
|
...
Each airport has a unique minimum legal connection time that must be met. If this time is not met, the PNR will appear on the "fail" queue. |
Capture Only
Selecting Selecting capture only will update the Softrip bookings with the latest schedule.
| Info |
|---|
This option should be selected if all changes are manually processed by the users. Process Example Run queues |
Place on TKT Q
The place on ticketing queue option allows users to designate the number of days prior to departure that a PNR should appear again on the GDS ticketing queue in order to be ticketed again with the updated schedule.
This This only applies to accepted schedule changes that require a ticket to be re-issued.
...
| Panel | ||
|---|---|---|
| ||
When processing schedule changes, the business will determine the number of days prior to re-ticketing. This is done as buffer in the event more changes are done to the PNR. Entering the below formats allow users to set-up filters per airline. |
| Panel | ||
|---|---|---|
| ||
Format Examples 45 PNRS with schedule changes that were accepted will be placed on the ticketing queue 45 days before departure
45;20:AF,US PNRS with schedule changes that were accepted will be placed on the ticketing queue 45 days before departure. PNRS that are on AF or US carriers that have schedule changes that were accepted will be placed on the ticketing queue 20 days before departure.
45;20:AF,US;10:LH,B6
PNRS with schedule changes that were accepted will be placed on the ticketing queue 45 days before departure. PNRS that are on AF or US carriers that have schedule changes that were accepted will be placed on the ticketing queue 20 days before departure.
PNRS that are on LH or B6 carriers that have schedule changes that were accepted will be placed on the ticketing queue 10 days before departure. |
Min/Max Conn time
The The min/max time field is the acceptable minimum and maximum flight connection times.
| Panel | ||
|---|---|---|
| ||
Format Example: Enter 2/5 The system will place the PNR on the failed queue if the schedule change is anywhere outside two (2) to five (5) hours. Example: The original flight landed at 12:00 PM, departing at 5:00 PM. The schedule change is now departing at 6:00 PM. This would fail. |
Major/Minor Time
Enter Enter a number of minutes that determines whether a change in time is a minor change or a major change.
| Info |
|---|
|
...
Note: This does not control whether the GDS should accept or reject the schedule change. See Min/Max connection time. |
| Info |
|---|
Note: This is a business requirement and is not dictated by the GDS. |
Ref In
Always “N”
| Panel | ||
|---|---|---|
| ||
Where the booking number is located in the PNR. Example: Booking number appears next to the passenger names. This information stems from the GDS. |
Ref Key
The The reference key, typically an asterickasterisk. This is how a booking number is identified in a PNR.
...
Setting up the schedule change queue
The The schedule change queue is a feature that is included in the Air Operations set-up process.
Just Just like other resqueues, Softrip will set up the events/actions that will be associated to the queue itself under the booking rule EVT-SCHCHG. The customer will be responsible for customizing the e-mail communication within the queue settings.
The The queue is designed to send notifications to the customer on any schedule change that has been processed through Air Schedule Changes in Operations.