HHGrace MPW Schedule, Slot & Capacity Enquiry
Prepare an HHGrace MPW schedule, slot, data-in and capacity enquiry with exact timing definitions, evidence owners and fab-confirmed gates.
Short answer: There is no public MST feed that proves a live HHGrace (Hua Hong / 华虹) MPW slot or data-in deadline. Start by defining the exact technology option, readiness date, die-area range, samples, package/test scope, customer entity, country/end use and PDK/NDA status. MST Singapore can turn that non-confidential scope into an HHGrace capacity enquiry and coordinate fab review as a non-exclusive agent for overseas projects. A planning window becomes actionable only after the fab confirms technical eligibility, capacity, milestones and commercial prerequisites for the specific case.
This distinction matters because buyers often use “schedule” to mean four different things: when a shuttle might run, whether space remains, when commercial registration closes and when final design data is due. Treating those as one date creates false urgency and missed gates. The useful output is not a copied calendar row; it is a dated decision record with definitions, owners, evidence and a next confirmation step.
What should an HHGrace MPW schedule enquiry ask?
Ask for the smallest set of facts that can be reviewed without design IP. Identify the preferred node and process family, but also explain the electrical requirement that drives it. Give a die-area range rather than an unverified final outline. State the earliest credible design-ready date and the business target separately. Include sample form and quantity, expected package and test scope, project entity, country/region and end-use category. Finally, state whether the team already has an NDA, a controlled PDK path and an EDA environment that can use the applicable kit.
HHGrace’s public customer-inquiry form itself requests company and contact information plus application market, end product, chip type and platform. That establishes the shape of an initial enquiry. It does not publish a live MPW calendar, confirm space or waive later technical, legal and commercial review.
Separate the four clocks before comparing dates
| Clock | Question it answers | Evidence needed | Why it is not interchangeable |
|---|---|---|---|
| Planning window | Which period should the team target for implementation planning? | Internal design schedule and a dated fab-facing enquiry. | A planning target does not prove a run or slot exists. |
| Commercial gate | By when must eligibility, quote, purchase-order or reservation conditions be completed? | Fab-confirmed milestone name, timezone and prerequisites. | It may close before final layout data is expected. |
| Data-in gate | When is the accepted final data package due? | Applicable format, checksum, precheck, signoff and waiver rules. | “GDS deadline” may omit earlier dry-run or review gates. |
| Fab execution | What are the fab-defined tapeout, fabrication and delivery milestones? | Written project-specific confirmation and current change status. | Public program language cannot prove an accepted project date. |
Build a schedule brief the fab can actually review
A useful brief is explicit about what is known and what is still assumed. “Need 55nm soon” is not sufficient. “Targeting a low-power MCU with embedded non-volatile memory; 4–6 mm² preliminary die range; design signoff forecast for late Q1; 40 packaged engineering samples; overseas commercial entity; NDA not started” gives reviewers a path to ask the right next questions without exposing controlled files.
| Decision input | Evidence required | Unknown owner | Next gate |
|---|---|---|---|
| Node and process option | Requirement-to-platform rationale, voltage, memory, analog/RF and reliability needs. | Chip architect | Fab process-fit screening. |
| Design readiness | Owned plan through PDK setup, implementation, verification and release. | Design programme lead | Credible data-ready range. |
| Die and sample scope | Area range, seal-ring assumption, delivery form and sample quantity. | Physical-design and product leads | Capacity and commercial review. |
| Package and test | Pad map status, package concept, probe/final-test and bring-up assumptions. | Package/test owner | End-to-end schedule alignment. |
| Customer eligibility | Legal entity, country/region, application, end use and compliance context. | Commercial/compliance owner | Customer onboarding review. |
| Milestones | Exact names, dates, timezone, source revision and prerequisites. | MST/fab coordinator | Written fab confirmation. |
How MST coordinates the enquiry
- Normalize the non-confidential scope. MST checks whether the enquiry states a real process need, readiness range and delivery objective.
- Expose the unknowns. Missing NDA/PDK ownership, package assumptions, compliance context or signoff plan are recorded rather than guessed.
- Route a capacity enquiry. MST coordinates submission for HHGrace review; the fab decides whether the project, option and timing can proceed.
- Freeze the decision record. Any confirmed milestone is recorded with its definition, timezone, prerequisites and confirmation date so the team does not rely on an ambiguous screenshot.
MST’s role is customer access, requirement preparation and project coordination. It is not a source of unconditional fab allocation. If the requested timing is not workable, the next decision may be a later window, a different technology option or a separately qualified alternative route.
Red flags in a schedule answer
- A date is given without saying whether it is registration, preliminary data, final data, tapeout or estimated delivery.
- A “slot” is discussed without the exact process option, die-area range, customer eligibility or written acknowledgement.
- The deadline has no timezone, source revision or owner for subsequent changes.
- The internal schedule assumes immediate NDA/PDK access even though onboarding has not started.
- Package, wafer probe, dicing and final test are treated as if they occur inside the same fab milestone.
Use the right supporting resources
Open the HHGrace MPW agent and capacity-enquiry entry when the route is already known. Use the MPW Shuttle Finder to structure and compare planning windows without treating them as live HHGrace availability.
Frequently asked questions
Does MST publish the next HHGrace MPW shuttle date?
No. MST publishes a preparation and coordination path, not a live HHGrace schedule. Ask for current project-specific milestones after the non-confidential scope has been screened.
Does a public process update prove MPW capacity?
No. A company filing or process-platform announcement can describe technology status, but it does not establish MPW eligibility, available space, a data-in date or acceptance for one design.
What date should my design team plan against?
Plan against the earliest credible internal release range until the exact fab milestones are confirmed. Then track commercial, preliminary-data, final-data and fab-execution gates separately, including timezone and prerequisites.
Can I ask about timing before final GDS?
Yes. A useful early capacity enquiry uses node/process requirements, a die-area range, a readiness estimate, samples, package/test assumptions, customer country/end-use and PDK/NDA status. Public intake should remain non-confidential.
Who confirms an HHGrace slot or deadline?
The fab confirms technical eligibility, current capacity and applicable project milestones. MST prepares the enquiry and coordinates the review but does not convert a public planning date into a fab commitment.
Primary sources and review boundary
- HHGrace Customer Inquiry — official public intake fields for company, application market, end product, chip type and platform.
- HHGrace Online FAQ — official customer-support and online-service context.
- HHGrace Online — official controlled customer access surface; it is not evidence of public PDK entitlement.
- Hua Hong Semiconductor 2025 Annual Report — current public company and process-platform context, not an MPW slot schedule.
- GlobalFoundries GlobalShuttle — an official example showing that MPW program details vary by technology and customer; it is not an HHGrace schedule source.
Last technically reviewed: August 9, 2026. Public pages establish enquiry fields and public platform context only. HHGrace capacity, eligibility, slot, schedule, data-in deadline, PDK path, quotation and acceptance remain fab-confirmed case by case.
Related Articles
Ready to plan your MPW and first-silicon path?
Start with a non-confidential brief covering node/process fit, schedule, first-silicon validation, packaging/test, sample handling or re-spin needs. MST routes the request for review; feasibility, availability, timing and quotation are confirmed case by case.