What data for this category looks like
This category of data covers full-process documents related to incoming material inspection and supplier quality for manufacturing enterprises, including inspection specifications, sampling plans, incoming material reports, supplier audit reports, exception contact sheets, 8D reports, and concession acceptance approval documents. Data sources include purchase orders, drawing specifications, supplier quality certificates, output data from inspection equipment, historical quality ledgers, and supplier portal information. Updates are made with real-time records generated per batch of incoming materials, bulk data updated with monthly or quarterly supplier evaluations, and exception rectification documents added with irregular quality audits. Documents include structured fields such as batch number, supplier code, inspection items, and judgment results. Some documents are accompanied by unstructured on-site inspection photos.
What constraints these characteristics impose on the knowledge base retrieval and recall link
This category of data has high update frequency and scattered sources. Real-time records generated per batch of incoming materials and bulk evaluation data from monthly or quarterly reviews must be synchronized to the knowledge base, which imposes requirements on retrieval real-time performance. Document types cover structured ledgers and unstructured reports. Some data comes from original output of inspection equipment, so content parsing compatible with multiple formats is needed. Retrieval must accurately match exclusive fields such as batch number and supplier code to avoid returning irrelevant results across batches or suppliers. At the same time, retrieval results for quality data must be associated with historical exception records to support root cause analysis, so recalled content must contain sufficient context-related information.
How to configure settings
This configuration is based on FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
similarity | 0.75–0.85 | Match precise fields for incoming material inspection to avoid mixing low-relevance supplier historical data into results |
limit | Top 10 entries | Control the number of results recalled per query to meet the quick review needs of IQC personnel |
searchMode | mixedRecall | Combine semantic retrieval and keyword matching to accurately hit structured fields such as batch numbers and sampling plans |
usingReRank | Enabled | Re-rank recalled results to prioritize supplier audit reports more relevant to the current inspection task |
datasetSearchUsingExtensionQuery | Enabled | Generate extended queries based on user questions to cover multiple document types such as supplier quality certificates and 8D reports |
collectionIds | Bind the collection ID of the corresponding supplier quality knowledge base by business line | Isolate quality data from different suppliers to avoid retrieval interference across suppliers |
Three common configuration errors
- Retrieval results return quality data across suppliers. The symptom is that when querying the inspection specifications for supplier A, audit reports for supplier B are also returned. The cause is that
collectionIdswas not configured to bind the exclusive knowledge base collection, resulting in failure to isolate quality data from different suppliers. - Retrieval fails to correctly identify qualified judgment fields. The symptom is that the judgment result field in the returned incoming material reports is empty or inconsistent with the actual situation. The cause is that structured data field mapping configuration was not completed, which may lead to incorrect rejection and production line downtime.
- Retrieval does not return the latest exception rectification records. The symptom is that when querying the supplier root cause analysis plan, only older versions of 8D reports are returned. The cause is that real-time incremental update configuration was not enabled, resulting in the knowledge base not synchronizing the latest quality audit data, which may lead to defective materials flowing into the production link.
How to confirm the configuration is correct
- Perform a single retrieval to verify that the supplier of the returned results matches the query conditions, confirming that the
collectionIdsconfiguration takes effect. - Check the number of retrieval returned results to confirm that it meets the preset range, verifying that the
limitparameter is configured correctly. - Enter a query statement containing a batch number to verify whether the inspection documents for the corresponding batch can be accurately hit, confirming that the
datasetSearchUsingExtensionQueryconfiguration takes effect. - Compare the judgment fields of the retrieval results with the original documents to confirm that the structured data field mapping configuration is correct.
The values given are common starting points and should be measured against the reader's own samples.