The creation of new fares by a pricing system using rule data to specify the fare markets and amounts. The fares can either be calculated from existing fares in the market or specified to create a new fare using the rule provisions coded in Category 25.

The one- to eight-character identification of the fare.

An ATPCO record involving an Automated Rules Tariff, Carrier, Rule Number, Fare Class, Sequence, and Effective date combination. The Fare Class Application record provides miscellaneous data (such as fare type, ticketing codes, and passenger type) pertinent to the specified fare class that is necessary for pricing and assigns the reservation booking designators required to qualify for the fare. Also called Record 1 or Fare Class Record.

See Fare Class Application.

A portion of a journey or itinerary between two consecutive fare break points.

See fare break point.

The Fare Creator Table 979 is located in Category 35 Record 3. Table 979 provides fare calculation information to create either net or selling amounts from the starting fare. Selling amounts can be specified, calculated, or expressed as ranges. Net amounts can be specified or calculated.

A method of identifying multiple fare classes in a single entry. In the Category ID, the Fare Class field can be coded with a hyphen to mean all fare classes that contain these characters.

The act of maintaining and updating fare products (fares, rules, etc.). See also offer management. 2. The business decisions behind creating, modifying, or canceling fare, rule, and other records in order to support complex pricing. Fare management presents both historical and current market fare and rule data that airlines query and use to make changes. This process occurs concurrent to yield management, although most large carriers usually have different departments for these two processes. Also called decision support (industry).

The initial point of a pricing unit.

The organization that contracts with ATPCO to file fares, rules, and other data in its own files under its own control.

The primary purpose of a GDS, this process involves bringing together schedule, inventory, and fare and rule data to price and display itineraries.

A record in the Fares system that contains the actual fare amount, tariff, carrier, market, fare class code, routing, rule number, footnote, and other information.

The automated rule provisions for specific fare classes. The term can refer to rules governing published fares (grouped by categories) or to fares that are contained in the text of a rule (Fare By Rule). The term is used to differentiate between this type of rule and a General Rule.

The process by which the subscriber or pricing system determines which of the ATPCO fare records are applicable to the itinerary; a prerequisite of this process is the determination of the primary portion for each fare component.

A symbolic identification of the characteristics of a fare class that provides a way to group similar types of fares. It is directly connected to the rule provisions.

A document used to determine the correct Normal or Special tag, category type code, and fare type code for fare classes. (See Appendix B of the Automated Rules Subscription Documentation).

Data that includes or supports airline fares. It may include data for fares, rules, general rules, government filings, routings, add-ons, constructions, directories, fuel and insurance fees, surcharges, service fees, ticketing fees, optional service fees, baggage fees, taxes, PFCs, sales data, audit data, prorate data, and meta fare data.

An optional service that is associated to a specific fare and based on the reissue or refunds that are available for that fare. For example, a passenger may want to pre-purchase the opportunity to change or refund the ticketed itinerary.

A web-based application that provides access to all ATPCO's applications, including Fares, Rules, Footnotes, Routings, Market View, Optional Services, and PIPPS.