What this category of data covers
This category of data covers core production documents for manufacturing enterprise PMC, planning, shop scheduling and material control departments. These documents include sales orders, master production schedules, material requirements plans, weekly and daily production schedules, work orders, material shortage lists, and delivery change notices. Data sources include ERP order and inventory systems, BOM and process route libraries, equipment capacity ledgers, staff shift schedules, work-in-progress inventory, and supplier arrival records. Data update frequency varies with business rhythm. It includes daily and weekly updates, as well as real-time updates when orders are placed or exceptions occur. Document fields include process number, standard working hours, associated equipment ID, team number, and other related fields. Units include hours, sets, pieces, and other standard production units.
Constraints imposed by these characteristics on tool calling and plugin workflows
Multiple heterogeneous data sources require plugins to support standardized interfaces for different systems. This prevents extraction errors caused by incompatible data formats. Dynamic update frequencies require tool calling to support event-based triggering. This adapts to real-time needs when orders change or exceptions occur. Rich document fields require tool calling parameters to strictly match the fields of the corresponding documents. This ensures core production information is accurately extracted for process documents and exception reports. Complex scheduling and rescheduling logic requires tool calling to be bound to lightweight scheduling calculation plugins. It also requires support for quick rescheduling calls in exception scenarios, to avoid delays affecting production progress.
How to set configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Workflow/API tool selection | auto | Allows the model to independently select the appropriate tool based on the needs of the current process document or exception report |
| Tool call trigger timing | Trigger when order status changes or exceptions occur | Matches the rhythm of data updates tied to business events |
| Single tool call data limit | top 20 associated records | Avoids excessive data occupying the context window, while covering core production information |
| Workflow/API function-call configuration | Fixed format output | Used to generate standardized exception reports and process documents, ensuring field formats comply with shop floor management requirements |
| Timeout threshold | 300 seconds | Adapts to the complexity of shop scheduling calculations, avoiding process blocking caused by long wait times |
| Context window limit | 8000 tokens | Accommodates results pulled from multiple data sources, ensuring tool calls can obtain complete production information |
Three common configuration mistakes
- After calling a document processing tool, core formats such as process numbers and working hours in process documents are lost. This occurs because plugin parameters adapted to the shop floor process document format are not configured, and core business fields are not specified to be retained.
- Tool calls in the workflow have no independent selection logic, and all bound tools are executed directly after triggering. This occurs because the
toolChoiceparameter is not set toautomode, and trigger conditions for tool selection are not bound. - Fields in exception reports pushed via DingTalk webhook are missing. This occurs because corresponding fields such as material shortage lists and work order status from the scheduling system are not mapped to the webhook request body.
How to confirm proper configuration
- In the FastGPT v4.17.0 test environment, trigger a simulated order change scenario, check the tool call logs, and confirm there are corresponding data source pull records from the ERP system.
- Submit a simulated work order for a material shortage exception, check whether the generated exception report includes core fields such as material shortage lists, associated work order numbers, and expected delay times.
- View the workflow configuration interface, confirm that the
toolChoiceparameter is set toauto, and the tool list is bound to three types of plugins: process document processing, scheduling calculation, and message push. - Simulate a timeout scenario, confirm that the system triggers a retry prompt or alarm record when tool calls exceed 300 seconds.
The values provided are common starting points and should be measured against the reader's own samples.