What Data for This Category Looks Like
Data for this category primarily comes from order and inventory data, bill of materials (BOM), process routes, equipment capacity ledgers, staff shift schedules, work-in-progress inventory, and supplier delivery records from the enterprise ERP system. Daily maintained documents include sales orders, master production schedules, material requirement plans, weekly and daily production schedules, production work orders, material shortage lists, delivery change notices, and others. Data update frequency is typically daily, weekly, or triggered when order adjustments or exceptions occur. Data fields include order numbers, process names, equipment numbers, capacity thresholds, delivery requirements, etc., and corresponding units must be matched based on specific business scenarios.
Constraints Imposed by These Characteristics During Deployment and Upgrade
Data sources for this category are scattered, and update frequencies fluctuate. The deployment phase must support rapid access to multiple data source types to avoid scheduling data loss caused by incorrect data source configuration. Daily documents vary widely, including structured tables and unstructured process documents. Deployment must adapt to parsing and storage requirements for different document formats. Because data is linked across processes and equipment, sufficient computing resources must be reserved during deployment to support complex scheduling logic calculations. During upgrades, data migration consistency must be maintained to prevent loss of core data such as work orders and production schedules during version updates. Tender document and quotation preparation also requires linking large volumes of attached data, so deployment must configure a reliable storage link to ensure normal access to attachments. This guide is written for FastGPT v4.17.0.
How to Set Configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
DB_MAX_LINK | 10–15 | Meets the demand for high-frequency access to scheduling data across multiple departments, and prevents database connection exhaustion |
MONGODB_URI | Fill in the standard connection string according to the production environment | Stores core business data such as work orders, production schedules, and delivery change notices |
FE_DOMAIN | Fill in the publicly accessible frontend domain name | Ensures normal connectivity of tender document preview and sharing links |
STORAGE_S3_ENDPOINT | Fill in the enterprise object storage access address | Stores large attached files required for tendering such as BOM lists and process routes |
REDIS_URL | Configure the enterprise-level cache address | Caches frequently accessed equipment capacity and staff shift data to reduce database pressure |
Three Common Misconfigurations
- The frontend page loads continuously with a spinning indicator and fails to show normal content. The cause is that the
FE_DOMAINconfiguration does not match the actual deployed public domain name, breaking the frontend static resource loading link. - Containers fail to start normally after running the
docker-compose upcommand. The cause is that the downloadeddocker-compose.ymlhas not replaced the default local database configuration, andPG_URLhas not been correctly filled to point to the enterprise-level database instance, leading to database connection failure. - Attached files cannot display properly in the generated tender document. The cause is that the
STORAGE_S3_ENDPOINTconfiguration is incorrect, preventing connection to the enterprise object storage and making attached files such as BOM lists and process routes unavailable for retrieval.
How to Verify Successful Configuration
- Access the configured
FE_DOMAINand check that the frontend page loads normally, with no spinning indicator or error messages. - Run the
docker pscommand to confirm that all FastGPT-related containers are in a running state, with no abnormal exits or restart logs. - Upload a test work order document and confirm that it is successfully stored in the database associated with
MONGODB_URI, with no storage failure alerts. - Call the test interface to generate a tender document with attachments, and confirm that the attachments load and display normally, with no missing content or errors.
The values provided here are common starting points and should be measured against the reader's own samples.