What the data for this category looks like
Core data for the general mechanical equipment assembly category comes from PLM, ERP, parts inspection systems, assembly tool collection terminals, test benches, MES, and customer technical agreements. Data updates trigger when each device order reaches its completion node. Included data covers assembly process cards, multi-level BOMs, torque records, gap adjustment records, commissioning reports, factory inspection sheets, and packing lists. Data fields include material codes, torque values (unit N·m), gap tolerances (unit mm), coaxiality requirements (unit μm), and additional relevant fields. The volume of data linked to a single tender fluctuates based on order complexity.
What constraints these characteristics impose during deployment and upgrade
Generating multiple tender documents in parallel for this category requires deployments to support high-concurrency calls to multiple data sources. The dynamic data update characteristic tied to orders means upgrade processes cannot interrupt running tasks, and must support gray releases. The coexistence of multiple document types and structured data requires configuring storage and indexing rules adapted to different data formats, to avoid data read delays. Additionally, tender documents must strictly match the field requirements of customer technical agreements. Deployments must ensure data source permission configurations comply with internal data security standards.
How to set configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
DB_MAX_LINK | 100–200 | Each order for this category corresponds to multiple assembly documents and BOM data. A sufficient connection pool is required to support multiple users generating tender documents simultaneously under high concurrency |
MONGODB_URI | Configure according to the dataset address exported from PLM/ERP | Core BOM and process card data for the category is stored in the MongoDB instance of the PLM system. Direct connection is required to retrieve structured data |
REDIS_URL | Local 6379 port default configuration | High-frequency calls to customer technical agreements and historical tender templates need to be cached to reduce database query pressure |
STORAGE_S3_ENDPOINT | Internal enterprise object storage node address | Assembly documents and inspection records for this category have large file sizes, requiring unified storage and support for cross-node access |
FILE_TOKEN_KEY | Randomly generated 32-bit string | Temporary download links for tender documents need to be encrypted and stored to prevent unauthorized access to internal documents |
FE_DOMAIN | Secondary domain of the enterprise’s official website tender system | Generated tender document links must be bound to internal business domains to comply with internal usage standards |
Three common mistakes
- Phenomenon: After upgrading to FastGPT v4.17.0, the
systemEnvrelated configuration items in config.json cannot be found, leading to failed retrieval of BOM data for tender documents. Cause: The configuration structure was adjusted in this version, and existing configurations were not migrated to the specified environment variable file. - Phenomenon: After automated deployment via Vercel, accessing the tender document generation page returns a 404 Not Found error. Cause:
FE_DOMAINand the backend service route binding were not configured correctly, and static resource and API interface paths did not match. - Phenomenon: In tender documents shared without login, the reference original text function cannot be disabled as configured. Cause: The access permissions for
FILE_TOKEN_KEYwere not set correctly, causing the file access token for the shared link to not be bound to the expected validity period and permission rules.
How to confirm configurations are correct
- Log in to the FastGPT backend, view the database connection monitoring panel, confirm that the configured value of
DB_MAX_LINKmatches the preset value, and there are no persistent connection timeout errors. - Upload a standard assembly process card to the system, verify that file upload, download, and preview functions work normally through the storage node corresponding to
STORAGE_S3_ENDPOINT. - Generate a test tender document, check that the retrieved BOM data fully matches the original data fields exported from the PLM system.
- Generate a shareable link without login, test whether the access permissions of the link comply with the preset configuration requirements for disabling original text viewing.
The values provided are common starting points and should be measured against the reader's own samples.