What Data This Category Covers
This category covers process and inspection records across the entire semiconductor packaging flow. Data sources include wafer test maps, MES systems, bonding and molding equipment, ATE test machines, X-ray/SAM inspection equipment, and customer specification requirements. Daily documents include packaging process cards, bonding and molding parameter sheets, incoming wafer maps, test program version files, yield reports, and failure analysis reports. Data update frequency aligns with production batches, single-chip testing, and daily production summary processes. Individual records contain fields such as wafer traceability codes, test parameters, equipment operation logs, and failure classification identifiers. Units include industrial standard measurement units such as voltage, operating time, and pixel dimensions.
What Constraints Do These Characteristics Impose on HTTP Interfaces and External Systems
Data sources for this category are scattered and update frequencies vary widely. HTTP interfaces must support concurrent calls from multiple data sources and batch data synchronization. Multiple types of process documents and inspection records require interfaces to support parameter transmission and field validation rules for different formats. Individual records contain multi-dimensional fields such as wafer traceability codes and test parameters, requiring interfaces to support long parameter transmission and precise field matching. Errors in the production link directly affect product quality. Interfaces must include basic field validity checks to prevent invalid data from entering the system. Interfaces must adapt to the rhythm of synchronization triggered by production batch completion nodes, to avoid high-frequency invalid calls consuming system resources.
How to Configure
This configuration guide is based on FastGPT v4.17.0.
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
| Request header configuration | Carry the Authorization parameter, with a pre-configured Bearer token as the value | Adapt to the identity verification requirements of external industrial systems and ensure the security of interface calls |
| Variable transfer settings | Enable the variables parameter, pass fields such as batch ID, wafer traceability code, and test program version, with a value length not exceeding 2000 characters | Match the batch traceability requirements of semiconductor packaging and testing, ensure that interface calls carry accurate business identifiers |
| Response data processing | Configure the responseData field filtering rule to retain core fields such as bin codes, failure types, and equipment operation parameters | Focus on valid inspection and process records, reduce redundant data transmission, and adapt to the lightweight receiving requirements of production systems |
| Timeout setting | Set to 30–60 seconds | Adapt to the data return cycles of ATE test machines and X-ray equipment, avoid call failures caused by delayed device responses |
| Retry count configuration | Set to 2 retries, with a 5-second retry interval | Respond to temporary network fluctuations or brief device freezes, ensuring the success rate of data synchronization |
| Batch synchronization trigger | Trigger upon completion of production batch nodes | Match the batch-based update rhythm of this category's data, avoid high-frequency invalid calls |
Three Common Misconfigurations
- After a workflow is triggered via an HTTP interface, only a single call result is returned, and preset context is not retained. Cause: No batch identifier or session identifier associated with the context is passed in the
variablesparameter, causing the workflow to fail to associate historical data. - The interface returns a 401 Unauthorized status code, and identity verification cannot be completed. Cause: The
Authorizationparameter is not configured correctly, or the used token format does not meet the requirements of the external system. - Synchronized inspection record data has missing fields and cannot be used for batch yield statistics. Cause: Required core business fields are not specified in the
responseDataconfiguration, causing key data to be lost after filtering.
How to Verify Successful Configuration
- Test calls are initiated, and the request header is checked for the presence of the
Authorizationparameter. - The
variablesparameter containing a test batch ID is passed, and the workflow is verified to load the historical configuration information for that batch. - The
responseDatareturned by the interface is reviewed, and confirmation is made that core inspection fields such as preset bin codes and failure types are included. - A single call timeout is simulated, and confirmation is made that the interface completes data synchronization normally after triggering the retry mechanism.
The values provided here are common starting points and should be measured against the reader's own samples.