What Data for This Category Looks Like
Data sources for this category include MES systems, equipment FDC modules, defect detection and metrology devices, wafer map files, process recipe libraries, and experimental datasets. Data updates occur per wafer lot transfer, real-time parameter reporting, and daily aggregate statistics. Daily documents include process flow cards, batch run records, equipment recipes, SPC trend charts, exception handling sheets, defect maps, and yield reports. Fields include wafer lot identifiers, nanoscale process parameter values, defect location coordinates, equipment runtime duration, and more. Common units are nanometers, milliseconds, and standardized batch number formats.
Constraints for HTTP Interfaces and External Systems Workflows
Multi-source heterogeneous data, high-frequency real-time updates, and strict parameter precision requirements create multiple constraints for HTTP interface and external system integration. Multiple cross-departmental data sources require integration with multiple external services, so unified authentication and request formats are necessary. Precise transmission of nanoscale process parameters and batch-level data requires no field truncation and matching request formats. Interface calls triggered by each wafer lot’s process nodes must adapt to event-driven request timing to avoid invalid polling. Large file transfers for exception handling sheets and defect maps need reasonable timeout and retry configurations to prevent transmission failures from disrupting batch progress.
Configuration Settings
This content is based on FastGPT v4.17.0.
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
Authorization | Bearer <API key assigned by the platform> | Complies with external service authentication specifications to prevent unauthorized requests from being blocked |
variables | {"waferLotId":"","processStep":""} filled with actual business parameters | Used to pass wafer lot ID and process node information, adapting to external system data parsing logic |
| Timeout duration | 30–60 seconds | Adapts to the transmission and processing time of large wafer maps and SPC charts |
| Retry count | 2–3 attempts | Addresses short-term network fluctuations or temporary unavailability of external services |
responseData | Extract business content under this field | Unifies interface return formats to facilitate subsequent business logic processing |
| Request trigger timing | Triggered upon completion of process node events | Matches the rhythm of wafer fabrication workflows to avoid invalid requests |
Three Common Configuration Mistakes
- Issue: Interface returns 401 Unauthorized status code. Cause:
Authorizationparameter is not configured correctly, or the key’s permissions do not cover the wafer fabrication-related interface scope. - Issue: Variable results returned in AI conversations show content overlap, with the output of the latter variable containing the full content of the previous one. Cause: The
variablesparameter is not reset before each request, leaving historical wafer lot data from prior batches in the context. - Issue: External service interfaces cannot be connected during local deployment. Cause: Correct external service address and port are not configured, or local network restrictions block outgoing requests.
How to Verify Correct Configuration
- Send a simulated request with test wafer lot ID and process node information, check if the external service can correctly receive and return corresponding data.
- Review interface call logs to confirm the
Authorizationparameter format is correct, and request headers and bodies have no format errors. - Trigger actual process node events, observe if interfaces are called as expected, with no duplicate or missing requests.
- Verify the response data extraction logic, confirm that only inspection results and record content are extracted from the
responseDatafield.
The values provided here are common starting points and should be measured against the reader's own samples.