Engineering Change Order

Sent you an E-mail...

Dear Sir,

I am also interested in getting the same please mail me to srinivigna@yahoo.com

I have designed processes and built hundreds of forms, both static, and programmed in vb/vba. I can help you out. The ECO sytem was integrated with the rest of the quality management docs (non-conformance reports, corrective action reports, preventive action reports, and other change oriented docs.) and all had a corresponding register for managing them. Depending on the level of sophistication, and the amount of changes, and the level of training involved, so will the design of the system vary. Tell me what you are looking for, and I can help you with the documentation. Designing forms is easy. If that is all you want, I can do that for free, and work out the features with you. That is a form of play for me. (sorry for the pun)

How many change orders in a month?

How many users to the system?

What level of training for the user?

What kind of support will you need for the system?

Do you have a quality system in place?

Chris

That is a good concept brought out (It remains in our subconscious) The forms or systems designed must be integrated to the over-all QMS of the organisation.
We have the whole lot (Now going for the SAP - earlier had good old oracle, still running- where whole gamut was under single umbrella) It had the Quality management, Customer Portal, marketing, Purchase, Vendor management, Design Management etc all interlinked (internall), However user of one particular site will not and need not bother what is being done with his data.
Eg the data on NCs already updates the vendor rating system. Design change system updates the part list, manufacturing documents etc,

Well languaged the concept GA.

I strongly agree with a linked electronic system. It saves so much time and reduces errors (of the human kind).

On the flip side, try and keep it simple. Attaching or referencing relevant information is more valuable than filling out the form. Too many times forms like this repeat information from other forms or even on the same form.

Consider making it a 2-part format. ECR (engineering change request) and ECO in one format allows original information to be retained and not duplicated.

Also, keep in mind the cost of processing the ECO. A customer of ours refuses many good suggested changes simply because they have determined that it costs them $10,000 for every ECO circulated.

Allow your sign-off process to skip non-relevant departments as required. It saves time and headaches. Introducing a simple process to streamline the sing-off process is worth the effort.

Side note - many companies have moved away from the term "Engineering Change Order". Apparently people don't like being "ordered" around by Engineers. ECP (proceedure) is common or ECN (notification)

We use a field change order when we have discovery work that is not in the original scope. It basically describes the work the cost and the reason and has a place for signature from the associated managers. I may be able to take off the co. name and send you a copy if you do not find one.