XML 37 R25.htm IDEA: XBRL DOCUMENT
v3.10.0.1

Summary of Significant Accounting Policies (Policies) | 3 Months Ended
--- | ---
Jan. 31, 2019
Accounting Policies [Abstract] |
Use of Estimates | Use of Estimates. To prepare financial statements in conformity with U.S. GAAP, management must make estimates and assumptions that affect the amounts reported in the unaudited condensed consolidated financial statements and accompanying notes. Actual results could differ from these estimates and may result in material effects on the Company’s operating results and financial position.
Principles of Consolidation | Principles of Consolidation. The unaudited condensed consolidated financial statements include the accounts of the Company and all of its subsidiaries. All intercompany accounts and transactions have been eliminated.
Fiscal Year End | Fiscal Year End. The Company’s fiscal year generally ends on the Saturday nearest to October 31 and consists of 52 weeks, with the exception that every five or six years, the Company has a 53-week year. When a 53-week year occurs, the Company includes the additional week in the first quarter to realign fiscal quarters with calendar quarters. Fiscal 2019 is a 52-week year and will end on November 2, 2019. Fiscal 2018 was a 53-week year and ended on November 3, 2018. The results of operations for the first quarters of fiscal 2019 and 2018 included 13 weeks and 14 weeks, respectively, and ended on February 2, 2019 and February 3, 2018, respectively. For presentation purposes, the unaudited condensed consolidated financial statements and accompanying notes refer to the closest calendar month end.
Segment Reporting | Segment Reporting. Effective in fiscal 2019, the Company realigned its business to evaluate the results of its Software Integrity business separately from Synopsys’ traditional electronic design automation (EDA) and semiconductor IP business. The Chief Operating Decision Makers (CODMs) now regularly review disaggregated information for the following two reportable segments: (1) Semiconductor & System Design, which includes EDA tools, IP products, system integration solutions and associated services, and (2) Software Integrity, which includes security and quality solutions for software development across many industries. Synopsys' CODMs are its two co-Chief Executive Officers. Historical segment disclosures have been recast to retrospectively reflect the change from one to two reportable segments.
Goodwill | Goodwill. Effective in the first quarter of fiscal 2019, with the change in the Company’s reportable segments, the Company has determined there are now two reporting units, requiring goodwill to be allocated to the two reporting units using a relative fair value method. Goodwill represents the excess of the aggregate purchase price over the fair value of the net tangible and identifiable intangible assets acquired by the Company. The carrying amount of goodwill at each reporting unit is tested for impairment annually as of October 31, or more frequently if facts and circumstances warrant a review. As a result of changes to the Company's segment reporting, the Company conducted a quantitative impairment test for each of its reporting units and concluded that there was no impairment. The Company performs either a qualitative or quantitative analysis when testing a reporting unit’s goodwill for impairment. A qualitative goodwill impairment test is performed when the fair value of a reporting unit historically has significantly exceeded the carrying value of its net assets and based on current operations is expected to continue to do so. Otherwise, the Company is required to conduct a quantitative impairment test for each reporting unit and estimates the fair value of each reporting unit using a combination of a discounted cash flow analysis and a market approach based on market multiples. The discount rate used in an income approach is based on the Company's weighted-average cost of capital and may be adjusted for the relevant risks pertaining to projecting future cash flows. If the fair value of a reporting unit is less than its carrying value, a goodwill impairment charge is recorded for the difference. Refer to Note 3. Goodwill and Intangible Assets for a discussion of the change in reporting units as related to the realignment of the Company’s segments.
Revenue Recognition | Revenue Recognition. In May 2014, the Financial Accounting Standards Board (FASB) issued Accounting Standards Codification (ASC 606), "Revenue from Contracts with Customers," which supersedes the revenue recognition requirements in “Revenue Recognition (ASC 605).” The new guidance creates a single, principle-based model for revenue recognition that is intended to expand and improve companies' revenue disclosures. For revenue recognition policies under ASC 605, refer to Note 2 - Summary of Significant Accounting Policies in the Company’s Annual Report on Form 10-K for the year ended October 31, 2018. ASC 606 requires a company to recognize revenue when goods are transferred or services are provided to customers in an amount that reflects the consideration to which the company expects to be entitled to in exchange for those goods or services. ASC 606 also requires disclosures enabling users of financial statements to understand the nature, amount, timing, and uncertainty of revenue and cash flows arising from contracts with customers. The FASB has issued several amendments to ASC 606, including amendments that deferred the initially proposed adoption date and clarified accounting for licenses of intellectual property and identifying performance obligations. The Company adopted ASC 606 at the beginning of fiscal 2019 using the modified retrospective transition method. Under this method, periods prior to the adoption date are not adjusted and continue to be reported under the revenue accounting literature in effect during those periods. The Company evaluated contracts that were in effect at the beginning of fiscal 2019 as if they had been accounted for under ASC 606 from the contract inception and summarized the most significant adoption impacts as follows:
• | Revenue for certain ongoing contracts that was previously deferred would have been recognized in the periods prior to adoption under ASC 606. Therefore, upon adoption, the Company recorded the following adjustments to the beginning balances to reflect the amount of revenue that will no longer be recognized in future periods for such contracts: an increase to retained earnings of $265.1 million, a decrease to unbilled receivables of $27.4 million, an increase to contract assets of $126.9 million, and a decrease in deferred revenue of $165.6 million.
• | The Company capitalized $73.8 million of incremental costs for obtaining contracts with customers at the adoption date with a corresponding adjustment to retained earnings, and is amortizing these costs over the contract term.
• | The Company recorded an increase in its opening deferred tax liability of $81.4 million, with a corresponding adjustment to retained earnings, to record the tax effect of the above adjustments.
The impacts of adopting ASC 606 on the Company's unaudited condensed consolidated financial statements for the quarter are summarized in the tables below. Balance Sheet Accounts The following table summarizes the effects of adopting ASC 606 on certain account balances of the unaudited condensed consolidated balance sheet that were impacted as of January 31, 2019:
| As reported under ASC 606 |  | Adjustments |  | Adjusted balance under ASC 605
| (in thousands)
Receivables, net | $ | 762,292 |  |  | $ | 73,234 |  |  | $ | 835,526 |
Prepaid and other current assets | 249,927 |  |  | (167,729 | ) |  | 82,198 |
Deferred income taxes | 337,824 |  |  | 70,362 |  |  | 408,186 |
Other long-term assets | 358,527 |  |  | (95,715 | ) |  | 262,812 |
Accounts payable and other accrued liabilities | 335,341 |  |  | (10,713 | ) |  | 324,628 |
Deferred revenue | 1,262,201 |  |  | 112,374 |  |  | 1,374,575 |
Long-term deferred revenue | 63,013 |  |  | 80,614 |  |  | 143,627 |
Other long-term liabilities (1) | 296,098 |  |  | (16,671 | ) |  | 279,427 |
Retained earnings | 2,820,910 |  |  | (285,452 | ) |  | 2,535,458 |
(1) Includes long-term deferred tax liabilities. Statements of Operations The following table summarizes the effects of adopting ASC 606 on the unaudited condensed consolidated statements of operations for the three months ended January 31, 2019:
| As reported under ASC 606 |  | Adjustments |  | Adjusted under ASC 605
| (in thousands, except per share amounts)
Revenue: |  |  |  |  |
Time-based products | $ | 553,716 |  |  | $ | 15,856 |  |  | $ | 569,572 |
Upfront products | 130,513 |  |  | (16,786 | ) |  | 113,727 |
Maintenance and service | 136,172 |  |  | (21,414 | ) |  | 114,758 |
Total revenue | 820,401 |  |  | (22,344 | ) |  | 798,057 |
Cost of Revenue: |  |  |  |  |  |
Products | 116,620 |  |  | — |  |  | 116,620 |
Maintenance and service | 58,829 |  |  | — |  |  | 58,829 |
Amortization of intangible assets | 17,443 |  |  | — |  |  | 17,443 |
Total cost of revenue | 192,892 |  |  | — |  |  | 192,892 |
Gross margin | 627,509 |  |  | (22,344 | ) |  | 605,165 |
Operating expenses: |  |  |  |  |  |
Research and development | 271,326 |  |  | — |  |  | 271,326 |
Sales and marketing | 155,959 |  |  | 11,184 |  |  | 167,143 |
General and administrative | 42,061 |  |  | — |  |  | 42,061 |
Amortization of intangible assets | 10,784 |  |  | — |  |  | 10,784 |
Restructuring | (35 | ) |  | — |  |  | (35 | )
Total operating expenses | 480,095 |  |  | 11,184 |  |  | 491,279 |
Operating income | 147,414 |  |  | (33,528 | ) |  | 113,886 |
Other income (expense), net | (359 | ) |  | — |  |  | (359 | )
Income (loss) before provision for income taxes | 147,055 |  |  | (33,528 | ) |  | 113,527 |
Provision (benefit) for income taxes | (6,459 | ) |  | (5,670 | ) |  | (12,129 | )
Net income (loss) | $ | 153,514 |  |  | $ | (27,858 | ) |  | $ | 125,656 |
Net income (loss) per share: |  |  |  |  | — |
Basic | $ | 1.03 |  |  | $ | (0.19 | ) |  | $ | 0.84 |
Diluted | $ | 1.01 |  |  | $ | (0.19 | ) |  | $ | 0.82 |
Shares used in computing per share amounts: |  |  |  |  | — |
Basic | 149,288 |  |  |  |  | 149,288 |
Diluted | 152,661 |  |  |  |  | 152,661 |
Statements of Cash Flows Adoption of ASC 606 had no impact to cash from or used in operating, financing, or investing activities on the unaudited condensed consolidated cash flows statements. Revenue Policy The core principle of ASC 606 is to recognize revenue for the transfer of services or products to customers in an amount that reflects the consideration to which the Company expects to be entitled in exchange for those services or products. The principle is achieved through the following five-step approach:
• | Identification of the contract, or contracts, with the customer
• | Identification of the performance obligation 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, the Company satisfies a performance obligation
Nature of Products and Services The Company generates revenue from the sale of products that include software licenses and, to a lesser extent, hardware products, maintenance and services. The various types are set forth below. Electronic Design Automation Software license revenue consists of fees associated with the licensing of the Company's software primarily through Technology Subscription License (TSL) contracts. TSLs are time-based licenses for a finite term and generally provide the customer with limited rights to receive, or to exchange certain quantities of licensed software for, unspecified future technology. The majority of the Company's arrangements are TSLs due to the nature of its business and customer requirements. In addition to the licenses, the arrangements also include: post-contract customer support, which includes providing frequent updates and upgrades to maintain the utility of the software due to rapid changes in technology; other intertwined services such as multiple copies of the tools; assisting the Company's customers in applying the Company's technology in the customers' development environment; and rights to remix licenses for other licenses. Payments are generally received in equal or near equal installments over the term of the arrangement. Under ASC 605, these arrangements were qualified to be recognized ratably over the contract terms. Under ASC 606, the Company has concluded that its software licenses in TSL contracts are not distinct from its obligation to provide unspecified software updates to the licensed software throughout the license term. Such updates represent inputs to a single, combined performance obligation, commencing upon the later of the arrangement effective date 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 pattern of transfer to the customer over the duration of the subscription term. IP & System Integration The Company generally licenses IP under nonexclusive license agreements that provide usage rights for specific applications. Additionally, for certain IP license agreements, royalties are collected as customers sell their own products that incorporate the Company’s IP. Under ASC 605, the Company recognized revenue either upfront if certain criteria in ASC 605 were met, or over the contractual period for IP licensing and support arrangements if such arrangements were combined with other TSL arrangements. Under ASC 606, these arrangements generally have two distinct performance obligations that consist of transferring the licensed IP and the support service. Support services consist of a stand-ready obligation to provide technical support and software updates over the support term. Revenue allocated to the IP license is recognized at a point in time upon the later of the delivery date or the beginning of the license period, and revenue allocated to support services is recognized ratably over the support term. Royalties are recognized as revenue is earned, generally when the customer sells its products that incorporate the Company’s IP. Software Integrity Products Software Integrity product arrangements provide customers the right to software licenses, software updates and technical support. Under the term of these arrangements, the customer expects to receive integral updates to the software licenses that protect the customer’s software from potential security vulnerabilities. The licenses and software updates together serve to fulfill the Company’s commitment to the customer, as they represent inputs to a single, combined performance obligation that commences upon the later of the arrangement effective date or transfer of the software license. Software updates are part of the contract with the customer, and 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 The Company generally has two performance obligations in arrangements involving the sale of hardware products. The first performance obligation is to transfer the hardware product, which includes embedded software integral to the functionality of the hardware product. The second performance obligation is to provide maintenance on the hardware and its embedded software, including 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. The portion of the transaction price allocated to the hardware product is generally recognized as revenue at a point in time when the hardware is delivered to the customer. The Company has concluded that control generally transfers upon delivery because the customer has title to the hardware, physical possession of the hardware, and a present obligation to pay for the hardware. The portion of the transaction price allocated to maintenance is recognized as revenue that is ratable over the maintenance term. The adoption of ASC 606 did not change the timing of revenue recognition for hardware products and related services. Professional Services Our arrangements often include service elements (other than maintenance and support services). These services include training, design assistance, and consulting. Services performed on a time and materials basis are recognized over time, as the customer simultaneously receives and consumes the benefit provided. Certain arrangements also include the customization or modification of licensed IP. Revenue from these contracts is recognized over time as the services are performed, when the development is specific to the customer’s needs and Synopsys has enforceable rights to payment for performance completed. Performance is generally measured using costs incurred or hours expended to measure progress. The Company 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, specification and testing requirement changes, and changes in customer delivery priorities. Payments for services are generally due upon milestones in the contract or upon consumption of the hourly resources. Flexible Spending Accounts Some customers enter into a non-cancelable Flexible Spending Account arrangement (FSA) whereby the customer commits to a fixed dollar amount over a specified period of time that can be used to purchase from a list of Synopsys products or services. These arrangements do not meet the definition of a revenue contract until the customer executes a separate order to identify the required products and services that they are purchasing. The combination of the FSA arrangement and the subsequent order creates enforceable rights and obligations, thus meeting the definition of a revenue contract. Each separate order under the agreement is treated as an individual contract under the new standard and accounted for based on the respective performance obligations included within the FSA arrangements. Disaggregated Revenue The following table shows the percentage of revenue by product groups:
| Three Months Ended January 31,
| 2019 |  | 2018
EDA | 61 | % |  | 63 | %
IP & System Integration | 29 | % |  | 28 | %
Software Integrity Products & Services | 10 | % |  | 8 | %
Other | — | % |  | 1 | %
Total | 100 | % |  | 100 | %
Judgments The Company’s contracts with customers often include promises to transfer multiple products and services to a customer. Determining whether services and products are considered distinct performance obligations that should be accounted for separately versus together require significant judgment. The Company has concluded that (1) its EDA software licenses in TSL contracts are not distinct from its obligation to provide unspecified software updates to the licensed software throughout the license term, because those promises represent inputs to a single, combined performance obligation, and (2) 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. In reaching this conclusion, the Company considered the nature of the obligation to customers which is to provide an ongoing right to use the most up to date and relevant software. As EDA customers operate in a rapidly changing and competitive environment, satisfying the obligation requires providing critical updates to the existing software products, including ongoing iterative interaction with customers to make the software relevant to customers’ ability to meet the time to go to market with advanced products. Similarly, the Company also concluded that in its Software Integrity business, the licenses and maintenance updates serve together to fulfill the Company’s commitment to the customer as both work together to provide the functionality to the customer and represent a combined performance obligation because the updates are essential to the software’s central utility, which is to identify security vulnerabilities and other threats. Judgment is also required to determine the standalone selling price (SSP) for each distinct performance obligation. For non-software performance obligations (IP, Hardware, and services), SSP is established based on observable prices of products and services sold separately. SSP for license (and related updates and support) in a contract with multiple performance obligations is determined by applying a residual approach whereby all other non-software performance obligations within a contract are first allocated a portion of the transaction price based upon their respective SSP, using observable prices, with any residual amount of the transaction price allocated to the license because the Company does not sell the license separately, and the pricing is highly variable. Contract Balances The timing of revenue recognition may differ from the timing of invoicing to customers, and these timing differences result in receivables (billed or unbilled), contract assets, or contract liabilities (deferred revenue) on the Company’s unaudited condensed consolidated balance sheet. The Company records a contract asset when revenue is recognized prior to the right to invoice, or deferred revenue when revenue is recognized subsequent to invoicing. For 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 Company records an unbilled receivable when revenue is recognized and it has an unconditional right to invoice and receive payment. The contract assets indicated below are presented as prepaid and other current assets in the unaudited condensed consolidated balance sheet. The contract assets are transferred to receivables when the rights to invoice and receive payment become unconditional. Contract balances are as follows:
| As of January 31, 2019 |  | As of October 31, 2018
|  |  | as adjusted
| (in thousands)
Contract assets | $ | 167,729 |  |  | $ | 126,897 |
Unbilled receivables | 36,922 |  |  | 36,699 |
Deferred revenue | 1,325,214 |  |  | 1,104,110 |
During the three months ended January 31, 2019, the Company recognized $487.1 million of revenue that was included in the deferred revenue balance at the beginning of the period, as adjusted for the adoption of ASC 606. Contracted but unsatisfied or partially unsatisfied performance obligations were approximately $4.3 billion as of January 31, 2019, which includes $432.5 million in non-cancellable FSA commitments from customers where actual product selection and quantities of specific products or services are to be determined by customers at a later date. The Company has elected to exclude future sales-based royalty payments from the remaining performance obligations. The contracted unsatisfied performance obligations, excluding non-cancellable FSA, expected to be recognized over the next 12 months is approximately 50%, with the remainder recognized thereafter. Costs of Obtaining a Contract with Customer The incremental costs of obtaining a contract with a customer, which consist primarily of direct sales commissions earned upon execution of the contract, are required to be capitalized under ASC 340-40 and amortized over the estimated period over which the benefit is expected to be received. As direct sales commissions paid for renewals are commensurate with the amounts paid for initial contracts, the deferred incremental costs will be recognized over the contract term. Total capitalized direct commission costs as of January 31, 2019 were $95.7 million and are included in other assets in the Company’s unaudited condensed consolidated balance sheet. Amortization of these assets was $12.8 million during the three months ended January 31, 2019 and is included in sales and marketing expense in the Company’s unaudited condensed consolidated statements of operations.

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 Disclosure of accounting policy regarding (1) the principles it follows in consolidating or combining the separate financial statements, including the principles followed in determining the inclusion or exclusion of subsidiaries or other entities in the consolidated or combined financial statements and (2) its treatment of interests (for example, common stock, a partnership interest or other means of exerting influence) in other entities, for example consolidation or use of the equity or cost methods of accounting. The accounting policy may also address the accounting treatment for intercompany accounts and transactions, noncontrolling interest, and the income statement treatment in consolidation for issuances of stock by a subsidiary. + References Reference 1: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 810 -SubTopic 10 -Section S99 -Paragraph 2 -Subparagraph (SX 210.3A-02) -URI http://asc.fasb.org/extlink&oid=27015204&loc=d3e355033-122828 Reference 2: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 810 -SubTopic 10 -Section S99 -Paragraph 3 -Subparagraph (SX 210.3A-03) -URI http://asc.fasb.org/extlink&oid=27015204&loc=d3e355100-122828 Reference 3: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 3 -URI http://asc.fasb.org/extlink&oid=84158767&loc=d3e18780-107790 Reference 4: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 810 -SubTopic 10 -Section 50 -Paragraph 1 -URI http://asc.fasb.org/extlink&oid=109239629&loc=d3e5614-111684 + Details
Name: | us-gaap_ConsolidationPolicyTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration

