How to Choose an MPW Shuttle Run

Short answer: Choose an MPW shuttle run by proving process and PDK fit first, then comparing the exact commercial and milestone fields for the same deliverable. Record the technology option, eligibility, registration deadline, final GDS deadline, price unit, minimum area or charge, included sample form and quantity, packaging/test scope, estimated shipment definition and last provider confirmation. A public schedule is a shortlist—not evidence of available capacity or accepted design. The selected run remains a preliminary fit until the provider confirms access, technical acceptance, quotation and current milestones in writing.

The wrong selection method starts with the nearest date or lowest number in a price table. The right method begins with the circuit, eliminates technically unsuitable options, checks whether the team can legally and practically use the PDK, and only then compares run economics and timing.

Gate 1: Can this exact process option implement the chip?

A node name is not a process specification. Confirm the transistor and passive-device options, voltage domains, temperature models, RF or analog models, embedded memory, IO, ESD, metal stack, density/fill requirements, reliability options and supported IP. For mixed-signal and high-voltage designs, isolation and device SOA can be decisive. For RF, model quality, passives and packaging may dominate the nominal node.

The answer must come from the applicable PDK and provider/foundry documentation. A web page can establish a preliminary fit; it cannot replace controlled model and rule review.

Gate 2: Can your team obtain and use the PDK in time?

Ask which entity signs the NDA or design-kit licence, which engineers receive access, what EDA versions are supported and which IP/library releases apply. Include onboarding time in the schedule. A run three months away may be unusable if legal access, tool setup, design implementation and signoff cannot finish before its registration and final-data gates.

Gate 3: Are you comparing the same milestone?

Official programs use dates differently. A listed date can be a registration deadline, export-control deadline, reservation deadline, preliminary or dry-run GDS date, final GDS submission, provider tapeout, or estimated shipment. These are not interchangeable. Copy the provider’s exact wording, timezone and publication/revision date into the run record.

For example, one 2026 public table identifies GlobalFoundries entries as registration deadlines and describes a later final-data window, while other entries call their calendar date a GDS deadline. X-FAB’s detailed schedule separates reservation, signed quotation or purchase order, dry-run GDS, final GDS, tapeout and estimated shipment. The useful lesson is the field structure, not a promise that any displayed run remains open.

Build one normalized run record

Compare total project cost, not only fabrication price

Normalize every number into a project estimate with evidence. Include minimum billable area, extra wafers or die, provider service fees, third-party IP, EDA, design enablement, package engineering, substrate/NRE, assembly, test hardware, test program, characterization, shipping, duties and the cost of schedule movement or re-spin.

If a public table states EUR/mm² with a minimum fabrication cost equivalent to a given area, multiply only after confirming whether your design geometry and seal-ring convention fit. If a price applies to an academic or publicly funded category, do not apply it to a commercial startup without eligibility confirmation. Never copy a bare price into an article or proposal without its currency, unit, minimum, included/excluded items and source date.

Schedule backwards from final GDS

A credible run plan contains more than “layout complete.” Work backwards through provider dry-run or precheck, full signoff, package/pad-map freeze, top-level integration, IP/library readiness, PDK/tool installation, NDA/access, quote/PO and design registration. Add ownership and evidence at every gate.

1. Commercial/eligibility gate: entity, end use, region and participation class accepted for review.
2. Technology baseline: exact PDK, option, tools, models, libraries and IP frozen.
3. Area registration: size estimate and provider tolerance documented.
4. Dry-run or precheck: if required, delivery date and correction owner planned.
5. Final release: controlled GDS/OASIS, manifest, checksum, signoff and waivers approved.
6. Provider data acceptance: corrections closed under the provider’s process.
7. Run and delivery: provider-defined tapeout, fabrication and estimated shipment tracked separately.

Use a run-selection decision record

A scoring model that does not hide hard gates

Do not average away a fatal mismatch. First mark process/PDK fit, eligibility and completion feasibility as pass/fail gates. Only surviving routes should be scored. A practical weighted comparison may then consider total cost, schedule confidence, sample usefulness, package/test readiness, provider support, re-spin path and production transition.

Keep “unknown” distinct from “poor.” An unknown capacity or package scope should trigger an owner and next action, not silently receive a middle score. Use confidence labels such as documented, provider-confirmed, inferred or unknown.

Red flags in an MPW offer

• A node and date are shown, but the technology option and PDK version are missing.
• A price is quoted without currency, unit, minimum charge, included delivery or validity date.
• “Samples” are promised without saying wafer, loose die, packaged units or tested-good parts.
• A reservation claim has no run code, written provider acknowledgement or commercial prerequisites.
• Fabrication, package, test and qualification are described as one undifferentiated delivery.
• A third party presents slot, yield or shipment as unconditional even though only the responsible provider can confirm the current state.

Use the MPW Shuttle Finder to structure a shortlist and the MST MPW access guide for route context. If the model itself is new, start with What Is MPW in Semiconductor?. If the route is unclear, continue with Where Can I Manufacture a Small Batch of Custom Chips?. If access is the blocker, read How to Tape Out Your First ASIC Without a Foundry Account. For technical family selection, use BCD vs eFlash vs Logic CMOS vs SiGe BiCMOS, then compare the established MPW vs Full Mask decision.

Request a non-confidential MPW run-selection review. MST can normalize the stated requirement and public run evidence; the provider confirms access, capacity, technical acceptance, quotation and milestones.

Frequently asked questions

What is the most important MPW shuttle date?

There is no universal single date. Registration, export-control information, dry-run data, final GDS, tapeout and shipment are different milestones. The project must record each applicable deadline, its timezone and the provider’s definition.

Does a published MPW schedule mean the run has space?

No. A public schedule establishes that a program announced a run, not that capacity remains or that your design is accepted. Ask the responsible provider for current written confirmation after supplying the non-confidential screening information.

How do I compare MPW prices?

Normalize currency, pricing unit, minimum area or charge, discount eligibility, included samples, delivery form and exclusions. Add design enablement, package, test, logistics and likely re-spin costs before comparing project totals.

Should I choose the earliest run?

Only if the exact technology fits and the team can pass access, implementation, signoff and commercial gates before the relevant deadlines. Missing a dry-run or final-data gate can be more expensive than selecting a later feasible run.

How many samples will an MPW run deliver?

There is no universal number. Programs publish different defaults and conditions, and extra samples may be optional. Confirm whether the count refers to gross die, delivered die, packaged samples or tested-good units.

Primary sources and review boundary

• EUROPRACTICE 2026 schedules and prices — a current multi-provider example of different deadline meanings, units, minimums and sample notes.
• imec IC-Link 2026 MPW schedules — official provider schedule pages and downloadable detail.
• X-FAB MPW schedule 2026 — detailed reservation, quote/PO, dry-run, final-data, tapeout and estimated-shipment fields.
• GlobalFoundries GlobalShuttle — current shared-wafer program description and scheduling caveat.
• GlobalFoundries process design kits — official PDK scope and design enablement context.

Last technically reviewed: July 30, 2026. Public schedules and prices are dated discovery evidence, not capacity, acceptance or quotation. Confirm the exact option, eligibility, run code, milestones, commercial terms and delivery definition with the responsible provider.