XML 26 R11.htm IDEA: XBRL DOCUMENT
v3.19.1

REVENUES | 12 Months Ended
--- | ---
Dec. 31, 2018
Revenue from Contract with Customer [Abstract] |
REVENUES | 4. REVENUES Adoption of ASC Topic 606, “Revenue from Contracts with Customers” On January 1, 2018, we adopted Topic 606 using the modified retrospective method applied to those contracts which were not completed as of January 1, 2018. Results for reporting periods beginning after January 1, 2018 are presented under Topic 606, while prior period amounts are not adjusted and continue to be reported in accordance with our historic accounting under Topic 605. Nature of our products and services Our principal products and services include custom-engineered electrical transformers and engine-generator sets and controls, complemented by a national field-service network to maintain and repair power generation assets. Products We provide electrical transformers that help customers effectively and efficiently manage their electrical power distribution systems to desired specifications. We provide customers with sophisticated power generation equipment and an advanced data collection and monitoring platform, the combination of which is used to ensure smooth, uninterrupted power to operations during times of emergency. Services Power generation systems represent considerable investments that require proper maintenance and service in order to operate reliably during a time of emergency. Our power maintenance programs provide preventative maintenance, repair and support service for our customers’ power generation systems. Our principal source of revenue is derived from sales of products and fees for services. We measure revenue based upon the consideration specified in the customer arrangement, and revenue is recognized when the performance obligations in the customer arrangement are satisfied. A performance obligation is a promise in a contract to transfer a distinct product or service to the customer. The transaction price of a contract is allocated to each distinct performance obligation and recognized as revenue when or as, the customer receives the benefit of the performance obligation. Customers typically receive the benefit of our products when the risk of loss or control for the product transfers to the customer and for services as they are performed. Under ASC 606, revenue is recognized when a customer obtains control of promised products or services in an amount that reflects the consideration we expect to receive in exchange for those products or services. To achieve this core principal, the Company applies the following five steps:
| 1) | Identify the contract with a customer
A contract with a customer exists when (i) the Company enters into an enforceable contract with a customer that defines each party’s rights regarding the products or services to be transferred and identifies the payment terms related to these products or services, (ii) the contract has commercial substance and, (iii) the Company determines that collection of substantially all consideration for products or services that are transferred is probable based on the customer’s intent and ability to pay the promised consideration. The Company applies judgment in determining the customer’s ability and intention to pay, which is based on a variety of factors including the customer’s historical payment experience or, in the case of a new customer, published credit and financial information pertaining to the customer.
| 2) | Identify the performance obligations in the contract
Performance obligations promised in a contract are identified based on the products or services that will be transferred to the customer that are both capable of being distinct, whereby the customer can benefit from the product or service either on its own or together with other resources that are readily available from third parties or from the Company, and are distinct in the context of the contract, whereby the transfer of the products or services is separately identifiable from other promises in the contract. To the extent a contract includes multiple promised products or services, the Company must apply judgment to determine whether promised products or services are capable of being distinct and distinct in the context of the contract. If these criteria are not met the promised products or services are accounted for as a combined performance obligation.
| 3) | Determine the transaction price
The transaction price is determined based on the consideration to which the Company will be entitled in exchange for transferring services to the customer. The customer payments are generally due in 30 days.
| 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 the single performance obligation. Contracts that contain multiple performance obligations require an allocation of the transaction price to each performance obligation based on a relative standalone selling price basis or cost of the product or service. The Company determines standalone selling price based on the price at which the performance obligation is sold separately. If the standalone selling price is not observable through past transactions, the Company estimates the standalone selling price taking into account available information such as market conditions and internally approved pricing guidelines related to the performance obligations.
| 5) | Recognize revenue when or as the Company satisfies a performance obligation
The Company satisfies performance obligations either over time or at a point in time. Revenue is recognized at the time the related performance obligation is satisfied by transferring a promised product or service to a customer. Substantially all of our revenue is recognized at a point of time, as the promised product passes to the customer. Service revenues include maintenance contracts that are recognized over time based on the contract term and repair services which are recognized as services are delivered. The following table presents our revenues disaggregated by revenue discipline:
|  | For the Year Ended |
|  | December 31, |
|  | 2018 |  |  | 2017 |
Products |  | $ | 96,590 |  |  | $ | 105,225 |
Services |  |  | 9,800 |  |  |  | 9,166 |
Total Revenue |  | $ | 106,390 |  |  | $ | 114,391 |
See Note 16 – Business Segment, Geographic and Customer Information. Financial Statement Impact of Adopting ASC 606 The Company adopted ASC 606 using the modified retrospective method. There was no adjustment to opening retained earnings due to the impact of adopting Topic 606.

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