What data for this category looks like
Data for this category comes from wafer test maps, factory manufacturing execution systems (MES), bonding and molding equipment operation logs, ATE tester output results, X-ray/SAM inspection reports, and customer specification requirements. Daily maintenance documents include packaging process cards, bonding and molding process parameter tables, wafer incoming lot maps, test program version lists, yield statistics documents, and failure analysis reports. Data update frequency covers each production lot, each chip test cycle, and daily equipment operation statistics. Document fields include lot number, process parameter thresholds, test bin values, failure types, and more. They cover industrial parameter units such as voltage, time, and pressure.
What constraints these characteristics impose on deployment and upgrades
Since data sources include multiple types of industrial equipment logs, test results, and proprietary documents, deployment must support integration with multiple industrial interfaces. It must also adapt to offline deployment requirements where the intranet has no public network access. Data updates occur at high frequency and with fine granularity. Sufficient storage and cache resources must be configured to ensure response efficiency for real-time Q&A and data queries. Daily documents include proprietary format content such as wafer maps and test programs. Deployment must support uploading structured and semi-structured documents, and adapt to proprietary format parsing logic. During upgrades, original equipment integration configurations and knowledge base association relationships must be retained. This avoids interrupting real-time Q&A services for production links.
How to set configurations
These configurations are formulated based on FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
MONGODB_URI | mongodb://username:password@intranet database address:port/database name?authSource=admin | Stores equipment inspection logs, test data and knowledge base documents, must adapt to the authentication and address configuration of the packaging and testing factory's intranet database |
REDIS_URL | redis://:password@intranet cache address:port/0, cache instance memory configuration 16 GB | Caches frequently queried process parameters and equipment status, reduces database load, adapts to high-concurrency production scenarios |
DB_MAX_LINK | 20–30 | Limits database connection count, adapts to the intranet concurrent access scale of packaging and testing factories, avoids exhausting database resources |
STORAGE_S3_ENDPOINT | intranet object storage address:port | Stores large-volume documents such as wafer maps and failure analysis reports, adapts to deployment environments with no public network access in the intranet |
ROOT_KEY | Custom string with complexity ≥12 characters | Configures system administrator access keys, ensures access security for intranet deployments |
FE_DOMAIN | Packaging and testing factory intranet domain name or local IP:port | Specifies front-end access address, adapts to intranet usage scenarios |
Three common configuration errors
- Phenomenon: After selecting a specified model version on the front end, the actual call still uses the old model version. Cause: The model configuration parameters in the environment variables were not updated synchronously, or the configuration items were not correctly associated with the Q&A process.
- Phenomenon: After intranet offline deployment, the associated API service restarts continuously, and the log prompts a connection failure. Cause: Correct intranet database and cache addresses were not configured, or network policies restrict port access between services.
- Phenomenon: An embedding failure error occurs when uploading packaging process cards or wafer map documents. Cause: The proprietary format in the document was not adapted, or file reading failed due to incorrect storage configuration parameters.
How to confirm the configuration is complete
- Log in to the system backend, check the
MONGODB_URIconfiguration item, confirm it matches the intranet database address. - Upload a small packaging process card document, verify that the file upload and parsing process has no errors.
- Initiate a test Q&A related to equipment inspection, confirm that the response logic meets expectations, and the called model version matches the configured one.
- Check the connection status of
REDIS_URL, confirm that the cache service is running normally through the system monitoring tool.
The values provided are common starting points and should be evaluated against the reader's own samples.