What this category of data looks like
This category of data comes from BOM, Gerber files, and component coordinates provided by the client, as well as factory MES systems, solder paste and component batch records, mounters, SPI/AOI testing equipment, and reflow oven temperature data. Daily retained documents include BOM and coordinate files, line change sheets, stencil and furnace temperature records, first article confirmation reports, SPI/AOI testing reports, maintenance records, and traceability labels. Data is updated in real time with each work order and each production line change. Fields include component reference designators, part numbers, batches, furnace temperature curves, testing defect types, and more. There are no unified fixed units, and they adjust based on the corresponding document fields.
What constraints these characteristics impose on the "workflow orchestration" link
Data updates in real time with work orders and line changes, so workflow nodes must support dynamic binding of variables to adapt to exclusive data for different work orders. There are diverse document types and inconsistent fields, so the workflow must support multi-source data access nodes to read content from files in different formats such as SPI/AOI reports and maintenance records. Data is closely linked—for example, component batches correspond to furnace temperature curves—so workflow orchestration needs to set association logic between nodes to avoid data mismatches across nodes. The consequences of errors are severe, so the workflow must add a pre-check link to trigger checks when verifying part numbers and reference designators, preventing batch mounting of wrong components.
How to set the configurations
These configurations are based on FastGPT v4.17.0
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
variables | Bind work order ID, component batch number, line change sheet number | Adapt to dynamic data requirements of each work order and line change, ensuring the workflow calls exclusive documents for the corresponding work order |
nodeId | Assign unique identifiers separately for SPI detection nodes and maintenance record query nodes | Facilitate troubleshooting of cross-node data transfer issues and accurately locate logs for corresponding components |
| Tool call timeout setting | 600 seconds | Corresponds to long-cycle data reading during SMT equipment inspection, preventing workflow interruptions caused by slow return of equipment data |
| Multi-source document access configuration | Configure reading rules separately for BOM, SPI reports, and maintenance records, read the first 10 entries once | Match the diverse daily document structures of this category and accurately extract required fields |
| Log storage threshold | 1000 MB | Retain sufficient MCP service logs to troubleshoot abnormal calls for maintenance Q&A |
| Model ID association rule | Bind preset models corresponding to equipment types | Adapt to inspection and maintenance Q&A requirements for different mounters and reflow ovens |
Three Common Misconfigurations
- Phenomenon: The tool call node returns the error Invalid JSON: Bad control chara. Cause: Special characters in line change sheets and stencil temperature records are not escaped, causing the passed JSON format to fail to meet requirements.
- Phenomenon: Tool call nodes cannot add connection lines, and no small circle connection points appear on the interface. Cause: The tool call permission for the corresponding node is not enabled, or
variablesbinding is not enabled in the node configuration, causing link verification to fail. - Phenomenon: Detailed logs of the component MCP service cannot be viewed in the workflow. Cause: Detailed log storage is not enabled in the system configuration, or the log query permission corresponding to
nodeIdis not associated.
How to Confirm the Configuration is Correct
- Trigger a test work order, check whether the workflow automatically binds the current work order's
variablesand retrieves the corresponding BOM and line change sheet data. - Call the tool node, verify that the passed document content includes correct fields such as component reference designators and part numbers, with no format errors.
- View the component logs corresponding to
nodeId, confirm that the MCP service call requests and returned data are complete. - Adjust the test component batch number, verify whether the workflow can dynamically switch to the furnace temperature record data corresponding to the batch.
The values provided are common starting points and should be measured against the reader's own samples.