What this category of data looks like
This category of data covers daily business documents from manufacturing enterprise IQC, SQE and other departments, including inspection specifications, sampling plans, incoming material reports, supplier audit reports, abnormal contact sheets, 8D reports, concession acceptance approvals and other types. Data sources include purchase orders, drawing specifications, supplier quality certificates, inspection equipment, historical quality data and supplier portals, including fields such as batch numbers, inspection parameters, judgment standards, supplier information and more. The update rhythm changes with business scenarios: update incoming material reports and inspection records with each batch of incoming materials, update supplier evaluation data monthly or quarterly, and conduct audits and update audit reports irregularly.
Constraints imposed on knowledge base retrieval and recall by these characteristics
Multi-source and scattered data sources require retrieval configurations to support cross-data source association, to avoid recalling irrelevant supplier or inspection documents. Frequently updated business data requires the retrieval system to support incremental synchronization and scheduled refresh, ensuring recalled content aligns with the latest incoming material and supplier evaluation data. Diverse document types require adaptation to different chunking rules, balancing structured fields in inspection specifications and narrative content in 8D reports. Fields that associate batches and suppliers require retrieval logic to bind business identifiers, ensuring recalled content accurately matches the current inspection batch and cooperating supplier, and avoiding irrelevant information from interfering with judgments.
How to configure the settings
The following configurations are adapted for FastGPT v4.17.0.
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
similarity | 0.75–0.85 | Matches the precise judgment standards of incoming material inspection, to avoid mistakenly recalling irrelevant supplier documents and historical abnormal records |
limit | Top 8 entries | Adapts to the information volume of a single batch inspection, to avoid context overload affecting judgment efficiency |
searchMode | mixedRecall | Covers keywords in inspection specifications such as sampling plan parameters and semantically related content of historical abnormalities |
usingReRank | Enabled | Performs secondary ranking on recalled 8D reports and abnormal contact sheets, to prioritize root cause analysis content matching the current batch |
datasetSearchUsingExtensionQuery | Enabled | Automatically expands retrieval terms for batch numbers and supplier names, to associate more historical quality data and supplier documents |
collectionIds | Configured by supplier group | Targetedly recalls audit reports and quality certificates of corresponding suppliers, narrowing the retrieval scope to improve accuracy |
Three common configuration mistakes
- Symptom: The retrieval result returned by the API call is empty, and the answer field has no valid content. Cause: The associated knowledge base collection ID is not specified in the API request parameters, and the knowledge base corresponding to the supplier and incoming material inspection is not bound by default.
- Symptom: The retrieval results returned by platform testing and API calls are inconsistent, with differences in quantity or content. Cause: The
limitparameter is not configured correctly, ordatasetSearchUsingExtensionQueryis not enabled, resulting in failure to expand retrieval terms for batch numbers and supplier names. - Symptom: Download links for original documents can be obtained in conversations. Cause: Document download permission is not disabled in the knowledge base configuration, allowing users to directly download sensitive business documents such as inspection specifications and supplier audit reports.
How to confirm the configuration is complete
- Initiate an API call containing a test batch number and supplier name, check whether the returned retrieval results include the audit report of the corresponding supplier and the inspection specifications of that batch.
- Check the number of retrieval results returned by the API, confirm that it matches the value of the configured
limitparameter. - Trigger a retrieval request related to root cause analysis, check whether the recalled results prioritize 8D reports and abnormal contact sheets of the same batch.
- Test the document download function in the conversation, confirm that download links for original documents cannot be obtained.
The values provided here are common starting points and should be measured against the reader's own samples.