I think jBPM BI should be a mixture:
- Some "probe" mechanism like Tom mentioned on transitions as somehow
implemented by SeeWhy (but maybe less verbose for Ronald ;-))
- Some BestPratcises / Basic working examples for PEntaho integrations, especially a basic
cube layout and an Kettle ETL process for the jBPM log data
- Some BPR reports for existing log data for generic performance indicators (process
runtimes, task instance wait and run times, ...). This is what I think Heiko is working on
at the moment, right?
- Some KPI descriptions like I mentioned earlier. Even if this may be a lot of domain data
information, I think if the process processes this domain data anyway, it is not such a
bad idea to calculate KPI's already out of that and send better business events to BAM
(like SeeWhy does).
View the original post :
Reply to the post :