Business Rules in or out of BPM?

on August 24, 2010
BPM vs BRMS

All BPMS or All BRMS?

A comment on my post on rules engine algorithms inspired this follow-up post on BPM and business rules.

Business process management (BPM) is a discipline for designing, automating, measuring, and improving business processes. Business rules management (which has since evolved into business decision management or decision management), on the other hand, is a discipline for designing, automating, measuring, and improving business rules and decisions. The debate on whether organizations should implement business processes or business rules has been raging since the late 90’s. While many have now concluded that these approaches work hand in hand, I still see a few confused heads.

Vendors are mostly to blame for the divide. BPMS vendors (the “S” in “BPMS” stands for “System” or “Suite”) used to advocate that business processes are meant to encode both routing and decisions. Conversely, Business Rules Management System (BRMS) vendors used to say that a rules service can define all decision logic (the rules) as well as the sequencing of those packets of rules (the rule or decision flow). In short, both agreed that you only had to use one tool, but they disagreed on which one.

Debunking the “All BRMS” Story

Since I come from the business rules world, I will start by arguing against an “All BRMS” approach.

A rules service is great for single “hit-and-run” transactions but not so great with long ones. A long-running transaction waits for appropriate actions in order to continue to the next step. The action could be some form of human intervention such as a manual approval or a synchronous API call to a local or remote system like retrieving a credit report from a credit bureau. If the human intervention doesn’t take place of your API call fail, you want your transaction to wait patiently until the appropriate actions have been taken.

However, rules services aren’t well-suited for waiting patiently. While a software architect could deploy rules as a stateful service, many do not like that design due to its complexity and lack of scalability. As a work around, with careful design, a stateless service could possibly act like a state machine. We have taken this approach on a few occasions when a BPM implementation was not an option. Even so, we would not have taken this approach if BPM technology was available.

Debunking the “All BPMS” Story

Now, I’ll argue against an “All BPMS” approach.

A BPMS is great for orchestrating services and systems. Therefore, they can handle long-running transaction without issues. However, they’re not so great when it comes to the maintenance of the complex decisions embedded in processes. While BPM technologies can handle simple decisions, complex decisions will lead to so many links and nodes that you’ll have difficulty visualizing the overall process, let alone the decisions. I think about the Traffic Light Tree sculpture in London. With so many traffic lights, it’s impossible to tell who’s supposed to go. In addition, BPM technologies are usually limited in the decision logic representations that they support. This is where BRMS excels.

Finding the Right Balance

So while it’s possible to do all things with BPMS or BRMS, it’s not ideal. Instead, I recommend using them together. The trick is finding the right balance between processes and decisions. For example, insurance underwriting involves both processes and decisions. The processes include the various systems and people involved in processing an insurance application. How and when they interact with each other are best managed through a BPMS. The decisions, on the other hand, include approval, coverage, premium, etc. How these decisions are made are best managed through BRMS.

Learn more about our business rules and decision management platform, SMARTS™.

Search Posts by Category

ABOUT US

Sparkling Logic Inc. is a Silicon Valley-based company dedicated to helping organizations automate and optimize key decisions in daily business operations and customer interactions in a low-code, no-code environment. Our core product, SMARTS™ Data-Powered Decision Manager, is an all-in-one decision management platform designed for business analysts to quickly automate and continuously optimize complex operational decisions. Learn more by requesting a live demo or free trial today.