Basis of Presentation (Policies)

3 Months Ended

Sep. 29, 2018

Organization, Consolidation and Presentation of Financial Statements [Abstract]

The Company utilizes a 52-53 week fiscal year ending on the Saturday closest to June 30th. The Company’s fiscal 2019 is a 52-week year ending on June 29, 2019. The Company’s fiscal 2018 was a 52-week year ending on June 30, 2018.

Principles of Consolidation

The consolidated financial statements include the Company and its wholly-owned subsidiaries. All inter-company accounts and transactions have been eliminated.

Use of Estimates

The preparation of the Company’s consolidated financial statements requires management to make estimates and assumptions that affect the reported amount of assets and liabilities at the date of the financial statements, the reported amount of net revenues and expenses and the disclosure of commitments and contingencies during the reporting periods. The Company bases estimates on historical experience and assumptions about future periods that are believed to be reasonable based on available information. The Company’s reported financial positions or results of operations may be materially different under changed conditions or when using different estimates and assumptions, particularly with respect to significant accounting policies. If estimates or assumptions differ from actual results, subsequent periods are adjusted to reflect readily available current information.

Recent Accounting Pronouncements

Recent Accounting Pronouncements Adopted

In November 2016, the Financial Accounting Standards Board (“FASB”) issued an accounting standard update (“ASU”) that requires a statement of cash flows to present the change during the period in the total of cash, cash equivalents, and amounts generally described as restricted cash or restricted cash equivalents. In the three months ended September 29, 2018, we adopted this ASU using a retrospective transition method. Accordingly, our consolidated statement of cash flows for the three months ended September 30, 2017, as presented herein, has been restated to comply with the new requirements.

In May 2014, the FASB issued new authoritative guidance related to revenue recognition from contracts with customers, ASC 606 - Revenue from Contracts with Customers (the “revenue standard”). The new guidance provides a unified model to determine when and how revenue is recognized. The core principle of the new guidance is that a company should recognize revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration for which the entity expects to be entitled in exchange for those goods or services. The Company adopted the new standard effective in the first quarter of fiscal 2019 using the retrospective transition method, which requires the Company to recast each prior period presented consistent with the new guidance. Refer to “Note 3. Revenue” of the Consolidated Financial Statements for a summary of significant policies related to the new accounting standards. As part of the adoption, certain prior period amounts have been adjusted or reclassified within the consolidated financial statements.

The following table presents the impact of the revenue standard adoption to select line items of our Consolidated Balance Sheet as of June 30, 2018, (in millions) as follows:



	June 30, 2018
	As Reported		Adjustment			As Adjusted
ASSETS
Accounts receivable, net	$	217.5	$	1.1		$	218.6
Prepayments and other assets	54.8		1.5			56.3
Deferred income taxes	114.5		(0.2		)	114.3
Other non-current assets	13.6		1.8			15.4
Total assets	$	2,022.6	$	4.2		$	2,026.8
LIABILITIES AND STOCKHOLDERS’ EQUITY
Deferred revenue	71.9		(11.3		)	60.6
Accrued payroll and related expenses	51.4		1.4			52.8
Other current liabilities	77.0		1.9			78.9
Other non-current liabilities	182.8		(2.0		)	180.8
Total stockholders’ equity	720.7		14.2			734.9
Total liabilities and stockholders’ equity	$	2,022.6	$	4.2		$	2,026.8

The primary impacts to the previously issued amounts are as follows:

Accounts receivable, net: Adoption of the new revenue standard resulted in an increase to accounts receivable, net primarily due to two items: 1) The return rights provision, which represents a liability for expected customer returns, was previously presented as a reduction to accounts receivable and is now presented in other current liabilities; and 2) Contract assets which are recorded when a conditional right to consideration exists and transfer of control has occurred in advance of the Company’s right to invoice. Upon adoption of ASC 606, contract assets, which were previously presented as a component of accounts receivable, net, are now presented as a component of prepayments and other current assets.

Prepayments and other current assets: As noted above, contract assets, which are recognized when a conditional right to consideration exists and transfer of control has occurred in advance of the Company’s right to invoice, were previously presented as a component of accounts receivable, net. Upon adoption of ASC 606, contract assets are presented as a component of prepayments and other current assets.

Other non-current assets: 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. These costs are now classified as other non-current assets.

Short-term and long-term deferred revenue: Adoption of the new revenue standard resulted in a decrease of deferred revenue primarily due to the net change in timing of software related revenue. Under the previous standard revenue for software license sales bundled with post-contract support and/or services where vendor-specific objective evidence of fair value had not been established was recognized ratably over the support period. Upon adoption of ASC 606 the revenue related to such software license sales will now be recognized when control transfers, which is usually at the time of billing. 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. Long-term deferred revenue is presented under other non-current liabilities.

Other current liabilities: The returns provision, which represents a liability for expected customer returns, was previously presented as a reduction of accounts receivable and is now presented as other current liabilities.

Adoption of the revenue standard had no impact on net cash provided by or used in operating, investing or financing activities as presented on our Consolidated Statements of Cash Flows.

The following table presents the impact of the revenue standard adoption to select line items of our previously reported Consolidated Statement of Operations for the three months ended September 30, 2017 (in millions, except per share data) as follows:



	Three Months Ended September 30, 2017
	As Reported			Adjustment			As Adjusted
Revenues:
Product revenue	$	171.9		$	(6.8	)	$	165.1
Service revenue	23.3			2.5			25.8
Total net revenue	195.2			(4.3		)	190.9
Cost of revenues:
Product cost of revenue	63.5			(0.9		)	62.6
Service cost of revenue	11.4			0.1			11.5
Amortization of acquired technologies	4.1			—			4.1
Total cost of revenue	79.0			(0.8		)	78.2
Gross profit	116.2			(3.5		)	112.7
Income from operations	10.0			(3.3		)	6.7
Loss before taxes	(2.3		)	(3.3		)	(5.6		)
Provision for income taxes	2.5			(0.5		)	2.0
Net loss	$	(4.8	)	$	(2.8	)	$	(7.6	)

Net loss per common share:
Basic and diluted	$	(0.02	)	$	(0.01	)	$	(0.03	)
Shares used in per share calculations:
Basic and diluted	228.1			—			228.1

The impacts to the previously issued amounts are summarized, as follows:

Net revenue: Adoption of the revenue standard resulted in a change in the timing of revenue recognized primarily due to the treatment of software license revenue. Under the prior standard, if vendor-specific objective evidence had not been established for the post contract support and/or the services, software license revenue would have been recognized ratably over the support period. Upon adoption of ASC 606, revenue related to such software license sales will now be recognized when control transfers which is usually at the time of billing. The decrease in revenue for the period presented above is primarily the result of the elimination of ratable software license revenue. Such license revenue was previously amortized; however it is now recognized upon recast, at a point in time under the new standard.

Recent Accounting Pronouncements Not Yet Adopted

In June 2016, FASB issued guidance that changes the accounting for recognizing impairments of financial assets. Under the new guidance, credit losses for certain types of financial instruments will be estimated based on expected losses. The new guidance also modifies the impairment models for available-for-sale debt securities and for purchased financial assets with credit deterioration since their origination. The guidance is effective for the Company in the first quarter of fiscal 2021 and earlier adoption is permitted. The Company is evaluating the impact of adopting this new accounting guidance on its Consolidated Financial Statements.

In February 2016, the FASB issued guidance regarding both operating and financing leases, requiring lessees to recognize on their balance sheets “right-of-use assets” and corresponding lease liabilities, measured on a discounted basis over the lease term. Virtually all leases will be subject to this treatment except leases that meet the definition of a “short-term lease.” The guidance requires a modified retrospective transition approach for leases existing at, or entered into after, the beginning of the earliest comparative period presented in the financial statements. The guidance is effective for the Company in the first quarter of fiscal 2020. While the Company is not yet in a position to assess the full impact of the application of the new guidance, the Company expects adoption of this guidance will materially increase the assets and liabilities recorded on its Consolidated Balance Sheets.

Revenue Recognition

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 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.

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.

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.

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.

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.

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.

Fair Value Measurements

The Company’s cash and investment instruments are classified within Level 1 or Level 2 of the fair value hierarchy based on quoted prices, broker or dealer quotations, or alternative pricing sources with reasonable levels of price transparency.


•	Level 1: includes financial instruments for which quoted market prices for identical instruments are available in active markets. Level 1 assets of the Company include money market funds, U.S. Treasury securities and marketable equity securities as they are traded with sufficient volume and frequency of transactions.

•

Level 2: includes financial instruments for which the valuations are based on quoted prices for similar assets or liabilities, quoted prices in markets that are not active, or other inputs that are observable or can be corroborated by observable data for substantially the full term of the assets or liabilities. Level 2 instruments of the Company generally include certain U.S. and foreign government and agency securities, commercial paper, corporate and municipal bonds and notes, asset-backed securities, certificates of deposit, and foreign currency forward contracts. To estimate their fair value, the Company utilizes pricing models based on market data. The significant inputs for the valuation model usually include benchmark yields, reported trades, broker and dealer quotes, issuer spreads, two-sided markets, benchmark securities, bids, offers and reference data, and industry and economic events.


•	Level 3: includes financial instruments for which fair value is derived from valuation based on inputs that are unobservable and significant to the overall fair value measurement. As of September 29, 2018 and June 30, 2018, the Company did not hold any Level 3 investment securities.