What this category of data looks like
Data for this category primarily comes from PLM/ERP systems, part inspection ledgers, assembly tool collection data, test bench monitoring data, MES manufacturing execution systems and customer technical agreements. Data updates follow the rhythm of single devices or individual orders. Involved documents include assembly process cards, BOM lists, torque tightening records, gap adjustment records, commissioning reports, factory inspection sheets, packing lists and more. Document fields include material codes, tightening torque values, gap tolerances, coaxiality parameters and others. Corresponding units are mostly newton meters, millimeters, percentages and similar.
What constraints this category's characteristics impose on the "source citation and traceability" link
The multi-order custom assembly characteristic of this category requires that citation traceability be precisely bound to the production batch and order information of a single device, to avoid cross-order data confusion. Document types are diverse and have large field differences. Records from different links, such as torque records and gap adjustment sheets, have different reference weights for assembly quality. Targeted recall priority configuration is required. Data update frequency triggers when a single device completes its production node. It is necessary to ensure that the latest version of assembly data is called during traceability. A multi-level BOM structure requires traceability to cover the full link of documents from components to complete machines, and support hierarchical source association.
How to set the configurations
| Configuration Item | Suggested Approach | Rationale |
|---|---|---|
quoteMaxToken | 800–1200 token | Matches the average total length of assembly documents for a single device in this category, avoids truncating critical torque and gap parameters |
detail | true | Requires complete source metadata to be returned, supports hierarchical traceability for multi-level BOMs and multiple documents |
responseData | Enabled | Synchronously displays document storage path, version number and associated order number to meet precise traceability requirements |
| Single recall limit | Top 6 entries | Covers the number of core assembly documents for a single device, avoids redundant information interfering with review logic |
| Citation source sorting | By relevance in descending order | Prioritizes documents directly affecting assembly quality, such as torque records and gap adjustment sheets |
| Compatible version | FastGPT v4.17.0 | Adapts to the parameter configuration logic of the current version, avoids version compatibility issues |
Three common configuration errors
- Phenomenon: Returned citation files do not match the target device's assembly documents, and part processing records from other orders are mixed in. Cause: No document classification filtering rules are configured, and documents from non-assembly links are included in the traceability scope.
- Phenomenon: In FastGPT v4.17.0, citation content is returned even if the citation display switch is not enabled. Cause: The global default value of citation configurations was adjusted by default in this version, so application-level parameters need to be manually verified and adjusted.
- Phenomenon: When parsing streaming results returned by the
detailparameter, it is impossible to associate with the unique batch identifier of a single device. Cause: No association field between order number and device number is bound in the traceability configuration, resulting in missing key association dimensions in source information.
How to confirm the configuration is correctly set
- Submit an assembly review query for a single device, check if the returned citation list includes core documents such as the device's corresponding BOM, torque records and gap adjustment sheets.
- Enable the
detailparameter, verify that the returned results include metadata such as document storage path, version number and associated order number. - Simulate a cross-order query scenario, confirm that the returned citations do not include assembly data from other orders.
- Check the citation switch in the application configuration, confirm that citation content is only displayed when the corresponding configuration is enabled, to avoid default return behavior.
The values provided are common starting points and should be measured against the reader's own samples.