A Guide to Data Migrations for Customers and Local Markets.

Transcription

1 A Guide to Data Migrations for Customers and Local Markets. Travelport Data Migration Guide v1.00 Page: 1

2 Introduction This document is provided by the Data Migration Team and is intended to give a clear understanding of exactly what is involved when a migration takes place. If there are any questions regarding a Data Migration you can contact this department at data.migrations@travelport.com Data Migration Process Step 1 The agency request a date for migration ensuring there is minimum of seven days notification. Then they fully complete a release form and submit it to their Local Market Coordinator. Step 2 The Local Market Coordinator will check the release form to ensure all information is completed correctly. Step 3 Once checked the agency will then the form direct to the former GDS and to the Travelport Data Migration Department providing a minimum of 7 days notice. Note: If there are any issues with the form the former GDS will send it back to you rejected and you will have to resubmit the form requesting a capture date at least 7 days in advance. Step 4 The Local Market Coordinator will need to ensure that all the necessary procedures are followed in order for the migration to run smoothly. Step 5 The data will be captured by the former GDS at the time specified. Step 6 The releasing GDS will send the data to the receiving GDS in order for the data to be migrated. Travelport Data Migration Guide v1.00 Page: 2

3 Data Migration The Process Requesting Date of Migration The agreement Travelport has with the other GDSs is that they will only capture data during 0800 and 1700 Eastern US Time. If there is a requirement to capture data outside of these hours then this will have to be negotiated and agreed in advance with the GDS concerned. Completing the Release Form In order for the former GDS to release confidential customer information and bookings, they require a receipt for the submitted release form. The standard release form is designed for our typical migrations from one agency to another. It is recognised that there may be a requirement to migrate bookings from more than one site and/or into more than one agency. If this is the case then one form per pseudo is required. Travelport Data Migration Guide v1.00 Page: 3

4 Roles & Responsibilities Data Migration Department All data migrations to and from Travelport are coordinated and scheduled through the Data Migration Department. The Migration Team is responsible for: Coordinating and managing the relationship with the former GDS with respect to their capture of data. Scheduling capture requests in and out of Travelport. Note: The department is not responsible for direct communication with the agency. This is the local market s responsibility Agency Migration Coordinator The agency should appoint a migration coordinator to liaise with throughout the migration process. They will be responsible for: Completing the required Release Form and ensuring that all relevant fields are fully and accurately completed. Note: Should any vital information be missing or incorrect the form will be rejected and returned to the agency for rectification. Ensuring that the PNRs to be migrated are placed on the designated queue(s) prior to the agreed capture time stated on the release form. Note: If an account releasing PNRs needs technical assistance placing PNRs on queue (beyond what is already provided in this document), they must contact the appropriate Help Desk of the GDS where the PNRs currently reside. The staff at Data.Migrations@Travelport.com cannot provide technical assistance with aggregating PNRs. Travelport Data Migration Guide v1.00 Page: 4

5 Getting Started Inbound Migrations Amadeus to Travelport Preparations Required Before Conversions Here are some items which are required before a conversion can take place: Submit a release form Place All PNRs on queue Check for an IATA change Submit Release Form A release letter needs to be submitted so the conversion team can access your data. The release form needs to be completed and ed to the address listed on the top of the form. Place All PNRs on Queue All PNRs to be converted must be placed on a specific queue. Be sure the queue is not a system queue. Amadeus has a queue placement command called 'Search One'. The Q-roll command is an overnight request. 1. Sine-in with a manager Sine 2. In Amadeus, find an empty, unused, non-system queue. 3. Make sure the queue is activated, type QC/99 a. response: Queue not Activated, type QA/99C1 b. response: displays queue count then the queue is active 4. Type : LMB-ALL/99C1 The above command will place All air and non-air PNRs on queue 99 category 1. It is very important to verify that the destination queue is activated Amadeus Queue Roll (Search One) Restrictions and Important Notes It is the agency's responsibility to have the PNRs on queue by the capture time stated on the release letter. It is up to the account to verify both Air and NON-Air fall on queue. The Amadeus Search One is an overnight request (Batch). Your account is not charged for a Batch request. The destination queue must be activated Sine-in using a manager sine On your Amadeus Set, Type the Following Commands LMB-ALL/Q99C1 LMB-ALL/Q<queue number>c<category number> This command will place all Air and NON-Air PNRs on queue 99 category 1. The category is optional and will default to category 0 if omitted. Example: LMB-ALL/Q99 Travelport Data Migration Guide v1.00 Page: 5

