Do we need issue ECN (Engineering Change Notice) towards updated Material Specification?

[Rizkyffq]

Hello All,

Hopefully my thread is not OOT (out of topic), due i think this is very relevant to Design and Development.
So i got problem in my factory, the problem is related with ECN (Engineering Change Notice).
Our R&D recently has updated their material specification pertaining with low alloy steel 41XX which. The changes is to separate one material spec into two material spec, due there is one product that need more requirement than other product, in simple means there are two material specs of low alloy steel 41XX (General Use vs Specific Use).

Usually update/revision for material spec is not issued by ECN, our QMS will transmit it to HOD for all department (Only HOD ; Head of Department).
In our knowledge, ECN is only for Drawing changes not for Material Specification Changes.

In response by not using ECN, there are any department that missed the information of material specification changes, Purchasing department for example that his staff does not know material specification for Product A is actually must using material specification for generic use, but he uses old material specification. (this is because the transmittal of document for material specification by QMS only sent to HOD not all personnel).

Is there any system to give information about material specification update other than ECN, due ECN as our knowledge is scoped only for drawing changes not document changes.

Hope someone here has expertise on case like this.
Before Many thanks guys

 

[John Predmore]

ECN does not stand for Drawing Change Notice. Many companies I have worked for use the ECN system to approve and communicate changes to material specifications, and IMO a material change which affects the design is an engineering change.

 

[John C. Abnet]

Hello All,

Is there any system to give information about material specification update other than ECN, due ECN as our knowledge is scoped only for drawing changes not document changes.

Good day @Rizkyffq ;
Maybe the issue has to do with terms? ....possibly semantics?

I generally council my clients to avoid terms such as specific as "EngineeringCN

What is the goal of an ECN? Isn't it simply to control and notify of changes? In reality, isn't it simply a component of Change Point Control?

Consider this:
Your organization wishes to change a document or process. If that change can lead to a nonconformance, then that change should be controlled. Control may take on different appearances depending on the context and the size and/or scope of the organization. What constitutes as "control" is for your organization to decide. Generally, control means to ensure obsolete information is no longer available to the user, new information is conveyed to all interested parties, any necessary approvals are gained, and the date of implementing the "new" situation is logged for traceability.


Hope this helps.

Be well.