Reply from mchinsky on Jul 27 at 3:31 PM I will temper this and say, you might find the perfect fit vertically, written in Cobol, barely scraped into windows and another solution, that's newer with a bit less functionality due to it being newer, but being built for the future and referenceable as well.
I would strongly say go with the newer solution from a 'future proof' standpoint. For example, say today, you don't see a need for mobile device sales, it doesn't mean you won't need it 2 years from now. Good luck retrofitting a practical application for this on an ancient platform.
| | | ---------------Original Message---------------
From: Bill Cary
Sent: Friday, July 27, 2012 11:31 AM
Subject: dotNET for an ERP Solution for a Small Company
Let me give you a slight twist on this - though it is hinted at in the various responses.
First and foremost, you need to decide which package provides the best functional fit for your organization. This is more important than technology. However if all things are equal on the functionality side, then technology comes into play. When you look at it you do want to consider it in terms of what does it do for you as a business person. Does the technology allow you to connect to other systems such as CAD or PLC with less effort and cost? Does it allow you to accomplish ERP tasks from inside your email on your phone while traveling? Does it extend collaboration into your supply chain? I can go on in this vein, but you get the point. So the bottom line is, if the functionality is a draw, and the .NET framework is being utilized to deliver business benefits that the other technology either doesn't support or does it with more cost to you - then it is an important consideration.
Bill |
| Reply to this email to post your response. __.____._ |   _.____.__ |
No comments:
Post a Comment