What data looks like for this category
This category of data covers documents such as packaging process cards, bonding and molding parameters, wafer incoming inspection maps, test program versions, yield reports, and failure analysis reports. Data sources include wafer test maps, MES systems, bonding and molding equipment, ATE testers, X-ray/SAM testing equipment, and customer specification requirements. Data updates follow production batches, single test results, and daily frequencies. Fields include batch identifiers, wafer numbers, test BIN values, yield parameters, equipment operating parameters, and more. These involve physical and engineering units such as wafer size, test voltage, and packaging thickness.
What constraints these characteristics impose on HTTP interfaces and external systems
Multi-source heterogeneous data sources for this category require HTTP interfaces to support pulling data from multiple systems. The interfaces must be compatible with differences in field formats across different devices and systems, and complete unified mapping. The high-frequency update rhythm requires interface call frequency to match the pace of production batches, single test, and daily updates. This avoids data lag or redundant requests. The complex document structure and field requirements require interface request parameters to carry precise identifiers such as batch number, wafer number, and test program version. This ensures pulled data matches the corresponding production batch. Bids must align with customer specifications, so interfaces must support pulling the latest customer-specified fields. This prevents document errors caused by parameter mismatches.
How to set configurations
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
Authorization | Bearer ${API key exclusive to semiconductor packaging and testing factories} | Validates interface call legitimacy, and matches the authentication standards for interfaces provided by packaging and testing factories |
variables | ["batchNumber", "waferLotId", "testProgramVersion"] | Carries core identification parameters for semiconductor packaging and testing, ensures pulled data matches corresponding production and wafer batches, and supports precise alignment for bid documents |
responseData | Only return packaging process card, yield report, and customer specification fields | Filters redundant data, reduces interface transmission load, and adapts to the field requirements of bid documents |
| Interface timeout period | 600 seconds | Pulling semiconductor packaging and testing data involves synchronous queries across multiple devices, so sufficient response time must be reserved |
| Request retry count | 3 times | Addresses temporary response fluctuations from ATE testers and X-ray equipment, and ensures stable data pulling |
| Maximum response data transfer size | 500 MB | Yield reports and wafer test map data for semiconductor packaging and testing have large volumes, so transfer size must be limited to avoid timeouts |
Three common mistakes
- Phenomenon: The interface returns a
401 Unauthorizedstatus code, and production data cannot be pulled. Cause: TheAuthorizationparameter is not configured correctly, and an expired or unauthorized API key is used. - Phenomenon: The
responseDatafield is empty after calling the interface, and yield data for the corresponding batch is not obtained. Cause: Correct batchNumber or waferLotId is not passed invariables, so the interface cannot match data for the corresponding production batch. - Phenomenon: A third-party API request times out after the workflow starts, causing bid document generation to interrupt. Cause: A reasonable interface timeout period is not set, and the response duration of multi-device synchronous data pulling for semiconductor packaging and testing exceeds the preset threshold.
How to confirm the configuration is correct
- Call the configured HTTP interface, check if the
Authorizationparameter passes the interface permission check, and return a 200 OK status code. - Pass a test batchNumber in
variables, check ifresponseDatareturns packaging process card and yield report fields for the corresponding batch. - Simulate high-frequency calls for production batches, verify that the interface timeout period and retry count configuration can handle temporary response fluctuations.
- Trigger the workflow to call the interface in the FastGPT v4.17.0 workflow editor, confirm that the response result can be correctly assigned to workflow variables.
The values provided here are common starting points and should be measured against the reader's own samples.