IT|Redux

What is Wrong with BPM

Friday, February 16th 2007 | Ismael Ghalimi

Last year, I wrote a fairly controversial post explaining why nobody cares about BPM. The main idea was that most BPM projects are implemented by software vendors and system integrators, with little participation from customers themselves. As a result, BPM products remain at the level of frameworks, rather than being promoted to the level of platforms. It has been nine months since I wrote this article, and twelve since Intalio moved to an open-source model. This time and experience gave me a better understanding of the problem at hand.

A month after publishing my original post, I challenged my friend and industry analyst Bruce Silver to point me to a BPM vendor that could identify three customers who successfully managed to use its product to build a complex business process that would leverge a Service Oriented Architecture, and managed to do it without writing code and with no technical support from the vendor. He could not. Since then, I have asked analysts at Forrester, Gartner, and Upside Research the same question. They could not come with a better answer.

Time passed, and I kept looking, until we hired a sales engineer who used to work in the professional services division of one of our competitors, which I won’t name for obvious reasons. While we were getting him up to speed with our product, I asked him to outline the pluses and minuses of our product compared to our competitor’s, without disclosing any confidential information. What he came up with helped me validate some of my early assumptions.

In a nutshell, when using our competitor’s BPM product, putting a simple workflow process together during a sales call is a matter of minutes. Drap and drop this shape, draw this link, and voilà, you have a process up and running, with simulation and all. Of course, this makes for a great demo, the customer is impressed, and before you know it, an $300,000 check has been signed. Then, the fun begins.

Once you get beyond the most trivial scenario, forget about drag and drop, and get ready to write some serious amount of arcane code. You want to connect to a web service through WSDL? Well, this will require some code to be written, some files to be packaged, and debugging will keep you busy for quite some time. Could you use the sexy process simulator for process debugging? Forget about it…

As you dive deeper into this $300,000 piece of software, you then realize that the architecture you were sold turns out to be some scary patchwork of disparate technologies that were quickly cobbled together. While getting a process to call an external service (outbound call) was doable, getting an external service to call a process (inbound call) does not seem to be part of the offering, and you need to implement your own listener as a Servlet for it to be done. Nice…

Then comes the really fun part: the business folks want a different user interface for their workflow. The one you got out of the box seems to be working pretty well, and you could display your company logo at the top left, but somehow the suits have something different in mind, and they want it now. They paid $300,000 for some magic pixie dust that gives them business agility, and they expect it to make you a contortionist worthy of a full-time job with Cirque du Soleil. So you end up spending the next six months writing massive amounts of JavaScript code that will hardcode the customer’s process deep into the user interface. You will be late, over budget, and won’t benefit from future software upgrades, for what you have now is built upon a completely different codebase. Great…

What I am describing here is not specific to the particular competitor I referred to above. As a matter of fact, it has become the norm in the BPM industry today, leading to an alarming failure rate for BPM projects that go over time and over budget in most cases, and an abyssmally low level of repeat sales—same customer buying again from the same vendor.

The problem mainly comes from the fact that BPM is being sold to business buyers as a way for business people to manage executable business processes without involvement from IT folks. But experience tells us that such a thing does not exist, for both technical and practical reasons. At a technical level, the technology allowing business analysts to design an executable process providing transactional integration with back-end systems and complex interactions with human beings does not exist. It’s science fiction. It’s snake oil. It’s a lie. Pure and simple. And at a practical level, business people do not want to take responsibility for executable processes deployed in a production environment. They’re simply too smart for that, and they’d rather leave it to the poor IT folks who have been doing it for decades now.

As a result, most BPM vendors sell this stupid vision to naive customers upstream, then make up for it by deploying armies of expert consultants to write a lot of code that is making processes utterly inflexible downstream. And when they’re done with it, they run as fast as they can to the next customer. Awesome…

Quite frankly, this is not the BPM my friend Howard Smith and I had in mind back in 2000 when we laid the foundations for it. This is why the BPM 2.0 moniker was introduced last year. It is time for a complete reset of expectations, and the adoption of business practices that will demonstrate to customers the real value that BPM can bring to their businesses, without hiding anything. This is also the reason why Intalio adopted an open-source model. Putting lipstick on a pig does not work so well with open source…

