Tuesday, 7 February 2017

More ERP Analytics–how fast should my ERP be?

You know by now that we are able to patch your tools release so that you can understand how people are using your ERP.  You know you can slice and dice the data.  You know what screen is being used the most and what screen people are spending most time on!  You know this?

image

You can see from the above that I’ve shown for the last month for this client, the top applications (by page load), but also cross referencing that with page load time and also time on page – very different metrics.

So I can see the applications that are “busy”, but I can also see the applications that people spend most of their time on.  I can compare this on a monthly, weekly or daily basis.  I can also see what users are running the applications and time busy times of day.

 

Let’s look at productivity from another perspective:

Average page load time compares between two sites

clip_image001

and

clip_image001[4]

So we are comparing the average JDE page load time over an entire month across two different sites.  One has an average of .72 seconds (using data from over 313,000 individual page loads), the other has an average of 1.21 seconds for 281,000 page load samples).  Wow, is that significant?  I think so.

Do you think that asking ALL your users to wait on average another .5 of a second is appropriate?  NO WAY?  This is .49 of a second on average.  Now, the slower and smaller site loaded 544,588 pages in the month…  so if I could makes things quicker… on average, then I could get .49x544,588/3600 hours back.

74 hours of waiting around a month!  this is a pure lost productivity number – does not take into consideration user frustration.

Great, but what if you were worried about a particular application, then this could be measured also:

image

If you did make some changes, you could see how the performance has been affected, but also the time on page.

No comments:

Extending JDE to generative AI