What the Data for This Category Looks Like
Data sources for this category include design BOM, silicon steel sheet and insulating material test data, vacuum drying equipment collection records, oil test reports, high-voltage test reports from test stations, and other relevant documents. The system synchronizes data updates with each production process for individual products, and with each batch for raw materials. Daily documents include winding and core assembly records, vacuum drying logs, insulating oil test reports, partial discharge and pressure withstand test reports, and nameplate parameter tables. Fields include insulation resistance value, partial discharge value, drying temperature, material batch, and others. No unified batch format exists for these documents. Data for a single product links to the complete production chain.
Constraints Imposed on Deployment and Upgrade
Full production chain data association for individual products requires deploying storage structures that support cross-document association. Multiple non-standard document types, such as test reports and assembly records, require support for custom field mapping and parsing. High-frequency, small-batch data updates require optimizing database write performance. Single-product traceability demands configuring data version management and associated query capabilities. Accurate core test data requires configuring data validation rules during deployment. These rules prevent invalid data from entering the system and ensure reliability for subsequent audit processes.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
MONGODB_URI | mongodb://fastgpt:securepass@db-host:27017/transformer_prod?authSource=admin | Stores full-link test and assembly data for individual transformers, requires a dedicated database instance |
REDIS_URL | redis://:redispass@redis-host:6379/0?maxmemory=1000 MB&maxmemory-policy=allkeys-lru | Caches frequently accessed insulating oil reports and pressure withstand test reports to avoid repeated database reads |
DB_MAX_LINK | 20–30 | Adapts to the high-frequency, small-batch data write concurrency requirements for individual products, prevents connection pool exhaustion |
STORAGE_S3_ENDPOINT | http://s3-cn-huabei.example.com | Stores large documents such as high-voltage test reports and vacuum drying records, binds a dedicated storage endpoint |
FE_DOMAIN | https://transformer-inspection.fastgpt.your-domain.com | Binds a scenario-specific frontend domain to isolate access paths |
ROOT_KEY | 32-bit random string generated per enterprise security specifications | Manages administrator permissions for this scenario, avoids cross-scenario permission conflicts |
Three Common Configuration Mistakes
- Phenomenon: FastGPT v4.17.0 containers restart continuously, and the frontend page fails to load normally. Cause:
MONGODB_URIorREDIS_URLis not configured correctly, resulting in database connection failure, and the service exits automatically after startup. - Phenomenon: Uploaded insulating oil reports and pressure withstand test reports cannot be parsed correctly, leaving core fields empty. Cause: No scenario-specific custom field mapping rules are configured, so the system cannot recognize dedicated parameters such as partial discharge values and insulation resistance values.
- Phenomenon: Non-commercial version API keys cannot have usage duration and count limits set. Cause: Scenario-specific key management configuration is not enabled during deployment, and default key rules do not support custom permissions.
How to Verify Successful Configuration
- Access the configured
FE_DOMAINto confirm the frontend page loads normally with no obvious error prompts. - Upload a scenario-specific insulating oil test report to verify the system correctly stores document metadata and identifies core fields.
- Run an associated query for inspection records of a single transformer to confirm linked assembly records, test reports, and other data load completely.
- Check the database connection pool status to confirm current connection counts fall within the range specified by
DB_MAX_LINK.
The values provided are common starting points and should be measured against the reader's own samples.