EC (Engineering Change)

What is EC (Engineering Change)?

In government contracting, an Engineering Change (EC) represents a formal process for modifying a deliverable product or service after the initial contract specifications have been established. These changes can affect design, functionality, performance, or even the manufacturing process itself and require careful management.

Definition

An Engineering Change (EC) is a systematic alteration to a product’s specifications, design, or manufacturing process subsequent to its initial release. In the context of government contracts, ECs are often initiated to address unforeseen issues, incorporate technological advancements, improve performance, rectify defects, or meet evolving mission needs. The implementation of an EC requires formal documentation, review, and approval by both the contractor and the government.

The specific requirements for managing ECs are typically outlined in the contract's terms and conditions and often reference standards for configuration management. Successfully managing ECs is vital for government contractors because improperly managed changes can lead to delays, increased costs, and non-compliance. It's also important to remember that each EC must be compliant with regulatory bodies and standards.

Key Points

• Impact Analysis: ECs require thorough impact assessments. These assessments should examine the effects on cost, schedule, performance, interoperability, and other contractual obligations.
• Formal Documentation: The government requires meticulous documentation. Contractors must use Engineering Change Proposals (ECPs) to describe the change, its rationale, and all related impacts.
• Government Approval: Most ECs impacting performance, cost, or schedule require formal approval by the Contracting Officer (CO) or their designated representative.
• Configuration Management: Implement approved ECs within a robust configuration management system. This system should track changes, versions, and ensure proper integration.

Practical Examples

1. Component Obsolescence: A contractor providing electronic equipment discovers a critical component is no longer available. An EC is needed to identify and validate a suitable replacement, potentially affecting performance and cost.
2. Performance Improvement: During testing, a weapon system fails to meet a key performance requirement. An EC is proposed to modify the design to enhance performance, necessitating design changes and re-testing.
3. Cybersecurity Update: A software vulnerability is identified in a deployed system. An EC is required to develop and implement a patch, potentially affecting system functionality and requiring re-certification.