XML 45 R26.htm IDEA: XBRL DOCUMENT
v3.19.3

Revenue from Contracts with Customers (Policy) | 9 Months Ended
--- | ---
Sep. 30, 2019
Revenue from Contract with Customer [Abstract] |
Revenue Recognition | The Company recognizes revenue when it transfers promised goods or services to customers in an amount that reflects the consideration to which the Company expects to be entitled in exchange for those goods or services by applying the following five step model: (1) Identify the contract with a customer A contract with a customer exists when: (a) the parties have approved the contract and are committed to perform their respective obligations, (b) the rights of the parties can be identified, (c) payment terms can be identified, (d) the arrangement has commercial substance, and (e) collectibility of consideration is probable. Judgment is required when determining if the contractual criteria are met, specifically in the earlier stages of a project when a formally executed contract may not yet exist. In these situations, the Company evaluates all relevant facts and circumstances, including the existence of other forms of documentation or historical experience with our customers that may indicate a contractual agreement is in place and revenue should be recognized. In determining if the collectibility of consideration is probable, the Company considers the customer’s ability and intention to pay such consideration through an evaluation of several factors, including an assessment of the creditworthiness of the customer and our prior collection history with such customer. (2) Identify the performance obligations in the contract At contract inception, the Company assesses the goods or services promised in a contract and identifies, as a separate performance obligation, each distinct promise to transfer goods or services to the customer. The identified performance obligations represent the “unit of account” for purposes of determining revenue recognition. In order to properly identify separate performance obligations, the Company applies judgment in determining whether each good or service provided is: (a) capable of being distinct, whereby 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 (b) distinct within the context of the contract, whereby the transfer of the good or service to the customer is separately identifiable from other promises in the contract. In addition, when assessing performance obligations within a contract, the Company considers the warranty provisions included within such contract. To the extent the warranty terms provide the customer with an additional service, other than assurance that the promised good or service complies with agreed upon specifications, such warranty is accounted for as a separate performance obligation. In determining whether a warranty provides an additional service, the Company considers each warranty provision in comparison to warranty terms which are standard in the industry. Our contracts are often modified through change orders to account for changes in the scope and price of the goods or services we are providing. Although the Company evaluates each change order to determine whether such modification creates a separate performance obligation, the majority of our change orders are for goods or services that are not distinct within the context of our original contract and, therefore, are not treated as separate performance obligations. (3) Determine the transaction price The transaction price represents the amount of consideration to which the Company expects to be entitled in exchange for transferring promised goods or services to our customers. The consideration promised within a contract may include fixed amounts, variable amounts, or both. To the extent the performance obligation includes variable consideration, including contract bonuses and penalties that can either increase or decrease the transaction price, the Company estimates the amount of variable consideration to be included in the transaction price utilizing one of two prescribed methods, depending on which method better predicts the amount of consideration to which the entity will be entitled. Such methods include: (a) the expected value method, whereby the amount of variable consideration to be recognized represents the sum of probability weighted amounts in a range of possible consideration amounts, and (b) the most likely amount method, whereby the amount of variable consideration to be recognized represents the single most likely amount in a range of possible consideration amounts. When applying these methods, the Company considers all information that is reasonably available, including historical, current and estimates of future performance. The expected value method is typically utilized in situations where a contract contains a large number of possible outcomes while the most likely amount method is typically utilized in situations where a contract has only two possible outcomes. Variable consideration is included in the transaction price only to the extent it is probable, in the Company’s judgment, that a significant future reversal in the amount of cumulative revenue recognized under the contract will not occur when the uncertainty associated with the variable consideration is subsequently resolved. This threshold is referred to as the variable consideration constraint. In assessing whether to apply the variable consideration constraint, the Company considers if factors exist that could increase the likelihood or the magnitude of a potential reversal of revenue, including, but not limited to, whether: (a) the amount of consideration is highly susceptible to factors outside of the Company’s influence, such as the actions of third parties, (b) the uncertainty surrounding the amount of consideration is not expected to be resolved for a long period of time, (c) the Company’s experience with similar types of contracts is limited or that experience has limited predictive value, (d) the Company has a practice of either offering a broad range of price concessions or changing the payment terms and conditions of similar contracts in similar circumstances, and (e) the contract has a large number and broad range of possible consideration amounts. Pending change orders represent one of the most common forms of variable consideration included within contract value and typically represent contract modifications for which a change in scope has been authorized or acknowledged by our customer, but the final adjustment to contract price is yet to be negotiated. In estimating the transaction price for pending change orders, the Company considers all relevant facts, including documented correspondence with the customer regarding acknowledgment of and/or agreement with the modification, as well as historical experience with the customer or similar contractual circumstances. Based upon this assessment, the Company estimates the transaction price, including whether the variable consideration constraint should be applied. Contract claims are another form of variable consideration which is common within our industry. Claim amounts represent revenue that has been recognized for contract modifications that are not submitted or are in dispute as to both scope and price. In estimating the transaction price for claims, the Company considers all relevant facts available. However, given the uncertainty surrounding claims, including the potential long-term nature of dispute resolution and the broad range of possible consideration amounts, there is an increased likelihood that any additional contract revenue associated with contract claims is constrained. The resolution of claims involves negotiations and, in certain cases, litigation. In the event litigation costs are incurred by us in connection with claims, such litigation costs are expensed as incurred, although we may seek to recover these costs. For some transactions, the receipt of consideration does not match the timing of the transfer of goods or services to the customer. For such contracts, the Company evaluates whether this timing difference represents a financing arrangement within the contract. Although rare, if a contract is determined to contain a significant financing component, the Company adjusts the promised amount of consideration for the effects of the time value of money when determining the transaction price of such contract. Although our customers may retain a portion of the contract price until completion of the project and final contract settlement, these retainage amounts are not considered a significant financing component as the intent of the withheld amounts is to provide the customer with assurance that we will complete our obligations under the contract rather than to provide financing to the customer. In addition, although we may be entitled to advanced payments from our customers on certain contracts, these advanced payments generally do not represent a significant financing component as the payments are used to meet working capital demands that can be higher in the early stages of a contract, as well as to protect us from our customer failing to meet its obligations under the contract. Changes in the estimates of transaction prices are recognized on a cumulative catch-up basis in the period in which the revisions to the estimates are made. Such changes in estimates can result in the recognition of revenue in a current period for performance obligations which were satisfied or partially satisfied in prior periods. Such changes in estimates may also result in the reversal of previously recognized revenue if the ultimate outcome differs from the Company’s previous estimate. For the three and nine months ended September 30, 2019, there were no significant amounts of revenue recognized during the period related to performance obligations satisfied in prior periods. For the three and nine months ended September 30, 2018, we recognized revenue of $6.3 million associated with the final settlement of contract value for two projects which were completed in prior periods. In addition, for the three and nine months ended September 30, 2019 and 2018, there were no significant reversals of revenue recognized associated with the revision of transaction prices. (4) Allocate the transaction price to performance obligations in the contract For contracts that contain multiple performance obligations, the Company allocates the transaction price to each performance obligation based on a relative standalone selling price. The Company determines the standalone selling price based on the price at which the performance obligation would have been sold separately in similar circumstances to similar customers. If the standalone selling price is not observable, the Company estimates the standalone selling price taking into account all available information such as market conditions and internal pricing guidelines. In certain circumstances, the standalone selling price is determined using an expected profit margin on anticipated costs related to the performance obligation. (5) Recognize revenue as performance obligations are satisfied The Company recognizes revenue at the time the related performance obligation is satisfied by transferring a promised good or service to its customers. A good or service is considered to be transferred when the customer obtains control. The Company can transfer control of a good or service and satisfy its performance obligations either over time or at a point in time. The Company transfers control of a good or service over time and, therefore, satisfies a performance obligation and recognizes revenue over time if one of the following three criteria are met: (a) the customer simultaneously receives and consumes the benefits provided by the Company’s performance as we perform, (b) the Company’s performance creates or enhances an asset that the customer controls as the asset is created or enhanced, or (c) the Company’s performance does not create an asset with an alternative use to us, and we have an enforceable right to payment for performance completed to date. For our performance obligations satisfied over time, we recognize revenue by measuring the progress toward complete satisfaction of that performance obligation. The selection of the method to measure progress towards completion can be either an input method or an output method and requires judgment based on the nature of the goods or services to be provided. For our construction contracts, revenue is generally recognized over time as our performance creates or enhances an asset that the customer controls as it is created or enhanced. Our fixed price construction projects generally use a cost-to-cost input method to measure our progress towards complete satisfaction of the performance obligation as we believe it best depicts the transfer of control to the customer which occurs as we incur costs on our contracts. Under the cost-to-cost measure of progress, the extent of progress towards completion is measured based on the ratio of costs incurred to date to the total estimated costs at completion of the performance obligation. For our unit price construction contracts, progress towards complete satisfaction is measured through an output method, such as the amount of units produced or delivered, when our performance does not produce significant amounts of work in process or finished goods prior to complete satisfaction of such performance obligations. For our services contracts, revenue is also generally recognized over time as the customer simultaneously receives and consumes the benefits of our performance as we perform the service. For our fixed price service contracts with specified service periods, revenue is generally recognized on a straight-line basis over such service period when our inputs are expended evenly, and the customer receives and consumes the benefits of our performance throughout the contract term. The timing of revenue recognition for the manufacturing of new build heat exchangers within our United States industrial services segment depends on the payment terms of the contract, as our performance does not create an asset with an alternative use to us. For those contracts for which we have a right to payment for performance completed to date at all times throughout our performance, inclusive of a cancellation, we recognize revenue over time. For these performance obligations, we use a cost-to-cost input method to measure our progress towards complete satisfaction of the performance obligation as we believe it best depicts the transfer of control to the customer which occurs as we incur costs on our contracts. However, for those contracts for which we do not have a right, at all times, to payment for performance completed to date, we recognize revenue at the point in time when control is transferred to the customer. For bill-and-hold arrangements, revenue is recognized when the customer obtains control of the heat exchanger, which may be prior to shipping, if certain recognition criteria are met. For certain of our revenue streams, such as call-out repair and service work, outage services, refinery turnarounds and specialty welding services that are performed under time and materials contracts, our progress towards complete satisfaction of such performance obligations is measured using an output method as the customer receives and consumes the benefits of our performance completed to date. Due to uncertainties inherent in the estimation process, it is possible that estimates of costs to complete a performance obligation will be revised in the near-term. For those performance obligations for which revenue is recognized using a cost-to-cost input method, changes in total estimated costs, and related progress towards complete satisfaction of the performance obligation, are recognized on a cumulative catch-up basis in the period in which the revisions to the estimates are made. When the current estimate of total costs for a performance obligation indicate a loss, a provision for the entire estimated loss on the unsatisfied performance obligation is made in the period in which the loss becomes evident.

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 Disclosure of accounting policy for revenue. Includes revenue from contract with customer and from other sources. + References Reference 1: http://www.xbrl.org/2003/role/exampleRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 4 -Subparagraph (e) -URI http://asc.fasb.org/extlink&oid=84158767&loc=d3e18823-107790 Reference 2: http://www.xbrl.org/2003/role/exampleRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 4 -Subparagraph (f) -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