The Premier .NET Solution for
Authoring, Managing and Executing Business Rules

Home | Contact Us
Resources > Blogs > Theresa O'Neil > August 2009 > The Rules for Beautiful, Flexible Business Processes

The Rules for Beautiful, Flexible Business Processes

Jim Sinur’s insightful blog entry http://blogs.gartner.com/jim_sinur/2009/07/29/bpm-not-only-saves-money-it-is-visually-appealing/ states one of the more guttural appeals of BPM: “I think deep down we find BPM visually appealing.” BPM is like the guy who goes to the gym every morning while we’re checking email: muscle-bound and handsome.
As business users define processes, they may find that defining all the permutations around decision points can create a workflow that is unwieldy, both in terms of understanding and ability to maintain, execute, and optimize. The process can get—well—ugly. Suddenly, Mr. Fitness is extremely inflexible from too time in the weight room (and orange from too much time in the spray tan booth, but that’s a whole ‘nother topic, as they say).
For example, a workflow may be defined to execute the very complex logic that determines eligibility and pricing for insurance. With the permission of my good friends at ShareVis—whose software helps you create, deploy and maintain very beautiful processes (www.sharevis.com)-- Figure 1 shows how such decision logic, when embedded within a workflow, can make a process very complex.
For example, a single, high-level decision point called “Determine Eligibility” will encompass many underlying decisions and calculations. Figure 2 shows how this high level decision point within the workflow reduces the complexity of the workflow shown in the previous graphic. In this case, the ShareVis process calls InRule to manage and execute the decision logic.
By embedding every decision point within a workflow, organizations are not only making ugly processes, they’re unintentionally embedding decision logic—thus moving away from the vision of SOA. To help streamline business processes, organizations must identify decision logic and manage it differently from flow logic. By externalizing the decision logic from the workflow, a business rule engine can simplify a workflow and make the logic easier to update. Using business rule technology with your BPM tool can help renew the youthful beauty of your most complex business processes.

The underlying rules, logic, and calculations that drive that decision point can be maintained separately from the workflow, by the subject matter experts. Business rule technology, like yoga, brings flexibility and deep thought to complement the power of BPM.
Flexible, beautiful business processes brought to you by the Yogi of IT: Business Rule Technology.
Namaste.
Posted: 7/31/2009 3:29:06 PM by Global Administrator | with 0 comments
Filed under: sharevis


Comments
Blog post currently doesn't have any comments.

Title

Thinking in Rules. Thoughts and observations about business rules in the real world.

About

As Vice President of Business Development, Theresa O'Neil has responsibility for developing worldwide partnerships with ISV, reseller, services, and technology organizations. Prior to joining InRule, O'Neil was an executive at IBM Corporation, where she was responsible for developing the product and marketing strategies for the IBM Content Management and Discovery business. With a focus on growing new businesses, O'Neil has led marketing and strategy for successful software companies of all sizes. She is also a loyal fan of the Chicago White Sox.

Syndication

RSS
Home  |  Contact Us  |  Site Map  |  Terms of Use  |  Privacy
Copyright © 2009 InRule Technology, Inc. All rights reserved. None of the text or images on this page may be reproduced without the express written consent of InRule Technology.