What this category's data looks like
Data for this category primarily comes from PLM/ERP, part inspection data, assembly tool collection, test benches, MES, and customer technical agreements. Updates occur once per device or per order. Daily documents include assembly process cards, multi-level BOMs, torque records, clearance adjustment records, commissioning reports, factory inspection sheets, and packing lists. Fields typically include device model, assembly parameters such as coaxiality and pre-tightening torque, inspection values, and customer technical requirements. Units include millimeters, newton-meters, pascals, and others.
What constraints do these characteristics impose during deployment and upgrade
Since data for this category is updated per device or order and includes multi-level BOMs and multi-dimensional assembly parameters, deployment must support batch ingestion and incremental synchronization of multi-source heterogeneous data. Configuration items for adapting PLM/ERP interfaces must be reserved. During upgrades, version associations of historical assembly documents must be retained to avoid losing exclusive process and abnormal records for individual devices due to version updates. Additionally, since document fields include custom technical parameters, custom field mapping must be supported to prevent generic templates from failing to meet the requirements of different customer technical agreements.
How to set configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
DB_MAX_LINK | 100–150 connections | This category has a large number of assembly documents and inspection records associated with a single order, so the database connection pool must support concurrent queries |
REDIS_URL | Local Redis instance connection address, timeout set to 60 seconds | Assembly process data for this category requires fast reading via cache, and the timeout setting must match the average time required for data queries |
MONGODB_URI | Standard connection address for local MongoDB instance | Abnormal reports and commissioning reports for this category are mostly stored as unstructured documents, and MongoDB adapts to the flexible storage needs of such data |
PG_URL | Connection address for local PostgreSQL instance | Structured data such as BOMs and torque records for this category is suitable for storage and efficient querying via a relational database |
FE_DOMAIN | Public or internal domain name of the deployment server, port 8080 | The frontend interface must properly load associated document resources such as assembly process cards to avoid cross-domain access failures |
STORAGE_S3_ENDPOINT | Local object storage service access address, maximum single file size 500 MB | Assembly tool collection data and test bench data for this category have large volume, so local storage access configuration must be supported |
FILE_TOKEN_KEY | 32-character random string, calibrated via actual testing | Access tokens for process document downloads and abnormal report viewing must be secured to prevent unauthorized access |
Three common misconfigurations
- After deployment or upgrade, the frontend interface displays in English, and the knowledge base has no Chinese category tags. The cause is that the localized environment variables associated with
FE_DOMAINwere not configured correctly, or the default language parameter was not set to Chinese. - Unable to call the locally deployed large model to perform semantic parsing of process documents. The cause is that the interface address of the locally deployed large model was not filled correctly in the configuration items, or the internal network access permission for the corresponding port was not enabled.
- After upgrading to FastGPT v4.17.0, the reference links for process documents cannot be downloaded normally. The cause is that the configuration value of
FILE_TOKEN_KEYis inconsistent with the old version, resulting in token verification failure.
How to confirm the configuration is valid
- Access the frontend address corresponding to
FE_DOMAIN, confirm that the interface language is Chinese, and that uploaded assembly process card documents can be loaded normally. - Test connecting to the database via
PG_URL, query the BOM data for a single device, and confirm that the returned results match the data exported from PLM/ERP. - Upload an abnormal report document, attempt to download it via the access link generated using
FILE_TOKEN_KEY, and confirm that the file content can be obtained normally. - Simulate a scenario where multiple users query assembly data simultaneously, confirm that there are no errors in the database connection pool, and that the
DB_MAX_LINKconfiguration adapts to the current concurrency requirements.
The values provided here are common starting points, and should be evaluated against the user's own samples.