I agree, that first the requirements should be somehow collected. Reporting can be a pain in the ass in my experiences... In the simulation engine I added reports to show simulation results, there I use JasperReports (basiclly due to the fact, that I knew that much better myseld, so main evaluation criteria was Team Know-How ;-)), so this is already in the list of jBPM dependencies (if you want to use simulation reports). Pentaho is a very cool tool. I like expecially the OLAP stuff (Mondrian and the JPivot browser), you give the business analyst powerful easy to use tools. But the main problem here is to design the underlaying database layout / OLAP Cubes. If that is the goal of BAM (which I would say IS a part of BI) in jBPM, I would also start with these stuff first, and then select a reporting engine... About one year ago, we chose Jasper for a project, because support for MDX connections and Cross-Tab-Support was much better in Jasper... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111126#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...