How to Set Sampling and Acceptance Requirements for CNC Machined Parts

For a CNC machining order, begin the acceptance discussion with the parts, requirements and production context covered by the RFQ. The proposed checklists below are editorial suggestions, conditional on the drawing, contract and application. NIST describes acceptance sampling as a decision about an immediate lot based on a randomly selected sample; its main purpose is acceptance or rejection, rather than estimating the lot’s quality. That gives the purchasing discussion a concrete question: which agreed rule will decide the disposition of the submitted lot? NIST: acceptance sampling

Work through the scope, characteristics, lot boundaries and decision rules together. Keep proposed contractual requirements separate from the technical concepts supported by the cited sources.

Which manufacturing process and production stage are being accepted?

For this RFQ, identify CNC machining as the process and state whether the proposed acceptance covers a prototype, pilot lot or recurring production. As an editorial suggestion, agree the relevant drawing, material description and inspection coverage for that order; the production-stage label alone is not the proposed release rule.

State CNC machining as the process covered by the acceptance proposal. If the enquiry also includes stamping, sheet metal fabrication or injection molding, identify those items separately. State which items belong to this CNC machining enquiry and which need a separate scope discussion.

For the CNC machining items, identify whether the order concerns a prototype, a pilot lot or recurring production. These labels describe the purchasing context. As an editorial suggestion, follow each label with the proposed inspection coverage, approval responsibility and release condition. A prototype enquiry can therefore state its requested checks explicitly, while a recurring order can state the proposed rules for submitted lots. Mark requested coverage as a proposal and identify any coverage already required by the governing documents.

A useful scope sheet can list the part identifier, drawing revision, material grade, temper or condition, finish, quantity and intended application. Where a document specifies a standard edition or regional requirement, record that reference as stated. Treat an omitted edition, material condition or requirement as an open RFQ question rather than supplying an assumed value.

NIST distinguishes the immediate lot decision made by acceptance sampling from longer-term quality control. That distinction supports identifying which activity the proposed evidence addresses. NIST: acceptance sampling

For quotation review, request confirmation of the named scope and any proposed exclusions. Keep acceptance of the prototype, pilot lot or recurring submission tied to the rule agreed for that particular order.

Which characteristics determine whether a part is acceptable?

As an editorial suggestion, list the relevant drawing characteristics and their stated acceptance requirements, then classify their importance for the application. Agree which characteristics require verification of every part and which enter lot sampling. A risk label should express the buyer’s intended coverage, with the drawing and contract supplying the applicable requirements.

Build the proposed acceptance schedule around identified drawing characteristics. For each entry, record the feature or characteristic identifier, the governing drawing revision, the stated requirement and the proposed evidence. Where a limit or condition is missing, flag the question for agreement rather than inventing a tolerance or a verification rule.

An editorial classification can distinguish characteristics associated with safety, fit, function or appearance. Use those categories only where they describe the application and reflect the governing requirements. The buyer can propose more extensive verification for a designated high-risk characteristic, but the classification itself is not an externally established rule requiring inspection of every part.

Where the drawing or contract specifies size, position, roughness, material, burr condition, threads or functional fit, give each relevant requirement its own entry in the proposed schedule. For each entry, the RFQ can request a method proposal and the corresponding result format. Keep requirements that are still under discussion visibly open.

For characteristics assigned to lot sampling, define the counting basis used by the selected plan. NIST’s attributes discussion concerns counting defectives in a sample and applying decision rules to the lot. NIST: sampling-plan types

For any proposed every-part verification, name the characteristic and requested record separately. During quotation review, seek agreement on both the requirement and its coverage, so that a general phrase such as “critical features” is replaced by an identifiable list for this application.

What counts as one inspection lot?

Agree which parts are submitted together for one lot decision and record their quantity. As an editorial suggestion, set boundaries around sufficiently similar drawing revision, declared material, setup, program and production conditions where relevant to the contract and application. NIST supports random sampling from a lot, but does not establish those CNC grouping rules. NIST: acceptance sampling

NIST describes selecting a sample at random from a lot and using the sample information to decide the lot’s disposition, generally acceptance or rejection. The source establishes the relationship between the sampled lot and the decision. It does not prescribe CNC lot membership by material batch, setup or program revision. NIST: acceptance sampling

For this RFQ, a proposed lot schedule can state the submitted part identifiers, quantity and grouping conditions. Drawing revision, declared material, setup identifier, program revision and production window are editorial suggestions for that schedule where relevant to the drawing, contract and application. Agree which differences require separate submissions; do not treat every listed field as an automatic new-lot trigger.

Conditional scenario 1 — two drawing revisions: If an order includes parts to two drawing revisions, the buyer can propose a separate submitted lot for each revision. Under that agreement, each submission would have its own identified membership, quantity and selected sampling rule. This is a possible contractual arrangement, not a claim that NIST mandates revision-based lot splitting.

