Buyers should build a CTQ feature map by assigning every function-critical requirement to a unique feature ID and classifying its consequence as fit, seal, load, motion or appearance. Each row then names the requirement owner, manufacturing state, datum relationship, evidence method and change impact. The map becomes the common index for the model, drawing, process review, operation plan and acceptance records.
A CTQ map is not a copy of every drawing dimension. It captures requirements whose variation can change assembly or use, plus the upstream features that create or protect them. One feature may carry more than one consequence: a mounting face can control fit and load, while a bored axis can control motion and seal alignment. Separate rows keep each acceptance question explicit.
Fit CTQs govern whether mating parts locate, clear or fasten correctly. Seal CTQs govern a defined fluid or gas boundary, including related faces, ports and remaining walls. Load CTQs protect sections, interfaces and orientations that transmit force. Motion CTQs govern axes, guides, bearing seats or clearances that affect movement. Appearance CTQs apply only to identified visible zones and named surface conditions.
Write the functional consequence in plain engineering language before entering a tolerance. “Locates jaw rail relative to drive axis” is more useful than “critical dimension.” It tells the engineering team which relationship must survive process selection, fixture changes and inspection alignment. It also exposes duplicate controls that protect the same outcome without adding information.
CTQ Map Field | Required Entry | Example Decision | Why It Matters |
|---|---|---|---|
Category and consequence | Fit, seal, load, motion or appearance plus the failure effect | Motion: guide misalignment can create binding | Prevents “critical” labels without a functional reason |
Feature ID and requirement | Unique model/drawing identity and controlled relationship | M03: guide axis orientation to datum A | Keeps reviews and records tied to the same geometry |
Requirement owner | Buyer design, supplier casting, machining, finish, assembly or shared | Buyer owns function; machining owner proposes operation control | Stops assumptions from falling between organizations |
Manufacturing state | Raw casting, intermediate, machined, finished or assembled state | Seal land accepted after machining and final cleaning | Identifies when evidence becomes valid |
Datum relationship | Released frame or documented manufacturing reference that governs the feature | Bore axis evaluated from finished mounting plane and locator | Prevents coordinate systems from drifting between stages |
Evidence method | Dimensional, gauge, material, visual, leak or functional result as applicable | Guide gauge correlated to datum-based measurement | Links acceptance to the actual consequence |
Change impact | Tool, core, fixture, program, finish or test changes that reopen the row | Fixture locator revision requires M03 alignment review | Prevents stale evidence from approving a changed route |
Ownership has two layers. The buyer normally owns the functional requirement and approval authority. The supplier identifies which operation creates the feature and which team controls it. On a custom precision casting, casting may own the raw preform and wall envelope while machining owns the finished bore; quality owns neither design intent nor process creation, but it administers the agreed acceptance method.
The state field prevents one report from answering the wrong question. Raw measurements can confirm stock or core relationship. Intermediate results can confirm a transferred setup. Final dimensional or functional evidence answers delivered-part acceptance. If cleaning, coating, inserts or assembly can change the CTQ, specify whether evidence is collected before or after that operation.
Choose an evidence method only after the feature, state and reference are known. A coordinate report may fit a complex position; a functional gauge may fit a combined boundary; a leak result may fit the completed seal. The map should record what each method proves and what separate evidence remains necessary.
If a robotic gripper body carries two sliding jaws, a pneumatic passage, a mounting interface and a visible front face, the map separates their consequences. Guide axes and rail spacing are motion CTQs. The robot mounting pattern is a fit CTQ and may also carry load. Passage walls and plug interfaces belong to the seal boundary. The bridge between guides carries a load requirement, while only the defined front zone receives appearance acceptance.
The motion rows link finished guide geometry to the functional datum frame and to a correlated slide check. The seal rows identify the final tested configuration. The load row links minimum section and orientation to the approved design evidence. The appearance row names its viewing zone so a cosmetic rule does not spread to hidden internal geometry.
If the machining fixture changes, the map reopens guide-axis and mounting-pattern rows because both depend on localization. A finish-color change reopens the appearance row but not automatically the motion rows. A passage-core change reopens seal and remaining-wall rows. This targeted logic keeps revalidation proportional to technical impact.
Procurement should include the CTQ map revision with the RFQ and require suppliers to return assumptions, capability exceptions, proposed manufacturing owners and evidence scope against the same IDs. Engineering resolves missing consequences and datum relationships. Quality confirms that methods and records can identify each row. Commercial comparison then uses a common technical scope rather than quotations based on different interpretations.
After award, preserve the map as a living index rather than duplicating it in disconnected spreadsheets. Drawing or model changes update affected feature IDs; process changes identify reopened rows; approved evidence closes them. The release decision is simple: every CTQ has a consequence, accountable owner, defined state, governing relationship, suitable evidence and explicit change trigger.