XML 46 R8.htm IDEA: XBRL DOCUMENT
v3.10.0.1

Description of Business, Basis of Presentation and Significant Accounting Policies | 12 Months Ended
--- | ---
Dec. 31, 2018
Description of Business, Basis of Presentation and Significant Accounting Policies [Abstract] |
Description of Business, Basis of Presentation and Significant Accounting Policies | Description of Business, Basis of Presentation and Significant Accounting Policies Description of the Business. Teradata Corporation ("we," "us," "Teradata," or the "Company") is a leading hybrid cloud analytics software provider focusing on delivering pervasive data intelligence to our customers, which we define as the ability to leverage 100% of a company’s data to uncover real-time intelligence, at scale. We help customers integrate and simplify their analytics ecosystem, access and manage data, and use analytics to extract answers and derive business value from data. Our solutions and services comprise software, hardware, and related business consulting and support services to deliver analytics across a company’s entire analytical ecosystem. 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”). During the first quarter of 2018, the Company changed its historical presentation of its revenue and cost of revenue categories. Previously, the Company presented revenue and cost of revenue on two lines: product and cloud, and services. As part of the Company’s business transformation, the Company is transitioning away from perpetual transactions to subscription-based transactions. To better reflect this shift in the business, the Company adopted a revised presentation in the first quarter of 2018, including the separation of recurring revenue from non-recurring product and consulting services. Recurring revenue consists of our on-premises and off-premises subscriptions, which have varying term lengths from one month to five years. Recurring revenue is intended to depict the revenue recognition model for these subscription transactions. The recurrence of these revenue streams in future periods depends on several factors, including contractual periods and customers' renewal decisions. Perpetual software licenses and hardware revenue consists of hardware, perpetual software licenses, and subscription/term licenses recognized upfront. Consulting services revenue consists of consulting, implementation and installation services. In connection with these revisions, the Company also revised its cost of revenue classification to present costs associated with the new revenue presentation. This change in presentation does not affect the Company’s total revenues, total cost of revenues or overall total gross profit (defined as total revenue less total cost of revenue). Prior period amounts have been restated to conform to the current year presentation, unless otherwise stated that the prior period amounts have not been restated. 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, impairments of goodwill and other intangibles, stock-based compensation, pension and other postemployment benefits, and income taxes and any changes will be accounted for on a prospective basis. Actual results could differ from those estimates. Revenue Recognition. In May 2014, the FASB issued Accounting Standards Update No. 2014-09, Revenue from Contracts with Customers (“Topic 606”) that affects any entity that either enters into contracts with customers to transfer goods or services or enters into contracts for the transfer of nonfinancial assets unless those contracts are within the scope of other standards. Topic 606 supersedes the revenue recognition requirements of the prior revenue recognition guidance used prior to January 1, 2018. The Company adopted Topic 606 as of January 1, 2018 using the modified retrospective method for all contracts not completed as of the date of adoption. The reported results for 2018 reflect the application of Topic 606 while the reported results for 2016 and 2017 were prepared under the guidance of Accounting Standards Codification 605, Revenue Recognition, which is also referred to herein as the “previous guidance.” As a result, prior periods have not been restated and continue to be reported under the previous guidance. The cumulative effect of applying Topic 606 was recorded as an adjustment to accumulated deficit as of the adoption date. See Note 3 for the required disclosures related to the impact of adopting this standard. See Note 4 for costs to obtain and fulfill a customer contract. Revenue Recognition under Topic 606 The Company adopted Topic 606 as of January 1, 2018 for all contracts not completed as of the date of adoption. The core principle of Topic 606 is that an entity should recognize revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the Company expects to be entitled in exchange for those goods or services. To achieve that core principle, the Company performs the following five steps:
1. | identify the contract with a customer,
2. | identify the performance obligations in the contract,
3. | determine the transaction price,
4. | allocate the transaction price to the performance obligations in the contract, and
5. | recognize revenue when (or as) the Company satisfies a performance obligation.
The Company only applies the above five-step model to contracts when it is probable that the Company will collect the consideration it is entitled to in exchange for goods or services it transfers to the customer. The Company applies judgment in determining the customer’s ability and intention to pay, which is based on a variety of factors including the customer’s historical payment experience, published credit, and financial information pertaining to the customer. Revenue is measured based on consideration specified in a contract with a customer, and excludes any sales, value add, and other taxes the Company collects concurrent with revenue-producing activities. A performance obligation is a promise in a contract to transfer a distinct good or service to the customer. The Company recognizes revenue when it satisfies a performance obligation by transferring control over a good or service to a customer. Estimates of variable consideration are included in revenue to the extent that it is probable that a significant reversal of cumulative revenue will not occur once the uncertainty is resolved. The Company uses the expected value method or the most likely amount method depending on the nature of the variable consideration. Our estimates of variable consideration and determination of whether to include estimated amounts in the transaction price are based largely on an assessment of our anticipated performance and all information (historical, current and forecasted) that is reasonably available to us. If actual results in the future vary from the Company’s estimates, the Company adjusts these estimates in the period such variances become known. Typically, the amount of variable consideration is not material. For contracts with multiple performance obligations, the Company allocates the contract’s transaction price to each performance obligation using the relative standalone selling price of each distinct good or service in the contract. The Company must apply judgment to determine whether promised goods or services are capable of being distinct and distinct within the context of the contract. If these criteria are not met, the promised goods or services are combined with other goods or services and accounted for as a combined performance obligation. Revenue is then recognized either at a point in time or over time depending on our evaluation of when the customer obtains control of the promised goods or services. This evaluation requires significant judgment and the decision to combine a group of contracts or separate the combined or single contract into multiple performance obligations could change the amount of revenue recorded in a given period. In addition, the Company has developed assumptions that require judgment to determine the standalone selling price for each performance obligation identified in the contract. The Company determines the standalone selling price for a good or service by considering multiple factors including, geographies, market conditions, product life cycles, competitive landscape, internal costs, gross margin objectives, purchase volumes and pricing practices. The Company reviews the standalone selling price for each of its performance obligations 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. Teradata delivers its solutions primarily through direct sales channels, as well as through other independent software vendors and distributors and value-added resellers. Standard payment terms may vary based on the country in which the contract is executed, but are generally between 30 days and 90 days. The following is a description of the principal activities and performance obligations from which the Company generates its revenue:
• | Subscriptions - The Company sells on and off-premises subscriptions to our customers through our subscription licenses, cloud, service model, and hardware rental offerings. Teradata’s subscription licenses include a right-to-use license and revenue is recognized upfront at a point in time unless the customer has a contractual right to cancel, where revenue is recognized on a month-to-month basis and is included within the recurring revenue caption. Subscription licenses recognized upfront are reported within the perpetual software licenses and hardware caption. Cloud and service model arrangements include a right-to-access software license on Teradata owned or third party owned hardware such as the public cloud. Revenue is recognized ratably over the contract term and included within the recurring revenue caption. Service models typically include a minimum fixed amount that is recognized ratably over the contract term and may include an elastic amount for usage above the minimum, which is recognized monthly based on actual utilization. For our hardware rental offering, the Company owns the hardware and may or may not provide managed services. The revenue for these arrangements is generally recognized straight-line over the term of the contract and is included within the recurring revenue caption. Hardware rentals are generally accounted for as operating leases and considered outside the scope of Topic 606.
• | Maintenance and software upgrade rights - Revenue for maintenance and unspecified software upgrade rights on a when-and-if-available basis are recognized straight-line over the term of the contract.
• | Perpetual software licenses and hardware - Revenue for software is generally recognized when the customer has the ability to use and benefit from its right to use the license. Hardware is typically recognized upon delivery once title and risk of loss have been transferred (when control has passed).
• | Consulting services - The Company accounts for individual services as separate performance obligations if a service is separately identifiable from other items in a combined arrangement and if a customer can benefit from it on its own or with other resources that are readily available to the customer. Revenue for consulting, implementation and installation services is recognized as services are provided by measuring progress toward the complete satisfaction of the Company’s obligation. Progress for services that are contracted for at a fixed price is generally measured based on hours incurred as a portion of total estimated hours. Progress for services that are contracted for on a time and materials basis is generally based on hours expended. These input methods (e.g. hours incurred or expended) of revenue recognition are considered a faithful depiction of our efforts to satisfy services contracts and therefore reflect the transfer of services to a customer under such contracts.
Significant Accounting Policies and Practical Expedients under Topic 606 The following are the Company’s significant accounting policies not already disclosed elsewhere and practical expedients relating to revenue from contracts with customers:
• | Taxes assessed by a governmental authority that are both imposed on and concurrent with a specific revenue-producing transaction, that are collected by the Company from a customer, are excluded from revenue.
• | Shipping and handling costs associated with outbound freight after control over a product has transferred to a customer are accounted for as fulfillment cost and are included in cost of revenues.
• | The Company does not adjust for the effects of a significant financing component if the period between performance and customer payment is one year or less.
• | The Company expenses the costs to obtain a contract as incurred when the expected amortization period is one year or less.
Revenue Recognition under Topic 605 (periods prior to January 1, 2018) Teradata records revenue when it is realized, or realizable, and earned. Teradata considers these requirements met when:
• | Persuasive evidence of an arrangement exists
• | The offerings or services have been delivered to the customer
• | The sales price is fixed or determinable and free of contingencies or significant uncertainties
• | Collectibility is reasonably assured
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 days 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. The Company’s deliverables often involve delivery or performance at different periods of time. The Company's deliverables include the following:
• | Subscription license - revenue for these arrangements is typically recognized ratably over the contract term.
• | Cloud and service model - revenue for these arrangements are recognized outside the software rules and revenue is recognized ratably over the contract term.
• | Rentals - revenue for these arrangements is generally recognized straight-line over the term of the contract and are generally accounted for as operating leases.
• | Perpetual software and hardware - revenue is generally recognized upon delivery once title and risk of loss have been transferred.
• | Unspecified software upgrades - revenue is recognized straight-line over the term of the arrangement.
• | Maintenance support services - revenue is recognized on a straight-line basis over the term of the contract.
• | Consulting, implementation and installation services - revenue 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.
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 best estimate of selling price (“BESP”) for the group. The selling price for a deliverable is based on its vendor-specific objective evidence of selling price (“VSOE”) if available, third-party evidence of selling price (“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 is allocated utilizing the residual or fair value method. 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 software arrangement fee is allocated to the delivered elements and is recognized as revenue. The fair value method is similar to the relative selling price method used for non-software deliverables except that the allocation of each deliverable is based on VSOE. VSOE is based upon the normal pricing and discounting practices for those offerings and services when sold separately. Teradata uses the stated renewal rate approach in establishing VSOE for maintenance and when-and-if-available software upgrades. 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 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. 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. 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 platforms is the bell-curve method based on historical transactions. The BESP analysis is at the geography level to align it with the way in which the Company goes to market and establishes pricing for its offerings. BESP is analyzed on a semi-annual basis using data from the four previous quarters, which the Company believes best reflects most recent pricing practices in a changing marketplace. Shipping and Handling. Product shipping and handling are included in cost in the Consolidated Statements of Income (Loss). 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. Cost of service parts is determined using the average cost method. Finished goods inventory is determined using actual cost. Available-for-sale Securities. Available-for-sale securities are reported at fair value. Unrealized holding gains and losses are excluded from earnings and reported in other comprehensive income (loss). Realized gains and losses are included in other income and expense in the Consolidated Statements of Income (Loss). Long-Lived Assets 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 5 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 December 31 was as follows:
In millions | 2018 |  | 2017 |  | 2016
Depreciation expense | $ | 67 |  |  | $ | 55 |  |  | $ | 49 |
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 analytic applications are expensed as incurred based on the frequency and agile nature of development. Prior to 2017, costs incurred for the development of analytic database software that will be sold, leased or otherwise marketed were capitalized between technological feasibility and the point at which a product was ready for general release. 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 are complete. 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 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. In 2016, our research and development efforts became more driven by market requirements and rapidly changing customers' needs. In addition, the Company started applying agile development methodologies to help respond to new technologies and trends. Agile development methodologies are characterized by a more dynamic development process with more frequent and iterative revisions to a product release features and functions as the software is being developed. Due to the shorter development cycle and focus on rapid production associated with agile development, the Company did not capitalize any amounts for external-use software development costs in 2018 and 2017 due to the relatively short duration between the completion of the working model and the point at which a product is ready for general release. Prior capitalized costs will continue to be amortized under the greater of revenue-based or straight-line method over the estimated useful life. The following table identifies the activity relating to capitalized software for the following periods:
| Internal-use Software |  | External-use Software
In millions | 2018 |  | 2017 |  | 2016 |  | 2018 |  | 2017 |  | 2016
Beginning balance at January 1 | $ | 16 |  |  | $ | 13 |  |  | $ | 13 |  |  | $ | 105 |  |  | $ | 174 |  |  | $ | 177 |
Capitalized | 6 |  |  | 9 |  |  | 6 |  |  | — |  |  | — |  |  | 59 |
Amortization | (7 | ) |  | (6 | ) |  | (6 | ) |  | (48 | ) |  | (69 | ) |  | (62 | )
Ending balance at December 31 | $ | 15 |  |  | $ | 16 |  |  | $ | 13 |  |  | $ | 57 |  |  | $ | 105 |  |  | $ | 174 |
The aggregate amortization expense (actual and estimated) for internal-use and external-use software for the following periods is:
| Actual |  | For the years ended (estimated)
In millions | 2018 |  | 2019 |  | 2020 |  | 2021 |  | 2022 |  | 2023
Internal-use software amortization expense | $ | 7 |  |  | $ | 6 |  |  | $ | 7 |  |  | $ | 7 |  |  | $ | 6 |  |  | $ | 6 |
External-use software amortization expense | $ | 48 |  |  | $ | 34 |  |  | $ | 23 |  |  | $ | — |  |  | $ | — |  |  | $ | — |
Estimated expense, which is recorded to cost of sales for external use software, is based on capitalized software at December 31, 2018 and does not include any new capitalization for future periods. 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 is calculated based on the present value of future cash flows and 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. No impairment was recognized during 2018. 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 that would more likely than not reduce the fair value of a reporting unit below its carrying amount. See Note 5 for additional information. 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. See Note 10 for additional information. Research and Development Costs. Research and development costs are expensed as incurred (except for the capitalized software development costs discussed above). Research and development costs primarily include labor-related costs, contractor fees, and overhead expenses directly related to research and development support. Pension and Postemployment Benefits. The Company accounts for its pension benefit and its non-U.S. postemployment benefit obligations using actuarial models. The measurement of plan obligations was made as of December 31, 2018. 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 non-U.S. 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 and postemployment accounting rules. See Note 8 for additional information. 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 daily exchange rates prevailing during the period. Adjustments arising from the translation are included in accumulated other comprehensive income, 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. The Company made an accounting policy election in 2018 related to the Tax Act to provide for the tax expense related to global intangible low-taxed income (“GILTI”) in the year the tax is incurred. 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 the deferred income tax assets will not be realized. See Note 6 for additional information. Stock-based Compensation. Stock-based payments to employees, including grants of stock options, restricted shares and restricted share units, 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. The Company’s expected volatility assumption used in the Black-Scholes option-pricing model is based on Teradata's historical volatility. The expected term for options granted is based upon historical observation of actual time elapsed between date of grant and exercise of options for all employees. The risk-free interest rate used in the Black-Scholes model is based on the implied yield curve available on U.S. Treasury 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. See Note 7 for additional information. Earnings (Loss) Per Share. Basic earnings (loss) per share is calculated by dividing net income (loss) 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 share awards and other stock awards. Refer to Note 7 for share information on the Company’s stock compensation plans. The components of basic and diluted earnings (loss) per share for the years ended December 31 are as follows:
In millions, except earnings (loss) per share | 2018 |  | 2017 |  | 2016
Net income (loss) attributable to common stockholders | $ | 30 |  |  | $ | (67 | ) |  | $ | 125 |
Weighted average outstanding shares of common stock | 119.2 |  |  | 125.8 |  |  | 129.7 |
Dilutive effect of employee stock options, restricted shares and other stock awards | 2.0 |  |  | — |  |  | 1.8 |
Common stock and common stock equivalents | 121.2 |  |  | 125.8 |  |  | 131.5 |
Earnings (loss) per share: |  |  |  |  |
Basic | $ | 0.25 |  |  | $ | (0.53 | ) |  | $ | 0.96 |
Diluted | $ | 0.25 |  |  | $ | (0.53 | ) |  | $ | 0.95 |
For 2017, due to the net loss attributable to Teradata common stockholders, largely due to the tax expense recorded because of the Tax Cuts and Jobs Act of 2017, potential common shares that would cause dilution, such as employee stock options, restricted shares and other stock awards, have been excluded from the diluted share count because their effect would have been anti-dilutive. For 2017, the fully diluted shares would have been 127.8 million Options to purchase 2.6 million shares in 2018, 2.7 million shares in 2017 and 5.2 million shares in 2016 of common stock, 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. Recently Issued Accounting Pronouncements Leases. In February 2016, the Financial Accounting Standards Board (FASB) issued new guidance under Topic 842, which requires a lessee to account for leases as finance or operating leases. Both types of leases will result in the lessee recognizing a right-of-use asset and a corresponding lease liability on its balance sheet, with differing methodology for income statement recognition. For lessors, the standard modifies the classification criteria and the accounting for sales-type and direct financing leases. Entities will classify leases to determine how to recognize lease-related revenue and expense. This standard is effective for public entities for fiscal years, and interim periods within those years, beginning after December 15, 2018, and early adoption is permitted. We anticipate adopting this standard on January 1, 2019 using the prospective adoption approach with a cumulative-effect adjustment recognized to the opening balance of retained earnings on the adoption date with prior periods not recast and anticipate electing certain of the practical expedients allowed under the standard. We are in the process of aggregating and evaluating lease arrangements, implementing new controls and processes, and implementing a lease accounting system. Based on a preliminary assessment, the Company expects that most of its operating lease commitments will be subject to the new guidance and recognized as operating lease liabilities and right-of-use assets upon adoption. The impact to the Company’s balance sheet is estimated to result in approximately 3 percent increase in assets and approximately 4 percent increase in liabilities. The impact on our results of operations and cash flows is not expected to be material. Comprehensive Income. In February 2018, the FASB issued new guidance for Income Statement—Reporting Comprehensive Income (Topic 220): Reclassification of Certain Tax Effects from Accumulated Other Comprehensive Income (ASU 2018-02), which allows companies to reclassify stranded tax effects resulting from the Tax Reform Act from accumulated other comprehensive income to retained earnings. The amendments are effective for all entities for fiscal years beginning after December 15, 2018 and interim periods within those fiscal years. The impact on our results of operations and cash flows is not expected to be material. Clarifying the Scope and the Accounting Guidance for Contributions Received and Contributions Made. In June 2018, the FASB issued new guidance to clarify and improve the scope and the accounting guidance for contributions received and contributions made. The amendments are intended to assist entities in evaluating whether transactions should be accounted for as contributions (nonreciprocal transactions) or as exchange (reciprocal) transactions and determining whether a contribution is conditional. The amendments in this update are effective for fiscal years, and interim periods within those fiscal years, beginning after December 15, 2018. The Company is currently evaluating this guidance to determine the impact it may have on its consolidated financial statements. Fair Value Measurement. In August 2018, the FASB issued new guidance that modifies disclosure requirements related to fair value measurement. The amendments in this update are effective for fiscal years, and interim periods within those fiscal years, beginning after December 15, 2019. Implementation on a prospective or retrospective basis varies by specific disclosure requirement. Early adoption is permitted. The standard also allows for early adoption of any removed or modified disclosures upon issuance of this update while delaying adoption of the additional disclosures until their effective date. The Company is currently evaluating this guidance to determine the impact it may have on its disclosures. Compensation-Retirement Benefits-Defined Benefit Plans-General. In August 2018, the FASB issued new guidance that modifies the disclosure requirements for employers that sponsor defined benefit pension or other postretirement plans. For public companies, the amendments in this update are effective for fiscal years beginning after December 15, 2020, with early adoption permitted, and is to be applied on a retrospective basis to all periods presented. The Company is currently evaluating this guidance to determine the impact it may have on its disclosures. Customer’s Accounting for Implementation Costs Incurred in a Cloud Computing Arrangement That Is a Service Contract. In August 2018, the FASB issued new guidance that reduces complexity for the accounting for costs of implementing a cloud computing service arrangement and aligns the requirements for capitalizing implementation costs incurred in a hosting arrangement that is a service contract with the requirements for capitalizing implementation costs incurred to develop or obtain internal-use software (and hosting arrangements that include an internal-use software license). For public companies, the amendments in this update are effective for fiscal years, and interim periods within those fiscal years, beginning after December 15, 2019, with early adoption permitted. Implementation should be applied either retrospectively or prospectively to all implementation costs incurred after the date of adoption. The effects of this standard on our financial position, results of operations or cash flows are not expected to be material. Recently Adopted Guidance Presentation of Net Periodic Pension Cost and Net Periodic Post-Retirement Benefit Cost. In March 2017, the FASB issued accounting guidance for “Compensation – Retirement Benefits (Topic 715): Improving the Presentation of Net Periodic Pension Cost and Net Periodic Post-Retirement Benefit Cost.” The amendment requires the service cost component of net periodic benefit cost be presented in the same income statement line item as other employee compensation costs arising from services rendered during the period and other components of the net periodic benefit cost be presented separately from the line item that includes the service cost and outside of any subtotal of operating income. The Company adopted this amended guidance in the first quarter of 2018. The retroactive adoption of this standard resulted in an increase in operating income and a corresponding increase in other expense of $6 million in 2018, $4 million in 2017 and $3 million in 2016. Derivatives and Hedging (Topic 815), Targeted Improvements to Accounting for Hedging Activities. In August 2017, the FASB issued new guidance that intended to simplify the application of hedge accounting guidance and better align an entity's risk management activities and financial reporting for hedging relationships through changes to both the designation and measurement guidance for qualifying hedging relationships and the presentation of hedge results. The amendments expand and refine hedge accounting for both nonfinancial and financial risk components and align the recognition and presentation of the effects of the hedging instrument and the hedged item in the financial statements. The Company adopted this amended guidance during the second quarter of 2018 and applied it to the interest rate swap described in Note 9. The impact on the Company's consolidated financial statements was immaterial.

X
- Definition Description of business, basis of presentation and significant accounting policies + References No definition available. + Details
Name: | tdc_DescriptionOfBusinessBasisOfPresentationAndSignificantAccountingPoliciesTextBlock
Namespace Prefix: | tdc_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration

X
- Definition Description of Business, Basis of Presentation and Significant Accounting Policies [Abstract] + References No definition available. + Details
Name: | tdc_DescriptionofBusinessBasisofPresentationandSignificantAccountingPoliciesAbstract
Namespace Prefix: | tdc_
Data Type: | xbrli:stringItemType
Balance Type: | na
Period Type: | duration