What data for this category looks like
Data sources include EAM/CMMS systems, equipment sensor collection data, operator inspection records, maintenance history archives, spare parts inventory lists, and legal inspection records for special equipment. Data update rhythms cover scenarios such as completion of each shift’s inspection, weekly maintenance plan updates, and real-time sync during unexpected faults. Daily documents include equipment ledgers, inspection forms, maintenance plans, maintenance work orders, failure analysis reports, spare parts lists, and special equipment inspection records. Fields include equipment number, inspection point, failure code, spare parts model, inspection validity period, and more. Field units include unit, time, hour, day, and more.
What constraints these characteristics impose on workflow orchestration
Data sources for this category are scattered, and update rhythms vary widely. Workflows must be configured with multiple trigger nodes to match different data update timings, avoiding delayed or redundant data pulling. Field structures of multiple document types are inconsistent. Configure variables to preset field mapping rules adapted to each document, reducing format conversion costs during subsequent aggregation. Legal inspection information has a fixed update cycle. Set a scheduled trigger node to ensure the timeliness of inspection data. The accuracy of equipment health data directly links to production safety. Workflows must include a data validation step, to ensure core fields are not missing before entering the aggregation process. Additionally, linkage between maintenance work orders and spare parts inventory requires workflows to support cross-node data synchronization, avoiding mismatches between spare parts inventory and actual usage.
How to set up the configuration
This page is written based on FastGPT v4.17.0.
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
variables | Preset 12-15 core variables, including equipment number, inspection result, spare parts model, etc. | Match the fixed fields of daily documents in this category, reduce adaptation costs for cross-document aggregation |
nodeId | Set independent node IDs for inspection data pulling, maintenance work order aggregation, and report generation respectively | Facilitate quick location of corresponding workflow links during exception troubleshooting |
| Trigger timing | Trigger in three scenarios: after each shift’s inspection completion, weekly maintenance plan update, and when a fault occurs | Match the actual update frequency of data in this category |
| Data validation rules | Validate that equipment number, inspection result, and spare parts inventory quantity are not empty | Avoid invalid content in aggregated reports caused by missing fields |
| Log recording toggle | Enable workflow node execution logs | Retain the complete execution process of calls to external applications or plugins |
| URL parameter passing | Enable global variable URL parameter passing function | Support bringing dynamic parameters such as inspection batch numbers from external systems |
Three common mistakes
- No corresponding plugin-returned log content appears in the generated ledger aggregation after calling an external application or plugin in the workflow. The cause is that the workflow node’s log recording toggle was not enabled, so the call process was not retained.
- When trying to pass global variables via URL parameters of a share link, the corresponding dynamic data is not loaded in the report. The cause is that the parameter name to be passed was not declared in the workflow’s
variablesconfiguration, so the parameter could not be recognized. - Node execution times out when calling a custom Python code function in the workflow. The cause is that a reasonable timeout duration was not set in the workflow configuration, causing the code execution to be terminated before completion.
How to confirm the configuration is complete
- Manually trigger the workflow once, check whether the execution status of each node is successful, and confirm whether the document data of this category is loaded in the data pulling link.
- View the workflow’s log records, confirm that the process of calling external applications or plugins is completely retained, with no missing execution steps.
- Construct a URL link containing custom parameters, trigger the workflow, and check whether the incoming dynamic parameter values are loaded in the report.
- Verify that the generated report fields cover the key information of core documents such as equipment ledgers, inspection records, and maintenance work orders.
The values provided here are common starting points and should be measured against the reader's own samples.