Satya wrote:
On Wed, Jan 25, 2006 at 09:43:10AM +0530, Saswata Banerjee & Associates wrote:
Enterprise application is any software application that is designed to be used enterprise-wide. More accurately, it is a software that is using a centralised database and operated from different offices, different lans, wans, etc. These terms apply to large companies where there are multiple networks, multiple offices and the same application and data must be used and access from all locations or at least by a number of people.
An example would be the CRM systems and accounting system or an integrated ordering + inventroy + billing + accounting system (ERP ?)
They are also written by companies who refuse to let the "enterprise" application talk to any other software you may write -- no interoperability -- unless you pay them umpteen thousand dollars for an upgrade module.
If it's web-enabled, usually it's just an ActiveX control. IE-only.
vTiger (CRM), SugarCRM, CKERP (Groupware, Accounts, inventory, etc), WebERP (Accounts, Inventory)
We use these, all open source, all web-enabled, no activeX anywhere. Ofcourse, KG says they should not be used in enterprise environment as they are php based and therefore not secured.
There is another one called Compaire, but have not had time to use it. That is java + oracle based, but opensourced and webbased.
It depends on what you plan to use and what use you can make of it. Please remember that most of the applications actually running in enterprise applications space are legacy applications. They had to make do with resources and codes written at a time when the concept of connecting offices accross the globe and of interoperatability was alien. Most corporate customers will think twice before even looking at a proposal that touches existing and stable legacy systems.
I know of this, as I can see what is happening to my clients who are trying to migrate from legacy to new applications. I am quiet sure if the HODs had their way, they would dump the modern enterprise application software and go back to the legacy, even with its limitations. Just the thought of having to test each and every module and cross check output of thousands of different documents in the new software is mind boggeling. We did a costing system at a pharma company that took 4 months of continious testing and efforts for the managers to be comfortable that it is giving correct and accurate information which they can present to their board and decision makers. Now they are being asked to put in the same efforts as our software is being replaced with a new one at enterprise level. They are fighting hard to keep the one we wrote 6 year ago, even when we are telling them that the new software is better (not developed by us) and we will help in testing the system and ensuring that it is giving the correct results.
This is important to know because you will face the same problems when you suggest to any client to move to open source at enterprise level. Even with a software like SAP with milti-billion dollar companies and consulting organisations standing behind them, at ground level companies are scared of changing to the new software. With an open sourced software, it is worse. From the corporate decision makers' view point, if things go wrong, what happens ? Who is reponsible ? Even if someone takes responsibility, will I be able to recover from the loss or wrong decision ? Which alternate software will I use if this stops or is dropped ? How will we get the data back ? Will I need to get people to enter all the data again ?
Understand the commercial viewpoint, because without the support of corporate commercial managers (line managers), no open source software will move forward beyond OS and abstract tools. MySQL has been accepted because they have been able to address the issues and get major vendors to support them as integrated products with their own (in case you do not know, there is a customised version of MySQL for SAP called SAPDB or something). I can not think of any other enterprise level software that has made commercial inroads.
regards Saswata