About Me

My photo
I work for Fusion5 Australia . Connect with me on linked in here . I'm raising money for a good cause at the moment, follow donate to leukemia foundation

Tuesday, 2 June 2015

infographic for go-live

Technology has changed, we do not write about our successes in words, we use pictures.

Infographic’s are a nerds choice for not writing paragraphs.  I recently completed another go-live and decided to celebrate the usage with a pictochart:

I love a great piece of marketing, I must admit that I think that infographics are awesome for speaking across the many audiences that have something to do with an ERP go live.



Now, I must give a shout out to piktochart.com in their most simple free offering I was able to create a pretty cool visual summary that people could understand.  I’ve changed some of the numbers of this form to protect the innocent. 

So you can see from the above that there are some really nice pieces of data, some financial and some usage.  All of these were easily extracted from a series of database queries and also google analytics.  Some of the better statistics of course were gathered from ERP analytics.  For instance, we can tell how many ERP pages are loaded per day.  How many unique users log into the application per day.  We can tell how many times EVERY single JD Edwards application was run and how long they took to load.

We were also able to completely explain to the business that the end user performance was better, as we can tell average page load times per day, week and month.  This enabled us to unequivocally tell end user performance HAD improved!

To paint an accurate picture, performance improved, but we went to AWS in the cloud.  We went from pSeries enterprise and database servers to x86 linux.  We went from websphere to WLS 12C.  There was some massive changes! 

I think that the in memory 12C database option was the thing that saved us from some serious performance issues.

Nice UBE / Batch performance summary

This query will give you a performance summary of your batch jobs for the time period that you specify.  It’ll give you number of times the report|version combo has been run, average runtime, slowest run and fastest run.  That is pretty nice.  You can run this daily or weekly and do comparisons.  This is an advanced version that shows the “friendly” name too, so functional people will understand what you are talking about.

I’ve said here, give me the summary of jobs run between the 29/5 and the 11/5.

from svm910.f986114,ol910.f9860, pd910.f983051
where trim(jcpid) = trim(siobnm) and trim(jcvers) = trim (vrvers) and trim(jcpid) = trim (vrpid)
and TO_CHAR(JCETDTIM, 'DDMMYYYY') < '29052015' and TO_CHAR(JCETDTIM, 'DDMMYYYY') > '11052015'
group by jcpid, JCVERS, simd || vrjd ;