Ssam Essay
Inbound SSIM Airline Activation Guide
© 2011, Sabre Inc. All rights reserved. This documentation is the confidential and proprietary intellectual property of Sabre Inc. Any unauthorized use, reproduction, preparation of derivative works, performance, or display of this document, or software represented by this document, without the express written permission of Sabre Inc. is strictly prohibited. Sabre and the Sabre logo design are trademarks and/or service marks of an affiliate of Sabre Inc. All other trademarks, service marks, and trade names are owned by their respective companies.
Table of Contents
1
Overview Purpose ..................................................................................................................................... …show more content…
1 Schedule Update Methods......................................................................................................... 1
2
Technical Specifications Format and Configuration .......................................................................................................... 5 Compression of SSIM ................................................................................................................ 5 File Naming Convention............................................................................................................. 5 Sabre Processing of SSIM ......................................................................................................... 6 Multiple Carriers ......................................................................................................................... 6
3
Testing and Activation SSIM Questionnaire ................................................................................................................... 7 Comparison Testing ................................................................................................................... 7 Carrier Acceptance Testing ....................................................................................................... 7 Activation ................................................................................................................................... 7
4
SSIM Questionnaire Carrier Questionnaire................................................................................................................. 8
iii
Overview
1
Purpose Inbound Schedule Information Messages (SSIM) is a product designed to give a carrier the ability to send Sabre an entire schedule file. The SSIM file is a copy of the airline’s entire schedule. The Inbound SSIM product will be used to generate the schedule updates similar to OAG updates and Adhoc Schedule Messages and Standard Schedules Messages (ASM/SSM) that update specific (but not all) flights. Inbound SSIM File formatting must adhere to Chapter 7 of the IATA Standard Schedules Information Manual. This document describes the requirements, configuration and testing to transmit Schedules Information Messages (SSIM) directly to Sabre to process as a schedule change update in the Sabre system. This document is not intended for carriers opting to transmit their SSIM to OAG.
Schedule Update Methods Once a carrier is activated for Inbound SSIM, schedule updates are accepted by Inbound SSIM sent by carrier or Manual Dynamic Schedule Updates (MDSU) performed by the carrier. MDSU updates must be included in the carrier’s next SSIM or the updates will be removed. Inbound SSIM carrier’s changes submitted to OAG will be ignored when the schedules in the OAG files are processed. Inbound SSIM carriers are not eligible to send Sabre Ad Hoc Schedule/Standard Schedule Messages (ASM/SSM). If a carrier requests to change their method of schedule delivery, the carrier should contact their Sabre Airline Distribution Account Director.
Inbound SSIM Airline Activation Guide
June, 2011 Confidential and Proprietary Sabre Inc.
1
Technical Specifications
2
Format and Configuration Inbound SSIM File formatting must adhere to Chapter 7 of the IATA Standard Schedules Information Manual. Carriers sending the file directly to Sabre must establish a new File Transfer Protocol (FTP) with Sabre for a SSIM file to be transmitted. This includes the IP address used to transmit the SSIM file to Sabre. The carrier must provide the SSIM source used to transmit their file to Sabre. Sabre accepts one SSIM source per carrier.
Compression of SSIM The file should be compressed and with TDAccess software. TDAccess is provided to the carrier at no charge. Compression adds encryption for increased security. Additionally, file compression reduces carrier transmission time to Sabre and reduces Sabre’s processing time; both resulting in the carrier’s schedules available for sale more promptly than an uncompressed SSIM.
File Naming Convention Inbound SSIM file sent directly to Sabre requires that one of the following naming conventions be followed: cc_ssim_yyyymmdd_hhmm.cmp (if your file is compressed) cc_ssim_yyyymmdd_hhmm.dat (if your file is uncompressed) where cc is the source of the transmission (carrier code) and yyyymmdd should be replaced with the year, month, day and hhmm should be replaced with the hour, minute
Inbound SSIM Airline Activation Guide
June, 2011 Confidential and Proprietary Sabre Inc.
2
Sabre Processing of SSIM A valid inbound SSIM file is loaded in the Sabre schedules database. The processed file is archived for redundancy. Until Sabre converts the SSIM to Sabre schedule records, the schedules in the SSIM are not in the Sabre schedules database. Once schedules are in the Sabre schedules database, they are available for sale.
Multiple Carriers The carrier sending the inbound SSIM may include other carrier’s schedules after the other carrier has authorized to Sabre the inclusion of its schedules in the inbound SSIM. The carrier to be included in the inbound SSIM should contact their Account Manager.
Inbound SSIM Airline Activation Guide
June, 2011 Confidential and Proprietary Sabre Inc.
3
Testing and Activation
3
SSIM Questionnaire After completing the SSIM Addendum, the carrier will need to complete the SSIM Carrier Questionnaire.
Refer to Section 4 for the SSIM Carrier Questionnaire.
Comparison Testing Sabre will initially test the carrier’s SSIM file by converting the file in two unique development schedule databases. This enables a side by side comparison of the file to ensure the file contains all necessary details in the SSIM are in Sabre. Once completed, the SSIM will be processed in the integration (test) environment. As a last test before production activation, the SSIM will be processed in the certification (CERT) environment.
Carrier Acceptance Testing Carriers may test and validate their schedules in both the integration and certification environments in Sabre.
Activation Upon successful completion of Sabre and the carrier’s testing, the activation of production SSIM file will be scheduled. As part of the activation, a time for processing of each SSIM sent by the carrier into the Sabre schedules database will be mutually agreed upon. Sabre reserves the right to modify the scheduled processing at any time.
Inbound SSIM Airline Activation Guide
June, 2011 Confidential and Proprietary Sabre Inc.
4
SSIM Questionnaire
4
Carrier Questionnaire
1. Who is the primary point of contact for Schedule Change? a. Name b. Phone Number c. Email 2. Who will be the primary contact for the testing? a. Name b. Phone Number c. Email 3. For TDAccess compression software , provide: a. Operating System b. Contact Name c. Company Name d. Physical Mailing Address e. Email Address f. Phone Number
4. What IP addresses will the file originate from? 5. What will be the Source of the SSIM file? (Carrier or Third Party)
Inbound SSIM Airline Activation Guide
June, 2011 Confidential and Proprietary Sabre Inc.
5
© 2011, Sabre Inc. All rights reserved. This documentation is the confidential and proprietary intellectual property of Sabre Inc. Any unauthorized use, reproduction, preparation of derivative works, performance, or display of this document, or software represented by this document, without the express written permission of Sabre Inc. is strictly prohibited. Sabre and the Sabre logo design are trademarks and/or service marks of an affiliate of Sabre Inc. All other trademarks, service marks, and trade names are owned by their respective companies.
Table of Contents
1
Overview Purpose ..................................................................................................................................... …show more content…
1 Schedule Update Methods......................................................................................................... 1
2
Technical Specifications Format and Configuration .......................................................................................................... 5 Compression of SSIM ................................................................................................................ 5 File Naming Convention............................................................................................................. 5 Sabre Processing of SSIM ......................................................................................................... 6 Multiple Carriers ......................................................................................................................... 6
3
Testing and Activation SSIM Questionnaire ................................................................................................................... 7 Comparison Testing ................................................................................................................... 7 Carrier Acceptance Testing ....................................................................................................... 7 Activation ................................................................................................................................... 7
4
SSIM Questionnaire Carrier Questionnaire................................................................................................................. 8
iii
Overview
1
Purpose Inbound Schedule Information Messages (SSIM) is a product designed to give a carrier the ability to send Sabre an entire schedule file. The SSIM file is a copy of the airline’s entire schedule. The Inbound SSIM product will be used to generate the schedule updates similar to OAG updates and Adhoc Schedule Messages and Standard Schedules Messages (ASM/SSM) that update specific (but not all) flights. Inbound SSIM File formatting must adhere to Chapter 7 of the IATA Standard Schedules Information Manual. This document describes the requirements, configuration and testing to transmit Schedules Information Messages (SSIM) directly to Sabre to process as a schedule change update in the Sabre system. This document is not intended for carriers opting to transmit their SSIM to OAG.
Schedule Update Methods Once a carrier is activated for Inbound SSIM, schedule updates are accepted by Inbound SSIM sent by carrier or Manual Dynamic Schedule Updates (MDSU) performed by the carrier. MDSU updates must be included in the carrier’s next SSIM or the updates will be removed. Inbound SSIM carrier’s changes submitted to OAG will be ignored when the schedules in the OAG files are processed. Inbound SSIM carriers are not eligible to send Sabre Ad Hoc Schedule/Standard Schedule Messages (ASM/SSM). If a carrier requests to change their method of schedule delivery, the carrier should contact their Sabre Airline Distribution Account Director.
Inbound SSIM Airline Activation Guide
June, 2011 Confidential and Proprietary Sabre Inc.
1
Technical Specifications
2
Format and Configuration Inbound SSIM File formatting must adhere to Chapter 7 of the IATA Standard Schedules Information Manual. Carriers sending the file directly to Sabre must establish a new File Transfer Protocol (FTP) with Sabre for a SSIM file to be transmitted. This includes the IP address used to transmit the SSIM file to Sabre. The carrier must provide the SSIM source used to transmit their file to Sabre. Sabre accepts one SSIM source per carrier.
Compression of SSIM The file should be compressed and with TDAccess software. TDAccess is provided to the carrier at no charge. Compression adds encryption for increased security. Additionally, file compression reduces carrier transmission time to Sabre and reduces Sabre’s processing time; both resulting in the carrier’s schedules available for sale more promptly than an uncompressed SSIM.
File Naming Convention Inbound SSIM file sent directly to Sabre requires that one of the following naming conventions be followed: cc_ssim_yyyymmdd_hhmm.cmp (if your file is compressed) cc_ssim_yyyymmdd_hhmm.dat (if your file is uncompressed) where cc is the source of the transmission (carrier code) and yyyymmdd should be replaced with the year, month, day and hhmm should be replaced with the hour, minute
Inbound SSIM Airline Activation Guide
June, 2011 Confidential and Proprietary Sabre Inc.
2
Sabre Processing of SSIM A valid inbound SSIM file is loaded in the Sabre schedules database. The processed file is archived for redundancy. Until Sabre converts the SSIM to Sabre schedule records, the schedules in the SSIM are not in the Sabre schedules database. Once schedules are in the Sabre schedules database, they are available for sale.
Multiple Carriers The carrier sending the inbound SSIM may include other carrier’s schedules after the other carrier has authorized to Sabre the inclusion of its schedules in the inbound SSIM. The carrier to be included in the inbound SSIM should contact their Account Manager.
Inbound SSIM Airline Activation Guide
June, 2011 Confidential and Proprietary Sabre Inc.
3
Testing and Activation
3
SSIM Questionnaire After completing the SSIM Addendum, the carrier will need to complete the SSIM Carrier Questionnaire.
Refer to Section 4 for the SSIM Carrier Questionnaire.
Comparison Testing Sabre will initially test the carrier’s SSIM file by converting the file in two unique development schedule databases. This enables a side by side comparison of the file to ensure the file contains all necessary details in the SSIM are in Sabre. Once completed, the SSIM will be processed in the integration (test) environment. As a last test before production activation, the SSIM will be processed in the certification (CERT) environment.
Carrier Acceptance Testing Carriers may test and validate their schedules in both the integration and certification environments in Sabre.
Activation Upon successful completion of Sabre and the carrier’s testing, the activation of production SSIM file will be scheduled. As part of the activation, a time for processing of each SSIM sent by the carrier into the Sabre schedules database will be mutually agreed upon. Sabre reserves the right to modify the scheduled processing at any time.
Inbound SSIM Airline Activation Guide
June, 2011 Confidential and Proprietary Sabre Inc.
4
SSIM Questionnaire
4
Carrier Questionnaire
1. Who is the primary point of contact for Schedule Change? a. Name b. Phone Number c. Email 2. Who will be the primary contact for the testing? a. Name b. Phone Number c. Email 3. For TDAccess compression software , provide: a. Operating System b. Contact Name c. Company Name d. Physical Mailing Address e. Email Address f. Phone Number
4. What IP addresses will the file originate from? 5. What will be the Source of the SSIM file? (Carrier or Third Party)
Inbound SSIM Airline Activation Guide
June, 2011 Confidential and Proprietary Sabre Inc.
5