{"id":2850,"date":"2026-09-14T14:00:00","date_gmt":"2026-09-14T14:00:00","guid":{"rendered":"https:\/\/swesd.com\/?p=2850"},"modified":"2026-09-14T14:00:00","modified_gmt":"2026-09-14T14:00:00","slug":"jedec-tray-drawing-tolerances","status":"publish","type":"post","link":"https:\/\/swesd.com\/ko\/blog\/jedec-tray-drawing-tolerances\/","title":{"rendered":"JEDEC Tray Drawings: Dimensions and Tolerances Buyers Should Review"},"content":{"rendered":"

JEDEC Tray Drawings: Dimensions and Tolerances Buyers Should Review is a purchasing and validation problem: the aim is to turn a tray drawing into measurable purchase requirements without confusing reference dimensions with acceptance characteristics. 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 drawing<\/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
Outer envelope<\/td>\nLength, width, height and side features<\/td>\nConfirm against named equipment and gauges<\/td>\n<\/tr>\n
Pocket geometry<\/td>\nRows, columns, pitch, depth and clearances<\/td>\nUse the device drawing and functional gauges<\/td>\n<\/tr>\n
Stack dimensions<\/td>\nStack pitch, accumulated height and cover fit<\/td>\nMeasure a representative stack<\/td>\n<\/tr>\n
Datum scheme<\/td>\nMeasurement origins and orientation cues<\/td>\nAgree drawing revision and inspection method<\/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. Outer envelope: Turn the Requirement into Evidence<\/h2>\n

For jedec tray drawing, the buyer must define length, width, height and side features<\/strong>. This point controls whether the tray can turn a tray drawing into measurable purchase requirements without confusing reference dimensions with acceptance characteristics. 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 confirm against named equipment and gauges<\/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. Pocket geometry: Turn the Requirement into Evidence<\/h2>\n

For jedec tray drawing, the buyer must define rows, columns, pitch, depth and clearances<\/strong>. This point controls whether the tray can turn a tray drawing into measurable purchase requirements without confusing reference dimensions with acceptance characteristics. 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 the device drawing and functional gauges<\/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. Stack dimensions: Turn the Requirement into Evidence<\/h2>\n

For jedec tray drawing, the buyer must define stack pitch, accumulated height and cover fit<\/strong>. This point controls whether the tray can turn a tray drawing into measurable purchase requirements without confusing reference dimensions with acceptance characteristics. 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 a representative stack<\/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. Datum scheme: Turn the Requirement into Evidence<\/h2>\n

For jedec tray drawing, the buyer must define measurement origins and orientation cues<\/strong>. This point controls whether the tray can turn a tray drawing into measurable purchase requirements without confusing reference dimensions with acceptance characteristics. 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 agree drawing revision and inspection method<\/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: Copying dimensions from one worn sample<\/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: Omitting tolerances and datum references<\/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: Measuring isolated features without testing stack function<\/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