yang686526

change order
i thought i should post this under the config management fora... but it's not very active. + i participate here some so here goes.
does anyone know the technical difference between an engineering change order (eco) and engineering change request (ecr). we seem to use them interchangeably in my office here. and all the previous places i've worked have just used eco.
wes c.
if they are separate docs, the ecr would be written first, approved, then submitted to do the work. the eco is the doc that is written with description of changes (referencing the ecr#) and released to the files with the revised docs.
some companies don't see a need for more paperwork and/or understand config mngmt of documentation, so they just write a eco to describe changes and release it.
chris
sr. mechanical designer, cad
solidworks 05 sp3.1 / pdmworks 05
this varies from company to company, but in general an ecr is exactly what the name says. a request to the engineering department to make a design change. it may originate from the manufacturing department, a customer, or a vendor.
the engineering department should review the ecr, and if found acceptable, will issue an eco (or ecn, engineering change notice) along with the revised drawings or specs. the eco serves to document why the change was made.
typically there is no ecr if the change originates in the engineering department.
we use both and the ecr is useful to document the reason for the change if it comes from outside of engineering. a lot of times it gets bypassed if someone calls from production and we issue the eco directly. that is ok if it is a simple change like a missing washer, but for something more involved i would rather tell the boss to take it up with so-and-so on the line if he doesn't agree with it. an ecr often times gets thrown on the pile and forgotten about. sometimes the need for it has gone away by the time it is found again.
we use rfc & ecn (engineering change notice), but it is the same document. it has a checkbox, and if it is a customer request, then it's a rfc. if it is an internal change, then its an ecn.
flores
sw 2005 sp 4.0
i have the hardest time to get the manufacturing floor or assembly line to use ecrs. many times i get a phone call, most times someone drags something to my desk. i smile and hand them a blank ecr form after the discussion and i get that deer-caught-in-the-headlights look.
i think there is a world market for maybe five computers.
thomas watson, chairman of ibm, 1943.
thanks guys, that really clairfies it for me.
the lightbulb ((o)) goes on and i get it
wes c.
we have just implemented ptc's pdmlink. it is cmii compliant when it comes to change orders.
there are various levels:
1. problem report - many can be written against the same part
2. ecrequest - many problem reports can be combined into a single change request.
3. ecnotice - the end result of the ecr.
"wildfires are dangerous, hard to control, and economically catastrophic."
"fixed in the next release" should replace "product first" as the ptc slogan.
ben loosli
cad/cam system analyst
ingersoll-rand