Beginner's Guide to Performance Reports
Process Performance Reports on his blog. Using Websphere Lombardi Edition, he shows a few diagrams and gives good advice regarding how to build up the tracked data for your process reports. Of course, if you’re not using Lombardi Edition (or various versions of Teamworks and IBM BPM), you might not be able to relate to these diagrams- they include the tracking point metaphor that Lombardi introduced way back in 2004 to allow for a transparent snapshot of process instance data. It really makes it trivial to capture snapshots and timing data for use in correlations in reports. John does say one or two things I’d modify, such as:John Reynolds gives a beginner’s guide to
Process Performance is all about “How long did it take?”. If you want to know “How long?” then you have to know when “it” started and when “it” finished.I’d say, rather, that this is one of the most common kinds of reports – and in IBM BPM, one of the easiest to produce. There are other quite interesting reports that are similarly trivial to capture:
- How many of X did each person on the team process by month (or by week or by day, etc.)
- How many exceptions (complaints/defects/etc.) did we process by customer or by region (comparing performance)
- How much rework is happening?
- What percentage is going down the happy path versus exceptions?
- What is the typical # of exceptions per item?
- How many exceptions get “fixed the first time” (ie, once known, the issue is fixed correctly).