This page applies to FastGPT v4.17.0.
What the data for this category looks like
Data for this category typically comes from ERP/WMS systems, barcode or RFID identification devices, procurement and work order data, storage location management data, AGV or conveyor systems, and weighing equipment. Daily documents include receiving slips, putaway slips, material picking and return slips, inventory transfer slips, inventory count sheets, lot ledgers, first-in first-out (FIFO) and expiration date records. Fields include material code, lot number, storage location number, inspection status, expiration date, quantity, and others. Data update frequencies are divided into real-time (such as AGV position, real-time weighing data), daily (such as storage location changes, material picking and return records), and monthly (such as monthly inventory data). The data must be linked across multiple dimensions including production work orders and purchase orders to form a complete material flow chain.
What constraints do these characteristics impose during deployment and upgrade
Data sources for this category are scattered, and update frequencies vary significantly. During deployment, adaptation to multiple types of data sources is required, including structured data from ERP/WMS and real-time stream data from barcode and RFID devices. Document fields are numerous, and association relationships are complex. During deployment, fields must be accurately matched to ensure the accuracy of inspection and audit, avoiding audit errors caused by field misalignment. The synchronization frequency of real-time data must be adjusted based on business scenarios. For example, AGV position data requires real-time synchronization, while monthly inventory data can be synchronized daily, to avoid audit delays caused by data lag. Errors in this category directly affect production processes. During deployment, data verification links must be configured to prevent issues such as wrong materials, use of expired materials, and production line downtime due to material shortages. In addition, cross-process lot flow management requires deployment of link configurations to ensure complete traceability chains and avoid traceability interruptions.
How to Set Configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
DB_MAX_LINK | 10–20 | Adapt to concurrent read/write requirements for warehousing and lot data, avoid exhausting database connections |
MONGODB_URI | Follow the data source address exported from ERP/WMS | Persistent storage for documents including lot ledgers and inventory count sheets |
REDIS_URL | Local Redis service address or cloud Redis instance address | Cache real-time storage location and AGV status data, reduce database query pressure |
FE_DOMAIN | Public network domain name or internal network IP of the deployment node | Allow front-end pages to access APIs, enable visual audit of inspection records |
FILE_TOKEN_KEY | Random string generated through actual testing | Encrypt access permissions for uploaded documents including receiving slips and inventory count sheets |
Three Common Configuration Errors
- Service enters infinite restart loop: The
DB_MAX_LINKconfiguration value is lower than actual concurrent connection requirements, database connection pool is exhausted, causing the service to restart repeatedly. - Knowledge base data fails to sync:
MONGODB_URIis configured incorrectly, unable to connect to the deployed database instance, preventing documents from syncing to the knowledge base. - Interface shows quota-related error messages:
REDIS_URLis not configured, caching mechanism is not enabled, request rate limiting triggers an error.
How to Confirm Successful Configuration
- Check database connection logs, confirm that the number of connections for
DB_MAX_LINKfalls within the configured range, with no connection failures. - Upload a receiving slip document, confirm that
FILE_TOKEN_KEYverification passes, and the file can be accessed normally. - Access the front-end address corresponding to
FE_DOMAIN, confirm that the inspection record audit page loads normally. - Trigger a real-time data sync, confirm that lot ledger data syncs successfully.
The values provided here are common starting points, and should be evaluated against samples relevant to the actual deployment context.