Metrology software vendor Metrologic DCS has set out four practices it says can narrow the gap between geometric dimensioning and tolerancing (GD&T) as defined in design data and the measurements and reports that reach the shop floor. The company describes GD&T as the language linking design, production and metrology: applied well, it ensures a part assembles and functions as intended; misinterpreted, it produces conflicting measurements, scrap and costly back-and-forth between teams.
The risk is multiplying, the company argues, because product manufacturing information (PMI) is increasingly embedded in CAD files while standards keep evolving. Its recommendations run from reading design intent through to the reports handed to machine operators.
Start from the PMI
Using PMI means decoding design intent: which feature is targeted, which references apply and which tolerance is specified. Done manually, the company says, this step is error-prone. A value copied incorrectly or a reference misunderstood leaves the part inspected against a requirement that was never specified. Its advice is to use software that takes the PMI as its starting point instead of re-entering tolerances by hand, so that features and their evaluations are generated from the part's digital definition. The stated result is no re-keying, fewer interpretation gaps and time saved from the first step of program preparation.
Do not rebuild datum reference frames by hand
The datum reference frame (DRF) establishes where measurement starts. Built from reference features A, B and C, it determines which degrees of freedom are constrained for an evaluation. If it is constructed in the wrong order, or if the degrees of freedom are poorly selected, the same part can be declared conforming or non-conforming depending on the operator — a situation Metrologic DCS describes as a major source of GD&T misinterpretation. Automating the step, so that the DRF and its degrees of freedom follow the drawing definition rather than operator choice, is presented as the way to make results repeatable from one operator, one machine and one site to the next. In the company's Metrolog software, the DRF is created automatically when a GD&T is evaluated.
Reuse imported DRFs
Reference features are already defined in the CAD model, where the design office places the A, B and C labels. Recreating them during program preparation wastes time, opens the door to discrepancies and forces rework whenever the definition changes, according to the article; on a part carrying many annotations, it is also hard to tell which ones have been handled and which remain to be measured. The proposed approach is to start from the DRFs supplied by the PMI and predefine GD&T from them, while keeping a clear view of where each annotation sits on the part and how far its measurement has progressed. Metrolog's Scan GDT function is said to read decoded PMI and assign a status so that both the decoding and the measurement can be validated.
Reports the shop floor can act on
A report limited to pass or fail does not tell the shop floor what to do, the company notes. An operator who does not know which kind of defect is present adjusts by trial and error, which generates scrap and correction loops. It recommends tailoring the output to its reader: a table of numerical values for quality control, a go/no-go report for a quick decision and a decomposition analysis for the operator. In Metrolog, the defect of an evaluated feature is split into four independent types — form, size, position and orientation — alongside the global defect, so that the dominant type, and therefore the first correction to make, becomes visible. A good report, the company says, reduces scrap and speeds corrective action.
The four steps are the vendor's own recommendations, and the benefits it describes are stated expectations rather than independently measured outcomes.