BPM has emerged to a complex and extensive subject, nowadays based on theoretical and formal foundations. Therefore it's possible to evaluate proprietary systems and common best practices on neutral considerations.
As a kind of reusable design objectes, the Workflow Patterns identified and described by the Workflow Patterns Initiative since 1999 are a conceptual and tool independent basis for process technology.
This patterns could be sorted to various perspectives:
- Control-Flow Patterns
- Data Patterns
- Resource Patterns
- Exception Patterns
- Case Handling
- Service Patterns
Typical questions about real live processes could be :
- What is the most frequent path for every process model?
- How is the distribution of all cases over the different paths through the process?
- How compliant are the cases (i.e. process instances) with the deployed process models? Where are the problems?
- How frequent is the (non-)compliance?
- What are the routing probabilities for each split task (XOR or OR split/join points)?
- What is the average/minimum/maximum throughput time of cases?
- Which paths take too much time on average? How many cases follow these routings? What are the critical sub-paths for these paths?
- What is the average service time for each task?
- How much time was spent between any two tasks in the process model?
- How are the cases actually being executed?
- What are the business rules in the process model?
- Are the rules indeed being obeyed?
- How many people are involved in a case?
- What is the communication structure and dependencies among people?
- How many transfers happen from one role to another role?
- Who are important people in the communication (the most frequent flow)
- Who subcontract work to whom?
- Who work on the same tasks?
BPMN Style Rules