SUMMARY OF SIGNIFICANT ACCOUNTING POLICIES (Policies)	6 Months Ended
Jun. 30, 2025
Accounting Policies [Abstract]
Reclassifications	Certain prior year amounts are reclassified to conform to the current year presentation. This includes the separate disclosure of changes in Income taxes within operating activities on the Consolidated Statement of Cash Flows.
Supply Chain Financing	Amounts outstanding related to supply chain financing programs are included in Accounts payable in the Consolidated Balance Sheet.
Recent Accounting Pronouncements	The Company considers the applicability and impact of all Accounting Standards Updates (ASUs) issued by the Financial Accounting Standards Board (FASB). ASUs not listed below were assessed and determined to be either not applicable or are expected to have minimal impact on the Company's Consolidated Financial Statements. In November 2024, the FASB issued ASU 2024-03, Income Statement—Reporting Comprehensive Income—Expense Disaggregation Disclosures (Subtopic 220-40): Disaggregation of Income Statement Expenses, which requires companies to disclose additional information about the types of expenses in commonly presented expense captions. The new standard requires tabular disclosure of specified natural expenses in certain expense captions, a qualitative description of amounts that are not separately disaggregated, and disclosure of the Company's definition and total amount of selling expenses. The ASU should be applied prospectively for annual reporting periods beginning after December 15, 2026, with retrospective application and early adoption permitted. The Company is currently evaluating the impacts of this guidance on the Company's Consolidated Financial Statements. In December 2023, the FASB issued ASU 2023-09, Income Taxes (Topic 740): Improvements to Income Taxes Disclosures, which requires greater disaggregation of income tax disclosures. The new standard requires additional information to be disclosed annually with respect to the income tax rate reconciliation and income taxes paid disaggregated by jurisdiction. This ASU should be applied prospectively for fiscal years beginning after December 15, 2024, with retrospective application permitted. The Company is currently evaluating the impacts of this guidance on the Company’s Consolidated Financial Statements. In November 2023, the FASB issued ASU 2023-07, Segment Reporting (Topic 280): Improvements to Reportable Segment Disclosures, which requires companies to enhance the disclosures about segment expenses. The new standard requires the disclosure of the Company’s Chief Operating Decision Maker (CODM), expanded incremental line-item disclosures of significant segment expenses used by the CODM for decision-making, and the inclusion of previous annual only segment disclosure requirements on a quarterly basis. This ASU should be applied retrospectively for fiscal years beginning after December 15, 2023, and interim periods within fiscal years beginning after December 15, 2024. The Company adopted this guidance for annual disclosures for the year ended December 31, 2024, and interim disclosures for the first quarter of 2025. The adoption of this standard did not have a material impact on the Company’s Consolidated Financial Statements.
Revenue Recognition and Contracts with Customers	The Company tracks progress on satisfying performance obligations under contracts with customers. The related billings and cash collections are recorded in the Consolidated Balance Sheet in Accounts receivable—net and Other assets (unbilled receivables (contract assets) and billed receivables), and Accrued liabilities and Other liabilities (customer advances and deposits (contract liabilities)). Unbilled receivables arise when the timing of cash collected from customers differs from the timing of revenue recognition, such as when contract provisions require specific milestones to be met before a customer can be billed. Contract assets are recognized when the revenue associated with the contract is recognized prior to billing and derecognized when billed in accordance with the terms of the contract. Contract liabilities are recorded when customers remit contractual cash payments in advance of the Company satisfying performance obligations under contractual arrangements, including those with performance obligations to be satisfied over a period of time. Contract liabilities are derecognized when revenue is recorded, either when a milestone is met triggering the contractual right to bill or when the performance obligation is satisfied. Contract balances are classified as assets or liabilities on a contract-by-contract basis at the end of each reporting period. When contracts are modified to account for changes in contract specifications and requirements, the Company considers whether the modification either creates new or changes the existing enforceable rights and obligations. Contract modifications for goods or services and not distinct from the existing contract, due to the significant integration with the original good or service provided, are accounted for as if they were part of that existing contract. The effect of a contract modification on the transaction price and the Company's measure of progress for the performance obligation to which it relates, is recognized as an adjustment to revenue (either as an increase in or a reduction of revenue) on a cumulative catch-up basis. When the modifications include additional performance obligations that are distinct and at relative stand-alone selling price, they are accounted for as a new contract and performance obligation, which are recognized prospectively. PERFORMANCE OBLIGATIONS A performance obligation is a promise in a contract to transfer a distinct good or service to the customer and is defined as the unit of account. A contract’s transaction price is allocated to each distinct performance obligation and recognized as revenue when, or as, the performance obligation is satisfied. When the contracts with customers require highly complex integration or manufacturing services that are not separately identifiable from other promises in the contracts and, therefore, not distinct, then the entire contract is accounted for as a single performance obligation. In situations when the Company's contracts include distinct goods or services that are substantially the same and have the same pattern of transfer to the customer over time, they are recognized as a series of distinct goods or services. For any contracts with multiple performance obligations, the Company allocates the contract’s transaction price to each performance obligation based on the estimated relative stand-alone selling price of each distinct good or service in the contract. For product sales, each product sold to a customer typically represents a distinct performance obligation. In such cases, the observable stand-alone sales are used to determine the stand-alone selling price. Performance obligations are satisfied as of a point in time or over time. Performance obligations are supported by contracts with customers, providing a framework for the nature of the distinct goods, services, or bundle of goods and services. The timing of satisfying the performance obligation is typically indicated by the terms of the contract. Performance obligations recognized as of June 30, 2025, will be satisfied over the course of future periods. The Company's disclosure of the timing for satisfying the performance obligation is based on the requirements of contracts with customers. However, from time to time, these contracts may be subject to modifications, impacting the timing of satisfying the performance obligations. Performance obligations expected to be satisfied within one year and greater than one year are 56% and 44%, respectively. The timing of satisfaction of the Company's performance obligations does not significantly vary from the typical timing of payment. Typical payment terms of the Company's fixed price over time contracts include progress payments based on specified events or milestones or based on project progress. For some contracts, the Company may be entitled to receive an advance payment. The Company applied the practical expedient for certain revenue streams to exclude the value of remaining performance obligations for (i) contracts with an original expected term of one year or less or (ii) contracts for which the Company recognizes revenue in proportion to the amount the Company has the right to invoice for services performed.