Lot quantity also appears in NIST’s historical sampling-plan selection example, where inspection level determines the relationship between lot size and sample size. That example is not evidence for a current standard edition. NIST: choosing a sampling plan

As a recordkeeping suggestion, use the agreed lot identifier on the sampling record and shipment schedule if the contract requests that linkage. Review the proposed grouping and identifiers before applying the plan to the submitted quantity.

Which sampling plan applies to each defect class?

For each agreed defect class, identify the counting basis, selected sampling scheme and decision criteria. Record the applicable lot size, inspection level, plan type and inspection state when the chosen scheme uses them. Separately list any every-part verification required by the drawing or contract, or agreed for the application.

NIST defines a lot acceptance sampling plan as a sampling scheme plus decision rules. For a single attributes plan denoted (n, c), n is the sample size and the lot is rejected when the sample contains more than c defectives. A double plan can accept, reject or leave the first sample undecided; if the selected plan calls for a second sample after an undecided result, combine both sample counts for its final decision. NIST: sampling-plan types

These structures and the tradeoff between sampling effort and complexity are described by NIST. The table’s procurement questions are suggestions. NIST: sampling-plan types

NIST’s historical MIL Standard 105D example uses AQL, inspection level, lot size, a sample-size code and plan type. It also describes normal, tightened and reduced plans with switching rules. If the contract selects such a scheme, record its applicable inspection state and governing switching rules. This source does not verify the provisions of a current contractual edition. NIST: choosing a sampling plan

When must a setup pass first-article inspection?

If the drawing, contract or application requires first-article inspection, use its agreed trigger and release condition. As an editorial checklist, identify the setup covered, characteristics to be inspected, report scope, approval responsibility and point at which routine production may begin. The release proposal must be agreed for the order.

For an order that calls for first-article inspection, start with the provision governing when it applies. The following release fields are editorial suggestions, conditional on the drawing, contract and application: the identified setup, inspection scope, report contents, approving party and permission to begin routine production. They are not obligations established by the captured sampling pages.

Describe the proposed trigger in the agreement. An initial setup, a program revision, a tool change or a specified interruption can be listed if the parties intend it to trigger renewed review. Do not present those examples as automatic triggers. State which output is covered by the requested review and how approval will be communicated under the proposed contract.

Keep a capability request explicit. NIST describes process capability analysis as comparing a process with its specifications and illustrates the comparison with Cp and Cpk indices. If capability evidence is also requested, describe the study separately instead of accepting a first-article sign-off as the requested capability submission. This separation is a procurement recommendation based on the different evidence being requested. NIST: process capability

The RFQ can request proposed approval dates and dependencies without asserting a universal effect on cost or delivery.

How will each critical feature be measured?

For each acceptance-critical characteristic, request a proposed measurement method, relevant conditions and reporting format for review against the drawing, contract and application. As an editorial suggestion, record the evaluated feature and any applicable datum or alignment information. A named instrument or software package is a proposal, not established suitability for this order.

For each designated acceptance-critical characteristic, request a method proposal that identifies the requirement being evaluated. Suggested review fields include the feature identifier, proposed instrument or procedure, applicable part condition, relevant datum or alignment information and reporting format. These are editorial fields for agreement; they do not validate a particular tool for a tolerance.

Hexagon’s PC-DMIS 2020.1 documentation gives a narrow example under its Legacy Dimension Position option. That option calculates position from a feature to the X, Y or Z origin parallel to the respective axis, with the feature’s diameter, angle and vector also contributing to the calculation. Hexagon: Dimensioning Position

For that option, when datums are used, measured and deviation XYZ values are calculated relative to the datum alignment but displayed in the current alignment. The documentation states that dimensions with the same nominal values can report different measured and deviation values when different datums, or no datums, are defined. This is a software-specific example, not a general GD&T standard or an equipment claim about the supplier. Hexagon: Dimensioning Position

NIST characterizes measurement goodness through bias, short-term variability, long-term variability and uncertainty, primarily for ongoing measurement processes. NIST: measurement characterization

Where relevant to the application, request evidence addressing those issues alongside the method proposal. Agree whether the record calls for actual values, a categorical outcome or both; do not assume a reporting format establishes method suitability.

When is process capability evidence needed?

Request capability evidence when it is required by the governing documents or agreed for a tight or high-risk characteristic in the application. Define the characteristic, study context, data expectations and decision threshold. NIST describes capability analysis as a comparison between process performance and specification limits; it does not set this order’s procurement requirement. NIST: process capability

The procurement decision is whether the application calls for capability evidence for a named characteristic. A tight tolerance or high functional risk can be a reason to propose a study, but this article does not turn either description into a universal requirement. State any requirement already present in the drawing or contract, and distinguish it from additional evidence proposed for agreement.

