1
JD Edwards is not a
Cloud-ready ERP solution
The origin of this myth stems from the confusion between single tenant and a multi-tenant solution. A multi-tenant solution offers a single code base to multiple clients. In some cases, the database is common but data itself is effectively segregated based on the customer account. The architecture of this type of solution does not allow an option for on premises.
 

JD Edwards, on the other hand, is a single tenant solution. You can implement it on premises or host it at a third party location (including Oracle Cloud). The data is never co-mingled and the codebase is not shared with other customers. This means that you have a choice of implementing JD Edwards either on premises or in the Cloud.

There are pros and cons of deploying a common codebase across all customers and is a subject of a separate conversation. Essentially, SaaS (Software as a Service) is a commercial model, generally applied to Cloud-based applications, however, it does not guarantee a Cloud ready solution.
2
TCO (Total Cost of Ownership)
for a hosted JD Edwards solution is higher
Total Cost of Ownership (TCO) for any Cloud solution will typically include cost of - Infrastructure as a Service (IaaS), Platform as a Service (PaaS), Software as a Service (SaaS), and the Internet Service Provider.
 

JD Edwards pricing structure is not based on SaaS model; however, the IaaS and PaaS aspects will be an integral part of the fees structure for the JD Edwards Cloud option. While a SaaS pricing model minimizes the need for an initial capital expenditure, it does not guarantee a lower TCO over a five-year period.  A subtle difference: If a customer stops paying their annual maintenance (using a traditional license model), they have the right to continue to use their software (although it is always better to be current on the annual maintenance plan). If a customer stops their SaaS subscription, their access to the software will be revoked.


Finally, numbers don’t lie. It is important to objectively and comprehensively evaluate TCO over a five-year period after factoring depreciation and other factors, such as OPEX charges that can have a profound impact on the TCO.
3
Overall customer experience
is questionable
This myth is based on an experience of an older release of JD Edwards.
 

The release of latest version i.e. JD Edwards EnterpriseOne 9.2 has an amazing dashboard style navigation capabilities. The rendering using HTML 5 in combination with One View Reporting (OVR), Watchlists and E1 Pages makes JD Edwards EnterpriseOne extremely intuitive and natural.

The proof is in the pudding. Our recommendation is to take a quick look at the latest release of JD Edwards EnterpriseOne. JD Edwards EnterpriseOne 9.2 is a modern cutting-edge solution with a rich set of mobile-ready applications that come right out-of-the-box.
4
Future upgrades will continue
to be an arduous process
It is true that a SaaS application can enforce certain discipline around customizations.
 

It is possible to extend the same philosophy to JD Edwards solution, both hosted and on premises. An industry based template complete with a pre-configured solution will work for a vast majority of use cases. For those enhancements that genuinely support a competitive advantage can be isolated and hooked to the core system. This approach will make future upgrades extremely easy.

5
Integration with other Cloud applications
is not likely to be a seamless experience
Most large organizations will require multiple solutions (HCM, OTM, CRM) and some of these solutions are likely to be cloud based. There is no debate that seamless and robust integration between Cloud applications is critical for the overall productivity of the organization.
 

JD Edwards supports many integration strategies ranging from a direct call to JD Edwards business logic from an external system (XMLCallObject), Business Services, to the IoT Orchestrator in the 9.x release.

IoT is noteworthy as it allows the capability of parsing "Fast Data", analyzing it and then potentially triggering an action. A good example is of fast data received by JD Edwards IoT Orchestrator from a heat sensing device can trigger a work order when the temperature breaches pre-defined guard rails.
6
Not able to dynamically
scale up to peak demand
This is a myth as the ability to scale up during peak demand is the ability of computing power (CPU) in combination with the infrastructure, platform and internet bandwidth.
 

Most Cloud vendors will allow customers to sign-up for computing power for regular usage needs. Additional computing power (typically the monthly finance closing in the first week of month places heavy demand on the CPU) is dynamically deployed for an additional charge. In most cases, such usage-based model is cheaper than signing up for computing power at peak demand.

The subject of Cloud is riddled with hype and misconceptions. Rational thinking and common sense approach is needed to overcome the noise.
Want to know more about JD Edwards Cloud?
Connect with the Expert
Milind Joshi
VP and Head, Oracle JD Edwards Practice, KPIT Technologies
 
   

Terms of Use   Privacy Policy   Cookie Policy   Home   
Copyright © 2018 KPIT® Technologies Ltd.

CIN: L72200PN1990PLC059594