X
- Definition Disclosure of accounting policy for determining an entity's fiscal year or other fiscal period. This disclosure may include identification of the fiscal period end-date, the length of the fiscal period, any reporting period lag between the entity and its subsidiaries, or equity investees. If a reporting lag exists, the closing date of the entity having a different period end is generally noted, along with an explanation of the necessity for using different closing dates. Any intervening events that materially affect the entity's financial position or results of operations are generally also disclosed. + References Reference 1: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 810 -SubTopic 10 -Section 45 -Paragraph 12 -URI http://asc.fasb.org/extlink&oid=108774443&loc=d3e5291-111683 Reference 2: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 810 -SubTopic 10 -Section S99 -Paragraph 2 -Subparagraph (SX 210.3A-02(b)) -URI http://asc.fasb.org/extlink&oid=27015204&loc=d3e355033-122828 Reference 3: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 810 -SubTopic 10 -Section S99 -Paragraph 3 -Subparagraph (SX 210.3A-03(b)) -URI http://asc.fasb.org/extlink&oid=27015204&loc=d3e355100-122828 + Details
Name: | us-gaap_FiscalPeriod
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration

X
- Definition Disclosure of accounting policy for goodwill. This accounting policy also may address how an entity assesses and measures impairment of goodwill, how reporting units are determined, how goodwill is allocated to such units, and how the fair values of the reporting units are determined. + References Reference 1: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 350 -SubTopic 20 -Section 50 -Paragraph 1 -URI http://asc.fasb.org/extlink&oid=108376223&loc=d3e13816-109267 Reference 2: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 3 -URI http://asc.fasb.org/extlink&oid=84158767&loc=d3e18780-107790 + Details
Name: | us-gaap_GoodwillAndIntangibleAssetsGoodwillPolicy
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration

X
- Definition Disclosure of accounting policy for revenue recognition. If the entity has different policies for different types of revenue transactions, the policy for each material type of transaction is generally disclosed. If a sales transaction has multiple element arrangements (for example, delivery of multiple products, services or the rights to use assets) the disclosure may indicate the accounting policy for each unit of accounting as well as how units of accounting are determined and valued. The disclosure may encompass important judgment as to appropriateness of principles related to recognition of revenue. The disclosure also may indicate the entity's treatment of any unearned or deferred revenue that arises from the transaction. + References Reference 1: http://fasb.org/us-gaap/role/ref/otherTransitionRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 3 -URI http://asc.fasb.org/extlink&oid=84158767&loc=d3e18780-107790 Reference 2: http://fasb.org/us-gaap/role/ref/otherTransitionRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 1 -URI http://asc.fasb.org/extlink&oid=84158767&loc=d3e18726-107790 Reference 3: http://fasb.org/us-gaap/role/ref/otherTransitionRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 4 -URI http://asc.fasb.org/extlink&oid=84158767&loc=d3e18823-107790 + Details
Name: | us-gaap_RevenueRecognitionPolicyTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration

X
- Definition Disclosure of accounting policy for segment reporting. + References Reference 1: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 3 -URI http://asc.fasb.org/extlink&oid=84158767&loc=d3e18780-107790 + Details
Name: | us-gaap_SegmentReportingPolicyPolicyTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration

X
- Definition Disclosure of accounting policy for the use of estimates in the preparation of financial statements in conformity with generally accepted accounting principles. + References Reference 1: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 12 -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e6191-108592 Reference 2: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 11 -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e6161-108592 Reference 3: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 9 -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e6143-108592 Reference 4: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 1 -Subparagraph (b) -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e5967-108592 Reference 5: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 4 -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e6061-108592 Reference 6: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 8 -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e6132-108592 Reference 7: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 1 -Subparagraph (c) -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e5967-108592 + Details
Name: | us-gaap_UseOfEstimates
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration