XML 21 R9.htm IDEA: XBRL DOCUMENT
v3.19.1

Revenue from Contracts with Customers | 6 Months Ended
--- | ---
Mar. 30, 2019
Revenue from Contract with Customer [Abstract] |
Revenue Recognition and Contracts with Customers | Revenue from Contracts with Customers We recognize revenue from contracts with customers using the five-step model prescribed in ASC 606. The first step is identifying the contract. The identification of a contract with a customer requires an assessment of each party’s rights and obligations regarding the products or services to be transferred, including an evaluation of termination clauses and presently enforceable rights and obligations. Each party’s rights and obligations and the associated terms and conditions are typically determined in purchase orders. For sales that are governed by master supply agreements under which provisions define specific program requirements, purchase orders are issued under these agreements to reflect presently enforceable rights and obligations for the units of products and services being purchased. Contracts are sometimes modified to account for changes in contract specifications and requirements. When this occurs, we assess the modification as prescribed in ASC 606 and determine whether the existing contract needs to be modified (and revenue cumulatively caught up), whether the existing contract needs to be terminated and a new contract needs to be created, or whether the existing contract remains and a new contract needs to be created. This is determined based on the rights and obligations within the modification as well as the associated transaction price. The next step is identifying the performance obligations. A performance obligation is a promise to transfer goods or services to a customer that is distinct in the context of the contract, as defined by ASC 606. We identify a performance obligation for each promise in a contract to transfer a distinct good or service to the customer. As part of our assessment, we consider all goods and/or services promised in the contract, regardless of whether they are explicitly stated or implied by customary business practices. The products and services in our contracts are typically not distinct from one another due to their complexity and reliance on each other or, in many cases, we provide a significant integration service. Accordingly, many of our contracts are accounted for as one performance obligation. In limited cases, our contracts have more than one distinct performance obligation, which occurs when we perform activities that are not highly complex or interrelated or involve different product life cycles. Warranties are provided on certain contracts, but do not typically provide for services beyond standard assurances and are therefore not distinct performance obligations under ASC 606. The third step is determining the transaction price, which represents the amount of consideration we expect to be entitled to receive from a customer in exchange for providing the goods or services. There are times when this consideration is variable, for example a volume discount, and must be estimated. Sales, use, value-added, and excise taxes are excluded from the transaction price, where applicable. The fourth step is allocating the transaction price. The transaction price must be allocated to the performance obligations identified in the contract based on relative stand-alone selling prices when available, or an estimate for each distinct good or service in the contract when standalone prices are not available. Our contracts with customers generally require payment under normal commercial terms after delivery. Payment terms are typically within 30 to 60 days of delivery. The timing of satisfaction of our performance obligations does not significantly vary from the typical timing of payment. The final step is the recognition of revenue. We recognize revenue as the performance obligations are satisfied. ASC 606 provides guidance to help determine if we are satisfying the performance obligation at a point in time or over time. In determining when performance obligations are satisfied, we consider factors such as contract terms, payment terms and whether there is an alternative use of the product or service. In essence, we recognize revenue when or as control of the promised goods or services transfer to the customer. Under ASC 606, revenue recognized over time using the cost-to-cost method of accounting for the three and six months ended March 30, 2019 was 65% and 64%, respectively. The over time method of revenue recognition is predominantly used in Aircraft Controls and Space and Defense Controls. We use this method for U.S. Government contracts and repair and overhaul arrangements as we are creating or enhancing assets that the customer controls as the assets are being created or enhanced. In addition, many of our large commercial contracts qualify for over time accounting as our performance does not create an asset with an alternative use and we have enforceable right to payment for performance completed to date. Our over time contracts are primarily firm fixed price. Revenue is recognized on contracts using the cost-to-cost method of accounting as work progresses toward completion as determined by the ratio of cumulative costs incurred to date to estimated total contract costs at completion, multiplied by the total estimated contract revenue, less cumulative revenue recognized in prior periods. We believe that cumulative costs incurred to date as a percentage of estimated total contract costs at completion is an appropriate measure of progress toward satisfaction of performance obligations as this measure most accurately depicts the progress of our work and transfer of control to our customers. Changes in estimates affecting sales, costs and profits are recognized in the period in which the change becomes known using the cumulative catch-up method of accounting, resulting in the cumulative effect of changes reflected in the period. Estimates are reviewed and updated quarterly for substantially all contracts. For the three and six months ended March 30, 2019, we recognized lower revenues of $1,321 and higher revenues of $10,438, respectively, for adjustments made to performance obligations satisfied (or partially satisfied) in previous periods. Contract costs include only allocable, allowable and reasonable costs which are included in cost of sales when incurred. For applicable U.S. Government contracts, contract costs are determined in accordance with the Federal Acquisition Regulations and the related Cost Accounting Standards. The nature of these costs includes development engineering costs and product manufacturing costs such as direct material, direct labor, other direct costs and indirect overhead costs. Contract profit is recorded as a result of the revenue recognized less costs incurred in any reporting period. Variable consideration and contract modifications, such as performance incentives, penalties, contract claims or change orders are considered in estimating revenues, costs and profits when they can be reliably estimated and realization is considered probable. Revenue recognized on contracts for unresolved claims or unapproved contract change orders was not material for the three and six months ended March 30, 2019. As of March 30, 2019, we had contract and contract-related loss reserves of $49,383. For contracts with anticipated losses at completion, a provision for the entire amount of the estimated remaining loss is charged against income in the period in which the loss becomes known. Contract losses are determined considering all direct and indirect contract costs, exclusive of any selling, general or administrative cost allocations that are treated as period expenses. Loss reserves are more common on firm fixed-price contracts that involve, to varying degrees, the design and development of new and unique controls or control systems to meet the customers’ specifications. Contract-related loss reserves are recorded for the additional work needed on completed and delivered products in order for them to meet contract specifications. In accordance with ASC 606, we calculate contract losses at the contract level, versus the performance obligation level. For the three and six months ended March 30, 2019, 35% and 36% of revenue, respectively, was recognized at the point in time control transferred to the customer. This method of revenue recognition is used most frequently in Industrial Systems. We use this method for commercial contracts in which the asset being created has an alternative use. We determine the point in time control transfers to the customer by weighing the five indicators provided by ASC 606 - the entity has a present right to payment; the customer has legal title; the customer has physical possession; the customer has the significant risks and rewards of ownership; and the customer has accepted the asset. When control has transferred to the customer, profit is generated as cost of sales is recorded and as revenue is recognized. Inventory costs include all product manufacturing costs such as direct material, direct labor, other direct costs and indirect overhead cost allocations. Shipping and handling costs are considered costs to fulfill a contract and not considered performance obligations. They are included in cost of sales as incurred. Contract Assets and Liabilities Unbilled receivables (contract assets) primarily represent revenues recognized for performance obligations that have been satisfied but for which amounts have not been billed. These are included as Receivables on the Consolidated Condensed Balance Sheets. Contract advances (contract liabilities) relate to payments received from customers in advance of the satisfaction of performance obligations for a contract. We do not consider contract advances to be significant financing components as the intent of these payments in advance are for reasons other than providing a significant financing benefit and are customary in our industry. Total contract assets and contract liabilities as of March 30, 2019 are as follows:
|  | March 30, 2019 |  | September 30, 2018
Unbilled receivables |  | $ | 430,901 |  |  | $ | 405,610 |
Contract advances |  | 169,836 |  |  | 152,608 |
Net contract assets |  | $ | 261,065 |  |  | $ | 253,002 |
The increase in contract assets reflects the net impact of additional unbilled revenues recorded in excess of revenue recognized during the period. The increase in contract liabilities reflects the net impact of additional deferred revenues recorded in excess of revenue recognized during the period. For the three and six months ended March 30, 2019, we recognized $46,078 and $93,586 of revenue, respectively, that was included in the contract liability balance at the beginning of the period. Remaining Performance Obligations As of March 30, 2019, the aggregate amount of the transaction price allocated to the performance obligations that are unsatisfied (or partially unsatisfied), also known as backlog, was approximately $2,230,000. We expect to recognize approximately 73% of that amount as sales over the next twelve months and the balance thereafter. Disaggregation of Revenue See Note 17, Segments, for disclosures related to disaggregation of revenue.

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