The world is full of data and extracting insights from this is always a challenge.
Patterns in data can assist us predict the future, there is no doubt in that. If you can determine a predictor for poor sales or poor performance, then this might enable to you be proactive the next time things occur. This is fairly cryptic, but what if I could tell you that the sales order entry screens were running less over the last 2 weeks and that the average lines processed by R42565 (invoice print) was also down over the last couple of weeks. Well, this is a good indicator that sales are going to be down too – but what if user behaviour was a lead indicator. What if you could see that activity was down and talk to your staff about why this is occurring. The same insights could be make in all modules in JD Edwards. Everyone is looking at the transactional data – I’m looking at the user behaviour.
At fusion5 we created ERP Analytics about 10 years ago, giving our clients some really great insights into their user behaviours. We’ve augmented this recently with UBE analytics, which allows you to see exactly what is going on in your batch job activities. You can see tows processed and runtime, critical for evaluating performance.
Now, the combination of these two tools can allow you to create the most insightful and simple reporting tools around your ERP. You can create reports on engagement time, trend data about performance or nice and easy to read gauges that all of you users can consume in e1Pages!
As you can see from the above, I have defined these custom controls in data studio to report on very distinct values. I’ve defined the graphs to have custom ranges, this is really easy in data studio
I can set colours [colors for my American readers], maximums and minimums for any piece of that I have. I can also filter the data.
In this instance, I can look at any data available from batch or interactive JDE usage.
Things that you can put onto any report or graph:
- How long a user spent on a screen (name the screen, name the user if you want – or group of users)
- How many rows a UBE processed
- How often a UBE is run
- How long a UBE took - and compare months, weeks or days
- How many times a version of a form has been loaded
- How many pages loaded a day
- Average server response time for loading forms in certain system codes – or all of them
Above is a list of the fields that are available for evaluating batch
Just some of the fields available for interactive
You get the picture, really easy to select the metric, define some ranges and GO!
Here we can see that I’m looking at the average runtime for UBE’s over the last week and have defined the ranges that are appropriate for this client. I could further refine this for UBE’s that I’m interested in, like invoice print, or sales update.
Here, you can see your report in JDE using e1pages
Those colours are terrible – employ the classic JDE blue - #1e4a6dff
Or specific information in JDE itself…
No comments:
Post a Comment