6 The destination queue must be activated. To test if a queue is activated, type QC/99. To activate a queue, type QA/99C1. To add categories, type QAC/99/C1-6. To check all queues, type QT. Check for an IATA Change Electronic ticketing data does not transfer in the circumstance of an IATA change. We recommend ticketing these PNRs immediately or issuing paper tickets for itineraries that will take place after the conversion date. Sabre to Travelport Preparations Required Before Conversions Here are some items which are required before a conversion can take place. Submit a release form Place All PNRs on queue Check for an IATA change Submit Release Form A release form must be submitted so the conversion team can get access to your data. Contact the Conversion Project Planner or Conversion Programmer for the required capture dates. The release form must be completed and ed to both addresses listed on the top of the form. Place All PNRs on Queue All PNRs need to be placed on a specific queue. Make sure the queue is not a Sabre System queue. Read the instructions below on how to use the Sabre queue placement command called 'Spectra'. 1. In Sabre, find an empty unused queue. Not a system queue. 2. type : QK#ALL 3. hold and release: CONTROL+U 4. type: QJ/99 Check for an IATA Change Electronic ticketing data does not transfer in the circumstance of an IATA change. We recommend ticketing these PNRs immediately or issuing paper tickets for itineraries to be traveled after the conversion date. Tracking Data During Migrations from Competing GDS to Travelport Once PNRs are on queue, you are responsible for tracking all new PNRs created in competing GDS after that queue placement, as well as for any changes to those PNRs that were part of the queue placement. Once the data is captured from the queue by competing GDS, this data reflects only what was on the queue at the time of placement. During the week of conversion, your Onsite Support will train the agency in updating the converted/migrated PNRs and the manual conversion of any new PNRs created after the capture. Making Changes to Existing PNRs As the conversion team converts your data, you may view and make changes to existing PNRs in your old GDS. Make note of any changed PNR. If the PNR has been converted, it is possible the PNR may redirect its messages and ownership back to your old GDS. If Worldspan is installed, then use Worldspan to make the changes. How to Track Data Changes Hard Copy: Print any changed or newly created PNRs Travelport Data Migration Guide v1.00 Page: 6

7 Queue PNRs: Place any changed or newly created PNRs on a non-system queue. Update the PNRs After Conversion During the week of conversion, your Onsite Support will train the agency in updating the converted PNRs and the manual conversion of any new PNRs created after the capture by competing GDS. Worldspan Queues Utilized by the Conversion Team Queue 93:- The Conversion Team is utilizing Queue 93 for converted PNRs. All converted PNRs will be located in Queue 93 and its categories. Specific date ranges and category labels are applied. So please do not activate this queue. Your Conversion Programmer will activate Queue 93 and its categories during the conversion process. Queue 93 Queue 93 is set up to provide the account with a central location for processing un-ticketed, qfollow, and schedule problems. This queue is set up with six different categories. Category 0 schedule problem PNRs. Category 1 PNRs with queue follow-up brought over. (old remarks are found in 5.Q) Category 2 initially the count of all converted PNRs (the number should match the total of cat 4 & 5) Category 3 PNRs with T*DEF ticketing (mainly used for International conversions) Category 4 un-ticketed PNRs Category 5 ticketed PNRs. Queue 98:- The Conversion Team is utilizing Queue 98 to maintain World Files. Queue98 is used for quality controlling World Files. The Quality Control program can only be run by a Conversion Programmer. During upload, profiles are sent to the World File Queue 98 Category 1 for quality control processing. It is the account's responsibility to work Queue 98 and correct errors found within each profile. Travelport Data Migration Guide v1.00 Page: 7

8 Booking file queues in Galileo To assist the agency post migration, the Booking Files are placed on the following queues: QUEUE NO TITLE EXPLANATION 90 Waitlist Queue PNRs with waitlisted segments will be placed on this queue. 91 Schedule Changes Those PNRs whose flight times have been changed since they were booked in the former GDS but where this schedule change has not been actioned by the agency. The carrier reservation system will have changed the status of the segment to one of the following: Amadeus: SC Sabre: SC Worldspan: MS or SC These statuses will be converted to either TK, WK or HK. If the new flight schedule is not available in the Galileo GDS core then the segment will be entered as a TUR (tour) segment and the agency will need to review each of these individually. 92 Unticketed Unticketed PNRs (T:TAU/) move into this queue. 93 Train PNRs with Train segments are placed on this queue. 94 Miscellaneous PNRs that, during upload receive the following responses from Galileo: Check date/time continuity segment. Listed segment is followed by confirmed segment#. Check continuity segment#. Such PNRs are built in Galileo but moved to this queue for information. 95 Date Beyond Segments PNRs containing Date Beyond segments are placed on this queue (see earlier) 96 Open Segments with No Date PNRs containing Open with No Date TUR segments will be placed on this queue. 99 Cars and Hotels and Ticketed PNRs having Hotel and Car segments are placed on this queue as are all ticketing bookings. Travelport Data Migration Guide v1.00 Page: 8

9 Resolving Post Migration/Conversion Problems When you have problems with converted PNRs, review the information provided below to solve your problems. If you still need help, contact a Conversion Programmer. The conversion teams may be able to help, but we need examples. Collect as many examples as you can. Items like: The old CRS record locators Passenger names Travel date Missing segments Past date segments are not converted to Worldspan. Missing PNRs If you are missing any PNRs, first check the following before contacting a conversion programmer: Try looking for your PNR at the branch office. For PNRs with multiple passengers, try looking for the PNR by another passenger name listed in the PNR. The airline may have split the passengers into two PNRs. Remember, no past date or retention PNRs are converted, so verify the travel data. Check the creation/modification date on your old CRS PNR. If the PNRs was not on queue before the data capture took place, then the PNR will not be in Worldspan. Still can't find the PNR? Call your conversion Programmer! Or data.migrations@travelport.com Be sure you have the following information available: The old GDS record locator Passengers name(s) Travel date. Travelport Data Migration Guide v1.00 Page: 9