I
Very interesting article.
It seemed to be a little too quiet out there on the JDE litigation issues I
thought. It really is not surprising... it's just a fact that litigation will
most likely happen under the circumstances of that time, the introduction of
a new and very complex product. It's very possible JDE marketing took a
gamble on the timing of the introduction for competitive reasons, who knows?.
Though I must say, it is JD Edwards full responsibility to support and
correct the issues that may take place within their software.
From what I see so far, this is all based on 1997/98 events of OneWorld and
should not scare anyone at this point. OneWorld has come along way, and is
now a superior product partly because of those bumps along the way.
I was the manufacturing lead consultant on the second OneWorld implementation
which took place the end of 1997. It was a very interesting period for
OneWorld, and the manufacturing module. We did successfully install it within
six months (including an Agile integration) by keeping manufacturing setups
extremely simple, using only the functionality that was needed, and adding
the bells and whistles later. I also credit JD Edwards for their FULL support
as needed on that implementation.
Today, those same setups and testing can be done in less than half the time
it took then.... unless you're Big 5 of course.
John Paulson
Independent JDE Manufacturing and Distribution Consultant
JDEresource.com