XML 18 R7.htm IDEA: XBRL DOCUMENT
v3.10.0.1

Significant Accounting Policies | 9 Months Ended
--- | ---
Sep. 30, 2018
Accounting Policies [Abstract] |
Significant Accounting Policies | Note 2 — Significant Accounting Policies During the three and nine-month periods ended September 30, 2018, there were no changes in the Company's significant accounting policies from its disclosures in the Annual Report on Form 10-K for the year ended December 31, 2017. For a discussion of the significant accounting policies, please see the Annual Report on Form 10-K for the fiscal year ended December 31, 2017, filed with the SEC on March 9, 2018. Revenue Recognition The Company adopted Accounting Standards Update, or ASU, No. 2014-09, Revenue from Contracts with Customers (Topic 606) and related ASU No. 2016-08, ASU No. 2016-10, ASU No. 2016-12 and ASU No. 2016-20, which provide supplementary guidance, and clarifications, effective January 1, 2018. The results for the reporting period beginning after January 1, 2018, are presented in accordance with the new standard, although comparative information for the prior year has not been restated and continues to be reported under the accounting standards and policies in effect for those periods. Adoption of the new standard did not have a significant impact on the current period revenues or on the prior year Consolidated Financial Statements. No transition adjustment was required to the retained earnings of the Company as of January 1, 2018. Under the new standard revenue is recognized as follows: Revenue is recognized upon transfer of control of promised products or services to customers in an amount that reflects the consideration the Company expects to receive in exchange for those products or services. The Company determines revenue recognition through the following steps:
| • | Identification of the contract, or contracts, with a customer
| • | Identification of the performance obligations in the contract
| • | Determination of the transaction price
| • | Allocation of the transaction price to the performance obligations in the contract
| • | Recognition of revenue when, or as, we satisfy a performance obligation
The Company generates most of its revenue by supplying standard hardware products, which must be programmed before they can be used in an application. The Company also generates revenue from licensing their intellectual property or IP, software tools and royalty from licensing its technology. Product Revenue The Company recognizes hardware product revenue at the point of time when control of products is transferred to the customers. Intellectual Property and Software License Revenue The Company recognizes IP and Software License revenue at the point of time when the control of IP or software license has been transferred. Maintenance Revenue The Company recognizes revenue from maintenance ratably over the term of the underlying maintenance contract term. Renewals of maintenance contracts create new performance obligations that are satisfied over the term with the revenues recognized ratably over the term. Royalty Revenue The Company recognizes royalty revenue when the later of the following events occurs: a) The subsequent sale or usage occurs. b) The performance obligation to which some or all of the sales-based royalty has been allocated has been satisfied. Contracts with Multiple Performance Obligations Some of the IP and Software Licensing contracts with customers contain multiple performance obligations. For these contracts, the Company accounts for individual performance obligations separately if they are distinct. The transaction price is allocated to the separate performance obligations on a relative standalone selling price basis. We determine the standalone selling prices based on our overall pricing objectives, taking into consideration market conditions and other factors, including the value of our contracts, type of the customer, customer tier, type of the technology used, customer demographics, geographic locations, and other factors. Deferred Revenue When the Company receives consideration, or such consideration is unconditionally due, prior to transferring goods or services to the customer under the terms of a sales contract, the Company records deferred revenue, which represents a contract liability. The Company recognizes deferred revenue as net sales once control of goods and/or services have been transferred to the customer and all revenue recognition criteria have been met and any constraints have been resolved. Assets Recognized from Costs to Obtain a Contract with a Customer The Company recognizes an asset for the incremental costs of obtaining a contract with a customer if it expects the benefit of those costs to be longer than one year. Practical expedients and exemptions (i) Taxes collected from customers and remitted to government authorities and that are related to the sales of the Company’s products are excluded from revenues. (ii) Sales commissions are expensed when incurred because the amortization period would have been one year or less. These costs are recorded in selling, general and administrative expense in the Condensed Consolidated Statements of Income. (iii) The Company does not disclose the value of unsatisfied performance obligations for (i) contracts with original expected lengths of one year or less or (ii) contracts for which the Company recognizes revenue at the amount to which it has the right to invoice for the services performed. New Accounting Pronouncements Recently adopted accounting pronouncements: In May 2014, the Financial Accounting Standards Board, or FASB issued ASU No. 2014-09, Revenue from Contracts with Customers (Topic 606), which supersedes nearly all existing revenue recognition guidance under U.S. GAAP. The core principle of ASU No. 2014-09 is to recognize revenues when promised goods or services are transferred to customers in an amount that reflects the consideration to which an entity expects to be entitled for those goods or services. ASU No. 2014-09 defines a five-step process to achieve this core principle and, in doing so, more judgment and estimates may be required within the revenue recognition process than are required under existing GAAP. In applying this new guidance to contracts within its scope, an entity will: (1) identify the contract(s) with a customer, (2) identify the performance obligation 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 entity satisfies a performance obligation. Additionally, this new guidance would require significantly expanded disclosures about revenue. The new standard allows for two transition methods: (i) a full retrospective method applied to each prior reporting period presented, or (ii) a modified retrospective method applied with the cumulative effect of adoption recognized on adoption. ASU 2014-09 is effective for annual reporting periods beginning after December 15, 2017, including interim reporting periods within that reporting period. In March, April, May and December 2016, the FASB issued ASU Nos. 2016-08, 2016-10, 2016-12 and 2016-20, respectively, which provide supplemental guidance and clarification to ASU No. 2014-09. The Company adopted ASU No. 2014-09 and other supplementary guidance effective January 1, 2018 and applied the modified retrospective approach for the transition. After evaluation of the impact of the transition, the Company determined that this new standard has no impact on the revenues of the prior years and no adjustments are required to the Company's retained earnings as of January 1, 2018. In August 2016, the FASB issued ASU No. 2016-15, Statement of Cash Flows (Topic 230): Classification of Certain Cash Receipts and Cash Payments. This update clarifies how certain cash receipts and cash payments are presented and classified in the statement of cash flows. This ASU is effective for public business entities for fiscal years beginning after December 15, 2017, and for interim periods therein with early adoption permitted and must be applied retrospectively to all periods presented. The Company adopted this Accounting Standard effective January 1, 2018. The Company evaluated the impact on the financial statements and determined that the adoption of ASU No. 2016-15 had no impact on the consolidated financial statements. In October 2016, the FASB issued ASU No. 2016-16, Income Taxes (Topic 740): Intra-Entity transfers of assets other than inventory. This update removes the requirement under which the income tax consequences of intra-entity transfers are deferred until the assets are ultimately sold to an outside party, except for transfers of inventory. The tax consequences of such transfers would be recognized in tax expense when the transfers occur. The standard is effective for annual reporting periods beginning after December 15, 2017, and interim periods within those annual periods. The Company adopted this Accounting Standard effective January 1, 2018 and determined that the adoption of ASU No. 2016-16 had no impact on the consolidated financial statements. In May 2017, the FASB issued ASU No. 2017-09, Compensation-Stock Compensation (Topic 718). ASU No. 2017-09 provides clarification on when modification accounting should be used for changes to the terms or conditions of a share-based payment award. This ASU does not change the accounting for modifications but clarifies that modification accounting guidance should only be applied if there is a change to the value, vesting conditions or award classification and would not be required if the changes are considered non-substantive. The amendments of this ASU are effective for reporting periods beginning after December 15, 2017. The Company adopted this Accounting Standard effective January 1, 2018. The Company evaluated the impact on the financial statements and determined that the adoption of ASU No. 2017-09 had no impact on the consolidated financial statements. Recently issued accounting pronouncements not yet adopted: In February 2016, the FASB issued ASU No. 2016-02, Leases. The new standard establishes a right-of-use or ROU model that requires a lessee to record a ROU asset and a lease liability on the balance sheet for all leases with terms longer than 12 months. Leases will be classified as either finance or operating, with classification affecting the pattern of expense recognition in the income statement. The new standard is effective for fiscal years beginning after December 15, 2018, including interim periods within those fiscal years. The FASB subsequently issued the following amendments to ASU No. 2016-02, which have the same effective date and transition date of January 1, 2019, and which we collectively refer to as the new leasing standards:
| • | ASU No. 2018-10, Codification Improvements to Topic 842, Leases, which amends certain narrow aspects of the guidance issued in ASU N0. 2016-02.
| • | ASU No. 2018-11, Leases (Topic 842): Targeted improvements, which allows for a transition approach to initially apply ASU No. 2016-02 at the adoption date and recognize a cumulative-effect adjustment to the opening balance of retained earnings in the period of adoption as well as an additional practical expedient for lessors to not separate non-lease components from the associated lease components.
The Company is currently evaluating the impact of our pending adoption of the new leasing standards on the consolidated financial statements. In February 2018, FASB issued ASU No. 2018-02, Income Statement - Reporting Comprehensive Income. The new standard provides companies with an option to reclassify stranded tax effects resulting from enactment of the Tax Cuts and Jobs Act, or TCJA, from accumulated other comprehensive income to retained earnings. The guidance will be effective for the Company beginning in the first quarter of 2019 with early adoption permitted, and would be applied either in the period of adoption or retrospectively to each period (or periods) in which the effect of the change in the tax rate as a result of TCJA is recognized. The Company does not expect the adoption of this ASU to have a material impact on its results of operations, financial position and cash flows. In March 2018, FASB issued ASU No. 2018-05, Income Taxes (Topic 740). The new standard allows to insert the SEC’s interpretive guidance from Staff Accounting Bulletin No. 118 into the income tax accounting codification under U.S. GAAP. The ASU permits companies to use provisional amounts for certain income tax effects of the Tax Act during a one-year measurement period. The provisional accounting impacts for the Company may change in future reporting periods until the accounting analysis is finalized, which will occur no later than the first quarter of fiscal 2019. The Company is currently evaluating the impact of our pending adoption of the new standard on the consolidated financial statements. In June 2018, the FASB issued ASU No. 2018-07, Improvements to nonemployee share-based payment accounting. Currently, share-based payments to nonemployees are accounted for under Subtopic 505-50, which significantly differs from the guidance for share-based payments to employees under Topic 718. This ASU supersedes Subtopic 505-50 by expanding the scope of Topic 718 to include nonemployee awards and generally aligning the accounting for nonemployee awards with the accounting for employee awards. The effective date for public companies is for fiscal years beginning after December 15, 2018, and interim periods within those fiscal years. For all other entities, the effective date is fiscal years beginning after December 15, 2019. The Company is currently evaluating the impact of our pending adoption of the new standard on the consolidated financial statements. In August 2018 the FASB issued ASU No. 2018-13, Fair Value Measurement (Topic 820): Disclosure Framework - Changes to the Disclosure Requirements for Fair Value Measurement. This new standard modifies certain disclosure requirements on fair value measurements. This new standard will be effective for public companies on January 1, 2020. The Company is currently evaluating the impact of our pending adoption of the new standard on the consolidated financial statements. Other new accounting pronouncements are disclosed on the Annual Report on Form 10-K for the fiscal year ended December 31, 2017 filed with the SEC on March 9, 2018.

X
- References No definition available. + Details
Name: | us-gaap_AccountingPoliciesAbstract
Namespace Prefix: | us-gaap_
Data Type: | xbrli:stringItemType
Balance Type: | na
Period Type: | duration

X
- Definition The entire disclosure for all significant accounting policies of the reporting entity. + References Reference 1: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -URI http://asc.fasb.org/topic&trid=2122369 + Details
Name: | us-gaap_SignificantAccountingPoliciesTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration