What this category's data looks like
Typically, core data for the general mechanical equipment assembly category comes from PLM, ERP, parts inspection data, assembly tool collection systems, test benches, MES, and customer technical agreements. Daily documents include multi-level BOMs, assembly process cards, torque records, gap adjustment records, commissioning reports, factory inspection sheets, and packing lists. Data is updated once per device or per order, and assembly parameters and inspection records vary significantly across different orders.
Constraints on Tool Calling and Plugins
Multi-level BOMs and scattered data sources (PLM, MES, test benches, etc.) require tool calling to support cross-system data pulling and hierarchical parsing, ensuring accurate and complete BOM data in bid documents. Order-specific updated assembly data requires plugin calls to synchronize the latest inspection and debugging records in real time, avoiding expired parameters when generating quotations and bid content. The characteristics of multi-variant custom assembly require tool calling to adapt to exclusive parameter rules for different machine models, with calling logic adjusted for each type of equipment.
Configuration Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Workflow/API tool selection | Auto-trigger | Adapt to scenarios where assembly-related data is automatically called during bid document generation |
| Workflow/API function-call configuration | Enabled | Used to call structured data source interfaces such as BOMs and torque records |
| Maximum documents per single call | First 10 | Avoid overloading the single context and ensure tool calling response speed |
| Plugin timeout period | 120 seconds | Adapt to delay from pulling multiple data sources and prevent task interruption |
| Result verification threshold | Over 85% match rate | Ensure consistency between bid data and actual assembly parameters |
| File parsing format | Auto-identify based on uploaded files | Adapt to different types of assembly document formats, such as BOM spreadsheets and process card PDFs |
Three Common Mistakes
- Calling a specified interface returns a 500 error: A call to
/api/core/dataset/updatereturns a 500 status code, while the browser can access normally but the API call fails. Cause: Access permissions for the corresponding dataset are not configured in the workflow, resulting in failed interface authentication. - Semantic retrieval tool returns connection error: A "Connection error" message is returned when calling semantic retrieval and full-text retrieval tools, and assembly document content cannot be obtained. Cause: The data source address whitelist for the plugin is not configured, or network policies restrict cross-domain access.
- Doc2x tool call exception: A call to the Doc2x tool in FastGPT v4.9.1 returns a file reading error, with the error message containing an abnormal "result" field. Cause: The file parsing encoding parameter for the Doc2x tool is not specified, or the uploaded assembly document format exceeds the range supported by the tool.
How to Confirm Configuration Is Complete
- Trigger the bid document generation workflow in FastGPT v4.17.0, and check whether the tool automatically pulls the latest BOM, assembly process card, and other data.
- Manually call the configured plugin interface and check whether the returned results include specified assembly parameter fields such as torque values and gap parameters.
- Simulate a data source disconnection scenario and check whether the tool returns a corresponding error prompt without abnormal interruption.
- View workflow logs to confirm that the calling parameters for
toolChoiceandfunctionCallmeet the configured requirements.
The values provided here are common starting points and should be validated against local samples.