What This Category of Data Looks Like
The data sources for this category include PLM, ERP, MES from manufacturing enterprises, supplier materials, verification test results, and customer-specific requirements. Updates occur irregularly, each time a change is implemented. Daily documents include ECN/ECR, change assessment reports, drawings and BOM version files, process verification reports, switchover plans, inventory disposition documents, and customer approval documents. Each document includes core fields such as change number, version number, effective date, associated process or material, and some drawing documents contain quantitative information such as dimensions and process parameters.
Constraints for Citation Sources and Traceability
Multi-source and heterogeneous data sources require the traceability link to support connection with knowledge bases of multiple system types, and need to unify field formats across different documents to ensure matching accuracy. Irregular update cycles require traceability configuration to support incremental synchronization and version verification, to avoid referencing expired files from old versions. The range of document types covering text, drawings, tables and other formats requires chunking rules to adapt to different content structures, while retaining key identifiers such as version numbers and change numbers. The characteristic that changes are linked to multiple processes requires traceability to cover full-link documents including design, materials, and processes, to ensure that cited change basis is complete and not missing.
Configuration Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
quoteMaxToken | 800–1200 token | Adapts to the length of cited fragments from long documents such as ECN and process verification reports, avoiding truncation of key change descriptions |
responseData | Enabled | Used to return cited document details, meet the need for displaying traceability information on the terminal, and aligns with the API return rules of FastGPT v4.17.0 |
detail | Full | Ensures that returned cited fragments contain complete context-related information, making it easy to verify chain effects of changes |
| Single search limit | Top 6 entries | Covers multiple types of change-related documents (drawings, BOM, customer files), avoiding missed relevant basis |
| Reranking | Enabled | Prioritizes matching core fields related to changes (version number, change number), improving traceability accuracy |
| Maximum context | 4000–6000 characters | Accommodates relevant information across multiple change documents, supporting full-link traceability of changes |
Three Common Configuration Errors
- Calling the published API interface only returns model responses, with no citation details. The cause is that the
responseDataconfiguration is not enabled, or the configuration item is set to disabled. - The terminal reply does not display the online preview details of the original file for the cited fragment. The cause is that the path mapping rule for the original document is not configured, or the unique identifier field of the original document is not retained during knowledge base chunking.
- A red number error occurs during citation. The cause is that the value set for
quoteMaxTokenexceeds the context limit supported by the model, or there is a field format mismatch when connecting to multi-source knowledge bases.
How to Verify Successful Configuration
- In the API debugging tool of FastGPT v4.17.0, enter a test question related to changes, call the interface, and check whether the returned result contains the
responseDatafield and the corresponding cited fragment information. - Initiate a query on the terminal test page, and check whether the reply displays the cited document name, fragment content, and source identifier.
- Upload a test ECN document to the knowledge base, initiate a relevant query, and verify whether the returned cited fragment matches the change content in the document.
- Adjust the value of
quoteMaxToken, and verify whether the length of the returned cited fragment conforms to the expected configuration.
The values provided are common starting points and should be measured against the reader's own samples.