Basis of Presentation. The financial statements are presented on a consolidated basis and include the accounts of the Company and its wholly-owned subsidiaries in accordance with accounting principles generally accepted in the United States of America ("GAAP").

Use of Estimates. The preparation of financial statements in conformity with GAAP requires management to make estimates and judgments that affect the reported amounts of assets and liabilities, the disclosure of contingent assets and liabilities at the date of the financial statements, and revenues and expenses during the period reported. On an ongoing basis, management evaluates these estimates and judgments, including those related to allowances for doubtful accounts, the valuation of inventory to net realizable value, share-based compensation and income taxes and any changes will be accounted for on a prospective basis. Actual results could differ from those estimates.

Revenue Recognition. Teradata's solution offerings typically include software, software subscriptions (unspecified when-and-if-available upgrades), hardware, maintenance support services, and other consulting, implementation and installation-related ("consulting") services. Teradata records revenue when it is realized, or realizable, and earned. Teradata considers these requirements met when:

Teradata reports revenue net of any taxes assessed by governmental authorities that are imposed on and concurrent with specific revenue-producing transactions. The Company assesses whether fees are fixed or determinable at the time of sale. Standard payment terms may vary based on the country in which the agreement is executed, but are generally between 30 and 90 days. Payments that are due within six months are generally deemed to be fixed or determinable based on a successful collection history on such arrangements, and thereby satisfy the required criteria for revenue recognition. Teradata delivers its solutions primarily through direct sales channels, as well as through alliances with system integrators, other independent software vendors and distributors, and value-added resellers (collectively referred to as "resellers"). In assessing whether the sales price to a reseller is fixed or determinable, the Company considers, among other things, past business practices with the reseller, the reseller's operating history, payment terms, return rights and the financial wherewithal of the reseller. When Teradata determines that the contract fee to a reseller is not fixed or determinable, that transaction is deferred and recognized upon sell-through to the end customer.

The Company's deliverables often involve delivery or performance at different periods of time. Revenue for software is generally recognized upon delivery with the hardware once title and risk of loss have been transferred. Revenue for software subscriptions, which provide for unspecified upgrades or enhancements on a when-and-if-available basis, is recognized straight-line over the term of the subscription arrangement. Revenue for maintenance support services is also recognized on a straight-line basis over the term of the contract. Revenue for other consulting, implementation and installation services is recognized as services are provided. In certain instances, acceptance of the product or service is specified by the customer. In such cases, revenue is deferred until the acceptance criteria have been met. Delivery and acceptance generally occur in the same reporting period. The Company's arrangements generally do not include any customer negotiated provisions for cancellation, termination or refunds that would significantly impact recognized revenue.

In October 2009, the Financial Accounting Standards Board ("FASB") amended the accounting standards for revenue recognition to remove tangible products containing software components and non-software components that function together to deliver the product's essential functionality from the scope of the industry-specific software revenue recognition guidance. In October 2009, the FASB also amended the accounting standards for multiple deliverable revenue arrangements to:

The standard is effective prospectively for revenue arrangements entered into or materially modified in fiscal years beginning on or after June 15, 2010. Teradata adopted these standards on a prospective basis as of the beginning of fiscal 2011 for new and materially modified arrangements originating on or after January 1, 2011.

The Company evaluates all deliverables in an arrangement to determine whether they represent separate units of accounting. A deliverable constitutes a separate unit of accounting when it has standalone value, and if the contract includes a general right of return relative to the delivered item, delivery or performance of the undelivered items is considered probable and substantially in the control of Teradata. This new guidance does not generally change the units of accounting for the Company's revenue transactions. Most of the Company's products and services qualify as separate units of accounting and are recognized upon meeting the criteria as described above.

For multiple deliverable arrangements that contain non-software related deliverables, the Company allocates revenue to each deliverable based upon the relative selling price hierarchy and if software and software-related deliverables are also included in the arrangement, to those deliverables as a group based on the BESP for the group. The selling price for a deliverable is based on its VSOE if available, TPE if VSOE is not available, or BESP if neither VSOE nor TPE is available. The Company then recognizes revenue when the remaining revenue recognition criteria are met for each deliverable. For the software group or arrangements that contain only software and software-related deliverables, the revenue recognition criteria utilizing the residual method remains unchanged as further described below.

