ECO and ECR software

ECR versus ECO, and a workflow that survives an audit

Hardware teams search for ECO software and ECR software because the words get used interchangeably in email, then an auditor asks which record authorized the housing thickness change. They are not the same step. An engineering change request (ECR) is the proposal: a requestor describes what is wrong or what should change, names affected items, and asks the organization to decide. An engineering change order (ECO) is the authorized packet that implements the approved change — the items, the new revision of the drawing, the date it became the released original.

Some companies file an ECR, then convert it to an ECO when it is approved. Some skip the request and go straight to an order. Either way, quality expects a record with a requestor, a decision, and a trail. If the only artifact is a thread titled "please update the drawing," you do not have change control. You have archaeology.

A typical approval workflow looks like this. A design or manufacturing engineer opens a change, attaches the affected parts and assemblies, and writes why. The packet routes to people who are allowed to approve — not to everyone on a distribution list. One eligible approver can sign; the person who filed the request cannot also approve it. That separation of duties is the rule, not a preference. After approval, the new revision is released. Only then is there something a supplier is allowed to see. Drafts stay inside. The shop and the CM should not be looking at a work-in-progress PDF from someone's desktop.

The workflow has to be recorded on the change, not reconstructed from who was CC'd. When Quality or a customer asks who approved the thickness change and when the new drawing became released, the answer is the change record sitting on the same tenant as the BOM. That is ECO/ECR software. A description field in a ticket tool is not.

After release, the drawing still has to reach the supplier. Most PLM tools solve that by inviting the supplier as a user of the change packet. That creates a seat, a password, and a support ticket six months later. The supplier needed the current released PDF. They did not need an account.

Change as a packet, not a thread

Hardware teams search for ECO software, ECR software, and engineering change order because inbox CC lists do not survive an audit. In Nereite PLM you create a change record, route it through workflow steps, and keep affected items with the product record.

Approval is any-one eligible approver. The person who requested the change cannot approve their own request. That is the separation of duties quality expects, without a custom QMS bolted on the side.

Where drawings fit

When the change releases a new drawing revision, suppliers still never get a login. You Notify a share of the latest released PDF; they open it with a one-time code. The change history stays inside the tenant.

Questions