What Data for This Category Looks Like
Data sources for this category include approved formulation processes, MES electronic batch records, equipment and environment monitoring data, LIMS systems, and quality management systems. Daily documents include master production files, batch production records, cleaning records, inspection records, deviation CAPA change documents, and batch release review forms. Data updates trigger with each batch production run, execution of key process steps, and progress of monitoring plans. Document fields include material batch numbers, process parameters, test results, deviation records, and other relevant items. Units include weight, temperature, time, batch numbers, and similar metrics.
Constraints Imposed by These Characteristics During Deployment and Upgrade
Data for this category links to multiple production and quality management systems. During deployment, configure cross-system data pull permissions to ensure data source compliance. Frequent batch-by-batch and step-by-step updates require storage and retrieval components to support stable concurrent writes and queries. Strict data integrity requirements under GMP mandate reliable persistent storage during deployment to prevent data loss. Complex document structures and dedicated fields require retrieval configurations to match business document hierarchies and field rules. This avoids retrieval results that deviate from process and standard content.
How to Configure Settings
| Configuration Item | Recommended Setting | Rationale for This Setting |
|---|---|---|
DB_MAX_LINK | 10–15 concurrent connections | Matches the concurrent demand for high-frequency data pulls across multiple systems, prevents connection exhaustion from impacting retrieval efficiency |
REDIS_URL | Local deployment instance, memory configuration of 8 GB or higher | Supports high-frequency session caching and retrieval result caching, adapts to the demand for fast batch record queries |
STORAGE_S3_ENDPOINT | Compliant cloud storage endpoint or local persistent storage address | Meets GMP requirements for data persistence and traceability, ensures secure storage of production records |
PG_URL | Read-only database address linked to the enterprise quality management system | Pulls approved process specifications and standard data, avoids write operations interfering with production system operations |
ROOT_KEY | Configured as an internal network access exclusive key | Restricts management backend access to the internal networks of production and quality departments, complies with data access compliance requirements |
Three Common Misconfigurations
- Issue: After upgrading to FastGPT v4.17.0, all configuration settings for self-built process specification Q&A applications are lost. Cause: The persistent database storage volume was not mounted during the upgrade, causing application metadata to be overwritten and cleared.
- Issue: No code execution tool connection configuration option appears in the tool call configuration interface. Cause:
ROOT_KEYpermissions were not configured correctly, or supporting dependent services for the code execution tool were not enabled. - Issue: Timeout errors occur when retrieving batch production records, and complete process parameters cannot be obtained. Cause: The cache instance associated with
REDIS_URLhas insufficient memory configuration, which cannot support high-frequency retrieval result caching and queries.
How to Verify Correct Configuration
- Log in to the FastGPT management backend, view the database connection status panel, and confirm that the concurrent connection number configured for
DB_MAX_LINKmeets business pull requirements. - Initiate a test query, enter a question related to process specifications, and verify that retrieval results include specified document types such as master production files and batch records.
- Perform a version upgrade operation, verify that self-built application configurations are not cleared, and confirm that storage volume mounting configuration is correct.
- Check the tool call configuration interface, confirm that the code execution tool connection option is displayed, and verify that
ROOT_KEYpermission configuration is effective.
The values provided are common starting points and should be evaluated against the reader's own samples.