Latest Updates: ERP RSS

  • Brian

    Ideological Fanaticism + Open Source Software = Open Core Debate

    brian 11:13 pm on July 15, 2010 | 0 Permalink | Reply
    Tags: , BPM Training, Compiere, ERP, Open Core Debate, , , OSI

    Like many others I have been following the flurry of posts and comments that followed Jorg Janke’s blog post about Compiere. Without a doubt Jorg’s post is a great contribution to those of us involved in the day to day business of running open source software companies.

    However, most of the subsequent posts and comments focused on a hackneyed ideological debate surrounding open core and open source software in general. Is it just me or is this discussion really only interesting to an insular herd of open source VCs plagued recently by less than stellar returns and the cadre of lawyers that service this sector?

    For those of us that spend our days and nights running profitable, non-VC-run open source software companies, there is often little time for such banal ideological chatter. My shareholders are more impressed by numbers (the ones on the bottom line of the income statement), and our company is focused on creating world class software, engaging with a vibrant community to do so, and delivering value day in and day out to customers. With this in mind, who has time for an “open core” debate which completely misses the subtleties of running most successful companies?

    Since I seem to have appreciated something different in Jorg’s blog, here are a few of the points I feel are good take aways:

    1. Training. I guess this should be obvious, but for some reason it is easy to forget. I immediately cut and pasted some of Jorg’s thoughts and sent them directly to our head of sales. “… people tend to like the application they had most exposure to (and understood best).” This just drives home the point that we are already seeing. Those that take our BPM Software training course tend to continue on and purchase other services related to our BPM and Workflow Software. Jorg’s 80% up-sell number is interesting, especially for us since we are operating in such a similar space (BPM Software – Enterprise Software). Enterprise software tends to have a longer learning curve and so you have to figure out a way to get users over the “suck factor” to use the words of another open source exec/friend. I know we know this, but it never hurts to hear it again and go back to our strategy and see if we are really executing on it. Are our sales people taking the leads from trainings and performing the appropriate follow up? Are they being placed in the appropriate lead nurture campaigns? Are we focusing enough resources on training?

    2. Partners. You either love ‘em or you hate ‘em. Or in the case of Open Source Software – both! If there was ever a difficult subject in the world of open source, it is the subject of partners. Why do no open source companies admit this? I’ve been drilling open source execs on this point for years – how much of your revenue comes through partners and how much comes directly? Why is it I always get the same answer – “well, we actually don’t get that much revenue from our partners, but they are a really important part of our strategy,” most will say. I spoke with a partner of one open source ERP vendor the other day about partnering with us, and the partner asked me if we were going to force them to sell our Enterprise Version. He told me that his Open Source ERP vendor forces him to do this, but they usually don’t – instead they usually install the Open Source version, charge an installation, and charge the client their own support. No secret there, right? Wrong – this company was listed as a Gold partner for this particular vendor! So do all Open Source companies just suffer from SAP and MS channel envy? Is it really worth the uphill battle?

    3. Enterprise functionality and the balance of power – This is by far the most important point for me, and I believe for almost any open source company. And it is the point that Simon Phipps seems to over simplify while trying to draw ideological lines. The fact is not whether Open Core is good or bad. This type of ideological fanaticism serves no useful purpose. The truth is that “some” enterprise versions are bad and others are not. That’s right – no simple rule. I wish there was one, but there isn’t. The fact is that the Open Core needs to deliver enough value to make sense to enough people. If an open source company “cripples” its open source core, the community will soon head for greener pastures. And the fact is that the successful companies using open core are managing not to cripple their community editions.

    As Mark Radcliffe points out how could open core be doing so much damage to the community version if only 10% of an open source company’s users are using the Enterprise version and the other 90% are using the open source? Good point (although I think this number is actually much less in almost all cases).

    So here is an idea. Instead of worrying about approved licenses and what makes a company truly open or not, let’s just look at the numbers. If more than 10% of a “supposed” open source company’s users are actually paying money and using the software under a commercial license, then that company should no longer be called an Open Source Company. That’s right – they will be banished from this exclusive community. If less than 10% of your users are paying you money, then no worries – you will still have the right to be a card carrying member of the open source software company community.

    So there you have it, if you are an open source software company enjoying revenues in excess of $80 million USD per year – you better watch out because the OSI police are coming to get you because you must be cheating!

     
  • Amy

    May I take your order? BPM mashups through web services

    Amy 1:50 pm on May 30, 2010 | 0 Permalink | Reply
    Tags: , , , CRM, , ERP,

    I’ve been blogging lately about web services, and how they relate to business process management software.  To make a long short, BPM software packages can leverage web services to expand the BPM software’s reach and broaden its ability to share information, not only with users and databases directly in the BPM system, but also with other IT systems related to the business process.

    Few business processes are self-contained; most require information from people and systems across departments and business areas.  Many business processes even require information to be shared with external partners, clients, and providers.  Web services can expand the functionality of the BPM system and connect it with other systems across the organization, and beyond.  The resulting integrated systems are sometimes known as “mashups”.

    Mashups are pre-configured, ready-to-go integrations between different business software packages that speed and streamline the sharing of information among those systems.  For example, a BPM system can leverage web services to share client data with customer relationship management (CRM) software during an inventory process.  Or, budget data from an enterprise resource planning (ERP) system can be shared with the BPM, both in order to approve or deny an expense report filed using the BPM and subsequently to update the ERP once the expense report is complete.  Or, the BPM could be used to generate and retrieve documents stored in a document management system (DMS).

    Yes, web services can be used to share information with any other system that use web services.  Mashups make the sharing process that much easier, by preconfiguring the systems integration and streamlining the way that the two systems work together.

     
  • Brian

    Workflow Software, BPM Software, and ERP Software - How does it all fit together?

    brian 9:02 pm on February 4, 2010 | 2 Permalink | Reply
    Tags: ERP, Great Plains Software, JD Edwards Software, , Purchase Request, Purchase Request Process,

    It is nothing new to state that Business Process Management Software (BPM Software or Workflow Software) and ERP software go hand in hand.  In fact, I can probably count on one hand the number of meetings I have had with private companies in which ERP wasn’t discussed in the initial BPM meeting.  In private industry, the ERP and the BPM or Workflow solution are inextricably intertwined.  So much so, that the BPM consultant will end up discussing the client’s ERP within the first 30 minutes of the very first consultative meeting.

    Today I was in a meeting with a small company (100 employees) that had developed their own in house ERP software.  Present in the meeting were the executive president, numerous technical managers, and a number of different business area managers.  As is often the case, the president was not very technical.  He started the meeting by talking about the company system (he didn’t call it an ERP) at a very high level and how this system was designed to handle all of the company processes.  He hadn’t yet seen our BPM Software, but he ended his initial remarks by asking, “If we already have a main company system (i.e., ERP)  that handles all of our company processes, then why would we need BPM Software or a Workflow system?”

    This is a very good question.  The question points to a general weakness of the BPM Software Industry and a strength of the ERP industry.  ERP vendors have positioned their software as the system of systems.  They claim that this is the system that will run your business.  It manages your accounting, materials, inventory, and production process.  Once you have it installed you will have an efficient, modernized company.  And yes, it will even make your coffee.

    Of course, that sort of sales pitch is effective.  It goes to the heart of the insecurities of every General Manager or President, especially those that aren’t so familiar with the latest acronyms and systems jargon.  That is why the ERP vendor has historically been able to convince these businesses to fork over hundreds of thousands if not millions of dollars and go through a traumatizing process of installation that will usually last many months if not years.

    Of course, the ERP solution is important.   I am by no means suggesting that companies can forgo this investment.  However, the result is that when the BPM vendor or workflow software provider rolls in to town, the reception is usually one that begins with a strong bit of skepticism.  So, the question is, how does the BPM sales person now explain to this decision maker that there really is a need for a new business process system.  Hell, the BPM vendor doesn’t even have new language to describe what he/she is selling - it sounds just like the “other” system the company already has installed.

    This is a real problem when dealing with SMEs because of the limited attention span the decision makers usually have when it comes to technologies.

    I don’t have an easy answer.  I watched today as one of the sales guys on our team sloshed his way through a standard BPM explanation.  I would have kicked him under the table had I been sitting closer in order to tell him to just get on with the demo.  The description just wasn’t doing justice.  However, as is often the case, 30 minutes later as we were wrapping up the demo, the customer’s face had changed, and he was now rattling off ideas on where his business could implement BPM Software.  Why is BPM so difficult to describe yet often so easy to demonstrate?

    In the case of this customer we were demonstrating a Purchase Approval Process.  Of course, the customer’s ERP manages the purchase process - every ERP vendor will tell you that their software has a purchasing module whether it is SAP, JD Edwards, Great Plains, or Openbravo.   But it usually isn’t until many months after the ERP solution is installed that the company managers realize that an important part of their purchase process still isn’t automated.  Yes, the ERP will record the purchase of the product, create the appropriate accounting entries, produce the Purchase Order, allow for the reception of money, deduct the product from inventory, and confirm the delivery of the goods or services and receipt of payment.  But what about all the company best practices that go into the act of making the decision to make the purchase?  Ahh, that just sort of got let out as an after thought.  Or maybe it was specifically left out so that the ERP vendor could try and go back a year later to sell another product?  (I am really not a conspiracy theorist).  Either way, most businesses sooner or later come to the conclusion that their ERP still left them with a lot of Process Problems.

    This is where workflow software or BPM software (there is no difference - that was another marketing blunder) adds a much needed layer of process management to the company.  Let’s take the Purchase Process. In this company, the process went something like this -

    1. Employee makes a Request
    2. Request stake into consideration existing products and reference pricing
    3. Based on the reference pricing either one or two levels of management approval is needed
    4. Once approved, the purchasing manager sends out 3 Quote requests to approved vendors
    5. The quotes come back and need to be compared
    6. Final decision and a final approval ocurr

    Following best practices in this business process could save hundreds of thousands of dollars in the case of this company.   But time and time again the company didn’t follow best practices because the process was executed differently every time.

    I’ll let you know next week if they decided to buy the BPM Software…  :)

     
  • Brian

    OSBC 2008

    brian 12:30 am on March 28, 2008 | 0 Permalink | Reply
    Tags: , , ERP, , Wiki,

    Colosa just finished a fantastic OSBC. It was our first time exhibiting at the event, and we were very pleased with the interest ProcessMaker generated. Personally, I didn’t get to go to very many of the conference seminars, but I did spend a lot of time hanging out in the hallways with lots of other cool open source vendors. We had some great conversations around integrating with some of these solutions so I’d like to let you know a little about what we will be up to shortly.

    We’ve done a number of important “client requested” ERP integrations in the past, mostly with SAP but also with lots of different regional ERPs (mostly in South America). The thing about workflow and BPM is that it usually has something to do with other systems. And more often than not those other systems are…well ERP systems. A couple classic examples would be a Purchase Request Approval Workflow or a Return Merchandise Authorization Workflow (RMA). So, Fernando and I had a very nice chat with Paolo Juvara, Chief Products Officer at Openbravo - the clear leader in open source ERP and a terrific product.

    The result of the talk was an decision to begin testing an integration between Openbravo and ProcessMaker. I believe the result could be a killer mashup. The ProcessMaker workflow, we believe, will add lots of interesting value around the ERP system and vice versa.

    Another interesting mashup we are looking at doing is with Mindtouch’s Deki Wiki. If you don’t know it, this is a super cool wiki. So cool, that we are planning on moving our own website to it! The product uses html in a whole different way in the wiki environment and makes the whole experience much richer.

    So what will this integration mean to the user? Well, from our perspective, we work with organizations that are trying to create standard, repeatable, automated processes. Usually, the people performing these processes are people that tend to rotate in and out of the positions where they fill out the forms in our processes. This means that often times there is an information gap created surrounding the processes. How do you keep your organization informed about best practices that have to do with these processes. Well, if you in bed our ProcessMaker forms in the Deki Wiki then you’ve got a sort of living, breathing, growing manual around your process. Imagine how much smoother paperwork would flow with this type of information easily updated in the system? No more clumsy tags for manuals, etc. That’s the idea.

    The third mashup we are really excited about is with WSO2. We already have a full web services interface in ProcessMaker, but these guys are really the kings of Web Services. So, the idea is simple. We do workflow and user level stuff really well. But the user level workflow inevitably interacts with lots of systems. So the idea is we will create a rock solid connection to WSO2 and then let WSO2 help us connect to all the different systems that our users want to use. We think this will take ProcessMaker to a whole new level of utility in the Enterprise space!

    Well, all in all a great OSBC. Of course, we also got to hang out with our good friends at Knowledgetree and talk to lots of users already very excited about our recently launched plugin with Knowledgetree which now allows organizations to store all of their ProcessMaker generated or uploaded docs in the Knowledgetree Document Management System - a truly powerful combo.

     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
esc
cancel