What the Data for This Category Looks Like
PCB manufacturing inspection and process record data sources include customer Gerber files, drill files, BOM lists, CAM work drafts, equipment operating parameters, tank solution test records, AOI inspection reports, electrical testing reports, and section analysis reports. Data updates use production batches as the core cycle, paired with continuous shift-by-shift collection of equipment parameters and real-time test data. Documents for a single production batch include engineering production instructions, layered process parameter records, and multiple rounds of inspection reports. Fields include graphic number, drill hole diameter (unit: mm), lamination temperature (unit: ℃), chemical solution concentration (unit: g/L), inspection defect type and location, etc. There is no uniform fixed single document length. Some process reports require linking multiple cross-system files.
Constraints Imposed by These Characteristics on the Citation Source and Traceability Link
The multi-source, batched data characteristics of PCB manufacturing demand that the traceability link accurately bind production batch identifiers to avoid cross-batch data mixing. Fields across different process documents have strong correlations. For example, Gerber analysis records must match hole diameter information with drilling parameter reports. Tank solution test data must correspond to concentration thresholds in etching process records. Traceability must support cross-document field association queries. Single-batch data has a high update frequency and serious error consequences. Traceability must ensure search results only cover valid documents for the current production batch, while fully retaining the citation chain of original data. Relying solely on keyword matching while ignoring batch and process association rules is not sufficient.
Configuration Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Maximum Context Length | 8000–12000 characters | The total length of process documents for a single production batch is relatively high, requiring coverage of complete batch data |
quoteMaxToken | 1500–2000 token | The token count of a single process document falls within this range, ensuring complete citation content |
responseData Return Limit | Top 10 matching results | The number of process documents for a single production batch is usually within 10, covering all associated documents |
detail Recall Weight | Calibrated through actual testing | Different types of inspection reports have large differences in text complexity, requiring adaptation to different scenarios |
| Single Retrieval Upper Limit | 6 times | Matches cross-system CAM, equipment, and inspection data to ensure full coverage of the link |
| Context Cache Duration | 24 hours | Matches the update cycle of a single production batch, preventing retrieval failures due to expired cache |
Three Common Misconfigurations
- Phenomenon: Non-current production batch documents appear in search results. Cause: No production batch identifier is bound for filtering, and only keyword matching leads to cross-batch data being included.
- Phenomenon: Knowledge base disk usage exceeds expectations. Cause: No automatic batch data cleanup rules are configured, leaving redundant original files and embedding vectors from multiple batches.
- Phenomenon: Parameter fields for some processes are empty in traceability results. Cause: No association field mapping is established between CAM data and process reports, and only filename matching causes some associated documents to fail to be correctly retrieved.
How to Verify Proper Configuration
In FastGPT v4.17.0, configuration can be verified through the following executable actions:
- Upload all documents for a single production batch, perform a traceability query, and check that the returned results only include process records for that batch with no cross-batch data.
- Adjust the
quoteMaxTokenparameter value, verify that the truncated length of returned citation content matches the configured token range. - Check system logs to confirm that the number of matching results returned by
responseDatameets the configured upper limit. - Compare the associated fields of AOI inspection reports and electrical testing reports, confirm that traceability results can correctly link parameter information for corresponding processes.
Note: The values provided are common starting points and should be evaluated against the reader's own samples.