Autonomous Semiconductor Manufacturing with Multi-Modal LLMs and Reinforcement Learning

samsung · Tech · 2023 · source Agentic: yes · promotional bias: med · source-backed · extracted with prompt 0.5.4 (schema v2)

Generated from extraction.json — do not edit by hand. Every claim cites verbatim source evidence; stated means the quote directly asserts the claim, implied means it supports it indirectly.

Problem

Domain: Semiconductor manufacturing process control

Samsung is trying to move toward autonomous fab operations where AI can sense equipment behavior, analyze multimodal production data, and eventually support control decisions across extremely complex chip-manufacturing processes.

Constraints:

Architecture

Samsung frames Autonomous Fab around sensing, analysis, and control. The architecture combines equipment trace data, event logs, process histories, engineering notes, knowledge graphs, RAG/LLM assistants, multimodal foundation models, time-series models, OES/defect-image analysis, and reinforcement learning for future control. Production use already includes a multimodal engineering assistant and knowledge-graph/LLM alignment of sensor names, while process-control use remains gated by time-series accuracy and data-standardization work.

Diagram confidence: reconstructed (reconstructed from prose).

flowchart LR
  fab-equipment-sensors[Fab equipment sensors] --> trace-data-pipeline[Trace data pipeline]
  trace-data-pipeline --> time-series-foundation-models[Time-series foundation models]
  trace-data-pipeline --> knowledge-graph[Knowledge graph]
  event-and-history-stores[Event and history stores] --> knowledge-graph
  knowledge-graph --> rag-assistant[RAG assistant]
  rag-assistant --> engineer-users[Engineer users]
  multimodal-foundation-models[Multimodal foundation models] --> oes-analyzer[OES analyzer]
  multimodal-foundation-models --> defect-detector[Defect detector]
  trace-data-pipeline --> multimodal-foundation-models
  oes-analyzer --> engineer-users
  defect-detector --> engineer-users
  time-series-foundation-models --> process-control-layer[Process-control layer]
  fab-equipment-sensors --> process-control-layer
  process-control-layer --> reinforcement-learning-controller[Reinforcement learning controller]
Drag to pan · scroll or use +/− to zoom · reconstructed from the source's described component topology

Components

Component Role Interacts with
Fab equipment sensors Capture trace data such as reflected and forward power every second during process steps. Trace data pipeline, Process-control layer
Trace data pipeline Summarizes, windows, and stores time-series process signals for analysis. Fab equipment sensors, Time-series foundation models, Knowledge graph
Event and history stores Hold equipment events, alarms, maintenance history, and engineering notes. Knowledge graph, RAG assistant
Knowledge graph Connects equipment, chamber, wafer, sensor, and history relationships for alignment and diagnosis. Trace data pipeline, Event and history stores, RAG assistant, Engineer users
RAG assistant Answers engineer questions about errors and prior resolutions using historical/documentation context. Knowledge graph, Engineer users
Multimodal foundation models Combine text, image, table, and process data for diagnosis and analysis. Trace data pipeline, OES analyzer, Defect detector
Time-series foundation models Forecast equipment behavior from trace signals, though not yet control-ready. Trace data pipeline, Process-control layer
OES analyzer Analyzes optical emission spectroscopy peaks and plasma composition signals. Multimodal foundation models, Engineer users
Defect detector Classifies wafer-level defect patterns from inspection images. Multimodal foundation models, Engineer users
Process-control layer Future advanced process control loop using diagnosis, forecasting, and reinforcement learning. Fab equipment sensors, Time-series foundation models, Reinforcement learning controller
Reinforcement learning controller Candidate control mechanism for optimizing process recipes and actions. Process-control layer
Engineer users Domain experts who query assistants, interpret diagnoses, and govern fab actions. RAG assistant, Knowledge graph, OES analyzer, Defect detector

Data flow

Manufacturing equipment emits second-by-second trace data plus event, maintenance, inspection, OES, and image data. Knowledge graphs and LLMs align inconsistent sensor and chamber naming, RAG-style assistants retrieve historical fixes and suggestions, multimodal models analyze text/images/tables/time-series signals, and control candidates such as reinforcement learning are explored only after sensing and forecasting are trustworthy enough.

3 supporting quotes
“look at it to have this all autonomous fab what you need is three basic component sensing analysis and control”transcript, stated
“equipment I would say the trace the chart I showed before that's the main part of the equipment control and then”transcript, stated
“right we can utilize knowledge grab and LM and to make the alignments automatically one person ER is okay we can handle it we can take over from”transcript, stated

Why this architecture

Samsung uses a layered multimodal architecture because fab control is not a single-text problem: it requires sensor traces, event logs, maintenance history, images, spectroscopy, wafer context, and domain knowledge. Knowledge graphs and RAG help make messy engineering knowledge usable now, while time-series models and RL are explored cautiously because control requires high accuracy at critical transitions.

3 supporting quotes
“there are many different times the types of the data sources all of them needed and we need to have the foundation model”transcript, stated
“base so all of them all of this needs to be Network connected using the knowledge graph and so on and what is our goal is”transcript, stated
“foundation model times they don't work I don't want to say that it's not good enough to use for control yet I guess”transcript, stated

Models used: LLMs · RAG systems · multimodal foundation models · time-series foundation models · PatchTST · TimeLLM · TimeGPT · reinforcement learning

Scale

Alternatives considered (roads not taken)

Manual step/window statistics and domain-expert configuration

