Data Profile
Business data sources for SMT mounting and electronic assembly include customer-provided BOM, Gerber, and coordinate files, as well as MES systems, solder paste and component batch ledgers, mounters, SPI/AOI testing equipment, and reflow oven temperature records. Daily produced documents include changeover sheets, stencil usage records, first article confirmation sheets, SPI/AOI defect reports, maintenance records, and traceability labels. Data updates run in real time for each work order and each changeover. Fields include part number, reference designator, component batch number, mounting coordinates (unit: millimeters), furnace temperature curve parameters (unit: degrees Celsius, seconds), and additional relevant fields.
Constraints for Workflow Orchestration
Multi-source real-time data requires workflows to support node scheduling triggered by work orders, to avoid redundant data processing. Business documents in varied formats require workflow built-in format adaptation nodes to complete operations such as BOM field extraction and coordinate file parsing. Frequently updated work order data requires unobstructed data flow between workflow nodes, and support for using variables to store work order-specific parameters. Complex verification and defect analysis workflows need to be split into independent nodes to ensure traceability of exceptions in each step, while meeting field alignment requirements for process documents and exception reports.
Configuration Guidelines
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Trigger Rule | Trigger by work order ID, bind corresponding BOM and detection data | Match real-time data update rhythms for each work order to avoid repeated processing |
variables | Store work order ID, part number, component batch number, with a value range of 100–500 characters | Meet core field storage needs for SMT work orders, support cross-node data transfer |
nodeId | Assign unique identifiers to each format parsing and defect analysis node, use combinations of numbers and letters for values | Simplify log tracking and node exception localization |
| Maximum Single Processed File Size | 200 MB | Align with conventional sizes of PCB-related documents, prevent node timeouts |
| Exception Report Generation Condition | Trigger when number of defects ≥3 | Match standard exception reporting rules for SPI/AOI testing |
Three Common Mistakes
- Phenomenon: When a workflow node receives an HTTP request, the txt file field is empty, and subsequent processing cannot start. Cause: Variable binding is not configured correctly, and the file stream in the request is not mapped to the workflow's input node.
- Phenomenon: When calling a workflow in the robot, only a single independent workflow can be triggered, and multiple nodes cannot be chained. Cause: The workflow's nested call permission is not enabled, and dependency relationships between nodes are not configured correctly.
- Phenomenon: When exporting the workflow JSON file, the returned file content is missing some node configurations. Cause: Unnamed workflow nodes are not saved, or the export scope is not selected properly.
How to Verify Configuration Completion
- Upload test BOM and coordinate files, check if the workflow automatically triggers node execution.
- View the workflow variable panel, confirm core fields such as work order ID and part number have loaded correctly.
- Simulate SPI/AOI test defect data, check if the exception report generation process triggers.
- Use FastGPT v4.17.0 to export the workflow JSON file, confirm the file format meets standards and includes all configured nodes.
The values provided are common starting points and should be evaluated against the reader's own samples.