What the data for this category looks like
The daily documents for this category include sales orders, master production schedules, material requirement plans, weekly and daily production schedules, work orders, material shortage lists, and delivery change orders. Data typically comes from ERP orders and inventory, BOMs and process routes, equipment capacity, staff shifts, work-in-progress, and supplier deliveries. Updates occur daily, weekly, or when orders are created or exceptions arise. Core processing steps include decomposing orders into work orders and processes, scheduling under equipment and material constraints, handling emergency order additions and exception rescheduling, and covering all products and processes.
What constraints these characteristics bring to the deployment and upgrade phase
Multi-source heterogeneous data sources require adaptive parameters for multi-system integration to be configured during deployment, to avoid data synchronization gaps. Non-fixed update frequencies require real-time incremental synchronization configuration logic to be retained during upgrades, to meet fast rescheduling needs for emergency scenarios such as emergency order additions or equipment failures. A large volume of structured and unstructured business documents requires storage and index configurations to match the read/write performance of large files, to prevent scheduling tasks from being interrupted due to insufficient resources. Cross-process global data processing logic requires reasonable permission isolation rules to be configured during deployment, to avoid cross-leakage of scheduling data between different workshops.
How to set the configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
MONGODB_URI | mongodb://username:password@host:port/production_plan?authSource=admin | Stores unstructured documents such as work orders and production schedules, and historical scheduling data; matches the database address format used for enterprise ERP integration |
PG_URL | postgresql://user:pass@host:5432/prod_bom?sslmode=require | Stores structured business data such as BOMs and process routes; PostgreSQL supports complex associated query requirements |
REDIS_URL | redis://:password@host:6379/0 | Caches real-time equipment capacity and staff shift data; supports fast reading for high-frequency scheduling recalculations |
DB_MAX_LINK | 20–30 | Matches concurrent request volumes from multiple data sources; prevents scheduling task interruptions caused by exhausted connections |
STORAGE_S3_ENDPOINT | Configured per the enterprise's internal object storage address | Stores large files such as work order attachments and process documents; meets file sharing requirements for production scenarios |
ROOT_KEY | Randomly generated 32-character string | Configures the system's initial administrator permissions; avoids security risks posed by default keys |
Three common mistakes
- When deploying locally, setting
MONGODB_URItolocalhost:27017results in failure to read cross-workshop historical scheduling data after startup. This occurs because local deployment only accesses the local database, and does not connect to the remote database instance synchronized with the enterprise ERP. - After upgrading to FastGPT v4.17.0, original account password verification fails. This occurs because the user authentication table from the original database was not retained during the upgrade, or the
ROOT_KEYin the configuration file was changed, causing abnormal permission verification logic. - After upgrading, the text content extraction function fails and returns empty results. This occurs because the storage permissions corresponding to
STORAGE_S3_ENDPOINTwere not reconfigured during the upgrade, preventing reading of process document content from work order attachments.
How to confirm configurations are correct
- A single scheduling simulation task is executed, the database connection status in system logs is reviewed, and no connection limit error is triggered.
- A test work order attachment is uploaded, and normal storage permissions are verified through the system's file preview function.
- The system interface is called to query the latest equipment capacity data, and the cache data update frequency is confirmed to meet business expectations.
- The system is logged into using the initial administrator account, the permission control logic is verified to work normally, and sub-accounts can be created and managed normally.
The values provided here are common starting points, and should be evaluated against individual deployment samples.