Packaging, dicing and test RFQ
Scope
Scope the post-wafer work that turns prototype silicon into usable samples: wafer dicing, bare-die handling, QFN/BGA/WLCSP or ceramic package assumptions, open-cavity needs, socket/load-board expectations, wafer probe, packaged test, sample quantity, shipment, and acceptance criteria. MST does not guarantee package availability, yield, schedule, or final pricing before partner review; we organize a qualified, case-by-case RFQ path after the high-level brief.
Can help with
Package scoping
Translate die, pad, sample and use-case constraints into a package/test RFQ brief.
Dicing and bare-die handling
Clarify wafer output, die count assumptions, bare-die handling, packing and shipment needs.
Probe and packaged-test path
Separate wafer probe, packaged test, load-board and socket needs before partner quotation.
Workflow
1. Non-IP brief
Submit package target, die size range, sample count and validation needs.
2. Readiness screen
MST checks whether assumptions are quote-ready or need partner clarification.
3. Partner RFQ
Qualified requests are routed for case-by-case package, test and logistics confirmation.
Required input
Package / output target
Select all that apply; a rough target is enough.
Test / validation scope
Expected sample count
Known constraints
Deliverables
Package/test requirement brief
Readiness gap list
Partner-confirmed indicative quote path
Not accepted
GDS/OASIS, netlist, RTL, or confidential design database
Review gate
No GDS, netlist, RTL, source code or confidential design database is accepted at intake. Sensitive end uses, restricted parties and unclear shipment routes require manual review.
FAQ
What is Packaging, dicing and test RFQ?
Scope wafer dicing, packaging, wafer probe, packaged test, sockets, load boards and prototype-sample logistics after MPW tapeout.
What information should be submitted at intake?
Package / output target, Test / validation scope, Expected sample count, Known constraints
Can confidential design files be uploaded through public intake?
Public intake should contain high-level, non-confidential scope information only.
Does MST review compliance or risk before routing this RFQ?
No GDS, netlist, RTL, source code or confidential design database is accepted at intake. Sensitive end uses, restricted parties and unclear shipment routes require manual review.