Teradata's data warehousing software and hardware products are sold and delivered together in the form of a "Node" of capacity as an integrated technology solution. Because both the database software and hardware platform are necessary to deliver the data warehouse's essential functionality, the database software and hardware (Node) are excluded from the software rules and considered a non-software related deliverable. Teradata software applications and related support are considered software-related deliverables. Additionally, the amount of revenue allocated to the delivered items utilizing the relative selling price method is limited to the amount that is not contingent upon the delivery of additional items or meeting other specified performance conditions (the non-contingent amount).

VSOE is based upon the normal pricing and discounting practices for those products and services when sold separately. Teradata uses the stated renewal rate approach in establishing VSOE for maintenance and subscriptions (collectively referred to as postcontract customer support "PCS"). Under this approach, the Company assesses whether the contractually stated renewal rates are substantive and consistent with the Company's normal pricing practices. Renewal rates greater than the lower level of our targeted pricing ranges are considered to be substantive and, therefore, meet the requirements to support VSOE. In instances where there is not a substantive renewal rate in the arrangement, the Company allocates revenue based upon BESP, using the minimum established pricing targets as supported by the renewal rates for similar customers utilizing the bell-curve method. Teradata also offers consulting and installation-related services to its customers, which are considered non-software deliverables if they relate to the nodes. These services are rarely considered essential to the functionality of the data warehouse solution deliverable and there is never software customization of the proprietary database software. VSOE for consulting services is based on the hourly rates for standalone consulting services projects by geographic region and are indicative of the Company's customary pricing practices. Pricing in each market is structured to obtain a reasonable margin based on input costs.

In nearly all multiple-deliverable arrangements, the Company is unable to establish VSOE for all deliverables in the arrangement. This is due to infrequently selling each deliverable separately (such is the case with our nodes), not pricing products or services within a narrow range, or only having limited sales history. When VSOE cannot be established, attempts are made to establish TPE of the selling price for each deliverable. TPE is determined based on competitor prices for similar deliverables when sold separately. However, Teradata's offerings contain significant differentiation such that the comparable pricing of products with similar functionality cannot be obtained. This is because Teradata's products contain a significant amount of proprietary technology and its solutions offer substantially different features and functionality than other available products. As Teradata's products are significantly different from those of its competitors, the Company is unable to establish TPE for the vast majority of its products.

When the Company is unable to establish selling price using VSOE or TPE, the Company uses BESP in its allocation of arrangement consideration. The objective of BESP is to determine the price at which the Company would transact a sale if the product or service was sold on a standalone basis. The Company determines BESP for a product or service by considering multiple factors including, but not limited to, geographies, market conditions, product life cycles, competitive landscape, internal costs, gross margin objectives, purchase volumes and pricing practices.

The primary consideration in developing BESP for the Company's nodes is the bell-curve method based on historical transactions. The BESP analysis is at the geography level in order to align it with the way in which the Company goes to market and establishes pricing for its products. The Company has established discount ranges off of published list prices for different geographies based on strategy and maturity of Teradata's presence in the respective geography. There are distinctions in each geography and product group which support the use of geographies and markets for the determination of BESP. For example, the Company's U.S. market is relatively mature and most of the large transactions are captured in this market, whereas EMEA and APJ are less mature markets with generally smaller deal size. Additionally, the prices and margins for the Company's products vary by geography and by product class. BESP is analyzed on a quarterly basis using a rolling previous 4-quarters of data, which the Company believes best reflects most recent pricing practices in a changing marketplace.

The Company reviews VSOE, TPE and its determination of BESP on a periodic basis and updates it, when appropriate, to ensure that the practices employed reflect the Company's recent pricing experience. The Company maintains internal controls over the establishment and updates of these estimates, which includes review and approval by the Company's management. For the twelve months ended December 31, 2011 there was no material impact to revenue resulting from changes in VSOE, TPE or BESP, nor does the Company expect a material impact from such changes in the near term. Additionally, the adoption of the amended revenue recognition guidelines had no material net impact on the Company's results of operations for the twelve months ended December 31, 2011.

Term licenses, hosting arrangements and software-as-a-service ("SaaS"). As a result of the Company's acquisition of Aprimo, Inc. ("Aprimo") on January 21, 2011 (see Note 12), Teradata's application offerings were be expanded to include, term licenses, hosting arrangements and SaaS. Teradata previously offered its software applications primarily through a perpetual licensing arrangement. In cases where the contract requires the software to be hosted by the Company and provided via an on-demand arrangement, the software is considered a subscription. If the license is of limited life and does not require the Company to host the software for the customer, the software is considered a term license. In both types of these arrangements, revenues are recognized over the term of the agreement. For hosting arrangements where customers have the right to take possession of the Company's software at any time during the hosting period, the customer's rights to the software in these circumstances are not dependent on additional software payments or significant penalties.

