What Data for This Category Looks Like
The data for this category comes from raw material batch ledgers, production MES systems, slurry and coating testing equipment, workshop dew point monitoring devices, formation and grading cabinets, and laboratory testing equipment. Data update cycles cover production nodes for each batch of materials and each cell, with some environmental and equipment parameters synchronized in real time. Daily documents include batching records, coating and rolling parameter tables, winding/lamination process records, liquid injection ledgers, formation and grading data reports, OCV and safety test reports. Fields cover material batch numbers, process parameter values, test result values, and corresponding detection times.
What Constraints Do These Characteristics Impose on the Multi-Turn Dialogue and Prompts Link
The multi-batch, real-time updated data characteristics of this category require multi-turn dialogue to be bound to the specific cell production batch corresponding to the current bidding project, to avoid mixing data across batches. The diversity of subdivided process parameters and test fields requires prompts to precisely limit the range of callable documents, only allowing reference to audited data from batching, coating, formation and grading, and other links covered by the bidding project. Real-time synchronized environmental and equipment parameters require the dialogue context to automatically filter expired non-current batch data, preventing calls to production records not included in the bidding scope. Additionally, the high requirements of electrochemical systems for data accuracy require prompts to clearly distinguish between summary data used for quotation preparation and original test data from production links, to avoid misuse of parameters.
How to Configure the Setup
This configuration is based on the functional logic of FastGPT v4.17.0.
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
chatId | Bind to the cell production batch ID corresponding to the current bidding project | Ensure multi-turn dialogue only calls audited data from batching, coating, formation and grading, and other links for this batch, avoiding cross-batch data confusion |
messages | Only retain bidding-related context from the current dialogue turn, truncate historical messages exceeding 1200 characters | Control context information density, adapt to the field length of subdivided process parameters for lithium-ion cells, and prevent prompt matching failures |
variables | Preset 10 dedicated bidding variables including project batch number, coating areal density range, and average formation and grading capacity | Quickly call standardized cell data fields, reducing repeated input of process parameters |
| Context window length | 800–1200 token | Adapt to the number of parameters in subdivided scenarios, preventing excessive irrelevant data from loading in a single dialogue turn |
| Prompt template update frequency | Review once every 7 days | Match the process adjustment rhythm of bidding projects, ensuring prompts always cover compliant parameters for the current batch |
Three Common Mistakes
- Phenomenon: The dialogue returns results that do not match the preset prompt requirements, such as returning general electronic parameters when asking for cell coating areal density. Cause: The prompt does not limit references to only coating rolling parameter documents for lithium-ion cell manufacturing, causing the model to call irrelevant knowledge base content.
- Phenomenon: A context overflow error occurs during the dialogue, with the interface displaying "Context length exceeded". Cause: The historical message length of the
messagesparameter is not restricted, causing accumulated production data from multi-turn dialogue to exceed the system threshold. - Phenomenon: The exported dialogue record does not include the process parameter fields corresponding to the bidding batch. Cause: The specific batch ID is not bound via
variables, causing the dialogue context to not be associated with production documents for the corresponding batch, resulting in missing key information in the exported data.
How to Confirm the Configuration Is Complete
- A test dialogue is initiated, with the input "Please retrieve the coating rolling parameters for the current bidding batch", and returned results are verified to only include document data related to batching and coating for the corresponding batch.
- Multiple consecutive dialogue turns are initiated, and the system is observed to automatically truncate historical messages exceeding the set length, with no context overflow errors occurring.
- A dialogue record is exported, and the record is verified to include the dedicated bidding fields corresponding to the preset
variablesvariables. - After adjusting the prompt template, a new dialogue is initiated, and returned results are verified to match the requirements of the updated template.
The values given are common starting points and should be measured against the reader's own samples.