Last year, I complained that nobody cared about BPM, and that it was best illustrated by the fact that very few customers actually talked about their BPM projects, what was working, and what was not. So let’s start on the right foot, and let’s give them the stage for a change. Here is what customers have to say about our product, and what they are doing with it. And if that was not enough, you can find more of it there. And if you want to talk to them, let me know, and I will be more than happy to make some introductions. Enjoy!

Intalio|BPMS is the future of Business Processes Managment. Graphical process design tool, web-based workflow user interface, automatic generation of forms, and enterprise-class open-source architecture. It has everything our customers have been asking for.”
—Konstantin Boehm, Ancud IT

Intalio|BPMS is a very powerful BPM tool for process analysts. It bridges the gap between Business and IT in an elegant, easy to use manner.”
—Konstantin Boehm, Ancud IT

Having worked with manufacturing customers in multiple industries to deploy business processes for the plant floor that improve operational and supply chain efficiency, we have used various BPM technologies, and Intalio|BPMS distinguishes itself as an exceptional value. Intalio’s open standard technology has a full range of functionality that enables manufacturers to very cost effectively build and scale business processes across their operations.”
—John Mahoney, B2D Solutions

Intalio’s product has reached a level of maturity and sophistication that makes it the absolute leader in the BPMS space.”
—Mirela Cukovic, Broadlane

Intalio|BPMS perfectly completes Thaler’s SOA. It makes service orchestration and composite applications a reality, without having to write a single line of code. Application development enters a new era where business takes control back from IT.”
—Pierre-Philippe Bastin, Callataÿ & Wouters

We selected Intalio|BPMS as a best of breed in the new category of BPMS based on its thorough implementation of BPEL4WS. Our decision was also influenced by the maturity of Intalio’s integrated tools covering the design, deployment and management of enterprise IT processes that can be directly deployed onto an existing heterogeneous IT infrastructure consisting of both new best-of-breed and legacy applications that comprise today’s distributed computing environment.”
—Howard Smith, Computer Sciences Corporation

After building three prototypes with Intalio and two competing products, I was sure that the Intalio approach was the best.”
—Heinz Drews, Computer Sciences Corporation

It is clear that a product such as Intalio|BPMS is the direction of business process management systems for the future.”
—Clive Finkelstein, DM Review

Using Intalio|BPMS will allow projects to be deployed within two to four weeks, instead of the multi-month or multi-year cycles traditionally associated with large-scale IAM projects. We evaluated many other BPM solutions currently available on the market, but no other product came close to Intalio’s in terms of robustness, scalability, and ease of deployment.”
—Ameet Shah, Diamelle

Oooh! I like it…”
—Gil Regev, EPFL

Having a real, executable BPM 2.0 environment at your fingertips makes you rethink how you architect solutions. It simply gets you wild again. Keep up the good work!”
—Jose Diego de La Cruz, EPFL

The release of Tempo—the human interaction workflow component of the Intalio BPM suite—to Open Source further demonstrates Intalio’s industry leadership and commitment to making BPM 2.0 a reality. Tempo promotes the adoption of open standards, using XForms to implement the BPEL4People paper jointly drafted by IBM and SAP. Tempo raises the bar on what organizations should expect from a human interaction workflow component, and simultaneously eliminates cost as a barrier to adoption. I strongly encourage all interested parties to download, evaluate, and collaborate on enhancements to this significant contribution to the BPM and Open Source communities.”
—Vernon Stinebaker, Everse Corporation

My experience with Business Process Management and Workflow is based on the automation of the standards production chain at the ISO Central Secretariat in Geneva. At that time, I had just a workflow engine for the orchestration of services. With a product like Intalio|BPMS, my job would have been much simpler.”
—Alexander Samarin, ISO

There is more to the tool than meets the eye. Its capabilities will surprise you.”
—Jesse Velasco, MSI

I have now tested Intalio|BPMS, and the product is great. I have been looking for such an Open Source platform for years, and I am glad it is finally available on the market. Your decision to use BPMN for modelling processes is right on, and so is the choice of Eclipse as underlying framework. It is really nice to see BPMN becoming ready for prime time through Intalio’s work.”
—Tore Storodegard, Mobic

