Glossary

Structured-light scanning

Structured-light scanning is a non-contact optical method for capturing 3D surface geometry with projected light patterns.

AS9102 First Article Inspection and Net-Inspect Inspection and Sampling (AQL)

Structured-light scanning is a non-contact optical measurement method that captures three-dimensional surface geometry by projecting known light patterns onto a part and recording how those patterns deform across the surface. Software uses the camera images to calculate a 3D point cloud or mesh that represents the measured shape.

In manufacturing and quality contexts, structured-light scanning is commonly used for dimensional inspection, reverse engineering, tool and die verification, and first article inspection support for complex surfaces. The scan data may be compared to a CAD model, drawing requirements, or selected inspection characteristics when the measurement process, alignment method, and reporting workflow are defined.

Structured-light scanning should not be confused with barcode scanning or document scanning. It is also different from contact CMM inspection: a CMM measures discrete points with a probe, while structured-light scanning captures many surface points optically. Structured-light systems can be useful for freeform or accessible external geometry, but they may be limited by line of sight, surface finish, transparency, reflectivity, feature access, and tolerance requirements.

FAIRs should usually be linked to the part revision, manufacturing context, and the specific lot or serial population they support, not treated as a universal attachment on every serial number. In aerospace ERP or MES, the practical goal is traceable association with effectivity, process changes, and as-built history. The exact model depends on system integration, revision discipline, and validation of the evidence trail.

How detailed do material and special process entries need to be on Form 2?

They need to be detailed enough to unambiguously trace what was actually used and to support review against the drawing, specification, and purchase or processing records. In practice, that usually means exact material and process identifiers, revision status where applicable, and supplier or source linkage. More detail than needed can add noise, but vague entries create traceability and validation risk.

Do OEM-specific quality clauses override the standard AS9102 triggers?

Usually, no. OEM-specific quality clauses generally add to, clarify, or tighten AS9102 expectations rather than erase the baseline triggers. In practice, you must review the contract, drawing notes, PO clauses, and flowed-down customer requirements together, because conflicts, exceptions, and approval paths are often site- and program-specific.

Can FAI requirements be triggered automatically from ERP or MES?

Yes, FAI (e.g., AS9102) requirements can be triggered automatically from ERP or MES, but only when business rules, master data, and integrations are well defined and validated. In most brownfield plants this requires careful mapping of part/rev status, routing changes, and supplier data, plus change control, testing, and clear ownership of FAI logic.

Related Glossary