[Design of JBoss jBPM] - Re: Analytical and operational dashboards
by kukeltje
You already mentioned those:
anonymous wrote :
| Number of cases processed in through a particular process definition
| - Number of cases flowing through a particular activity
| - Longest work item delay by activity
| - Workitems awaiting a particular task
| - Workitems in a specific worklist claimed and/or completed by a particular user
| - Longest end-to-end delay
| - Mean time to approve by activity by participant
| - Mean end-to-end completion time.
| anonymous wrote :
| |
| | And mean/avg should also contain stdv since that tells me more
| |
| | All this in 'windows' e.g. week 1-6 or feb-july. What is shown can be debated upon and may be even parameter as well. e.g. show avg duration on a day when compare weeks or just weekly averages
| |
| | 'longest' is not that interesting. avg and stdv are
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184107#4184107
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184107
15 years, 7 months
index problem
by Tom Baeyens
i see in hudson that my adjusted ensureCleanup results in a problem. i'll go after
it asap and check in a fix later this afternoon.
--
regards, tom.
15 years, 7 months
[Design of JBoss jBPM] - Re: Analytical and operational dashboards
by kukeltje
"heiko.braun(a)jboss.com" wrote : anonymous wrote :
| | So to me a full blown graphical console doesnt add much to end-users. It is more important to make the jbpm data available through an easy to use api
| |
|
| I don't agree with this. IMO the API is not necessary because it has a DB schema already, which is ready for consumption. Actually I think quiet the opposite of what you say. Adding an API atop of the schema would just narrow the possibilities to query according to users demands.
|
| However, it is right that customization plays a huge part here. But to begin with I think we should be able to define a set of common analytical and operational questions user typical ask and build that into a console.
|
What is important is that (from my experience) users want to drill down to individual case data when using the dashboard for both operational data and analytical data (if it is still available). Since we advise people not to put all data in jBPM (as opposed to other BPM suppliers to a certain extend), but use their own domain model and storage, there should be e.g. a basic api that returns all businesskeys related to that period or an individual case (a business key being the FK between the domain and the processinstance). That way users can analyse bottlenecks more easily. Since I cannot imagine the jBPM console showing the domain data, an api with basic methods does sound interesting. Users can embed the basic operational/analytical data in their own apps then. Basic being the keyword!!
For more complex analytical dashboards, I personally advice my customer (hope there will be more) to use a real BI/BAM (sorry) product like Pentaho or Jaspersoft, since they often need this for other analysis as well, but that is just me. And since I saw you are using jaspersoft, maybe things will turn around.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184009#4184009
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184009
15 years, 7 months
[Design of JBoss jBPM] - Re: Analytical and operational dashboards
by kukeltje
JBPM-2, you solved it, I reported it ;-) (as well as JBPM-1 btw)
anonymous wrote : That's a too unspecific. We can produce graphs of information that's put into relation.
| I.e. comparing the number of process instances this month with the number of process instances last month. And this for comparing weeks, days, is that to unspecific? It's just like downdrilling. Basic view is e.g. comparing months (like in the dow-jones...ahhh bad example nowadays ;-) ). Clicking on a month then you see the weeks of this month, or select start and end week (like a sliding window) and downdrilling shows a day with e.g. the hour as the unit)
anonymous wrote : In what context to problems appear?
Sometimes in the context of a month, sometimes a week, sometimes a day. And they are not always 'problems' sometimes it is detecting a trend so more people can be hired the comming day's. Current values (may different ones like number of instances, duration etc) visible in relation to the average of a certain period (which in turn is debatable)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183994#4183994
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183994
15 years, 7 months
[Design of JBoss jBPM] - Analytical and operational dashboards
by heiko.braun@jboss.com
This refers to https://jira.jboss.org/jira/browse/JBPM-2.
(Don't laugh, some day I can tell my kids "... and I did JBPM-2, really'")
Ok ladies and gentlemen, no more talking about BI and BAM.
>From now on we talk about the analytical and the operational dashboard.
The former offers analytical insights, mostly based on historical data, i.e. the number of process executions compared to last month, while the later will help monitoring operations, i.e. alerting when a job cannot be executed after a number of retries.
To begin with I'll wrap up, what people posted to the JIRA:
anonymous wrote :
| 1. jBPM should store the duration and start date of a state/process in the logs
| 2. Write some detailed info on wiki
| 3. Show processinstance and data
| 4. day/week/month overviews
| 5. near realtime data per process
| 6. produce graphs of day/week/month overviews
|
| Some more ideas i got from a requirements document...
| - Number of cases processed in through a particular process definition
| - Number of cases flowing through a particular activity
| - Longest work item delay by activity
| - Workitems awaiting a particular task
| - Workitems in a specific worklist claimed and/or completed by a particular user
| - Longest end-to-end delay
| - Mean time to approve by activity by participant
| - Mean end-to-end completion time.
|
anonymous wrote :
| Before going full blown on statistics a simple extensible audit trail would be nice, pretty much every commercial workflow toolset has this available in
| one way or another in both their standard clients as well as in their api's. So to me a full blown graphical console doesnt add much to end-users. It is more important to make the jbpm data available through an easy to use api set then to build a console wich wont satisfy all users. The current api command fails in my view on this one as it only offers an all or nothing aproach to getting processlog instances on a process instance....
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183956#4183956
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183956
15 years, 7 months