What this category of data looks like
Data for this category mainly comes from wafer test maps, factory manufacturing execution systems (MES), bonding and molding equipment, ATE test machines, X-ray/SAM inspection equipment, and customer specification documents. Daily maintenance documentation includes packaging process cards, bonding and molding parameter tables, incoming wafer maps, test program version files, yield reports, and failure analysis reports. Data update frequency synchronizes with production batches, single-chip test results, and daily equipment operating status. Fields include wafer batch numbers, equipment operating parameters, test bin values, failure types, and more. There are no unified fixed units; values vary based on document type and device interface definitions.
What constraints these characteristics impose on HTTP interfaces and external systems
Dispersed data sources and high update frequencies require HTTP interfaces to support multi-source data synchronous pulling, and need to adapt to interface formats of different devices and systems. Diverse daily document types, including structured parameter tables and unstructured inspection maps, require interfaces to support multi-format data transmission. High-frequency updates from single-chip tests require interfaces to have low-latency response capabilities to avoid production process stagnation. Large differences in field definitions across different devices require dynamic parameters to be passed via variables to adapt to different data sources, while supporting custom mapping of responseData to unify data structures. Batch transmission requirements for failure analysis reports and yield reports require interfaces to support segmented upload configurations.
How to configure
The following configurations are based on FastGPT v4.17.0, adapted to the equipment inspection and maintenance Q&A scenario for this use case:
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
Authorization | Bearer ${token}, validity period set to 24 hours | Token validity periods for packaging and testing equipment and MES systems typically match production shift lengths, avoiding frequent refreshes that disrupt real-time inspection |
variables | Pass three dynamic parameters: wafer batch number, equipment ID, test program version | Data for this category must be bound to batch and equipment information to ensure Q&A matches documentation for the corresponding production link |
responseData | Map to three fields: equipment status, fault code, associated document ID | Daily maintenance Q&A requires quick association with historical parameters and failure reports for the corresponding equipment; unified field formats facilitate calls by downstream systems |
| Max recall per request | Top 8 results | Fault types for packaging and testing equipment are concentrated in a small number of links such as bonding and molding; too many recall results will interfere with maintenance personnel's judgment |
| Timeout period | 30–60 seconds | Real-time requirements for equipment inspection; excessively long timeouts will cause production process stagnation. Adjust the interval based on actual measurements |
Three common misconfigurations
- The phenomenon is an interface error returning 403 Forbidden: the token is not authorized to use the model. The cause is that model permissions corresponding to the packaging and testing scenario are not bound to the current token, or the token validity period is shorter than the production shift length, causing expiration.
- The phenomenon is that the document association field returned by the interface is empty. The cause is that the correct wafer batch number or equipment ID was not passed via
variables, making it impossible to match document data for the corresponding production batch. - The phenomenon is that the fault handling result returned after the interface call does not match the actual equipment parameters. The cause is that the field mapping for
responseDatawas not configured, and raw interface data was used directly, resulting in field formats incompatible with the maintenance Q&A system.
How to confirm the configuration is correct
- Call the test interface, pass a known wafer batch number and equipment ID, and check if the returned results include the corresponding packaging process card and fault handling steps.
- Simulate a token expiration scenario to verify if the interface returns the corresponding permission error, confirming that the token validity period configuration takes effect.
- Compare interface return data from different devices, and check if the fields mapped via
responseDataare unified to adapt to downstream system calls. - Initiate high-frequency consecutive calls, verify if the interface response time meets production real-time requirements, and adjust the timeout configuration as needed.
The values provided are common starting points and should be measured against the reader's own samples.