What the data for this category looks like
Production data sources for this category include cell capacity grading data, MES systems, welding equipment, torque tools, BMS software version records, and EOL test bench data. Daily documents include grouping rules, BOM lists, welding and torque records, BMS flashing records, insulation and voltage withstand reports, EOL test reports, and system configuration lists. Data updates occur once per produced power battery pack or energy storage cabinet. Corresponding documents are updated synchronously each time the BMS software version changes. Document fields include cell capacity, internal resistance, material code, torque value, BMS version number, and more. Some fields have clear units, such as torque value with the unit N·m.
Constraints for knowledge base retrieval and recall workflows
This category has high data update frequency and small per-batch data volume. The retrieval system must support incremental updates and precise matching to avoid redundant data occupying context space. Multiple document types coexist. The retrieval mode must adapt to both structured ledger fields and unstructured process rules. Data fields have clear units and business-specific meanings. The retrieval process must retain field precision to avoid incorrect associations caused by fuzzy matching. Production errors have serious consequences. Recall result relevance and accuracy must meet business compliance requirements. Retrieval results must not include production data from unrelated categories.
Configuration settings
This configuration is based on FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
similarity | 0.75–0.85 | Match high-precision business documents such as grouping rules and welding parameters, filter low-match irrelevant data |
limit | Top 8 recalled entries per call | The number of documents linked to a single pack production ledger is limited, avoiding generation delays from overly long context |
searchMode | mixedRecall | Cover both structured ledger fields and unstructured process rules, adapt to multiple types of business documents |
usingReRank | Enabled | Perform secondary sorting on recall results, improve ranking priority for key documents such as BMS configurations and insulation test reports |
datasetSearchUsingExtensionQuery | Enabled | Automatically expand synonymous expressions for process rule queries, cover wording differences across different business documents |
collectionIds | Bind the exclusive knowledge base collection for this category | Isolate production data from other categories, prevent irrelevant content in retrieval results |
Three common misconfigurations
- Retrieval response timeout, with a single call taking more than 30 seconds. This happens when the
limitparameter is not restricted, recalling excessive historical ledger data and causing the context length to exceed processing thresholds. - Retrieval results omit documents such as BMS flashing records. This occurs when
datasetSearchUsingExtensionQueryis not enabled, failing to match synonymous expressions of process documents and preventing rule queries from hitting corresponding business records. - Retrieval results include documents from the cell manufacturing link. This happens when
collectionIdsis not configured to bind the exclusive knowledge base collection, leading to cross-category data interfering with retrieval result accuracy.
How to verify a correct configuration
- Upload the production ledger and corresponding process documents for a single energy storage system, initiate a retrieval request, and confirm the returned results include exclusive data such as the welding torque record and BMS version information for that pack.
- Adjust the
similarityparameter to 0.8, initiate a query related to grouping rules, and confirm the matching degree of returned results meets expectations with no low-correlation irrelevant content. - View system retrieval logs, confirm the number of recalled documents per call does not exceed the set
limitvalue, and there are no abnormal timeout records. - Switch to the knowledge base collection of another category, initiate a business query for this category, and confirm the current retrieval only returns exclusive document data for this category.
The values given are common starting points and should be measured against the reader's own samples.