What the data for this category looks like
Core data for this category comes from design BOM, silicon steel sheet and insulating material ledgers, vacuum drying equipment logs, oil test reports, and high-voltage test records from the test station. Daily output documents include winding and core assembly records, vacuum drying records, insulating oil reports, partial discharge and withstand voltage test reports, and nameplate parameter tables. Data is updated per finished unit or per batch of raw materials. Document fields include rated capacity, insulation resistance, partial discharge peak value, test date, and others. Some fields use dedicated units: partial discharge magnitude uses pC, and insulating oil moisture content uses ppm.
What constraints these characteristics impose on the deployment and upgrade phase
This category’s data is updated per finished unit or per batch of raw materials, and includes multiple types of test documents in specialized formats. These factors create multiple constraints during deployment and upgrade. First, enable access to multi-source heterogeneous data, and enable quick associated entry of single or batch data. This meets full-process traceability requirements for a single product. Second, configure parsing rules for specialized documents such as insulating oil reports and partial discharge test reports. Retain field matching logic for dedicated units including partial discharge magnitude and insulating oil moisture content. Third, maintain compatibility with the storage structure of old-version single-unit data during upgrades. Avoid data association breaks, and ensure historical records can be queried normally.
How to set the configurations
This configuration is based on FastGPT v4.17.0, as detailed below:
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
DB_MAX_LINK | 150–250 items/second | Adapts to the concurrent query requirements of multi-dimensional test data for a single product, and prevents database connection overflow |
MONGODB_URI | mongodb://admin:securepass@db-host:27017/fastgpt?authSource=admin | Stores document-type data such as full-process assembly records and test reports for single products, and supports precise single-unit traceability queries |
REDIS_URL | redis://:redispass@redis-host:6379/1 | Caches frequently called insulating parameter standards and test threshold data, and controls query delay to within 100 milliseconds |
STORAGE_S3_ENDPOINT | https://s3-cn-north-1.example.com | Stores large-capacity high-voltage test raw data and insulating oil test reports, and ensures stability for large file uploads and downloads |
FILE_TOKEN_KEY | Randomly generated 32-bit hexadecimal string | Encrypts document access tokens, and prevents unauthorized personnel from accessing sensitive test data |
FE_DOMAIN | https://fastgpt-transformer.example.com | Configures the front-end access domain name, and uniformly manages resource loading and permission verification for supplier audit pages |
Three common mistakes
- Phenomenon: After restarting the deployment server, all high-voltage test reports and audit configuration information stored in the container are lost. Cause: Data persistent mounting is not configured, and business data is stored in the container writable layer, which is automatically reset after the container restarts.
- Phenomenon: After pulling the official docker-compose file for deployment, services related to supplier audit cannot start. Cause: The official repository has not updated the docker-compose template adapted to the specialized configuration of this category in time, resulting in a mismatch between the image version and business requirements.
- Phenomenon: No contact personnel follow up after a commercial version deployment application is submitted. Cause: Complete enterprise contact information is not filled in the application form, or the internal work order assignment process is not triggered after the form is submitted.
How to confirm the configuration is complete
- Import the full-process test data and assembly records of a single transformer, check whether the data association relationship meets the single-unit traceability requirements, and confirm the validity of the database connection configuration.
- Upload a standard-format insulating oil report, verify whether dedicated fields such as partial discharge magnitude and insulating oil moisture content are correctly identified, and confirm that the document parsing rule configuration is correct.
- Restart the deployment service container, check whether stored historical test data and audit configuration are fully retained, and confirm that the data persistent configuration takes effect.
- Submit a supplier audit process application, verify whether the application can be normally transferred after submission, and confirm that the front-end and back-end interface configurations match.
The values provided are common starting points and should be measured against the reader's own samples.