ASME GDTP Technologist common mistakes
ASME GDTP Technologist · Understand the traps and how to avoid them.
Accepts a flatness, straightness, circularity, or cylindricity callout that carries datum references in the feature control frame, or expects one of those controls to orient/locate a surface to a datum.
Candidates memorize the symbol set as a list and sort by shape (plane, cylinder, surface) instead of by the attribute being controlled, so 'form' and 'orientation' symbols blur together under exam pressure.
What to do instead
Build a two-column table from memory: form controls (flatness, straightness, circularity, cylindricity) never take datums; orientation controls (parallelism, perpendicularity, angularity) always do; profile may take datums but need not; runout requires a datum axis. Drill by classifying a symbol first, then reading the frame.
Locates a datum axis or datum plane at the as-built surface or center of the actual part (e.g., puts the datum axis at the measured center of a hole) instead of at the datum feature simulator.
Candidates reason from the physical part they can see rather than from the inspection setup, and the simulators (surface plate, expanding mandrel, chuck, V-block) are invisible in the drawing.
What to do instead
For every datum feature, name the simulator out loud: a flat face is simulated by a surface plate and the datum plane is the plate; an external cylinder is simulated by a chuck/collet (smallest circumscribed); an internal cylinder by an expanding mandrel (largest inscribed). Then note that datum-related tolerances are evaluated against that simulator-derived axis/plane, never the actual surface.
Rejects a perfectly round but tapered or barreled cylinder for failing circularity, or assumes circularity limits total surface variation along the length.
The words 'round' and 'circular' pull candidates toward thinking of the whole cylindrical surface, and cylindricity is easily conflated with circularity because both use the same cross-section picture.
What to do instead
State the zone explicitly: circularity is a 2D annular zone between two concentric circles evaluated independently in each cross-section, with no datum and no control of taper, size, straightness, or alignment. Only cylindricity uses two coaxial cylinders over the full length. When a question describes taper, boresight, or variation along the axis, circularity is not the answer.
Marks an angularity (or perpendicularity/parallelism) requirement as failed because the toleranced surface is also too far from, or wrongly positioned relative to, the datum, or because the surface's distance varies across the part.
Orientation and location are conceptually adjacent, and the same surface can be shown in a figure where the offset is visibly wrong, so candidates over-attribute the failure to the orientation control.
What to do instead
Apply the test: orientation controls only the angle of the zone relative to the datum (basic angle for angularity, 90 degrees for perpendicularity, 0 degrees for parallelism); the zone floats in location. Location of the feature must be held by a separate position, profile, or size dimension. Before answering, ask 'is the angle right but the distance wrong?' - if yes, the orientation control passes.
Computes bonus tolerance for a position tolerance at MMC as (measured local size at any one cross-section minus MMC size) and then adds it to the stated tolerance, or applies the same sign of bonus to both internal and external features.
The candidate reduces bonus tolerance to 'actual size minus MMC' as a slogan and never internalizes that position at MMC is evaluated against the actual mating envelope, or that for external features the bonus runs the other way.
What to do instead
Write the formulas per case before computing. Internal feature (hole) at MMC: bonus = actual mating size (largest inscribed perfect cylinder) - MMC size. External feature (pin/boss) at MMC: bonus = MMC size - actual mating size (smallest circumscribed). Total allowable = stated tolerance + bonus, plus any separate datum shift if a datum is at MMC. Local size from a single cross-section may not be substituted for the mating envelope.
Treats every profile tolerance zone as a symmetrically disposed bilateral zone, and treats a profile of a line callout as controlling the whole surface (or profile of a surface as controlling only selected cross-sections).
The default bilateral zone is taught first and remembered best, and the U (unequal) modifier and the line/surface distinction are the least-practiced, least-drawn parts of the profile toolbox.
What to do instead
Read the frame for two things: (a) the symbol - profile of a line controls individual line elements independently, profile of a surface controls the entire surface; (b) the U modifier - the value after U states the amount of tolerance on one side of the true profile, with the remainder on the other. Also confirm every locating/profile dimension on the drawing is basic (boxed), since the profile frame supplies all the tolerance.
Applies an MMC or LMC modifier to a circular or total runout callout, or claims circular runout controls cylindricity and taper along the full length of the part.
Candidates generalize 'modifiers give bonus tolerance' across all geometric controls, and circular runout's indicator dial seems to sweep the whole surface in the illustration.
What to do instead
Fix two rules: runout is always RFS - no MMC/LMC modifier is permitted on either runout symbol; and circular runout is evaluated independently at each cross-section (it limits radial variation, not axial/taper variation), while total runout sweeps the entire surface and controls cumulative variation including taper and alignment in one control. Runout always requires a datum axis established from a cylindrical datum feature.
In a composite position frame, allows the lower segment to cite a datum reference that does not appear in the upper segment, or reverses the roles and expects the lower segment to locate the pattern to the datum reference frame.
The two segments are stacked and look like one callout, so candidates read the lower segment as an independent tolerance and lose track of which segment does the locating.
What to do instead
Apply the composite rule: the upper segment locates the pattern to the datum reference frame and controls the pattern's position; the lower segment is a refinement controlling feature-to-feature (and orientation) relationships, repeats the same symbol, has a smaller tolerance, and may cite only the same datums in the same order or fewer (a subset, never a new datum). Check datum order left to right in both segments before judging validity.
Computes virtual condition for an internal feature as MMC plus the geometric tolerance (or LMC minus), and substitutes the resultant condition value where virtual condition is asked for.
The boundary concepts are all 'size-of-the-tolerance-zone' math with similar-sounding names, and the plus/minus direction flips between internal and external features, so candidates guess the sign.
What to do instead
Derive both boundaries from the worst-case mating part instead of recalling signs. Virtual condition uses MMC: internal feature VC = MMC - geometric tolerance (the smallest hole that will accept the largest mating pin); external feature VC = MMC + geometric tolerance. Resultant condition uses LMC and the opposite direction: internal RC = LMC + geometric tolerance; external RC = LMC - geometric tolerance. Also confirm the geometric tolerance is at MMC or LMC before computing either boundary; at RFS there is no virtual condition.
Treats a boxed basic dimension as if it carried the general block tolerance and computes acceptable limits from it, or reads a parenthesized reference dimension as a controlled requirement.
Candidates skim the drawing for numbers and apply the title-block tolerance note reflexively, without noticing the rectangle around the value or the parentheses.
What to do instead
Before using any dimension, classify it: boxed = basic/theoretically exact, tolerance comes only from the associated feature control frame; parenthesized = reference, for information only, not inspected; plain = toleranced by the local or general note. Also confirm the FCF's reading order (symbol, tolerance value, modifiers, datum references in precedence order) and check the general notes for 'unless otherwise specified' defaults before declaring a requirement.