What the Data for This Category Looks Like
Core data for this category includes cell capacity grading data, MES production records, welding and torque equipment logs, BMS flashing records, insulation and voltage withstand reports, EOL test results, and system configuration lists. Data sources cover equipment and management systems across the entire production process. Updates are generated upon completion of each battery pack or energy storage cabinet production. Configuration-related data is synchronized each time the BMS software version is changed. Daily associated documents include grouping rules, BOMs, thermal management plans, and more. Fields include cell parameters, torque values, test voltages, software version numbers, and more.
Constraints Imposed During Deployment and Upgrade
Data sources for this category are scattered and update frequently. During deployment, multiple data sources such as MES, welding equipment, and BMS systems must be integrated. Connection parameters and permissions for each data source must be configured in advance. During the upgrade process, configuration rules associated with the BMS software version must be updated synchronously. Document indexes for both old and new versions must be kept compatible to avoid data gaps during traceability. Single-batch data volume grows with production scale. Sufficient storage and computing resources must be reserved during deployment to prevent slow data loading that impacts traceability efficiency. Field formats for documents such as grouping rules and torque records are fixed. Field mapping rules must be defined in advance during deployment to ensure data can be correctly associated with the corresponding traceability chain.
The following configuration items apply to FastGPT v4.17.0.
Configuration Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
DB_MAX_LINK | 100–150 connections | Adapts to the connection requirements of multiple data sources and high update frequency for this category, avoiding connection pool exhaustion |
MONGODB_URI | Configure according to the actual production database address | Stores unstructured data such as test reports and equipment logs, matching the document storage type of this category |
REDIS_URL | Configure as the local cache service address, set cache validity period to 3600 seconds | Accelerates loading of traceability results for high-frequency queries, meeting real-time requirements in production scenarios |
STORAGE_S3_ENDPOINT | Configure according to the enterprise's internal object storage address | Stores large-volume files such as batch-generated insulation and voltage withstand reports and EOL test data |
PG_URL | Configure according to the actual production relational database address | Stores structured business data such as BOMs, grouping rules, and system configuration lists |
Common Misconfigurations
- Symptom: Clicking a document link associated with traceability prompts a download failure or file not found. Cause:
STORAGE_S3_ENDPOINTor object storage access permissions are not configured correctly, making stored test reports and log files unreadable. - Symptom: The initial interface after deployment is in English, and the language switches to an unexpected version after a pull operation is performed. Cause: The localization configuration item corresponding to
FE_DOMAINwas not configured in advance, or the corresponding language pack file was not loaded during deployment. - Symptom: Timeout errors occur when querying multiple traceability data in batches. Background logs show connection pool exhaustion. Cause: The
DB_MAX_LINKconfiguration value is too low to support connection requests from multiple data sources simultaneously.
How to Verify Successful Configuration
- Run a single-pack traceability query. Check that returned fields include expected content such as cell parameters, torque values, and software version numbers. Confirm that field mapping rules are active.
- Access the page corresponding to
FE_DOMAIN. Verify that the interface language matches the preset configuration. Confirm that the localization configuration loaded correctly. - Upload a test insulation and voltage withstand report. Check that it can be stored successfully and retrieved in subsequent queries. Confirm that the storage configuration is active.
- View the real-time status of the database connection pool. Confirm that the current active connection count matches the configured
DB_MAX_LINKvalue. Verify that the connection pool configuration is reasonable.
The values provided are common starting points and should be measured against the reader's own samples.