ROUND THE WORLD (RTW) and CIRCLE (CT) FARES DATA APPLICATION OVERVIEW

Transcription

1 ROUND THE WORLD (RTW) and CIRCLE (CT) FARES DATA APPLICATION OVERVIEW The information contained in this document is the property of ATPCO. No part of this document may be reproduced, stored in a retrieval system, or transmitted in any form, or by any means; mechanical, photocopying, recording, or otherwise, without the prior written permission of ATPCO. Under the law, copying includes translating into another language or format. Legal action will be taken against any infringement Copyright 2002 by Airline Tariff Publishing Company All rights reserved.

2 1.0 OVERVIEW DEFINITIONS AND ASSUMPTIONS DEFINITIONS ASSUMPTIONS EDITS... 7 RTW/CT.Overview.01

3 1.0 OVERVIEW Round the World (RTW) and Circle Trip (CT) fares are priced as single fare components on a single pricing unit where the origin and destination of the fare component are the same point. These fares are governed by unique tariffs. They can be public or private, published or created via Fare By Rule (Category 25), or specified or constructed via the use of add-ons. RTW/CT.Overview.02

4 2.0 DEFINITIONS AND ASSUMPTIONS 2.1 Definitions Term Inbound Travel Outbound Travel Turnaround Definition All sectors after the point of turnaround. All sectors up to the point of turnaround. The furthest ticketed point on the fare component measured from fare component origin. Measurement is based on Great Circle Miles (GCM) Refer to the Glossary and applicable Data Application Documents for the detailed application of the above terms. RTW/CT.Overview.03

5 2.2 Assumptions Tariffs Must be in unique RTW or CT tariffs respectively. Fares Fare component origin and destination must be the same point. o If travel does not have to return to the point of origin, then this is controlled via Transfers (Category 9) Fare Break Surface at destination. Must be RT (Tag 2). However, these fares are not half-round trip fares. Directional Indicator must be F (From). Carrier Fare Selection (Proposed) The carrier whose fare is selected is determined based on standards agreed to set forth in IATA Resolutions 017ha. Surface Sectors Embedded surface sectors are not permitted: o On a transatlantic sector o On a transpacific sector o On a sector between Area 2 and Area 3 NOTE: The above can be overridden via positive embedded surface sector data in Transfers (Category 9) Fare break surface sectors are not permitted on the first sector of the fare component RTW/CT.Overview.04

6 Geographic restrictions For RTW fares, only a single transatlantic and a single transpacific sector is permitted For CT fares o The fare component does not have to contain transatlantic or transpacific travel. o If the fare component contains transatlantic or transpacific travel, then a maximum of two transatlantic sectors are permitted or a maximum of two transpacific sectors are permitted. Both transatlantic and transpacific sectors are not permitted. Backtracking: There are no assumed restrictions. All backtracking restrictions are controlled by automated data in Full Map Routings, Flight Application (Category 4), Stopovers (Category 8), and/or Transfers (Category 9). Refer to data application for these records for further detail. Indirect Travel: There are no assumed limitations on indirect travel (such as those specified in IATA Resolutions). Any restrictions are controlled by automated data in Full Map Routings, Flight Application (Category 4), Stopovers (Category 8), and/or Transfers (Category 9). Refer to data application for these records for further detail. Add-on Construction Specified RTW/CT fares may be combined with RTW/CT add-ons to create a through fare. A single add-on tariff Add-on is added once at origin but impacts travel at origin and destination Constructed fare must have the same origin and destination Add-on must be RT (Tag 2) Zone must be 000. Zone 000 has no application and should be ignored during processing. RTW/CT tariffs will not have any P04 or P06 created. Matching of the specified Fare and Add-on will occur against the Carrier, Tariff, and the Origin of the specified fare and the origin of the Add-on. Add-on must not have footnote F or T Add-on Routing must be Routing 4444 has no application and should be ignored during processing Combinations RTW/CT fares cannot be used in an Open Jaw (OJ), Round Trip (RT), or Circle Trip (CT) Combination. The Record 2 Scoreboard values for Sub-categories 101, 102, and 103 must be N (not permitted). RTW/CT fares can be used in End-on-End or Side Trip Combinations based on applicable Category 10 data. RTW/CT.Overview.05

7 Fare Construction The following are not applicable: Higher Intermediate Point (HIP) checks Mileage Surcharges Differentials RTW/CT.Overview.06

8 3.0 EDITS Edits are proposed as follows in order to support automation of RTW and CT fares. Automated Rules For RTW/CT tariffs only: 1. Fare Class Application (Record 1). OW/RT (byte 48) must be value 2 Directional Indicator (byte 97) must be Blank 2. Category Control (Record 2). Outbound/Inbound (byte 118) must be Blank Directional Indicator (byte 119) must be Blank 3. Category Control (Record 2) for Combinations (Category 10) Single Open Jaw (byte 95) must be value N Double Open Jaw (byte 97) must be value N CT2/RT (byte 109) must be value N CT3+/CT (byte 121) must be value N Outbound/Inbound (byte 180) must be Blank Directional Indicator (byte 181) must be Blank 4. Category Control (Record 2) for Fare By Rule (Category 25) Outbound/Inbound (byte 125) must be Blank Directional Indicator (byte 126) must be Blank 5. Stopovers (Category 8) Out (bytes 18-19) must be Blank In (bytes 20-21) must be Blank OR (byte 22) must be Blank Inbound/Outbound (byte 163) must be Blank 6. Transfers (Category 9) Out (bytes 33-34) must be Blank In (bytes 35-36) must be Blank RTW/CT.Overview.07

9 OR (byte 37) must be Blank Outbound/Inbound (byte 187) must be Blank International Fares For RTW/CT tariffs only: Origin City (bytes 7-11) and Destination City (bytes 14-18) must be the same Routing Number (bytes 45-48) must not be 0000 Directional Indicator (byte 111) must be value F Add-ons For RTW/CT tariffs only: OW/RT (byte 102) must be value 2 Routing Number (bytes ) must be 4444 Footnote (bytes ) must not be value F or T Add-on Zone (bytes ) must be 000 RTW/CT.Overview.08