Main

February 18, 2009

Jobs: RuleBurst (Haley Rules) Modeler

Jobs: RuleBurst (Haley Rules) Modeler  

BIZRULES is looking for a Haley Rules Modeler *

The Haley Rule Modeler designs and implements the Haley Rules using the Haley data model and rules. The Haley Rule Modeler is expected to have extensive experience implementing the Haley rules engine and should have experience implementing the Haley rules engine in the context of Seibel implementations.

* by "Haley Rules" the client means
- RuleBurst Rule Engine (BRE)
- SoftLaw Rule Engine (BRE) / Expert System (ES) 
- Haley Office Rules
- Haley Expert Rules
- Haley Business Rule Engine (BRE)

This is for a long term project. RULEBURST/SOFTLAW experts anywhere in the world (Australia, UK, Canada, USA, etc.) are welcome to apply for this challenging opportunity! Relocation available for top candidates.

If you are interested and have experience with RULEBURST / SOFTLAW / HALEY RULES contact us or send your resume to

Careers8@BizRules.com

+1 305.994.9510

September 12, 2008

Bosch drives into the rule engine market

Bosch has joined the club. On September 8, 2008 The Bosch Group acquired Innovations Software Technology. Both companies are based in Germany. This move heats up the BRE/BRMS market consolidation that was already sizzling:

Sep. 2008 –The Bosch Group acquired Innovations Software Technology
Jul. 2008 - IBM announced their intent to buy ILOG
Nov. 2007 – RuleBurst acquired Haley Rules
Oct. 2007 – SAP acquired Yasu
Aug. 2007 – Trilogy acquired Gensym
Oct. 2006 – Planet Group acquired ACI Worldwide
Jan. 2006 – Trilogy acquired Versata
Jan. 2006 – MDA acquired Mindbox
Sep. 2005 – Fair Isaac acquired RulesPower

