Previous in Forum: What do you feel about using Teflon tape on Gas Cutting Equipments?   Next in Forum: Q.C,INSPECTOR
Close
Close
Close
7 comments
Rate Comments: Nested
Participant

Join Date: May 2007
Location: USA
Posts: 1

Change Management Process - Who's Really Good?

07/15/2008 11:31 AM

I want to benchmark change management processes - Engineering Change Request through implementation. Which companies perform change management well (fast and effective) and what makes them special?

The company I work for manufactures small gas and electric vehicles for golf, trail and industrial applications producing about 650 units per day. While it is easier to discuss similar size products and processes, I am sure there is something to be learned from different industries as well.

Any thoughts or experiences you can share?

Register to Reply
Interested in this topic? By joining CR4 you can "subscribe" to
this discussion and receive notification when new comments are added.

Good Answers:

These comments received enough positive votes to make them "good answers".

"Almost" Good Answers:

Check out these comments that don't yet have enough votes to be "official" good answers and, if you agree with them, vote them!
Guru

Join Date: Jul 2006
Location: "Dancing over the abyss."
Posts: 4884
Good Answers: 243
#1

Re: Change Management Process - Who's Really Good?

07/15/2008 10:22 PM

'Which companies perform change management well" : my nominees: Boeing. Nasa.

"what makes them special?" They understand the urgency of Critical Human Safety (inverted delta) Issues.

milo

__________________
People say between two opposed opinions the truth lies in the middle. Not at all! Between them lies the problem, what is unseeable,eternally active life, contemplated in repose. Goethe
Register to Reply
5
Guru

Join Date: Aug 2007
Location: Columbia City, Indiana, USA
Posts: 836
Good Answers: 96
#2

Re: Change Management Process - Who's Really Good?

07/15/2008 11:32 PM

As a manufacturer, we have the same issues constantly ... and this has been my similar experience for my 38 years in my field at several manufacturing sites.

On one end of the spectrum is total bureaucracy ... slow, but effective in creating a paper trail, and as already mentioned, absolutely necessary for high-risk / safety issues. On the opposite end of the spectrum is the total, out-of-control, seat-of-the-pants (albeit well intentioned) process where nothing is documented. For most 'common' applications, neither works very well.

