Visio Premium's BPMN template is a drawing tool for BPMN diagrams, not a true modeling tool that internally understands the BPMN metamodel. It does provide a validation feature that uses Visio 2010's new Validation API to check the diagram against the rules of the BPMN 1.2 spec, and that is helpful. But deep down, the "model" is just shapes on pages. Nevertheless, it is possible to generate from the diagram a true BPMN 2.
"BPM is dead." Really?? No, I don't think so. In fact, we're seeing more innovation now in the technology of BPM than at any time in the past several years. Big Data, real-time sense and respond, predictive analytics, goal-driven and "adaptive" processes, social BPM, mobility.... The list goes on. Wait, you say, that's not really BPM. But what you mean is they are missing from the current generation of BPM Suites.
BPM took center stage on Day 2 of IBM Impact, which used to be a SOA/BPM event but somehow seems to have morphed into a cloud/social/mobile/collaboration event. Wait, isn't that Lotusphere? It was sometimes hard to tell. The key BPM feature touted on Day 1 - identifying other process experts at runtime and contacting them right away by instant messaging - I know I saw on the Lotusphere main stage back before Y2K.
I fretted about this for weeks but I finally pulled the trigger. My book BPMN Method and Style is now available as a Kindle ebook, compatible with Kindle, Kindle Fire, Kindle for iPad, or Kindle for PC. I got a lot of requests for this, especially international, so we'll see if there is a market for it or not. I worked hard on the graphics. In the end there is only so much you can do with them in Kindle format.
Our next BPMN Method and Style live-online (virtual classroom) training is May 7-9 from 11am-4pm ET, 8am-1pm PT, or 5pm-10pm CET. This class is the gold standard in BPMN training and certification. It teaches you not only the BPMN shapes and symbols you need to learn (and how to use them correctly!)... and which ones you can safely ignore, but it provides prescriptive guidance that ensures that your BPMN diagrams are clear and complete, shareable across the business and between business and IT.
At the BPMN Workshop in Lucerne two weeks ago I presented a talk called "Fulfilling the Promises of BPMN 2.0." The basic point was that the BPMN 2.0 specification by itself is insufficient to deliver on the standard's two most fundamental promises: first, as a semantically precise process notation, that the meaning of the depicted process logic is unambiguous from the diagram alone; and second, as an XML process description language (even limited to non-executable model elements in the Analytic subclass), that the serialization rules are sufficiently unambiguous to allow automated interchange between tools.
Often the Gartner BPM conference seems to me the same-old same-old, but I have to say I am getting some valuable new perspective at this year's event in Baltimore. The new wrinkle this year is what Gartner is calling iBPMS, the "i" meaning intelligent. It's really shorthand for a number of new technology-based capabilities that have been swirling around the edges of BPM for a couple years, but which have now graduated to the Magic Quadrant checklist: adaptive, predictive, sensor- and event-aware, rule-driven, context-aware, real-time, social, mobile, cloud-based, maybe even gamified.
It was a longer wait than I expected, but in BPM 7.5.1, IBM is now providing real BPMN 2.0 support. I haven't had a chance to play with it yet or look at the documentation - I think GA is later this week - but I got the briefing from the team. And I have to say, I am very happy with what I saw. In a recent post, I talked about what "
I spend a lot of my time working on tools to validate BPMN process models. You might ask, don't BPMN tools do that already themselves? The good ones do, but only according to their own interpretation of the rules in the BPMN specification. It is unforgivable, but in the 7+ years that have elapsed from the publication of BPMN 1.0 until today, the spec has never actually enumerated its rules in one place, such as an Appendix.
I was expecting more feedback on my Executable BPMN 2.0 post. I did get a thoughtful and amusing rant from Alex Pavlov. He dismisses the whole idea of executable BPMN 2.0 as a cynical ploy by the middleware vendors that created it. Besides making some good points on the possibility of executable BPMN 2.0, he challenges me to defend why anyone would think adopting the standard is a good idea in the first place.