Why English? | Reading a Semiconductor Foundry Wafer-Supply Agreement

A foundry wafer-supply agreement can combine manufacturing services, capacity reservation, long-range planning, purchase commitments, technology access, masks, testing and logistics. The title does not reveal which party bears demand risk or whether payment buys delivered wafers, reserved capacity, development work or several items.

Begin with recitals, definitions, commercial schedules and order-of-precedence clauses. Draw the business model in one sentence using defined terms: who provides design information, who owns masks, who starts wafers, what output is delivered, and which commitments survive a forecast change.

‘Supplier will support Customer’s requirements’ sounds broad. A later schedule may cap qualified technologies, sites, wafer diameters, monthly capacity and products. The specific schedule can turn an inspirational sentence into a bounded obligation.

• Name every party and capacity.
• Identify product and process scope.
• List incorporated schedules.
• Record order of precedence.
• State what each payment purchases.

This is not legal, engineering, procurement, accounting or export-control advice. Commercial language requires the actual signed documents and qualified review.

Students learn to convert a title into a mechanism. ‘Supply’ can hide design, reservation, manufacture, test and delivery stages.

Semiconductor nouns are dense. A contract may distinguish process technology, node, platform, design rules, product, part number, mask set, wafer diameter, revision, site and qualified line. Treat each as a controlled field rather than a synonym for ‘the chip’.

Build a product-technology-site matrix. If the agreement allows transfers between fabs or equivalent tools, locate qualification, notice and customer-approval rules. Check whether new revisions enter automatically or require a written addendum.

A customer may order the same commercial part after a design revision, yet the foundry sees a new mask set and manufacturing revision. Without version control, yield and acceptance data from the earlier product can be applied to the wrong output.

• Create a defined-term glossary.
• Map product to technology and site.
• Control mask and revision identity.
• Check alternate-site rights.
• Track qualification status.

Node labels alone do not prove performance, suitability or equivalence. Engineers and quality teams determine technical acceptability.

This is taxonomy in action: well-chosen categories let teams compare like with like instead of arguing from familiar labels.

Early engineering lots, prototypes, qualification wafers and volume production can have different pricing, yield expectations, acceptance rules and schedule commitments. A reader should find the gate between phases and the evidence required to cross it.

Map non-recurring engineering, mask fabrication, design-rule checks, tape-out, pilot lots, qualification, production release and sustaining changes. State whether a forecast before qualification is binding, conditional or merely planning information.

A pilot lot can deliver valuable learning while missing the mature yield target. Calling it ‘failed supply’ may be wrong if the contract treats the lot as development. Calling it ‘successful’ may also be wrong if the qualification gate was not passed.

• Name every project phase.
• Define entry and exit evidence.
• Separate NRE from production price.
• Control waiver scope.
• Archive qualification decisions.

A commercial reader should not declare technical qualification. The report can show the gate and evidence owner.

Students see why project verbs matter: design, verify, qualify, release and manufacture are sequential but not interchangeable.

Forecasts can be binding for a near-term window, flexible in later months and informational farther out. Capacity reservations, minimum purchases, take-or-pay terms and rescheduling limits may overlay those buckets.

Create a rolling-horizon table showing each month, forecast status, reserved capacity, permitted variance, order deadline and consequence of change. Then show how the horizon rolls after each update. A single annual total hides the operational constraint.

A customer may reduce the annual forecast by ten percent yet breach a near-term non-cancellable window. Conversely, a distant forecast increase may not create a firm foundry obligation. The bucket controls the conclusion.

• Map binding and flexible buckets.
• Keep units explicit.
• Reconcile reservation and order.
• Track permitted variance.
• Model rolling updates.

Do not infer enforceability from business-system labels such as ‘firm’ or ‘committed’ without checking the contract definition.

This is spreadsheet English: column names have legal and operational meaning, so learners must define them before calculating.

A purchase order may be an offer, a release under the master agreement or an administrative record. The agreement should explain required fields, acceptance, priority, change, cancellation and conflict with boilerplate.

Draw the chain: forecast, capacity allocation, purchase order, acknowledgement, material planning, wafer start, work in process, test, shipment and invoice. Mark the last reversible point and the cost already committed there.

A buyer can request cancellation after wafer start. Whether it owes full price, work-in-process cost or another amount depends on the cancellation clause and stage evidence. ‘Cancelled in ERP’ does not decide liability.

• Define valid order fields.
• Record acceptance method.
• Identify cancellation cut-offs.
• Track requested versus committed date.
• Control conflicting terms.

