What Data for This Category Looks Like
Data for this category primarily comes from PLM/ERP systems, parts inspection records, assembly tool collection data, test benches, MES systems, and customer technical agreements. Typical daily documents include assembly process cards, BOM lists, torque records, clearance adjustment records, trial run reports, factory inspection sheets, and packing lists. Data is updated per single device or each production order. Fields include specific assembly parameters such as torque values (unit: N·m), clearance values (unit: mm), and concentricity tolerances. Document structures are highly customized per order, mostly combining structured forms and non-standard technical descriptions.
What Constraints Do These Characteristics Impose on Source Citation and Traceability
Documents are updated per single device or production order. Citation traceability must be precisely linked to exclusive data for the corresponding production batch, to avoid invalid cross-order matching. Data comes from multiple heterogeneous sources including PLM, MES, test benches, and others. Traceability configurations must support cross-system data association verification, ensuring cited process parameters and abnormal records originate from the same production stage. Customized document structures and precise parameter fields with units require traceability to match field semantics and unit consistency, preventing confusion between clearance and torque data from different orders. A single citation must cover the complete closed loop of assembly processes and abnormalities, rather than only extracting a single document segment.
Configuration Settings
These configurations are adapted for FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
quoteMaxToken | 900–1100 token | Adapts to the total parameter and text volume of single-unit general mechanical equipment assembly documents, preventing truncation of critical traceability fields such as torque and clearance values |
responseData | Return original document path, order number, device serial number | Matches the category's data management pattern of per-order and per-device tracking, enabling precise traceability to original documents for the corresponding production batch |
detail | Enabled | Used to return complete citation fragments for abnormal reports and process documents, covering associated content from assembly process cards and trial run records |
| Citation source filtering rules | Filter by device serial number | Prevents invalid cross-device citations, adapting to the business model of single-unit customized assembly for this category |
| Multi-source data association configuration | Bind associated fields between PLM and MES | Links BOM lists and assembly torque records, ensuring cited process parameters align with actual assembly stages |
Three Common Configuration Errors
- Symptom: Exported knowledge base original document links cannot be accessed normally via nginx proxy, returning a 404 status code. Cause: No proxy forwarding rules for the knowledge base original document path are configured, causing FastGPT-generated links to point to internal system addresses that cannot be accessed externally.
- Symptom: Citation results only return a single document fragment, without associating complete process and abnormal records for the corresponding order. Cause: The
detailconfiguration is not enabled, or thequoteMaxTokenvalue is set too small, truncating cross-document associated content. - Symptom: Recalled citation data spans orders, with parameter confusion across different device batches. Cause: No citation source filtering rules configured by device serial number, leading to matching document content from unrelated orders.
How to Verify Correct Configuration
- Initiate an assembly process parameter query, check if the returned results include the original document path, order number, and device serial number fields specified in the
responseDataconfiguration. - Review the completeness of citation fragments, confirm that critical assembly parameters are not truncated, and adjust the
quoteMaxTokenvalue to cover full content. - Simulate a cross-order query request, verify that returned results only include documents related to the target device, with no data from unrelated orders included.
- Test access to the original document link via the nginx proxy, confirm that the original content of the corresponding assembly document can be opened normally.
The values provided here are common starting points and should be evaluated against the reader's own samples.