Patent Grant
7617136
This application is related to the following co-pending and commonly assigned patent application:
application Ser. No. 10/027,967, entitled “SYSTEM AND METHOD FOR CAPTURING AND STORING BUSINESS INFORMATION FOR THE TRAVEL AND TRANSPORTION INDUSTRIES”; filed on Dec. 21, 2001 by Pieter Lessing, William Black, John Kumar, David Hubbard, and Kim Nguyen-Hargett; and
application Ser. No. 10/190,099, entitled “SYSTEM AND METHOD FOR CAPTURING AND STORING FINANCIAL MANAGEMENT INFORMATION”; filed on Jul. 3, 2002 by Sreedhar Srikant, William S. Black, Scott Kilmo, Karen Papierniak, and James W. Smith.
The present invention relates generally to Data Warehouse solutions, and more particularly, to systems and methods for capturing, storing and using detailed business information for the travel and transportation industries. Still more particularly, the present invention is related to a logical data model for storing and organizing revenue management information for travel and transportation industries such as airlines, travel agencies, cruise lines, hotel companies, rental car companies, passenger rail companies and bus lines.
NCR Corporation has developed a data warehouse solution including a comprehensive suite of analytical and operational applications that captures, organizes and advances the use of high-value business information for the travel and transportation industries. This solution provides a travel provider with answers to basic questions such as:
The Enterprise Data Warehouse (EDW) has proved a strategic weapon for most modern organizations. It should be active, dynamic and flexible in order to cope with changing business requirements. It should provide a strategic background to support changing retail consumer-travel provider relationships.
The foundation of the enterprise data warehouse is a comprehensive and responsive logical data model addressing challenges in the near future without compromising existing business processes. A logical data model is a graphical representation of the way data is organized in a data warehouse environment. The logical data model specifically defines which individual data elements can be stored and how they relate to one another to provide a model of the business information. The data model ultimately defines which business questions can be answered from the data warehouse and thus determines the business value of the entire decision support system.
A properly designed LDM provides a foundation for more effective sales, marketing and customer management and supports the customer relationship management (CRM) requirements related to identifying, acquiring, retaining and growing valuable customers. A logical data model for the travel and transportation industries reflects the operating principles and policies of these industries and provides the underlying structure for the data imported into the data warehouse.
Ideally, a logical data model for the travel industry should provide support for current and future revenue management applications, such as NCR Corporation's Teradata® Revenue-Management Intelligence (RMI) solution. The Teradata RMI solution offers travel providers the capability to understand customer demand and behavior and optimize their current revenue-management systems and processes. The Teradata RMI solution allows travel providers to integrate historic, current and future inventory, schedule, flight and booking data onto a single platform to support both tactical and strategic decision-making, allowing for reduced delays and gaps in information. Travel providers will also be able to monitor and refine the success of their efforts through the measurement, tracking and reporting of revenue-management performance.
It is an object of the present invention to provide a new and useful system and method for capturing, storing and organizing information supporting revenue management applications for travel and transportation industries.
It is a further object of the present invention to provide a logical data model that defines the structure for storing and organizing revenue management information for travel and transportation industries.
The foregoing objects are accomplished through utilization of a revenue management system for a travel provider comprising: a database for storing revenue, product and service, and customer information for a travel provider; a logical data model comprising a plurality of entities and relationships defining the manner in which the revenue, product and service, and customer information is stored and organized within the database; and a revenue management application for analyzing the revenue, product and service, and customer information contained within the database to manage inventory, pricing and demand forecasting for the travel provider. The travel provider can be an airline, a car rental agency, a cruise line, a lodging provider; a travel agency; a bus line or a passenger rail service provider.
Analysis of Passenger Name Record (PNR), booking, ticketing, inventory, schedule, authorization adjustment and flown/ticket lift data maintained within the database enables a travel provider to identify fraudulent and improper booking and ticketing activity, or an airline to determine optimal passenger and revenue mix for airline flights.
Still other objects and advantages of the present invention will become readily apparent to those skilled in the art from the following detailed description, wherein the preferred embodiments of the invention are shown and described, simply by way of illustration of the best mode contemplated of carrying out the invention. As will be realized, the invention is capable of other and different embodiments, and its several details are capable of modifications in various obvious respects, all without departing from the invention. Accordingly, the drawings and description thereof are to be regarded as illustrative in nature, and not as restrictive.
The present invention is illustrated by way of example, and not by limitation, in the Figures of the accompanying drawings, wherein elements having the same reference numeral designations represent like elements throughout and wherein:
Subject Area of the logical data model in accordance with the preferred embodiment of the present invention;
Subject Area of the logical data model in accordance with the preferred embodiment of the present invention;
A travel and transportation industry customer-centric warehouse is established on the Teradata Scalable Data Warehouse 101 as defined by the Travel Logical Data Model (TLDM), described below. The application server 103 supports analytic and operational applications, such as NCR Corporation's Teradata Solutions for Travel and Transportation suite of business applications.
The Travel Logical Data Model is a consumer-centric travel data model supporting Revenue Management, Financial Management, Customer Relationship Management, Privacy and Click Stream analysis. It can serve as the base for a full enterprise data warehouse implemented at the client's site. The model has been designed in a modular fashion so non-relevant components can be removed without impacting the consistency of the model. It's an integrated, subject-oriented base of strategic business information that serves as a single source of decision support, providing the travel provider with the ability to make simple reports or sophisticated information analysis.
The TLDM supports the following core areas: Base Functions 220, Privacy 222, Customer Relationship Management (CRM) 224, Click Stream 226 and Financial 228. Together with Revenue Management segment 244, the TDLM supports functionality broken down into three main areas:
(1) Solution support—The Travel LDM supports the Teradata CRM, the Financial Management and the Revenue Management Intelligence solution offers.
(2) Business Information areas covered by the Model—The Travel LDM contains application-neutral information about the following subjects and more:
(3) Business Intelligence that can be derived from the information—The Treavel LDM supports a vast amount of business intelligence. Some examples:
The Teradata Travel Logical Data Model, as described herein, serves several different kinds of customers, including Airlines 230, Rental Car Companies 232, Cruise Lines 234, Lodging (Hotel) Companies 236, Travel Agencies 238, Bus Lines 140, and Passenger Rail 242. Companies.
As stated earlier, a properly designed logical data model provides a foundation for more effective sales, marketing, and operations management and supports the customer relationship management requirements related to identifying, acquiring, retaining and growing valuable customers.
A logical data model (LDM) is an abstract construct that is physically realized in the database or data warehouse. The data model provides an architecture for the information that will be included in a data warehouse. The database provides the physical realization of that architecture in a form that can be efficiently maintained and used. There may well be some differences between the logical data model and the final database design. The database may include some tables (summary tables, etc.) or columns that have no direct correlation in the logical data model. Elements in the logical model may be grouped differently in the physical database.
A logical data model is organized by Subject Areas, each comprised of numerous Entities, Attributes and Relationships. The data model hierarchy includes one or more Subject Areas. Each Subject Area includes one or more Entities or Tables, each having Attributes and Relationships. Each Attribute describes a fact about an Entity. Relationships between two or more Entities are further defined by Cardinality. The Relationships define which entities are connected to other entities and the cardinality of the relationships. Each of these elements will be described in greater detail below.
A subject area is a subset of objects taken from the universe of data objects for a particular line of business or industry that focus on a particular Business Process. Typically, a subject area is created to help manage large data architectures that may encompass multiple business processes or business subjects. This is the highest-level data concept within a conceptual entity/relationship (E/R) model. Working with subject areas is especially useful when designing and maintaining a large or complex data model. Dividing the enterprise into several distinct subject areas allows different groups within an organization to concentrate on the processes and functions pertinent to their business area.
An Entity represents a person, place, thing, concept, or event (e.g. PARTY, ACCOUNT, PRODUCT, etc.). It represents something for which the business has the means and the desire to collect and store data. An Entity must have distinguishable occurrences, e.g., one must be able to uniquely identify each occurrence of an entity with a primary key (e.g. Party Identifier, Account Identifier, Invoice Number, etc.). An Entity is typically named with a unique singular noun or noun phrase (e.g., PARTY, TRANSPORTED PASSENGER, etc.) that describes one occurrence of the Entity and cannot be used for any other Entity. It should be exclusive of every other Entity in the database. An Entity cannot appear more than once in the conceptual entity/relationship (E/R) model. Each Entity may have relationships to other Entities residing in its own Subject Area or in other Subject Areas.
An Attribute is a data fact about an Entity or Relationship. It is a logical (not physical) construct. It is data in its atomic form. In other words, it is the lowest level of information that still has business meaning without further decomposition. An example would be FIRST NAME, or LAST NAME. An example of an invalid attribute would be PERSON NAME if it includes both the first and last names, as this could be further decomposed into the separate, definable (first name, last name) data facts.
A Relationship is an association that links occurrences of one or more Entities. A Relationship must connect at least one Entity. If only one Entity is connected, the Relationship is said to be Recursive. A Relationship is described by a noun or passive verb or verb phase that describes the action taken in the Relationship. A Relationship represent a static state of being between the occurrences of the Entities it connects. Relationships are not intended to represent processes or data flows. They cannot be linked to another Relationships. They may optionally represent future, present, and/or past relatedness. The time frame must be explicitly defined in the data definition. Relationships may contain attributes. In a normalized model, a Relationship containing Attributes will result in the creation of an Entity.
In order for a data model to be considered accurate, it must contain both the maximum and minimum number of Entity occurrences expected. This is controlled by rules of cardinality, which describes a relationship between two Entities based on how many occurrences of one Entity type may exist relative to the occurrence of the other Entity. Typically, it is a ratio, commonly depicted as a one-to-one (1:1); one-to-many (1:N); and many-to-many (M:N) relationship.
The maximum cardinality may be an infinite number or a fixed number but never zero. The minimum cardinality may be zero, or some other positive number, but it must be less than or equal to the maximum cardinality for the same relationship.
The logical data model for the E-Business will now be described in more detail. The logical data model uses IDEF1X modeling conventions, as shown in Table 1.
Relationship and cardinality conventions are shown in Table 2.
The Travel Logical Data Model (TLDM) is a large data model composed of a large number of tables. To effectively view and understand the data model, the data tables have been logically organized into smaller groups called subject areas. Each subject area is comprised of a set of tables that contain information relevant to a particular entity. In addition, the subject areas address particular business questions.
The Travel Logical Data Model is presented in the following views to facilitate its understanding:
The Conceptual View of the Travel Logical Data Model is illustrated in
The Conceptual View is derived directly from the Travel Logical Data Model by selecting the most important entities from every subject area, being sure that at least one entity from each subject area was selected and distilling the relationships among the selected entities, while still maintaining the general nature of the way the entities relate to each other. During this process, intervening entities were abstracted into relationships. Many-to-many relationships were used where appropriate. Several entities shown in the Conceptual View, e.g., PAYMENT ACCOUNT 412/414, OnD PRODUCT PERFORMANCE 1700, FM JOURNAL ENTRY 2001, and WEB OPERATIONS 2700, represent a subject area or combination of entities within a subject area. The result is a simple, easy to understand diagram that conveys the general content of the underlying logical data model.
Each subject area within the logical data model, as well as the entities included within the subject area, will be illustrated in the Figures and described in greater detail below.
The Subject Area Views show small (but highly detailed) subsets of the model. Subject areas are collections of entities about business information objects or concepts that are closely related. The sum total of all subject areas equals the TLDM. These views contain the definitive full details of the logical data model. For example, one view shows entities related to assets controlled by the travel business and another view shows entities related to reservations with the travel business. Subject areas are application neutral, and make no assumption as to usage. Additionally, subject areas form the building blocks with which to construct solution views.
For ease of use and understanding, the Travel Logical Data Model has been divided into twenty-six subject areas titled: ACCOUNT, ASSET, DEMOGRAPHICS, FM ASSET, FM EQUITY, FM EXPENSE, FM GENERAL LEDGER ACCOUNT, FM JOURNAL ENTRY, FM LIABILITIES, FM REVENUE, FORECASTS AND MODELS, GEOGRAPHY, LOCATION, OND PRODUCT PERFORMANCE, PARTY, PASSENGER EN ROUTE, PRN OPERATIONS, PRIVACY, PRODUCT, PROMOTION, PURCHASE, RESERVATION, TRAVEL TRANSACTION, WEB OPERATIONS, WEB SITE, and WEB VISIT subject areas. There is some natural overlap between the subject areas, i.e., an entity may appear in multiple subject areas if it has direct relationships with entities in multiple subject areas. For example, the FARE BASIS table appears in the Figures for both the PURCHASE and RESERVATION subject areas. This means that the information in the FARE BASIS table is relevant to each of those subject areas; each subject area refers to the same physical item table.
A discussion of the subject area views illustrated in detail in
The ACCOUNT Subject Area, shown in
Provisions have been made to handle award balance transfers from partners and their various loyalty programs. These can include hotel, rental car, credit card and other loyalty programs. Most current award redemption options are built into the model. Additional award options can to be added. These reflect awards in an actual AWARD CERTIFICATE or an electronic version of one.
Payment can be made in a variety of ways. Checking Account and Credit Card are present as sub-types of Account in the Account Subject Area. Cash, Travel Pass, and Certificate are present as sub-types of Payment in the Purchase Subject Area.
The entities of the ACCOUNT Subject Area are defined as follows:
ACCOUNT (401) An account established by a PARTY with an ORGANIZATION typically to facilitate and enable the transfer of funds.
ACCOUNT BALANCE (HISTORY) (402) A history of all transactions associated with a rewards account. It tracks earnings as well as dispersions (Award Redemption) and maintains current as well as lifetime balances. This is an example of a physicalized/history construct that would be needed if all information since inception is not kept.
ACCOUNT EARNINGS (403) A subtype of transaction associated with an Account Balance transaction that tracks all reward earnings posted to a Rewards Account.
ACCOUNT LEVEL (404) This entity is the domain of Account Levels achievable within a Rewards Program. Example Levels can be Bronze, Silver, Gold or Standard, Premier, Executive Premier, etc.
ACCOUNT REDEMPTION (405) A subtype of transaction associated with an Account Balance transaction that tracks all Award disbursements from a Rewards Account.
ACCOUNT TYPE (406) Describes a kind of ACCOUNT. Example: Checking, Credit Card, Loyalty Card, etc.
AIRPORT LOUNGE AWARD (407) This entity is a subtype of Award Certificate and allows a specific airline customer to gain access to the VIP LOUNGE.
AWARD (408) The entity that represents an award requested by the customer as a result of redemption of frequent traveler points or as payment by the travel provider for having provided poor service.
AWARD CERTIFICATE (409) The actual certificate or type of Award requested and received by a customer.
AWARD TYPE (410) The domain that discriminates the type or kind of AWARD. Example: First Class Round Trip or First Class Upgrade.
CHARITY DONATION (411) The sub-type for redemption certificates used to contribute airline mileage to charitable organizations.
CHECKING ACCOUNT (412) An agreement between a PARTY and a financial ORGANIZATION to establish an account to draw funds against using a checkbook. Example: Bank of America VIP Plus Checking Account #333-444-333
COMPENSATORY EARNINGS (413) Segment credits, points, and other earnings given as compensation to a customer by Customer Service. Usually as a result of a service incident or complaint.
CREDIT CARD (414) A physical card issued by an ORGANIZATION, enabling customers to make purchases on credit. Example: Citibank platinum Visa
CREDIT RATING (415) Internal or external ways of classifying a PARTY's or a PAYMENT ACCOUNT's credit worthiness. Example: Do not extend credit to this person, low risk, high risk, TRW score.
DIRECT EARNINGS (416) Segment credits and points award earnings resulting from customer's use of travel related services.
EXCHANGE AWARD (417) A subtype of Award Certificate that associates a specific Account Redemption to a Reward Program exchange.
LOYALTY ACCOUNT (418) An account issued by an enterprise to a PARTY to encourage purchase behavior in the form of DISCOUNTs or the collection of frequent purchaser points
LOYALTY ACCOUNT EVENT (419) This entity represents the activity taking place in a PARTY's Loyalty Account. Example: ACCOUNT EARNINGS or ACCOUNT REDEMPTION.
LOYALTY EVENT TYPE (420) The domain of the discriminator of an Account Balance transaction. Examples are: Earnings, Redemptions, Adjustments, etc.
LOYALTY PROGRAM (421) A defined program for tracking and qualifying reward earnings and granting award packages.
OFFER (422) A specific incentive made available to customers. Usually contains 2 parts: a.) condition(s) to be met, and b.) the reward for a.) Example: Fly American to Hawaii in December 2001 and stay free at the Sheraton for a weekend.
PARTNER AWARD (423) A subtype of Award Certificate that associates a specific Account Redemption to a PARTNER.
PARTNER EARNINGS (424) A sub-type of the ACCOUNT EARNINGS that represents the earnings received from PARTNER PARTYs.
PARTNER PRODUCT (425) Identifies the PRODUCTs offered by a PARTNER PARTY.
TICKET AWARD (426) This entity is a subtype of AWARD CERTIFICATE and associates a specific ACCOUNT REDEMPTION to a TICKET or Flight Pass.
TRANSFER EARNINGS (427) A sub-type of the ACCOUNT EARNINGS that represents the earnings transferred to or from a PARTY.
UPGRADE AWARD (428) This entity is a subtype of AWARD CERTIFICATE and tracks information associated with a Transportation Fare Class Upgrade Award
The entities of the ASSET Subject Area are defined as follows:
AIRCRAFT (501) This entity reflects a specific airplane used to transport passengers and goods.
ASSET (502) A specific passenger, freight vehicle, or lodging property.
ASSET TYPE (503) A subtype of asset which describes the particular kind of ASSET. Example: BUS, TRAIN, AIRCRAFT, CRUISE SHIP, etc.
BUS (504) This entity reflects a ground based vehicle used for transporting multiple customers and goods.
CRUISE SHIP (505) This entity reflects a specific Ship used to transport passengers and goods.
LODGING PROPERTY (506) A property that provides temporary lodging for INDIVIDUALs.
PASSENGER RAILROAD CAR (507) This entity reflects a specific passenger train car used to transport passengers.
RENTAL VEHICLE (508) A specific vehicle which customers can rent for temporary use. Example: Ford Taurus, Buick Century.
SERVICE CLASS CONFIGURATION (509) Indicates the sellable capacity per class of service. Expressed in “seats” for aircraft, “cabins” for Ships, etc. Example: AIRCRAFT: 20 1st class seats, 120 coach class seats, etc.
TRANSPORT VEHICLE (510) This entity reflects the domain of vehicles used to transport passengers and goods.
TRANSPORT VEHICLE CONFIG (511) A Pre-defined configuration of a TRANSPORT VEHICLE with a fixed number of sellable “spots” per SERVICE CLASS.
TRANSPORT VEHICLE TYPE (512) Identifies the type of TRANSPORT VEHICLE Example: Cruise Ship, Aircraft, etc.
VEHICLE MODEL (513) The type of vehicle as manufactured. Example: Boeing 747 model 300, Acura 3.2 TL.
Subject Area stores information concerning customer segments of interest to the retail enterprise. Its primary usage is for the creation of market or consumer SEGMENTs (groups of PARTYs sharing common characteristics) for marketing purposes. Additionally, DEMOGRAPHICs can be used to find common characteristics or profiles of a select group of consumers. This information is typically obtained (purchased or leased) from a third party.
The entities of the DEMOGRAPHIC Subject Area are defined as follows:
ADDRESS DEMOGRAPHIC (601) Contains specific characteristic information about a geographic area. Typically purchased from a 3rd Party. Example: Zip Code 90210 has a characteristic of Median Income >$100,000 per year.
DEMOGRAPHIC (602) Information (usually purchased form a third party) describing a PARTY or geographic area or PARTYs in a geographic area. Example: PARTY Income Level, Credit Rating, Number of children, etc. Geographic: Average temperature in January, etc. PARTYs in a Geographic Area: Typical household size, Number of automobiles, etc.
DEMOGRAPHIC GROUP (603) A clustering of related DEMOGRAPHICs. Example: Financial (contains Income Level, Credit Rating, etc.)
DEMOGRAPHIC VALUE (604) The actual value of a DEMOGRAPHIC. Example: Income level=‘Between $40,000 and $49,999’
PARTY DEMOGRAPHIC (605) Contains specific characteristic information about a PARTY. Typically purchased from a 3rd Party. Example: INDIVIDUAL: Rachel has an income of $120,000 HOUSEHOLD: The Smiths have 5 kids and 2 cars. ORGANIZATION: Acme Explosives & Gifts has annual sales revenue of $4M.
SEGMENT MEMBER (606) An associative entity that maps INDIVIDUALs into SEGMENTs. An INDIVIDUAL can be a member of multiple SEGMENTs, and vice versa.
SEGMENTATION (607) A cluster of PARTYs for marketing purposes. A SEGMENTATION can be re-used, and can receive multiple OFFERs Note: This is typically called a SEGMENT, but we choose SEGMENTATION instead to avoid confusion due to the specialized use of the term “SEGMENT” in the airline industry.
SEGMENTATION COMPONENT (608) The characteristics that qualifies a PARTY to be a member of a SEGMENTATION. Example: ‘Income between $20,000 and $29,999’, ‘Made more than 5 purchases in the last month’, etc.
SEGMENTATION GROUP (609) Allows related SEGMENTATIONs to be grouped together. Example: to segment top spenders into 10 decile segments—these 10 segments can now all be grouped together by relating them to the same SEGMENTATION GROUP: e.g: “Top Spenders by decile”
Financial Management information is detailed in seven Subject Areas, all prefixed with “FM” (Financial Management). Financial Management Subject Areas include FM ASSET, FM EQUITY, FM EXPENSE, FM GENERAL LEDGER ACCOUNT, FM JOURNAL ENTRY, FM LIABILITIES, and FM REVENUE Subject Areas.
Everything a business owns is usually referred to as Assets. These range from cash and investments to natural resources such as land, timber, etc. For accounting purposes these are usually classified under three groups: Current Assets, Fixed Assets and Other Assets.
The entities of the FM ASSET Subject Area, illustrated in
ACCOUNTS RECEIVABLE (701) The entity that provides details for the accounts receivable accounts. Accounts receivable are the payments a company expects to collect from a party. Accounts receivable accounts are types of current assets.
AMORTIZATION METHOD (702) This reference entity contains the various ways that an amount can be amortized such as cash basis (no amortization), straight line, declining balance, and interest method. A=cash basis (assumed that there should not be an entry specifying cash) B=straight line C=declining balance D=interest method
ASSET ACCOUNT (703) The entity that indicates the types of asset accounts.
ASSET ACCOUNT TYPE (704) The entity that identifies the type of asset like fixed asset, current asset, or other asset.
AVAILABLE CASH ACCOUNT (705) The entity that provides details for the available cash accounts. These accounts are any cash in currency, checking and savings accounts. Available cash accounts are types of current assets.
CURRENT ASSET ACCOUNT (706) The entity that indicates the types of current asset accounts.
CURRENT ASSET ACCOUNT TYPE (707) The entity that identifies the type of current asset like available cash, prepaid expenses, inventory, accounts receivable, or securities.
DEFERRED CHARGE ACCOUNT (708) The entity that provides details for deferred charges. These are expenditures that will be gradually written off over a future period of time.
DEPRECIABLE ASSET ACCOUNT (709) The entity that identifies the depreciable fixed asset account. Depreciable assets include property, plant and equipment.
EQUIPMENT ACCOUNT (710) The entity that provides details for equipment accounts. Equipment is used to perform company business. Equipment is a type of a depreciable asset.
FIXED ASSET ACCOUNT (711) The entity that indicates the types of fixed asset accounts.
FIXED ASSET ACCOUNT TYPE (712) The entity that identifies the type of fixed asset account like depreciable asset or non-depreciable asset account.
GOODWILL ACCOUNT (713) The entity that provides details for goodwill. These details could include the cost differential between the acquisition cost of a business and the market value of the asset acquired.
INTANGIBLE ASSET ACCOUNT (714) The entity that indicates the other asset is intangible. Types of intangible assets are patents and goodwill. These assets have no physical existence, yet having a substantial value to the company.
INTANGIBLE ASSET ACCT TYPE (715) The entity that indicates the type of an intangible asset account. For example: patent or goodwill.
INVESTMENT ASSET ACCOUNT (716) The entity that provides details for investments. These investments in debt securities with a positive intent and the ability to hold these securities until they mature.
NONDEPRECIABLE ASSET ACCOUNT (717) The entity that identifies the non-depreciable fixed asset account. Non-depreciable assets include things like raw land.
OTHER ASSET ACCOUNT (718) The entity that indicates the asset account is a other asset account. Types of other asset accounts include investments, deferred charges or intangible assets.
OTHER ASSET ACCOUNT TYPE (719) The entity that indicates the type of an other asset. For example: investments, deferred charges or intangible asset.
PATENTS ACCOUNT (720) The entity that provides details for patents. These details could include the legal cost a company paid an individual or a company to obtain a patent.
PLANT ACCOUNT (721) The entity that provides details for plant accounts. Plants are the buildings that are used to perform company business. Plants are a type of a depreciable asset.
PREPAID EXPENSE ACCOUNT (722) The entity that provides details for the prepaid expense accounts. Prepaid expenses are those expense that have been paid in advance like insurance. Prepaid expense accounts are types of current assets.
PROPERTY ACCOUNT (723) The entity that provides details for property accounts. Property is a type of a depreciable asset.
RAW LAND ACCOUNT (724) The entity that provides details for raw land accounts. Raw land is a type of a non-depreciable asset.
SECURITIES ACCOUNT (725) The entity that provides details for the securities accounts. Securities are short term investments with a maturity of three to twelve months. Securities accounts are types of current assets.
The FM EQUITY Subject Area, illustrated in
Entities belonging to this Subject Area and their definitions are as follows:
COMMON STOCK ACCOUNT (801) The entity that identifies a dividend equity as common stock. Common stock are units of ownership of a public corporation.
COMMON STOCK ACCOUNT TYPE (802) The entity that identifies the type of common stock accounts. Types of common stock include voting stock and non-voting stock.
DIVIDEND EQUITY ACCOUNT (803) The entity that identifies the equity account has dividends. Types of dividend equities are common stock and preferred stock.
DIVIDEND EQUITY ACCOUNT TYPE (804) The entity that identifies the type of dividend for dividend equity accounts. Types of dividend equities are common stock and preferred stock.
EQUITY ACCOUNT (805) The entity that indicates a general ledger account is an equity account. These accounts are related to ownership interest possessed by the shareholders in a company. Types of equity accounts include dividend equity and non-dividend equity.
EQUITY ACCOUNT TYPE (806) The entity that identifies the type of equity account. Types of equity accounts include dividend equity and non-dividend equity.
EQUITY SURPLUS ACCOUNT (807) The entity that identifies the net worth that is from stock issued at a premium over par or stated value.
FOREIGN CURRENCY ADJ ACCOUNT (808) The entity that identifies a non-dividend equity as a foreign currency adjustment. Foreign currency adjustments are the gains or losses resulting from a translation of one currency into another.
NONDIVIDEND EQUITY ACCOUNT (809) The entity that identifies the type of non-dividend equity. Types of non-dividend equities include retained earnings, treasury stock and foreign currency adjustments.
NONDIVIDEND EQUITY ACCT TYPE (810) The entity that Identifies the type of non-dividend equity accounts. Types of non-dividend equity accounts include retained earnings, treasury stock and foreign currency adjustments.
NONVOTING STOCK ACCOUNT (811) The entity that identifies a common stock dividend equity as a non-voting stock. Non-voting stock equities of a public corporation do not posses voting rights.
PREFERRED STOCK ACCOUNT (812) The entity that identifies a dividend equity as preferred stock. Preferred stock has preference over common stock in the payment of dividends and the liquidation of assets.
RETAINED EARNING ACCOUNT (813) The entity that identifies a non-dividend equity as retained earnings. Retained earnings are net profits kept to accumulate in a business after dividends are paid.
TREASURY STOCK ACCOUNT (814) The entity that identifies a non-dividend equity as treasury stock. Treasury stock is required by the issuing company and is available for resale or retirement.
VOTING STOCK ACCOUNT (815) The entity that identifies a common stock dividend equity as a voting stock. Voting stock equities of a public corporation have voting rights.
The FM EXPENSE Subject Area tracks expense detail data, effecting easy tracking of expenses, e.g. salaries, product costs, etc., by Accounting Period (time), Travel Transaction, Customer, etc.
The entities of the FM EXPENSE Subject Area, illustrated in
BENEFITS EXPENSE (901) The entity that provides details for benefit accounts. Benefits are set-aside for associates for services rendered. Benefit accounts are a type of labor accounts.
COST OF SALES ACCOUNT (902) The entity that indicates the expense account is a cost of sales. These are costs a company incurs to purchase products or services that it sells.
EXPENSE ACCOUNT (903) The entity that indicates a general ledger account is an expense account. Types of expense accounts include operating expense, interest expense and other expense.
EXPENSE ACCOUNT TYPE (904) The entity that indicates the type of expense account. Types of expense accounts include cost of sales, operating expense, interest expense, interest income and other expense.
FACILITY OP EXPENSE ACCOUNT (905) The entity that indicates the operating expense pertains to facilities. Facility expenses are related to the maintenance of a physical facility.
GENERAL AND ADMIN ACCOUNT (906) The entity that indicates the operating expense pertains to general and administrative. These expenses are typically classified as administrative in nature. For example: advertising, salaries, commissions, office expense, etc.
INTEREST EXPENSE ACCOUNT (907) The entity that indicates the expense account is an interest expense. Interest expense is paid to bondholder's for the use of their money.
LABOR EXPENSE (908) The entity that indicates labor expenses related to salary, wages and benefits for operating expenses such as marketing expense, general and administrative and research and development.
LABOR EXPENSE TYPE (909) The entity that indicates the type of labor expense. Labor expenses include salary, wages and benefits.
MARKETING EXPENSE ACCOUNT (910) The entity that indicates the operating expense pertains to marketing. Marketing expenses are related the actual marketing of a product (i.e. advertising).
OPERATING EXPENSE ACCOUNT (911) The entity that indicates the expense account is an operating expense. Operating expenses are those that are required to run a company.
OPERATING EXPENSE ACCOUNT TYPE (912) The entity that indicates the type of operating expense accounts. Operating expenses include selling, marketing, general and administrative, research and development, facilities and others.
OTHER EXPENSE ACCOUNT (913) The entity that indicates the expense account is for other operating expense. Other expenses are those that are required to run a company and cannot be classified as one of the other types of expenses.
OTHER OP EXPENSE ACCOUNT (914) The entity that indicates the operating expense pertains to other operating expenses. These expenses are general in nature and cannot be classified as one of the other types of operating expenses.
R AND D EXPENSE ACCOUNT (915) The entity that indicates the operating expense pertains to research and development. Research and development expenses are related to research and development of products or services for a company.
SALARY (916) The entity that provides details for salary accounts. Salary is compensation paid to associates for services rendered. Salary accounts are a type of labor accounts.
WAGES (917) The entity that provides details for wage accounts. Wages is compensation paid to hourly employees for services rendered. Wage accounts are a type of labor accounts.
FM GENERAL LEDGER ACCOUNT Subject Area
There are five main types of General Ledger Accounts. They are ASSET ACCOUNT, LIABILITY ACCOUNT, EXPENSE ACCOUNT, REVENUE ACCOUNT and EQUITY ACCOUNT. Each account in turn may have sub-ledgers. For example, ASSET ACCOUNT consists of FIXED ASSET or CURRENT ASSET, etc.
Entities belonging to this Subject Area and their definitions follow:
FINANCIAL PLAN (1001) The entity that provides details about how much money is planned to be available, how it is to be divided up and spent for various purposes.
FINANCIAL PLAN STATUS (1002) The entity that provides the status of a financial plan.
GL ACCOUNT BALANCE (1003) The entity that indicates the balance amounts for various combinations of projects, departments and general ledger accounts.
GL ACCOUNT INTERNAL ORG (1004) The entity that provides an association between general ledger accounts and internal departments.
GL ACCOUNT INTERNAL ORG TYPE (1005) The entity that indicates the types of general ledger accounts and how internal organizations use them.
Usually journal entries are batch processed into the general ledger system by the feeder systems. For example, an airline's expense reimbursement system likely interfaces with the general ledger on a periodic cycle, resulting in a batch posting of journal entries. A journal entry has one header and multiple lines, each journal entry line having a monetary amount that can be translated to accommodate the airlines' standard currency. A large airline will likely have many sets of books to track journal entries. This is a mechanism to help manage the accounting process. An internal organization will use many general ledger accounts to record transactions, but only one set of books.
Entities belonging to this Subject Area and their definitions are as follows:
GL ACCOUNT TYPE (1006) The entity that indicates the types of general ledger accounts.
GL ACCOUNT (1101) The entity that indicates accounts used in financial transactions for a company. This includes both the general ledger and subsidiary ledger accounts.
GL BATCH (1102) The entity that groups journal entries into general ledger transactions.
GL BATCH TYPE (1103) The entity that indicates the type of general ledger batch.
GL POSTING STATUS (1104) The entity that indicates the posting status of a general ledger batch.
JOURNAL ENTRY HEADER (1105) The entity that provides summary of an accounting transaction recorded in the general ledger.
JOURNAL ENTRY LINE (1106) The entity that provides details of an accounting transaction usually, credit or debit recorded for a transaction. One journal entry header will have multiple journal entry lines.
SET OF BOOKS (1107) The entity that indicates a collection of accounting transactions used by a company. A collection is typically referred to as a ‘set of books’.
The entities of the LIABILITIES subject area are defined as follows:
ACCOUNTS PAYABLE (1201) The entity that provides details of accounts payable for a company. Accounts payable records how much a company owes suppliers for the purchase of supplies or services on credit.
ACCRUED LIABILITY ACCOUNT (1202) The entity that provides details for the accrued liabilities. Accrued liabilities are expenses from prior periods that have not been paid.
CURRENT LIABILITY ACCOUNT (1203) The entity that indicates the types of current liability accounts.
CURRENT LIABILITY ACCOUNT TYPE (1204) The entity that identifies the type of current liability accounts. Types of current liabilities include accrued liability, deferred revenue, short-term debt, current long-term debt, income taxes and accounts payable.
CURRENT LONG TERM DEBT ACCOUNT (1205) The entity that provides details for the current long-term debt. Long-term debt is the principal on the long-term debt due in the next year.
DEFERRED INCOME TAX ACCOUNT (1206) The entity that provides details for the deferred income taxes. Deferred income taxes are the tax liabilities a company may postpone paying until some future time.
DEFERRED REVENUE ACCOUNT (1207) The entity that provides details for the deferred revenue. Deferred revenue is sales or revenues the company has been paid but has not yet earned, such as advance deposits on a contract.
DEPRECIABLE ASSET ACCT PAYABLE (1208) This associative entity provides details of accounts payable for a company and identifies the depreciable fixed asset general ledger account.
INCOME TAX PAYABLE ACCOUNT (1209) The entity that provides details for the income taxes. Income taxes are the amount due to taxing authorities.
LIABILITY ACCOUNT (1210) The entity that indicates a general ledger account is a liability account. These accounts are related to money owed to owner party. Types of liability accounts include current liability and non-current liability.
LIABILITY ACCOUNT TYPE (1211) The entity that identifies the type of liability account. Types of liability accounts are current liability and non-current liability.
LONG TERM DEBT ACCOUNT (1212) The entity that provides details for the long-term debt. Long-term debt is the liability amount due in a year or more.
NONCURRENT LIABILITY ACCOUNT (1213) The entity that indicates the liability account is a non-current liability. Non-current liabilities that are not due in the next twelve months. Types of non-current liabilities include deferred income taxes, long-term debt and reserves.
NONCURRENT LIABILITY ACCT TYPE (1214) The entity that identifies the type of non-current liability accounts. Types of non-current liabilities include deferred income taxes, long-term debt and reserves.
RESERVES ACCOUNT (1215) The entity that provides details for the reserves. Reserves are the accrual of anticipated expenses to be paid out in the future, such as product liability, litigation, etc.
SHORT TERM DEBT ACCOUNT (1216) The entity that provides details for the short term debt. Short term debt is all dept obligations coming due within one year.
The FM REVENUE Subject Area tracks revenue, or income, detail data. The entities of the FM REVENUE Subject Area, illustrated in
INTEREST INCOME ACCOUNT (1301) The entity that indicates the expense account is for interest income. Interest income is received by the company from its investment in stocks and bonds.
OTHER REVENUE ACCOUNT (1302) The entity that provides details on other revenue. Other revenue is income from activities that are not in the normal course of business.
REVENUE ACCOUNT (1303) The entity that indicates a general ledger account is a revenue account. Types of revenue accounts include interest income and other revenue.
REVENUE ACCOUNT TYPE (1304) The entity that indicates the type of revenue account. Types of revenue accounts include sales revenue and other revenue.
SALES REVENUE ACCOUNT (1305) The entity that provides details on the sales revenue. Sales revenue is the primary source of revenue earned by the company from its customers.
The entities of the FORECASTS and MODEL SCORES Subject Area are defined as follows:
ANALYTICAL MODEL (1401) Describes a process used to predict, cluster, or classify information. Typically used in Data Mining and Knowledge Discovery. Examples: Sales Forecasting, Customer Scoring and Segmentation, a model that describes the propensity of a customer to defect to another travel provider.
ANALYTICAL MODEL ALGORITHM (1402) Describes the type of algorithm used to construct the model. Example: Neural Network, Cluster, Regression.
ANALYTICAL MODEL TYPE (1403) Describes the type of model. Example: Seasonal Sales Forecast, Promotional Order Forecast, Customer Scoring, Segmentation, etc.
FORECAST BOOKING CURVE (1404) Used for future estimates, projections & forecasts for a given PRODUCT (or SEGMENT). Accommodates multiple simultaneous methods and forecast sources. Can also house the (derived) “actual” quantity to compare against “forecast”. This example forecasts the Booking Curve (Reservations per Booking Class at a given checkpoint prior to departure)
FORECAST SALES (1405) Used for future estimates, projections & forecasts for a given PRODUCT (or SEGMENT). Accommodates multiple simultaneous methods and forecast sources. Can also house the (derived) “actual” quantity to compare against “forecast”
MODEL RUN (1406) Describes an actual execution of an ANALYTICAL MODEL. Example: Seasonal Item forecast for Q1 that was run on Dec. 12.
PARTY ROLE (1407) Code and description used to identify the role of the PARTY in the PARTY TRAN ROLE entity. Example: Reservationist, Traveler, Travel Requestor, etc.
The GEOGRAPHY Subject Area, shown in the diagram of
The entities of the GEOGRAPHY Subject Area are defined as follows:
ADDRESS (1501) An ADDRESS provides a means of communications such as postal address, telephone number, or electronic address (e.g. e-mail). An ADDRESS may also represent a physical location (e.g. street, post office box, parcel of land, cell-site tower) or a geographical boundary (e.g. North East America, EMEA) for sales and marketing purposes.
ADDRESS RELATED (1502) The relationships that exist between two Addresses, as specified by Address Related Reason. For example, one Address may be an alternate for another Address.
ADDRESS RELATED REASON (1503) Domain of values indicating why one occurrence of Address has a relationship to another Address.
ADDRESS TYPE (1504) Indicates if an ADDRESS is a GEOGRAPHY, ELECTRONIC, or TELEPHONE.
ADDRESS USAGE (1505) The way an ADDRESS is used in a specific instance, usually by a PARTY. Example: GEOGRAPHY ADDRESS usage (market to, bill to, ship to, etc.) TELEPHONE ADDRESS usage (fax, voice, pager, etc.)
AREA (1506) The entity that indicates an area for a GEOGRAPHY ADDRESS. Areas can consist of multiple countries. For example: Europe, Asia, etc.
CENSUS BLOCK (1507) A grouping of ADDRESSes used by the government for census statistics. Usually a subset of POSTAL CODE. Example:
The number of 3 member HOUSEHOLDs in a small geo area according to the 1998 census data.
CITY (1508) A geographical region within a TERRITORY. Can also be a hamlet, village, township, etc. Example: Los Angeles, Dijon, etc.
COUNTRY (1509) A geo-political region with sovereign governing. Example: U.S.A., Canada, Denmark, etc.
COUNTY (1510) A geographic region within a TERRITORY. Example: Los Angeles County
DWELLING TYPE (1511) Identifies a type dwelling. example: single family, multi-family, etc.
ELECTRONIC ADDRESS (1512) A non-physical/virtual ADDRESS. Could be an e-mail, ftp, URL, etc. Example: clark@kryptonite.com, ftp.att.net/bob, etc.
ELECTRONIC ADDRESS TYPE (1513) Specifies the type of ELECTRONIC ADDRESS, such as e-mail, ftp, or url.
GEOGRAPHY ADDRESS (1514) A GEOGRAPHY ADDRESS can represent a physical mailing address, asset locations, and geographical boundaries.
LOCATION ADDRESS (1515) Describes how a specific combination of ADDRESS and LOCATION is used. Example: ‘123 Main Street’ is used by ‘Call Center 23’ as ‘Mail To’. ‘310-555-2342’ is used by ‘Call Center 46’ as ‘Customer Service Fax number’
MSA (1516) Note: MSA is but one of many Geographical Classification schemes that are used in Retail, and is shown only as an example. All classifications used by an actual client should be added to the model during an actual engagement. Metropolitan Statistical Area. Predefined geographic areas for marketing use, center around large metropolitan areas. Example: Miami MSA, San Francisco MSA, etc.
POSTAL CODE (1517) A grouping of MAIL ADDRESSes assigned by the Post Office. Frequently used in marketing analysis and planning. Example: USA: 90210, Canada: G1s 1C1 U.K.: W1P 7HE
TELEPHONE ADDRESS (1518) Telephone number. Could be voice, data, fax, pager.
TELEPHONE COMM TYPE XREF (1519) A cross reference of telephone numbers with the types of communications that can be directed to the telephone number (e.g. fax, voice, data).
TELEPHONE COMMUNICATION TYPE (1520) The types of communications that can be directed to a telephone number (e.g. fax, voice, data).
TERRITORY (1521) A geographic region within a COUNTRY. Can be a State, Province, etc. Example: California, Quebec, Gauteng, etc.
WORLD REGION (1522) The entity that indicates the WORLD REGION for a country. For example: APAC (Asia Pacific), EMEA (Europe Middle East Africa), etc.
The LOCATION Subject Area defines direct customer interaction points and the costs associated with them. This is required to determine direct customer CHANNEL interaction and its associated costs. The corporate organization structure regarding office hierarchy is also addressed in the DISTRICT, REGION and DIVISION entities. The client's organization hierarchy must be interpreted and implemented accordingly.
The LOCATION Subject Area also deals with the TRAVEL FACILITY associated with the product or service. For example, the TRAVEL FACILITY entity has sub-types dealing with the departure or arrival TRAVEL FACILITY depending on the mode of travel selected by the TRANSPORTED PASSENGER (such as BUS DEPOT, TRAIN STATION, SHIP PORT, or AIRPORT).
The entities of the LOCATION Subject Area, illustrated in
AIRLINE HUB (1601) This entity contains capacity statistics by airline for any major airport or airline center of operations (hub).
AIRPORT (1602) The domain of locations where Air Transportation occurs, Aircraft take-off and landings and where passengers board or de-board airplanes.
BUS DEPOT (1603) The domain of locations where Bus Transportation occurs, Example: Where Buses depart and arrive and passengers board or get off buses.
CALL CENTER (1604) A type of LOCATION of the enterprise. Typically where customer service support or customer reservation is provided.
CHANNEL (1605) The various CHANNELs in which the PRODUCTS or SERVICE's are sold. LOCATIONs (facilities) belong to 1 specific CHANNEL. A specific PRODUCT or SERVICE price may vary across CHANNELs. Example: Internet, Call Center, Over the Counter (In-Person Point of Sale.)
CITY TICKET OFFICE (1606) Airline ticket office located in any given city at a location other than the airport.
DISTRICT (1607) A grouping of LOCATIONs that fall within a specific geographic area. A DISTRICT is used to organize groups of LOCATION's for the purposes of planning, reporting and analysis.
DIVISION (1608) Represents an administrative grouping of REGIONs. DIVISIONs exist to further cluster PRODUCT's or SERVICE's into groups for administrative or organizational reporting purposes. A DIVISION often represents the highest LOCATION hierarchy level in an enterprise's organization. The actual naming convention for LOCATION hierarchy may vary across organizations.
KIOSK (1609) A physical device than can be used by INDIVIDUALs for self-service applications. Example: A Self Service device at the airport where customers can perform their own check-in and obtain a boarding pass.
KIOSK TYPE (1610) This entity describes the nature of the KIOSK Example: Enabling Web Access, Enabling Airport Check-In, etc.
LOCATION (1611) A physical or virtual site which is owned or leased by a business entity to support Sales and/or Services. Example: AIRPORT, CITY OFFICE, WEB STORE, etc
LOCATION OPERATING COST (1612) Denotes the planned and actual operating cost, for specific period by LOCATION.
LOCATION TRAIT (1613) A generic construct to describe characteristics of a LOCATION.
LOCATION TRAIT VALUE (1614) A cross-reference between TRAITs and LOCATIONs, describing the specific TRAITs that belongs to a LOCATION.
LOCATION TYPE (1615) Identifies the type of LOCATION. Example: KIOSK A finer level of differentiation can also be used: For example, located at a Mall, Stand Alone Center, rental office, etc
OPERATING COST (1616) Denotes the types of OPERATING COSTs for a LOCATION. Example: The expenditure items can include: Rent, Service Charge, Heat and Electricity, Distribution, Repairs, Facility Maintenance and Grounds, Equipment Maintenance, Security, Cleaning, Refuse, Communication—Telephone, Mail, FedEx, Bank Charges, Stationary and Supplies, Labor.
OPERATING COST TYPE (1617) Classifies the different OPERATING COSTs into logical groupings. Example: Utilities, office-related, maintenance, etc.
RAIL STATION (1618) The domain of locations where Rail Transportation occurs, i.e., where trains depart and arrive and passengers board or get off trains.
REGION (1619) An intermediate organization grouping level within the geographic hierarchy, which groups LOCATIONs. A specific regional geographic area of the country or county.
SHIP PORT (1620) The domain of locations where Ship Transportation occurs, i.e., where Ships depart and dock and passengers board or get off ships.
TRAVEL FACILITY (1621) The domain of locations where Transportation occurs, i.e., where buses, trains or airplanes depart and arrive and passengers board or get off them.
TRAVEL FACILITY GROUP (1622) A Grouping of TRAVEL FACILITIES for Marketing or Analytical purposes. Example:—can be used to group together all the airports that are part of the “NorthEast Market”, “Chicago Market”, etc.—can be used to group “all the Ports that are in the Caribbean Market” for a Cruise Ship Company.
TRAVEL FACILITY GROUP XREF (1623) Maps TRAVEL FACILITIES to TRAVEL FACILITY GROUPS. A TRAVEL FACILITY can be a member of multiple TRAVEL FACILITY GROUPs.
TRAVEL FACILITY LOCATION (1624) Business location where Transportation occurs. Example: Atlanta Hartsfield AIRPORT, NY Port Authority BUS STATION, etc.
TRAVEL FACILITY TYPE (1625) A type of TRAVEL FACILITY that may be used by a passenger. Example: BUS DEPOT, RAIL STATION, AIRPORT, etc.
WEB STORE (1626) A sub-type of LOCATION. Allows the enterprise to differentiate between their web-based activities. This entity is not meant to differentiate between physical web servers (IP Addresses)—it's more of a logical/business biased concept. Example: Frequent flyer Web Store, Travel Specials Web Store, etc.
The OnD PRODUCT PERFORMANCE Subject Area depicts what happens during a trip. This Subject Area closely relates to the PASSENGER EN-ROUTE Subject Area and shows what happens to a customer TRANSPORT VEHICLE once a BOARDING EVENT takes place and it leaves the departure point. Provisions have been made in this Subject Area to track various OnD PRODUCT incidents in case an irregular operation takes place for this specific OnD PRODUCT.
The entities of the OnD PRODUCT PERFORMANCE Subject Area, illustrated in
AIRLINE MARKET STATISTICS (1701) The summary information obtained from a third party concerning number of passengers flown in the specified market and average fares paid.
BOOKING CLASS (1702) A grouping of FARE BASIS codes for the purpose of accepting and controlling bookings in its reservations system. Ideally, the reservations system booking classes would have a one-to-one correspondence with the number of fare-basis codes (and price levels) on each flight, such that seat availability limits could be established for each price level. Most airline reservations systems, however, are limited in the number of bookings classes they use for any one flight, meaning that airlines must combine multiple fare-basis codes into one booking class. This problem is, of course, exacerbated by the fact that each flight also carries passengers from many different O&D markets, each with its own set of potentially different fare-basis codes.
CANCELLED (1703) A subtype entity of LEG INCIDENT entity detailing a scheduled leg that was cancelled.
DELAYED (1704) A subtype entity of LEG INCIDENT entity showing the total minutes a scheduled leg was delayed from its original schedule.
DISASTER (1705) This is a subtype entity of the LEG INCIDENT entity that describes an event that has negative results. Example: Plane Crash.
DIVERTED (1706) This is a subtype of the LEG INCIDENT entity that shows the new destination (diverted) travel facility for a LEG INCIDENT that was rerouted from its original destination.
EQUIPMENT SUBSTITUTION (1707) A subtype of the LEG INCIDENT entity that represents the equipment that was used to substitute for the scheduled equipment due to irregular operations.
FARE BASIS (1708) The domain for determining the basis that a fare will be computed on a specific travel segment/itinerary. The travel provider establishes different fare product categories, both to target specific demand segments and in response to competitive forces in the market. To do this, multiple fare-basis codes, or published fares, each with its own set of rules, effective dates, and price levels, all in the same O&D market are used. Thus, there could well be five or six different standard excursion fares in a city-pair market, differing in terms of day of week of travel, flight applicability, routing and price level. Fare-basis codes, which consist of up to eight characters and define a very specific fare product offering, but which are generally comprehensible only to the airline pricing department that uses them.
FLIGHT (1709) An aircraft carrying passengers, operated by an airline and traveling direct or non-stop from originating city to destination city.
FLIGHT PRODUCT (SEGMENT) (1710) An entity that defines a flight product between an origin and a destination that is available on a regularly scheduled basis. It will always consist of one or more contiguous LEGs within a given FLIGHT. Note: a FLIGHT PRODUCT is usually known as and referred to as a SEGMENT by airlines. Example: Penguin Airline's Flight 1101 from L.A. to N.Y.C. that departs in the morning.
INCIDENT REASON (1711) The reason description for an OnD PRODUCT INCIDENT. Example: EQUIPMENT SUBSTITUTION, DELAYED, CANCELLED, etc
INCIDENT TYPE (1712) The type code assigned to an OnD PRODUCT INCIDENT. Example: 1=Equipment substitution, 2=Delayed, 3=Cancelled, etc.
LEG BOOKING (HISTORY) (1713) The history of the actual bookings for a SERVICE CLASS of a SCHEDULED LEG as they were realized, a set number of days prior to departure. This would include information on bookings, seats booked, seats ticketed, deadweight seat count, etc. Note: The “(HISTORY)” suffix indicates that some of the attributes of this entity may be derivable in some instances by looking at the actual detailed passenger check-in information, while other attributes may only be sourcable from a Revenue Management System.
LEG FLOWN (SUMMARY) (1714) The summary information of the performance of an actual scheduled OnD LEG as it was realized, i.e. (flown) by the airline. Example: Penguin Airline's Flight 1101 from L.A. to N.Y.C. that departed on Tuesday, Jan. 23, 2001 at 10:00 am. Cost per ASM—17.3 cents, etc. Note: The “(SUMMARY)” suffix indicates that some of the attributes of this entity may be derivable in some instances by looking at the actual detailed passenger reservation and check-in information, while other attributes may only be sourcable from a Revenue Management System.
LEG INCIDENT (1715) This entity relates the incidents registered during a specified LEG. Example: DELAYED, CANCELED, etc.
OnD PRODUCT (1716) A distance based travel PRODUCT that is defined by Origination and Destination (O&D), weekday of departure and time of departure.
QUALITY OF SERVICE INDEX (1717) A Civil Aeronautics Board-era basis for determining the amount and quality (presumably from the public's perspective) of airline service in a market. For each carrier in the market, take the product of the factors for each flight by that carrier, add across all flights, compare to the sum of all carriers in the market and the fraction is then the carriers “QSI share” of the market, in terms of passengers or revenue. The Basics: QSI=f(frequency, service type, aircraft type, network presence, frequent flyer program dominance) Frequency=number of flights per day (for each carrier individually) Service Type factor=1.0 nonstop (for each flight), 0.7 one-stop, 0.6 single connection, 0.55 two-stop, 0.5 double connection. Aircraft type factor=1.0, widebody jet (for each flight), 0.85, narrowbody jet, 0.8 regional jet, 0.7 large turboprop, 0.6 small turboprop. Network presence factor=typically, a sliding scale of 1.5 to 0.5 depending on the number of markets served
ROUTE (1718) Indicates the series of TRAVEL FACILITYs visited by a FLIGHT. This information is technically derivable from the LEG information, but this entity allows for operations and relationships at a ROUTE level—for example we can indicate the Revenue Management Analyst responsible for the ROUTE. Example: A flight that takes of in Los Angeles, flies to Chicago, then takes off again and flies to New York would have a ROUTE of LAX-ORD-JFK
SCHEDULED LEG (1719) Details the date and time that a travel provider has scheduled to provide transportation. A LEG can be scheduled for multiple dates.
SCHEDULED SEGMENT (1720) Details the date and time that a travel provider has scheduled to provide transportation. A SEGMENT can be scheduled for multiple dates.
SCHEDULED SEGMENT LEG (1721) Exists to relate SCHEDULED SEGMENTs to SCHEDULED LEGs. Each SCHEDULED SEGMENT is made up of one or more SCHEDULED LEGs.
SEGMENT BOOKING (HISTORY) (1722) The history of the actual bookings for a BOOKING CLASS of a SCHEDULED SEGMENT as they were realized, a set number of days prior to departure. This would include information on bookings, seats booked, seats available, Waitlist, etc. Note: The “(HISTORY)” suffix indicates that some of the attributes of this entity may be derivable in some instances by looking at the actual detailed passenger check-in information, while other attributes may only be sourcable from a Revenue Management System.
SEGMENT FLOWN (SUMMARY) (1723) The summary information of the performance of an actual scheduled OnD SEGMENT as it was realized, i.e. (flown) by the airline. Example: Penguin Airline's Flight 1101 from L.A. to N.Y.C. that departed on Tuesday, Jan. 23, 2001 at 10:00 am. Note: The “(SUMMARY)” suffix indicates that some of the attributes of this entity may be derivable in some instances by looking at the actual detailed passenger reservation and check-in information, while other attributes may only be sourcable from a Revenue Management System.
SERVICE CLASS (1724) The type of service requested by the passenger. Example: AIRCRAFT—First Class, Business Class, Economy Class; LODGING PROPERTY—Deluxe Room, Suite; CRUISE LINE—Steerage; RENTAL VEHICLE—Full Size, Intermediate, etc.
TRANSPORTED PASSENGER (1725) Every entry in this entity represents an actual passenger that was transported exactly one LEG. Example: On a LAX/ORD/JFK flight for a passenger flying from LAX to JFK there will be two entries.
TURN BACK (1726) Indicates a LEG INCIDENT describing a turn back and return to its Originating TRAVEL FACILITY because of some irregular operation
YIELD LEVEL (1727) The level of revenue attained from sale of seats for a flight when compared to the maximum revenue that could be obtained by selling each seat for its maximum value.
The PARTY Subject Area, illustrated in
The entities of the PARTY Subject Area are defined as follows:
AIRLINE (1801) The domain of Air Transportation Carriers as listed with the Department of Transportation (DOT) and the International Air Transport Authority (IATA).
ASSOCIATE (1802) An individual who is employed by the ORGANIZATION.
BUS ORGANIZATION (1803) This entity reflects the domain of Bus Transportation Carriers as listed with the Department of Transportation (DOT) and the International Association of Public Transport.
BUSINESS (1804) A formal organization that is a legal entity (e.g. has a tax status with the government) consisting of one or more individuals formed for the purpose of conducting business or providing a service. This entity is a subtype to ORGANIZATION.
BUSINESS LEGAL CLASSIFICATION (1805) The domain of codes used in the legal classification of the businesses. Examples are: Inc=Incorporated, Ltd=Limited.
BUSINESS NAICS (1806) The association of a business to one or more North American Industry Classification (NAICS) codes.
BUSINESS SIC (1807) The association of a business to one or more standard industry classification (SIC) codes. A business may have multiple SIC codes with one primary classification.
CAR RENTAL ORGANIZATION (1808) This entity reflects the domain of Car Rental Agencies for both US and International locations.
CONTRACT (1809) The agreement between the Customer and an enterprise CONTRACT TERM (1810) The terms of a contract. Examples include Volume discounts, Negotiated Rates, Due Dates, etc.
CONTRACT TERM CATEGORY (1811) The domain of terms that can be used in setting up a contract.
CONTRACT TYPE (1812) This entity is a discriminator for the categories of a contract.
CREATION SOURCE TYPE (1813) An indication of how/where the first information about the existence of a Party was obtained. Examples: PL—Purchased Prospect List, WB—Web Site, CC—Customer Care Center CM—Campaign Reply, etc
CRUISE LINE (1814) This entity reflects the domain of Shipboard Passenger Carriers as listed with the Department of Transportation (DOT) and the International Maritime Organization.
CUSTOMER PREFERENCE (1815) The detailed information collected about individual customer preferences. Example: Customer seating preferences, Customer preferred international and domestic destinations, Customer preferred reading material, Customer preferred on board drinks, etc.
DUNS (1816) Dun & Bradstreet information pertaining to a particular business.
ETHNICITY (1817) The ethnicity of an individual. Example: Latino, Caucasian, African American, etc.
GDS PROVIDER (1818) This entity is the domain of booking systems used by the airline industry to make airline flight reservations. Examples: SABRE, WORLDSPAN, AMADEUS, etc.
GENDER TYPE (1819) This minor entity represents the gender that an individual can have.
HOUSEHOLD (1820) This is a subtype entity to PARTY. A household is a grouping of individuals created for marketing purposes. The individuals typically live at the same address and have biological ties.
INDIVIDUAL (1821) This is a subtype entity to PARTY. This entity consists of those people that are of interest to the enterprise.
INDIVIDUAL NAME (HISTORY) (1822) This entity tracks an individual's name over time. This entity keeps track of current and prior names.
INDIVIDUAL TYPE (1823) Indicates the subtype (if applicable) of this individual. Example: Associate.
INTERNAL ORGANIZATION (1824) This is a subtype to ORGANIZATION. It is an organization that is internal to an enterprise such as a department or subsidiary.
INTERNAL ORGANIZATION TYPE (1825) The sub-type discriminator for an internal organization. This minor entity identifies the type of internal organization. Examples of internal organization types include departments or divisions.
LODGING ORGANIZATION (1826) This entity reflects the domain of Lodging and Hotel owners as listed with the American Hotel and Lodging Association and its international counterparts.
NAICS (1827) The North American Industry Classification System. NAICS was developed jointly by the U.S., Canada, and Mexico to provide new comparability in statistics about business activity across North America.
NAME TYPE (1828) This minor entity identifies the different types of names that an individual or organization could have such as ‘doing business as’ (dba), legal name, alias, phonetics, etc.
ORG BUSINESS TYPE (1829) This entity classifies organizations into types. For businesses examples can be hospital, inpatient hospital, outpatient clinic, gas station, retail store, travel agency. For internal organizations the business types could be marketing, financial, sales etc.
ORG ORG BUSINESS TYPE (1830) This entity relates an organization to organization business types. For businesses examples can be hospital, inpatient hospital, outpatient clinic, gas station, travel agency. For internal organizations the business types could be marketing, financial, sales etc.
ORGANIZATION (1831) This is a subtype entity to PARTY. An organization is any group of individuals (or one individual) or other organizations formed for a purpose. Examples are internal organization and businesses. This definition does not include groups of individuals that form a segment.
ORGANIZATION NAME (HISTORY) (1832) This entity keeps track of organization name changes over time. It keeps the current and prior names.
ORGANIZATION TYPE (1833) The sub-type discriminator for an organization. This minor entity identifies the type of organization. Examples of organization types include businesses or internal organizations.
PARTNER PARTY (1834) The domain of companies or enterprises that can participate in Rewards programs by granting earnings externally to the company that manages the Reward Account.
PARTY (1835) A party is any individual, organization or household that is of interest to the enterprise.
PARTY ADDRESS (1836) Describes how a specific combination of ADDRESS and PARTY is used. This tends to be the ‘default/primary’ usage, thus only one address per usage is allowed. It can also be used to indicate the address to use for marketing to a customer. Example: ‘123 Main Street’ is used by ‘Rachel’ as ‘Ship To’ ‘23 Abbey Rd’ should be used to market to R. Starr ‘310-555-2342’ is used by ‘John’ as ‘Fax number’.
PARTY ADDRESS (HISTORY) (1837) This entity relates parties to addresses and tracks changes over time. A party can have many addresses and an address can be used by many parties.
PARTY IDENTIFICATION (1838) The numbers that may be assigned to a party by a legal jurisdiction for identification purposes, as specified by PARTY IDENTIFICATION TYPE. Example: Social Security Number, Passport Identification, Driver's License, Federal Tax Identification Number, National Identity Card Number, Etc.
PARTY IDENTIFICATION TYPE (1839) The types of legal jurisdiction identification that may be used by a party. Example: Social Security Number, Passport Identification, Driver's License, Federal Tax Identification Number, National Identity Card Number, Etc.
PARTY LOGIN (1840) This entity represents the login information of a PARTY. This entity supports tracking of a PARTY's login names for multiple web sites
PARTY PARTY RELATIONSHIP (HISTORY) (1841) This entity defines the relationships between parties—individual and individual; individual and organization; organization and organization; individual and household and household and household relationships. A party can be part of many relationships. A party can have many types of relationships with another party. Examples of relationships could be employee-employer, spouse, household-member, father-son, supplier, or competitor.
PARTY REL STATUS REASON (1842) A reason why a particular Party Status Type Cd may be assigned to a party relationship.
PARTY REL STATUS TYPE (1843) The domain of classifications tracked to the relationship role for a Party. Examples: A—Active, I—Inactive, P—Prospective U=Unmarketable Customer (i.e. deceased).
PARTY SCORE (1844) A relative value, or ‘score’ produced by an ANALYTICAL MODEL after reviewing business information. This can provide a measure or way to group and treat PARTYs that the business interacts with. Example: Customers can be ‘scored’ for profitability, frequency of purchases, propensity to buy, etc. Vendors and suppliers can similarly be ‘scored’ PARTY TRIP FEEDBACK (1845) Feedback from a PARTY regarding an event which took place during a TRIP.
PARTY TYPE (1846) The sub-type discriminator for a party. Valid sub-type occurrences are INDIVIDUAL, ORGANIZATION and HOUSEHOLD.
PASSENGER TRAVEL PROVIDER (1847) This entity reflects the domain of PASSENGER TRAVEL PROVIDERs. Example: AIRLINE, RAILROAD, CRUISE LINE, etc.
PASSENGER TRAVEL TYPE (1848) Identifies the type of PASSENGER TRAVEL PROVIDER
PERSONA (1849) The ‘role’ an INDIVIDUAL is playing while interacting with the enterprise. Typically in association with an ORGANIZATION. Example: Two different PERSONAe of Jill may be: Jill is ordering ITEMs in her capacity as ‘owner’ of ‘Jill's Dog Grooming Co.’, or Jill is calling about a problem with an order in her capacity as ‘buyer’ for AT&T.
PREFERENCE (1850) The domain of preferences used to identify personal customer preferences.
PREFERENCE GROUP (1851) The domain of groups used to collect customer preference information about a customer.
PREFERENCE VALUE (1852) The specific customer preferences that make up the CUSTOMER PREFERENCE entity.
RAILROAD (1853) This entity reflects the domain of Rail Transportation Providers as listed with the International Rail Association of Public Transport.
SIC (1854) A Standard Industry Classification is a statistical classification standard describing all establishments. It categorizes businesses by the type of business in which each they are engaged. Businesses engaged in the same activity, regardless of size or type of ownership are given the same SIC code. In the United States the SIC is maintained by the Office of Management and Budget, Executive Office of the President.
TRAVEL AGENCY (1855) Identifies each non-travel provider business used to arrange and make travel reservations, sell tickets, and distribute tickets to the designated passenger or designee.
TRAVEL PROVIDER (1856) The ORGANIZATION PARTY that supplies various types of travel and transportation PRODUCTs.
TRAVEL PROVIDER TYPE (1857) A type of TRAVEL PROVIDER that describes the kind of travel being provided. Example: PASSENGER TRAVEL PROVIDER, CAR RENTAL ORGANIZATION, LODGING ORGANIZATION.
The PASSENGER EN-ROUTE Subject Area, illustrated in
The entities of the PASSENGER EN-ROUTE Subject Area are defined as follows:
BAGGAGE CHECK (1901) The entity that reflects the act of placing baggage in the care of the transportation provider to transport in a separate baggage compartment at the time of CHECK-IN
BOARDING DENIED (1902) The entity that reflects the act of denying boarding to a passenger by a travel provider at the time of CHECK-IN
BOARDING EVENT (1903) The entity that reflects the customer's act of boarding an aircraft for a specific FLIGHT SEGMENT. It follows a CHECK-IN EVENT and requires a boarding coupon. The boarding coupon contains class and seating information as well as the flight and departure information.
CHECK-IN EVENT (1904) The event when a passenger holding a TRAVEL COUPON checks in at the curb, airline or gate counter to let the airline know they are ready to travel on the scheduled flight.
CONTACT TYPE (1905) The domain of types of contact events deemed valuable enough to be retained for the life of a customer. Event types include complaints, compliments, cancellations, etc.
DENIED REASON (1906) The reason that boarding was denied to a ticketed passenger.
EVENT REASON (1907) This entity represents the domain of reasons given by the customer for the occurrence of the event. Example: Moving, Loss of service, Need Information, etc.
EVENT RESOLUTION TYPE (1908) The resolution or outcome of the customer event.
PARTY CONTACT EVENT (1909) All points of contact with each customer.
PARTY TRAN ROLE (1910) Indicates the PARTY involved in the TRANSACTION, and their ROLE. Example: for RESERVATIONS: the “taking reservation” PARTY; for PURCHASES: the “selling” PARTY, the “ticket issuing” PARTY, etc.
PURCHASE ITEM (1911) The specific items PURCHASEd as part of a TRAVEL TRANSACTION.
REQUEST TYPE (1912) The domain of special requests for the passenger Example: Special meal, Wheel chair, or Language help.
SPECIAL REQUEST (1913) Any special request made by the passenger for that travel segment, such as a special meal or wheel chair assistance. The request may be made at anytime in the Airline booking, ticketing, check-in or boarding process.
TICKET (1914) The entity that represents the actual coupon used to claim reserved service. Can be physical coupon or electronic version of same.
TRAVEL COUPON (1915) A single boarding leg of a TICKETed Itinerary for one passenger for one contiguous period of travel.
TRIP (1916) A Group of related TRAVEL TRANSACTIONs. Usually related to a specific ‘Journey’ made for a specific purpose. Example: A return flight to Hawaii plus a rental car reservation plus a hotel reservation.
TRIP EVENT (1917) The actual event(s) which happen during a TRIP. Example: CHECK-IN EVENT, BAGGAGE CHECK, BOARDING EVENT.
TRIPEVENT TYPE (1918) The type of a TRIP EVENT
The PNR OPERATIONS Subject Area deals with the capture of Passenger Name Record (PNR) data. This subject area maps the actual PNR data captured as part of PNR decode and allows the image of the PNR to be stored in the warehouse for later evaluation and display. Detail PNR data is used in the Revenue Management area and can be used by customer service to access PNR data for PNRs that have been deleted from the Reservations system. The bulk of the “decoded” PNR (Passenger Reservation) information is provided in a clear, relational form in the Subject Areas dealing with RESERVATIONs and PURCHASEs. This Subject Area is provided to satisfy customer requests to provide the ability to mine the “raw” source PNR data after it has been purged from the Reservation system. This will allow the retrieval of previously non-decoded information if needed.
The entities of the PNR OPERATIONS Subject Area, illustrated in
PNR BOOKING (2002) Portion of PNR that contains the source booking information.
PNR FARE (2003) Portion of PNR that contains the source fare information.
PNR MISCELLANEOUS (2004)
PNR PAYMENT (2005) Portion of PNR that contains the source payment information.
PNR REMARK (2006) Portion of PNR that contains the source remarks information.
The Privacy Subject Area deals with the aspect of consumer privacy and a consumer's ability to “opt-in” or “opt-out” of having various personal data collected and used. This enables a consumer to “opt-out” of disclosure to third parties. Opt-out selections may include:
The implications of these requirements on data mining, data warehousing, and in particular database marketing, are determined by the travel provider in accordance with local rules and regulations concerning data privacy.
The entities of the PRIVACY Subject Area, illustrated in
PARTY PRIVACY (2101) A Customer's privacy preferences for the collection and use of personal data. The Privacy Information Type and Privacy Consent Type combine to indicate the category of data and consent for which the Option Indicator applies.
PRIVACY (HISTORY) (2102) A history of a customer's privacy preferences for the collection and use of personal data. The Privacy Information Type and Privacy Consent Type combine to indicate the category of data and consent for which the Option Indicator applies.
PRIVACY CONSENT TYPE (2103) The domain of values for preferred interaction methods or permitted disclosure of personal information. Examples: Direct Marketing, Third-Party Disclosure, Affiliate Disclosure.
PRIVACY INFORMATION CATEGORY (2104) The domain of values for the Categories of Privacy Data that the Customer can implicitly or explicitly opt in or out of. Example Categories are: ALL—referring to all categories of private data, NAME—referring to a Customer's name information, ADDRESS—referring to a Customer's Address information, PHONE—referring to a Customer's Phone information, DEMOGRAPHIC—referring to a Customer's Demographic information, ONLINE_CONTACT—referring to a Customer's contact information via email or web, INTERACTION DATA—referring to a Customer's web interactions, FINANCIAL ACCOUNT—referring to a Customer's Financial information, NAVIGATION DATA—referring to a Customer's navigation data over the web or call center, EMPLOYER—referring to a Customer's Employer information.
PRIVACY INFORMATION TYPE (2105) The domain of values describing personal information that the Customer can implicitly or explicitly permit or reject. Examples are: Name Type, Address Types, Phone Types, Demographic Type, Employer Type.
The PRODUCT Subject Area, illustrated in
The entities of the PRODUCT Subject Area are defined as follows:
BUS PRODUCT (2201) All of the published city markets providing bus transportation services by Bus Organization.
CODE SHARE BASIS (2202) Identifies the business agreement regarding fares for a codeshare flight. A codeshare is an association between one airline's scheduled flight and another airline's representation of the same flight, using different flight numbers, codeshare partnerships and agreements; where codeshare means either airline can sell and issue tickets on it's own company ticket stock.
CRUISE PRODUCT (2203) All of the published destinations and ports of call provided for sale by a particular CRUISE LINE.
FLIGHT CODESHARE (2204) This entity is an association between one airline's scheduled flight and another airline's representation of the same flight, using different flight numbers, codeshare partnerships and agreements; where codeshare means either airline can sell and issue tickets on it's own company ticket stock.
LEG (2205) This entity represents the basic building block of a single Origin and Destination pair that represents travel with no intermediate stops. Example: For an Air it would be one take off and one landing, for Rail it would be travel between two consecutive station stops.
LODGING PRODUCT (2206) The entity that represents the domain of available lodging options for a customer for the purpose of obtaining temporary lodging for a specified period of time at a predetermined rate.
NON TRAVEL PRODUCT (2207) A PRODUCT offered that does not include travel. Example: Model Planes, Coffee Mugs, Logo Clothing, etc.
OnD PAIR (2208) A pair of locations where Transportation occurs, i.e., where buses, trains or airplanes depart and arrive and passengers board or get off them.
OnD PRODUCT TYPE (2209) Identifies the type of OnD PRODUCT OnD TIMETABLE (2210) The domain of published O&D schedules for a future time period. These contain O&D, date and time for each OnD PRODUCT scheduled for operation. Example: a LA to New York flight schedule may be published for 1 year into the future
PRODUCT (2211) A travel offer or item available for sale to a PARTY(s). Examples: Fly LAX-SFO morning flight, Ocean view Miami Hotel room, Jacket with Airline logo.
PRODUCT TYPE (2212) A type of PRODUCT that describes the kind being purchased. Example: OnD PRODUCT, RENTAL PRODUCT, LODGING PROPERTY, etc.
RAIL PRODUCT (2213) All of the published O&D destinations provided for sale by a particular RAILROAD.
RENTAL PRODUCT (2214) A domain of rental vehicles that customers can rent for temporary use.
ROUTE GROUP (2215) A Way to group related ROUTEs together. Note that ROUTE GROUP can also contain ROUTE GROUPs, thus creating a hierarchy. Example: all “Trans Atlantic” routes can be collected into a ROUTE GROUP, than can then again be part of a larger “International” ROUTE GROUP.
ROUTE TYPE (2216) This identifies a ROUTE TYPE, i.e. “short haul” or “long haul”
SEGMENT LEG (2217) This entity cross references the LEGs (basic building blocks) that make up an OnD PRODUCT. An OnD PRODUCT can consist of one or more LEGs. Example: LA-NY product can consist of a LA-Chicago product plus a Chicago-NY product.
WEEK DAY (2218) The domain of each day of the week that represents MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, & SUNDAY.
The PROMOTION Subject Area contains information about the various travel promotion opportunities that travel companies make available to their customers. Each promotion has one or more corresponding OFFERs that feature everything from non-travel merchandise to trips and trip upgrades and awards. Often these are used in conjunction with specific CRM (Customer Relationship Management) offers to highly targeted SEGMENTs of their customer base.
The entities of the PROMOTION Subject Area, illustrated in
AD (2301) A marketing message aimed at a segment of consumers. Usually mentions specific products or services. Can be placed in magazines, on web pages, television, etc.
AD COMPONENT (2302) An associative entity that tracks MULTIMEDIA COMPONENTs involved in the creation of an AD
AD PRODUCT (2303) An AD defined for specific product area.
AD TYPE (2304) Indicates the subtype of the AD. Example: Radio, TV, Web, etc.
CAMPAIGN (2305) A marketing effort with a specific start and end date. Typically a large effort, that can consist of multiple PROMOTIONs. The goal of a CAMPAIGN is usually to enhance the image of the enterprise, and/or drive more business and/or obtain more customers Example: American Airlines launches a 3-month CAMPAIGN to build brand awareness. They create several consumer oriented PROMOTIONs and TV ADs to support the CAMPAIGN.
COUPON (2306) An internal type of OFFER. It needs to be shown or ‘redeemed’ (physically or virtually) to receive the mentioned incentive. Can be serialized to track individual instances. Example: A printed offer that can be cut out and shown to a travel agent, or an insert in the Sunday Paper, or a code e-mailed to an INDIVIDUAL.
COUPON CERTIFICATE (2307) A specific instance of a COUPON that is trackable through a unique number. The intent is to provide targeted INDIVIDUALs with trackable COUPONs to be able to identify the customer at redemption time (even if the redemption transaction is cash) Example: A direct mail piece with a specific OFFER, containing a barcode with a unique code, or an individualized e-mail code.
DIRECT MAIL OFFER (2308) An OFFER that is sent through the postal service
EMAIL AD (2309) An AD that can be delivered to a consumer via e-mail.
EMAIL OFFER (2310) An OFFER that is sent via email
INCENTED SEGMENT (2311) A mapping of a group of SEGMENTs to a specific OFFER. An OFFER can be made to more than one SEGMENT. Example: All customers whose travel went down over 50% over the last 6 months are offered 10% off the next time they travel.
MULTIMEDIA COMPONENT (2312) MULTIMEDIA COMPONENT refers to various multimedia elements that can be use to construct a WEB PAGE, AD, catalog, etc. Example: Image files, urls, html pages, etc.
NON TRAVEL OFFER (2313) An OFFER that provides an incentive to a customer, that does not include travel. Example: flight bags, golf balls, etc.
OFFER TYPE (2314) Indicates the subtype of the OFFER. Example: TRAVEL OFFER, EMAIL OFFER, etc.
PRINT AD (2315) An ad in a newspaper or a magazine. Additional sub-types of ADs can be created as needed—for instance: BILLBOARD AD, RADIO AD, etc.
PROMOTION (2316) A narrowly defined marketing effort designed for a specific purpose. Can be part of a larger CAMPAIGN. It has a specific start and end date. A PROMOTION can contain multiple OFFERS and ADs. Example: A PROMOTION is created to drive Delta's Atlanta to Salt lake service during December 2001. It consists of 2 OFFERS (one for free airport limousine service, and one for 10% off flights booked in October 2001) AND 2 ADs: a TV AD and a BANNER AD placed on selected websites.
TRAVEL OFFER (2317) An OFFER involving a specific market (O&D pair) or product (O&D pair on a given day and time) usually during a specific time period. Example: Product: Fly LAX-SFO, Monday through Thursday, during January 2002 and get 10% off. Market: Fly LAX-ATL during December 2001 and get a companion ticket for 50% off.
TRAVEL OFFER XREF (2318) A mapping of which products/markets are involved in a specific OFFER. A product/market can participate in an OFFER in 2 ways: a.) you have to travel to receive an incentive (fly to Alaska to receive . . . ) and/or b.) forms part of the incentive (get a ticket to SFO for 50%) NOTE: Attributes can be added to spell out the exact details of the market/product/OFFER relationship.
TV AD (2319) An AD designed to be shown on television. Usually 30 seconds in length.
WEB AD (2320) A marketing message targeted for specific set of consumers on a web page Example: ‘Fly AMERICAN banner ad’ on www.yahoo.com
WEB AD TYPE (2321) A classification scheme used to organize WEB ADs. The classification can be used to provide summary information about the performance of various WEB ADs. For example—premium banner ad, discounted banner ad, keyword related banner ad. It could also provide information about whether the ad is static or dynamic (for example—general rotation) OR specify if it is a brand awareness ad versus an information ad
WEB BANNER AD (2322) Marketing messages containing a mix of images and text that is usually hosted by a third party ORGANIZATION on a WEB PAGE. Example: A Fly AeroMexico ad with an AeroMexico logo that links to its web site.
WEB TEXT AD (2323) Marketing messages using text descriptions intended for placement on a WEB PAGE. Example: A text message saying ‘Fly Lufthansa’ that is linked to its web site.
The PURCHASE Subject Area, illustrated in
The entities of the PURCHASE Subject Area are defined as follows:
AIRLINE TICKET (2401) This entity represents the Ticket issued to a passenger for the purpose of boarding a Revenue Flight between cities.
BUS TICKET (2402) This entity represents the Ticket issued to a passenger for the purpose of boarding.
CASH (2403) A sub-type of payment that records information when cash is used.
CERTIFICATE (2404) This entity is a sub-type of payment and represents a method of payment for the acquisition of a Ticket.
CERTIFICATE TYPE (2405) The domain for the types of redemption certificates used to purchase a Ticket such as when a flight is overbooked and you give up your confirmed seat in lieu of a Free Ticket. Example: Mileage Redemption, Free Ticket,etc CHARGE TYPE (2406) A type of charge or quote component for a PRODUCT. Example: Transfer Fee, Landing Tax, Airline Fare, Meal ticket, surcharge for bringing a pet, etc.
CRUISE LINE TICKET (2407) This entity represents the Ticket issued to a passenger for the purpose of boarding a specified cruise ship in order to sail to a specified destination.
FREE CERTIFICATE (2408) A sub-type of CERTIFICATE that identifies a certificate issued by an airline to be used to receive a free airline ticket. Example: Certificate for free round trip to any U.S. City awarded to a passenger who was bumped from a flight.
ITEM CHARGES (2409) Specifies the component amounts that make up the total price charged for a PRODUCT. Example: Transfer Fee, Landing Tax, Airline Fare, Meal ticket, etc.
NON REVENUE (2410) A subtype of CERTIFICATE that describes the travel vouchers associated with ASSOCIATE travel for the airline. This may include company and non-company business.
PARTY STATUS (2411) An overall classification status for a PARTY. Example:—inactive—do not do business with etc.
PAYMENT (2412) The methods by which a Ticket is purchased and paid for as well as tracking changes and reimbursements/refunds.
PAYMENT TYPE (2413) The domain of Payment Methods used to transact the purchase of a Ticket. Example: Cash, Credit Card, Airline Ticket Coupons, Corporate Air Travel Pass, etc
PURCHASE (2414) A sub-type of the TRAVEL TRANSACTION entity that represents the Item(s) or Service(s) bought and paid for by the PARTY.
RAILROAD TICKET (2415) This entity represents the Ticket issued to a passenger for the purpose of boarding a passenger train between City Markets.
RETURN ITEM (2416) A specific PURCHASE ITEM returned by the PARTY.
RETURN REASON (2417) The reason code associated with a RETURNed ITEM. Example: Business Trip Cancelled, Changed Mind, Illness, etc.
TICKET AWARD CERTIFICATE (2418) A sub-type of CERTIFICATE that contains information about a certificate received as a result of redeemed mileage from a frequent traveler account.
TICKET FORMAT (2419) This entity is the domain of values used to discriminate different Ticket types. Examples: ATB2(a magnetic strip ticket that is issued by IATA), E-Ticket and Manual.
TICKET PAYMENT (2420) The methods by which a TICKET is purchased and paid for as well as tracking changes and reimbursements/refunds.
TICKET TYPE (2421) A sub-type of TICKET that contains information about the type of TICKET purchased. Example: BUS TICKET, CRUISE LINE TICKET, AIRLINE TICKET, etc.
TRAVEL PASS (2422) A sub-type of Ticket Purchase that records information when a Travel Pass is used.
TRAVEL TRANSACTION (2423) An entity which represents a travel transaction which can contain the RESERVATION and PURCHASE of travel PRODUCTs. Our current convention is to create a new transaction for each TRIP.
The RESERVATION Subject Area, illustrated in
entities of the RESERVATION Subject Area are defined as follows:
AIRLINE RESERVATION (2501) This entity represents the intention (reservation) made by a passenger to purchase an airline ticket for the purpose of boarding a Revenue Flight between City Markets.
CAR RENTAL RESERVATION (2502) This entity represents the intention (reservation) made by a customer to rent a passenger vehicle or truck for a specified period in a designated market.
CRUISE LINE RESERVATION (2503) This entity represents the intention (reservation) made by a passenger to purchase a cruise for the purpose of boarding a ship and sailing to a specified destination.
LODGING RESERVATION (2504) This entity represents the intention (reservation) made by a customer to make a visit to a HOTEL for the purpose of obtaining temporary lodging for a specified period of time at a predetermined rate.
PARTYRELATIONSHIP ROLE (2505) Indicates the relationship of one party to another party Examples: Manager, Employer, Employee, Campaign Vendor, Customer, Reseller, Dealer, Product Manager, Account Executive.
QUOTED CHARGE (2506) Shows the various PRODUCT or fare component amounts that make up a quote that was given during a RESERVATION. Example: Breaks down the total fare into it's components: Transfer Fee, Landing Tax, Airline Fare, Meal ticket, etc.
RAILROAD RESERVATION (2507) This entity represents the intention (reservation) made by a passenger to purchase a railroad ticket for the purpose of boarding a passenger train between City Markets.
RESERVATION (2508) The sub-type of the TRAVEL TRANSACTION entity that represents the domain of requests for a specific itinerary associated with a TRAVEL TRANSACTION. Examples: Hotel Reservation, Airline Reservation, Rental Car Reservation.
RESERVATION ITEM (2509) The specific items reserved as part of a TRAVEL TRANSACTION.
RESERVATION ITEM TYPE (2510) Identifies the type of RESERVATION ITEM. Examples: Car Rental, Lodging, Air, etc.
RESERVATION PREFERENCE (2511) Ties the CUSTOMER PREFERENCEs as stored in their personal profile to a specific RESERVATION.
RESERVATION STATUS (2512) The domain of status types for a specific itinerary item associated with booked RESERVATIONs. Status conditions include: Open, Closed, Cancelled.
VISIT (2513) A period of time that a PERSONA spends at a LOCATION. Example: Rachel visited our web site today from 12:32 through 13:47. John spent 17 minutes today on the phone with our CALL CENTER, making reservations.
This Subject Area represents the actual transaction with the customer for a travel package or service. Within the subject area, a VISIT reflects a customer's interaction with the TRAVEL PROVIDER. It can reflect a web site visit, a call to a Reservation Center, or a physical visit to a City Ticket Office or Airport Ticket Office. The PARTY TRAN ROLE is introduced to identify a PARTYs role in the transaction. This could be the person making the reservation, the travel agent they are using, the party paying for the trip, or the person(s) taking the trip.
The entities of the TRAVEL TRANSACTION Subject Area, illustrated in
BROWSE (2601) A type of TRAVEL TRANSACTION that captures what PRODUCTs have been looked at but not reserved or purchased.
BROWSE ITEM (2602) The specific items viewed as part of a BROWSE session by a customer.
REASON (2603) This entity indicates the reason why two (or more) TRAVEL TRANSACTIONs are related. Examples: a reservation gets cancelled and replaced by a different reservation, a browsing transaction results in a reservation and or an issued ticket, etc.
TRAVEL TRANSACTION TYPE (2604) Identifies the type of TRAVEL TRANSACTION. Example: Browse, Reservation, Purchase.
TRAVEL TRANSACTION XREF (2605) Cross reference entity to allow TRAVEL TRANSACTION to be related to each other. This can be used to related similar transactions (several RESERVATION transactions) or different transactions (relating RESERVATIONs to PURCHASEs, etc.)
The entities included within the WEB OPERATIONS Subject Area are defined as follows:
CRAWLER (2701) Contains a list of Crawler sites that have visited the Web Site of the business entity. A Crawler is a program search engine that takes information from a Web Site.
CRAWLER PERMISSION TYPE (2702) Codes used to specify the type of permission that a Crawler is allowed when accessing a Web Site or Web Page.
CRAWLER WEB PAGE PERMISSION (2703) The access rights granted to a Crawler for a specified Web Page.
CRAWLER WEB SITE PERMISSION (2704) The access rights granted to a Crawler for a specified Web Site.
FILE (2705) Represents an electronic file (song.mp3, document. pdf, etc.)
In data processing, a related collection of records. For example, the records on each of your customers could be placed in a file. In turn, each record would consist of fields for individual data items, such as customer name, customer number, customer address, and so forth.
FILE DOWNLOAD (2706) Tracks information on Files that were downloaded from a Web Site. For example, an MP3 site would keep records on what songs were downloaded.
FILE TYPE (2707) Information stored on the types of Files, usually broken down by extension. Examples are “.mp3”,“.exe”, and “.pdf”. Alternatively, files could be associated with known file types such as MP3 file, application, or Adobe Acrobat document.
HTML COMPRESSION TYPE (2708) The type of compression that may be applied to an HTML Response File.
HTML RESPONSE FILE (2709) The actual HTML file that is returned to the user as a result of a click. It is possible that the HTML returned could be larger than the maximum size allowed for a single row in Teradata, in that case this entity could not be used as is to store that information. The HTML Response File table was added to support interface with a web site replay product from TeaLeaf. They capture a visitor's session and provide the capability of replaying the session. They do it by building a blob (large data block) and storing it in the database.
TIME ZONE (2710) The time zone for particular locations around the world. Data may be simple or complex. Often only an offset from Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT) is recorded. Los Angeles' time zone would thus be shown as GMT-0700 (Greenwich Mean Time minus 7 hours). Honolulu, Hi. as GMT-1000 (minus 10 hours). Indicators for usage of Standard or Daylight time (along with other appropriate attributes such as City and State for the U.S) and data for Longitude and Latitude may also be added to this entity if, and as, needed.
WEB GROUP PUBLISHER (2711) A cross reference of the actual PUBLISHERs contained in a specific WEB SITE GROUP.
WEB PAGE GENERATION TYPE (2712) This entity is used to classify the method involved in generating a web page. Example: Static versus dynamic page
WEB SERVER (2713) Provides summary information about the physical server devices servicing a WEB VISIT.
WEB SERVER ACTIVITY (2714) Provides operational metrics for Web Server.
WEB SERVER ERROR (2715) An entity used to provide information about WEB SERVER errors
WEB SERVER SOFTWARE (2716) Captures information about the software being utilized by the Web Server. (Apache, IIS, etc)
WEB SITE CRAWLER (HISTORY) (2717) A history of the Web Sites that have been accessed by specified Crawlers.
WEB SITE GROUP (2718) This entity groups web sites into classifications such as a Computer and Technology web site, Cooking web site, Astronomy web site, etc. A web site can be in many groups and a group contains many web sites. Also known as Network. One example of a group is a group of Publisher sites that an Ad or Campaign is run on. Ad Networks commonly have predefined Networks that Advertisers can choose to run their ads on. Examples include a Computers & Technology Network that would include all of the Computer & Technology related sites the Ad Network has space on or a Sports Network that includes all of the Sports related sites the Ad Network has.
WEB SITE GROUP XREF (2719) This entity groups web sites into classifications such as a Computer and Technology web site, Cooking web site, Astronomy web site, etc. A web site can be in many groups and a group contains many web sites.
WEB SITE SERVER (2720) Associates the Web Sites that are supported by a Web Server.
WEB VISIT FILE (2721) This associative table stores all the Files downloaded during a Web Visit.
The WEB SITE Subject Area models the specifics about a travel provider's web site. It contains information about WEB PAGEs (PAGE COMPONENTs and WEB ADs), and information about WEB AD PLACEMENT.
The entities of the WEB SITE Subject Area, illustrated in
CONTEXT (2801) Contains the business intent represented by web pages.
E LOCATION (2802) An entity used to describe an internet location within an E SITE. Example: the/clothing/women's section in a proprietary system (such as AOL) or shopping.yahoo.com/Computers (on yahoo)
E LOCATION TYPE (2803) An entity used to classify E LOCATIONs. This is similar to the WEB PAGE TYPE entity that classifies WEB PAGEs, the only difference being that WEB PAGEs refer to internal pages of an Enterprise and the E LOCATION refers to external web pages (Yahoo) or proprietary systems (AOL) For example: Home page, Category page, Products page, Order page, Help page, Search page
E SITE (2804) An electronic site refers to an external web site such as www.yahoo.com or a proprietary site developed for subscribers such as the AOL system
E SITE TYPE (2805) An entity used for classifying different types of web sites such as portals, aggregators, ISPs, etc.
EXTERNAL WEB AD PLACEMENT (2806) The specifics of where and when a specific external WEB AD will be displayed. These are ads that are placed on an externally-owned web site. Example: Banner Ad #232 (with the animated Poodle) will be displayed on the AOL ‘Pets’ area during January 2000.
INTERNAL WEB AD PLACEMENT (2807) The specifics of where and when a specific internal WEB AD will be displayed. These are ads that are placed on an Enterprise-owned web site. Example: Banner Ad #232 (with the animated Poodle) will be displayed on the AOL ‘Pets’ area during January 2000.
NAVIGATION LEVEL (2808) Used to construct a hierarchical structure of the web site. Each level points to the next higher level hierarchical navigation levels the user can access from this WEB PAGE. NOTE: It is only intended to be used by high level navigational type pages. This allows the Enterprise to set up a Navigation Structure that makes it simple for users to “drill down” from general to specific information/ITEMs. Example: Department Level, Product Category Level, Product Sub Category Level, etc.
WEB AD PLACEMENT (2809) The specifics of where and when a specific WEB AD will be displayed. Example: Banner Ad #232 (with the animated Poodle) will be displayed on the AOL ‘Pets’ area during January 2000.
WEB AD PLACEMENT STATS (2810) Provides statistics about web ads that are useful in measuring their effectiveness. These values are usually collected by the ad-agency. For example, banner ad ‘blue sweater’ on mysite.com has 100 impressions, 20 clickthroughs over the last month.
WEB AD POSITION (2811) An entity that tracks difference places used in placing a WEB AD on a given WEB PAGE. For example, lower right hand corner, top middle, middle-left, etc
WEB PAGE (2812) A collection of multimedia components displayed to visitors via use of a web browsing application during visits to a WEB SITE. A WEB PAGE can contain product information, marketing information, customer service information. It can also allow for interaction, in the form of the creation of shopping carts, orders, etc. These pages are owned by the Enterprise. E SITE models external web pages. Example: A DVD Movies category page may consist of a group of images, text about the quality of the clothing, and information about a current sale.
WEB PAGE CONTEXT (2813) Links the Context for which the Web Page is being rendered.
WEB PAGE MM COMPONENT (2814) An associative entity that tracks various components appearing on a WEB PAGE.
WEB PAGE PAGE REGION (2815) Associates all of the possible Web Page Regions a Web Page may have. These regions include descriptors such as “Top Right”, “Lower Left”, “Center Left” and other positional descriptors, as needed.
WEB PAGE REGION (2816) This entity represents areas in which a WEB PAGE may be divided, examples include (TOP, BOTTOM, TOP-LEFT).
WEB PAGE TYPE (2817) This entity categorizes the WEB PAGEs according to business rules For example: Home page, Category page, Products page, Order page, Help page, Search page
WEB SECTION TYPE (2818) This entity represents a classification of the content for a WEB SITE SECTION similar to sections of a newspaper. A WEB SITE may be divided into several sections based on the content of the pages one section may be sports related content while another may be finance related.
WEB SITE (2819) This entity represents a collection of Enterprise-owned WEB PAGES under a single domain name. External web sites are found under E SITE.
WEB SITE CONTENT TYPE (2820) This entity represents a classification of the content of a WEB SITE possible SITE CONTENT TYPEs include Sports, News, Portal, etc.
WEB SITE NAVIGATION (2821) Provides the site map independent of the fact that the pages that form this structure may change over time. For example, “Blue suede shoes” page could be part of the “Elvis collection” class hierarchy or the “Men's Shoes” class hierarchy. And over time “Blue suede shoes” could also be part of the “What's hot” class hierarchy. The web site navigation entity provides a way of showing these changes over time.
WEB SITE SECTION (2822) This entity represents divisions of a WEB SITE such as Yahoo Sports or Yahoo Finance in order to divide large WEB SITES into smaller divisions of related WEB PAGES that contain similar content
The WEB VISIT Subject Area, illustrated in
BROWSER APPLICATION (2901) Web browser application being used. Microsoft Internet Explorer, WebTV, Netscape Navigator, etc.
BROWSER ID (2902) Defines a specific instance of an unique Web Browsing Application on a specific computer. Example: “John's copy of Microsoft 5.0 I.E. Browser on his iBook laptop computer.”
BROWSER VERSION (2903) Type of web browser application and version being used. Examples: Microsoft Internet Explorer 5.0, WebTV 1.0, Netscape Navigator 6.0, etc.
CONVERSION (2904) Represents the successful result of a recommendation provided by a recommendation engine such as that provided by BeFree. A recommendation is considered successful if a user clicks on the recommendation. A purchase need not be made in order for a recommendation to be considered a Conversion. (Analyst Note: the Recommendation Engine will most likely populate this information. The information in this entity is very similar to Ad Response, however since they represent information from 2 different business functions and data sources, the LDM team has decided to represent both entities.) (Analyst Note: This table is present to support integration with recommendation engines and does not imply this solution functions as a recommendation engine). The information contained in this entity is derivable and is provided to support various 3rd party E-Commerce applications.
CONVERSION CATEGORY (2905) Contains information concerning the linkage between recommended Offerings and the Web Page that the Offering was displayed on.
DOMAIN IP REASON (2906) Specifies the type of relationship that may exist between an IP Address and a Domain. Examples: IP Address of linking Server, Valid IP Addresses for a Domain.
DOMAIN ROOT (2907) The extension name of the domain server. Examples: .com, .net, org.
E LOC REF DIRECTORY (2908) Information about an internet directory listing that a customer used for accessing a WEB SITE. Example: For instance a customer could access yahoo and then go to the ‘business section’ and then to ‘wholesalers’ to finally select ‘Wholesaler A’. The corresponding directory listing information will be www.yahoo.com/business/wholesalers/
E LOC REF SEARCH (2909) An entity used to capture the outcome of an internet search that was in turn used by a customer to access a web site Example: if you conduct search on yahoo for blue sweaters, the search term gets embedded in the new url created (www.yahoo.com/?p=blue+sweaters). If the search results in an Enterprise's page, then the referral url will have the search information in it.
E LOC REF WEB AD (2910) An entity used to capture information about WEB ADs that were used by customers to access the web site. The entity also has information relevant to WEB ADs such as start and end dates and cost information
E LOC REFERRAL TYPE (2911) An entity used for classifying E LOCATION referrals into various sub-types such as Searches, Web Ads, Directories, etc.
E LOCATION REFERRAL (2912) An entity used to track E LOCATIONs that provide different referral mechanisms such as banner ads, directory listing, etc to a customer for accessing a web site Example: an electronic location could be a web site such as www.yahoo.com or a location within a proprietary web browsing system such as AOL. Note that with proprietary systems, we may not get a finer granularity of information as compared to web pages
EMAIL CLIENT APPLICATION (2913) Represents the email application used by a client to read and send email, such as Microsoft Outlook Express 5.0.
EMAIL REFERRAL (2914) This entity is used to capture information about any uniform resource link embedded in emails that were used to access a web site. Email referrals could be due to PROMOTIONs, WEB ADs or other methods.
ENTRY FLAG (2915) Describes the order of the pages viewed during a web visit: Examples: First Page, Exit Page, Intermediate Page.
EXIT METHOD (2916) The methods by which the user may leave a Web Site. This would have the value ‘timeout’ for most Web Visits but other values could be defined for explicit actions that result in a user exiting the Web Site such as clicking a logout button.
INTERACTION TASK (2917) Entity used for capturing information about individual web activity performed. These could range from basket selecting a travel destination, deleting an item, etc. The exact range of tasks that can be captured depends on the capabilities of the commerce server Example: Select seat choice, delete rental car from the shopping cart, place an order, etc
INTERNET PROTOCOL ADDRESS (2918) IP addresses are assigned to every computer or device on a TCP/IP network such as the internet. They may be assigned statically, where a computer/device is assigned an IP Address and it will always use that address. They may also be assigned dynamically where at the point a computer connects to a network, it is assigned an IP Address from the pool of addresses available from that provider. This entity is differentiated from ELECTRONIC ADDRESS (Geography SSA) which may not have IP Address detail but will likely have an e-mail User Name. Customers wishing to do so may make this entity a subtype of ELECTRONIC ADDRESS.
IP ADDRESS DOMAIN (2919) The domains that are associated with an Internet Protocol Address, as specified by Domain IP Reason. (NOTE: This is an associative entity used to resolve the M:M relationships between Internet Protocol Address and Visitor Domain.)
OPERATING SYSTEM (2920) The computer operating system being used by a Web Visitor. Example: Mac OS X, Linux, Windows 2000, etc.
PAGE REQUEST STATUS (2921) The status code of the page request. Examples include 200, 404, 401
PAGE VIEW (2922) Page view stores the information about the actual WEB PAGEs displayed to an individual during a given WEB VISIT. For example: home page→product page→casual wear→blue sweater. Along with this chain of pages visited information about bytes transferred, the time stamp when the page was viewed and a host of other details are stored.
PAGE VIEW MM COMPONENT (2923) Lists all the Components downloaded during a Page View. This relates a request for a Web Page document with the images and other Components that are requested to render the Web Page. Each entry equates to an HTTP request for a non Web Page document, identified by the extension of the file requested (pg, gif, etc.)
QUERY STRING FIELD NAME (2924) The domain of parameter names that may appear in the Query String of the URL for a Web Page. Examples: First name, Site, Location.
QUERY STRING FIELD VALUE (2925) The domain of parameter values that may appear in the Query String of the URL for a Web Page.
QUERY STRING NAME VALUE (2926) Stores the relationship between Page Views, Query String Field Names and Query String Field Values. It holds the set of name-value pairs from the query string of the URL that is associated with this Page View. The query string is the component of the URL that follows the document path. It begins with a question mark and consists of any number of sets of name-value pairs (?param1=value1¶m2=value2 . . . paramn=valuen). The name-value pairs often include things such as search parameters. This entity can be used to store both the parameters for the current URL as well as the referring URL, Query String Current URL Ind is used to distinguish between the two URLs.
RECOMMENDATION (2927) Contains a record for each recommendation that was made by the recommendation engine. (This table is present to support integration with recommendation engines and does not imply that internal functions will serve as a recommendation engine). The information contained in this entity is derivable and is provided to support various 3rd party E-Commerce applications.
REFERRAL (2928) Referral is used to capture information about a customer's previous browsing history—prior to making a WEB VISIT. As part of customer's previous history only the immediate previous uniform resource link (uri) information is preserved. For example if a customer browsed aol→yahoo→clothing>women's clothing . . . , then the referral information will carry information about yahoo since that was the site browsed immediately prior to the web site. A customer could also use an email or directly access the web site by using a bookmark/favorites list.
REFERRAL TYPE (2929) An entity used for classifying referrals into various sub-types such as EMAIL referrals, E LOCATION referrals, etc.
VISITOR DOMAIN (2930) This entity stores information about domain from which customers access the Enterprise's web site. The domain is usually looked up by using or translating the IP Address into the domain name. The domain can have several components, e.g. top level (edu=education, corn=commercial, net=network), as well as a name (acme, ucla, at&t), and country (uk, de, fr, it, etc). (This is useful in providing summary level information about various access points for customers such as internet service providers, public access terminals, companies, universities, government sites, etc. The information can be useful in selecting advertisements and designing promotions. Example: if the visitor domain is www.uc.edu, then we can infer it is an individual from the University of Cincinnati and further the individual is from an educational domain. Similarly if the visitor's domain is www.acme.com, then its an individual associated with the Acme company, while mediaone.net would indicate the visitor's ISP.
WEB IDENTIFICATION METHOD (2931) The means by which a Party is identified for a Web Visit. There are three possible values: IP address, cookie, and registered.
WEB VISIT (2932) A VISIT during which an internet WEB SITE is accessed by an individual using the world wide web. Subtype of VISIT
WEB VISIT TYPE (2933) This entity represents a classification of the result derived from a WEB VISIT. Possible values include Browse, 1st Purchase, Repeat Purchase, etc.
A listing of all the attributes included within the entities shown in
The Travel Logical Data Model described above supports revenue management solutions, such as NCR Corporation's Teradata Revenue Management Intelligence (RMI) solution. The RMI solution provides an Airline or other travel provider with the ability to increase revenues by achieving optimal passenger and revenue mix on each flight through investigative analysis of Passenger Name Record (PNR), booking, ticketing/TCN, inventory, schedule, authorization adjustment and flown/ticket lift data. It improves the management of inventory, pricing and demand forecasting through forecast accuracy and revenue management performance measures. The solution further protects revenue and inventory through the identification of fraudulent and improper booking and ticketing activity.
The data sources 3001 through 3005 at the bottom of
The following are real world examples of Revenue Management (RM) questions that can be answered by the system described above.
RM Base Questions:
These base questions deal with fundamental RM issues defined in conjunction with a major international airline.
This set of analytics is designed to identify flight exceptions or anomalies that need to be manually reviewed by a Revenue Management analyst. The analytics support drill down and drill across to allow the analyst to look at the data in a variety of views. They can be executed for a particular departure date or a range of departure dates. The requests can be for all segments, all O&Ds, all O&Ds for a particular market and/or region, all O&Ds with a particular origin, or all O&Ds for a particular destination. Each request can also support a specified number of days out from departure.
All of the following questions are concerned with summing the number of bookings and/or revenue for some unit (a specific O&D, for example) and comparing the bookings and/or revenue of that unit to the average bookings and/or revenue of all like units over some time-based filter criteria. This means that drill down and drill across is critical since it is impossible to create just one view that satisfies any one requirement, because the analyst must specify the filter criteria over which to calculate the averages.
This set of analytics is used to perform show rate analyses. They are designed to answer questions about how actual show rates compare to projected show rates. These analytics can be for an entire departure date, a departure time, a flight, or for a specific market, origin, or destination within a particular departure date.
Questions 1, 3 and 5 are concerned with calculating the show rate at one departure date for some unit (a specific O&D path, for example) and comparing the show rate of that unit to the actual or average show rate of all like units over some filter criteria. This being the case, it is impossible to create just one view that satisfies any one requirement, because it is up to the person writing the query to specify the filter criteria over which to calculate the show rates. However, views can be defined as a common base for constructing queries of the type required. This can be presented as drill down or drill across analytics.
This set of analytics is designed to display information about specific segments or market O&Ds. If the request is information for a segment, then the entire set of O&D paths over the segment will be displayed. If the information is for a market O&D, then the entire set of O&D paths within the market O&D will be displayed.
Revenue recovery questions deal with fraud and other illegal practices. Corporate Security teams that are proactive with the use of warehouse data have identified a number of illegal activities that can affect the Enterprise. Some examples of abuse are:
The Figures and description of the invention provided above reveal a flexible relational data model for a travel or transportation enterprise. The Travel Logical Data Model design enables the capturing of detail data concerning customers of a travel provider, products and services provided by the travel provider, customer transactions with the travel provider, and customer purchases of products and services from the travel provider. The travel provider can be an airline, a car rental agency, a cruise line, a lodging provider; a travel agency; a bus line or a passenger rail service provider. The Teradata Travel Logical Data Model is a comprehensive and flexible blueprint of how to organize data within a data warehouse to support business insight and intelligence. It provides the structure to address the business questions needed to manage multiple business areas for all of the travel industry segments.
The Teradata Travel Logical Data Model supports Revenue Management applications, providing an Airline or other travel provider with the ability to increase revenues by achieving optimal passenger and revenue mix on each flight through investigative analysis of Passenger Name Records, booking, ticketing/TCN, inventory, schedule, authorization adjustment and flown/ticket lift data. Revenue Management applications supported by the Travel LDM can improve the management of inventory, pricing and demand forecasting through forecast accuracy and revenue management performance measures, and protect revenue and inventory through the identification of fraudulent and improper booking and ticketing activity.
The foregoing description of the preferred embodiment of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto.
This application claims priority under 35 U.S.C. § 119(e) to the following co-pending and commonly-assigned patent application: Provisional Application Ser. No. 60/487,547, entitled “SYSTEM AND METHOD FOR CAPTURING, STORING AND ANALYZING REVENUE MANAGEMENT INFORMATION FOR THE TRAVEL AND TRANSPORTION INDUSTRIES,” filed on Jul. 15, 2003.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5021953 | Webber et al. | Jun 1991 | A |
| 5255184 | Hornick et al. | Oct 1993 | A |
| 5560005 | Hoover et al. | Sep 1996 | A |
| 5652867 | Barlow et al. | Jul 1997 | A |
| 5897620 | Walker et al. | Apr 1999 | A |
| 5918209 | Campbell et al. | Jun 1999 | A |
| 5948040 | DeLorme et al. | Sep 1999 | A |
| 6263315 | Talluri | Jul 2001 | B1 |
| 6336097 | Scipioni | Jan 2002 | B1 |
| 20020069093 | Stanfield | Jun 2002 | A1 |
| 20020120492 | Phillips et al. | Aug 2002 | A1 |
| 20020178034 | Gardner et al. | Nov 2002 | A1 |
| 20030055689 | Block et al. | Mar 2003 | A1 |
| 20030110062 | Mogler et al. | Jun 2003 | A1 |
| 20030115093 | Lim et al. | Jun 2003 | A1 |
| 20030225600 | Slivka et al. | Dec 2003 | A1 |
| 20040015409 | Chittenden et al. | Jan 2004 | A1 |
| 20040044664 | Cash et al. | Mar 2004 | A1 |
| 20040054549 | Chittenden et al. | Mar 2004 | A1 |
| 20050004818 | Liman | Jan 2005 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 60487547 | Jul 2003 | US |
