What the Data for This Category Looks Like
Business data for semiconductor wafer fabrication scenarios covers multiple types of process-related documents. These include process flow cards, batch run records, equipment recipes, SPC charts, exception handling sheets, defect maps, and yield reports. Data primarily comes from MES systems, equipment FDC modules, defect detection and metrology equipment, wafer map files, process recipe libraries, and experimental data. Updates occur in real time alongside wafer batch progress and equipment operating status. Some batch reports update on a daily basis. Fields include nanoscale process parameters, batch numbers, defect coordinates, and more. Units cover micrometers, watts, and other semiconductor process-specific measurement standards.
Constraints Imposed on Citation Source and Traceability
Multi-source heterogeneous data sources require traceability processes to associate unique identifiers across different systems. This prevents cross-source data confusion. Long process chains and complex rework paths require traceability results to accurately match document fragments for corresponding processes. This prevents traceability drift. The coupling of nanoscale process parameters and cleanroom environments requires strict alignment of timestamps and batch information in traceability data. Misalignment can lead to process judgment deviations. Real-time updated batch data requires traceability interfaces to support low-latency queries. Delayed data can otherwise impact Q&A accuracy.
Configuration Settings
These configurations are adjusted for FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
quoteMaxToken | 800–1200 characters | Wafer manufacturing process documents contain long sections of parameters and process descriptions. This range covers core traceability content for a single process |
responseData | Enabled | Required to return exclusive fields such as batch numbers and equipment FDC parameters of citation fragments, supporting accurate traceability |
detail | Enabled | Required to display the original storage path of citation fragments, matching the document directory structure of MES systems and equipment logs |
| Single recall citation count | Top 3–5 entries | A single wafer batch can have hundreds of processes. Limiting recall count avoids context overload while covering core attribution basis |
| Citation matching threshold | 0.75–0.85 | Semiconductor process parameters have high precision requirements. This threshold filters low-relevance non-target process documents |
Three Common Misconfigurations
- Search matches multiple relevant documents but only returns one citation. This occurs when the
quoteMaxTokenparameter is misconfigured or the single recall citation count is set too low, resulting in truncation of valid traceability fragments. - A missing field error is returned after calling the citation traceability interface. This happens when the
responseDataparameter is not enabled, and required fields such as batch numbers and equipment parameters of original citations are not returned, preventing complete traceability. - Citation traceability results do not match process data for the target wafer batch. This is caused by failure to align timestamps and batch identifiers of citation fragments, leading to traceability drift to documents for non-target processes.
How to Verify Correct Configuration
- Upload a single wafer process flow card, initiate a Q&A related to process parameters, and check if the character count of citation fragments in the returned results falls within the preset range.
- Review the citation source list in the Q&A results, and confirm that exclusive business fields such as batch numbers and equipment FDC parameters are included.
- Adjust the single recall citation count to top 5 entries, initiate a cross-process yield attribution Q&A, and check that the number of returned citations matches the set value.
- Simulate an exception handling scenario, and verify that the storage path of citation results matches the document directory structure of the MES system.
The values provided here are common starting points and should be measured against the reader's own samples.