by Rob Goris
Simple, real-time business intelligence by manipulating grids
Reporting is an essential part of everyday business and therefore an essential part of an ERP. Today´s businesses need relevant, up-to-date, accurate and consumable metrics that help them make the right decisions. Traditionally, reports are generated once in a while (month, quarter) and are exported to PDF for printing & annotating or Excel for further manipulation. Reports are used in presentations and meetings to look at past performance, understand the status quo and project future performance. The danger lies in the choice of dimensions and the interpretation of the data. Reports are static and generated as a one-off document with a set of dimensions, normally defined by a ready-made SQL query or via a visual query builder. Openbravo´s Sales Dimensional Reports allow the user to choose a number of filters and dimensions and even the sorting order can be set. This works well if the user knows in advance what metrics she is looking for and what data set she wants to look at. The drawback is that it does not allow analyzing the data in realtime by changing the filters and dimensions and looking at the impact on the results while doing so.
A while ago, in the Family Grid, I have presented a fairly abstract idea for basic business intelligence functionality by combining parent and child data in one grid, joining grids and filtering and aggregating columns. Now, I´d like to show you a more simplified version of this idea.
The Family Grid II scenario (download it here) lets the user view sales orders in one grid and a set of order lines for all of these in the other. Both the sales order grid and the order lines grid can be filtered on any attribute using column filters. Columns containing numerical values can be aggregated (sum, count, average, median). The grids can be joined (inner or outer join) with the click of a button which, for example, lets the user find all sales order that contain a certain product (or all sales that do not contain that certain product). Final result sets can be exported to Excel or PDF and the view (which is in fact a query rather than a report) can be saved for reuse.
It should be noted that this approach does not intend to replace traditional reporting because many SQL queries just cannot be build using the Family Grid. However, I believe that this way of manipulating grids is very powerful and can lead to insights that can be hard to discover using traditional one-way reporting. Playing with a data set in real time using parent and child grids, filters, aggregations and joins with an easy-to-use GUI lets non-expert users unlock the power of data in an ERP without having to invest in hi-end business intelligent software.
Are you as convinced as I am about the business value of this feature? Discuss it here.
By the way, we´re not happy with the name of this functionality. Family Grid does not cover it really. What about RapidGrid, GridSift, PowerGrid, Data Distiller, Metrix, EasyAnswer, RapidAnswer, IntelliGrid, "Openbravo RapidEdge Edition – the fastest way to start a competitive edge", "PerfectGrid - the fast & simple way to your information"?
source:
http://planet.openbravo.com/
Tuesday, July 13, 2010
Wednesday, June 30, 2010
Packaging Openbravo 3.0 as a distribution
by Paolo Juvara
Openbravo 3.0 is going to be a landmark release for the Openbravo ecosystem for many reasons, ranging from improved functionality to a completely revised platform.
As the first release candidate milestone of Openbravo 3.0 approaches (the target release is July 2010), I would like to take the time to explore one specific area of innovation: the packaging and delivery of the product.
Unlike previous releases, where Openbravo was offered as a monolithic product on top of which users could install extensions, Openbravo 3.0 is going to be delivered as "distribution" of modules. By distribution, I mean a collection of modules - one of which is Core - selected and integrated to achieve the desired functional footprint of the release.
This approach presents several advantages, including a smoother upgrade for 2.50 users and the ability to reuse 2.50 modules in 3.0. The following presentation illustrates the concept.
Leveraging the modular architecture of 2.50, we have been providing extension modules on top of Core. Some of those extensions are technology oriented, like the Seam Integration or the new User Interface Selector, while others, like Advanced Payables and Receivables, are functional in nature. In both cases, these are pre-3.0 features that can be deployed as modules on top of 2.50.
We can continue to release such modular components until we have all the building blocks we need for 3.0.
This is an effective way to add new capabilities but for 3.0 we also need to remove some unwanted features from Core, in some cases because it is obsolete functionality and in other cases because it is more appropriate as a module rather than a core feature.
Removing functionality is tricky: if we eliminate the code, in fact, we take the risk of breaking a dependency for an existing module therefore negating the objective of ensuring a smooth upgrade and the durability of modules. To avoid this problem, we will improve the License Manager capabilities of Core: currently the License Manager is the technology that allows us to distinguish between a Community Edition and a Professional Edition; we intend to enhance its capabilities to allow us to securely hide unwanted features and ensuring that they cannot be accidentally re-enabled. While still physically present, the unwanted features will be for all intents and purposes de-activated.
Leveraging this technology, we can deliver Openbravo 3.0 as a "template" that combines all the desired modules, plus a configuration script that defines the default configuration of the system.
We have already followed a similar approach for QuickStart, one of the professional solutions that we developed for our partners in 2.50 and we will apply the same technique for 3.0.
Using our 3.0 distribution as starting template, it is then possible to add further configuration scripts and provide additional specializations. In this respect, this packaging approach provides a nice balance between the base product and its vertical specializations as both solutions share the same development and distribution approach.
There are some obvious benefits to this approach:
With 3.0 we fully embrace the distribution approach, coming to a full circle and confirming our commitment to build the ecosystem of reference in the open source ERP space.
As the first release candidate milestone of Openbravo 3.0 approaches (the target release is July 2010), I would like to take the time to explore one specific area of innovation: the packaging and delivery of the product.
Unlike previous releases, where Openbravo was offered as a monolithic product on top of which users could install extensions, Openbravo 3.0 is going to be delivered as "distribution" of modules. By distribution, I mean a collection of modules - one of which is Core - selected and integrated to achieve the desired functional footprint of the release.
This approach presents several advantages, including a smoother upgrade for 2.50 users and the ability to reuse 2.50 modules in 3.0. The following presentation illustrates the concept.
Leveraging the modular architecture of 2.50, we have been providing extension modules on top of Core. Some of those extensions are technology oriented, like the Seam Integration or the new User Interface Selector, while others, like Advanced Payables and Receivables, are functional in nature. In both cases, these are pre-3.0 features that can be deployed as modules on top of 2.50.
We can continue to release such modular components until we have all the building blocks we need for 3.0.
This is an effective way to add new capabilities but for 3.0 we also need to remove some unwanted features from Core, in some cases because it is obsolete functionality and in other cases because it is more appropriate as a module rather than a core feature.
Removing functionality is tricky: if we eliminate the code, in fact, we take the risk of breaking a dependency for an existing module therefore negating the objective of ensuring a smooth upgrade and the durability of modules. To avoid this problem, we will improve the License Manager capabilities of Core: currently the License Manager is the technology that allows us to distinguish between a Community Edition and a Professional Edition; we intend to enhance its capabilities to allow us to securely hide unwanted features and ensuring that they cannot be accidentally re-enabled. While still physically present, the unwanted features will be for all intents and purposes de-activated.
Leveraging this technology, we can deliver Openbravo 3.0 as a "template" that combines all the desired modules, plus a configuration script that defines the default configuration of the system.
We have already followed a similar approach for QuickStart, one of the professional solutions that we developed for our partners in 2.50 and we will apply the same technique for 3.0.
Using our 3.0 distribution as starting template, it is then possible to add further configuration scripts and provide additional specializations. In this respect, this packaging approach provides a nice balance between the base product and its vertical specializations as both solutions share the same development and distribution approach.
There are some obvious benefits to this approach:
- Easy upgrade for 2.50 users to 3.0: technically, an upgrade is reduced to the installation of additional modules and a configuration template (of course, there are many non technical aspects involved with an upgrade, but avoiding technical problems already simplifies the challenge)
- Guaranteed durability of modules: all of the 2.50 modules will be able to work in 3.0 as well because none of their dependencies is altered.
- Opportunity to gather early feedback on 3.0: we do not need to have 100% of the functionality ready to start exposing it to our community. In fact, many of the 3.0 modules have already been independently available for several months and went through their own feedback and stabilization cycle.
- Reduced maintenance cost for 2.50: since 2.50 and 3.0 share a common Core, the cost of maintenance will be largely reduced.
With 3.0 we fully embrace the distribution approach, coming to a full circle and confirming our commitment to build the ecosystem of reference in the open source ERP space.
source: http://planet.openbravo.com/
Wednesday, June 23, 2010
Consona acquires Compiere – What about the Community?
Source:planet.openbravo.com
by Paolo Juvara
Last Wednesday the open source ERP community woke up with the news of the Consona acquisition of Compiere, one of the pioneers in open source ERP. The text of the announcement can be found here.
Since the announcement, many observers and commentators started a debate on whether this is a victory for open source or the sad demise of one the pioneers of the open source ERP category. Many also speculated on what might be in the store for the product, with most people interpreting the transaction primarily as a technology acquisition.
A recurring theme among commentators is that Compiere failed to embrace its community.
With such a symbolic event fresh in our mind, it is time to reflect on how Openbravo facilitates the development of its own community.
Last year I had commented on Adam Blum's post on The Seven Habits of Highly Effective Open Source Products. An effective open source product must display "a credible community with a credible effort to involve the community in the development of the product, as described in Adam's seven habits:
The results of these efforts are a community that is lively, growing and productive.
Looking at the public SourceForge statistics - which are public and independent -, for the period of May 2010:
by Paolo Juvara
Last Wednesday the open source ERP community woke up with the news of the Consona acquisition of Compiere, one of the pioneers in open source ERP. The text of the announcement can be found here.
Since the announcement, many observers and commentators started a debate on whether this is a victory for open source or the sad demise of one the pioneers of the open source ERP category. Many also speculated on what might be in the store for the product, with most people interpreting the transaction primarily as a technology acquisition.
A recurring theme among commentators is that Compiere failed to embrace its community.
With such a symbolic event fresh in our mind, it is time to reflect on how Openbravo facilitates the development of its own community.
Last year I had commented on Adam Blum's post on The Seven Habits of Highly Effective Open Source Products. An effective open source product must display "a credible community with a credible effort to involve the community in the development of the product, as described in Adam's seven habits:
- Public source viewing
- Common license
- Public source code checkins
- Public bugs
- Public forums
- Anyone can contribute
- Public, complete and modifiable documentation"
How does Openbravo measures against Adam's seven habits?
- Openbravo offers public source viewing at http://code.openbravo.com
- Openbravo adopts a common license with the Openbravo Public License being a common variation of the popular Mozilla Public License
- Openbravo offers public source code checkins available either at http://code.openbravo.com, through the openbravo-commit mailing list, or on the #openbravo IRC channel on freenode.net.
- Openbravo offer a public issue tracker at http://issues.openbravo.com where any community member can view or report issues
- Openbravo hosts and moderates public forums on the Openbravo Forge mirrored on SourceForge.
- Openbravo accepts open contribution through a documented process either in the form of extension modules, core contributions or in many other ways.
- Openbravo maintains a public, complete and modifiable documentation available in the wiki.
But it does not stop there:
- Openbravo offers a public road map.
- Openbravo engages with its community on the direction of the product.
- Openbravo offers full visibility of the progress of its development process.
- Openbravo engages with its community in the design of upcoming features.
- Openbravo supports its community not only through forums but also through the #openbravo IRC channel on freenode.net.
- Openbravo engages with its community of developers through the openbravo-developer mailing list.
- Openbravo educates its community on its latest version with frequent public webinars.
- Openbravo hosts monthly open community meetings (see the log of the May session as an example).
- Openbravo goes beyond public source checkins and offers public visibility of the testing of those checkins and how they get integrated into the product through our continuous integration infrastructure.
- Openbravo engages its community of users through a collaborative QA process supported by an open test case repository.
- Openbravo offers a public collaboration space with the Openbravo Forge.
- Openbravo hosts and moderates a wiki that contains more than 3,000 articles, with 1,300 monthly edits, and servers around 35,000 unique monthly visitors.
- Openbravo has formalized its commitment to its community through the Openbravo Manifesto.
- Openbravo has adopted a business model that does not divorce its Community Edition users from its Professional Edition solutions but embraces the usage of the Community Edition. There is an easy and smooth transition path for those community users that are ready to enjoy the increased benefits of the Professional Edition. Similarly there is freedom of choice for developers and service providers to distribute their development either as open source or with a commercial license.
Looking at the public SourceForge statistics - which are public and independent -, for the period of May 2010:
- Activity ranking: 2
- Forum post: 655 (and this does not include any of the hundreds of discussions in the Openbravo Forge other than the core ones)
- Downloads: 23,845 (and this does not include the 2,480 downloads from the Ubuntu repository nor any of the thousands of downloads of extension modules from our own Central Repository)
- The Openbravo community is large and growing, with 10,426 registered members at the end of May and increasing at a pace of over 300 new members per month.
- The Openbravo community is engaged giving us feedback on the product, with anywhere between 20 and 30% of the defect and new feature requests reported in any given month coming from the open community.
- The Openbravo community is productive, with 361 public projects registered in the Openbravo Forge at the end of May and managed by our community.
- The Openbravo community is effective, having produced as of the end of May 161 modules distributed through the Central Repository to the entire ecosystem of users.
Tuesday, June 22, 2010
What does Consona's acquisition of Compiere mean?
Source:
http://openingerpsfuture.blogspot.com/2010/06/what-does-consonas-acquisition-of.html
Friday, 18 June 2010,Posted by Manel Sarasa
What does Consona's acquisition of Compiere mean?
Since the announcement of Consona’s acquisition of Compiere, many people have asked me for my thoughts and comments. What does this deal mean for the open source ERP market, the ERP industry as a whole, and for the Openbravo community? I am keen to answer these questions and share my thoughts.
First, my interpretation of the nature of the acquisition. Everything I have read and heard about it reveals that the driving rationale for Consona was to acquire the technology, and not the open source element of Compiere, and so I predict this will mean the end for Compiere's community. Am I happy about that? No, not at all. Besides the disruption that this will bring to many people, I am a firm believer that at this stage the more successful open source ERP companies there are, the better. This is not good news at any level.
My second observation is about the predictability of this end game. Compiere's business model, organization and management style - specifically in product development, sales strategy and channel management – always resembled that of a traditional proprietary vendor, rather than one suited to an open source provider. Open source must never be used merely as a marketing tool - if you don't believe in open source and invest heavily in its development, then you don't create an open source culture within the project team and therefore cannot leverage its many benefits. Open source isn’t something you can just dabble in.
But I would like to sign off with some positive messages for the open source ERP industry. At Openbravo we are as excited and positive as ever. Open source has always been and will always be the very core of our business. This dedication and commitment is what helped us lead this market. Our purpose is to improve the efficiency of businesses around the world by bringing an ERP to every company. And for this reason our ambition has always been to create the leading web-based open source ERP company. We are strong believers that horizontal ERPs are a commodity and should be free; that value is in the services and industry specific solutions; and that openness and a strong community is a requirement for building better software in the 21st century. Success with open source ERP requires a collaborative, organic approach that unleashes synergies between the community and commercial use of the product, without artificial barriers. Rest assured that we will continue making it happen.
Ultimately, this acquisition means one less open source ERP player, reaffirming Openbravo’s leadership in this market and our genuine commitment to it.
First, my interpretation of the nature of the acquisition. Everything I have read and heard about it reveals that the driving rationale for Consona was to acquire the technology, and not the open source element of Compiere, and so I predict this will mean the end for Compiere's community. Am I happy about that? No, not at all. Besides the disruption that this will bring to many people, I am a firm believer that at this stage the more successful open source ERP companies there are, the better. This is not good news at any level.
My second observation is about the predictability of this end game. Compiere's business model, organization and management style - specifically in product development, sales strategy and channel management – always resembled that of a traditional proprietary vendor, rather than one suited to an open source provider. Open source must never be used merely as a marketing tool - if you don't believe in open source and invest heavily in its development, then you don't create an open source culture within the project team and therefore cannot leverage its many benefits. Open source isn’t something you can just dabble in.
But I would like to sign off with some positive messages for the open source ERP industry. At Openbravo we are as excited and positive as ever. Open source has always been and will always be the very core of our business. This dedication and commitment is what helped us lead this market. Our purpose is to improve the efficiency of businesses around the world by bringing an ERP to every company. And for this reason our ambition has always been to create the leading web-based open source ERP company. We are strong believers that horizontal ERPs are a commodity and should be free; that value is in the services and industry specific solutions; and that openness and a strong community is a requirement for building better software in the 21st century. Success with open source ERP requires a collaborative, organic approach that unleashes synergies between the community and commercial use of the product, without artificial barriers. Rest assured that we will continue making it happen.
Ultimately, this acquisition means one less open source ERP player, reaffirming Openbravo’s leadership in this market and our genuine commitment to it.
Wednesday, May 26, 2010
Review: For ERP, Is It Time To Applaud Openbravo?
10:27 AM EDT Tue. Apr. 15, 2008
Think of any proprietary platform, and there is an open-source alternative, whether it's an operating system or a database, or even, yes, an ERP system. Enterprise resource planning software is used for operational planning, including managing orders, inventory, accounting, and logistics. Long dominated by industry giantsOracle (NSDQ: ORCL) and SAP (NYSE:SAP), ERP deployments are generally associated with the large enterprise. Open source ERP systems bring the technology within reach of the small and midsize enterprises, and all the way down to the small business. There are a handful of open source ERP solutions that can be considered business-ready --- thorough documentation, extensive technical and customer support, and a regular release schedule. Openbravo ERP, from Spanish company Openbravo is one. The Test Center deployed the Web-based ERP and discovered a fully functional system that supports procurement and warehouse management, project and service management, production management, and financial management. It also supports BI and CRM. Designed for the SME, Openbravo ERP is flexible, scalable, and affordable.
A big concern about open source has always been about interoperability: would it work with what's already in production? Openbravo ERP eases those concerns somewhat, supporting both proprietary Oracle (10g) and open source PostgreSQL databases. Openbravo ERP is Java-based and requires several Apache products. At this point, Microsoft-centric customers with SQL Server databases, .NET framework, and IIS, won't be feeling the Openbravo love, but they are probably looking at Microsoft Dynamics ERP, anyway. However, Openbravo does run on servers running Microsoft Windows XP, 2000, 2003 Server.
Openbravo is different from other open-source ERP in that its interface is entirely Web-based. The user can view production information, inventory, customer information, order tracking, and workflow information all from a Web browser. This simplifies access, since authorized users don't have to wait for special client software to be installed on their computers. As most Web applications, the interface is intuitive and menu options are easily accessible. Various management options are organized as menus, such as sales, procurement, and production. Clicking on the option opens up all the associated tasks in a drop-down. For example, transactions such as sales and shipment orders are accessible under the Sales Management menu. Each task window is icon-driven, and the icons are pictorially easy to understand. Reports are easy to create and there are several templates, as well as the ability to create customized ones. The reports and data can be exported toMicrosoft (NSDQ: MSFT) Excel or saved as PDF.
Openbravo spent a lot of time designing the architecture the ERP is constructed on. The metadata-driven engine is based on a 2002 version of another open-source ERP project, Compiere. Openbravo improved upon the engine, and consists of only 10 percent of the code base, according to the company's Web site. The entire system is constructed on two development frameworks: the Model-View-Controller and Model-Driven-Development. Under MVC, data is manipulated by controllers, not directly by the user. By referencing a data model dictionary, the application engine can automatically recompile and rebuild whenever the administrator makes a change. And MDD allows models of code for user-created code. These two models simplify integration with other programs.
Deploying Openbravo ERP requires getting all the supporting applications installed and configured first. Test Center used a Debian 4.0r3 Etch server. Openbravo has been tested on other Linux flavors as well, including Red Hat Enterprise Linux, CentOS,Novell (NSDQ: NOVL) SUSE, Canonical's Ubuntu and Fedora. The testing server already had the latest Java and Ant installed; solution providers would have to remember to install them beforehand. Ant is an Apache software tool that automates software builds for Java files (similar to make).
Because it's a Java-based application, Openbravo also requires Tomcat, an Apache Web container that specifically handles Java Servlet and JSP. For the database backend, PostgreSQL was installed on the test server.
Once the individual components are in place, the actual Openbravo ERP installation is script-driven. Openbravo is distributed with all source code developed by Openbravo and few third-party libraries. The script requires information about the database server, such as IP address, username, and port, and about the system, such as the Web URL. Once the script completes, the Openbravo ERP is accessible by pointing the browser to the specified URL.
Deployment is where solution providers can really provide service. Compared to an SAP or Oracle deployment, Openbravo is relatively easy, but it's still not plug-and-play. An ERP implementation typically is handled by, or at least, supported by, system integrators and consultants. This works well with Openbravo's distribution model, which relies on the channel. Openbravo is available in two versions: the Community Edition and Network Edition. Community Edition is available for free from SourceForge.net and intended for developers and non-critical environments. The Network Edition is the production-ready and stable solution, available through certified partners. For this Test Center review, Openbravo Community Edition was installed.
The latest features are available in the Community Edition and there are frequent releases throughout the year, while the Network Edition is updated biannually. For an annual subscription (prices vary depending on number of users or unlimited use), the Network Edition offers automatic upgrades, bug-fixes, unlimited support, and embedded licenses for proprietary software and third-party support.
Montclair, N.J.-based Corra Technology is an open-source solution provider providing system integration, support, and consulting services. CEO Ron Bongo estimated the company has already been contracted to do four or five Openbravo installations in 2008, and the company expects to do at least ten or fifteen this year.
ERP systems have to support big companies with complex business systems and a large user base. Does Openbravo scale? Bongo said a typical Openbravo deployment for Corra Technology is in the $10 million to $100 million range, and scalability has never been a problem. The company's focus on model-driven architecture makes the application stable, scalable, and easy to develop for.
System integrators with software development capabilities can develop applications for Openbravo, especially with the Eclipse IDE. Other applications can synchronize data with Openbravo using the Java-based Openbravo API. Also, Openbravo ERP is released under the Mozilla Public License 1.1, which means the code can be used as a foundation for other proprietary licensed products.
Openbravo also offers Openbravo POS, an application specifically designed for touch screens used in the retail industry. Openbravo POS can work together with Openbravo ERP, or separately in any existing point-of-sale environment.
System integrators can speed up some of the deployment by creating an appliance with the basic components pre-installed. With proper hardware, the appliance can have the ERP system and its dependencies in place, waiting to be configured according to each customer's individual specifications and requirements.
A note about documentation and support: many open source projects often rush to get the product out, which often means documentation, if available, is usually skimpy and often riddled with errors. While a strong community-driven-forum is essential for an open source project, businesses need access to thorough, in-depth, and clearly written documentation. Openbravo shines in this aspect. The installation guide, user manual, and associated reference materials on configuring third-party applications and hardware specifications are superb. Bongo said Openbravo spent a long time getting the software ready, but also in getting the commercial team behind the product for support. "They have all the pieces in place," he said.
Corra Technology is in the enviable position of not having to convince customers to consider open-source deployments since "99 percent" of its customers approach the company asking for open-source solutions. For solution providers still trying to convince their customers, selling open-source ERP doesn't have to be a difficult conversation. According to Bongo, many CIOs are actively considering open-source solutions when considering IT projects. Open source solutions save customers money, especially for ERP. Customers can specify their requirements and have only those services in the ERP system, so that they are not paying for services they aren't interested in. The ease of customization also means customers are no longer locked in to expensive ERP software and supporting systems.
Cost-competitive, a modern architecture, and flexible (and it works!) -- what more do customers need for ERP?
A big concern about open source has always been about interoperability: would it work with what's already in production? Openbravo ERP eases those concerns somewhat, supporting both proprietary Oracle (10g) and open source PostgreSQL databases. Openbravo ERP is Java-based and requires several Apache products. At this point, Microsoft-centric customers with SQL Server databases, .NET framework, and IIS, won't be feeling the Openbravo love, but they are probably looking at Microsoft Dynamics ERP, anyway. However, Openbravo does run on servers running Microsoft Windows XP, 2000, 2003 Server.
Openbravo is different from other open-source ERP in that its interface is entirely Web-based. The user can view production information, inventory, customer information, order tracking, and workflow information all from a Web browser. This simplifies access, since authorized users don't have to wait for special client software to be installed on their computers. As most Web applications, the interface is intuitive and menu options are easily accessible. Various management options are organized as menus, such as sales, procurement, and production. Clicking on the option opens up all the associated tasks in a drop-down. For example, transactions such as sales and shipment orders are accessible under the Sales Management menu. Each task window is icon-driven, and the icons are pictorially easy to understand. Reports are easy to create and there are several templates, as well as the ability to create customized ones. The reports and data can be exported toMicrosoft (NSDQ: MSFT) Excel or saved as PDF.
Openbravo spent a lot of time designing the architecture the ERP is constructed on. The metadata-driven engine is based on a 2002 version of another open-source ERP project, Compiere. Openbravo improved upon the engine, and consists of only 10 percent of the code base, according to the company's Web site. The entire system is constructed on two development frameworks: the Model-View-Controller and Model-Driven-Development. Under MVC, data is manipulated by controllers, not directly by the user. By referencing a data model dictionary, the application engine can automatically recompile and rebuild whenever the administrator makes a change. And MDD allows models of code for user-created code. These two models simplify integration with other programs.
Deploying Openbravo ERP requires getting all the supporting applications installed and configured first. Test Center used a Debian 4.0r3 Etch server. Openbravo has been tested on other Linux flavors as well, including Red Hat Enterprise Linux, CentOS,Novell (NSDQ: NOVL) SUSE, Canonical's Ubuntu and Fedora. The testing server already had the latest Java and Ant installed; solution providers would have to remember to install them beforehand. Ant is an Apache software tool that automates software builds for Java files (similar to make).
Because it's a Java-based application, Openbravo also requires Tomcat, an Apache Web container that specifically handles Java Servlet and JSP. For the database backend, PostgreSQL was installed on the test server.
Once the individual components are in place, the actual Openbravo ERP installation is script-driven. Openbravo is distributed with all source code developed by Openbravo and few third-party libraries. The script requires information about the database server, such as IP address, username, and port, and about the system, such as the Web URL. Once the script completes, the Openbravo ERP is accessible by pointing the browser to the specified URL.
Deployment is where solution providers can really provide service. Compared to an SAP or Oracle deployment, Openbravo is relatively easy, but it's still not plug-and-play. An ERP implementation typically is handled by, or at least, supported by, system integrators and consultants. This works well with Openbravo's distribution model, which relies on the channel. Openbravo is available in two versions: the Community Edition and Network Edition. Community Edition is available for free from SourceForge.net and intended for developers and non-critical environments. The Network Edition is the production-ready and stable solution, available through certified partners. For this Test Center review, Openbravo Community Edition was installed.
The latest features are available in the Community Edition and there are frequent releases throughout the year, while the Network Edition is updated biannually. For an annual subscription (prices vary depending on number of users or unlimited use), the Network Edition offers automatic upgrades, bug-fixes, unlimited support, and embedded licenses for proprietary software and third-party support.
Montclair, N.J.-based Corra Technology is an open-source solution provider providing system integration, support, and consulting services. CEO Ron Bongo estimated the company has already been contracted to do four or five Openbravo installations in 2008, and the company expects to do at least ten or fifteen this year.
ERP systems have to support big companies with complex business systems and a large user base. Does Openbravo scale? Bongo said a typical Openbravo deployment for Corra Technology is in the $10 million to $100 million range, and scalability has never been a problem. The company's focus on model-driven architecture makes the application stable, scalable, and easy to develop for.
System integrators with software development capabilities can develop applications for Openbravo, especially with the Eclipse IDE. Other applications can synchronize data with Openbravo using the Java-based Openbravo API. Also, Openbravo ERP is released under the Mozilla Public License 1.1, which means the code can be used as a foundation for other proprietary licensed products.
Openbravo also offers Openbravo POS, an application specifically designed for touch screens used in the retail industry. Openbravo POS can work together with Openbravo ERP, or separately in any existing point-of-sale environment.
System integrators can speed up some of the deployment by creating an appliance with the basic components pre-installed. With proper hardware, the appliance can have the ERP system and its dependencies in place, waiting to be configured according to each customer's individual specifications and requirements.
A note about documentation and support: many open source projects often rush to get the product out, which often means documentation, if available, is usually skimpy and often riddled with errors. While a strong community-driven-forum is essential for an open source project, businesses need access to thorough, in-depth, and clearly written documentation. Openbravo shines in this aspect. The installation guide, user manual, and associated reference materials on configuring third-party applications and hardware specifications are superb. Bongo said Openbravo spent a long time getting the software ready, but also in getting the commercial team behind the product for support. "They have all the pieces in place," he said.
Corra Technology is in the enviable position of not having to convince customers to consider open-source deployments since "99 percent" of its customers approach the company asking for open-source solutions. For solution providers still trying to convince their customers, selling open-source ERP doesn't have to be a difficult conversation. According to Bongo, many CIOs are actively considering open-source solutions when considering IT projects. Open source solutions save customers money, especially for ERP. Customers can specify their requirements and have only those services in the ERP system, so that they are not paying for services they aren't interested in. The ease of customization also means customers are no longer locked in to expensive ERP software and supporting systems.
Cost-competitive, a modern architecture, and flexible (and it works!) -- what more do customers need for ERP?
Subscribe to:
Posts (Atom)
