What the data for this category looks like
Data for this category primarily originates from ERP orders and inventory, bills of materials (BOMs) and process routes, equipment capacity, staff shifts, work-in-progress, and supplier arrivals. Daily processed documents include sales orders, master production plans, material requirements plans, weekly scheduling sheets, work orders, material shortage lists, and delivery change notices. Fields covered include order numbers, material codes, capacity values, shift durations, work-in-progress quantities, and more. Units include pieces, hours, days, and others. Data update frequencies include daily, weekly, and real-time updates when orders or exceptions occur.
Constraints These Characteristics Impose on Deployment and Upgrade
Since data sources cover multiple internal enterprise systems, deployment must adapt to multi-data source connection configurations to avoid cross-system data synchronization failures. Document structures are diverse, with significant field differences between formats. Upgrades require reserving flexible adjustment space for parsing rules to accommodate scheduling-related documents in different formats. Data updates have no fixed cycle and may include sudden exceptions. Deployment must configure dynamically adjustable synchronization trigger mechanisms to ensure timely processing of abnormal data. Additionally, data for this category is directly linked to production progress. Deployment and upgrade processes must maintain the integrity of data verification logic to prevent erroneous data from entering the scheduling link.
How to Set Configurations
| Configuration Item | Recommended Value | Basis for This Setting |
|---|---|---|
DB_MAX_LINK | 100–150 connections | This category has large data volume and frequent updates. A sufficient connection pool can support concurrent work order and scheduling data query requests |
MONGODB_URI | Cluster address with read-write separation configuration | A large amount of historical work order and work-in-progress data needs to be stored. Read-write separation can reduce latency for high-frequency queries |
REDIS_URL | Cluster address with RDB persistence configuration | Used to cache daily updated material requirements and equipment capacity data, reducing the overhead of repeated ERP queries |
FE_DOMAIN | Secondary domain name registered for internal enterprise use | Adapt to the access permissions of shop scheduling terminals to ensure normal interface calls from internal systems |
FILE_TOKEN_KEY | 32-bit randomly generated encrypted string | Protects the transmission security of uploaded scheduling documents and work order data to prevent unauthorized access |
STORAGE_S3_ENDPOINT | Access address of the enterprise internal storage service | Used to store all types of uploaded scheduling-related documents to ensure normal reading and calling of data |
Three Common Misconfigurations
- Symptom: Frequent timeout errors occur when processing scheduling data after deployment. Cause: The
DB_MAX_LINKconfiguration was not adjusted for the category's high-concurrency data volume, leading to database connection exhaustion. - Symptom: A 500 error is returned when uploading documents such as weekly scheduling sheets or work orders. Cause:
STORAGE_S3_ENDPOINTor the associated storage service access permissions were not configured correctly, leading to failed document uploads. - Symptom: Scheduling-related data cannot be synchronized after connecting to enterprise WeChat. Cause: Interface requests were not allowed through the domain name whitelist configured via
FE_DOMAIN, leading to cross-domain access being blocked.
How to Verify Successful Configuration
- Log in to the database monitoring panel in the FastGPT v4.17.0 backend, and confirm that the active connection count does not exceed the
DB_MAX_LINKconfigured value. - Upload a test sales order document, and verify that it parses correctly and the data import process completes successfully.
- Access the frontend address bound to
FE_DOMAIN, and confirm that the scheduling data display page loads without issues. - Trigger a material shortage list synchronization task, and confirm that no corresponding error logs are generated by the system.
The values provided are common starting points and should be evaluated against the reader's own samples.