Rejected because: It requires heavy manual expertise and cannot scale across all signals and steps.

“bit different and in order to this what you need you need to have all the domain expertise knowledge experience as of”transcript, stated
“today or yesterday a lot of manual efforts were needed all of this can be reduced and simplified and further enhance using llm ji and so on that will”transcript, stated

Strict human-enforced sensor naming discipline

Rejected because: Even rare naming mistakes create huge accumulated alignment work across chambers and process steps.

“before we utilize a lot of training to Engineers when you name it please follow these rules if you don't follow you will”transcript, stated
“make okay I all right okay we tend to make errors let's say you are 99% time is accurate and you miss only 1% error then imagine that there are 100”transcript, stated

Use time-series foundation models directly for live control

Rejected because: The models are not yet accurate enough at microsecond/critical transition behavior for control.

“they never used this level of the micr second Data before so it's understandable even with the fine training pre-training probably not good enough”transcript, stated

Patterns

rag-retrieval (knowledge)

The engineering assistant retrieves historical error context and suggestions from manufacturing knowledge sources.

“the engineer just prompting I got error ABC what should I do or what happened before then engines LL gave you the answer what happened before and give you suggestions”transcript, stated

tool-use-orchestration (manufacturing)

The system orchestrates sensor traces, event histories, metrology, images, and knowledge graphs rather than a single data source.

“we have a lot of information process and Equipment operation and analytics is the different type of the knowledge and different type of resources”transcript, stated

data-quality-loop (data)

Knowledge-graph alignment repairs inconsistent sensor naming instead of relying only on perfect human data entry.

“we can utilize knowledge grab and LM and to make the alignments automatically one person ER is okay we can handle it”transcript, stated

fine-tuning-adaptation (modeling)

Samsung is exploring semiconductor-specific training/fine-tuning for foundation models that have not seen industrial time-series data.

“even with the fine training pre-training probably not good enough we are collab we trying to collaborate”transcript, implied

human-in-the-loop-gate (operations)

The autonomous-fab framing explicitly augments engineers rather than removing them from control decisions.

“it's not about get getting rid of the people Engineers it is more making them more powerful”transcript, stated

Tradeoffs

Use AI to augment fab engineers

Chose autonomous-fab assistance with humans behind the scenes over replacing process engineers outright.

Rationale: The stated goal is to make engineers more powerful while freeing them from manual knobs and repetitive analysis.

“not much human imar needed but actually is the behind the scene people can do more stuff rather than just replacing the knobs”transcript, stated

Adopt knowledge graphs for alignment

Chose automatic relationship-based alignment over manual naming-rule enforcement alone.

Rationale: A one-percent naming error becomes large across many chambers and steps.

“if you accumulate all of them they're huge so we have to do all this manually this very huge nuisance task”transcript, stated

Gate control uses until prediction quality improves

Chose diagnosis/forecasting exploration before live process control over premature closed-loop control with current time-series models.

Rationale: Control requires accurate forecasts in the critical windows where current models lag.

“they don't work I don't want to say that it's not good enough to use for control yet”transcript, stated

Gotchas (what bit them)

Second-by-second trace signals are too large and complex for manual monitoring.

Root cause: Even a small etch recipe emits many sensor readings across windows and steps.

Resolution: Samsung combines summarization/windowing today with multimodal and time-series models for richer analysis.

“even just only two step is very complicated to monitor all these signals every second's data is too much and huge”transcript, stated

Sensor names are not consistently aligned across chambers and tools.

Root cause: Humans make small naming errors and different perspectives need different relationships.

Resolution: Knowledge graphs and LLMs align equivalent sensors automatically.

“chamber a sensor a is behaving correctly chamber B same sensor a but they name it differently”transcript, stated
“we can utilize knowledge grab and LM and to make the alignments automatically”transcript, stated

Time-series foundation models are not yet control-ready.

Root cause: Industrial microsecond-level process-control data differs from what general time-series models have seen.

Resolution: Samsung treats them as an active collaboration and research area before using them for control.

“it's not good enough to use for control yet I guess they never used this level of the micr second Data before”transcript, stated

Manufacturing data cannot simply be shared externally for model development.

Root cause: Fab data is sensitive and every fab/vendor may use different formats.

Resolution: Samsung describes building its own cloud and emphasizes data standardization.

“unfortunately we cannot just share all the data to outside so what we do is we build our own cloud”transcript, stated

Evaluation

Samsung evaluates by comparing manufacturing usefulness: engineer-assistant answers, sensor-alignment quality, OES/defect detection usefulness, time-series forecast accuracy in critical windows, and whether models can support advanced process control.

Metrics: close to 1,000 process steps for 5nm logic · 80% yield profitability target · second-by-second trace data · 100 chambers and 1,000 steps compounding naming errors · microsecond-level time-series control requirements

3 supporting quotes
“if 1,000 steps are there it's really difficult ER to have all of them controlled optimized properly”transcript, stated
“yield at least 80% to be profitable”transcript, stated
“not good enough to use for control yet”transcript, stated

Outcomes

The transcript provides concrete operating context: roughly 1,000 steps for advanced logic, 80% yield requirements, second-by-second trace data, and data-standardization/privacy constraints.

3 supporting quotes
“this is actually the the engine we actually built this is translated version of this engine”transcript, stated
“this wraps up the my entire talk so again the key message is rag domain expert and multimodal and the foundation model and knowledge”transcript, stated
“with llm is way easier much better”transcript, stated