|
| Recent
Articles |
Enterprise Software And Blogging
Bill Gates seems to bemoan the fact that enterprise software isn't covered by blogs and journalists. Instead, he points out, that we like talking about consumer software. It's a good point, especially since...
Intranets Are In Trouble
Intranets are in trouble. These internal versions of the World Wide Web have held huge promise. After all, if people can simplify their lives using the Web, why shouldn't the same technology simplify work?
Halloween IT Horror Stories: Blogging
As Halloween rapidly approaches, it is time for the IT Halloween Horror Stories.
We all have stories that have freaked, amazed, made us wonder, and otherwise, stunned us into submission or disbelief as we...
How Choice Drives Change
I've always believed that choice drives change. Or more specifically, that choices provided by free markets drive change in institutions towards more democratic systems. Perhaps it is because of the system I grew up in...
Avoid Massive Training Costs In Your Call Center
I saw a piece on Computerwire by Janine Milne recently - "Poor IT Training Costs UK Contact Centers Billions" (subscription required). Janine made the point that with 25% churn and complex IT systems, training...
|
|
|
01.11.07
Using Business Rules & Analytics Together
 By James Taylor
Using business rules and analytics together is one of the defining characteristics of an enterprise decision management approach.
Dan Selman had an interesting post over on the ILOG blog today - Integrating Business Objects and JRules using SOA. The post discusses a well-written "lab" white paper that walks through the process of this integration in detail with screenshots, practical guidance etc.
While, at one level, the integration described is pretty straightforward and more to do with the integration of services built using different tools (this integration being, of course, one of the primary benefits of using an SOA), it also shows some interesting characteristics of using an EDM approach.
• There is a nice separation of concerns with the rules engine executing rules and the analytic platform executing queries, doing sums etc
• The rules engine uses the same view of the data that the analytic platform presents to users, ensuring that the automated decision making environment and the manual decision making environment are synchronized
• The rules engine can use the analytic platform without having to worry about how potentially complex analytics are performed
• Rules that use the data managed by the analytic platform to take action are easy to change rather than embedded in the analytics platform
Now, there are a few things I would like to see in addition:
• Integration of the rules development environment with the query platform so that, for instance, a rule developer can see how real instances are distributed before setting a threshold in a rule.
• Integration of rules testing with the query platform to make it easy to use existing data to test rules.
• Support for data mining for rules - using data mining algorithms to develop the rules and then loading them directly into the rules environment.
• Integration of the performance management/dashboard environment with the rules maintenance environment so that a business manager can see that a change is required, using the dashboard, and then actually make the change, using the rule maintenance environment.
A business rules management system is a the critical platform for automating decisions using EDM. Integration with analytic platforms follows it a close second.
Comments
About
the Author:
VP of Product Marketing with a passion for the technologies of decision automation. 15 years designing, developing, releasing and marketing advanced enterprise software platforms and development tools. Across the board experience in software development, engineering and product management and product marketing.
http://www.edmblog.com
|
|
