Glossary · System coordination, integration and orchestration
Workflow engine
Also known as: Workflow management system, Process engine
German: Workflow-Engine
In software engineering, a workflow engine is a software component that executes defined workflows, sequences of automated and human tasks, by tracking their state, invoking services or assigning tasks to people, and handling waits, timeouts and errors.
- System integration
In one sentence
A workflow engine executes defined workflows of automated and human tasks, tracking their state and handling waits, timeouts and errors.
Example
A workflow engine runs the engineering change process: it routes the change request to design, quality and documentation, waits for approvals and triggers the release in the PLM system.
How it applies
- Engineering: Workflows are often modeled in BPMN or a domain-specific notation and executed by the engine, which persists the state so long-running processes survive restarts.
- Manufacturing: Workflow engines run approval processes, change management, deviation handling and electronic work instructions at the MES level. They are not suitable for real-time machine control.
- Change: Workflow definitions change over time; running instances may still use the old version. Plan versioning and migration.
- Documentation: Documentation processes, such as review and approval of manuals and change-driven updates, can run in a workflow engine. Document each workflow's steps, roles and escalation rules so participants know what is expected of them.
Workflow engine vs. rules engine
A workflow engine manages a process over time: steps, waiting and hand-offs. A Rules engine evaluates decisions at a point in time. Workflows often call rules at decision points.