Order administration can create legal consequences. Procurement and counsel should govern deviations and boilerplate conflicts.

Students learn process mapping: a result is built through reversible and irreversible steps, not created instantly when a form appears.

Price can apply per wafer start, completed wafer, mask, engineering hour, reserved unit or delivered good die. It may vary by technology, layer count, test, yield arrangement, volume, material surcharge, currency or index.

Build a price equation with defined inputs and effective dates. Show taxes, freight, packaging, scrap treatment and credits separately. If price review depends on documented cost change or negotiation, do not substitute an invented escalation formula.

A lower price per wafer can still produce a higher effective product cost if included tests differ or yield risk shifts. The agreement reader should not compare two numbers until the delivered scope and risk allocation match.

• Name the priced unit.
• List included operations.
• Track currency and effective date.
• Separate surcharge and tax.
• Reconcile credits and prepayments.

Commercial models can be confidential and accounting treatment is specialist work. Use authorised data and review.

This chapter strengthens quantitative literacy: denominators and included scope matter as much as the number.

Yield may mean functional die per wafer, percentage passing a test, line yield, lot yield or another agreed measure. It depends on die size, test programme, exclusions, sampling and data treatment. A contract may use yield for information, investigation, credit or acceptance.

Copy the yield definition exactly and map numerator, denominator, test point and excluded causes. Separate baseline, target, warranty and forecast. Then find whether the remedy is rework, replacement, credit, investigation or none.

If 700 of 1,000 measured die pass, ‘70% yield’ is only meaningful if the agreement defines those measured die as the denominator and the programme revision is valid. Edge exclusions or retest can change the calculation.

• Define numerator and denominator.
• Name the test stage.
• Control programme revision.
• Separate target from guarantee.
• Link remedy to wording.

Yield analysis is engineering and statistical work. A contract reader should make the calculation traceable, not certify product performance.

This is mathematical language at its best: a percentage becomes trustworthy only after the set being counted is clear.

The agreement may require incoming review, a notice period, evidence of nonconformance, root-cause cooperation, return authorisation and exclusive remedies. Latent defects, reliability failures and epidemic failure provisions may follow different timelines.

Build a decision tree from delivery to acceptance, rejection, investigation, disposition and remedy. State whether payment, use or silence constitutes acceptance and whether acceptance limits later warranty claims.

A customer can miss a visible-defect notice window but later discover a latent process problem. The contract may treat those events differently. The report must not close the second path just because the first window expired.

• Map notice periods.
• Separate visible and latent issues.
• Preserve lot traceability.
• Define investigation cooperation.
• Identify exclusive remedies.

Quality disposition requires authorised technical and contractual review. Do not recommend product use from a writing guide.

Learners practise branching logic: one event can open different routes depending on timing, evidence and definitions.

A foundry continuously improves tools, materials and flows, while customers need controlled product performance. The change clause balances ordinary control with notification, approval, requalification and emergency response.

Classify changes by impact and contract category: site, tool set, material, recipe, mask, test, subcontractor or specification. Record notice lead time, required data, customer response window and what happens if approval is withheld.

A chemical supplier change may not alter the customer part number, yet it can still fall within a process-change category. Conversely, routine maintenance may be excluded. The definition, not the drama, controls notice.

• Create a change taxonomy.
• Map notice and approval rights.
• Identify affected products and lots.
• Track qualification evidence.
• Control emergency deviations.

Not every change requires customer approval, and not every notification creates a veto. Read the negotiated allocation carefully.

Students learn change-control language: stable output can depend on documented evolution rather than absolute sameness.

A fabless customer can own product design while the foundry owns manufacturing know-how. Masks, reticles, test programmes, improvements, process data and yield data may have separate ownership, licences, access rights and return or destruction rules.

Create an asset-rights table: owner, permitted user, purpose, location, confidentiality level, licence term, security control and exit treatment. Avoid saying ‘the customer owns the chip’ as if that resolves every layer.

A foundry-developed process improvement can benefit the product without becoming customer-owned design IP. A customer-specific mask can be customer property while physically controlled at the fab. English must preserve both truths.

• Inventory intangible and physical assets.
• Name ownership and licence separately.
• Control affiliate and subcontractor access.
• Map data rights.
• Plan return or destruction.

IP scope and semiconductor security are specialist legal and technical matters. Obtain qualified advice.

This is relational vocabulary: ownership, possession, custody, access and licence describe different connections.

