Media releases are provided as is by companies and have not been edited or checked for accuracy. Any queries should be directed to the company itself.

Beyond JD Edwards... an alternative

  • 22 March, 2007 11:50

<p>By Peter McCarthy, Consultant, Crossley96 P/L</p>
<p>Every now and again you come across something which is worth taking more than a second glance at, and this is one that I believe should be shared with my industry colleagues.</p>
<p>Just to put things in perspective you need to know that I’m a JDE devotee from a long way back, proud to have been a long term employee of the company for over 16 years as a Project Manager, Technical Manager and Senior Applications Technical Specialist. It was a great company to be part of and I enjoyed a fantastic time and made a lot of genuine friends among both work colleagues and customers alike.</p>
<p>Only recently have I embraced the ‘Dark Side’ by moving over to independent contracting, although still very much deeply entrenched in the JDE world.</p>
<p>I’ve come across a legitimate contender amongst the horde of sometimes questionable application software alternatives being offered to clients unsure where JDE’s future may lie under the Oracle stewardship. It’s a product called Odyssey, built by R &amp; D software company Mid-Comp International, headquartered in Melbourne.</p>
<p>I had worked alongside their CEO Steve Bridges at JDE in the early 90s before he and a couple of other guys started Mid-Comp, and we still bump into each other from time to time. Knowing full well that I make my living from JDE consulting, Steve asked if I would be interested in performing an independent assessment of Odyssey. He was looking for a ‘warts and all’ appraisal of Odyssey’s legitimacy as a JDE replacement, and wanted someone who would be honest and critical.</p>
<p>“Who better to pick over it than a defender of the faithful” was the gist of it, so I was off to Melbourne with cynicism locked and loaded.</p>
<p>World’s largest pure-JAVA app?</p>
<p>First up was a brief introduction to the Odyssey application content and an overview of the architectural concepts. Apparently Odyssey may be the largest commercial pure JAVA business application on the planet with over 24,000 classes (blobs of object programming code) and 800 .jsp (HTML) screens. Ho hum … low care factor … cynicism switched on &amp; fully operational!</p>
<p>For starters it is web delivered pure JAVA so there is the immediate departure from green screen / screen scraper / Windows interface look &amp; feel which was a nice start. Odyssey is visually very different, yet somehow comfortably familiar for the JDE literate and I was pleasantly surprised how quickly this transpired.</p>
<p>They have this concept of Business Rules Policies which makes just about every function configurable. The closest I can come to for a comparison is JDE Dream Writer, but Policies are more than that. Dream Writers are hard coded program switches relying on pre-defined value options existing within the base program, but Odyssey Policies are literally chunks of variable object code which get merged in at run time. If a client needs a new business rule, we just add another Policy to the ‘plug &amp; play’ mix … we don’t normally need to touch the framework layer (program base code).</p>
<p>It is very easy to navigate once you accept that the mouse plays a major part in navigation (as is the norm for web applications). You can also set up Jump To navigation similar in concept to JDE Fast Path, but different in that the Odyssey feature allows individual user definitions which can be added to or replaced ad-hoc by the users … all by themselves.</p>
<p>No need for predefined function key exits … easy to remember, easy to change, which means low stress levels for a newbie during training.</p>
<p>The assessment tasks were straightforward:</p>
<p>1. Perform the full gambit of normal daily transactions as you would for JDE:
a. sales &amp; Purchasing
b. inventory &amp; distribution
c. the corresponding accounting back office stuff (AR, AP, &amp; GL)</p>
<p>2. Try to break it</p>
<p>With about 15 minutes of familiarisation with the basic screen disciplines and application process work flows under the belt, my Mid-Comp minders let me loose on a publicly
available demo version called Odyssey to Go, and left me alone to fend for myself.</p>
<p>User manuals were provided under the “when all else fails, RTFM” principal, but we all knew that if someone with my years of experience needed to continually resort to the
Manuals, then the average end user’s frustration level would have already resulted in tears or swearing, so my going for the HELP would indicate a fail for that function.</p>
<p>My cynicism was taking a bit of a pounding…</p>
<p>I was pleasantly surprised to find that all the standard JDE operations I would expect to find in a distribution environment have been well and truly catered for here, and Odyssey in fact pleasantly exceeded my expectations. My cynicism was taking a bit of a pounding. There is also a lot of additional application functionality such as wireless EAN-way scan / pack, VMI, etc., which traditionally is third party bolt-on product for JDE users.</p>
<p>Significant thought has gone into keeping the screens uncluttered, which I’m told is the way it needs to be for high volume web traffic transactions. Coupled with a concept
Mid-Comp calls Inheritance Processing, this makes Odyssey functions fairly intuitive.</p>
<p>As an example, only four fields need to be entered by the user to perform a Sales Order (client ID, client’s reference, product ID, quantity). The rest are automatically propagated from what I can only relate to as process templates / defaults set up against a combination of the client, product, warehouse, order type, user, and financial company. The hard bit to get your head around is that these inherited defaults are hierarchical, and may have come from any level of the inheritance tree. The upside is that you can set up template models at every level of the tree to suit the business trading needs, providing unlimited ordering variations which the user keying the in order doesn’t need to concern themselves with… it’s all done with smoke &amp; mirrors.</p>
<p>What all this leads to is that if you can’t get a user working independently on basic Sales Order Entry in less than 15 minutes or so, then they may never get it. Sure, if they need to understand what they are doing beyond keying in the order then it may take an hour or so of basic training. Realistically the entire product follows the same philosophy:</p>
<p>Keep it simple wherever possible, and provide optional complexity when needed via radio buttons.</p>
<p>Anybody having had exposure to JDE will become familiar with Odyssey very easily indeed. The application suite is fairly comprehensive out of the box. The standard package is feature rich primarily because of the plug &amp; play business rule Policies.</p>
<p>In essence I’d give Odyssey the thumbs up, as I believe it is unlikely that there would be much worth griping about from the conventional JDE customer operating in the Supply Chain / Distribution sector.</p>
<p># # #</p>
<p>Peter McCarthy, Crossley96 P/L
Email: e-</p>

Most Popular