Hard to help without knowing more about your specific environment, but I would concur with Kevin - if you and your users are a Microsoft shop then Dynamics will probably win out on user acceptance in this comparison. This is a recurring theme in multiple case studies we have written.
You may wish to consult this white paper:
istart.com.au
You might also want to take a look at www.softwareshortlist.com - they will match your requirements against leading vendors and introduce you to them.
Senior Account Manager at a tech services company with 51-200 employees
Consultant
2015-03-19T14:44:06Z
Mar 19, 2015
I have a different take when choosing an ERP. Every ERP system has check boxes/features some a few more then other. More check boxes are not necessarily better (a good example of too many check boxes is Norton Anti Virus). Since, ERP systems have such a high failure rate, I concentrate my efforts on the amount of customizations that are needed, as well as the business rules engine that is available. In my opinion, ERP systems software is not why we have so many failures in the industry; I believe the failures stem from poor implementation and training. I have found, the more complex the system, the higher the cost, as well as more complications regarding the implementation, thus more failures.
Since I am involved with the sales of SAP and Katalyst-ERP I will withhold my comments on your choices. With that said, I steer my clients to the simpler solution. My Example: I can sell SAP (a complex system to implement and train) or Katalyst-ERP (a streamed lined system, that is a great deal less complex to implement). When we have issues with Katalyst-ERP we have the developer team involved in the implementation, business rules, and any customizations needed; for us this equals success. On the other hand with SAP we are like others at the mercy of the software company, no source code, poor technical support etc…
I hope this helps Joe Ciechomski
Head of ERP Services at a retailer with 1,001-5,000 employees
Vendor
2015-03-19T14:11:33Z
Mar 19, 2015
I have not purchased either but having looked at AX previously if the companies estate is heavily tied with Microsoft and also they have strong SQL skills then i can understand this but JDE has a lot of fans out there.
Application Manager at a manufacturing company with 51-200 employees
Vendor
2015-03-19T12:55:04Z
Mar 19, 2015
I can only really speak about Dynamics Ax as I have little knowledge of the Jd Edwards package.
From a users point of review we have had good feedback about most of the functionality. A few issues with low resolution machines and windows sizing but anyone that uses ms office should be able to pick up Dynamics relatively easy. The most difficult part is the data setup for financial and items.
I will not say Dynamics is perfect as it will require some development work in areas that should be out of the box. However, as long as you are careful with what is changed then the product should meet most requirements.
Just try to look at Business process change before changing core functionality. I have seen disasters where businesses try to amend the system to fit practices that are not within the Dynamics processes.
Hard to help without knowing more about your specific environment, but I would concur with Kevin - if you and your users are a Microsoft shop then Dynamics will probably win out on user acceptance in this comparison. This is a recurring theme in multiple case studies we have written.
You may wish to consult this white paper:
istart.com.au
You might also want to take a look at www.softwareshortlist.com - they will match your requirements against leading vendors and introduce you to them.
I also spotted this on this site - may be useful www.itcentralstation.com
I have a different take when choosing an ERP. Every ERP system has check boxes/features some a few more then other. More check boxes are not necessarily better (a good example of too many check boxes is Norton Anti Virus). Since, ERP systems have such a high failure rate, I concentrate my efforts on the amount of customizations that are needed, as well as the business rules engine that is available. In my opinion, ERP systems software is not why we have so many failures in the industry; I believe the failures stem from poor implementation and training. I have found, the more complex the system, the higher the cost, as well as more complications regarding the implementation, thus more failures.
Since I am involved with the sales of SAP and Katalyst-ERP I will withhold my comments on your choices. With that said, I steer my clients to the simpler solution. My Example: I can sell SAP (a complex system to implement and train) or Katalyst-ERP (a streamed lined system, that is a great deal less complex to implement). When we have issues with Katalyst-ERP we have the developer team involved in the implementation, business rules, and any customizations needed; for us this equals success. On the other hand with SAP we are like others at the mercy of the software company, no source code, poor technical support etc…
I hope this helps Joe Ciechomski
I have not purchased either but having looked at AX previously if the companies estate is heavily tied with Microsoft and also they have strong SQL skills then i can understand this but JDE has a lot of fans out there.
Sorry can’t really help on this.
Kevin Pilcher
Hi,
Theres is a very useful information in below link.
www.meritsolutions.com
Regards,
Ajay Kumar
Any specific reason to lean towards Dynamics AX and not even considering SAP ?
I can only really speak about Dynamics Ax as I have little knowledge of the Jd Edwards package.
From a users point of review we have had good feedback about most of the functionality. A few issues with low resolution machines and windows sizing but anyone that uses ms office should be able to pick up Dynamics relatively easy. The most difficult part is the data setup for financial and items.
I will not say Dynamics is perfect as it will require some development work in areas that should be out of the box. However, as long as you are careful with what is changed then the product should meet most requirements.
Just try to look at Business process change before changing core functionality. I have seen disasters where businesses try to amend the system to fit practices that are not within the Dynamics processes.
Hope this assists
Kind regards
Tony Bowyer