SUMMARY OF SIGNIFICANT ACCOUNTING POLICIES (Policies)

6 Months Ended

Jun. 30, 2025

Certain prior year amounts are reclassified to conform to the current year presentation. This includes the separate disclosure of changes in Income taxes within operating activities on the Consolidated Statement of Cash Flows.

Supply Chain Financing

Amounts outstanding related to supply chain financing programs are included in Accounts payable in the Consolidated Balance Sheet.

Recent Accounting Pronouncements

The Company considers the applicability and impact of all Accounting Standards Updates (ASUs) issued by the Financial Accounting Standards Board (FASB). ASUs not listed below were assessed and determined to be either not applicable or are expected to have minimal impact on the Company's Consolidated Financial Statements.

In November 2024, the FASB issued ASU 2024-03, Income Statement—Reporting Comprehensive Income—Expense Disaggregation Disclosures (Subtopic 220-40): Disaggregation of Income Statement Expenses, which requires companies to disclose additional information about the types of expenses in commonly presented expense captions. The new standard requires tabular disclosure of specified natural expenses in certain expense captions, a qualitative description of amounts that are not separately disaggregated, and disclosure of the Company's definition and total amount of selling expenses. The ASU should be applied prospectively for annual reporting periods beginning after December 15, 2026, with retrospective application and early adoption permitted. The Company is currently evaluating the impacts of this guidance on the Company's Consolidated Financial Statements.

In December 2023, the FASB issued ASU 2023-09, Income Taxes (Topic 740): Improvements to Income Taxes Disclosures, which requires greater disaggregation of income tax disclosures. The new standard requires additional information to be disclosed annually with respect to the income tax rate reconciliation and income taxes paid disaggregated by jurisdiction. This ASU should be applied prospectively for fiscal years beginning after December 15, 2024, with retrospective application permitted. The Company is currently evaluating the impacts of this guidance on the Company’s Consolidated Financial Statements.