Accounting for arrangements prior to January 1, 2011. For transactions entered into prior to January 1, 2011, the Company allocates revenue for multiple deliverable arrangements for which VSOE exists for undelivered elements but not for the delivered elements, using the "residual method". Teradata does not typically have VSOE for its hardware and software products. Therefore, in a substantial majority of Teradata arrangements entered into prior to January 1, 2011, the residual method is used to allocate the arrangement consideration. Under the residual method, the VSOE of the undelivered elements is deferred and accounted for under the applicable revenue recognition guidance, and the remaining portion of the arrangement fee is allocated to the delivered elements and is recognized as revenue. For arrangements in which VSOE does not exist for each undelivered element, revenue for the entire arrangement is deferred and not recognized until delivery of all the elements without VSOE has occurred, unless the only undelivered element is PCS in which case the entire contract is recognized ratably over the PCS period.

Contract accounting. If an arrangement involves significant production, modification or customization of the application software or the undelivered services are essential to the functionality of the delivered software then the Company uses the percentage-of-completion or completed-contract method of accounting. The percentage-of-completion method is used when estimates of costs to complete and extent of progress toward completion are reasonably dependable. The Company typically uses labor hours or costs incurred to date as a percentage of the total estimated labor hours or costs to fulfill the contract as the most reliable and meaningful measure that is available for determining a project's progress toward completion. In circumstances when reasonable and reliable cost estimates for a project cannot be made, the completed-contract method is used whereas no revenue is recognized until the project is complete. When total cost estimates exceed revenues, the Company accrues the estimated losses immediately. For purposes of allocation of the arrangement consideration, any products for which the services are not essential are separated utilizing the relative selling price method discussed above. PCS is also separated and allocated based on VSOE and then recognized ratably over the term. The remaining contract value, which typically includes application software and essential services, is then recognized utilizing the percentage-of-completion or completed-contract methods discussed above.

Shipping and Handling. Product shipping and handling costs are included in cost of products in the Consolidated Statements of Income.

Cash and Cash Equivalents. All short-term, highly-liquid investments having original maturities of three months or less are considered to be cash equivalents.

Allowance for Doubtful Accounts. Teradata establishes provisions for doubtful accounts using both percentages of accounts receivable balances to reflect historical average credit losses and specific provisions for known issues.

Inventories. Inventories are stated at the lower of cost or market, using the average cost method.

Property and Equipment. Property and equipment, leasehold improvements and rental equipment are stated at cost less accumulated depreciation. Depreciation is computed over the estimated useful lives of the related assets primarily on a straight-line basis. Equipment is depreciated over 3 to 20 years and buildings over 25 to 45 years. Leasehold improvements are depreciated over the life of the lease or the asset, whichever is shorter. Total depreciation expense on the Company's property and equipment for the years ended December 31, 2011, 2010 and 2009 was $33 million, $25 million and $22 million, respectively.

 Capitalized Software. Direct development costs associated with internal-use software are capitalized and amortized over the estimated useful lives of the resulting software. The costs are capitalized when both the preliminary project stage is completed and it is probable that computer software being developed will be completed and placed in service. Teradata typically amortizes capitalized internal-use software on a straight-line basis over three years beginning when the asset is substantially ready for use.  Costs incurred for the development of software that will be sold, leased or otherwise marketed are capitalized when technological feasibility has been established. Technological feasibility is established when planning, designing and initial coding activities that are necessary to establish the product can be produced to meet its design specifications. In the absence of a program design, a working model is used to establish technological feasibility. These costs are included within capitalized software and are amortized over the estimated useful lives of the resulting software. The Company amortizes capitalized software over periods up to four years using the greater of the ratio that current gross revenues for a product bear to the total of current and anticipated future gross revenues for that product or the straight-line method over the remaining estimated economic life of the product beginning when the product is available for general release. Costs capitalized include direct labor and related overhead costs. Costs incurred prior to technological feasibility and after general release are expensed as incurred. The following table identifies the activity relating to capitalized software:

Valuation of Long-Lived Assets. Long-lived assets such as property and equipment, acquired intangible assets and internal capitalized software are reviewed for impairment when events or changes in circumstances indicate that the carrying amount of the assets may not be recoverable. An impairment loss would be recognized when estimated future undiscounted cash flows expected to result from the use of the asset and its eventual disposition are less than the carrying amount.

