Shining 3D Inspect for CAD Comparison and GD&T

When a scanner produces a clean mesh, the quality decision has only started. A color map can look convincing while the wrong alignment, tolerance band, or datum setup hides the condition that matters. Shining 3D Inspect is designed for the work between captured geometry and an inspection record: comparison, measurement, interpretation, and reporting.

This guide focuses on manufacturing inspection in the United States. It explains what the software can support, where engineering judgment remains essential, and how to avoid turning an attractive visualization into an unsupported acceptance decision.

What problem does Inspect solve?

Inspect organizes the inspection work that follows 3D capture: importing measured and nominal geometry, aligning them, mapping full-field deviation, evaluating dimensions and GD&T, and producing reports. It gives a quality team one environment for analysis, but it does not define the product requirement or validate the measurement process.

The official official Inspect product overview lists full-field scan-to-CAD comparison, 3D color maps, 2D cross-sectional analysis, GD&T evaluation under ISO or ASME settings, application-oriented modules, and customizable reporting. The Inspect documentation also describes feature extraction, recalculation, scripting, and report customization.

That scope is different from reverse-engineering software. Reverse engineering reconstructs design geometry from measured data. Inspection software asks whether measured geometry conforms to an existing requirement. Teams that need both paths should keep the inspection result and the reconstructed CAD model as separate controlled deliverables.

What should be locked before scan-to-CAD comparison begins?

Lock the drawing or model revision, units, coordinate system, datum strategy, inspection characteristics, tolerance rules, scan preparation method, and acceptance authority before opening the comparison. If these controls change after results are visible, the analysis can become outcome-driven instead of requirement-driven, and repeated reports may no longer be comparable.

• Nominal definition: identify the released CAD model, drawing, model-based definition, and revision.
• Measured data: preserve the raw scan, processed mesh, units, scanner settings, and any smoothing or hole filling.
• Alignment rule: state whether the result uses a datum-based, feature-based, coordinate-system, or best-fit alignment.
• Acceptance characteristics: list the dimensions, profiles, GD&T controls, and surface regions that drive the decision.
• Reporting controls: define the report template, reviewer, retention period, and approval route.

How should scan data be aligned to CAD?

Use the alignment that represents the drawing requirement and the way the part functions. A global best fit can reduce average deviation while moving critical datums or interfaces away from their required relationship. Record the alignment sequence, constrained degrees of freedom, selected features, exclusions, and any manual adjustments in the inspection record.

The manufacturer documents multiple alignment methods for different inspection scenarios. The method is not a cosmetic setup choice. It establishes the coordinate relationship used by every downstream color map, cross section, dimension, and GD&T result.

For a machined part, a datum-based alignment may be appropriate when the engineering definition controls the part through datum features. A best-fit alignment may be useful for process development or freeform surface comparison, but it should not be substituted for the required datum reference frame. If the inspection objective changes, save a separate analysis rather than silently overwriting the approved setup.

What can a 3D color map prove?

A color map can show where measured surfaces sit above or below nominal geometry within a chosen scale. It is useful for locating warpage, springback, machining stock, profile variation, and regional patterns. It does not by itself prove conformance because alignment, filtering, coverage, uncertainty, and tolerance interpretation still govern the result.

Use a stable color scale when comparing parts over time. Auto-scaling each report can make two materially different conditions look similar. Show the tolerance limits, preserve neutral bands, identify excluded or unmeasured regions, and add section views where a surface map cannot explain local form.

The software's dent and sheet-metal modules can help focus specific analyses, but the organization still needs a qualified method. That includes defining the minimum reportable feature, scan coverage rules, surface preparation limits, and how an operator handles marginal results.

How should GD&T be evaluated in the software?

Start with the standard and revision named by the product definition, then build the datum reference frame before evaluating controlled features. Inspect can calculate GD&T under ASME or ISO settings, but the software cannot decide which interpretation the contract requires or whether the extracted feature represents the functional surface.

ASME Y14.5 establishes the symbols, rules, definitions, requirements, defaults, and practices used to state and interpret GD&T. The current official ASME page identifies Y14.5-2018 as reaffirmed in 2024. A customer drawing may invoke another edition, so the inspection setup should follow the contractually applicable revision rather than the newest available setting by assumption.

The official GD&T Check documentation notes that switching between ASME and ISO changes the calculation method and recalculates results. That behavior is a reason to control the standard selection in the inspection template and to require reviewer approval for changes.

What makes a 3D inspection report defensible?

A defensible report connects each result to the correct part, nominal revision, measured dataset, alignment, standard, tolerance, software version, measurement-system status, and reviewer. It shows what was measured, what was not measured, and which rule produced the conclusion. The PDF is evidence of the process; it is not the process itself.

At minimum, retain:

• part number, serial or lot identifier, and inspection date;
• nominal file name, revision, and unit system;
• scanner, calibration status, software version, and operator;
• raw scan and processed dataset identifiers;
• alignment method, datum construction, filters, and excluded regions;
• color scale, tolerance bands, dimensions, GD&T results, and disposition;
• reviewer approval and any deviation authorization.

NIST's metrological traceability guidance explains that traceability is a property of a measurement result, supported by a documented unbroken chain of calibrations with each link contributing to measurement uncertainty. Merely using calibrated equipment or producing a software report is not enough. The provider of the result is responsible for supporting the traceability claim.

Where does automation help, and where should it stop?

Automation is valuable when the part family, fixture, datum logic, feature extraction, tolerances, and report template are stable. Validate the routine against representative good, bad, and borderline parts before release. Stop automatic disposition when alignment confidence falls, coverage is incomplete, a critical feature fails extraction, or results approach the decision limit.

The documentation covers recalculation when a measured model is replaced and scripting tools for automated measurement workflows. Treat each automated routine as controlled inspection software: assign an owner, version it, test changes, preserve a known dataset, and require review after software updates or process changes.

A practical rollout begins with one recurring part family. Compare automated results with an approved manual method, document differences, and define exception handling. Expansion should follow demonstrated repeatability, not the visual speed of the first report.

What should procurement ask before selecting Inspect?

Procurement should evaluate the complete workflow, not only the license price. Confirm supported scan and CAD formats, workstation requirements, alignment and GD&T needs, report templates, automation scope, training, maintenance, data retention, and the acceptance method for representative parts. Include the quality owner and daily operator in the evaluation before purchase.

The live Inspect Software product page lists current U.S. configurations and pricing. Teams still choosing capture hardware can review the industrial 3D scanning inspection workflow and the industrial scanner portfolio. For a concrete hardware-side example, see the FreeScan Combo machined-part inspection workflow.