Parts included/not included in ECO/ECN

R

ramack

I'm new to this forum, came across it while looking for ECO/ECN info. I've started a new job about 3 months ago. One of the things that I'm in charge of is ECOs. This is a pretty small company that is fairly new and document control is pretty poor which has caused a gamut of issues. There is a PLM package that is being used, but it's really more for Sales, Work Orders/Pick Lists and inventory management. It does have an ECO/ECN module, which is pretty basic, but better than nothing.

So, with that background, a discussion arose about what I'm including in the ECO. In a nutshell, say I have an Assembly A. In that assembly, there is a Part B. There is also a Part C that is not part of the BOM and assembly. I'm substituting Part B with Part C and I've started an ECO for this change. So my question is this. What should be included in the ECO? I am including and "tagging" all three (in this very generic situation), the Assembly A, Part B and Part C because all three are involved "in" the change, but only Assembly A is actually being changed. My "superior" , who is also one of the biz owners view is that only the Assembly A should be included and only note the substitution of Part B with Part C.

By "tagging" Parts B and C as being part of the ECO, they will have that ECO history with this change and future changes if there are any. By not specifically including them into the ECO, any linking to this or other ECOs will not be retained.

So I guess in short the question is what becomes included in the ECO/ECN, the assembly that is being directly being changed or all items, parts and assemblies that are involved in the change?

Just curious what the views are from those that have been involved with ECO. I've fortunately in the past, haven't had to deal with ECOs since most of what I do is R&D, prototyping and one offs.
Thanks,
 
Last edited by a moderator:

Ronen E

Problem Solver
Moderator
Re: Parts included/not included in ECN

Hello and welcome to the Cove!

One factor to consider is whether the attribute “assemblies where the item is used” is included in your system. If it is, then obviously parts B & C change under that generic change scenario.

Technically I tend to agree with your point of view, but it’s well established in business that “It’s the boss’s right to be the boss.” Tread lightly, and may the force be with you.

Ronen.
 
Top Bottom