Gartner Day 1: Benoit Lheureux

I decided on Benoit Lheureux’ session on BPM’s role in multi-enterprise commerce, although we’re had some technical difficulties and started late. This is much more about B2B and middleware than BPM, so it should be interesting to hear the perspective from the B2B viewpoint. If this turns out to be a dog, I’ll be out of here for Process Modelling for Profit, but the slides look interesting and I’m very interested in inter-organization collaboration and process choreography. He just used the word “mashup”, so I think that I’m staying, although the slightly smarmy “my friends” method of address did put me off a bit.

By now, the Gartner presentation framework is clear: each has exactly 20 slides; each has a Key Issues (agenda) slide with exactly 3 points (although Lheureux cheated by inserting a few extra slides that weren’t in the downloaded version of the presentation). People with 120-slide presentations, take note of how the professionals do it.

Lheureux describes his research as looking at multi-enterprise integration, or how to bind your business processes with the business processes of your trading partners. He opens with the question of how tightly you should be binding your applications and business processes with those of your business partners.

He makes the bold statement “EDI software is dead”, having been replaced by B2B gateway software that is more process-aware, and sees B2B projects as proliferating — doubling in the next five years — since there is a widespread recognition that organizations realize that their business processes are not just internal any more, and B2B needs to be a strategy rather than a discrete project. It used to be that you had your applications running internally, with some degree (if you’re lucky) of internal visibility, but no external integration or visibility: you’d need some sort of manual process for providing both integration and visibility to external business partners. Now, however, you can’t be competitive working that way any more. Furthermore, some of the functions done within organizations are being outsourced, further driving B2B requirements.

Gartner predicts that by 2011, 25% of new business software will be delivered as SaaS. Not 25% of what you’re running in total, but 25% of the new stuff; still, that’s huge. And I drink that particular Kool-Aid: I believe that this shift is happening now, and will continue to grow. SaaS is one form of B2B, in that you’re integrating in some way with the SaaS provider, but this also provides the potential to integrate with other trading partners via the SaaS platform itself. In addition to the SaaS model of multi-enterprise integration, there’s also the more traditional EDI-style e-commerce, plus integration via portals or mashups.

Lheureux discusses three approaches for implementing these B2B projects: run your own B2B gateway, outsource the B2B infrastructure (previously “EDI VAN”), or outsource the entire B2B project (previously “managed EDI”). He then dug into the issues of the choreography and monitoring of multi-enterprise BPM.

Gartner also predicts that by 2011, at least 40% of all new multi-enterprise integration projects will use BPMS. I can agree with this one too; besides, I figure if it doesn’t look like it’s going to come true, Gartner will just change the definition of BPM again. 🙂

He then discussed the four multi-enterprise BPM styles:

  1. Blind document/transaction exchange, e.g., exchange purchase orders, to lower transaction cost, latency and errors by increasing automation. No shared process visibility or execution, and the process is difficult to change.
  2. Intelligent document/transaction exchange, e.g., shared view of order-to-cash process, to provide some process visibility.
  3. Multi-enterprise applications, e.g., shared execution of vendor-managed inventory, to centralize process control. This maximizes process visibility since both trading partners are participating in the same process (not just exposing a limited view of an internal process from one to another), but this is a big thing to do and requires a great deal of trust between the trading partners.
  4. Multi-enterprise BPMS and rules, e.g., shared compliance management, in order to centralize the process and rules definition. This increases flexibility considerably, but again requires a great deal of trust and collaboration between the trading partners in order to make this work.

Organizations are going to have to implement more than one of these styles of multi-enterprise integration over the next few years as this field evolves. And if you’re already using B2B, B2B-enabled middleware or BPM, portals, SaaS or a variety of other technologies, then you already have some of the infrastructure in place to get started at this. The support for B2B versions of many of the standard BPM functionalities is just not there yet, however: practically no one is doing B2B process simulation, for example.

He ended up with some recommendations for multi-enterprise BPM strategy, such as synchronizing multi-enterprise and internal BPM projects, and developing a shared B2B infrastructure, with a focus on enabling shared process visibility (via BAM) and shared process control (via business rules).

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.