XML 21 R10.htm IDEA: XBRL DOCUMENT
v3.8.0.1

Revenue from Contracts with Customers (Notes) | 3 Months Ended
--- | ---
Mar. 31, 2018
Revenue Recognition from Contracts with Customers [Abstract] |
Revenue from Contract with Customer [Text Block] | Revenue Recognition The Company recognizes revenue upon transfer of control of promised goods and services in an amount that reflects the consideration it expects to receive in exchange for those goods and services. Unless indicated otherwise below, all of the goods and services are distinct and are accounted for as separate performance obligations. Where an arrangement includes multiple performance obligations, the transaction price is allocated to these on a relative standalone selling prices basis. The Company has established standalone selling prices for all of its offerings - specifically, a same pricing methodology is consistently applied to all licensing arrangements; all services offerings are priced within tightly controlled bands and all contracts that include support and maintenance state a renewal rate or price that is systematically enforced. Rambus’ revenue consists of royalty, product and contract and other revenue. Royalty revenue consists of patent and technology license royalties. Products consist of memory buffer chipsets sold directly and indirectly to module manufacturers and OEMs worldwide through multiple channels, including our direct sales force and distributors. Contract and other revenue consists of software license fees, engineering fees associated with integration of Rambus’ technology solutions into its customers’ products and support and maintenance fees. 1.Royalty Revenue Rambus’ patent and technology licensing arrangements generally range between 1 and 7 years in duration and generally grant the licensee the right to use the Company's entire IP portfolio as it evolves over time. These arrangements do not typically grant the licensee the right to terminate for convenience and where such rights exist, termination is prospective, with no refund of fees already paid by the licensee. There is no interdependency or interrelation between the IP included in the portfolio licensed upon contract inception and any IP subsequently made available to the licensee, and the Company would be able to fulfill its promises by transferring the portfolio and the additional IP use rights independently. However, the numbers of additions to, and removals from the portfolio (for example when a patent expires and renewal is not granted to the Company) in any given period have historically been relatively consistent; as such, the Company does not allocate the transaction price between the rights granted at contract inception and those subsequently granted over time as a function of these additions. Patent and technology licensing arrangements result in fixed payments received over time, with guaranteed minimum payments on occasion, variable payments calculated based on the licensee’s sale or use of the IP, or a mix of fixed and variable payments.
• | For fixed-fee arrangements (including arrangements that include minimum guaranteed amounts), variable royalty arrangements that the Company has concluded are fixed in substance and the fixed portion of hybrid fixed/variable arrangements, the Company recognizes revenue upon control over the underlying IP use right transferring to the licensee, net of the effect of significant financing components calculated using customer-specific, risk-adjusted lending rates ranging between 3% and 6%, with the related interest income being recognized over time on an effective rate basis. Where a licensee has the contractual right to terminate a fixed-fee arrangement for convenience without any substantive penalty payable upon such termination, the Company applies the guidance in the New Revenue Standard to the duration of the contract in which the parties have present enforceable rights and obligations and only recognizes revenue for amounts that are due and payable.
• | For variable arrangements, the Company recognizes revenue based on an estimate of the licensee’s sale or usage of the IP during the period of reference, typically quarterly, with a true-up being recorded when the Company receives the actual royalty report from the licensee.
2.Product Revenue Product revenue is recognized upon shipment of product to customers, net of accruals for estimated sales returns and allowances, and to distributors, net of accruals for price protection and rights of return on products unsold by the distributors. To date, none of these accruals have been significant. The Company transacts with direct customers primarily pursuant to standard purchase orders for delivery of products and generally allows customers to cancel or change purchase orders within limited notice periods prior to the scheduled shipment date. 3.Contract and Other Revenue Contract and other revenue consists of software license fees, engineering fees associated with integration of Rambus’ technology solutions into its customers’ related support and maintenance. An initial software arrangement generally consists of a term-based or perpetual license, significant software customization services and support and maintenance services that include post-implementation customer support and the right to unspecified software updates and enhancements on a when and if available basis. The Company recognizes the license and customization services revenue based on man-days incurred during the reporting period as compared to the estimated total man-days necessary for each contract, and the support and maintenance revenue ratably over term. The Company recognizes license renewal revenue at the beginning of the renewal period. The Company recognizes revenue from professional services purchased in addition to an initial software arrangement on a cumulative catch-up basis if these services are not distinct from the services provided as part of the initial software arrangement, or as a separate contract if these services are distinct. During the first quarter of 2016, the Company acquired Smart Card Software Ltd., which included Bell Identification Ltd. (Payment Product Group) and Ecebs Ltd. (Ticketing Products Group), which transact mostly in software and Software-as-a-Service arrangements, respectively. The Company's Payment Product Group derives a significant portion of its revenue from heavily customized software in the mobile market, whereby the Payment Product Group’s software solution interacts with third-party solutions and other payment platforms to provide the functionality the customer requires. Historically, these third-party solutions have evolved at a rapid pace, with the Payment Product Group being required to deliver as part of its support and maintenance services the patches and updates needed to maintain the functionality of its own software offering. As the utility of the solution to the end customer erodes very quickly without these updates, these are viewed as critical and the customized software solution and updates are not separately identifiable. As such, these arrangements are treated as a single performance obligation; revenue is deferred until completion of the customization services, and recognized ratably over the committed support and maintenance term, typically ranging from 1 year to 3 years. The Company's Ticketing Products Group primarily derives revenue from ticketing services arrangements that systematically consist of a software component, support and maintenance, managed services and hosting services. The software could be hosted by third-party hosting service providers or the Company. All arrangements entered into subsequent to the acquisition preclude customers from taking possession of the software at any time during the hosting term and the Company has concluded that should a customer that was under contract as of the acquisition date ever request possession of the software, the Ticketing Products Group would have the ability to charge the customer, and enforce a claim to payment of a substantive fee in exchange for such right, and that the costs of setting up the environment needed to run the software would act as a significant disincentive to the customer taking possession of the software. Based on the above, the Company concluded that these services are a single performance obligation, with customers simultaneously receiving and consuming the benefits provided by Ticketing Products Group’s performance, and recognize ticketing services revenue ratably over term, commencing upon completion of setup activities. The Company recognizes setup fees upon completion. While these activities do not transfer a service to the customer, the Company elected not to defer and amortize these fees over the expected duration of the customer relationship owing to the immateriality of the amounts charged. Significant Judgments Historically and with the exception noted below, no significant judgment has generally been required in determining the amount and timing of revenue from the Company's contracts with customers.
• | The Company has adequate tools and controls in place, and substantial experience and expertise in timely and accurately tracking man-days incurred in completing customization and other professional services, and quantifying changes in estimates.
Key estimates used in recognizing revenue predominantly consist of the following:
• | All fixed-fee arrangements result in cash being received after control over the underlying IP use right has transferred to the licensee, and over a period exceeding a year. As such, all these arrangements include a significant financing component. The Company calculates a customer-specific lending rate using a Daily Treasury Yield Curve Rate that changes depending on the date on which the licensing arrangement was entered into and the term (in years) of the arrangement, and takes into consideration a licensee-specific risk profile determined based on a review of the licensee’s “Full Company View” Dun & Bradstreet report obtained on the date the licensing arrangement was signed by the parties, with a risk premium being added to the Daily Treasury Yield Curve Rate considering the overall business risk, financing strength and risk indicators, as listed.
• | The Company recognizes revenue on variable fee licensing arrangements on the basis of estimates. In connection with the adoption of the New Revenue Standard, the Company has set up specific procedures and controls to ensure timely and accurate quantification of variable royalties, and implemented new systems to enable the preparation of the estimates and reporting of the financial information required by the New Revenue Standard.
Contract Balances Timing of revenue recognition may differ from the timing of invoicing to the Company's customers. The Company records contract assets when revenue is recognized prior to invoicing, and a contract liability revenue is recognized subsequent to invoicing. The contract assets are primarily related to the Company’s fixed fee IP licensing arrangements and rights to consideration for performance obligations delivered but not billed as of March 31, 2018. The contract assets are transferred to receivables when the billing occurs. The Company’s contract balances were as follows:
| As of
(In thousands) | March 31, 2018 |  | January 1, 2018
Unbilled receivables | $ | 771,002 |  |  | $ | 818,371 |
Deferred revenue | 16,985 |  |  | 20,737 |
During the three months ended March 31, 2018, the Company recognized $10.7 million of revenue that was included in the contract balances, as adjusted for ASC 606, at the beginning of the period. 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. Contracted but unsatisfied performance obligations were approximately $32.7 million as of March 31, 2018, which the Company primarily expects to recognize over the next 2 years.

X
- Definition Revenue Recognition from Contracts with Customers [Abstract] + References No definition available. + Details
Name: | rmbs_RevenueRecognitionfromContractswithCustomersAbstract
Namespace Prefix: | rmbs_
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://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -URI http://asc.fasb.org/topic&trid=2122369 Reference 2: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -URI http://asc.fasb.org/topic&trid=49130388 + Details
Name: | us-gaap_RevenueFromContractWithCustomerTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration