What this category of data looks like
Daily documents for general mechanical equipment assembly include assembly process cards, BOMs, torque records, gap adjustment records, commissioning reports, factory inspection sheets, and packing lists. Data sources include PLM/ERP, part inspection data, assembly tool collections, test benches, MES, and customer technical agreements. Data updates occur once per device and once per order. Fields include material code, torque value, coaxiality value (unit mm), tightening time, and others. BOM structures vary across custom orders.
What constraints do these characteristics impose on the "workflow orchestration" link
Multi-variety order-based assembly means each device’s BOM and assembly parameters differ. Workflows must support dynamic binding of order-specific data, and avoid hardcoded parameters. Multi-source data transfer needs require workflow configuration to link parameters across system nodes. This ensures data from PLM, MES and other systems automatically syncs to validation steps. Each device’s assembly process has fixed process cycles. Workflow trigger timing must match each process’s completion node, to ensure defects are captured promptly. Non-standard equipment has differentiated validation requirements. Workflows must support flexible configuration of validation items, to adapt to quality standards for different devices.
How to set the configuration
This configuration applies to FastGPT v4.17.0.
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
variables | Bind fields from per-order BOMs, torque records, and gap adjustment records | Adapt to customized data requirements for multi-variety order-based assembly, avoid hardcoded parameters |
nodeId | Associate the IDs of PLM data nodes and MES assembly collection nodes | Enable automatic transfer of cross-system data, no manual entry of device assembly information |
| Timeout Threshold | 300–600 seconds | Adapt to network latency for cross-system data queries, calibrated based on actual measurements |
| Validation Trigger Node | After no-load commissioning is complete | Match core links of quality traceability, ensure defects are captured before factory shipment |
| Optional Parameter Configuration | Load dynamically by process type | Cover differentiated validation items for different device assemblies, adapt to non-standard device assembly scenarios |
Three common mistakes
- Database link workflows throw SQL errors that return no data. Symptoms include empty result sets or syntax error prompts. The cause is failure to bind
variablesparameters for the corresponding order, using hardcoded SQL query conditions directly. This cannot match each device’s unique BOM or assembly records. - HTTP nodes fail when calling peanut shell addresses. Symptoms return getaddrinfo EN errors. The cause is failure to configure network proxy settings for the workflow, or the peanut shell address not opening access permissions for the corresponding port. This prevents the node from resolving the domain name.
- Custom tool variables do not display optional parameters. Symptoms include no optional fields in the parameter configuration bar for HTTP call tools. The cause is failure to declare the optional range of parameters in the workflow’s
variablesconfiguration, preventing the tool from loading preset parameter items.
How to confirm the configuration is complete
- Trigger a simulated order workflow, check if logs from each node correctly pull BOM, torque records and other data for the corresponding order.
- Manually modify a simulated assembly gap anomaly value, verify if the workflow triggers validation alerts and records anomaly information.
- View workflow run statistics, confirm that data transfer duration for cross-system nodes falls within the preset timeout threshold.
- Test the parameter dropdown options for custom tools, confirm that optional parameter items match preset process types.
The values provided here are common starting points, and should be evaluated against the reader’s own samples.