NIST describes process capability analysis as comparing process performance with specification limits. Its overview illustrates a capability chart and describes Cp and Cpk. The page explains that Cp alone does not account for an off-center process, while Cpk incorporates distance from the process mean to the specification limits. NIST: process capability

As an editorial study checklist, identify the characteristic, specification limits, process context, data collection scope, index or other agreed analysis, and acceptance threshold. Request the basis for treating the process as in control and for the analysis assumptions. The parties should agree on the selected analysis and its assumptions for the order; the cited NIST overview does not set a universal acceptance threshold. NIST: process capability

Measurement review is a separate proposed item. NIST’s measurement-characterization page addresses bias, variability and uncertainty, primarily in ongoing processes. It does not establish an instrument’s suitability for this part. NIST: measurement characterization

Name the characteristics covered by the requested study and agree how its results enter the purchasing decision. Keep the lot-sampling rule and any every-part verification requirements separately identified in the contract.

What happens when a sample fails?

Apply the selected plan’s decision rule before choosing the lot response. For a single (n, c) attributes plan, NIST describes rejection when defectives exceed c. As an editorial suggestion, agree any hold, further inspection, segregation, replacement or disposition path and approval responsibility before shipment, conditional on the contract and application. NIST: sampling-plan types

Record the observed result and apply the selected decision rule. Under NIST’s single (n, c) attributes description, more than c defectives leads to lot rejection. A double plan can instead produce an undecided first-sample result; if the selected plan calls for a second sample, combine both sample counts for its final decision. Keep those outcomes distinct in the proposed inspection record. NIST: sampling-plan types

Teaching scenario — an undecided first sample: Suppose the selected double-sampling plan permits a second sample after an undecided first result. The inspector records both sample counts and applies that plan's combined acceptance rule. The example sets no universal sample size or acceptance number.

Before shipment, agree the handling path that the contract permits after rejection. An editorial checklist can cover the responsible reviewer, any lot hold, segregation arrangements, further inspection, proposed replacement or other disposition, and the authority to approve a subsequent submission. Each item is conditional on the drawing, contract and application. No universal hold or reinspection obligation follows from the source’s general plan description.

NIST describes a common rectification procedure where testing is non-destructive: rejected lots receive inspection of every unit and defectives are replaced with good units. Its average outgoing quality discussion concerns that combined sampling-and-rectification procedure. This supports describing the option, not requiring it for every CNC order. NIST: sampling-plan types

If that option is proposed, agree its applicability and the evidence requested after rectification. If another path is selected, state that path explicitly. As a recordkeeping suggestion, retain the original sampling result alongside the agreed disposition and any later review. Where further sampling is permitted, identify the applicable rule rather than improvising an additional sample as a route to acceptance.

What must the RFQ and inspection record contain?

As an editorial RFQ checklist, provide the governing documents, production context, proposed lot boundaries, characteristic coverage and acceptance evidence. Include first-article, capability and failed-lot provisions where required or agreed. Propose record identifiers and approval fields that match the contract; these are order-specific requests rather than universal documentation rules.

Use the RFQ to propose the acceptance package for the actual order. The checklist below is an editorial suggestion, conditional on the drawing, contract and application. Record unresolved items as questions for agreement rather than describing the package as complete while requirements remain unspecified.

Suggested RFQ checklist:

• Part identifiers, drawing revision, material grade and temper or condition, finish, quantity, application, and any specified standard edition or regional requirement.
• CNC machining scope, prototype, pilot or recurring-production context, and proposed lot membership, quantity and identifiers.
• Relevant characteristic requirements, proposed functional-risk classifications, every-part verification and lot-sampling coverage.
• Selected sampling scheme, counting basis, decision criteria, and applicable inspection level, plan type, inspection state and switching rules.
• Proposed measurement methods, relevant conditions and reports, plus any agreed first-article scope, release responsibility or capability study.
• Failed-lot handling, further inspection, segregation, disposition and approval provisions, with requested submission dates and quotation scope.

For schemes that use them, NIST’s historical selection example relates lot size and inspection level to a sample-size code, then plan type to the selected plan. It also includes inspection states and switching rules; the page does not verify a current contractual edition. NIST: choosing a sampling plan

A proposed inspection record can carry the applicable document revision, characteristic identifiers, lot identifier, sampling rule, observed results, lot decision and agreed approvals or disposition. Where shipment linkage is requested, identify the relevant shipment reference explicitly. Ask the supplier to confirm the proposed records, activities, prices and dates. Leave equipment, certification and performance statements subject to separate evidence review.

Please send the complete RFQ information: drawing and revision, material grade and condition, finish, quantity, production context, application, applicable contractual requirements, and the proposed inspection and acceptance package. Can you also provide the lot boundaries, characteristic coverage, sampling rules, measurement proposals and any required first-article, capability or failed-lot provisions so the quotation can address the full agreed scope?