Part of our decision to adopt Intalio|BPMS was its technical architecture and capabilities. From modeling to execution, we were pleased to see that Intalio engineers decided to rely on many industry standards and Open Source building blocks. Our main challenge was to integrate the Intalio|Workflow (Project Tempo) with the Open Source LifeRay portal, our preferred portal framework. Tempo uses proven and well-known frameworks and standards, such as Spring, Web Flow, XForms, and AJAX. As a result, our technical team was able to start working quickly on the integration project. Things went even faster once we engaged with Intalio’s technical support team. Today, we are proud to offer a powerful duo that combines an enterprise-grade portal with solid foundations for sales process management, tightly integrated with external systems such as Salesforce.com and Oracle E-Business Suite.”
—Natalie Watson, OperMIX

Our experience in sales coaching and practice improvement has demonstrated that customer-related processes are the most critical and complex in any organization. Yet, sales people and executives need to keep very flexible practices, as market needs are constantly shifting. While using CRM or ERP solutions can certainly help deal with standard processes (30 to 50% of end-to-end processes), it cannot provide enough flexibility to support unique sales processes that set a company apart from its competition. Our customers are now starting to realize how BPM can be applied to customer satisfaction and loyalty building. Over other BPM solutions that are available in the market today, I believe Intalio|BPMS is the best choice for many reasons: it protects customer’s investment on the long term using standard approaches and technologies, it represents the lowest total cost of ownership, and above all, it is highly flexible and reactive, allowing us to change processes on the fly.”
—Hicham Jellab, OperMIX

I cannot believe it. I modeled and deployed my first process in a record time. I think you have a very nice tool. Congratulations!”
—Christian Thoma, University of Applied Sciences, Karlsruhe

Designing processes on Intalio|Designer is flawless. Great tool and in-depth training made us realize the true potential Intalio can deliver.”
—Harish Krishnaji Rao, e4e, Inc.

Entry filed under: BPM 2.0

14 Comments - Add a comment

1. Francis Ip  |  February 16th, 2007 at 9:11 pm

BPMS is still in its infancy. It has a long way to go before it can measure up to a SCADA (Supervisory Control And Data Acquisition) system that controls real-time processes like manufacturing, intelligent building (air purification, lighting, temperature, security, access, power, etc.), and the like.

Missing from the current BPMS is a key element—interfaces to interoperate with other systems. An interface is an elementary systems engineering concept that all engineers should know, if one claims to be a software engineer or architect. The current BPMN is a close system that provides no means to define interfaces. This is the key reason why a lot of underlying codes are needed to make a BPMS work.

The customization of interfaces is a typical activity that the object-oriented approach was supposed to solve. It looks like the practices of the 60’s prevail, even with structured and object-oriented approaches. The same old problem of writing custom code begs for future maintenance work when a new version of software is released. Will IT people ever learn?

Even though BizTalk doesn’t support BPMN, but it has a mapper with which an analyst can define interfaces for interoperating with other systems, including EDI, which is missing in many other BPMS.

2. James Governor  |  February 19th, 2007 at 5:13 am

Ismael,

One thing that strikes me with your list is that it’s quite consulting/IT services led.

What about end-user customers?

3. h.o.s.a.m.r.e.d.  |  February 20th, 2007 at 9:52 am

Hi,

Interesting topic. I have recent experience in the BPM field, using FileNet. For a customer in the Gulf, the project was going well initially. But after the customer saw it and used the workflow, they started a development cycle to enhance their processes. This required changes in the process design and in the code, because the solution provided links from the workflow design to Java API calls.

My point is the following: when a customer makes first use of BPM, you should expect that your project will require future enhancements, for both processes and the customer’s business.

4. Dian Schaffhauser  |  February 20th, 2007 at 11:30 am

Here’s a case study that we recently ran on BPMEnterprise.com about an Intalio customer—the Animal Health Service in central Netherlands. In that situation, it’s more of a message management system. Interestingly, with 3 years into the effort, the organization has another 2 years to go, they believe, before they’ll be fully moved onto the Intalio platform.

5. Todd Biske&hellip  |  February 20th, 2007 at 1:29 pm

[…] The second post that caught my eye was Ismael Ghalimi’s post… […]

6. Ismael Ghalimi  |  February 20th, 2007 at 2:29 pm

