| Item |
Workflow |
BPM |
| Process Management Cycle |
Design and Execution |
Full process, including sorting, monitoring, and analysis |
| Target User Group |
Programmers |
Business and IT personnel |
| Platform-based facilities |
Process Engine Kernel |
Integrated Platform facilities such as processes, organizations, permissions, forms, rules, portals, monitoring, and analysis |
| Application Scope |
Department-level, more than 10 branches |
Enterprise-level multi-level process layers, supporting hundreds |
| Integration Capability |
EAI or integrated tools |
Extensive integration facility support |
| Application features |
Single applicationProgram |
Enterprise process-based architecture |
| Solution Structure |
Embedded in specific applications to meet specific business needs |
Complete solutions and templates for enterprise process cycle management |
Figure 1: workflow structure (WfMC point of view)
Figure 2: BPM structure (BPT view)
Who can translate the conclusion of a tongue twister? Workflow focuses on programmers, supplemented by design; BPM systems focus on business personnel, supplemented by programming. Workflows must be the core technology of BPM systems; workflows may not be BPM systems.