Inspection and Process Record Review for General Mechanical Equipment Assembly: Deployment and Upgrade

Daily documents for this category include assembly process cards, BOMs, torque records, gap adjustment records, commissioning reports, factory

What this category’s data looks like

Daily documents for this category include assembly process cards, BOMs, torque records, gap adjustment records, commissioning reports, factory inspection sheets, and packing lists. Data primarily comes from PLM/ERP systems, part inspection data, assembly tool collection terminals, test benches, MES systems, and customer technical agreements. Updates are performed per single device or single order. Each document includes clear numeric fields: torque values (unit N·m), gap values (unit mm), coaxiality (unit μm), and standardized approval workflow node information.

What constraints these characteristics impose on the deployment and upgrade phase

This category’s data is updated per single unit or single order, and includes a large number of structured numeric fields and standardized workflow nodes. Deployment must adapt to access formats for multi-source heterogeneous data. Upgrade processes must retain association relationships for historical assembly records, to avoid breaking mappings between BOMs and inspection records during version iterations. Since data sources include workshop collection terminals and test benches, deployment must reserve interface configuration space for industrial protocols. This ensures normal data synchronization from different devices to the system. The independence of single order data also requires the system to support order-level permission isolation, to prevent cross-order data confusion.

Configuration Settings

For FastGPT v4.17.0 deployment and upgrade, configure the following items based on the characteristics of this category:

Configuration ItemRecommended ValueRationale
DB_MAX_LINK20–30 connectionsAdapts to concurrent query demands for multiple documents per single order, prevents database connection exhaustion
MONGODB_URIFill in the address of the actual deployed MongoDB instance, add authentication parametersStores large volumes of unstructured assembly records and test reports, requires support for high-concurrency writes
PG_URLFill in the address of the actual deployed PostgreSQL instance, configure connection pool parametersStores structured BOM, torque record, and similar data, supports complex associated queries
REDIS_URLConfigure as a local cache instance address, set expiration time to 3600 secondsCaches frequently accessed assembly process card data, reduces database query pressure
FILE_TOKEN_KEYGenerate a random 32-character stringUsed to generate file access tokens, ensures access security for sensitive documents such as assembly records
STORAGE_S3_ENDPOINTFill in the address of the deployed object storage serviceStores large files up to 1000 MB such as test videos and scanned packing lists from assembly processes

Three Common Mistakes

  • Phenomenon: FastGPT image pull times out or fails. Cause: No domestic mirror acceleration source is configured, or the server network cannot access the official image repository.
  • Phenomenon: internal server error is displayed when importing a plugin. Cause: The data source connection parameters configured for the plugin do not match the actual deployed PG_URL or MONGODB_URI, or file permissions required by the plugin are not correctly configured.
  • Phenomenon: Unable to find the docker-compose.yml configuration file for the corresponding version. Cause: The official configuration file for the historical FastGPT version is not correctly obtained, or parameters in the configuration file do not match the current deployment environment.

How to Confirm Configuration is Complete

  • Run the docker ps command, confirm all FastGPT-related containers are in a running state.
  • Access the domain configured in FE_DOMAIN, log in to the system, attempt to import a BOM document, and verify that the upload and parsing process operates normally.
  • Call a system interface to query assembly records for a single order, confirm that returned data fields match fields exported from PLM/ERP systems.
  • Restart the FastGPT service, verify that administrator permissions function normally.

The values provided are common starting points, and should be evaluated against the reader’s own samples.