Interline Electronic Ticketing-CZOA GBR20071105.doc

Interline Electronic TicketingGeneral Business RequirementsBetweenChina Southern Airlines Andxx AirwaysVersion: 1.0TABLE OF CONTENTSGeneral Information31.Eligibility41.1Flight Eligibility (S.S.I.M)41.2Itinerary Eligibility41.2.1Open Segments41.2.2Conjunctive Itinerary41.2.3Group Bookings/Itinerary51.3Passenger Type Code51.4Tax field51.5 Reservation Status Code (PNR)51.6Revalidation52.Ticket Issuance62.1Ticket Sales Outside 72 Hours of Departure62.2Ticket Sales Inside 72 Hours of Departure62.3Codeshare72.4Form of Payment73.Ticket Void/Cancel84.PNR Changes85.Check-in Process105.1Coupon Control105.2EDIFACT Through Check-in (ITCI)105.3Boarding Passes105.4Self-Service Devices (Kiosk/Virtual Check In)106.1Third Party Ground Handling116.2PNL/ADL/ETL/PRL processing117.Refund Processing118.Exchange/Re-issue Processing119.Direct Print1210.Print Exchange1211.Baggage1312.Irregular Operations1312.1General Requirements1312.2Rerouting1312.3Involuntary Indicator1312.4Involuntary rerouting1312.5Endorsement of an Etkt1412.6FIM (Flight Interruption Manifest)1413.Flight Emergency1414.Receipts/Itineraries1415.Legal Documents/Notices1516.Fraud Prevention1516.1Present Credit Card Indicator1516.2Suspend1516.3Fraud Prevention Contacts1517.Data Security1617.1Surfing Tracking and Prevention1617.2Tickets Display/Control Request1617.3Ticket Data Masking1618.Data Retention1619.Backup Procedures1719.1Ticket Not Found1719.2Help Desks1720.Revenue and Interline Accounting1720.1 Change of Status (CoS) message1720.2 Sending back Control on unused coupons1820.3 Settlement Authorization Code1820.4Interline settlement1821.Interline Contracts (Agreements)1821.1Notification of Technology Changes1822.Messages1922.1Message Versions1922.2Ticket Display Criteria1922.3Ticket Display Response1922.4Mixed response1922.5Automated Name Correction2022.6Reservation Change Advisory Message2022.7Unsolicited Airport Control (UAC)2022.8History Display2022.9Redirected Airport Control2122.10Link Down/Timeout/Retry2122.11GDS implementations2122.12Passive Segments and GDSs2123.Form of Identification (FOID)2124.Miscellaneous22General InformationPurposeThe purpose of this document is to summarize the general business requirements for bi-lateral Interline Electronic Ticketing.This document does not address development, procedures or processing unique to each individual carriers in-house processing.This document is divided into sections based on the different business processes that can be affected by the Electronic Ticketing product. It contains the agreed upon resolutions and outstanding issues associated with each process.Project ScopeThe scope of this project is to facilitate of Electronic Ticketing within the scope of the Interline Agreement between CHINA SOUTHERN Airlines and xxxAirlinesAssumptio Resources are available Follow industry standardsDependencies EDIFACT messaging Communications Links Interline Bi-lateral agreement Completion of successful integration testing (programmer to programmer) Completion of successful customer testing (airline to airline)Constraints Resources Timeline1. Eligibility1.1Flight Eligibility (S.S.I.M)CZRequirement:A. If an itinerary contains one or more ineligible flights, the transaction will result in a paper ticket sale.B. CZ will send the ETKT eligibility indicator following the S.S.I.M format/process via CZs normal schedule filing process. This indicates the flight number(s) eligible for ETKTC. CZ expects OA to provide the Electronic Ticketing Eligibility indicator via S.S.I.M. Format./process to indicate ETKT Eligible flightsIssues:Final Resolution:1.2Itinerary EligibilityCZRequirement:A. CZ will not issue an electronic ticket for any itinerary that contains a segment not operated by air service. (e.g. Bus or Rail services sold via flight number are not eligible for electronic ticketing.) CZ will only issue Electronic ticket if all air segments have ETKT eligibility indicator and the carrier which CZ has interline traffic agreement and interline Electronic Ticketing agreement with.B. ETKT for ID is supportedC. ETKT for award (redemption) is supported. Issues:Final Resolution:1.2.1Open SegmentsCZRequirement:A. CZ as the validating carrier does not permit the sale of electronic tickets on an interline itinerary with OPEN segments. All segments for all interline flights must have booked.B. Sale of CZ OPEN segments is permitted of CZ validating eTickets , but the first segment must be confirmed.Issues: Final Resolution:1.2.2Conjunctive ItineraryCZRequirement:A. CZ can accept conjunctive tickets from an OA validating carrier that contains up to 16 coupons.B. CZ can issue conjunctive tickets up to 16 coupons.Issues: Final Resolution:1.2.3Group Bookings/ItineraryCZRequirement:A. CZ allows the issuance of electronic tickets for groups.B. If the group size is too large in one PNR, will split PNR before ticket issuance.C. CZ requires that each ticket has a specific passenger name；D. CZ as Operating Carrier , cannot accept eTickets with only a group nameE. Each member of the group must have their own eTicket.F. CZ can send the UAC by individual passenger. CZ prefers to receive the UAC for the individual passenger.Issues:Final Resolution:1.3Passenger Type CodeCZRequirement: All passenger type codes are eligible for ETKT issuance except CBBG (cabin baggage), COUR (courier), DIPL (diplomat).Issues: Final Resolution:1.4Tax field CZRequirement:CZ sends/receives 3 taxes in EDIFACT messages (TXD). If more than 3 taxes, the additional taxes are rolled up into an XT tax.Issues: Final Resolution:1.5 Reservation Status Code (PNR)CZRequirement:A. CZ allows ticketing against the following status codes: Confirmed KK/HK/RR/KL - Ticket Status =OK Waitlist HN/HL - Ticket status = RQB. Ticketing is not allowed against UC/UU/UN/HX/NO status codesIssues: Final Resolution:1.6Revalidation CZRequirement:A. CZ does not support the Revalidation Message.B. CZ as the validating carrier can revalidate e-tickets including OA coupons. CZ will obtain all coupon control prior to revalidation.C. CZ will not revalidate OA validated e-tickets.Issues: Final Resolution:2. Ticket Issuance2.1Ticket Sales Outside 72 Hours of DepartureCZRequirement:A. SSRTKNE: CZ, as the validating carrier, will send an SSRTKNE via teletype to the marketing carrier PNR notifying when an electronic ticket is issued for ticket sale. It is the marketing carriers responsibility to then pass the SSRTKNE on to the operating carrier.B. SSRTNKE: CZ does expect to receive a SSRTKNE when the ticket sale is outside of 72 hours.C. UAC: CZ has the ability to send the UAC. CZ would like to receive the UAC for tickets issued outside 72 hours.D. CZ prefer OA to send UAC immediately when ticket is issued.E. CZ sends the UAC to the operating carrier. If the UAC message is “rejected” by the operating carrier, then CZ will keep the coupon OPEN in the CZ database. The operating carrier will be required to request control of coupon(s) when needed. F. If the operating carrier does not respond to the UAC, CZ(validating carrier) will leave the coupon status code as OA Control, even if it doesnt exist in the operating carrier database. Airport Control will be granted if the same operating carrier requests control via the RAC.G. CZ will resend the UAC three times when operating carrier does not respond to the UAC.Issues: Final Resolution: 2.2Ticket Sales Inside 72 Hours of DepartureCZRequirement:A. The validating carrier will send an SSR TKNE via teletype to the marketing/operating carrier PNR notifying when an electronic ticket is used for ticket sales for inside 72 hours.B. CZ will send an UAC message with the coupons that depart within 72 hours. All other coupons on the ticket(s) will be sent as information.C. CZ prefers OA to send UAC immediately when ticket is issued.D. If unsolicited airport control message is “rejected” by the marketing/operating carrier, then the operating carrier will be required to request control of coupon(s) when needed.E. If the marketing/operating carrier does not respond to the UAC, the validating carrier will leave the coupon status code as “airport control” even if it doesnt exist in the marketing/operating carrier database. F. The validating carrier will not send a UAC message for OA marketed which VC operated.G. CZ will resend the UAC three times when operating carrier does not respond to the UAC.Issues: Final Resolution:2.3CodeshareCZRequirement:A. CZ recognises a code-share partner as a carrier established in its own right, that does not use the CZ airline designator nor the 784 accounting code.B. Where an itinerary has one or more code-share sectors, CZ as Validating Carrier will only issue an eTicket where CZ has an Interline eTicketing agreement with both the Operating and Marketing Carriers. Issues: Final Resolution:2.4Form of PaymentCZRequirement:A. CZ issues ET using maximum up to 2 FOPs. B. CZ will accept and store multiple forms of payment if they are received in an EDIFACT message.C. CZ will return multiple forms of payment if they are stored in CZ . Issues: Final Resolution:3. Ticket Void/CancelGeneral RequirementsCZRequirement:A. Only the validating carrier can void the ticket if all the coupons are OPEN for USE and the validating carrier has control. If the ticket is already reported to airlines accounting, it cannot be voided.B. System cancel is not permitted in the interline process, system cancel is unique to CRS.C. CZ does not have a “cancel” ticket sale, once the ticket is sold the only way to “undo” is to void the sale.Issues: Final Resolution:4. PNR ChangesGeneral RequirementsCZRequirement:A. CZ will not automatically regenerate a TKNE when cancel or rebook the interline segments.B. CZ expects OA to send SSR TKNE at the time of rebooking CZ segments.C. SSR “TKNE” shall only be used for notification that an electronic ticket has been issued. D. In the interline situation, those carriers in the itinerary including the validating carrier must be notified that a ticket has been issued electronically. This notification must be sent at time of Electronic Ticket issuance or reissue, and will take the form of an SSR advisory: (a) the SSR message shall be sent to all carriers in the itinerary including the validating carrier as bilaterally agreed; (b) the SSR advisory is sent via teletype by the system issuing the electronic ticket; (c) an SSR element must be generated for each electronically ticketed passenger for each segment ticketed. If more than one passenger is ticketed from the same PNR, in the same transaction, multiple passenger SSRs will be contained in the same message; (d) the SSR advisory is sent immediately upon successful completion of the electronic ticket issuance; (e) the SSR code is TKNE; (f) the SSR status code and number is HK1; (g) an SSR TKNE is not sent on OPEN segments; (h) an SSR TKNE is transmitted for Passive Segment(s); (i) an SSR TKNE is sent for Infant tickets not occupying a seat, using the associated adult name. Precede the infant ticket number with the code INF; Example: SSR TKNE DL HK1ATLZRH0066Y01SEP-1KESSLER/PMRS.INF006123456789C1 (j) Non consecutive Electronic Ticket numbers (or where the Electronic Ticket number series differ) shall be located in a separate TKNE element. Consecutive Electronic Ticket numbers contained in a single SSR TKNE element. Follow the coupon data with an oblique, and include the last 3 digits of the first ticket number, a dash (-) delimiter and the last 3 digits of the last ticket number. (k) an SSR TKNE ticket number shall be followed immediately by the coupon delimiter “C” followed by one digit indicating the actual coupon number; (l) the SSR TKNE shall not contain check digit. Proposed format, conjuncted ticket set with multiple segments on one carrier (with clarification): SSR TKNE NW HK1MSPORD0122Y22AUG-1MACKIN/L.0054922111221C3/220-222 SSR TKNE NW HK1ORDNRT0068Y23AUG-1MACKIN/L.0054922111221C4/220-222 SSR TKNE NW HK1NRTMSP0067Y30AUG-1MACKIN/L.0054922111221C1/220-222Issues: Final Resolution:5. Check-in Process5.1Coupon ControlCZRequirement:A. CZ can manually push the control to OA. CZ expects OA to initiate the airport control request when required. B. When has an irregular operation, CZ can manual push the control to OA.C. CZ, as operating carrier, will not send Change Of Status message for interim status i.e. CHECKED-IN.Issues:Final Resolution:5.2EDIFACT Through Check-in (ITCI)CZRequirement:A. Through check-in processes handle electronically ticketed passengers.B. CZ requires all the boarding passes, including those for the segments not used yet, to be printed out at the departure airport.C. The status of the coupon on the next segments other than the first one will be changed into “Flown” only when each time each segment is used, in another word, when the passenger is really flown.Issues: Final Resolution: 5.3Boarding PassesCZRequirement:A. CZ will pirnt the boarding pass for an OA flight. B. CZ Will print ET on boarding pass, but will not use any ATB stock for boarding passes.Issues: Final Resolution: 5.4Self-Service Devices (Kiosk/Virtual Check In)CZRequirement:Is in development.CZ can use Kiosk in PEK,CAN, URC, DLC, SHE, HRB, SIA, ZUH airport for domestic flight.CZ cant support to handle Through Check-in or international flight Check-in by Kiosk.Issues: Final Resolution:5.5Internet Check inCZRequirement:CZ can use internet to handle Check-in for domestic flight.CZ cant support to handle Through Check-in or international flight Check-in by internet.Issues: Final Resolution:6. Ground Handling6.1Third Party Ground HandlingCZRequirement:CZ can use Third Part Ground Handling in CDG airport.Issues: Final Resolution:6.2PNL/ADL/ETL/PRL processingCZRequirement:Not supportedIssues: Final Resolution:7. Refund ProcessingGeneral RequirementsCZRequirement:A. CZ will reject any Change of Status Refund (R) message from an OA for a coupon where CZ is the Validating Carrier.B. CZ will not refund eTickets where OA is the Validating Carrier.Issues:Final Resolution:8. Exchange/Re-issue ProcessingGeneral RequirementsCZRequirement:A. CZ will process exchanges of OA validated coupons by first systematically obtaining (airport) control of the coupon(s). Validating carrier will determine if control is released.B. Each validating carrier will accept the change of status message to change the coupon to EXCHANGEDC. CZ can support reissue to exchange electronic to electronic (E to E) 、Electronic to paper (E to P) and paper to electronic (P to E).D. CZ can do a partial or whole e-ticket exchange. E. CZ can exchange up to4 ticket documents on an exchange including the multiple document numbers that make up a conjunctive e-ticket. F. CZ will not automatically regenerate a TKNE for cancelled or rebooked PNR segments where an e-ticket has been issued, unless the e-ticket has been exchanged/reissued.Issues:Final Resolution:9. Direct Print General RequirementsCZRequirement:A. CZ will not direct print OA electronic ticket on CZ stock. B. CZ can accept and acknowledge a Cos for PRINTED from the Operating Carrier, but will not return SAC when receive PR status.Issues:Final Resolution:10. Print ExchangeGeneral RequirementsCZRequirement:A. CZ currently can support Print Exchange;B. CZ can accept and acknowledge a Cos for Print Exchange (EDIFACT code is a PE) and respond SAC.Issues:Final Resolution:11. BaggageGeneral RequirementsCZRequirement:A. CZ as Validating Carrier will not issue Excess Baggage Coupons electronically.B. CZ as Operating Carrier will not accept electronic Excess Baggage from any OA as Validating Carrier.C. Excess baggage will be handled procedurally. Passengers will be advised to present their excess baggage coupon to the operating carrier.Issues: Final Resolution:12. Irregular Operations12.1General RequirementsCZRequirement:A. CZ does not support IRR/OP the interim coupon status (i.e. IATA 722F=I, EDIFACT=IO).B. CZ does not support an electronic FIM.Issues: Final Resolution:12.2ReroutingCZRequirement: When change the itinerary, CZ requires an exchange ET.Issues: Final Resolution:12.3Involuntary IndicatorCZRequirement:A. When OA has an irregular operation, CZ can receive/store OA sends I involuntary indicator.B. Involuntary, No reason given, EDIFACT=I, 722F=I.Issues: Final Resolution:12.4Involuntary rerouting CZRequirement: When change the itinerary, CZ requires an exchange ET.Issues: Final Resolution:12.5Endorsement o