What the data for this category looks like
Data sources cover engineering orders, sand, gravel, cement admixture inspection records, aggregate moisture content measurement data, real-time mixing plant control system data, and laboratory test reports. Daily processed documents include mix proportion notices, opening identification records, production and delivery slips, raw material inspection sheets, test block records, and strength reports. Data updates follow this schedule: production records generated per vehicle, inspection completed per batch of raw materials, and daily summary statistics. Single records include fields such as raw material mix ratio, transportation duration, slump, and test block strength.
What constraints these characteristics impose on the deployment and upgrade phase
High-frequency vehicle-level and batch-level data updates require configuring sufficient database connection pools to avoid write blocking. Multi-type document parsing and storage needs demand adapting parsing rules for specialized document formats and large-capacity storage configurations. Mixed access of real-time control system data and offline laboratory data requires configuration items that support multi-source data synchronization. Error consequences involve project shutdowns and quality responsibilities, so strict permission control for core configurations is required to prevent data anomalies from misoperations. Daily summary statistics need stable storage and query capabilities to ensure timely quality audits.
How to set configurations
This configuration applies to FastGPT v4.17.0. Specific parameters are listed below:
| Config Item | Suggested Value | Rationale |
|---|---|---|
DB_MAX_LINK | 20–30 connections | Adapt to high-frequency data writes per vehicle and per batch of raw materials, avoid database connection blocking |
REDIS_URL | Local cluster address with access password | Support high-frequency session caching and real-time data synchronization, adapt to vehicle-level update frequency |
STORAGE_S3_ENDPOINT | Storage node address with capacity over 1000 MB | Store multi-type documents such as test block records and strength reports, meet large-capacity storage requirements |
MONGODB_URI | Cluster connection address with 2–3 shards | Store structured data classified by daily and batch, reduce query pressure on a single database |
FILE_TOKEN_KEY | 32-bit random string calibrated by actual measurement | Ensure access security for uploaded documents such as mix proportion notices, prevent unauthorized access |
ROOT_KEY | Complex key known only to deployment administrators | Restrict modification permissions for core configurations, avoid misoperations affecting production processes |
Three common misconfigurations
- Symptom: After upgrading, the system prompts that the account password does not match, and the management backend cannot be accessed. Cause: The
ROOT_KEYconfiguration was not migrated correctly during the upgrade, causing the identity verification key to not match the original system. - Symptom: After uploading a mix proportion notice, the parsing result lacks core fields such as aggregate moisture content and slump. Cause: Specialized document parsing rules were not configured during deployment, so the system cannot recognize the specialized document formats used in ready-mixed concrete production.
- Symptom: When deploying using the ocearbase version of compose.yml, the fastgpt container restarts continuously with no valid log output. Cause: The
REDIS_URLconfiguration is incorrect, causing the cache service connection to fail, and the container cannot complete initialization.
How to confirm the configuration is correct
- Log in to the system backend configuration page, verify that the
DB_MAX_LINKconfiguration value matches the preset 20–30 connections. - Upload a single raw material inspection sheet, confirm that the parsing result can extract inspection parameters for sand, gravel, and cement, with no required fields missing.
- Run the docker logs command to view the fastgpt container logs, with no error messages about database connection timeouts or identity verification failures.
- Use the
ROOT_KEYto generate a temporary access token, confirm that stored production and delivery slip documents can be accessed normally.
The values listed here are common starting points and should be evaluated against the reader's own samples.