At this point, I believe the database itself could almost be considered an API, it defines the data that could be reasoned on. Currently there is need to put a Java API on top of that, as it will become very difficult to create one that is both generic enough to support all use cases and specific enough to offer simple methods to end users. I do believe though that it could be useful to define a "minimal" schema (the minimal data that the db should contain to make it useful), and think about making that extensible so people can add more information later (and be able to use that extra information somehow in the analysis). Are there any plans to support business indicators (KPIs)? Because people usually don't really reason about "the number of process instances", more about "outstanding orders", "the time to complete an order", etc. This might be somewhat related to CEP: creating higher-level business events from lower-level process events. Just a thought for the future though, to support business users. Simple operational dashboards for admins are probably the first step towards that. Heiko: I'd love to hear about your ideas / technology / progress on this next week, you don't be surprised if I ask you that question ;) Kris View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184984#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...