What data belongs to this category
Data for this category originates from PLM, ERP, MES, supplier materials, validation tests, and customer-specific requirements. Updates occur irregularly, triggered alongside every process or engineering change. Core documents include ECN/ECR, change assessment reports, drawings and BOM version files, process validation reports, production switching plans, inventory disposal forms, and customer approval documents. Fields include change number, version number, effective date, material code, process parameters, customer approval document number, and others. Some parameters have dedicated units such as rotational speed and temperature.
What constraints do these characteristics impose on the tool calling and plugins workflow
Multi-source system data sources require tool calling to support multi-API integration logic, preventing scenarios where a single call only pulls data from one system. Irregular update frequency requires plugins to support incremental sync triggers, and cannot rely on fixed-cycle data pulling. Diverse document structures require tool calling to pre-set parsing rules for different document types, enabling field extraction for files such as ECN and BOM. Dedicated fields and units require tool calling to configure precise field mapping, avoiding data field mismatch issues.
Configuration settings
The following configurations are developed for FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Workflow/API tool selection | auto | Adapt to the need for parallel tool calling in process change and engineering change scenarios |
| Workflow/API function-call configuration | Allow calling all registered tools | Cover scenarios of pulling data from multiple systems including PLM, ERP, MES |
| Context window size | 8000–12000 token | Accommodate content from multiple core documents such as ECN, BOM versions, and process validation reports |
| Tool calling timeout | 120 seconds | Match the average response duration for cross-system data pulling |
| Field mapping rules | Pre-set according to change document templates | Match the dedicated field formats of ECN/ECR and customer approval documents |
Three common configuration mistakes
- Tool calling returns empty results, and logs indicate field mismatch. This occurs when dedicated field mapping rules are not pre-set for change documents such as ECN and BOM, preventing the plugin from correctly extracting target data.
- Streaming output configuration fails, and frontend calls report errors. This occurs when the streaming return logic for
automodetoolChoiceis not defined, and multi-system data splicing segmentation requirements are not addressed. - Multimodal plugin calls return results with significant deviation. This occurs when image recognition prompt templates are not configured for dedicated scenarios such as process drawings and BOM version diagrams, and version metadata for drawings is not associated.
How to verify correct configuration
- Initiate a simulated process change test request, and confirm that tool calling correctly pulls ECN documents from PLM and BOM version data from ERP.
- Review tool calling logs to confirm that the
toolChoiceparameter takes effect, and that returned fields from called tools match change document templates. - Trigger a timeout test to confirm that the tool calling timeout setting aligns with actual cross-system response durations, and that frequent timeout errors do not occur.
- Test multimodal plugin calls by uploading process drawings, and confirm that recognition results associate corresponding version BOM information.
The values provided are common starting points and should be measured against the reader's own samples.