What This Category of Data Looks Like
This category covers full-process quality control from work-in-progress to finished products. Daily documents include control plans, patrol inspection records, SPC reports, finished product inspection reports, nonconforming product reviews, release orders, and monthly quality reports. Data is primarily sourced from MES systems, online testing equipment, laboratory test results, process parameter logs, customer quality standards, and historical defect databases. Data updates occur per production batch, with real-time collection per shift or periodic updates. Fields include inspection item number, test value, judgment result, operator, equipment number, release status, and more. Units adjust dynamically based on the type of inspection item.
Constraints for Source Citation and Traceability
Since data sources are scattered and update frequencies vary by production batch, citation and traceability must accurately match production batches to corresponding documents for each inspection step, to avoid mixing data across batches. There are significant structural differences across document types, so support is required for automatically associating matching fields by document type. For example, extract trend data from SPC reports, and extract release judgment results from finished product inspection reports. The ongoing updates to the historical defect database mean traceability results must reflect the latest defect records. The citation scope must be limited to documents linked to the current production task, to prevent irrelevant data from disrupting judgments. Release order approval authority is tied to documents, so traceability must retain citation trails for approval nodes to ensure auditability.
Configuration Settings
These configurations apply to FastGPT v4.17.0:
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
quoteMaxToken | 800–1200 token | Matches the average length of single-batch inspection documents for this category, to avoid truncating critical judgment information |
responseData | Enabled | Used to display identifiers such as cited document type and production batch number in results, meeting audit traceability requirements |
detail | Enabled | Retains specific field content of cited documents, making it easy for quality engineers to verify inspection items and final judgment results |
| Single search citation limit | Top 3–5 entries | The number of documents associated with a single batch in this category is limited; too many citations will exceed context capacity limits |
| Document filtering rules | Filter by production batch tag | Matches the batch-based update feature of the data, preventing irrelevant cross-batch data from mixing into the current audit scenario |
Three Common Configuration Errors
- Symptom: Cited document sources appear in the debug page, but no citation traces are shown on the officially published page. Cause: The
responseDataconfiguration item is not enabled, or the citation display function is not activated in the publish settings. - Symptom: The knowledge base search citation limit is set to 2000, but the single-round answer still exceeds the token limit. Cause: The
quoteMaxTokenvalue was not adjusted based on the average length of documents in this category. Using an overly high search limit directly causes context overflow. - Symptom: Program execution results in the workflow cannot be used as background knowledge input for subsequent modules. Cause: The output fields of the execution result are not configured as a citeable data source, or the
detailconfiguration is not enabled to expose result metadata.
How to Verify Successful Configuration
- A query targeting the inspection records of the current production batch is executed, and the returned results are checked for metadata including document type and batch number.
- The token count of the returned results is verified to fall within the range set by
quoteMaxToken, with no critical information truncated. - A cross-batch query is run, and the system is verified to automatically filter documents not associated with the current batch.
- The officially published page is accessed, and citation sources are confirmed to be properly displayed below the answer.
The values provided are common starting points and should be measured against the reader's own samples.