Requirements for maintenance of flight series, service loads, fares and classes for GO7 customers with W2 subhosting integration

In this article, you will find a list of simple configuration, which you need to follow to make sure that regular daily actions you take in such modules of aero CRS as Flight series, Service loads etc. do not result in the unintentional cancellation of your flights in GDS.
The schedules are imported to SMS5 (W2) and from there to GDS via SSIM file (schedule file,) which is generated by GO7 and then automatically uploaded to SMS5. If a schedule is not included to SSIM file of GO7 (whether on purpose or by mistake), then such a schedule get cancelled immediately in SMS5 and then in GDS, meaning that all PNRs in GDS also get cancelled (will get a cancellation message from our system). We identified that in the majority of the cases this is not the intention of our GO7 customers to cancel the schedules in GDS. Therefore, below we provide the scenarios which must be avoided in order not to remove your schedules from SSIM file by mistake:
1. Do not remove GDS distribution channel from flight series currently having GDS distribution ON.
image.png
Deactivating GDS distribution channel from a flight series, will remove it from the next SSIM file, therefore, it will be cancelled in SMS5 and in GDS, as well as all GDS reservations in this flight series will get cancelled. 
 
2. Do not replace your current service load with a new service load if it IATA identifier empty. AND never remove the IATA identifier from the service load used for flight series distributed in GDS.
image.png
Remember, that without IATA identifier SSIM record will not be generated (as aircrft type information is mandatory part of SSIM record), it means that the flight series will disappear from your next SSIM file and will be cancelled in SMS5 and in GDS, as well as all GDS reservations in this flight series will get cancelled. We strongly recommend that you add the IATA identofier all your existing service loads, and make it a part of your standard procedure of creating a new service load.
3. Do not remove mapping for GDS in class settings (Class code / W2 code)
image.png
If the mapping is removed from one of the classes (you may decide to stop selling in this class in GDS), nothing bad will happen yet. However, if in the specific flight series there will be no classes with GDS mapping at all (perhaps, you only sold in one class in GDS, and then you removed the mapping), then the flight series will be removed from the next SSIM file and will be cancelled in SMS5 and in GDS, and all GDS reservations in this flight series will get cancelled. Please remember that if you decide to introduce a new class for GDS distribution, you must enable mapping on it as well.
4. Do not deactivate GDS distribution on class level (do not mix with item 3 above). Remember that on  the flight series there should be at least one class which (i) has a mapping for GDS (see above) and (ii) is activated for GDS distribution.
image.png
If you do a change in the flight series, which may result in deactivation for GDS distribution of all classes in this flight series, then the flight series will be removed from the next SSIM file and will be cancelled in SMS5 and in GDS, and all GDS reservations in this flight series will get cancelled. Whenever you take an action "Update class" for a class distributed in GDS, make sure "Enable on GDS" option remains activated.
5. Do not remove GDS/LDS connection code from a destination which is used in one of your flight series activated for GDS distribution.
image.png
If the GDS/LDS connection code is removed from destination, then the flight series will be removed from the next SSIM file and will be cancelled in SMS5 and in GDS, and all GDS reservations in this flight series will get cancelled. Please also remember that this is also relevant for newly introduced routes for GDS distribution - you must check that the IATA code is in place in each destination used in the new flight series.  It is easy to check if the code is in place for all your destinations.
image.png
What if you indeed decided to close the flight series for distribution in GDS (W2) only, but you still keep it operational in GO7 and you do not want to have GDS PNRs cancelled?
In this case, before you deactivate distribution for GDS channel,  please reach Go7 support team and inform about specific flight series (route , flight number) you want to switch GDS distribution for. Our team will make necessary adjustments on our side to prevent cancellation of the flights, and will reconfirm to you. After receiving confirmation from our team, please go ahead and deactivate GDS distribution the regular way. The flight series will be removed from SSIM file, but due to extra configuration done it will not be cancelled on our side (the sales will be closed), and already existing PNRs will not be affected.
What if you really want to fully cancel a flight series in GO7, as you decided not to operate it?
In this case, just deactivate the flight series in the regular way. The flights series will be excluded from SSIM file, the schedules would get cancelled in SMS5 and in GDS, and GDS agents will get informed about the cancellation
As you are already aware, fare filing for GDS distribution is done outside of G07. However, fares defined in GO7 are used for issuing the internal ticket for a GDS (W2) reservation. Therefore, it is mandatory to make sure that for any class/route, distributed in GDS, there is at least one OW fare available for Worldticket travel agency (in your system the name can differ). During the initial set-up our consultants from GO7 Implementation team make sure that such fares would be properly assigned to the travel agency used for distribution. However, later at the operation stage, it is important that the team of your airline, while taking care of pricing adjustments, follows the few rules, relevant for the proper W2 distribution.
  1. Do not deactivate fare, corresponding to the class that is mapped with GDS class, if it is the only existing fare for GDS mapped class. If there is no active fare linked to class mapped with GDS and this fare is not available to Worldticket travel agency, all bookings will be rejected in GDS immediately after being created. At least one fare needs to be always activated for every class that is mapped with GDS class and available for Worldticket agency. If you really decide to stop W2 distribution on the route, please remember to deactivate GDS distribution on flight series level, then the flight will not be shown in GDS and the GDS agents will not be confused.
  2. Do not assign a brand to a fare, if there is no other fare for the same class/route. Brands are not supported for GDS distribution . If a brand is assigned, new bookings will be rejected in GDS immediately after being created. So it is mandatory to make sure, that there is a fare, not connected to a brand, available for Worldticket travel agency

Another action, which you should be careful with in order to exclude possible issues with GDS reservations is Booking transfer.

Do not perform “Booking transfer” action in relation to GDS bookings. New date / flight will be not reflected in GDS, and besides, in such case the booking transfer will also  stop any incoming messaging from GDS, for example in case when agent rebooks or cancels the booking afterwards. It will not be possible to fix such booking either . As the result, you may face a  situation that passengers comes to the airport according to his GDS ticket and not CRS booking.  It is supposed to be the GDS agent who originally issued the ticket, to reacommodate passenger - also in case of involuntary rebooking (flight cancelled).

If you have any doubts about requirements, defined in the article, we kindly ask you to contact GO7 implementation team.

Have more questions? Submit a request

Comments

Powered by Zendesk