Goodwill. Goodwill represents the excess of the purchase price in a business combination over the fair value of net tangible and intangible assets acquired. Goodwill amounts are not amortized, but rather are tested for impairment annually or upon occurrence of an event or change in circumstances change that would more likely than not reduce the fair value of a reporting unit below its carrying amount. The Company did not recognize any goodwill impairment charges in 2011, 2010 or 2009.

Warranty. Provisions for product warranties are recorded in the period in which the related revenue is recognized. The Company accrues warranty reserves using percentages of revenue to reflect the Company's historical average warranty claims.

Research and Development Costs. Research and development costs are expensed as incurred (with the exception of the capitalized software development costs discussed above). Research and development costs primarily include payroll and headcount-related costs, contractor fees, facilities, infrastructure costs, and administrative expenses directly related to research and development support.

Pension and Postemployment Benefits. The Company accounts for its pension and postemployment benefit obligations using actuarial models. The measurement of plan obligations was made as of December 31, 2011. Liabilities are computed using the projected unit credit method. The objective under this method is to expense each participant's benefits under the plan as they accrue, taking into consideration salary increases and the plan's benefit allocation formula. Thus, the total pension or postemployment benefit to which each participant is expected to become entitled is broken down into units, each associated with a year of past or future credited service.

The Company recognizes the funded status of its pension and postemployment plan obligations in its consolidated balance sheet and records in other comprehensive income certain gains and losses that arise during the period, but are deferred under pension accounting rules.

Foreign Currency. Assets and liabilities of non-U.S. subsidiaries that operate in a local currency environment are translated into U.S. dollars at period-end exchange rates. Income and expense accounts are translated at average exchange rates prevailing during the period. Adjustments arising from the translation are included in accumulated other comprehensive income (loss), a separate component of stockholders' equity. Gains and losses resulting from foreign currency transactions are included in determining net income.

Income Taxes. Income tax expense is provided based on income before income taxes in the various jurisdictions in which the Company conducts its business. Deferred income taxes reflect the impact of temporary differences between assets and liabilities recognized for financial reporting purposes and such amounts recognized for tax purposes. These deferred taxes are determined based on the enacted tax rates expected to apply in the periods in which the deferred assets or liabilities are expected to be settled or realized. Teradata recognizes tax benefits from uncertain tax positions only if it is more likely than not the tax position will be sustained on examination by taxing authorities, based on the technical merits of the position. The Company records valuation allowances related to its deferred income tax assets when it is more likely than not that some portion or all of the deferred income tax assets will not be realized.

Share-based Compensation. Share-based payments to employees, including grants of stock options, are recognized in the financial statements based on their fair value. The fair value of each stock option award on the grant date is estimated using the Black-Scholes option-pricing model with the following assumptions: expected dividend yield, expected stock price volatility, weighted-average risk-free interest rate and weighted average expected term of the options. As of October 2011, the Company's expected volatility assumption used in the Black-Scholes option-pricing model is based on a blend of peer group volatility and Teradata volatility. Prior to that date, because the Company did not have a sufficient trading history as a stand-alone public company, the volatility was purely based on the peer group volatility. The expected term assumption is based on the simplified method under GAAP, which is based on the vesting period and contractual term for each vesting tranche of awards. The mid-point between the vesting date and the expiration date is used as the expected term under this method. The risk-free interest rate used in the Black-Scholes model is based on the implied yield curve available on U.S. Treasury zero-coupon issues at the date of grant with a remaining term equal to the Company's expected term assumption. The Company has never declared or paid a cash dividend.

Treasury Stock. Shares of the Company's common stock repurchased through the share repurchase programs is held as treasury stock. Treasury stock is accounted for using the cost method.

Earnings Per Share. Basic earnings per share is calculated by dividing net income by the weighted-average number of shares outstanding during the reported period. The calculation of diluted earnings per share is similar to basic earnings per share, except that the weighted-average number of shares outstanding includes the dilution from potential shares added from stock options, restricted stock awards and other stock awards. Refer to Note 5 for share information on the Company's stock compensation plans.

The components of basic and diluted earnings per share are as follows:

No stock options were excluded from the computation of diluted earnings per share for the twelve months ended December 31, 2011. Options to purchase 0.6 million shares of common stock for 2010 and 1.8 million shares of common stock for 2009 were not included in the computation of diluted earnings per share because their exercise prices were greater than the average market price of the common shares and, therefore, the effect would have been anti-dilutive.