What this category's data looks like
Daily data from professional heat treatment plants, automotive and bearing component heat treatment workshops includes heat treatment process cards, charging charts, furnace temperature curves, hardness and metallographic reports, equipment inspection forms, and exception handling records. Data sources cover material grades, customer technical requirements, temperature control instruments, furnace temperature uniformity testing equipment, hardness testers and metallographic equipment, and manufacturing execution systems. Update frequency is per heat load or per batch. Documents have clear fields and units: process cards note heating temperature and holding time, hardness reports note Rockwell or Vickers hardness, and furnace temperature curves include time axes and real-time temperature values.
What constraints do these characteristics impose on source citation and traceability
This category has high data update frequency, and single-batch data is closely linked. Traceability must accurately match specific heat loads or batches to avoid generalized retrieval. Document types are diverse, including text, tables, curves and other formats. Traceability must support fragment extraction and association of multi-format source data. Data sources include two categories: automatic equipment collection and manual entry. Traceability must clearly identify the data generation channel and entry subject. Single data entries include professional parameters and clear units. Traceability must display specific fields and values to help business personnel verify. At the same time, the consequences of errors are severe. The traceability link must ensure that the cited content is completely consistent with actual production data, and eliminate irrelevant or incorrect citations.
How to configure the settings
This configuration applies to FastGPT v4.17.0
| Configuration Item | Recommended Setting Range | Rationale |
|---|---|---|
| Similarity Threshold | 0.85–0.92 | Match professional terminology for heat treatment processes, avoid low-relevance retrieval results |
| Maximum Context | 8000–12000 token | Accommodate the complete content of multiple segments such as furnace temperature curves and process cards |
quoteMaxToken | 1500 characters | Limit the length of a single traceability content, adapt to single-page or single-segment fragments of heat treatment documents |
responseData | Return source data only | Ensure responses only use original text from the knowledge base, no additional content is generated |
detail | Enable full traceability | Display specific fields and units of source documents, such as heating temperature, hardness values, etc. |
| Number of Retrieval Results | Top 3–5 | Cover multiple documents related to the same heat load, such as process cards, charging charts, furnace temperature curves |
Three common configuration errors
- Phenomenon: The returned response does not directly use the original text from the knowledge base, and non-preset generated content appears. Cause: The
responseDataparameter is not configured correctly, and the mode of returning only source data is not locked. - Phenomenon: The interface shows that source data has been associated, but the response does not include specific document fragments or parameter details. Cause: The
detailconfiguration is not enabled, or the number of retrieval results is set too few, resulting in incomplete extraction of traceability information. - Phenomenon: The system does not respond for a long time after configuring index-related parameters. The problem persists after commenting the corresponding configuration and restarting the service. Cause: The chunking strategy is not adjusted for the multi-format characteristics of heat treatment documents, resulting in exceptions during index construction, or system resources are occupied by excessive single-heat-load data.
How to confirm the configuration is correct
- Initiate a query containing specific heat treatment parameters, check whether the response is completely consistent with the original text in the knowledge base.
- View the traceability information attached to the response, confirm whether it includes specific fields and units of source documents, such as heating temperature, holding time, hardness values, etc.
- Check system logs to confirm that there are no error messages such as token overflow or index construction exceptions.
- Test queries for multiple different heat loads, confirm that the traceability information can accurately associate with corresponding documents such as process cards and furnace temperature curves.
The values provided are common starting points and should be measured against the reader's own samples.