In November 2023, the FASB issued ASU 2023-07, Segment Reporting (Topic 280): Improvements to Reportable Segment Disclosures, which requires companies to enhance the disclosures about segment expenses. The new standard requires the disclosure of the Company’s Chief Operating Decision Maker (CODM), expanded incremental line-item disclosures of significant segment expenses used by the CODM for decision-making, and the inclusion of previous annual only segment disclosure requirements on a quarterly basis. This ASU should be applied retrospectively for fiscal years beginning after December 15, 2023, and interim periods within fiscal years beginning after December 15, 2024. The Company adopted this guidance for annual disclosures for the year ended December 31, 2024, and interim disclosures for the first quarter of 2025. The adoption of this standard did not have a material impact on the Company’s Consolidated Financial Statements.

Revenue Recognition and Contracts with Customers

The Company tracks progress on satisfying performance obligations under contracts with customers. The related billings and cash collections are recorded in the Consolidated Balance Sheet in Accounts receivable—net and Other assets (unbilled receivables (contract assets) and billed receivables), and Accrued liabilities and Other liabilities (customer advances and deposits (contract liabilities)). Unbilled receivables arise when the timing of cash collected from customers differs from the timing of revenue recognition, such as when contract provisions require specific milestones to be met before a customer can be billed. Contract assets are recognized when the revenue associated with the contract is recognized prior to billing and derecognized when billed in accordance with the terms of the contract. Contract liabilities are recorded when customers remit contractual cash payments in advance of the Company satisfying performance obligations under contractual arrangements, including those with performance obligations to be satisfied over a period of time. Contract liabilities are derecognized when revenue is recorded, either when a milestone is met triggering the contractual right to bill or when the performance obligation is satisfied.

Contract balances are classified as assets or liabilities on a contract-by-contract basis at the end of each reporting period.

When contracts are modified to account for changes in contract specifications and requirements, the Company considers whether the modification either creates new or changes the existing enforceable rights and obligations. Contract modifications for goods or services and not distinct from the existing contract, due to the significant integration with the original good or service provided, are accounted for as if they were part of that existing contract. The effect of a contract modification on the transaction price and the Company's measure of progress for the performance obligation to which it relates, is recognized as an adjustment to revenue (either as an increase in or a reduction of revenue) on a cumulative catch-up basis. When the modifications include additional performance obligations that are distinct and at relative stand-alone selling price, they are accounted for as a new contract and performance obligation, which are recognized prospectively.

PERFORMANCE OBLIGATIONS

A performance obligation is a promise in a contract to transfer a distinct good or service to the customer and is defined as the unit of account. A contract’s transaction price is allocated to each distinct performance obligation and recognized as revenue when, or as, the performance obligation is satisfied. When the contracts with customers require highly complex integration or manufacturing services that are not separately identifiable from other promises in the contracts and, therefore, not distinct, then the entire contract is accounted for as a single performance obligation. In situations when the Company's contracts include distinct goods or services that are substantially the same and have the same pattern of transfer to the customer over time, they are recognized as a series of distinct goods or services. For any contracts with multiple performance obligations, the Company allocates the contract’s transaction price to each performance obligation based on the estimated relative stand-alone selling price of each distinct good or service in the contract. For product sales, each product sold to a customer typically represents a distinct performance obligation. In such cases, the observable stand-alone sales are used to determine the stand-alone selling price.

Performance obligations are satisfied as of a point in time or over time. Performance obligations are supported by contracts with customers, providing a framework for the nature of the distinct goods, services, or bundle of goods and services. The timing of satisfying the performance obligation is typically indicated by the terms of the contract.

Performance obligations recognized as of June 30, 2025, will be satisfied over the course of future periods. The Company's disclosure of the timing for satisfying the performance obligation is based on the requirements of contracts with customers. However, from time to time, these contracts may be subject to modifications, impacting the timing of satisfying the performance obligations. Performance obligations expected to be satisfied within one year and greater than one year are 56% and 44%, respectively.

The timing of satisfaction of the Company's performance obligations does not significantly vary from the typical timing of payment. Typical payment terms of the Company's fixed price over time contracts include progress payments based on specified events or milestones or based on project progress. For some contracts, the Company may be entitled to receive an advance payment.

The Company applied the practical expedient for certain revenue streams to exclude the value of remaining performance obligations for (i) contracts with an original expected term of one year or less or (ii) contracts for which the Company recognizes revenue in proportion to the amount the Company has the right to invoice for services performed.