XML 24 R11.htm IDEA: XBRL DOCUMENT v3.8.0.1
Revenue
3 Months Ended
Mar. 31, 2018
Revenue from Contract with Customer [Abstract]  
Revenue from Contract with Customer [Text Block]
REVENUE
Revenue is recognized upon transfer of control of promised products or services to customers in an amount that reflects the consideration to which Cadence expects to be entitled in exchange for promised goods or services. Cadence’s performance obligations are satisfied either over time or at a point in time. Revenue from performance obligations that transferred to customers over time accounted for approximately 90% of Cadence’s total revenue for the three months ended March 31, 2018.
Product and maintenance revenue includes Cadence’s licenses of time-based and perpetual software, sales of emulation hardware, licenses of per-use IP, and the related maintenance on these licenses and sales.
Service revenue includes revenue received for performing engineering services (which are generally not related to the functionality of other licensed products), customized IP on a fixed fee basis, and sales from cloud-based solutions that provide customers with software and services over a period of time.
Cadence enters into contracts that can include various combinations of licenses, products and services, some of which are distinct and are accounted for as separate performance obligations. For contracts with multiple performance obligations, Cadence allocates the transaction price of the contract to each performance obligation, generally on a relative basis using its standalone selling price. The stated contract value is generally the transaction price to be allocated to the separate performance obligations. Revenue is recognized net of any taxes collected from customers that are subsequently remitted to governmental authorities.
Nature of Products and Services
Software
Cadence’s time-based license arrangements grant customers the right to access and use all of the licensed products at the outset of an arrangement and updates are generally made available throughout the entire term of the arrangement, which is generally two to three years. Cadence’s updates provide continued access to evolving technology as customers’ designs migrate to more advanced nodes and as our customers’ technological requirements evolve. In addition, certain time-based license arrangements include remix rights and unspecified additional products that become commercially available during the term of the agreement. Payments are generally received in equal or near equal installments over the term of the agreement.
As explained in Note 1, the multiple software licenses, related updates, and technical support in these time-based arrangements constitute a single, combined performance obligation and revenue is recognized over the term of the license, commencing upon the later of the effective date of the arrangement or transfer of the software license. Remix rights are not an additional promised good or service in the contract, and where unspecified additional software product rights are part of the contract with the customer, such rights are accounted for as part of the single performance obligation that includes the licenses, updates, and technical support because such rights are provided for the same period of time and have the same time-based pattern of transfer to the customer.
Hardware
Cadence generally has two performance obligations in arrangements involving the sale or lease of hardware products. The first performance obligation is to transfer the hardware product (which includes software integral to the functionality of the hardware product). The second performance obligation is to provide maintenance on hardware and its embedded software, which includes rights to technical support, hardware repairs and software updates that are all provided over the same term and have the same time-based pattern of transfer to the customer. Transaction price allocated to the hardware product is generally recognized as revenue at the time of delivery because the customer obtains control of the product at that point in time. Cadence has concluded that control generally transfers at that point in time because the customer has title to the hardware, physical possession, and a present obligation to pay for the hardware. Transaction price allocated to maintenance is recognized as revenue ratably over the maintenance term. Payments for hardware contracts are generally received upon delivery of the hardware product.
IP
Cadence generally licenses IP under nonexclusive license agreements that provide usage rights for specific designs. In addition, for certain of Cadence’s IP license agreements, royalties are collected as customers ship their own products that incorporate Cadence IP. These arrangements generally have two performance obligations — transferring the licensed IP and associated maintenance, which includes rights to technical support and software updates that are all provided over the maintenance term and have a time-based pattern of transfer to the customer. Revenue allocated to the IP license is recognized at a point in time upon the later of the delivery of the IP or the beginning of the license period and revenue allocated to the maintenance is recognized over the maintenance term. Royalties are recognized as revenue in the quarter in which the applicable Cadence customer ships its products that incorporate Cadence IP. Payments for IP contracts are generally received upon delivery of the IP. Cadence customizes certain IP and revenue related to this customization is recognized as “Services” below.
Services
Revenue from service contracts is recognized over time, generally using costs incurred or hours expended to measure progress. Cadence has a history of accurately 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. Payments for services are generally due upon milestones in the contract or upon consumption of the hourly resources.
Cadence combines its products and technologies into five product groups 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 groups and services for the three months ended March 31, 2018:
 
Three Months Ended
 
March 31,
2018
 
April 1,
2017
Functional Verification, including Emulation and Prototyping Hardware
26
%
 
23
%
Digital IC Design and Signoff
30
%
 
29
%
Custom IC Design
26
%
 
26
%
System Interconnect and Analysis
9
%
 
10
%
IP
9
%
 
12
%
Total
100
%
 
100
%

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. The actual usage of Cadence’s products by these customers may differ and, if that proves to be the case, the revenue allocation in the table above would differ.
Significant Judgments
More judgments and estimates are required under Topic 606 than were required under Topic 605. Due to the complexity of certain contracts, the actual revenue recognition treatment required under Topic 606 for the Company’s arrangements may be dependent on contract-specific terms and may vary in some instances.
Cadence’s contracts with customers often include promises to transfer multiple software and/or IP licenses and services, including professional services, technical support services, and rights to unspecified updates to a customer. 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. As described in Note 1, 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 SSP for each distinct performance obligation. Cadence rarely licenses or sells products on a standalone basis, so Cadence is required to estimate the range of SSPs for each performance obligation. In instances where SSP is not directly observable because Cadence does not sell the license, product or service separately, Cadence determines the SSP using information that may include market conditions and other observable inputs. 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 maintenance and professional services that are separate performance obligations, and also for Cadence’s combined performance obligations that include software licenses, updates, and technical support. 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 sheet. Cadence records a contract asset when revenue is recognized prior to invoicing, or 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. For certain hardware and IP agreements with payment plans, Cadence records a receivable related to revenue recognized upon delivery because it has an unconditional right to invoice and receive payment in the future related to those deliveries.
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 March 31, 2018 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 March 31, 2018 were as follows:
 
As of
 
March 31,
2018
 
December 30,
2017
 
 
 
As Adjusted
 
(In thousands)
Contract assets
$
6,077

 
$
3,964

Deferred revenue
366,915

 
336,060


During the three months ended March 31, 2018, Cadence recognized $142.6 million of revenue that was included in the deferred revenue balance, as adjusted for Topic 606, at the beginning of the period. 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. The Company has elected to exclude the future royalty payments from the remaining performance obligations. Contracted but unsatisfied performance obligations were approximately $2.6 billion as of March 31, 2018, 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.
The amount of revenue recognized in the three months ended March 31, 2018 from performance obligations satisfied in previous periods was $6.2 million. This amount represents royalties earned during the period and excludes 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.
Deferred Sales Commissions
Cadence records an asset for the incremental costs of obtaining a contract with a customer, including direct sales commissions that are earned upon execution of the contract. Cadence uses the portfolio method to recognize the amortization expense related to these capitalized costs related to initial contracts and renewals and such expense is recognized over a period associated with the revenue of the related portfolio, which is generally two to three years for Cadence’s software arrangements and upon delivery for its hardware and IP arrangements. Incremental costs related to initial contracts and renewals are amortized over the same period because the commissions paid on both the initial contract and renewals are commensurate with one another. Total capitalized costs as of March 31, 2018 were $24.5 million and are included in other assets in Cadence’s condensed consolidated balance sheet. Amortization of these assets was $5.2 million during the three months ended March 31, 2018 and is included in sales and marketing expense in Cadence’s condensed consolidated income statement.