hexagon logo

Profile and Actual Zone

This is a little more of a GD&T standards question as opposed to a PC-DMIS question-- and probably a rudimentary question at that:  According to ASME Y14.5.1 2019, to report out a profile, you take the extreme point on whatever side of the true profile it is, and double it to get the "actual zone."  This is how profile is to be reported whether we're checking the profile manually with an indicator or using inspection software.  My question is why is this the way to calculate it as opposed to adding the highs and lows together (FIM) like a form or orientation inspection?  Engineers have asked me about this before and the most elementary way of answering it was to tell them that the profile result was representing what the profile tolerance "would have to be" in order to pass because doubling that value created a new zone (actual MMB and actual LMB).  I'm still not entirely sure why.

For the record, I never read the actual ASME Y14.5.1 2019 text; I only watched videos about it so there's a good chance that I'm missing info.

Parents Reply
  • I've said this before, and I'll say it again.  Legacy can most certainly DO simultaneous evaluations.  Been doing it for over 30 years with Pcdmis, still doing it to this day.  Make your alignment, measure your features, report your features.  EVERY ONE of those dimensions have been done using simultaneous evaluations.

    https://www.dimensionalconsulting.com/simultaneous-requirements.html

    • Simultaneous Requirements means that the requirements apply at the same time (yup)
    • Simultaneous Requirements are gaged in the same gage at the same time (yup)
    • Simultaneous Requirements apply to Tolerance of Position and Profile (yup)
    • Requirements are simultaneous when they locate the features (yup)
      To the same datums (yup)
      In the same order (yup)
      At the same material condition (yup, even through they put it on the print, 99% of automotive doesn't allow you MMC/LMC on datum holes)
Children
  • Whilst what you say is technically correct, the whole point of a simultaneous requirement is to ensure the same datum shift is applied across all relevant dimensions.  If the datum reference frame is fully constrained and all datums are RFS then there IS NO datum shift, in which case you will get the same result whether you invoke simultaneity or not.

    As soon as you have a partially constrained DRF and datum modifiers to contend with, there is no easy way of reporting multiple legacy dimensions simultaneously.