The challenge will be to create a system that people will actually use (the best process in the world is useless if folks don't use it properly ... 'play by the rules') and in that (again for most manufacturing environments) that just means a process that documents all you really need, but is as simple as possible. While there may be 'canned' methods, like trying to implement ERP / MRP, you often end up with a great process tool of which you only need some small percentage.

If it were me (and it is 'me' in my own 'sandbox' ), I would focus on the basics, then add as needed until you are happy with the system you have created. Start with Development Engineering / R&D, and create a system that documents all design changes in the development process. If you can implement this within an ERP system (or just about any maintained database) these changes will also instantly reflect cost impacts, and possibly development schedule impacts as well. Then, depending on your internal process of transferring from design to mass production (everyone is different in structure and nomenclature ... DV, PV, MP and all the associated and varied validation steps), the MP released documentation (BOM, Process Docs, Support Drawings and other defining documents) usually begins again with their own 'rev level', then the task becomes one of controlling parts and part revisions, processes and process revisions, the effects these changes have on sub-assemblies and WIP, and the effects these things have on the final assembly.

Did I mention that at this point it becomes quite a nightmare? Consider this scenario: Receiving inspection receives part 123, but it is out of spec. MRB decides that it can be used by deviation, but using it requires a different screw and washer, so a deviation is also written for the sub-assemblies that are effected. The challenge then is how to structure the effectivity (not a real word, but the only one that works), or for how long the deviation is effective (either time or number of parts). Actually, the paperwork is easy, but the control of the deviated parts and subsequent sub-assemblies can be quite a nightmare. On the shop floor, there is a pallet of sub-assemblies XYZ, and another pallet of XYZ which must be assumed to be the same, but they're not, because some were assembled with a deviated part and different screws. Both XYZs have the same form, fit, and function, but is there any downstream impact? Probably no one thought of that.

All this means is that to properly control changes (design process, production release, deviations, ECO and ECN, revision levels, WIP, Inventory management, Effectivity, Phase in / Phase out), you may (depending on where your company is today) need to completely re-think your basic part numbering system and part numbering protocols. (honestly, few companies began their operation with a good system and I have yet to find an environment that sooner or later didn't require 'major surgery' when it came to the documentation protocols.)

Certainly the aerospace and aviation industries are TOPS at the control process, but again it is very top-heavy and may be more than you need. Automotive would be a small step down on the ladder of complexity, but only a small step. One company who has always impressed me with their process and production controls (albeit seen from afar) is John Deere. Consider the level of their quality, there inherent need to create products with interchangeable parts that really do interchange ... for years, the fact that for some products they do large volume runs, but for many they are extremely complex and in short runs, and the fact that they can, in effect, build 'one-offs', or said differently, and they can intercede in a mass production run and do at least some level of 'customization' on selected items on the assembly line. Consider also, they are just folks, and their suppliers also 'mess up', they also have loads of ongoing development and changes, they make deviations to keep things going, and on and on ... all the same things you and I suffer. Again, I only see them from a distance, but I can't help but put them on a pedestal when it comes to manufacturing control prowess.

Okay, I have talked A LOT, and I appreciate your patience, but I do truly understand the dilemma one faces when trying to increase the level of controls.

Good luck, and kind regards.

__________________
"Just when I had all the answers, they changed all the questions"
Register to Reply Good Answer (Score 5)
Guru
United States - US - Statue of Liberty - New Member Hobbies - Fishing - New Member

Join Date: Nov 2007
Location: Gone to Alabama with my banjo on my knee...
Posts: 5595
Good Answers: 20
#5
In reply to #2

Re: Change Management Process - Who's Really Good?

07/16/2008 4:44 PM

OMG! What a good answer (so voted)! I'm glad I read the existing posts, this one and a couple of others say all and more that I would've.

__________________
Veni, vidi, video - I came, I saw, I got it on film.
Register to Reply Off Topic (Score 5)
Guru

Join Date: Aug 2007
Location: Columbia City, Indiana, USA
Posts: 836
Good Answers: 96
#6
In reply to #5

Re: Change Management Process - Who's Really Good?

07/16/2008 5:19 PM

Thanks, Friend ... I would have much preferred to write, "hey, we have solved all these problems", and MEANT IT

__________________
"Just when I had all the answers, they changed all the questions"
Register to Reply Off Topic (Score 5)
Guru
United States - US - Statue of Liberty - New Member Hobbies - Fishing - New Member

Join Date: Nov 2007
Location: Gone to Alabama with my banjo on my knee...
Posts: 5595
Good Answers: 20
#7
In reply to #6

Re: Change Management Process - Who's Really Good?

07/17/2008 8:05 AM

Oh, don't go there! Solve all the problems, Mate, and we're out of a job for sure!

__________________
Veni, vidi, video - I came, I saw, I got it on film.
Register to Reply Off Topic (Score 5)
Anonymous Poster
#3

Re: Change Management Process - Who's Really Good?

07/16/2008 1:59 AM

The design is mostly made to customer orders. The formal use of the EC process starts when a project has reached the first allocated baseline and the documentation has been approved and frozen. The main focus when designing the current process has been to enable a fast and quality focused process that can be supported in a PDM system. The process starts by the evaluation of a failure report and investigation of possible solutions. The suggestions are evaluated by a team, which decides on the proposed measures and writes ECO:s for all affected parts. This is followed by the redesign process, where the change is planned and executed, followed by a review and approval and finally the changed documents are distributed and archived. The amount of documents created and managed in the ECM have been reduced by the replacement of three different failure reports by one. There are currently only three document types that are specific to the ECM. The information is though still paper based for the change documentation, but the reduction of ECM documents makes it easier to implement the documents in a computer environment.

The normal procedure is that the ECO is signed by the project manager, design manager or product manager depending on level and type of the change. If the change for example contradicts a company policy, it must be signed by the product manager. The EC team is a flexible group, which is specially composed for each change proposal. This gives the company the possibility to always gather the most experienced people for each change, thus giving the opportunity of making the correct decision. A PDM system to support the process. Most PDM systems have a problem oriented approach linking one ECO to a problem, regardless the number of parts to be changed. The main objective with the computer support of ECM in a PDM system is to enable a faster change process. The EC team meetings could for example be supported by the viewing functionality of the PDM system to enable participants to view the information before the meeting. Moreover, the PDM system can be used to support check-in and check-out of documents and to support versioning of documents. In order to provide a fully automated process, only digital documents should be used in the process. Since most documents are created in computer tools, this should not cause any problems. Todays' paper based ECM related documents could be directly implemented in the PDM environment. This would enable an intuitive link between changes and product structures providing all team members with fast and accurate information about changes in the product structure.

Regards

Register to Reply
Power-User
United States - Member - U.S.A. Hobbies - Fishing - New Member

Join Date: Apr 2006
Location: Abbeville, SC
Posts: 108
Good Answers: 2
#4

Re: Change Management Process - Who's Really Good?

07/16/2008 8:46 AM

Our company does work for both Honda and Yamaha. Without a doubt Honda has a good Engineering change request format. It is a one sheet document that simply states the date, main PN, and child PN. Then there are 2 sections. Section 1 is for the original problem (issue) and section 2 is for the solution for this problem. There is also a small section for original part cost and new part cost.

Each section needs to have a small sketch (hand sketch ok). The first to show the problem, the second a solution. The main thing to remember, even with a big company like Honda, is to show and write like a fifth grader. This is not to be demeaning, but it is to make sure the point gets across (also Honda request it this way). We are engineers and understand complicated issues and the affects of change. However a lot of individuals looking at these documents are paper pushers and they need a little more info to process the issue at hand.

Just remember to take all request seriously. If the employee's feel like their request are being dis-regarded, then they are less likely to suggest anything in the future. Remember also that if the EC has been accepted and it is a cost savings to the company, or a resolve of a safety issue, that the employee gets some kind of compensation to that effect. This will keep them thinking and on their toes.

Hope this helps some.

__________________
There are always others less fortunate than you, be happy, to them you are Mr. Jones.
Register to Reply Score 1 for Good Answer
Register to Reply 7 comments

Good Answers:

These comments received enough positive votes to make them "good answers".

"Almost" Good Answers:

Check out these comments that don't yet have enough votes to be "official" good answers and, if you agree with them, vote them!
Copy to Clipboard

Users who posted comments:

Anonymous Poster (1); DCaD (2); EnviroMan (2); Milo (1); possum (1)

Previous in Forum: What do you feel about using Teflon tape on Gas Cutting Equipments?   Next in Forum: Q.C,INSPECTOR

Advertisement