MST
RFQ cartCart

MPW tapeout handoff: match GDS, verification reports and the sample delivery timeline

Planning an MPW project?

Share a non-confidential brief to discuss process fit, shuttle timing, packaging and test scope.

“GDS uploaded” is not the same milestone as “design accepted,” and neither means samples are ready to test. A useful MPW handoff connects one frozen layout release to its verification evidence, owners and downstream packaging/test plan. This checklist helps reveal missing dependencies before a deadline becomes urgent.

Define the milestones instead of quoting one lead time

MilestoneEvidence to requestWhat it does not establish
Project/run registrationProvider acknowledgement and remaining conditionsDesign acceptance or guaranteed capacity
Design submissionReceipt of the specified files and release identifierSuccessful signoff
Design acceptanceProvider confirmation against the applicable requirementsWafer fabrication completion
Wafer startConfirmed manufacturing milestonePackaged-sample delivery date
Fabrication completionStatus of wafers/dies and release to the next operationPassing packaged chips
Assembly/test completionAgreed quantity, inspection/test results and dispositionReceipt at your laboratory
Laboratory receiptShipment received and incoming checks completeFunctional success on your board
Ask which dates are contractual, provisional or dependent on other participants. A public calendar is a planning input. For example, GlobalFoundries describes platform-specific shuttles and directs customers to its portal for current schedules; it is not evidence of a reserved MST slot. See the GlobalShuttle program (https://gf.com/manufacturing/services/multi-project-wafer-program/) .

Build a release manifest

Record the following in a controlled handoff package, with an owner for every unresolved item:
Manifest fieldWhat must agree
Layout artifactFilename, format, revision, checksum, top cell and units
Process identityFoundry/platform, process options, PDK and rule-deck releases
Layer interpretationRequired layer mapping and any provider-specific submission conventions
Verification evidenceDRC/LVS reports, run configuration and exact layout/netlist revisions checked
ExceptionsRemaining errors or waivers, rationale and named approval authority
Physical interfacesDie outline/thickness assumptions, pad map and package/assembly drawing revisions
Test handoffSample allocation, test owner, required data and acceptance criteria
Do not pair a clean report from an earlier layout with a new file merely because the top-cell name matches. A checksum can identify the artifact; it cannot prove that the circuit passes DRC/LVS or that a waiver is accepted. Follow the actual provider's verification and submission requirements.

Worked example: schedule backward from the laboratory

Suppose an invented planning exercise allows 7 calendar days for shipment, 21 calendar days for packaging/test and 14 calendar days of contingency after fabrication. The total is 7 + 21 + 14 = 42 calendar days. In that simplified sequence, fabrication must complete at least 42 calendar days before the target laboratory receipt date.
These are teaching assumptions, not observed supplier lead times. This calculation does not determine the GDS submission date: fabrication duration, run acceptance, queueing, holidays and upstream review time still need provider confirmation. If operations overlap, model the actual dependencies instead of simply summing every duration. Test-board and fixture preparation may run in parallel but still block useful measurements if unfinished.

Use the tools for the checks they actually perform

The report revision checker (https://mst-sg.com/tools/report-revision-check/) helps compare report metadata with a selected release. The handoff manifest generator (https://mst-sg.com/tools/gds-handoff-manifest/) organizes artifact identity and handoff information. Neither runs signoff DRC/LVS or approves a design for a foundry.
Try the synthetic exercise in the MPW handoff handbook (https://mst-sg.com/tools/mpw-handoff-handbook/) before using your project's controlled data. Use the procurement timeline planner (https://mst-sg.com/tools/mpw-procurement-timeline/) to record assumptions and owners. Keep restricted design files out of public discussion threads.

Primary references and further reading

Next step: request an MPW readiness review (https://store.mst-sg.com/mpw#mpw-inquiry-form) with a non-confidential milestone plan and list of missing evidence. Continue with the packaging and quotation guides in the MPW community (https://store.mst-sg.com/community/c/mpw) .
Parts

Replies (0)

No replies yet.

Planning an MPW project?

Share a non-confidential brief to discuss process fit, shuttle timing, packaging and test scope.