Tech News
Password policy update / MixVel distribution system
Dear colleagues,Please note that from May 22, 2024 an updated password policy for operator authorization on the MixVel distribution system using MixVel terminal emulator will be introduced and the new password policy will be gradually applied to operators.
Updates:
− Password complexity is increased;
− Number of failed login attempts is reduced from 6 to 3;
− Inactive operator ID are blocked after 45 days.
For updated MixVel distribution system password policy please visit the Manuals and Information Security sections on the Sirena-Travel web-site.
Kindly be aware of the above changes.
Kind regards,
Sirena-TravelPassword policy update / System "Statistics"
Dear colleagues,
Please be advised that reset of all current passwords in the System "Statistics" is scheduled on May 22, 2024 due to password policy update. When a user logs in to the application after the password reset the application will request to change the password.
For updated password requirements please visit the System "Statistics" password change page.
Kindly note the above-mentioned changes.
Kind regards,
Sirena-TravelNot Valid Before \ Not Valid After filing procedure update
Dear colleagues,
Please be advised that starting from June 03, 2024 a software development of Not Valid Before \ Not Valid After completion algorithm update when issuing a ticket in compliance with IATA PSCRM Res. 722 TICKET - GENERAL PROCEDURES AND DEFINITIONS, chapter 6 и 7 will be implemented on MXV production system.
6. NOT VALID BEFORE
When applicable, the earliest return date (day and month) shall be reflected for each flight coupon. Exception: Where tariff rules prohibit voluntary reservation changes, or where such changes are only permissible against additional payment, the date to be reflected shall be the same as the reservation date reflected on the same coupon.
7. NOT VALID AFTER
When a ticket has a normal one-year validity and is not issued in conjunction or in exchange for another ticket, no date is required. In all other cases, the expiry date (day and month) shall be used.
Exception 1: Where tariff rules prohibit voluntary reservation changes, or where such changes are only permissible against additional payment, the date to be reflected shall be the same as the reservation date reflected on the same coupon.
Exception 2: When a ticket is reissued under the provisions of Resolution 735d, the original NVA date may be used or it may be left blank.
If upon filing the airline specifies minimum and maximum stay restriction reflecting the ticket validity, but Cat 16 permits or prohibits chargeable or free of charge change, then the following procedures for Not Valid Before\ Not Valid After field completion will apply:
Where tariff rules prohibit ticket changes, or where such changes are only permissible against additional payment according to Cat 16 enter the flight dates in NVB/NVA fields. For other fares – complete as per Cat 6/7 fare application data or leave blank (fields are left blank in case of absence of Cat 6/7 data).
If Cat 16 is not completed or not formalized then the parameters reflecting ticket validity depending on tariff type code (system reference data) will be analyzed.
Not reflected/ P=Permited - NVB/NVA to be completed as per Cat 6/7.
Reflected /R=Required - NVB/NVA are reflected by the flight dates of the corresponding coupons.
Blank/ N=Not Permited - NVB/NVA fields are left blank.
Kindly note the above-mentioned changes and update the filing parameters accordingly.
Kind regards,
Sirena-Travel
Sirena-Travel GDS update in terms of filling out Netting in RET(IATA) IT0N file record
Dear colleagues,
Please be advised that on May 23, 2023 the production software of MXL will be updated in terms of filling out the fields containing Netting-transaction information (residual amounts of original ticket used for payment for a new ticket) in the version 22 and 23 of RET(IATA) IT0N file record.
After updating the original ticket amounts used for payment for fares, taxes and miscellaneous fees for a new ticket will be specified in the IT0N record as follows:
Example:N000002RUB0RTR 00000001790RM6 00000000269CWJ 00000000458CWH 00000000352CWI 00000000937CB8 00000000312 00000000000 00000000000 00000000000 00000000000
Description of the fields in detail below:
Currency used is RUB0
"TR" =1790 is the residual tax amount of the original ticket
"M6" =269 is the residual tax amount of the original ticket
Used in payment for:
"WJ"=458 tax of the new ticket
"WH"=352 tax of the new ticket
"WI"=937 tax of the new ticket
"B8"=312 tax of the new ticket
RET format also provides opportunity to show the residual amount of fare/tax/fee not used for payment for a new ticket – U code.
Please refer to SP Data Interchange Specifications Handbook version 23 for full description of the format.URGENT! Change of Minimum Connect Time information filing procedure
Dear colleagues!
Due to the decision made by Cirium to stop transmission of Minimum Connecting Time (hereinafter MCT) change data files to Sirena-Travel GDS you are kindly requested to send completed MCT Template (Attachment 1) toossr@sirena-travel.ru in order to ensure prompt information update.
Terminal version update - 1.73b (Rev.3)
Dear colleagues,A new version of the terminal - 1.73b (Rev3) has been installed in Sirena-Travel GDS.It includes the following changes in the Railway Transportation application:1. For passengers under 14 years of age who have Russian citizenship, and the identity document belongs to another country, it became possible to select Russia in the “Citizenship†field.2. To reduce situations when the passenger's personal data is filled in incorrectly, an additional notification has been added for the operator if the "patronymic" field of the passenger is not filled.
Sincerely,Sirena-Travel.Updated protocol for working with XML gateway (Version 0.190)
Changes have been made to the protocol for working with the XML gateway (Version 0.190 dated 20.12.2021) of Sirena-Travel GDS. The main changes concern the response to a request when creating and viewing a booking (booking and order):
- the description of the parameters of the additional services booked has been added;
- the description of the parameters of the executed documents has been added;
- Added description of getting information about the place and session of PNR creation.
To access the XML documentation, you need to fill out an application in the POPs system.
New terminal version 1.72b (Rev.4)
The new version of the terminal 1.72b (Rev.4) has been installed in Sirena-Travel GDS, in which the software modifications are implemented in the graphical application "Railroad transportation".
List of improvements:- added schemes of wagons of the "Strizh" train
- added an additional feature for the train and carriage - automatic transmission - the train is equipped with an automatic passenger boarding control system. When issuing electronic tickets for such trains, the refund operation is possible until the train leaves the passenger's boarding station.
Using the originally issued ticket as a voucher to pay for future transportation
In accordance with the recommendations of the International Air Transport Association (IATA) contained in the Information for Airlines ( Customer vouchers) version No. 1 dated March 28, 2020, the ticket originally issued to the passenger can be used as a voucher to pay for future transportation.
This technology allows airlines not to make a refund to the payer at the moment, but to use the originally issued ticket as a voucher for future traffic.
The functionality of Sirena-Travel GDS allows the airline to formulate a clear and flexible commercial policy regarding the use of the originally issued ticket as a voucher in its own sales offices and travel agents.
In order to implement the technology of using the originally issued ticket as a voucher for paying for future flights in accordance with standard procedures in the Sirena-Travel GDS, airlines need to include the following key points in their own commercial policies and rules for booking and selling:- Unused amount for an originally issued unused or partially used ticket is accepted as payment for a new ticket. Revalidation operations (changes in the originally issued ticket), or exchange without surcharge, exchange with surcharge or part-exchanges.
- The ability to change the status of the originally issued unused or partially used ticket, which will be used as a voucher for future transportation, in order to be able to select the originally issued tickets as vouchers for accounting systems. Transfer of coupon statuses on an originally issued ticket to U (Unavailable) status with subsequent status change when exchanging a ticket for E (Exchange) status. For TCH tickets is a mandatory requirement.
- The period during which the originally issued ticket can be accepted for exchange (for a fully or partially unused ticket). In the event of a forced change in the conditions of transportation, an originally issued ticket can be set to any period (for example, 1 year or more). At the same time, the carrier may establish that the expiration dates of the originally issued ticket are rejected. In case of voluntary changes in the conditions of transportation, the period may not be more than 1 year from the date of issuance of the originally issued ticket
- The dates of transportation and the route of the new ticket is not limited by the conditions of the originally issued ticket.
- A new ticket can be issued according to the tariffs and for categories of passengers differing from the tariffs and passenger category applied in the originally issued ticket.
- The form of payment for the new ticket should contain information about the form of payment for the originally issued ticket. It is especially important for payments by bank cards. For TCH tickets it is a mandatory requirement.
- A new route must be booked in the original PNR.
- An initially issued ticket can be accepted in exchange for a new ticket for flights of another carrier - an interline partner, while saving the settlement code in a new ticket.
- An initially issued ticket can be returned after the expiration of a new term set by the carrier, a refund operation and using a manual mask.
- The possibility of using SSR elements to inform the airline, of its own or agent sale, that this PNR and ticket will be used for registration of future flights indicating the expiration date established by the carrier. The presence of an SSR element will allow the use of this information for accounting systems.For TCH tickets it is a mandatory requirement.
- Possibility of exchanging a neutral ticket for an Airline ticket in Airline session. This opportunity is determined by the carrier whose settlement code is indicated in the originally issued ticket.
- If there is an EMD issued for additional carrier services to the originally issued ticket. The new expiration date of the ticket set by the carrier applies to EMDs issued for the ticket. At the same time (when exchanging a ticket), a new EMD will be issued through the EMD refund operation against the amount of the originally issued EMD.
