XML 24 R11.htm IDEA: XBRL DOCUMENT
v3.19.2

Revenue | 6 Months Ended
--- | ---
Jun. 29, 2019
Revenue from Contract with Customer [Abstract] |
REVENUE | REVENUE Cadence combines its products into five categories related to major design activities. The following table shows the percentage of product and related maintenance revenue contributed by each of Cadence’s five product categories and services for the three and six months ended June 29, 2019 and June 30, 2018:
| Three Months Ended |  | Six Months Ended
| June 29, 2019 |  | June 30, 2018 |  | June 29, 2019 |  | June 30, 2018
Functional Verification, including Emulation and Prototyping Hardware 1 | 22 | % |  | 23 | % |  | 23 | % |  | 25 | %
Digital IC Design and Signoff | 31 | % |  | 30 | % |  | 31 | % |  | 29 | %
Custom IC Design and Simulation | 26 | % |  | 26 | % |  | 26 | % |  | 26 | %
System Interconnect and Analysis | 10 | % |  | 9 | % |  | 9 | % |  | 9 | %
IP | 11 | % |  | 12 | % |  | 11 | % |  | 11 | %
Total | 100 | % |  | 100 | % |  | 100 | % |  | 100 | %
_____________ 1 Includes immaterial amount of revenue accounted for under Topic 842. Revenue by product group fluctuates from period to period based on demand for products and services, and Cadence’s available resources to deliver them. Certain of Cadence’s licensing arrangements allow customers the ability to remix among software products. Cadence also has arrangements with customers that include a combination of products, with the actual product selection and number of licensed users to be determined at a later date. For these arrangements, Cadence estimates the allocation of the revenue to product groups based upon the expected usage of products. Significant Judgments Cadence’s contracts with customers often include promises to transfer to a customer multiple software and/or IP licenses and services, including professional services, technical support services, and rights to unspecified updates. Determining whether licenses and services are distinct performance obligations that should be accounted for separately, or not distinct and thus accounted for together, requires significant judgment. In some arrangements, such as most of Cadence’s IP license arrangements, Cadence has concluded that the licenses and associated services are distinct from each other. In others, like Cadence’s time-based software arrangements, the licenses and certain services are not distinct from each other. Cadence’s time-based software arrangements include multiple software licenses and updates to the licensed software products, as well as technical support, and Cadence has concluded that these promised goods and services are a single, combined performance obligation. Judgment is required to determine the standalone selling price (“SSP”) for each distinct performance obligation. Cadence rarely licenses or sells products on a standalone basis, so Cadence is required to estimate the SSP for each performance obligation. In instances where the SSP is not directly observable because Cadence does not sell the license, product or service separately, Cadence determines the SSP using information that maximizes the use of observable inputs and may include market conditions. Cadence typically has more than one SSP for individual performance obligations due to the stratification of those items by classes of customers and circumstances. In these instances, Cadence may use information such as the size of the customer and geographic region of the customer in determining the SSP. Revenue is recognized over time for Cadence’s combined performance obligations that include software licenses, updates, technical support and maintenance that are separate performance obligations with the same term. For Cadence’s professional services, revenue is recognized over time, generally using costs incurred or hours expended to measure progress. Judgment is required in estimating project status and the costs necessary to complete projects. A number of internal and external factors can affect these estimates, including labor rates, utilization and efficiency variances and specification and testing requirement changes. For Cadence’s other performance obligations recognized over time, revenue is generally recognized using a time-based measure of progress reflecting generally consistent efforts to satisfy those performance obligations throughout the arrangement term. If a group of agreements are so closely related that they are, in effect, part of a single arrangement, such agreements are deemed to be one arrangement for revenue recognition purposes. Cadence exercises significant judgment to evaluate the relevant facts and circumstances in determining whether the separate agreements should be accounted for separately or as, in substance, a single arrangement. Cadence’s judgments about whether a group of contracts comprise a single arrangement can affect the allocation of consideration to the distinct performance obligations, which could have an effect on results of operations for the periods involved. Cadence is required to estimate the total consideration expected to be received from contracts with customers. In limited circumstances, the consideration expected to be received is variable based on the specific terms of the contract or based on Cadence’s expectations of the term of the contract. Generally, Cadence has not experienced significant returns or refunds to customers. These estimates require significant judgment and the change in these estimates could have an effect on its results of operations during the periods involved. Contract Balances The timing of revenue recognition may differ from the timing of invoicing to customers, and these timing differences result in receivables, contract assets, or contract liabilities (deferred revenue) on Cadence’s condensed consolidated balance sheets. For certain software, hardware and IP agreements with payment plans, Cadence records an unbilled receivable related to revenue recognized upon transfer of control because it has an unconditional right to invoice and receive payment in the future related to those transferred products or services. Cadence records a contract asset when revenue is recognized prior to invoicing and Cadence does not have the unconditional right to invoice or retains performance risk with respect to that performance obligation. Cadence records deferred revenue when revenue is recognized subsequent to invoicing. For Cadence’s time-based software agreements, customers are generally invoiced in equal, quarterly amounts, although some customers prefer to be invoiced in single or annual amounts. The contract assets indicated below are presented as prepaid expenses and other in the condensed consolidated balance sheet and primarily relate to Cadence’s rights to consideration for work completed but not billed as of June 29, 2019 on services and customized IP contracts. The contract assets are transferred to receivables when the rights become unconditional, usually upon completion of a milestone. Cadence’s contract balances as of June 29, 2019 and December 29, 2018 were as follows:
| As of
| June 29, 2019 |  | December 29, 2018
| (In thousands)
Contract assets | $ | 10,501 |  |  | $ | 10,055 |
Deferred revenue | 420,872 |  |  | 401,174 |
Cadence recognized revenue of $88.1 million and $246.0 million during the three and six months ended June 29, 2019, and $67.7 million and $210.3 million during the three and six months ended June 30, 2018, respectively, that was included in the deferred revenue balance at the beginning of each fiscal year. All other activity in deferred revenue is due to the timing of invoices in relation to the timing of revenue as described above. Revenue allocated to remaining performance obligations represents the transaction price allocated to the performance obligations that are unsatisfied, or partially unsatisfied, which includes unearned revenue and amounts that will be invoiced and recognized as revenue in future periods. Cadence has elected to exclude the future royalty payments from the remaining performance obligations. Contracted but unsatisfied performance obligations were approximately $2.8 billion as of June 29, 2019, of which Cadence expects to recognize approximately 60% of the revenue over the next 12 months and the remainder thereafter. Payment terms and conditions vary by contract type, although terms generally include a requirement of payment within 30 to 60 days. In instances where the timing of revenue recognition differs from the timing of invoicing, Cadence has determined that its contracts generally do not include a significant financing component. The primary purpose of invoicing terms is to provide customers with simplified and predictable ways of purchasing Cadence’s products and services, and not to facilitate financing arrangements. Cadence recognized revenue of $8.2 million and $16.7 million during the three and six months ended June 29, 2019, and $8.3 million and $14.5 million during the three and six months ended June 30, 2018, respectively, from performance obligations satisfied in previous periods. These amounts represent royalties earned during the period and exclude contracts with nonrefundable prepaid royalties. Nonrefundable prepaid royalties are recognized upon delivery of the IP because Cadence’s right to the consideration is not contingent upon customers’ future shipments.

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

X
- Definition The entire disclosure of revenue from contract with customer to transfer good or service and to transfer nonfinancial asset. Includes, but is not limited to, disaggregation of revenue, credit loss recognized from contract with customer, judgment and change in judgment related to contract with customer, and asset recognized from cost incurred to obtain or fulfill contract with customer. Excludes insurance and lease contracts. + References Reference 1: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -URI http://asc.fasb.org/topic&trid=49130388 Reference 2: 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_RevenueFromContractWithCustomerTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration