Data Structure for This Category
Daily documents for this category include control plans, patrol inspection records, SPC reports, final product inspection reports, nonconforming product review records, release orders, quality monthly reports, and others. Data sources include MES systems, online inspection equipment, laboratory systems, process parameter databases, customer standard databases, and historical defect databases. Data is continuously collected alongside production batches and shifts, including fields such as batch identifiers, inspection thresholds, defect records, and release status. There is no fixed unified format, so adaptation for multi-source heterogeneous quality data access is required.
Constraints Imposed on Workflow Orchestration
Multi-source heterogeneous data sources require the workflow to configure multiple independent data pull nodes to connect to different quality data sources individually. The high-frequency update feature requires workflow trigger conditions to be bound to production events, ensuring the latest inspection data is used. The diverse document types require the workflow to include built-in format conversion nodes to unify inspection records of different formats into standardized content usable for bid documents. Additionally, the business requirement of binding quality data with bid quotations requires the workflow to include data verification and compliance check links, ensuring only quality data from qualified batches enters the quotation preparation process.
Configuration Settings
This configuration applies to FastGPT v4.17.0, and specific parameters can be adjusted slightly based on on-site device response speed.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
variables | Use production batch ID as the unique storage key | Ensure that quality data passed across workflow nodes is bound to the corresponding production batch, avoiding confusion between data from different batches |
| Node timeout period | 600 seconds | Adapt to the time required to pull data from multiple sources including MES and inspection equipment, avoiding workflow interruption due to device response delays |
| Trigger rule | Bind to production batch completion event | Ensure that the workflow starts using the latest patrol inspection records and inspection report data |
| Parameter mapping rule | Match inspection items according to control plan fields | Convert standard inspection requirements into executable workflow node logic |
nodeId | Assign independent identifiers to each data source node | Distinguish quality data from different sources, facilitating subsequent exception troubleshooting and log tracing |
| Output format configuration | Align with bid document template fields | Directly generate quality certification materials that meet quotation preparation requirements |
Common Misconfigurations
- Phenomenon: Batch data stored in
variablesin the workflow is lost across requests, or confused with data from other batches, with abnormal global variable values shown in logs. Cause: No unique production batch identifier is bound tovariables, causing global variables to be overwritten by requests from different batches. - Phenomenon: The judgment node's matching rule only returns the ELSE branch, unable to trigger the IF logic, with the node running status showing matching failure. Cause: The matching condition was not set correctly during rule configuration, and a non-positive matching rule was mistakenly used for qualification judgment.
- Phenomenon: The workflow cannot obtain production batch parameters passed by the system, with empty node input fields. Cause: No system event parameters are bound in the workflow trigger configuration, or the parameters are not correctly mapped to
variables.
How to Verify Correct Configuration
- Trigger a test batch workflow, check the running logs of each node, and confirm that the batch identifier stored in
variablesmatches the test batch. - Simulate input of nonconforming product records, verify whether the judgment node triggers the preset review process branch, with the node status showing matching success.
- Check the document content output by the workflow, confirm that the quality data fields align with the requirements of the bid template.
- Trigger workflows for multiple different batches, check the
variablesdata of each node, and confirm that the parameters of each batch do not interfere with each other.
The values provided are common starting points and should be measured against the reader's own samples.