(click to see the new BRE Family Tree

Oracle and Microsoft entered the business rule engine (BRE) market by building their own rule engine technology. Competitors, however, took a different approach. Global technology leaders IBM and SAP acquired BRE vendors ILOG and Yasu. Insurance software vendor MDA acquired BRE vendor Mindbox. And rule engine vendors Fair Isaac and Trilogy acquired smaller BRE vendors RulesPower, Versata, and Gensym.

I asked David S. Kim, Managing Director and CEO of Innovations Software Technology, to share his thoughts and tell us what this means to customers, end-users, and to the rules market. Here’s what he had to say in our email discussion.

How does the Bosch acquisition of Innovations compare to the other acquisitions and consolidation in the rules industry?

“The big difference is that we were not acquired to have our product line integrated into a stack of other software. We were acquired to be the core of a new software and systems company within The Bosch Group. We will be creating new technologies and value chains within Bosch and open the door to new lines of business,” Kim said.

Continue reading "Bosch drives into the rule engine market" »

July 29, 2008

BRE Family Tree update shows IBM ILOG acquisition

The latest BRE Family Tree update is here. There you can download the new family tree in jpg, png, or tif formats. We have redesigned the family tree to show a lot more information than before. To make the chart less commercial, we got rid of the colors that indicated which BRE vendors were BIZRULES partners. Now the chart can be used by anyone, vendor, salesman, consultant, or customer who wants to see "the state of the BRE market" or who wants a guide to help them select their BRE vendor.

This new diagram also shows the connection to Rete, CLIPS, Jess, and Drools. Rule engines that use the Rete algorithm have an "R" flag. Engines based on CLIPS have a "C" flag. and engines based on Jess have a "J" flag.

We also show what environments each rule engine runs on (i.e. COBOL, C++, Java, and .Net), and whether it runs natively on that environment. This section is still under construction. We've asked BRE vendors to confirm this information, so we can finalize this section. We planned to present this chart for the first time at the upcoming October Rules Fest conference in Dallas, TX.  But now that IBM and ILOG are uniting, I thought you would like to see this chart now.  If you are a vendor representative, please take a look at your product data and let us know if we missed anything or if you'd like to update your product information. 

This is a guide to many of the leading BRE vendors that we are familiar with. It is not an exhaustive or complete list - there are probably other BREs on the market and not on the list that we haven't even heard of yet. Let us know who you are!  This guide is a good start for companies trying to evaluate and assess the BRE market. 

If you need more information about these BRE vendors, or if you need help selecting the best and the right rule engine for your particular needs, call BIZRULES at 305.994.9510. Some of you have asked for the BRE Family Tree poster... Call us for info about that.

BRE Family Tree 2008

July 28, 2008

IBM sets the course and ILOG steers the Ship

IBM is one of the few companies that sets the course in technology. Now they will use ILOG to steer the ship.

IBM has announced their intention to buy ILOG for $340 million USD. ILOG is widely recognized as one of the leading BRMS software vendors.

This move helps legitimize business rules management systems (BRMS) and rule engine technology. This will shake up the playing field in the BRMS/BRE space as ILOG BRMS competitors aligned with and partnered with IBM will need to rethink their strategy and technology.

Integrating ILOG BRMS with IBM's BPM and SOA technologies will also raise the bar in the BPM/BRMS space. Pegasystems has been a leader in the BPM/BRMS space, which Pega basically invented, ever since they released their PRPC PegaRULES Process Commmander product. BPM vendors lacking BRE capabilities are going to have to start OEMing a BRE tool, building one, or buying one like IBM did.

This move also speeds up the BRMS market consolidation that has been picking up steam in recent years. Last year SAP acquired the Yasu rule engine, and Ruleburst (previously SoftLaw) acquired Haley Rules. Prior to that, of course, Fair Isaac acquired RulesPower, and Trilogy bought Versata then Gensym. Going further back, CA bought Platinum Technology (which had acquired AION and the AION BRE). AION, of course, was started by a bunch of ex-IBMers, who wanted to improve on IBM's TIRS (The Integrated Reasoning Solution) mainframe rule engine, who left IBM to develop the AION rule engine. After TIRS, IBM began working on Common Rules. That IBM rule technology and research effort could be combined with ILOG's BRMS tool in the future.

IBM also plans to embed ILOG rules technology across its broad product offerings, further strengthening their products and further legitimizing rules technology.

The business rules market is alive and well. The tools are getting better. The vendors are getting larger. The methodologies are getting easier. As rules-based tools become more widely adopted, companies will be able to spend more time designing quality rules and managing effective rules, and less time worrying about the rule engine technology under the hood.

Companies that resisted rules technologies and methodologies in the past almost missed the boat. Now they have another chance to get on board the rules express.  IBM is ready to rule again.

See also:

 

 

March 13, 2008

Introducing the BIZRULES® RuleMap™

Documenting business rules is a good first step on the path towards the business rules approach.

But sometimes that's not enough.  Taking the next step and getting to the next level requires simulating business rules so they are easy to review and verify.

Over the past few months BIZRULES has been working on a new product that lets us do both. It's a visual tool that lets us not only draw diagrams of business rule models, it also lets us simulate the rule logic. This tool helps us speed up the rules harvesting process and improves the quality of our rulebooks.

BIZRULES® RuleMap™ is an interactive rulebook that models business rules and simulates business logic.  This logical model lets you see how your business rules really work. It lets you visualize the Reasoning Chain™ that leads to smart conclusions and right decisions.


We use this tool to document your business rules independent of any BRE - yet it can be implemented using any BRE. Again, this is a logical model of your business rules.  It can be used as the rulebook or specs for authoring the rules in any BRE.

Take a look at a sample RuleMap. And let us know what you think. Contact us for pricing or a web demo.

 

 

July 12, 2007

JOBS: Business Rule Anaysts & BRE Developers/Architects

BizRules is looking for

  • Business Rule Analysts
  • Business Requirements Analysts
  • BRE/BRMS developers & architects fluent with rule engines, especially ILOG JRules, PegaRULES PRPC, Haley Rules, and Fair Isaac Blaze Advisor
  • IBM WAS WebSphere Application Server / J2EE architects

for permanent full-time and long-term contract opportunities nationwide. If you have experience as a rules analyst, developer, or architect and are looking for challenging projects with Fortune 500 clients, contact BIZRULES or send your resume to

JOBS [at] BIZRULES.COM

305.994.9510

(See http://bizrules.com/us/page/careers.htm for more detailed job descriptions)

October 11, 2006

Press Release: ILOG Reveals Its Acceptance Into IBM SOA Specialty Program - Quick Facts

MOUNTAIN VIEW, Calif. – October 11, 2006 – ILOG, a leading Business Rule Management System (BRMS) vendor, today announced its acceptance into the IBM SOA Specialty Program after successfully completing IBM’s extensive service-oriented architecture (SOA) technical and business requirements.

With this achievement, ILOG has integrated its JRules™ BRMS seamlessly with the IBM SOA Foundation, a single, integrated platform that combines application server and integration capabilities.

According to ILOG, ILOG JRules is the first Business Rule Management System to be integrated with the IBM WebSphere Process Server, a key element of IBM's SOA offering.

Source: http://www.tradingmarkets.com/.site/news/BREAKING%20NEWS/451679/

September 29, 2006

Knowledge-Based Systems Defined (by IBM)

http://www.insurancenetworking.com/protected/article.cfm?articleId=4331&pb=ros

Here's a great article in Insurance Networking News where James Bisker, global insurance industry leader, IBM Institute for Business Value, defines knowledge-based, expert and artificial intelligence systems and provides insight into how they can benefit insurance industry operations. He says:

"The type of KBS that is often referred to as an 'expert system' is technically known as a rule-based system."
At first I didn't totally agree and said so right here. Then I felt bad saying he was wrong and I was right. So what I'd really like to say is that the article is great, and James has said some pretty wonderful things about technology that I am pretty passionate about: rules, knowledge, A.I., and expert systems. Sure, I have some thoughts that are a little different, but that doesn't mean that one of us is wrong and the other is right. Life is too short for that.

It means that we both believe the same technologies can help business improve their condition. We see a few minor details a little differently, but who cares. The key point is that IBM is telling us that AI, expert systems, and rule engines are driving the insurance industry forward. This is great stuff! Executives everywhere would do themselves a disservice if they ignore his advice.

My newly enlightened take-way from this article is that a key executive at IBM is helping to legitimize much-maligned solutions like expert systems and knowledge management. Wow!

James says that a Knowledge based system is referred to or technically known as an expert system. I agree. Then he goes on to say that a knowledge-based system is the same as a rule-based system.

I see them as two different types of applications, however, with slightly different technology behind each.

I believe the difference between knowledge-based and rule-based systems is subtle, yet criticially important. Here's why: companies spend millions of dollars buying rule-based and knowledge SW packages every year. Sometimes they buy a rule-based solution when they really need a knowledge-based solution, and vice-versa.

I wrote about the differences earlier:

James goes on to say really smart things about the value of capturing corporate knowledge and building KBSs. I agree completely:

"One of the important implications of using KBSs will center around their impact on individual employees. This is especially true as more insurance employees leave the workforce as they retire or seek other employment. In this case, using knowledge management systems to capture the knowledge of internal experts will be crucial. Being able to extract corporate knowledge and distribute it consistently will ensure steady performance and efficiency in times of transition. KBSs also allow less experienced staff to operate at higher levels with less oversight, which frees up more senior personnel for more complex activities. Finally, and perhaps most importantly, the use of these systems increases consistency and compliance to internal and external policies and regulations."

I wrote recently (Knowledge Management is Key to Preventing Brain Drain. BP found out the hard way) about what happened to BP when they didn't retain knowledge, and what happened to Mobil Oil when they did.

Locations of visitors to this page