Comparative study of Open Source ERP Systems

By 07030244018 Ravindra Nath Sharma SDM – 07-09

Symbiosis Centre for Information Technology (A constituent member of SIU Established under section 3 of the UGC Act 1956 vide notification no. F.9-12/2001-U.3 of the Government of India)



Apart from the efforts of me, the success of this project depends largely on the encouragement and guidelines of many others. I take this opportunity to express my gratitude to the people who have been instrumental in the successful completion of this project. I want to thank Mr SVK Bharathi (faculty and my guide for this R&D project) for giving me the opportunity of working on my R&D project under his guidance and for enhancing my ambit of knowledge to a greater altitude. I can’t say thank you enough for his tremendous support and help in spite of his busy schedule. I feel motivated and encouraged every time I attended his meeting. I thank him for patiently attending my queries between his busy schedules .Without his encouragement and guidance this project would not have materialized. I would like to show my greatest appreciation to the CTO Mr. Shyam Sharma Business Head and Chief Technology Officer (CTO) compugenius I am deeply indebted to my Director Ms. Shaila Kagal whose inspiring suggestions and encouragement helped me in executing the project. I would also like to thank my colleague Mr. Mahesh Panchal for giving me time to time reviews and their valuable thoughts. Especially, I would like to give my special thanks to God and my Family whose love enabled me to complete this work.


Chapter 1: Introduction 1.2 Objectives....................................................................................5 1.3 Scope...........................................................................................6 1.4 Methodology..................................................................................7 Chapter 2 Review of literature 2.1Open Source ERP.............................................................................................8 2.2 Popularity of Open Source ERP.......................................................................10 2.3Difference between open source ERP and commercial ERP............................11 2.4 Points to be kept in mind while choosing the appropriate ERP platform.........12 2.5Parameters for choosing dot net and j2ee for ERP applications........................14 2.5Parameters for choosing dot net and j2ee for ERP applications...............15 Chapter-3: Analysis of Problem under Research 3.1Evaluation Criteria for Open Source ERP............................................16 3.2Open Source ERP Product and Price...................................................18 3.3.1open bravo .........................................................................................20 3.3.2Compiere.............................................................................................23 3.3.3Tiny ERP..............................................................................................24 Comparision of features of three popular open source products.................25


...............................................31 References………………………………………………………32 Appendix…………………………………………………………33   4 ...................................................3Conclusion .....30 4......................................................................2Recommendations........1Findings.................29 4......................................................Chapter 4 4..

Compare the two open source ERP packages on the basis of evaluation criterion 5 .Comparative study of Open Source ERP Systems FPR Chapter 1: Introduction Summary of Abstract: Companies availing ERP services always face the hassle of paying a large sum of money for license fees. Blogs. Evaluation Criteria for Open Source ERP. Success stories. So more and more companies going for open source ERP the need of the hour is to define the evaluation criterion or the factors that should be kept in mind while choosing open source ERP by companies . 3. They continued in many areas like modification and deployment. which Open source ERP systems are best suited for companies along with its pitfalls. 1.the research will be based on the comparative study of the two most popular open source ERP packages into consideration with their parameters on which they are selected by the companies. Articles.2 Objectives: The objective of the research is to 1. We will also analyse the need of open source ERP in SME sector especially . It includes study of various white paper. News. Find out some of the issues concerning Open Source ERP for S.Then Analyze the companies who has adopted Open source ERP systems. additionally I’ll go through books & reference material Afterword it’s mandatory to study and compare Open source ERP systems / Technologies / framework . However open source ERP helped to remove this drawback.E'S by taking two prevalent open source ERP packages into consideration 2. First study Open source ERP systems by collecting data through Internet.M. It includes findings like.why open source is becoming popular in this segment of industry. forums & site. Case. This did not stop with the implementation process alone.

