« January 2007 | Main | March 2007 »

February 26, 2007

Press Release: Oracle Siebel CRM Release 8 is powered by HaleyRulesTM and HaleyAuthorityTM

Oracle's Siebel CRM Release 8 Leverages Haley To Maximize Business Flexibility and Provide Dynamic Privacy Management

PITTSBURGH, PA - January 31, 2007 - Haley Systems, Inc., the technology leader in business rules management systems, today announced that Oracle has embedded HaleyRules(tm) and HaleyAuthority(tm) as the business rules technology in its recently announced Siebel CRM Release 8.

By embedding business rules into Siebel CRM, businesses are able to achieve new levels of cost containment, time-to-market response and long-term competitive advantages. Haley technology is a key part of the Siebel Privacy Management solution within Siebel Universal Customer Master, a comprehensive customer data hub that unifies customer data across multiple business units and functionally disparate systems to provide a trusted authoritative source of customer information across the enterprise.

"Providing business users with an easy to use, yet powerful way to define and refine their business rules is a key ingredient to enabling business agility," says Mark Woollen, Vice President of CRM Product Strategy at Oracle. "By leveraging technology from Haley in Oracle's Siebel CRM Release 8, we are able to provide our customers with a high-performance solution that will enable them to define and enforce the rules they need to stay ahead in today's fast paced, ever changing business environment."

HaleyAuthority is the multi-user rule authoring application that enables business users to capture, organize, manage and test business rules. It stores rules in a central knowledge management database. Rules files are used by Haley's business rules engine - HaleyRules - the technology-leading business rules inference engine for Java and .NET environments. Haley's business rules technology will give Oracle's Siebel CRM users the ability to customize their business processes and policies. As a premier Oracle partner, Haley also offers optional add-on and plug-in products to enhance the Siebel CRM solution and a broad range of expert professional services including consulting, training and implementation.

"The strength of Haley's proven technology, robust lightweight rules engine and unique approach to rules authoring provides business users advanced accessibility and control to capture, manage and review business rules," said Hans Witt, CEO and President of Haley Systems.

Source: http://www.haley.com/newsevents/PressRelease_OracleCRM.html

Haley is a BizRules Alliance Partner

Curtail complexity with a rules engine

Interesting article by Andrew Glover at The Disco Blog on how rule engines remove complexity from rules, and as a result simplify the task of programming rules.

His example is beer recommendation rules, and that alone will make most of you click here.


Comparing Microsoft's Business Rule Engines

Did you know that Microsoft has two rule engines?

Here is a presentation by Steven Kaufman, Principal Consultant in MCS (Microsoft Consulting Services), comparing Microsoft Workflow Rule Engine and Microsoft BizTalk Business Rule Engine.

This slide summarizes the differences pretty well:


1 1 1 1 1

February 08, 2007

Macro decisions (million dollar decisions)

Macro decisions are strategic or tactical decisions. I like to call them million dollar decisions. Examples of macro decisions that can be automated using business rules:
  • What is the best product that we should recommend for this customer?
  • What is the best solution for this situation?
  • What is our underwiting strategy and policy?
  • What is our refund policy?
  • What is our pricing strategy for next year?
  • What is our discount policy this year?
  • What promotions should we run?
  • What should we do to improve improve yields and revenue?
  • Where should we locate the new store?
  • Where should we build the plant?
  • Where should we build the product?
  • Where should we hire the employees?

  • What Legal Entity structure should we use for this company?
  • What Legal Entity should we use for this contract?
  • Should we create a new legal entity for this deal?
  • What is the best way to structure this deal?

  • How do we design this plant so as to prevent and contain fires? How do we clean up this oil spill?
  • How do we minimize tax and maximize revenue for this contract?
  • How should we record these types of accounting transactions?
  • How do we calculate this quarter's tax provision?
  • How do we solve this customer's mission critical problem right now?
  • How do we troubleshoot this problem?
Thanks to James Taylor at the EDM blog for the idea for this list. If you have any others you'd like to add to the list, please add your comment below.

See also:

Micro decisions (a million little decisions)

Micro decisions are operational decisions. I like to call them a million little decisions. Examples of micro decisions that can be automated using business rules:
  • Is the customer eligible for the product?
  • Is the customer eligible for the promotion?
  • What discounts is the customer entitled to?
  • What should I up-sell right now?
  • What should I cross-sell right now?
  • What is the highest available commission (HAC)?
  • What is the lowest available fare (LAF)?
  • What credit card does the customer prefer to use?
  • Do I have all the information I need to save this record in the system?
  • How do I work-around the bug or limitation in the system?
  • Who should we assign as the company contact person for this sale?
Thanks to James Taylor at the EDM blog for the idea for this list. If you have any others you'd like to add to the list, please add your comment below. See also:

Locations of visitors to this page