Research Note
Markets
07 April 2003
The Business Rule Engine 2003 Magic Quadrant
J. Sinur

Business rule engines are moving toward maturity. In 2003, they will support business agility when called on to do so.

Core Topic

Architecture and Design for Application Development ~ Application Development


Key Issues

How can AD methodologies contribute to time-to-market results while maintaining quality?

How can AD organizations specify flows, requirements and rules to implement "killer" solutions in a dynamic fashion?


After a 10-year absence from the center stage of technology, business rule technologies, specifically business rule engines (BREs), are making a strong climb out of the Trough of Disillusionment and up the maturity curve on the Hype Cycle. The size of the BRE market is evidence of this trend. We estimate that it now comprises revenue of more than $200 million, and will continue to grow at a steady rate during the next several years.

BRE technology is being included in the area of flow control represented by business process management (BPM) technology, which is pervading many sectors as a compound market. Today, about one-third of the 70 or more vendors in the BPM pure-play market have some form of a BRE, even if it is simplistic rule externalization. There is an emerging concept that service-oriented architecture (SOA) and its associated Web services also should include rules sensitivity. This may occur through 2004; the momentum has yet to be determined.

The business activity monitoring (BAM) market has emerged and is indicating the need for enterprises to change rapidly. Although enterprises initially will make reactive changes, this is better than recognizing problems weeks later and requiring lengthy software change projects to adapt. BAM will allow instant recognition for change and adjustment. BRE technology will allow instant changes where desired, within the bounds of production promotion policies and management audit needs. Thus, constant reactive change will become an area of concern for senior-level management. BRE will be used in conjunction with business modeling, represented in business process analysis (BPA), for planned agility. Although already somewhat present in enterprises with planning cultures, more enterprises will develop scenario plans with the associated rules necessary to adapt to a given scenario. Also, "corporate war game" scenarios will emerge in more-dynamic flows, such as supply or value chains.

Market and Technical Requirement Changes

We have used the technical requirements, slightly modified, from the BRE 2002 Magic Quadrant (see Figure 1 and "The 2002 Business Rule Engine Market Magic Quadrant") to place vendors on the 2003 Magic Quadrant (see Figure 2). Several significant changes occurred in the past year. In 2002, there were few known rule methods. However, there recently has been strong activity from several consulting organizations in the BRE market, including Business Rule Solutions, Knowledge Partners and Knowledge Gravity. These vendors have rule methodologies that can be adapted and used in business applications for rules creation, management and change. In addition, Business Rule Solutions now offers capabilities for terminology management, which is necessary for strong and consistent rule definition.

Figure 1

BRE Technical Requirements


Source: Gartner Research (April 2003)

Figure 2

BRE 2003 Magic Quadrant


Source: Gartner Research

Several vendors have delivered strong rule management technologies, including Corticon, Formula/ESI, ILog, Pegasystems, RulesPower and Sapiens. These capabilities vary in solution set, but they all employ a rules repository that is often active at runtime. Corticon and RulesPower include a powerful rule consistency and collision detection capability that catch business inconsistencies in multiple rules and rule sets. More BRE vendors now include functionality that enables goal-directed flows that can be linked with scenarios. Even many of the simple rule externalization engines offer a form of "truth maintenance" to interrogate rule results at any time, which is required for goal-directed flows.

A sign of a thriving market is the number of viable and mutually beneficial partnerships. BRE vendors are beginning to partner with BPA vendors — for example, Popkin Software and Formula/ESI; we expect more partnership announcements soon. One of the more-mature partnering opportunities is with BPM vendors. For example, FileNet, Staffware and Tibco have BREs as original equipment manufacturer partners; we expect to see more BRE/BPM partnerships.

Another sign of a thriving market is the entrance of new players. In 2002, AMS, RulesPower, SEEC, SoftLaw and YASU Technologies entered the BRE market.

Emerging Trends

We expect continued growth driven by average return-on-investment experiences in the 10 percent to 15 percent range, which is the most-common range that we have seen on surveys and from clients, although there are many intangible benefits. We also expect to see more separation of the leaders from the rest of the vendors because they are accelerating their marketing programs after two years of plus growth in down times. Eventually, fewer vendors will be successful in a steady growth market because of consolidation.

The BRE market could disappear in the long term because technology streams are converging. Many BPM vendors have good-enough rules capabilities to support business agility or to link to multiple popular BREs. We believe that new agile applications will be composed of flow rules and services that leverage SOAs. Therefore, large vendors such as IBM and Microsoft must buy, build or integrate rule engines. We expect it will take 18 months or more for IBM and Microsoft to deliver the kind of functionality that can compete effectively in this market. Ultimately, there may be too few stand-alone rule vendors to justify a separate market.

Vendors with inference engines or multiple engine types likely will survive in this market because they scale to more-difficult problem domains and are also easy enough to use for simplistic applications (see "The 2002 Business Rule Engine Market Magic Quadrant" for a detailed explanation of inferencing).

BRE Magic Quadrant Criteria

Gartner rates vendors in two areas — Completeness of Vision and Ability to Execute — for inclusion in a Magic Quadrant.

Completeness of Vision

Ability to Execute


Acronym Key

BAM Business activity monitoring
BPA Business process analysis
BPM Business process management
BRE Business rule engine
SOA Service-oriented architecture


Bottom Line: The business rule engine market will continue to grow and mature because business requires the kind of agility that needs BREs. Although more original equipment manufacturer and partnership relationships will emerge, there will be a stand-alone rule market as enterprises become more comfortable with rules, and problem domains become more complex over time.


This document has been published by:
Service Date Document #
Application Development & Maintenance 7 April 2003 M-19-4791
Rapid Development Solutions 7 April 2003 M-19-4791
Java Strategies & Technologies 7 April 2003 M-19-4791
PRISM for Applications Development 7 April 2003 M-19-4791
PRISM for Healthcare Payers 7 April 2003 M-19-4791

© 2003 Gartner, Inc. and/or its Affiliates. All Rights Reserved. Reproduction of this publication in any form without prior written permission is forbidden. The information contained herein has been obtained from sources believed to be reliable. Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information. Gartner shall have no liability for errors, omissions or inadequacies in the information contained herein or for interpretations thereof. The reader assumes sole responsibility for the selection of these materials to achieve its intended results. The opinions expressed herein are subject to change without notice.