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

Revenue | 3 Months Ended
--- | ---
Sep. 29, 2018
Revenue from Contract with Customer [Abstract] |
Revenue | Note 3. Revenue Effective in the first quarter of fiscal 2019, the Company adopted the revenue standard using the retrospective transition method which requires the Company to recast each prior period presented, consistent with the new guidance. The most significant impact of the revenue standard relates to our accounting for contracts containing software. As a result, for software solutions bundled with post-contract support (“PCS”) and/or services where vendor-specific objective evidence (“VSOE”) has not been established for the PCS and/or services, revenue will now be recognized when control transfers which is usually at time of billing rather than ratably over the life of the support term. The actual revenue recognition treatment required under the standard will depend on contract-specific terms and in some instances transfer of control and revenue recognition may differ from the time of billing. Revenue recognition under the revenue standard for the remainder of the Company’s products and services remains substantially unchanged. The Company derives revenue from a diverse portfolio of network solutions and optical technology products and services, as follows:
• | Products: Network Enablement (“NE”) and Service Enablement (“SE”) products include instruments, microprobes and perpetual software licenses that support the development, production, maintenance and optimization of network systems. The Company’s Optical Security and Performance (“OSP”) products include proprietary pigments used for optical security and optical filters used in commercial and government 3D Sensing applications.
• | Services: The Company also offers a range of product support and professional services designed to comprehensively address customer requirements. These include repair, calibration, extended warranty, software support, technical assistance, training and consulting services. Implementation services provided in conjunction with hardware or software solution projects include sale of the products along with project management, set-up and installation.
Steps of revenue recognition The Company accounts for revenue in accordance with the revenue standard, in which the following five steps are applied to recognize revenue.
1. | Identify the contract with a customer: Generally, the Company considers customer purchase orders, which in some cases are governed by master sales or other purchase agreements, to be the customer contract. All of the following criteria must be met before the Company considers an agreement to qualify as a contract with a customer under the revenue standard: (i) it must be approved by all parties; (ii) each party’s rights regarding the goods and services to be transferred can be identified; (iii) the payment terms for the goods and services can be identified; (iv) the customer has the ability and intent to pay and collection of substantially all of the consideration is probable; and (v) the agreement has commercial substance. The Company utilizes judgment to determine the customer’s ability and intent to pay, which is based upon various factors including the customer’s historical payment experience or credit and financial information and credit risk management measures implemented by the Company.
2. | Identify the performance obligations in the contract: The Company assesses whether each promised good or service is distinct for the purpose of identifying the various performance obligations in each contract. Promised goods and services are considered distinct provided that: (i) the customer can benefit from the good or service either on its own or together with other resources that are readily available to the customer; and (ii) the Company's promise to transfer the good or service to the customer is separately identifiable or distinct from other promises in the contract. The Company's performance obligations consist of a variety of products and services offerings which include networking equipment; proprietary pigment, optical filters, proprietary software licenses; support and maintenance which includes hardware support that extends beyond the Company's standard warranties, software maintenance, installation, professional and implementation services, and training.
Determining whether products and services are considered distinct performance obligations may require significant judgment. We may enter into contracts that involve a significant level of integration and interdependency between a software license and installation services. Judgment may be required to determine whether the software license is considered distinct in the context of the contract and accounted for separately, or not distinct in the context of the contract and accounted for together with the installation service.
3. | Determine the transaction price: Transaction price reflects the amount of consideration to which the Company expects to be entitled in exchange for transferring goods or services to the customer. The Company’s contracts may include terms that could cause variability in the transaction price including rebates, sales returns, market incentives and volume discounts. Variable consideration is generally accounted for at portfolio level and estimated based on historical information. If a contract includes a variable amount, the price adjustments are estimated at contract inception. In both cases, estimates are updated at the end of each reporting period as additional information becomes available.
4. | Allocate the transaction price to performance obligations in the contract: If the contract contains a single performance obligation, the entire transaction price is allocated to that performance obligation. Many of the Company’s contracts include multiple performance obligations with a combination of distinct products and services, maintenance and support, professional services and/or training. Contracts may also include rights or options to acquire future products and/or services, which are accounted for as separate performance obligations by the Company only if the right or option provides the customer with a material right that it would not receive without entering into the contract. For contracts with multiple performance obligations, the Company allocates the total transaction value to each distinct performance obligation based on relative standalone selling price (“SSP”). Judgment is required to determine the SSP for each distinct performance obligation. The best evidence of SSP is the observable price of a good or service when the Company sells that good or service separately under similar circumstances to similar customers. If a directly observable price is not available, the SSP must be estimated based on multiple factors including, but not limited to, historical pricing practices, internal costs, and profit objectives as well as overall market conditions.
5. | Recognize revenue when (or as) performance obligations are satisfied: Revenue is recognized at the point in time control is transferred to the customer. For hardware sales, transfer of control to the customer typically occurs at the point the product is shipped or delivered to the customer’s designated location. For software license sales transfer of control to the customer typically occurs upon shipment, electronic delivery, or when the software is available for download by the customer. For sales of implementation service and solution contracts or in instances where software is sold along with essential installation services, transfer of control occurs and revenue is typically recognized upon customer acceptance. In certain instances, acceptance is deemed to have occurred if all acceptance provisions lapse, or if the Company has evidence that all acceptance provisions will be, or have been, satisfied. For fixed-price support and extended warranty contracts, or certain software arrangements which provide customers with a right to access over a discrete period, control is deemed to transfer over time and revenue is recognized on a straight-line basis over the contract term due to the stand-ready nature of the performance obligation. Revenue from hardware repairs and calibration services is recognized at the time of completion of the related service. For other professional services or time-based labor contracts, revenue is recognized as the Company performs the services and the customers receive and consume the benefits.
Revenue policy and practical expedients The following policy and practical expedient elections have been made by the Company under the revenue standard:
• | Revenue-based taxes as assessed by governmental authorities have been excluded from the measurement of transaction price(s).
• | Shipping and handling activities performed after customer obtains control of the good are treated as activities to fulfill the promise (cost of fulfillment). Therefore, the Company does not evaluate whether the shipping and handling activities are promised services.
• | Incremental costs of obtaining contracts that would have been recognized within one year or less are recognized as an expense when incurred. These costs are included in selling, general, and administrative expenses (“SG&A”). The costs of obtaining contracts where the amortization period for recognition of the expense is beyond a year are capitalized and recognized over the revenue recognition period of the original contract.
• | The portfolio approach is used for certain types of variable consideration for contracts with similar characteristics. The methodology is used when the effects on the financial statements of applying this guidance to the portfolio would not differ materially from applying this guidance to the individual contracts within that portfolio.
• | Where at contract inception, the expected period between the transfer of promised goods or services and payment is within one year or less, we forgo adjustment for the impact of significant financing component for the contract.
• | For contracts that were modified before the beginning of the earliest reporting period presented, the Company has applied a transition practical expedient and will not recast the contracts for those modifications. Instead we have reflected the aggregate effect of all modifications when identifying the satisfied and unsatisfied performance obligations, determining the transaction price and allocating the transaction price.
• | For the reporting periods presented before the date of initial application, the amount of the transaction price allocated to the remaining performance obligations and the explanation of when it expects to recognize that amount as revenue is not disclosed.
Disaggregation of revenue The Company's revenue is presented on a disaggregated basis on the Consolidated Statements of Operations and in “Note 18. Operating Segments and Geographic Information”. This information includes revenue from reportable segments and a break-out of products and services for which the nature and timing of the revenue as characterized above is generally at a point in time and over time, respectively. Balance sheet and other details Receivables: The Company records a receivable when an unconditional right to consideration exists and transfer of control has occurred, such that only the passage of time is required before payment of consideration is due. Timing of revenue recognition may differ from the timing of customer invoicing. Payment terms vary based on product or service offerings and payment is generally required within 30 to 90 days from date of invoicing. Certain performance obligations may require payment before delivery of the service to the customer. Contract Assets: A contract asset is recognized when a conditional right to consideration exists and transfer of control has occurred. Contract assets include fixed fee professional services where the transfer of services has occurred in advance of the Company's right to invoice. Contract assets are included in other current assets on the consolidated balance sheet. There were contract assets of $1.4 million and $1.3 million as of September 29, 2018 and June 30, 2018, respectively. Contract asset balances will fluctuate based upon the timing of transfer of services, billings and customers’ acceptance of contractual milestones. Deferred revenue: Deferred revenue consists of contract liabilities primarily related to support, solution deployment services, software maintenance, product, professional services, and training when the Company has a right to invoice or payments have been received and transfer of control has not occurred. Revenue is recognized on these items when the revenue recognition criteria are met, generally resulting in ratable recognition over the contract term. Contract liabilities are included in other current liabilities on the consolidated balance sheets. The Company also has short term and long term deferred revenues related to undelivered hardware and professional services, consisting of installations and consulting engagements, which are recognized as the Company's performance obligations under the contract are completed and accepted by the customer. The following tables summarize the activity related to deferred revenue (in millions):
| Three Months Ended
| September 29, 2018
Deferred revenue: |
Balance at beginning of period | $ | 71.9 |
Revenue deferrals for new contracts (1) | 26.7 |
Revenue recognized during the period | (26.0 | )
Balance at end of period | $ | 72.6 |
Short-term deferred revenue | $ | 61.5 |
Long-term deferred revenue | $ | 11.1 |
(1) Included in these amounts are the impact from foreign currency exchange rate fluctuations. Remaining Performance Obligations: Remaining performance obligations represent the aggregate amount of the transaction price allocated to performance obligations not delivered, or incomplete, as of September 29, 2018. Remaining performance obligations include deferred revenue plus unbilled amounts not yet recorded. The aggregate amount of the transaction price allocated to remaining performance obligations does not include amounts owed under cancelable contracts where there is no substantive termination penalty. The Company also applied the practical expedient to not disclose the amount of transaction price allocated to remaining performance obligations for the periods prior to adoption of the new revenue standard. Remaining performance obligation estimates are subject to change and are affected by several factors, including terminations, changes in the scope of contracts, periodic revalidation, adjustments for revenue that has not materialized, and adjustments for currency. The value of the transaction price allocated to remaining performance obligations as of September 29, 2018, was $236.1 million. The Company expects to recognize 94% of remaining performance obligations as revenue within the next 12 months, and the remainder thereafter.

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