Capacity shortages, utility interruption, material constraints, disasters, geopolitical controls and equipment failure can affect supply. The agreement may allocate capacity, require mitigation, permit alternate sites, suspend obligations or create termination rights.

Map trigger, notice, evidence, mitigation, allocation rule, recovery plan and consequence. Separate an excused delay from a permanent right to ignore the obligation. Check whether the customer must maintain dual-source or safety stock assumptions.

A force-majeure notice may excuse a delay while still requiring allocation fairness, updates and mitigation. A customer’s urgent need does not automatically override the written allocation rule.

• Define disruption triggers.
• Record notice and updates.
• Map allocation method.
• Test alternate-site options.
• Plan termination and transition.

Export controls, sanctions and force majeure are high-stakes legal areas that change. Use current official requirements and counsel.

Students learn resilience reasoning: a plan should show how information, alternatives and decisions move during disruption.

A wafer-supply agreement is a lens on design, manufacturing, test, logistics, quality, procurement, finance and law. It shows why English matters even in a field built from physics and nanometre-scale processes: teams still need controlled definitions, forecasts, evidence and change notices.

Use public industry pages and public filed agreements for study. Build a process map without copying confidential terms. Then identify careers at each handoff: design enablement, process integration, product engineering, test, quality, supply planning, procurement, contracts and compliance.

A class can compare two public clauses by mechanism rather than deciding which company got the better deal. Ask what each clause measures, which risk it allocates and what evidence would activate it.

• Study only authorised public material.
• Map the semiconductor value chain.
• Label confidential boundaries.
• Identify interdisciplinary careers.
• Practise evidence-based comparison.

Public agreements may be old, amended, redacted or governed elsewhere. They are specimens, not current commercial advice.

Parents can encourage curiosity across subjects: the same learner may enjoy physics, data, contracts and communication because semiconductor work needs all four.

A fictional fabless company uses a specialty 200 mm foundry process. It submits a twelve-month rolling forecast, reserves monthly capacity, releases purchase orders eight weeks before wafer start and receives tested wafer data. A product revision is approaching qualification, while the foundry proposes a materials change.

Build the commercial flow

Draw forecast, reservation, order, acknowledgement, wafer start, processing, test, delivery, acceptance and payment. At each arrow, write the defined notice, unit and evidence. If one arrow has only ‘as agreed’, flag the missing mechanism instead of inventing it.

Run three forecast scenarios

• Demand falls inside the non-cancellable window
• Demand rises beyond reserved capacity
• Qualification slips while capacity has been reserved

For each scenario, calculate only after defining whether the unit is a wafer start, completed wafer, lot or currency commitment. State which result comes from the agreement and which is a planning assumption.

Test the proposed change

Classify the materials change under the change-control clause. Identify notice, supporting comparison data, affected products, qualification work, customer response and implementation date. Do not assume that ‘equivalent material’ is either automatically acceptable or automatically prohibited.

Open a low-yield investigation

Specify product revision, lot, wafer count, die map, test-programme version, numerator, denominator, retest treatment and comparison baseline. Then trace the agreement’s notice, cooperation and remedy route. Keep process-cause hypotheses outside the contract conclusion until engineering evidence supports them.

Is a forecast a binding purchase commitment?

Sometimes only in defined time buckets or alongside reservation terms. Read the agreement’s definitions, horizon and consequences.

What is a wafer start?

It generally refers to wafers entering fabrication, but the agreement’s definition and measurement point control the commercial meaning.

Does a yield target guarantee good die?

Not automatically. Yield must be defined, and the contract may treat a target as planning information, an investigation trigger or a remedy threshold.

Can a foundry change its process without approval?

Rights vary. Some changes may require notice, data, requalification or consent; others may fall within normal control. The negotiated clause governs.

Who owns the masks?

Ownership, custody, use and return can be split. Check the mask, tooling, IP and exit provisions.

Does force majeure cancel every obligation?

Usually not as a general conclusion. Notice, mitigation, allocation, duration and termination effects depend on the wording and current law.

• Singapore EDB semiconductor industry overview for current ecosystem context.
• Public X-FAB wafer-supply agreement exhibit as a reading specimen.
• Writing a supplier nonconformance report for lot evidence and corrective action.
• Reading a data processing addendum for another layered technology agreement.

The best wafer-supply reader does not race toward a favourable interpretation. They keep product, process, unit, time bucket and evidence aligned—so engineering, procurement and legal teams can decide from the same manufacturing story.