Francis,

You might be interested to learn that Intalio|Designer has the exact same mapper as Microsoft BizTalk’s. And as far as the development of interfaces is concerned, for both process-to-system interfaces as well as process-to-human ones, you can design them without having to write a single line of code using our product. I think you should really take a look at it.

Best regards
 -Ismael

7. Ismael Ghalimi  |  February 20th, 2007 at 2:32 pm

h.o.s.a.m.r.e.d.

I full agree with you. Code gets in the way of agility. Zero Code is the answer.

Best regards
 -Ismael

8. Ismael Ghalimi  |  February 20th, 2007 at 2:34 pm

James,

System Integrators tend to be the most vocal among our customers, but end-users have no problem sharing the love. For more feedback from customers, you can take a look at this list of quotes. You will find many more end-users there.

Best regards
 -Ismael

9. Ismael Ghalimi  |  February 20th, 2007 at 2:38 pm

Dian,

Even though the project with the Animal Health Service required a fair amount of system-to-system messaging, I would not reduce it to just that. In fact, they also had to develop thousands of human workflows, with fairly complex user interfaces for them. And as far as deployment time is concerned, it’s largely due to the fact that we’re dealing there with the largest BPM deployment ever attempted, for any product I know (250,000 process steps, 100,000 users). Most of our projects are completed within weeks or months typically.

Best regards
 -Ismael

10. Francis Ip  |  February 20th, 2007 at 5:44 pm

Ismael,

I will, when the new version of Intalio|BPMS comes out of Beta. I will evaluate the mapper, the rule engine, the designer, the simulator, the activity monitor, and also the help in designer, it there is one. If they are as good as you claim, I will definitely use them, instead of Protege 2000, to build the enterprise ontology and the knowledge base of EARN.

In the meantime, I am going to make assumptions about the capabilities of each component in the BPMS, and articulate a conceptual architecture on building a “dynamic” EARN.

Best regards
 -Francis

11. Luis Bender  |  February 22nd, 2007 at 6:20 am

Ismael,

The scenario you described is not exclusive to BPM software, it may also be applied to implementations of ERP, CRM, and many other software packages. When you have too much customization in a BPM (or ERP, or CRM) project, you probably are in one of the two following situations:

1. You choose the wrong tool to address your process needs.
2. Your implementation methodology is flawed, and you’re not driving the project by the best cost-benefit decisions.

Anyway, I can’t see why choosing Intalio’s BPMS instead of one from it’s competitors Appian, Savvion, Lombardi, or Pegasystems would increase the success rate so much. Can you?

Best regards
-Luis Bender

12. Ismael Ghalimi  |  February 23rd, 2007 at 11:52 am

Luis,

I agree with your analysis.

Regarding your question, yes, I can see why Intalio|BPMS would deliver better results. I would invoke two reasons: The first is technical, and due to the fact that Intalio|BPMS is based on a Zero Code development approach. The less code you have to write, the easier it gets to maintain complex processes. The second is practical, and due to the fact that customers use our product directly, instead of relying on services provided by the vendor. Doing so, they have more skin in the game, and their success rate tends to go up.

Best regards
 -Ismael

13. IT|Redux&hellip  |  February 28th, 2007 at 11:12 am

[…] 3. By raising the abstraction level even higher, the BPM vendor gains a sexy tool that is great for sales presentations, but makes it even more difficult upon its professional services resources—remember, customers rarely implement processes themselves, as described in this past article—to actually implement executable business processes. Where you already had two levels (graphical notation and code), you now have three (graphical notation for business analysts, graphical notation for technical people, code). Synchronization and dependence tracking is hard enough with two levels, and that’s the reason why Intalio opted for a Zero Code, single level approach. Three makes it just impossible. Newton’s three laws of motion work well with one or two bodies, but as soon as you get three, you end up having to solve complex differential equations that are best handled by chaos theory. Well, BPM follows similar rules, and when you get from one, to two, then three levels of abstractions, everything falls apart. […]

14. Enterprise Irregulars&hellip  |  March 4th, 2007 at 12:32 am

[…] Two weeks ago, a couple of independent BPM vendors announced plans… […]

Trackback this post  |  Subscribe to the comments via RSS Feed

Leave a Comment

Required

Required, hidden