{"id":2878,"date":"2026-09-19T08:00:00","date_gmt":"2026-09-19T08:00:00","guid":{"rendered":"https:\/\/swesd.com\/?p=2878"},"modified":"2026-09-19T08:00:00","modified_gmt":"2026-09-19T08:00:00","slug":"ic-tray-incoming-inspection","status":"publish","type":"post","link":"https:\/\/swesd.com\/de\/blog\/ic-tray-incoming-inspection\/","title":{"rendered":"IC Tray Sampling Plan for Incoming Quality Inspection"},"content":{"rendered":"

IC Tray Sampling Plan for Incoming Quality Inspection is a purchasing and validation problem: the aim is to build a receiving sampling plan that detects wrong revision, damaged pockets, warpage and missing evidence before trays reach production. A reliable decision starts with the protected device and its complete route, then converts the search term into measurable drawing, sample and receiving requirements. There is no universal material, tolerance, reuse count or test value that safely fits every program.<\/p>\n

Decision Summary for ic tray inspection<\/h2>\n
\n\n\n\n\n\n\n\n\n
Decision area<\/th>\nDefine before quotation<\/th>\nEvidence to request<\/th>\n<\/tr>\n<\/thead>\n
Identity gate<\/td>\nPart number, revision, supplier and lot<\/td>\nMatch purchase and approved sample<\/td>\n<\/tr>\n
Visual gate<\/td>\nCracks, flash, contamination and labels<\/td>\nUse defect definitions and lighting<\/td>\n<\/tr>\n
Dimensional gate<\/td>\nCritical pockets, datums and stack features<\/td>\nUse controlled gauges and sampling<\/td>\n<\/tr>\n
Functional gate<\/td>\nFit, stack and equipment interface<\/td>\nTest representative worst-case units<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

Use the table as an RFQ discussion guide, not as a substitute for controlled values. Final limits should come from current device drawings, equipment interfaces, the facility ESD program, supplier documentation and qualified trials. When a number is not yet known, state the functional risk and agree a prototype test instead of copying a limit from an unrelated tray.<\/p>\n

\"ic
BGA matrix IC tray from the SWESD IC tray product page<\/figcaption><\/figure>\n

1. Identity gate: Turn the Requirement into Evidence<\/h2>\n

For ic tray inspection, the buyer must define part number, revision, supplier and lot<\/strong>. This point controls whether the tray can build a receiving sampling plan that detects wrong revision, damaged pockets, warpage and missing evidence before trays reach production. Write the requirement against the actual device, route and equipment rather than a generic tray description. Name the responsible drawing or work instruction, the condition in which the characteristic applies, and who approves an exception.<\/p>\n

The practical verification is to match purchase and approved sample<\/strong>. Begin with identified samples from the proposed production material and tooling. Record sample quantity, lot or cavity, conditioning, equipment, method and result. Include both normal and credible worst-case conditions. A pass on one convenient sample is useful for development, but it is not evidence that production variation is controlled.<\/p>\n

Ask the supplier to explain which input variables can change this result. Depending on the characteristic, these may include resin or sheet lot, additive level, molding or forming settings, cooling, trimming, storage, cleaning and previous use. Convert important variables into incoming evidence, periodic checks or formal change notification. This makes the requirement auditable and prevents a catalog promise from becoming the only acceptance basis.<\/p>\n

2. Visual gate: Turn the Requirement into Evidence<\/h2>\n

For ic tray inspection, the buyer must define cracks, flash, contamination and labels<\/strong>. This point controls whether the tray can build a receiving sampling plan that detects wrong revision, damaged pockets, warpage and missing evidence before trays reach production. Write the requirement against the actual device, route and equipment rather than a generic tray description. Name the responsible drawing or work instruction, the condition in which the characteristic applies, and who approves an exception.<\/p>\n

The practical verification is to use defect definitions and lighting<\/strong>. Begin with identified samples from the proposed production material and tooling. Record sample quantity, lot or cavity, conditioning, equipment, method and result. Include both normal and credible worst-case conditions. A pass on one convenient sample is useful for development, but it is not evidence that production variation is controlled.<\/p>\n

Ask the supplier to explain which input variables can change this result. Depending on the characteristic, these may include resin or sheet lot, additive level, molding or forming settings, cooling, trimming, storage, cleaning and previous use. Convert important variables into incoming evidence, periodic checks or formal change notification. This makes the requirement auditable and prevents a catalog promise from becoming the only acceptance basis.<\/p>\n

\"ic
Alternative matrix layout on a real SWESD IC tray<\/figcaption><\/figure>\n

3. Dimensional gate: Turn the Requirement into Evidence<\/h2>\n

For ic tray inspection, the buyer must define critical pockets, datums and stack features<\/strong>. This point controls whether the tray can build a receiving sampling plan that detects wrong revision, damaged pockets, warpage and missing evidence before trays reach production. Write the requirement against the actual device, route and equipment rather than a generic tray description. Name the responsible drawing or work instruction, the condition in which the characteristic applies, and who approves an exception.<\/p>\n

The practical verification is to use controlled gauges and sampling<\/strong>. Begin with identified samples from the proposed production material and tooling. Record sample quantity, lot or cavity, conditioning, equipment, method and result. Include both normal and credible worst-case conditions. A pass on one convenient sample is useful for development, but it is not evidence that production variation is controlled.<\/p>\n

Ask the supplier to explain which input variables can change this result. Depending on the characteristic, these may include resin or sheet lot, additive level, molding or forming settings, cooling, trimming, storage, cleaning and previous use. Convert important variables into incoming evidence, periodic checks or formal change notification. This makes the requirement auditable and prevents a catalog promise from becoming the only acceptance basis.<\/p>\n

4. Functional gate: Turn the Requirement into Evidence<\/h2>\n

For ic tray inspection, the buyer must define fit, stack and equipment interface<\/strong>. This point controls whether the tray can build a receiving sampling plan that detects wrong revision, damaged pockets, warpage and missing evidence before trays reach production. Write the requirement against the actual device, route and equipment rather than a generic tray description. Name the responsible drawing or work instruction, the condition in which the characteristic applies, and who approves an exception.<\/p>\n

The practical verification is to test representative worst-case units<\/strong>. Begin with identified samples from the proposed production material and tooling. Record sample quantity, lot or cavity, conditioning, equipment, method and result. Include both normal and credible worst-case conditions. A pass on one convenient sample is useful for development, but it is not evidence that production variation is controlled.<\/p>\n

Ask the supplier to explain which input variables can change this result. Depending on the characteristic, these may include resin or sheet lot, additive level, molding or forming settings, cooling, trimming, storage, cleaning and previous use. Convert important variables into incoming evidence, periodic checks or formal change notification. This makes the requirement auditable and prevents a catalog promise from becoming the only acceptance basis.<\/p>\n

Prototype and Production Approval<\/h2>\n

Approve the proposal in gates. First review the device revision, orientation, allowed contact, route, equipment and packaging stack. Next inspect identified first articles and verify the four decision areas above. Then load representative minimum and maximum devices, build the real stack, apply covers or restraints, and run the normal handling sequence. Include cleaning, heat, labels, storage and shipment only where they belong to the actual route.<\/p>\n

Keep the approved drawing, material or construction identity, sample lot, photographs, raw results, deviations and sign-off together. Receiving inspection should check identity before sampling, separate lots, inspect critical features with the approved datum and method, and quarantine failures before they mix with accepted inventory. Sampling depth follows risk and supplier history; it should not be invented in a blog or purchase note.<\/p>\n

\"ic
Fine-pitch QFN matrix tray from the SWESD product range<\/figcaption><\/figure>\n

Failures That the Control Plan Must Prevent<\/h2>\n

Failure 1: Sampling before separating lots<\/h3>\n

This shortcut can release trays that look acceptable but fail during handling. Contain the affected lot, identify where the assumption entered the specification, and compare the tray with the controlled device and process requirements. Repeat the relevant dimensional, functional or electrical check under documented conditions. Record the disposition so the same issue can be recognized at receiving and during reuse.<\/p>\n

Failure 2: Recording only pass or fail without defect location<\/h3>\n

This shortcut can release trays that look acceptable but fail during handling. Contain the affected lot, identify where the assumption entered the specification, and compare the tray with the controlled device and process requirements. Repeat the relevant dimensional, functional or electrical check under documented conditions. Record the disposition so the same issue can be recognized at receiving and during reuse.<\/p>\n

Failure 3: Releasing a lot while required test evidence is missing<\/h3>\n

This shortcut can release trays that look acceptable but fail during handling. Contain the affected lot, identify where the assumption entered the specification, and compare the tray with the controlled device and process requirements. Repeat the relevant dimensional, functional or electrical check under documented conditions. Record the disposition so the same issue can be recognized at receiving and during reuse.<\/p>\n

RFQ and Supplier Checklist<\/h2>\n