{
  "schemaVersion": 1,
  "id": "atlas-lesson-manufacturing-execution-dispatch",
  "title": "MES, dispatch and process release",
  "category": "learning",
  "format": "Atlas lesson",
  "description": "Coordinates material routes, equipment eligibility, holds and measurement decisions.",
  "canonicalUrl": "https://semiaifoundry.com/learn/atlas/manufacturing-execution-dispatch/",
  "publishedDate": null,
  "revisionDate": "2026-10-07",
  "author": null,
  "topic": "Fabrication / Factory systems",
  "series": null,
  "license": null,
  "rightsUrl": "https://semiaifoundry.com/ai-atlas/licenses.html",
  "version": "1.3.0",
  "status": "Published educational lesson",
  "evidenceScope": "TSMC describes public capabilities, not its proprietary rules, live queues or customer priority policy. The lesson uses generic operations reasoning.\n\nThe scenario is fictional and qualitative. No manufacturing recipe, production dispatch scheduler, equipment interface or real lot release is executed or inferred.",
  "contentCoverage": "published-lesson",
  "artifactUrl": "https://semiaifoundry.com/ai-atlas/lesson-data/manufacturing-execution-dispatch-bd3550e94e978ca6.json",
  "interactiveUrl": "https://semiaifoundry.com/ai-atlas/#manufacturing-execution-dispatch",
  "related": [],
  "supersedes": [],
  "supersededBy": [],
  "contentHash": "cb37740961a7aa505e4a5c72ed43bf0b4560606f775c1cd128836b9d12665be6",
  "contentLength": 7170,
  "jsonUrl": "https://semiaifoundry.com/agents/publications/atlas-lesson-manufacturing-execution-dispatch.json",
  "markdownUrl": "https://semiaifoundry.com/agents/publications/atlas-lesson-manufacturing-execution-dispatch.md",
  "sections": [
    {
      "id": "section-1",
      "title": "MES, dispatch and process release",
      "start": 46,
      "end": 404
    },
    {
      "id": "section-2",
      "title": "The mechanism",
      "start": 404,
      "end": 2242
    },
    {
      "id": "section-3",
      "title": "Science and assumptions",
      "start": 2242,
      "end": 2270
    },
    {
      "id": "section-4",
      "title": "Flow conservation",
      "start": 2270,
      "end": 3072
    },
    {
      "id": "section-5",
      "title": "Engineering example",
      "start": 3072,
      "end": 3720
    },
    {
      "id": "section-6",
      "title": "Distinctions and tradeoffs",
      "start": 3720,
      "end": 4123
    },
    {
      "id": "section-7",
      "title": "Specifications and interfaces",
      "start": 4123,
      "end": 4387
    },
    {
      "id": "section-8",
      "title": "Interfaces",
      "start": 4387,
      "end": 4593
    },
    {
      "id": "section-9",
      "title": "Check your understanding",
      "start": 4593,
      "end": 4622
    },
    {
      "id": "section-10",
      "title": "Why can maximizing every tool’s utilization increase cycle time?",
      "start": 4622,
      "end": 5059
    },
    {
      "id": "section-11",
      "title": "A model recommends processing a held lot. What establishes whether dispatch may proceed?",
      "start": 5059,
      "end": 5487
    },
    {
      "id": "section-12",
      "title": "Evidence and scope",
      "start": 5487,
      "end": 5970
    },
    {
      "id": "section-13",
      "title": "Sources",
      "start": 5970,
      "end": 6484
    },
    {
      "id": "section-14",
      "title": "Continue exploring",
      "start": 6484,
      "end": 6507
    },
    {
      "id": "section-15",
      "title": "Foundations",
      "start": 6507,
      "end": 6635
    },
    {
      "id": "section-16",
      "title": "Related lessons",
      "start": 6635,
      "end": 7170
    }
  ],
  "citations": [
    {
      "title": "Explore in Atlas",
      "url": "https://semiaifoundry.com/ai-atlas/#manufacturing-execution-dispatch"
    },
    {
      "title": "TSMC — Intelligent Packaging Fab",
      "url": "https://www.tsmc.com/english/dedicatedFoundry/services/apm_intelligent_packaging_fab"
    },
    {
      "title": "Edwards — Semiconductor vacuum and abatement",
      "url": "https://www.edwardsvacuum.com/en-us/semiconductor"
    },
    {
      "title": "Temporal Activities",
      "url": "https://docs.temporal.io/activities"
    },
    {
      "title": "Published lesson data",
      "url": "https://semiaifoundry.com/ai-atlas/lesson-data/manufacturing-execution-dispatch-bd3550e94e978ca6.json"
    },
    {
      "title": "Atlas releases and licensing",
      "url": "https://semiaifoundry.com/ai-atlas/licenses.html"
    },
    {
      "title": "Wafer handling, carriers and genealogy",
      "url": "https://semiaifoundry.com/learn/atlas/wafer-handling-genealogy/"
    },
    {
      "title": "Cycle time, ramp and effective capacity",
      "url": "https://semiaifoundry.com/learn/atlas/fab-ramp-cycle-time/"
    },
    {
      "title": "HBM stack assembly, repair and staged test",
      "url": "https://semiaifoundry.com/learn/atlas/hbm-stack-assembly-test/"
    },
    {
      "title": "User authority and service identity",
      "url": "https://semiaifoundry.com/learn/atlas/tool-authority-identity/"
    },
    {
      "title": "Workflow graphs and explicit state",
      "url": "https://semiaifoundry.com/learn/atlas/workflow-graphs-state/"
    },
    {
      "title": "Evaluation & the AGI frontier",
      "url": "https://semiaifoundry.com/learn/atlas/evaluation/"
    }
  ],
  "recordHash": "8e454f89a0c4bda146f12750052e8c608c159595fa2e715bf25dce2a40403a0e",
  "contentFormat": "text/markdown",
  "content": "Fabrication / Factory systems · Atlas v1.3.0\n\n# MES, dispatch and process release\n\nCoordinates material routes, equipment eligibility, holds and measurement decisions.\n\n[Explore in Atlas](https://semiaifoundry.com/ai-atlas/#manufacturing-execution-dispatch)Chamber, wafer carrier and fab floor; schematic routes\n\nLearning objectiveSeparate dispatch, qualification, process control and material release.\n\n## The mechanism\n\nA manufacturing execution system records where material is and whether the next operation is permitted. Dispatching chooses among eligible lots and tools, while engineering holds prevent suspect material from continuing. These are different decisions from selecting a process recipe or statistically controlling its result. Re-entrant fabrication makes scheduling difficult because wafers revisit tool families many times and share them with other products. Prioritizing one lot may delay another without increasing total output. The useful factory view therefore connects route state, tool qualification, queue time, inspection and genealogy, and distinguishes an urgent order from a physically feasible production path.\n\nA model recommendation can be an input to dispatch without becoming the authority that releases a lot or selects equipment. Route eligibility, holds, qualification, current state and authorized decisions remain distinct control conditions. The fictional incident workflow illustrates this boundary using inventory and work orders; it should not be mistaken for an implementation of a real fab’s MES or private dispatch algorithm.\n\n1.  Represent the actual route, including repeated visits and required measurement gates.\n2.  Determine which tools are qualified and currently available for each operation.\n3.  Apply holds and queue-time constraints before ranking eligible material.\n4.  Dispatch and record the operation, retaining recipe and equipment identity.\n5.  Reconcile completed work with inspection and downstream demand rather than optimizing isolated tool counts.\n6.  A recommendation retains its model/data provenance and the asset or lot identity to which it applies.\n7.  An authorized dispatch evaluates current holds and qualification before creating a concrete operational effect.\n\n## Science and assumptions\n\n### Flow conservation\n\n$$\n\\mathrm{WIP}_{\\mathrm{next}}=\\mathrm{WIP}_{\\mathrm{now}}+N_{\\mathrm{arrivals}}-N_{\\mathrm{departures}}\n$$\n\nNext work in process equals current work in process plus arrivals minus departures, all in the same material unit.\n\nSymbols and units\n\nWIP\\_next\n\nMaterial in process after the interval\n\nsame declared material units\n\nWIP\\_now\n\nMaterial in process before the interval\n\nsame declared material units\n\nN\\_arrivals\n\nMaterial entering during the interval\n\nsame declared material units\n\nN\\_departures\n\nMaterial leaving during the interval\n\nsame declared material units\n\nAll terms count the same material unit over one time interval; WIP means work in process.\n\nAssumptions Count split/merge events explicitly. Wafer, die and package counts cannot be added without conversion.\n\n## Engineering example\n\nSynthetic shift: 120 wafers arrive at a qualified step and 90 depart. Its queue grows by 30 wafers unless material is diverted or held elsewhere; raising arrival priority does not remove the imbalance.\n\nSuppose a classifier flags a hypothetical chamber for inspection while a lot is held pending qualification. The flag may create an inspection recommendation, but it does not release the hold. A workflow may seek the authorized review and record a work order; it still cannot mark the lot eligible merely because a model prediction was confident. This separates prediction quality from the controlled operational action.\n\n## Distinctions and tradeoffs\n\nA scheduling priority cannot create qualified capacity in a tool family that is already the binding constraint.\n\nLocal utilization can conflict with cycle time and time-sensitive surface requirements; a busy tool is not automatically improving system output.\n\nQueueing and release decisions affect when logic dies and HBM stacks become available for package convergence.\n\n## Specifications and interfaces\n\nRoute state\n\nEligible, processing, queued or held\n\nA material state at a timestamp, not a final yield prediction.\n\nTool eligibility\n\nQualified product/process combination\n\nInstalled equipment may not be released for every route.\n\n### Interfaces\n\nOrders, route and tool state Input\n\nRequired operations, priorities and qualification constraints\n\nDispatch and genealogy events Output\n\nAuthorized movement and a traceable process history\n\n## Check your understanding\n\n### Why can maximizing every tool’s utilization increase cycle time?\n\n1.  All fabrication steps have identical capacity\n2.  Extra work-in-process can build queues ahead of a bottleneck\n3.  More queued wafers always mean more finished packages\n\nAnswer and reasoning\n\nExtra work-in-process can build queues ahead of a bottleneck\n\nUpstream releases can exceed downstream throughput, increasing waiting without increasing completed output.\n\n### A model recommends processing a held lot. What establishes whether dispatch may proceed?\n\n1.  The confidence score alone\n2.  Current route/hold/qualification and authorization conditions\n3.  Whether the recommendation is fluent\n\nAnswer and reasoning\n\nCurrent route/hold/qualification and authorization conditions\n\nDispatch authority and eligibility remain external operational constraints, not model-generated permissions.\n\n## Evidence and scope\n\nTSMC describes public capabilities, not its proprietary rules, live queues or customer priority policy. The lesson uses generic operations reasoning.\n\nThe scenario is fictional and qualitative. No manufacturing recipe, production dispatch scheduler, equipment interface or real lot release is executed or inferred.\n\nNo current calculator directly models this lesson’s main mechanism. Use the library for related bounds while retaining their stated omissions.\n\n## Sources\n\n-   [TSMC — Intelligent Packaging Fab](https://www.tsmc.com/english/dedicatedFoundry/services/apm_intelligent_packaging_fab)\n-   [Edwards — Semiconductor vacuum and abatement](https://www.edwardsvacuum.com/en-us/semiconductor)\n-   [Temporal Activities](https://docs.temporal.io/activities)\n\n[Published lesson data](https://semiaifoundry.com/ai-atlas/lesson-data/manufacturing-execution-dispatch-bd3550e94e978ca6.json) · [Atlas releases and licensing](https://semiaifoundry.com/ai-atlas/licenses.html)\n\n## Continue exploring\n\n### Foundations\n\n-   [Wafer handling, carriers and genealogy](https://semiaifoundry.com/learn/atlas/wafer-handling-genealogy/)\n\n### Related lessons\n\n-   [Cycle time, ramp and effective capacity](https://semiaifoundry.com/learn/atlas/fab-ramp-cycle-time/)\n-   [HBM stack assembly, repair and staged test](https://semiaifoundry.com/learn/atlas/hbm-stack-assembly-test/)\n-   [User authority and service identity](https://semiaifoundry.com/learn/atlas/tool-authority-identity/)\n-   [Workflow graphs and explicit state](https://semiaifoundry.com/learn/atlas/workflow-graphs-state/)\n-   [Evaluation & the AGI frontier](https://semiaifoundry.com/learn/atlas/evaluation/)"
}