What data for this category looks like
Data sources for this category include cell grading data, factory MES systems, welding equipment logs, torque tool records, BMS software version files, and EOL test bench test data. Daily documents include cell grouping rules, material BOM lists, welding and torque operation records, BMS flashing logs, insulation and voltage withstand test reports, EOL finished product test reports, and system configuration parameter lists. Data is updated once for each produced battery pack or energy storage cabinet. Corresponding configuration data is synchronized each time the BMS software version is updated. Fields include cell grading parameters, welding torque values, insulation resistance values, BMS version numbers, EOL test pass rates, and more. There is no unified standard format across categories.
What constraints these characteristics impose on the "workflow orchestration" link
Since data sources cover hardware device logs and software configuration files, the workflow must support access to data in different formats. Do not use hard-coded field parsing rules. Single device data is updated independently. The workflow must support triggering by a single work order to ensure the inspection scope matches the corresponding device data. Documents include safety-sensitive parameters such as welding torque and insulation resistance. The workflow must add parameter validity check nodes to prevent invalid values from entering the Q&A process. BMS version changes adjust system configuration logic. The workflow must support dynamically loading the latest version of configuration rules to avoid using expired parameters.
How to set the configuration
The following configurations are based on the workflow interface design of FastGPT v4.17.0.
| Configuration Item | Recommended Approach | Basis for This Approach |
|---|---|---|
| Data Source Node Configuration | Bind dedicated API interfaces of MES, welding equipment, and BMS systems, filter data by the work order ID defined in variables | Data must be associated with a single device. Filtering by work order ID accurately matches the historical records of the corresponding device |
| Context Window Size | 800–1200 characters, calibrated based on actual testing | Must cover the complete inspection record and grouping rules of a single device, to avoid truncation of key parameters |
| Node Trigger Rule | Trigger by work order status change bound to nodeId | Ensures the inspection Q&A is only triggered after the device completes the corresponding process, avoiding invalid calls |
| Special Character Processing Rules | Escape special characters such as double quotes and backslashes, retain original semantics, with processing duration not exceeding 500 milliseconds | Device logs and BMS configurations often contain characters such as double quotes. Unprocessed content will cause workflow parsing failures |
| Benchmark Test Configuration | Select 10–20 device work orders from different batches as the test set, calibrated based on actual testing | Must cover scenarios with different cell grading parameters and BMS versions, to ensure workflow stability |
Three common mistakes
- Phenomenon: Workflow debugging and verification fails. The interface prompts "Please check whether the nodes are filled correctly and whether the connections are normal". Even the simplest two-node workflow cannot run. Cause: The data source node is not correctly bound to the work order ID configured in
variables, or the connections between nodes do not pass valid parameters. - Phenomenon: An error occurs when the workflow parses device logs. Torque record content containing double quotes cannot be recognized. Cause: No special character escaping rules are configured. Directly passing text with double quotes causes node parsing failure.
- Phenomenon: Workflow operation results are inconsistent. The inspection Q&A logic deviates between work orders of different batches. Cause: Configuration rules are not dynamically loaded according to the BMS version bound to
nodeId. Expired grouping and detection parameters are used.
How to confirm the configuration is complete
- Run a test work order with known parameters. Check whether the data source pulled by the workflow matches the historical records of the corresponding device.
- Simulate log text containing double quotes as input. Confirm that the workflow does not have parsing errors and the output results are normal.
- Switch configuration files of different BMS versions. Verify whether the inspection logic of the workflow is updated synchronously.
- Run the benchmark test set. Check whether the response results of the workflow meet the preset verification rules, with thresholds calibrated according to actual business scenarios.
The values provided are common starting points and should be measured against the reader's own samples.