Then selected open source ERP projects are reviewed and classified according to these criteria. forum. The research will proceed in the following way as shown in the diagram 6 . the advantages of flexible systems are elaborated. Need: Different vendor claim that it is hard to adopt the open source ERP. additionally I’ll go through books & reference material Afterword it’s mandatory to study and compare Open source ERP systems / Technologies / framework. Articles. and Blogs. Groups) First I’ll study Open source ERP systems by collecting data through Internet.3 Scope: Open source ERP systems are often targeted to enterprises whose requirements are not covered by standard software. Working in the same direction. Along with its pitfalls. Besides the focus on flexibility. Case. But from developers perspectives it’s not that much hard also to customize that. In this work the suitability of current open source ERP systems for these enterprises will be examined. It includes study of various white papers. which Open source ERP systems are best suited for companies. 1. cases on open source ERP . Then Analyze the companies who has adopted Open source ERP systems. & Getting data from primary resources (Developers. Open source specific criteria for support. Similar circumstances apply to organizations that need continuous adaption of the software to changing processes and needs. Analyze. Success stories. News. forums & site. continuity and maturity are worked out.4 Methodology: This research is carried out by study.1. Starting from the question which opportunities a company has to support its processes with IT. It includes findings like.

improvements. 7 . It is finalized by preparing brief report. Finally study comes to end by Suggestions.Research results: The study of open source ERP & The problem solutions while adopting open source ERP along with comparisons with other packages. & conclusion.

Companies really find it taxing to pay the additional cess whenever a renewal is made to existing license system. Since they invest a large amount in the initial stage they find difficulty in paying again and again.1. All that the company has to do is to download the software and make use of it. 8 . All these have been completely done away with by the intervention of open source ERP. Review of literature: 1Methods to Implement an ERP System 2. Some of the features of Open Source ERP are as follows: 2.1. Cutting down the costs This is the first and foremost advantage of ERP. The good news is that the source code is also available in many a times.1Open Source ERP: The companies can download the software programs at free of cost and use them.Chapter 2 2.

The others find it convenient to make the necessary payments for the service rendered. However that does not become the only reason for the growing popularity of open source ERP applications. Some more reasons contribute to open source ERP popularity. Neither do they have to train the employees in a fully fledged manner. Firstly the accountability is solely on the part of the company as the vendor has little prominence in this whole. Some complexities Open Source is not completely free from limitations.E.2. The interpretations of the conditions are still unclear. Some of the reasons are as follows: 9 . This also implies saving of time. Even though it is acclaimed as free software that does away with the criteria of licenses there are many implied conditions which has to be dealt carefully.M. Open source gives everything readymade right from source code. Lesser dependence on the vendor Open Source ERP application not only brings down the costs but also reduces the dependence on vendor. In addition companies have their own inhibition that discourages one to go for open source ERP 2. The clarity has been increasing only after successive lawsuits. Companies don't prefer to go for open source applications due to cost alone. This debate continues endlessly in one end while in the other end the fact remains that ERP open source has made it possible for S. The companies have to approach the vendor for each and every petty issue. In fact this in itself is another form of saving. But it is not so after the intrusion of open source ERP. 2.1. Some companies feel that open source is not promising enough to meet the application deliverables.2 Popularity of Open Source ERP: It is a well known fact that open source ERP has done away with the concept of license fees. There are some issues which the company has to think twice before going for open source ERP application. Thirdly Open source has been found unsuitable especially for conventional applications that require the fulfilment of preset criteria.However this issue has drawn lot of controversies recently. They choose it if and only they are convinced that it will help them keeping their IT infrastructure and requirements in mind. The company need not wait till the vendor comes to sort out the issue. Secondly the company there is many legal issues associated with open source ERP.'s to enter the market owing to the cheap cost.

In this context open source ERP has helped in reducing the amount spent not only by way of offering source code and software programs at free of cost but also by easing the procedures. This does not necessarily mean diminish of open source ERP popularity. though there are lots of arguments for intrusion into one's privacy and sharing of confidential details. 10 . This is an advantageous feature made possible by open source ERP technicalities. 2. It is no exaggeration to say that ERP occupies a significant place in the budget of the company. Open Source ERP finds itself unacceptable in large companies that adopt difficult process though not in all cases. A partial ERP application is selected for the particular function/functions. The ERP vendor need not be called every time because the source code acts as a guide to the company. Moreover the company can carry modifications on its own just by clarifying with the ERP vendor. For e. Normally they stay in the company till the process of migration especially if the company is new and lacks a proactive approach to ERP. The common databases of these concerns have helped a lot.2. His services may be used only when there is absolute necessity. Open Source erp technicalities are also suited for member concerns from the same industry.2. This stage was often considered to be a troublesome one since there could be more clashes between the vendor and the company regarding the process. The remaining codes can be ignored.5. This has become possible due to open source ERP technicalities. 2. The intensity of these clashes could be than during the initial restructuring stage because the vendor will press for more changes now given that ERP has been experimented and the exact gaps and loopholes have been identified.g.2 Flexibility Open source ERP is more flexible that a partial ERP application.3 Easy to understand and use: A unique feature of Open Source ERP technology is that it can handle the functions without any complexities. But when it comes to ERP the codes can be selected based on the requirements. This is by and large the reason for small companies to choose Open Source ERP for their operations. It is also to be noted that this feature will be absent if the company chooses a proprietary technology.1 Bringing down the costs and doing away with Vendor's Dependence The amount of money invested in ERP deserves no special mention. Since the codes are readily available the chances of mistakes are considerably reduced even if they are not nil.5. the hospitals sharing the information about patients will find this service extremely useful during cases of emergency more so when a doctor takes care of a particular patient and he has no clue about his history.

2. Flexibility This important feature was found absent in commercial ERP. Even the licenses are available along with the source code. The prices do vary significantly but according to the size of the company and volume of business. 11 . This is a motivating factor to companies that shun the idea of ERP for the sake of price tags. It consumes a lot of time not only during implementation but in every stage of ERP process due to the nature of work involved.1Pricing Commercial ERP is an expensive package and suitable only for bigger corporations. Their usage modalities are rarely liberal and cause troubles when they are modified.1 Duration. He is later blamed for inflating the costs. in the future. 2. The greatest advantage of Open source ERP application is that it is available at free of cost. The user can learn the rest. When it comes to security open source ERP is less risky when it comes to bringing things under public domain.5.3. Some orientations on how it all works wills do. Instead of modifying those in wake of the inherent difficulties companies had no other choice but to change their way of business. 2. This feature is unknown in open source ERP as everything is free e. One of them is referred as commercial while the other is called open source ERP. . In any cases they have been found to be extremely costly irrespective of the quantum in which they are purchased. This was often a debacle even though it was argued that the best ERP were designed for the best business practices. These packages are not subject to flexibility and moulding.commercial and open source ERP have lots of differences. In the case of commercial ERP vendors don't disclose the prices initially for it would make any sane person to refuse the order.3Difference between open source ERP and commercial ERP Enterprise resource planning is available in two states. Dependence and Results The time allotted for implementing open source ERP is very less when compared with commercial ERP than open source. 2.3. Another major allegation against the package is that they consist of lot of hidden costs. It was a difficult task to make them suit the working pattern. Hence the deployments also turn out to be costly and inconvenient due to the procedures involved. In fact no amount of formal training is required to run an Open Source ERP application. This essentially makes sure that the procedures for training are very easy.3. The innumerable number of complexions in commercial ERP calls for longer time span. He gets to learn unlearn and relearn during the course of working. Some of the differences are as follows: 2.4Training and security The training part of open source ERP is negligible.

3 Security Commercial ERP systems are less secure when compared with open source erp applications. The productivity is also high in open source ERP systems and the failure rates are very low. The results are also bound to be effective because the user gets to learn through the process of self teaching. They are by and large prone to the traps and pitfalls of hackers (no matter however tight is the segregation of the components). Since open source is a (self) built in process companies rely less on vendors and takes care of needs by themselves. 2. However the fact remains that they are not recognized well in the market for fear of failure as customers are still prepared to pay for results.3. 2. There are lots of controversies regarding them.4 Conclusion The differences between commercial and open source ERP applications show the Edge enjoyed by open source ERP players.3. If they don't give the necessary impetus the results will be poor. Similarly the companies are largely debating the validity of training sessions designed and handled exclusively by the ERP vendor. 12 . On the other hand Open Source ERP does not require much training. It calls for lots of investments in terms of time and money. This is another way of reducing the level of dependence on the ERP vendor.2Training Lots of training is required for using commercial ERP.Even though open source ERP makes everything transparent and available in the public domain it bring into the notice of user whenever something goes wrong.3. They can go a long way only if the awareness is high (which is encouraging in the current scenario).When it comes to the question of relying on the vendor the open source ERP vendor enjoys a considerable edge than the commercial ERP. 2. The source code is more than a training manual. The company need not spend much on training and makes a minimal utilization of the resources.

13 . The designs should be in such a manner that they can be used freely either in integrated or distributed applications.4. By and large the features should not be subject to any amount of rigidity. This helps to increase the comfort zone psychologically and technically because of the feeling that the platform has demonstrated competence in ERP. The more they have been tried and tested the greater is their credibility. The platform should basically allow fee flow and exchange of data between the networks and be applicable to work in the latest atmosphere.3. This problem is an unavoidable one especially in the introduction stage. 2.5.4. 2.2. 2. The preferred ERP platforms should resist the errors that come during the procedures. The preferred ERP platform should have the capacity of being tuned well within the company's environment. Prior experience with ERP The company should check if the platforms in question have already been experimented successfully in an ERP environment. Effective outputs The ERP platforms should contribute valuably to the output. This will help in easily working with the existing systems rather than going for a new one. However there are other factors to be considered in this regard. Networking facilities The organization should consider the channels used for disseminating information and its relevance with the platform in choice. Thing will become worse if the preferred ERP platforms are also of the same stature. Therefore the designing part of the platform will be able to speak for itself only if they are done unequivocally. The ERP platform will be retained only if they are satisfied that it justifies the costs incurred.4.4.2. The system should work well and be able to balance the flaws that arise during procedures. Proper designs ERP applications are often more than complex and taxing. even though they may be due to some functional component and not directly connected with the platform.4 Points to be kept in mind while choosing the appropriate ERP platform: The company has to exercise lot of care in choosing ERP platforms. All platforms are bound to face struggle while working in the introduction stage. Companies normally tend to go for a platform that is akin to the current work scenario.4.4. Sustainability The company needs to be assured that they can implement this platform for a considerable longer time. Some of them are as follows: 2.1. 2.

They can be taken as parameters for assessment but to take them as deciding factors will not suffice.2 On the basis of strength The term strength is to be analyzed in two connotations. Conclusion These general characters need not necessarily suit every company. The company should as well take all the relevant internal and external factors in to account to decide on this matter before choosing ERP platforms.5Parameters for choosing dot net and j2ee for ERP applications: The battle for supremacy for ERP platforms choice goes uninterrupted others. The man-hours allotted by the company are also taken into account in this context. 2. Since change has become an incredible element in organizational provisions have to be always made keeping the future in mind.6. It is a critical decision for the companies. Firstly it denotes the platforms and applications put into use. Similarly the fates of these two companies are also unpredictable as they keep constantly improving their functions and scope. On the other hand they choose ERPj2ee if the platform happens to be windows. if the number of persons is 90during the time of implementation but the company thinks of an alternative to go for 290 or 14 . Assortment of related levers The company has to not only check the comfort level of the platform with the main applications but also with the supporting levers. Any company will aim at obtaining a platform that can satisfy both these conditions. Since they go in hand during the process it becomes important to give them the due attention. 2. Secondly it denotes the systems advocated by the company to keep abreast of the market trends. Companies generally have a tendency to go for ERP dot net for Windows platform.G.Some parameters taken into account by the companies are as follows: 2. It is advisable to go for j2ee when the overheads exceed 290and more.4. For E.1Working pattern There are two factors that generally constitute the working pattern. This is important in ensuring that there are no hassles in when the entire operations are set in motion. The monetary factor.5. Firstly the company has validity of using applications with reference to the current level of operations anticipated in the future.5.2.They can be used even beyond that stage but the comfort level will decrease. financial strength of the company besides the budgetary policies have a strong hold in deciding these two factors. to see the and those the future behaviour Dot net can be used comfortably if the number of people working in the systems is around 90. There is a particular reason for laying overstress in component.

The general connotation is that J2ee developers are at least 5% more costly than dot net developers. However the companies company needs to evaluate the price in terms of the facilities offered by the platforms. On the other hand other platforms will have those facilities as an option. In addition the company needs to decide if it is going to develop from the existing systems or invest on a new one altogether. Otherwise they can go for ERP dot net. 2.more in the next six months the company can either wait till then if the expansion is not confirmed and then decide on the platform. Frankly speaking both applications are highly expensive. The money payable as salary or professional fees to the consultants and specialists employed on project basis is another factor. Some platforms will have default facilities which might be of no use to the company.3 Cost of the platforms The company needs to find this out initially and match it with their budgets and requirements. ERP platforms choice is crucial in this aspect.J2ee continues to top prices in all areas including setting up and procurement charges.5. 15 . On the other hand if the expansion is very likely the company can straight away go for ERP j2ee applications.

Open source ERP solutions are particularly easy to customize. making it easy for users finding information and connecting it to the business process they are managing in the ERP information system.1.2. 3.1. creating customer.Chapter-3: Analysis of Problem under Research 3. Also. of course.4.3. That is true.1Evaluation Criteria for Open Source ERP 3. Besides core processes. intuitive. 3. 16 . developers activity might vary over time. It’s important to consider the development activity in the months prior to the time the decision about the open source ERP solution is made.1. It is vital to identify the unique strength of each open source ERP solution and decide which one fits your business requirements best. maintaining customer orders and sending invoices are integral parts of ERP systems. Functionality All ERP packages are expected to support core business process. these solutions are written in popular. clear. For example. software vendors go bankrupt and support and maintenance companies discontinue operations. many open source projects do not last many years.1. One ERP solution might be very good at managing manufacturing operations. It is also important to evaluate how easily customized code is migrated during software upgrades. widely used computer languages such as PHP and Java. while another one will have a robust accounting module. Customization Complexity No matter how comprehensive an ERP solution is.1. User interfaces should be clean. However. enabling users to be as efficient as possible in their daily tasks. modern technologies make it much easier to build pleasant user interfaces. 3. vendor and products master records. The good news is. since the source code is freely available. Development Activity Unfortunately. since the products are open source. User Experience Although many older ERP solutions do not pride themselves in their user experience. effecting rate of bug fixes and new features development. offer context-based help. for non open-source software as well-smaller software companies are bought and products are discontinued. customizing the software is inevitable. the source code is available and you can continue developing the product to fit your specific needs even if the official development of the project stopped. ERP solutions vary widely. in any given open source project.

You must consider early on future growth rates. An open source ERP can never provide that level of integration support. database files). These are often the factors that differentiate mature open source ERP solutions from others. your vendors’ ordering system.1. spreadsheets. That is especially true for ERP implementations . allowed downtimes. system availability is not 100% or the system shuts down because the database is full. that step can take months if not years. Open source ERP solutions should provide a flexible migration component. using XML files to import and export data such as customer and product records is the de-facto standard in data exchange. stopping low quality data from entering the new system and an exception reporting tool. ability to scale to large numbers of records. allowing import of data from multiple sources(text files. security features.1. high availability options. Knowledge A key success factor in any kind of information system implementation is knowledge around the product. For large ERP implementations.mail servers. acting as a gatekeeper. For example. New open source ERP solutions do not always have enough experienced consultants that can help customers bring out the highest possible Return On Investment. Hopefully.suddenly. great software products are not successful because there are not enough professionals who know how to implement the product. cost of lost data etc.5. a poor migration can bring an ERP project to failure. Still. Too often. an ERP system will help the business grow to a point where this issues will rise .a validation layer. Migration The first step of most ERP projects is migration. What it can do is use standards which are supported by other software vendors to enable painless integration. but are of equal importance to any business software -performance.csv.8. the amount and complexity of data to migrate from older systems to the new ERP system is much smaller. 3.6.the complexity of the project and the varying requirements from one project to another requires strong knowledge of the ERP software being implemented.1. creating a new customer orders or displaying an inventory report takes 10 seconds instead of 1 second. your shipping companies’ software.usually a huge bundle of software components that manage that integration. In commercial ERP solutions. and recovery procedures in case of system or database crash. 3. Integration Every ERP project requires integration. user management and access control. especially by small and medium companies. The open source ERP solution you will use will need to communicate with other software systems . Production readiness is commonly overlooked.7. 3. 17 .3. Production-readiness We use the term production readiness as a placeholder for a set of requirements that has nothing to do with functionality. Exposing functionality as web services and being able to consume web services from other systems is also becoming increasingly popular.excel files. since the volume of transactions and data stored in the ERP system is relatively small.1. For smaller companies implementing open source ERP solutions. the integration is handled by middleware .

It refers to the software programs that can be copied and reproduced Without even paying the license fees. writing large amounts of great code. the higher chances of success for an open source project.3.a thriving.9. money you can invest in customization. You can be sure of one thing . bug reporting and support forums.M.M. will save a lot of money on licensing the software itself. There is a long debate between supporters of open source software and commercial software vendors over the question “How much does free. open source software.E'S are as follows: ERP'S intervention in S. Also. without being paid! It sounds crazy. All successful open source projects have one thing in common . Issues concerning Open source ERP in SME'S Open Source applications are tools that has made it possible for S. most are free to download and use-you will still need to customize the software and require some consulting services. not always.10. Almost all open source products are free to download and use. ERP has turned out to be the apt solution to meet the fast-moving channels in the corporate sector.E.M. The larger the community. spanning multiple time zones. There was no looking back especially when the industries suffered from dearth of connectivity and communication. However there are some restrictions and the question of proprietary or nonproprietary technology comes to the picture in determining the judicious use. There are many nuances of 18 .O Open source is free. Well. but it’s true. the list above is a must in your checklist of evaluation criteria for open source ERP solutions.C. actually costs”.1. support and maintenance. Proprietary and Non proprietary technologies The two major types of Open source are classified as Open source with Proprietary technologies and Open source applications with non proprietary technologies. The subsequent applications only increased its scope.1. Some of the issues concerning Open Source ERP for S. supplying everything required to support wide adoption of software-not only development but also documentation. diverse community. but some some are not. Although there are some other criteria you might want to consider. 3.'S ERP was enjoying a large segment among big players. However as stressed earlier it was not possible to cater to all the sectors.E. consulting.'s to realize their ERP dreams. Community The open source movement is all about community. This has done away with the hassles faced by the companies. A group of people working night and day.

On the contrary they can choose only those applications required for their daily routine. Thus proprietary technology poses some restrictions to the users’ . Moreover even if bigger companies copy the entire software verbatim the idle functions may cause extra storage process and may even disturb the process. Open source and S.M.M. This is not only because of cost but also due to other practical difficulties. Their operations are extensive and hence they may only need more than what is available in a particular software.E. This happens to be a main advantage for an S. This neither imposes many precincts like that of the former. Small and medium industries cannot afford to install large applications. They have to invariably select all the functions from software irrespective of the fact whether they are useful or not. On the other hand the autonomy of choice is available with S.On the other hand non-proprietary technology is devoid of the restrictions.E's.'S There is a considerable advantage in using Open source applications in S. When compared with bigger companies. There are many more nuances of open source ERP.E.These technologies determine the extent of usage and scope of open source applications. 19 .M. Proprietary technology prohibits the copying of the software except for some conditions.M. Open source applications can help the companies to reduce the technicalities by offering comprehensive solutions on need basis that is the company can decide to make a copy of only those functions required by source ERP . The company need not necessarily take a note or install all the functions of software.E'S. These limitations don't find a place in S.M. In this context it becomes wiser to use open source applications that can serve the dual purpose of reducing (or not even paying) the license fees.E.'S.

XTuple xTuple offers 3 editions . Their SaaS ERP offering is sold for 140€ per user per month. The Standard edition goes for 25$/User/Month and the professional for 50$/User/Month. Development model of OPENBRAVO Openbravo follows a development model that combines elements of agile programming with aspects of a traditional waterfall development process.000€ for unlimited users. the latter 2 being enhanced. We then add the feature to our queue of requests. Openbravo Openbravo provides a single paid edition (’Openbravo Network’). allowing you to choose which modules you want to use and pay for. we do a quick initial assessment to roughly estimate the amount of effort required to implement the feature. Standard Edition and OpenMFG. Average price is 100€ per hour. For Postbooks. They are currently the only open source ERP vendor to offer that. a free.Postbook. OpenERP Support Plans OpenERP is also offering a SaaS ERP (ERP on Demand). This process balances three elements: how well understood a feature is community priorities and development capacity. 4. 2. for example. For 5-19 users. When we receive feature requests. the price is 500$/User/Year.000€ for the first 5 users and then 500€ per user. They offer both Standard and Professional editions. At the beginning of a release. Compiere Compiere has been offering commercial editions of their ERP product for a long time now. the open source edition. depending on the number of users. open source edition. OpenERP (Former TinyERP) OpenERP does not offer different ‘editions’ of its software. commercial ERP versions based on Postbooks. 3. They have a very flexible pricing scheme. Prices are 5. They currently offer a promotion price of 10. per year.Open Source ERP Product and Prices 1. developer targets an appropriate set of features that he wants to build. but they do offer different support packages. going all the way down to 100$/User/Year for 200+ users. xTuple offers varying prices for support and services. which is a really good deal if you plan to run more than 20 or so users. 20 .

At the beginning of each iteration. Open bravo is not focusing now on micro companies (SoHo) (with less than 5-10 employees). The source control system is SVN Scripting languages Openbravo does not directly use any scripting language. SQL and PL/SQL. say between 10 and several 100 employees who have the need for an integrated management system.The target clients are small and mid-size enterprises (SMEs). at the end. Another new customer is a Spanish consulting company focused on implementing open-source software solutions and outsourcing to final customers with more than 200 employees and Euro 20 million (AU$31.6 million) in revenues. he develops a functional specification and then break down the project into sub features. Recent customers One of newest customers is a company focused on the sales of food products and logistics to professional clients like hotels. And there is also a media company that focuses on economic and market information about companies and industries in Spain that has recently started using Open bravo. and the like. which are completely served by major players like Oracle or SAP. Largest customer base (sector wise) Open Bravo has mainly mid size enterprise customers in four key industries: manufacturing. it belongs to a large Spanish retail chain with around US$8 billion (AU$8. but felt a standard solution was not for them. He decide which sub feature to build next and we assess whether the whole project is still on track to complete in time for the release.87 billion) in revenues. Development environment: Openbravo is developed in Java. but. restaurants. Active from three locations. Java coding and debugging is done in Eclipse. Apache Ant and Tomcat installed. PostgreSQL or Oracle. professional services and media.For each feature. Our user interface implements AJAX using the DOJO library. Most of developers work on a Linux machine with a database. which usually can't afford an ERP or large corporations. 21 . We work closely with the DOJO project and occasionally we make changes to the DOJO JavaScript code. the Java Development Kit. distribution & logistics. The release development cycle is broken into several iterations. our product embeds a standard version of DOJO. Target market Open Bravo’s largest customers are mid-size enterprises (Over 100 employees).

Future plans of Open bravo Actively building the distribution channel. The application server contents business logics and it is still implemented in open source J2EE application server JBoss. For example customers could use part of the information system of client or is possible that remote connected employee can use this HTML option. Compiere can run on many platforms: Linux. OS X. Microsoft SQL. focus on scalable products to facilitate rapid growth Fostering dissemination by reinforcing communication efforts Continuing to build the team with top-tier professionals Opening limited number of offices in strategic locations around the world (as of 2008) Compiere: Compiere can demonstrate advantages and drawbacks of open source solutions from the point of view of a medium size company. IBM DB2. 22 . and Solaris. Architecture and technology of compiere: Compiere is 100 percent Java solution based on Oracle technologies and J2EE standards. too. Advantageous use of this client is the case where the installation of fully featured client is not possible or suitable. The alternative HTML client could be use for smaller volume of processing and it has almost full functionality like a Java client. Client is completely created in Java and it communicates with the database by JDBC protocol. Windows. with partners around the world Fostering localization of Open bravo ERP to facilitate entry in new markets Further developing the ERP solution to enhance functionalities Introducing value-added products and services based on the ERP. Postgres. Other J2EE servers are planned. It means on the server and client side. with the application server by RMI methods. The architecture is as for platform independent and in the last release of software the independent database layer was modified to support many databases: Sybase.

This concept is called “Fail-safe transaction”. The user and the administrator are alerted by system as for faults. It allows the user to use it for himself. 23 .1). The originally closely connected processes are separated from one another and processed by asynchronous way and the system checks the finishing of all processed branches. Some license conditions of distribution must be observed (for example using of object name. Application logic is strictly separated from the presentation layer and is described in so called “Rule engine”. Without these tools client can hardly follow the actual version. Implementation and maintenance cost of compiere: Compiere is distributed under Mozilla license (MPL 1. Due to used technologies the application of Compiere requires a system specialists for Oracle and partly also for application server. One of them is still big dependence on commercial database Oracle. etc). Compiere offers migrating tools included in annual fee. The application can be modified and these changes are allowed to be sold without any duty towards the open source community. and clients. But Compiere also includes next hidden costs. but the system can continue processing. this variant is not sufficient for real installation.Architecture of compiere The Structure of the whole system is implemented with huge independence of particular objects. his partners. Only the main task influences the work of user. adding license text to sources. Although Compiere supports Oracle Express. Subsidiary faulty processes do not block of user.

small and medium enterprises having up to 150 employees in the sectors trade. MRP (manufacturing resource planning). Client works with the system by means of personalised environment. Lots of charts and graphics types are available. In any case the client must become aware that it is not just the simple system installation but the company own processes must be compared with preset once in application very thoroughly and their modification. User’s environment is generated on the basis of rules and therefore the application is stabile and consistent. The modules available are accounting (inspired by Sage 100). Tiny ERP: The user interface of TinyERP is comfortable and well designed. sales& purchases (delivery. point of sale). Compiere product includes processes in unified application more than the set of traditional independent ERP modules. marketing. Thanks to supported CRM features Compiere is flexible enough to be used for various businesses. User can reorganise input form. mail reaction. Time-demanding user’s inputs are replaced by the defaults and by selections from once entered data. field names or hide unimportant data or add specific helps. 24 . there are some special purpose modules and a interface to ecommerce application Modules can be installed partly in TinyERP.In spite of the fact that Compiere specialists say. we can hardly agree. It is targeted to micro. The concept of so called application dictionary assures quick changes and fluent run of application. User’s access to data and processes are controlled by elaborated security model. Accounting server and workflow server are at disposal for the user and they provide planning and processing. project management. sales management. because the system is so complex that its implementation is not possible without deep knowledge of logics and functionality. MRPII. change fonts. parameterization. purchase. adaptation for concrete user must be taken in account. He can also add new fields validation criteria. alerts or document printing. human resources. Additionally. inventory control. The user can add whole modules with minimal risk of application destabilisation in standard way and user profits of standard user’s environment and standard security model and standard databases. distribution and service. Business model and application functionality: The case of Compiere. CRM. that the system implementation takes just a few days. when the application framework is the integral part of system and the whole application is developed by this framework. as for accounting record and warehousing transaction or processing of customer’s requirement.

Spain. Schemes for Belgium and France can be delivered. Partners also do module development. Romanian. Czech. Polls on new wanted features are also conducted there. Albanian and Dutch.Customization Forms. A detailed change log is published in the download section. Tiny ERP is customizable via the client in Administrator mode. Server side translations are available in Spanish. There is no public roadmap available. All logic and data stems from the server. A brief public introduction to module development is available online. The client is based on the multi-platform GTk+38 toolkit and provides a “fat” client like rich GUI. Access to the concurrent code versioning system is available only for partners. Forms and workflow are customizable with XML files. The installation (38Pages). Portuguese. reports and workflow development are supported without the requirement of programming. Internationalization The translation of languages lies mostly on the server side and to a small part on the client side. Architecture TinyERP uses a self-developed proprietary server. Most contributions concern translation and bug fixing. Chinese. Project structure TinyERP is run by the Belgium company tiny sprl39 which employs five developers. Documentation A Wiki is used for collaborative documentation authoring. It is mostly used in French-speaking countries. TinyERP supports multiple accounting schemes. Transparency New features are published in the “New Releases” forum when released. For low level code customization a forum thread explains some of the functionality. A user tutorial (77 pages) is sold. The founders themselves sell services too. Partners have access to additional resources. Besides the many French partners there are also partners in Argentina. A brief tutorial for developing new modules is available. Canada. The code is very compact and has a tight memory footprint. It provides a translation mechanism for the content of form fields showing list values. The technical concepts and architecture are not documented. Without client side translation the GUI is in mixed language. French. 25 . user (141 pages) and administration (31 pages) manual are free. Some of these translations are not for the current version of TinyERP or are not complete. German. Italian. and Switzerland. Hungarian.

Comparision of features of three popular open source products Features order management inventory management  personnel management accounting management business partner management customer relatioship management sales and marketing management projrct management service management work flow design database support oracle XE database support PL SQL application directory java hot map debug java client web client fiest public release open source OSI approval compiere yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes Nov‐01 yes yes open bravo yes yes yes yes yes yes yes yes yes yes yes yes Adempiere yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes Apr‐06 Oct‐06 yes yes 26 .

if any. As the cliché goes. ERP applications are typically very complex. ERP systems are by their very nature more general tools. The advantage of that approach is that these applications are probably very well-suited for your specific business requirements. If you have unusual requirements (say. for example. you need a system to track orders. If you are wedded to the functionality of your current applications. It's also difficult to comprehend all the functionality they offer and understand how organisations requirements will map to the product's functionality. Examine them to ensure they're efficient. The five critical steps in developing strategy for companies in implementing open source ERP: Step one: Is ERP for you? The very first thing you should address is clear: Do you need an ERP system at all? The answer to this is not as obvious as one might think. works in progress probably won't matter. materials. If you're a distributor. you import live animals for pets and therefore need government certificates and need to ensure adequate food and space is available) those need to be defined so that you will be able to see which. you might be better served by sticking with them and updating them as required with new versions. Assessing your processes with a sceptical eye can help you understand whether you're doing some things only because of habit or even because your current applications force you to. but having two-level pricing will. Defining the functionality you require for your business is the second step in developing your ERP from the company point of view this should be strategy for the best use of open source ERP.not better. Don’t overlook your processes. Step two: Define your requirements From step one above.Chapter 4 Findings: From the study and research conducted by me I came to find out that open source is becoming popular and the various layers in the market are providing the service but to compare all on the given decided parameters is really difficult as one is good at reporting and the other is easy to install and easy to adapt changes . works in progress and inventory. If you're a manufacturer. ERP products can support them. Step three: Select a partner Very few organizations successfully install an ERP system on their own. Most organizations considering ERP have environments made up of disparate applications. it's clear that you need to understand (and document!) the functionality you need from your application infrastructure. each focused on fulfilling a particular set of business requirements. 27 . automating a poor process only gets it done faster -.

technically. Many companies engage a partner to help them understand their product requirements and whether it makes sense to move away from their current functionality-specific infrastructure. End users are a different breed. Step five: Implement the system To ensure that the transition to the new system goes smoothly from a technical perspective. Organisation may have more than one candidate to select from that case. organisation should be able to select the ERP product that's right for organisation.Because of this. They typically think of the software as something they use to do their real job. Open source ERP: The bottom line 28 . extra communication during the project planning and implementation stages is a good idea. Make sure organisation' are in tune with them in all ways -. and culturally. it may make sense to address this earlier in your ERP search. partnering with a service provider that focuses on all-night work sessions rather than boring processes is not a good match for organisation. depending on organisation organization. financially. Select a product that meets at least your must-have features list and appears to be moving in a direction to address your nice-to-have list. Technical personnel are often willing to live with product crashes and failures. if organisations are moving to open source and your potential partner tries to steer organisation toward a proprietary platform. Because of this. it makes sense to find a service provider that can help you with the process. what should organisation do? I will always recommend choosing a product that fits with organisation infrastructure and technical direction. The fact that the user base is nontechnical requires consideration as well. a good project plan is critical. Don't get overly hung up on whether a product fulfils 5% more of your nice-to-have list. move to the next candidate on Step four: Select a product Based upon the requirements organisation’ have developed and the partner organisation’ have chosen. If the product requires a commitment to a scripting language that is obscure or that organisation will never use for any other purpose. In fact. While this step is placed third on our list. If organisation likes deliberate project planning. maybe it's not the right one for organisation. Developing a migration plan for moving from the current system(s) and transferring data to the new system should be part of the project plan. Be sure to build these tasks into your implementation plan. so they don't have much patience for problems. Similarly. Setting up a test system to ensure that important data flows and interapplication integrations works properly is important. they may actually enjoy the process of figuring out what went wrong.

or project management. CRM. Open ERP covers and integrates most enterprise needs and processes such as Accounting. It is rich with more than 250 modules. Openbravo can also create and export reports and data to several formats. customer information. These include the following capabilities: Financial Management (Accounting) 29 . OpenERP is the most powerful and flexible Open Source ERP. It is possible to synchronize this information with other applications through the Java-based Openbravo API. Project management. For a more exhaustive outline of capabilities and features Compiere’s solution capabilities span Enterprise Resource Planning (ERP) and Customer Relationship Management (CRM). Stock.. Open ERP is always a good choice in terms of risk and the cost of integration. where the user can view the entire status of a company. such as PDF and Microsoft Excel. Purchase. HR. Production. and workflow information. Services management. Management by affairs.opening ERP's future Openbravo is a web-based. released under the GNU General Public License version 2. Having a single application provide a range of functionality can make your business operate more efficiently and profitably. Openbravo features a web-based interface. This ensures Open ERP a right product for any business vertical. The model for the program was originally based on the Compiere ERP program that is also open source.It has got more than 250 open source modules apart from the Custom made modules. As Openbravo is web based. including production information.The Fastest Developing Open Source ERP. Marketing campaign. order tracking. Compiere for CRM purpose: I have recently evaluated and reviewed Compiere and wanted to outline some of my findings. inventory. Sales. Openbravo . For those who are focusing on ERP solutions. Recommendations: These are the recommendations based on the study made on opensoure ERP they does not belong to any individual and are made on my study and may vary from person to person Open ERP . etc.Open source ERP can be a great choice for your organization. It deals with each kind of industry. I have limited this evaluation of Compiere to some key areas. especially the small and medium companies. from accountancy to stock management. based on the Mozilla Public License. it is possible to access the interface from anywhere that there is an Internet connection. open source ERP business solution for small and medium sized companies that are released under the Openbravo Public License.

they are specific to a group of user’s tasks and responsibilities ensuring that the users only see what is required to do their job. I have not seen an easier way to do this . improve productivity. Compiere offers one of their best modules to date . no development is required. 30 . warehousing and outbound operations. The time and expense this saves during initial implementation as well as during periodic upgrades contributes to the already lower cost of ownership when compared to traditional ERP solutions. The Compiere ‘Application Dictionary’ is a library of business logic meta-data that can be updated or extended to allow an organization to adapt Compiere to fit the unique requirements of their business. reduce warehouse space utilization or increase customer satisfaction. I personally think that Compiere is under-selling this particular capability. Dealing with the confusion this creates has always been a challenge when implementing some of the traditional ERP solutions. This is ideal for organizations that are looking to cut costs. When roles are established.Compiere hit this one out of the park. forms and fields that are available to the user are all determined by the user’s assigned role. In Compiere. Warehouse Management Recently released in Compiere 3. The menus. the ability to tailor a user’s online experience in terms of ‘look and feel’ is defined easily using roles. windows. Amongst complex applications.Sales Order Management Materials Management (Purchasing) Warehouse Management Customer Service (Support & Self-Service) Role-Based User Interfaces One of the things I liked most about Compiere is its flexibility to adapt to an organization and to the roles within an organization. The level and extent of the customization that can be accomplished using the ‘Application Dictionary’ would require significant development time and effort in any other application. Despite a broad array of features and functionality Compiere makes it easy to provide a simple streamlined user interface to your users. I have found that 80% of ERP users use about 20% of the features and functionality that are available to them. Roles are easily setup by an administrator.WMS (Warehouse Management System). Compiere allows this adaptability while maintaining easy upgradability.2. WMS expands an already solid Materials Management module with a broad range of brand new functionality that automates inbound. speed of deployment and a lower cost of ownership. Through years of observation. This easily translates into reduced training and support costs. Adaptability Compiere employs an innovative model-driven architecture that gives you unprecedented adaptability.

Some ERP systems still have to prove the flexibility concepts in practice with documented business cases. retail or manufacturing industries where the warehouse operations are complex.Compiere’s WMS solution is worth looking at as either an add-on to a larger Compiere implementation or as part of an integrated ERP solution. is a mature system. Conclusion: Open source ERP systems allow unique. For the purpose of a coarse. there are numerous warehouses or the number of items and transactions are high . 31 . flexibility. Further work needs to be done in the areas of functional features documentation and is solid and mature. If an organization only requires basic inventory and materials management functionality. The project structure of the selected ERP systems varies from company-driven to community-driven. However. In situations where you may be looking to cut warehousing costs as it relates to warehouse moves and utilization .At the centre of the WMS module is a highly flexible and configurable rules engine for setting up intelligent materials movement through all phases of warehouse management operations. Compiere. I recommend using the functionality included in the Materials Management module at no additional cost . some system properties are pointed out: SQL Ledger has accounting focus and is proved internationally. . The main reasons for choosing open source ERP systems are cost. whereas Opentaps/Ofbiz is more relational database centric. providing many customization possibilities. provides more ERP functionality than SQL Ledger and can be customized with add-on modules. for the mid-size to larger organizations in the distribution. the current market leader. subjective summary. TinyERP is evolving fast. adaptable processes that support a diversification strategy. It is best used out-of-the-box or as accounting module in an integrated solution. This expansion of the Materials Management module is offered by Compiere for an additional fee per user or per warehouse. where IT is a source for differentiation from competitors. ERP5 is following a purely object oriented approach. Company-internal system knowledge allows continuous process improvement and quick reaction to changing requirements.the advanced functionality provided by WMS is worth the additional cost. The availability of the source code and its use as application development framework can lead to a higher degree of flexibility and allows a close functional fit of the system to business processes. ERP5 and Opentaps (OfBiz) have very flexible architectures. vendor independence and company-internal knowledge generation. The SQL Ledger fork LX Office should only be evaluated for the German speaking market. GNU Enterprise is not production ready and missing any reference customers. [7]Pricing of various open source ERP packages http://www.openbravo.htm [5] Differences between the available Open source ERP packages http://www.php [5] Reasons for the popularity of Open Source ERP [6] Features of compiere http://www.html [3] Evaluation criterion for open source ERP systems [4] The parameters considered by the company in choosing dot net and j2ee for ERP applications 32 .com/c/a/Commentary/The-Case-for-OpenSource-ERP/ [2] Open source ERP grows up http://www.htm [8] Features of openbravo [4] Open Source ERP Resources For The Small-Medium Business http://opensourceerpguru.infoworld.References [1] The Case for Open-Source ERP

com JBOSS An open source J2EE application An interface to DATEV Software. www.gnuenterprise. A newer approach for versioning is subversion.tigris. Also see www. especially in GNU Public In most open source projects the source code is CVS 33 . is a bank independent online banking protocol used especially by German banks HRMS IDE Human Resources Management System.html Graphical User Interface LXDATEV GNUe GPL GUI HBCI Home Banking Computer Interface.subversion. UNIX is developed in C Common Gateway Interface.Appendix A: Glossary All Terms can also be looked up at http://en. Office and OfBiz. http:\\www. a standard web server interface Concurrent Versioning System: A client/server system for the central management of concurrent changes of source files.sun. used by many accountants.gnu. http:\\java. used by open source projects like GNU enterprise. DATEV itself is accountant cooperative providing software for accountants in Germany and Central Europe. GNU Enterprise www. www.wikipedia. an ERP module for human resources Integrated Development Environment Java A platform neutral programming language widely used for enterprise software C CGI CVS Programming language.

Sign up to vote on this title
UsefulNot useful