Functional vs. Process Driven GD&T
Functional vs. Process Driven GD&T
(OP)
Hello,
This time a little bit less specific question:
I am looking for some good real life examples showing differences between function and process driven GD&T, and somehow proving that function-based dimensioning and tolerancing is indeed beneficial in comparison to the latter approach.
Did anyone ever experience a situation when for instance manufacturing dept. insisted on adjusting GD&T scheme to their needs (tolerance values, datum structures, etc.), but at the end of the day, after doing some stacks, it occured that tolerances were unnecessarily tighten from functional point of view?
Any input will be really valuable.
Thanks a lot.
This time a little bit less specific question:
I am looking for some good real life examples showing differences between function and process driven GD&T, and somehow proving that function-based dimensioning and tolerancing is indeed beneficial in comparison to the latter approach.
Did anyone ever experience a situation when for instance manufacturing dept. insisted on adjusting GD&T scheme to their needs (tolerance values, datum structures, etc.), but at the end of the day, after doing some stacks, it occured that tolerances were unnecessarily tighten from functional point of view?
Any input will be really valuable.
Thanks a lot.





RE: Functional vs. Process Driven GD&T
Simple, I see it all the time. The shop wants to hold stuff like mounting screw holes for mounting simple electrical cover plates to main datums systems on large caastings. This is so they do not have to establish the actual (functional) cast electrical box datums and can machine in one set up. In the "good old days', before CNC, they would have had a jig to locate the holes for the cover and had a real person drill them on a press. The parts were actually functionally better then, but more capital and labor intensive.
Frank
RE: Functional vs. Process Driven GD&T
GD&T should be process oriented to the extent that your part can be fabricated by the process you think they are going to use. If the process cannot achieve the tolerances, either you must loosen them somehow, or you must go to another process.
Otherwise, GD&T should be based on functional requirements.
Designers must have some understanding of what fabrication processes can achieve, and apply tolerances accordingly. If the tolerance stack does not work, there is re-design to be done.
RE: Functional vs. Process Driven GD&T
Let's say that designer has sufficient understanding of what fabrication processes can achieve, but, as Frank nicely described, the shop demands other than functional set of datum features in order to make their life easier during fabrication. So in consequence the designer is forced to assign non-functional datum features on a print. What then?
RE: Functional vs. Process Driven GD&T
I don't know much about ISO things and I don't even know if what this inspector told me was correct but it seems that using averages are inherently flawed. I don't even know if I'm really addressing your question.
Powerhound, GDTP S-0731
Engineering Technician
Inventor 2010
Mastercam X6
Smartcam 11.1
SSG, U.S. Army
Taji, Iraq OIF II
RE: Functional vs. Process Driven GD&T
Theory is fine but it is the fact it is not followed in practice or doesn't apply to real world applications that is the whole problem I see with many of my day-to-day GD&T issues. I keep trying to stress it here amongst (sorry!) the elites. This is also why I now think the ISO's method may be the best way, just hold their feet to the fire!
Frank
RE: Functional vs. Process Driven GD&T
The worst part is, all the time and money we spend blaming the casting vendor because his casting is not accurate enough when it was just fine before, it is our processing that has changed.
How many do you want? ;)
Frank
RE: Functional vs. Process Driven GD&T
I'd actually used a roll pin in a part to help position/self fixture part during assembly. I'd made the hole the pin wend into the tertiary datum for related holes etc.
Well the vendor had instead used an edge near the hole as the datum and all features were shifted by .15 accordingly.
I pointed out that I'd dimensioned based on function. They replied back with the old truism that it was bast to go from a corner of the part.
Initially I resisted making change but then lost the will to care and made the surface they'd actually used the datum as the tolerances etc. were well within process capability & in the application an argument could be made that that surface was a functional datum (though in my opinion if was a weaker argument than using the hole).
What is Engineering anyway: FAQ1088-1484: In layman terms, what is "engineering"?
RE: Functional vs. Process Driven GD&T
I have never been in this argument.
If you prepare your drawings carefully, your datums will work. For example, if you are designing a machined casting, you should specify datum targets, so that everyone works from the same set of datums.
When I was trained on ASME Y14.5M-1994, I was told that the datums specify fixturing for both fabrication and inspection. My final cop-out would be to inspect the part using the official datums. If it passes, it is okay, and I do not care how the fabricator did it.
Conceivably, a fabricator could use your fabrication drawings that specify the part, and create his own fabrication drawings. He could use his own datums that suit his fabrication process, tightening tolerances to make your official datums work. If your parts are good, you should be happy.
RE: Functional vs. Process Driven GD&T
I am assuming you meant "best"?
I remember those days, "0"-lines on the edges, inspection determined the order of precedence. We are not required to go quite that far, I am sure there are many who still wish be did, though. Definately, no envelope principle here, though!
Frank
RE: Functional vs. Process Driven GD&T
What is Engineering anyway: FAQ1088-1484: In layman terms, what is "engineering"?
RE: Functional vs. Process Driven GD&T
Your last paragraph is a very common scenario. Your last sentence is spot on.
Powerhound, GDTP S-0731
Engineering Technician
Inventor 2010
Mastercam X6
Smartcam 11.1
SSG, U.S. Army
Taji, Iraq OIF II
RE: Functional vs. Process Driven GD&T
I was somehow hoping to hear that process driven selection of datum features is quite common practice in the industry. Your replies seem to confirm my experience with similar situations.
There is an example in A.Krulikowski's "Advanced Concepts of GD&T" (7th edition, pages 13-6 & 13-7) explaining a disadvantage of such datum structure conversion. Though I do not think the problem is always such black and white, in my opinion the example quite nicely emphasizes the issue. I attached these two pages below.
http:/
RE: Functional vs. Process Driven GD&T
In a perfect world design engineer should possess significant amount of manufacturing as well as quality control related knowledge. In today's world of $10/hr CAD-monkeys – don't get me started.
So in reality we end up with some sort of compromise.
Example one: small shop to small shop. GD&T is not used. Shop is trying hard with some amount of trial and error. Once they find "the sweet spot" they can run good parts forever. (Until new management shows up at either company and starts improving things.
Example two: manufacturing starts yelling "we cannot do that" even before the last print is unrolled. They are trying to make their life easier even before job started. Sometimes you may be surprised that after loosening all the tolerances your machine still works (which may prove that you didn't really know what functional requirements are)
Example three: the product is really big, complicated and important. You will never get it right from the first time. On prototype stage, when trying to assemble it, you figure out REAL functional requirements. On preliminary production run shop starts realizing what is holding them back, and comes with some feedback. By the time of full-scale production your drawings start taking decent shape.
So, I don't think you will find definitive answer in the real world.
RE: Functional vs. Process Driven GD&T
At least you guys work in the same world I do! I am glad to know I am not alone out here.
Frank
RE: Functional vs. Process Driven GD&T
Frank
RE: Functional vs. Process Driven GD&T
I will try to throw in few more examples to support my case.
Look at this 30-something years old book intended for draftsmen, not even engineers.
The paragraph 10 "Shop processes" stretches from page 267 to page 297, that's 30 pages.
The paragraph 12 "Tolerancing" goes from page 335 to page 355, that's only 20 pages.
As you can see both are getting at least equal attention (at least back in time when drafting was respectable profession).
RE: Functional vs. Process Driven GD&T
There is never time to do it right, but always time to do it over.
RE: Functional vs. Process Driven GD&T
Can you, please, give me that new ISO book title again?
Frank :)
RE: Functional vs. Process Driven GD&T
The ISO Geometrical Product Specifications – Find your way in GPS (378 pages, B5 format, English only, ISBN 978-87-7310-721-8)
I am afraid you will wait forever for it to appear on Amazon.
I ordered copy directly from ISO. It is not difficult; all you need is a credit card. The shipping cost hurts (a little).
The more I read it, the more I think it was worth it.
By the way, the guy is not big fan of ISO 2768. Go figure...
RE: Functional vs. Process Driven GD&T
What is Engineering anyway: FAQ1088-1484: In layman terms, what is "engineering"?
RE: Functional vs. Process Driven GD&T
RE: Functional vs. Process Driven GD&T
I have read Alex Krulikowski's "Advanced Concepts of GD&T" Chapter 13 The Datum System, and some of the shop floor mechanic fully agreed what Alex said while I talked with them regarding the datum setup, but I can't open your attached file, here is my post.
SeasonLee
RE: Functional vs. Process Driven GD&T
Thanks, Does he explain how 2768 is supposed to work in any more detail than Henzold? Henzold just basically introduces the concept like the ISO standard does, IMHO.
Frank ;)
RE: Functional vs. Process Driven GD&T
No, he is trying to avoid duplicating standard.
He points out "grey" legality of "no rejection" clause, as in "who is to decide if part actually works?"
RE: Functional vs. Process Driven GD&T
What is Engineering anyway: FAQ1088-1484: In layman terms, what is "engineering"?
RE: Functional vs. Process Driven GD&T
Thanks.
Note, however, that we subcontract all of our fabrication. We are the customer and we are always right. My impression is that the OP is not the customer. Depending on how his office politics work, he could be frequently, and possibly always wrong.
RE: Functional vs. Process Driven GD&T
Frank
RE: Functional vs. Process Driven GD&T
The company starts outsourcing. The company doesn't use GD&T. They actually buy/build gauges and ship them following the prints. Company gets back good parts.
Now, what are the alternatives?
In order to get back good parts without sending out some heavy iron (or living, breathing engineer) is for your GD&T to have enough data for gauges to be built locally.
And that will make your GD&T (just a little bit) process-oriented.
RE: Functional vs. Process Driven GD&T
All I was saying is that it happens more often than one would like to think. Ultimately the part has to conform to the print per the DRF. Nothing says a part has to be built that way. Whether you establish a datum then drill a hole WRT it or drill the hole and establish the datum later makes no difference. What does matter is how it's checked. If it checks out then how it was made is irrelevant. Simplistic, I know, but that's really my point.
Powerhound, GDTP S-0731
Engineering Technician
Inventor 2010
Mastercam X6
Smartcam 11.1
SSG, U.S. Army
Taji, Iraq OIF II
RE: Functional vs. Process Driven GD&T
I think most of us here, believe that.
You guys may have just talked me into getting Alex's book.
Frank
RE: Functional vs. Process Driven GD&T
You are a bit late.
Alex's "Advanced" is long out of print.
RE: Functional vs. Process Driven GD&T
Powerhound, GDTP S-0731
Engineering Technician
Inventor 2010
Mastercam X6
Smartcam 11.1
SSG, U.S. Army
Taji, Iraq OIF II