{"id":2860,"date":"2026-09-16T08:00:00","date_gmt":"2026-09-16T08:00:00","guid":{"rendered":"https:\/\/swesd.com\/?p=2860"},"modified":"2026-09-16T08:00:00","modified_gmt":"2026-09-16T08:00:00","slug":"jedec-tray-reuse-program","status":"publish","type":"post","link":"https:\/\/swesd.com\/nl\/blog\/jedec-tray-reuse-program\/","title":{"rendered":"JEDEC Tray Reuse: Inspection, Cycle Limits and Cost Control"},"content":{"rendered":"

JEDEC Tray Reuse: Inspection, Cycle Limits and Cost Control is a purchasing and validation problem: the aim is to manage repeated tray cycles with identification, inspection, cleaning and retirement rules rather than informal visual reuse. 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 jedec tray reuse<\/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
Cycle identity<\/td>\nTray family, lot and reuse count<\/td>\nUse a durable record that survives cleaning<\/td>\n<\/tr>\n
Inspection gate<\/td>\nDamage, warpage, pocket wear and labels<\/td>\nDefine accept, repair and scrap conditions<\/td>\n<\/tr>\n
Performance checks<\/td>\nFit, stack, cleanliness and electrical function<\/td>\nSet risk-based intervals<\/td>\n<\/tr>\n
Economics<\/td>\nReturn rate, loss, cleaning and replacement<\/td>\nMeasure total cycle cost<\/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

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

1. Cycle identity: Turn the Requirement into Evidence<\/h2>\n

For jedec tray reuse, the buyer must define tray family, lot and reuse count<\/strong>. This point controls whether the tray can manage repeated tray cycles with identification, inspection, cleaning and retirement rules rather than informal visual reuse. 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 a durable record that survives cleaning<\/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. Inspection gate: Turn the Requirement into Evidence<\/h2>\n

For jedec tray reuse, the buyer must define damage, warpage, pocket wear and labels<\/strong>. This point controls whether the tray can manage repeated tray cycles with identification, inspection, cleaning and retirement rules rather than informal visual reuse. 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 define accept, repair and scrap conditions<\/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

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

3. Performance checks: Turn the Requirement into Evidence<\/h2>\n

For jedec tray reuse, the buyer must define fit, stack, cleanliness and electrical function<\/strong>. This point controls whether the tray can manage repeated tray cycles with identification, inspection, cleaning and retirement rules rather than informal visual reuse. 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 set risk-based intervals<\/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. Economics: Turn the Requirement into Evidence<\/h2>\n

For jedec tray reuse, the buyer must define return rate, loss, cleaning and replacement<\/strong>. This point controls whether the tray can manage repeated tray cycles with identification, inspection, cleaning and retirement rules rather than informal visual reuse. 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 measure total cycle cost<\/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

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

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

Failure 1: Counting reuse only when a tray returns from a customer<\/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: Mixing approved and unknown-history trays<\/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: Setting an arbitrary cycle limit without condition data<\/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