« September 2007 | Main | November 2007 »
October 30, 2007
SAP, business rules and decision management
(Posted by guest blogger, James Taylor)
As anyone watching the business rules space will have noticed, SAP recently bought Yasu, one of the small rules vendors. Gartner wrote about this hereand made a couple of useful comments on the acquisition and it made me think I should blog some kind of response to answer the question "what does this mean for business rules and decision management in general?"
At one level this is clearly a threat to existing business rules management system vendors - whenever a big player like SAP starts including some feature in their broad product set, vendors of those features have to worry. Some SAP customers who might in the past have considered buying a BRMS to add some flexibility to their installation might now just use the embedded Yasu technology. Similarly the folks who were selling their BPM tools as a way to enhance SAP now have to worry a little more also, as the SAP platform will now offer embedded business rules. As the folks at Gartner said:
"This smart, if late, acquisition will challenge the status quo of the BRE and business process management technology markets"
However, I don't think this is the main consequence of the purchase. Overall I think it is positive for the rules market for a very simple reason. Today a very small percentage of the projects that should be done using business rules are done using business rules. This is the main challenge facing those of us who espouse a new way to developing systems - getting the non-believers to try a new approach. SAP adopting business rules makes the technology much more mainstream and helps to solidify its position as a serious technology. Just as the growing strength of the open source rules business shows a maturing market, so does this. Broader use and understanding of business rules technology can only help.
The issue here is the difference between taking a rules-based, declarative approach to "coding" (in a process or system) and actually managing decisions as a corporate asset. Just as BPM vendors provide some support for rules (and I agree with Gartner that this will force "BPM suite vendors to make additional BRE acquisitions as they satisfy their desires for direct ownership of this crucial technology"), this is not the same as supporting decision management. Decision Management means externalizing the high volume, operational decisions that drive your business processes and managing them as a separate asset. Just as BPM vendors correctly point out that managing your processes outside your ERP/CRM products can add value, so can managing your decisions. I could argue, and have, that managing decisions separate is even more important. While a process might be delivered using a single BPM environment, many decisions must be shared across processes, systems and channels. No matter how good the individual platforms you use are at managing rules, managing a cross-platform, cross-channel, cross-process decision requires you to step outside that platform. Most companies have long since realized that they cannot do everything on a single platform. If you have SAP and other software running your business, you need to manage decisions in a way that supports both. Indeed SAP's increasing positioning of NetWeaver as an integrated composition environment reinforces this. If the right place to manage something is outside of SAP then Netweaver will let you compose it into the solution you need. If you building decision services using a powerful BRMS like Fair Isaac's Blaze Advisor then Netweaver will let you integrate them into SAP but you will still be able to reuse those services and rules in other areas.
So, what should SAP do?
- Integrate Yasu into Netweaver to support declarative programming of relevant constructs.
This is a better way to "code" many things and this should be extended widely throughout NetWeaver. This will help grow the acceptance of business rules as a paradigm. - Make it easy to build real decision services on Netweaver (not quite the same as 1 above) and publish the APIs so that Fair Isaac, ILOG et al can develop compatible deployments.
This will allow easy integration with products built on other rules platforms as well as making for easy upgrades for companies that start off embedding rules in their SAP platform and want to move to true decision management over time. - Take the modules of SAP that are hardest to configure using SAP's traditional table-driven approach and embed the rules engine so that rules can be used to configure these instead
Put some skin in the game. If rules are better, and they are, then some of SAP's application teams will need to show they believe. - Encourage third parties to develop rules-based decision services for Netweaver
It's a great way to add functionality to SAP installations without a lot of database or user interface change, which minimizes both development costs and deployment disruption. Major analytic application vendors like Fair Isaac are already well on the way to offering decision services-based engines that would really enhance SAP installations. - Think about analytics in terms of decision services
SAP is total distracted on the analytic front with its acquisition of Business Objects. Once it gets done with that it should be talking to its data mining and analytics partners about how to bring analytically-enhanced decisioning to NetWeaver.
Some other posts you might find interesting include:
- Decision Services
- Get set for change time
- Decision Management at the Heart of Future Enterprise Applications
- Using decision management to complement ERP
- SOA, BPM (and EDM) for Enterprise Applications
Finally, these are my personal opinions not necessarily those of Fair Isaac Corporation.

Visit my Smart (Enough) Systems Blog(RSS) or my ebizQ blog (RSS). Buy the bookor visit the companion wiki.
Posted by James Taylor at 11:03 AM | Comments (0)
October 26, 2007
A report from the 10th Business Rules Forum
(Posted by guest blogger, James Taylor)
I have just got back from the 10th Annual Business Rules Forum. This is a show I attend regularly but this was the best ever for me. Not only were the logistics great with a nice expo, good rooms and FunLabs allowing attendees to spend 2 hours really using a vendor's product (much better than the usual walk-by demos), the content was great. For instance:
- More than 10 sessions about analytics, data mining and the convergence of business rules with data analysis techniques.
- 7 or so sessions explicitly bringing business rules and SOA together, for instance in discussing Decision Services.
- Another 7 sessions on how business rules and decision management make for more effective business process management.
- No less than 28 actual case studies showing how real companies from Everbank to Travelers Insurance, BlueCross BlueShield to Delta Dental, Precedent Insurance to Freddie Mac, Walt Disney to Dell.
Not only was this year's show a great opportunity to learn about enterprise decision management, the organizers made an existing announcement. Next year will see the First Annual Enterprise Decision Management Summit™, which will be co-located with the 11th Annual Business Rules Forum™. Not only is this exciting because it shows the growing acceptance of decision management, especially enterprise decision management, as an approach to solving the challenges facing organizations today, it is exciting as I will be chairing it with my co-author on Smart (Enough) Systems, Neil Raden. Look for lots of sessions on analytics, combining analytics with business rules, how decision management fits with SOA and BPM and much more.
The theme for the 2008 Conferences is going to be All Around Agility™ and I hope we will see many of you there.
Here's a quick summary of my posts from the conference
- A framework for selecting business rules platforms
- From Business Rules to Enterprise Decisioning
- Business Process Management with Business Rules and Business Intelligence
- Business Rules, Decision Management and Smarter Systems
- Insurance 2020: Innovating Beyond Old Models
- Turbocharging Business Rules Engines with BI 2.0
- Intelligent Process Automation: The Key to Business Process Automation
- Combining the Power of Analytics and Business Rules to Drive Enterprise Decisioning Solutions
- True Adventures in Business Rules
- Reaping the Benefits of Rules through SOA and Business Rule Management at Travelers
- Vendor Panel
- Agile Compliance
- Top 10 Data Dangers When Discovering Business Rules
- Getting It Right. Rules and Requirements in Software

Visit my Smart (Enough) Systems Blog (RSS) or my ebizQ blog (RSS). Buy the book or visit the companion wiki.
Posted by James Taylor at 4:24 PM | Comments (0)
October 22, 2007
At Business Rules Forum this week
(Posted by guest blogger, James Taylor)
This week I am attending the 10th annual Business Rules Forum and blogging about it over on my blog. Check out www.smartenoughsystems.com/wp for details. I will post a summary when I get back.
Don't forget to subscribe to my new blog in addition to this one (RSS)

Visit my Smart (Enough) Systems Blog (RSS) or my ebizQ blog (RSS). Buy the book or visit the companion wiki.
Posted by James Taylor at 7:59 PM | Comments (0)
October 18, 2007
Using business rules to prevent software spoiling
(Posted by guest blogger, James Taylor)
One of my favorite sites on software development - Coding Horror - had a great post today on how software spoils. Jeff's focus in his post was on how feature bloat can kill commercial software products. They go from tightly focused, easy to use products to bloatware that contains so many useless features (useless to any particular person, that is) that they are "spoiled"
When it comes to internal software - applications or services developed by an organization for its own use - one tends not to see this kind of bloating. However, even this kind of software "spoils". In particular the software no longer meets the needs of the business because the evolution of the software is out of synch with the evolution of the business. Typically this means that the business has changed and the software has not changed in ways that make sense given the new focus of the business. It can also mean that the software is simply not changing fast enough and so has fallen behind the business. You see this all the time as workers share tricks and tips to get around software problems, as note fields are used to contain data that can no longer be stored in structured fields as the rules about what's valid have changed. You see more and more manual exceptions generated and so on.
Externalizing business rules in decision services and empowering the business to manage the rules in such services can really help with this problem.
- Business rules, being declarative and atomic, are easier to change as each change has fewer ripple effects.
- Business rules, especially once templated, allow business users to much more actively change their rules for themselves, reducing the time from need to change.
- Externalizing change into a decision service can dramatically reduce the rate at which the rest of the application "spoils" as so many of the changes that cause spoiling are changes to business rules.
- If the application is originally developed so that the rules are under business control then developers may avoid introducing capabilities that will never be used. Business users might ask for something they don't really need but are unlikely to create rules they don't really need when they are doing the work themselves.
- The separation of concerns that results from having decisions (business rules or business logic) managed separately makes any kind of change easier. A process change only requires change to process definitions, a policy change only to rules in a decision service, a technology change only to the plumbing.
I am sure you can think of others.
One additional thought. Several commenters on the original post made the point that Firefox's add-ons and greasemonkey scripts help fight bloat and therefore spoiling by allowing features that only some people want to be added only by those people. I have not given a lot of thought to how this might work with business rules but I could imagine allowing, say, store or regional managers to include or exclude specific rulesets for transactions in their scope of control to achieve something similar. Because one particular manager has a need to make a decision more complex thanks to some local problem, would not have to mean that everyone had to do so. The structuring of decisions with rulesets and rules would allow different degrees of complexity, even different approaches, to be assembled and disassembled by business users as they needed them. This might allow more business users to feel that the system reflected their true needs rather than some bloated corporate uber-policy.
Additional posts on this topic that you might enjoy include:
Don't forget to subscribe to my new blog in addition to this one (RSS)

Visit my Smart (Enough) Systems Blog (RSS) or my ebizQ blog (RSS). Buy the book or visit the companion wiki.
Posted by James Taylor at 10:18 AM | Comments (0)
October 16, 2007
How can your decision services get new experiences?
(Posted by guest blogger, James Taylor)
I recently started reading an interesting new blog - the Decision Strategist - and saw a post titled New Experiences Improve Decision Making. It was an interesting (if short) post that made the critical point that "one of the best ways of improving our decision making was to vary our experiences". This is clearly true and the author goes on to give some good reasons for this (of which more in a minute). What to do, though, if you have automated the decision? Say you have built a decision service to automate and manage an operational decision. How can you ensure that this decision service continues to improve its decision making? How does a service get "new experiences"?
A decision service can get new experiences in two ways - automatically and manually. Ensuring that a decision service gets new experiences automatically means either developing adaptive analytics that respond to new data as it is collected or using adaptive control. Adaptive analytics are sometimes appropriate - when you get very quick feedback on how good a decision is and when variations are not driven by your own actions but by the market as a whole. Adaptive control, the establishment of multiple decision strategies that can be tracked and compared over time, can always be used, however. By running some transactions through alternatives and by tracking the result you can establish a decision service that, more or less, learns from a greater variety of "experiences".
Manually driving the results of broader experience into a decision service is a business intelligence/performance management issue in large part. If the business users who control the rules in your decision service have good reporting and performance management tools, then they can use these to investigate their business. Widening the range of information being considered allows them to make changes to their rules that reflect a wider experience. Of course, they have to want to do this. Even good tools can still be used to merely reinforce existing prejudices.
The post identifies four specific ways in which this helps and three seem to be relevant here:
- Correcting the confirmation bias. Not only do wider experiences help with this, the use of predictive analytic models to replace human judgment can often do this very effectively (such as in the use of credit scoring to replace loan officers value judgments).
- Expanding automatic associations. As the post notes "a subconscious preference ... can lead to suboptimal decision making" and gathering, and analyzing data more widely can help correct this. Using descriptive analytics to understand the true associations can be particularly effective.
- Enlarging our idea of normal. We might think that our normal approach will work better but adaptive control can show us that an alternative will work better.
Just because you are automating a decision, don't forget to give your decision services new experiences when you can.

Visit my Smart (Enough) Systems Blog (RSS) or my ebizQ blog (RSS). Buy the book or visit the companion wiki.
Posted by James Taylor at 4:46 PM | Comments (0)
October 15, 2007
Feed and URL updates
(Post by Guest Author, James Taylor)
This week marks something of a transition for me and for the blog. I am going to become a guest author here on the Fair Isaac EDM blog - look for me to blog about twice a week. The URL for the Fair Isaac blog remains www.edmblog.com and the feed is still at feeds.feedburner.com/EnterpriseDecisionManagementWeblog. The folks at Fair Isaac will be taking over the management of the blog and I suspect you will see some other authors appear over time. I am particularly hopeful that they will start to share more customer stories.
My personal blog (still focused on the opportunities and challenges of decision management) will now be over at www.smartenoughsystems.com/wp (part of the companion site for Smart (Enough) Systems). If you want to continue reading all my posts, and I hope you do, please subscribe to the feed at feeds.feedburner.com/SmartEnoughSystems. Those of you subscribed by email will get an invitation directly through the email subscription manager we use. The book's companion site also has a wiki under construction in which I hope you will participate. I just posted on How decision management fits with key 2008 technologies
It's been a real blast blogging here on edmblog.com - over 750 posts in two years or so - and I hope you will continue to subscribe to this blog and join me on my new one.
James
P.S. Don't forget that I also post to ebizQ at www.ebizq.net/blogs/decision_management so if you really want to have a complete picture of my posts, you should subscribe to that feed too (feeds.feedburner.com/JamesTaylorsDecisionManagement).
Posted by James Taylor at 9:12 AM | Comments (0)
October 8, 2007
While Forrester Envisions Consolidation for the 3 "Bs", it's Happening for Apps and BI Vendors
(Posted by guest Blogger, Gib Bassett)
Cognos and Microstrategy are the two remaining independent Business Intelligence (BI) software giants following today’s news that SAP was purchasing Business Objects. Speculation was building online last week that a deal was in the works and in fact for much of this year since Oracle purchased Hyperion, such rumors have been the case.
As I mention in my prior blog about Forrester's prediction of convergence among BI, Business Process Management and Business Rules vendors, firms like Business Objects and SAP used to market against one another, the former espousing the benefits of an enterprise view of data, reporting and analysis, and the other the same, but with deeper functionality and built for the applications producing the data. A few years and many joint customers later, it’s easy to see why this consolidation is taking place, and it should only become more common as the remaining vendors continue to evolve their product sets around Services Oriented Architectures (SOA) and web services.
It would not be a great leap to say Cognos is next on the block and will probably get snapped up by Oracle. Although Oracle bought analytics vendor Hyperion earlier this year, that company was more known for its OLAP database and finance applications than broadly applicable BI reporting and analysis tools which is really the core of Cognos’ business. Such a scenario would leave Microstrategy as the sole large independent choice for customers not interested in sourcing everything from a single vendor. If the promise of SOA holds, however, the single vendor benefit promised by mergers may not be as valuable as it seems.
All this is consistent with what we’ve written about on the blog regarding Enterprise Decision Management (EDM), and its basis in SOA concepts rendered as Decision Services potentially blending rules and analytics. Remaining a component of a larger multi-source solution has numerous benefits to customers considering EDM solutions, primarily that providers can focus on developing their best of breed capabilities without dilution from a larger host business focused on a broader market. It will be interesting to watch and see how the 3 “Bs” converge as Forrester predicts, and how other trends such as Operational Analytics will be affected by changes to the marketplace.
Posted by James Taylor at 10:46 AM | Comments (0)
While Forrester Envisions Consolidation for the 3 "Bs", it's Happening for Apps and BI Vendors
(Posted by guest Blogger, Gib Bassett)
Cognos and Microstrategy are the two remaining independent Business Intelligence (BI) software giants following today’s news that SAP was purchasing Business Objects. Speculation was building online last week that a deal was in the works and in fact for much of this year since Oracle purchased Hyperion, such rumors have been the case.
As I mention in my prior blog about Forrester's prediction of convergence among BI, Business Process Management and Business Rules vendors, firms like Business Objects and SAP used to market against one another, the former espousing the benefits of an enterprise view of data, reporting and analysis, and the other the same, but with deeper functionality and built for the applications producing the data. A few years and many joint customers later, it’s easy to see why this consolidation is taking place, and it should only become more common as the remaining vendors continue to evolve their product sets around Services Oriented Architectures (SOA) and web services.
It would not be a great leap to say Cognos is next on the block and will probably get snapped up by Oracle. Although Oracle bought analytics vendor Hyperion earlier this year, that company was more known for its OLAP database and finance applications than broadly applicable BI reporting and analysis tools which is really the core of Cognos’ business. Such a scenario would leave Microstrategy as the sole large independent choice for customers not interested in sourcing everything from a single vendor. If the promise of SOA holds, however, the single vendor benefit promised by mergers may not be as valuable as it seems.
All this is consistent with what we’ve written about on the blog regarding Enterprise Decision Management (EDM), and its basis in SOA concepts rendered as Decision Services potentially blending rules and analytics. Remaining a component of a larger multi-source solution has numerous benefits to customers considering EDM solutions, primarily that providers can focus on developing their best of breed capabilities without dilution from a larger host business focused on a broader market. It will be interesting to watch and see how the 3 “Bs” converge as Forrester predicts, and how other trends such as Operational Analytics will be affected by changes to the marketplace.
Posted by James Taylor at 10:46 AM | Comments (0)
While Forrester Envisions Consolidation for the 3 "Bs", it's Happening for Apps and BI Vendors
(Posted by guest Blogger, Gib Bassett)
Cognos and Microstrategy are the two remaining independent Business Intelligence (BI) software giants following today’s news that SAP was purchasing Business Objects. Speculation was building online last week that a deal was in the works and in fact for much of this year since Oracle purchased Hyperion, such rumors have been the case.
As I mention in my prior blog about Forrester's prediction of convergence among BI, Business Process Management and Business Rules vendors, firms like Business Objects and SAP used to market against one another, the former espousing the benefits of an enterprise view of data, reporting and analysis, and the other the same, but with deeper functionality and built for the applications producing the data. A few years and many joint customers later, it’s easy to see why this consolidation is taking place, and it should only become more common as the remaining vendors continue to evolve their product sets around Services Oriented Architectures (SOA) and web services.
It would not be a great leap to say Cognos is next on the block and will probably get snapped up by Oracle. Although Oracle bought analytics vendor Hyperion earlier this year, that company was more known for its OLAP database and finance applications than broadly applicable BI reporting and analysis tools which is really the core of Cognos’ business. Such a scenario would leave Microstrategy as the sole large independent choice for customers not interested in sourcing everything from a single vendor. If the promise of SOA holds, however, the single vendor benefit promised by mergers may not be as valuable as it seems.
All this is consistent with what we’ve written about on the blog regarding Enterprise Decision Management (EDM), and its basis in SOA concepts rendered as Decision Services potentially blending rules and analytics. Remaining a component of a larger multi-source solution has numerous benefits to customers considering EDM solutions, primarily that providers can focus on developing their best of breed capabilities without dilution from a larger host business focused on a broader market. It will be interesting to watch and see how the 3 “Bs” converge as Forrester predicts, and how other trends such as Operational Analytics will be affected by changes to the marketplace.
Posted by James Taylor at 10:46 AM | Comments (0)
While Forrester Envisions Consolidation for the 3 "Bs", it's Happening for Apps and BI Vendors
(Posted by guest Blogger, Gib Bassett)
Cognos and Microstrategy are the two remaining independent Business Intelligence (BI) software giants following today’s news that SAP was purchasing Business Objects. Speculation was building online last week that a deal was in the works and in fact for much of this year since Oracle purchased Hyperion, such rumors have been the case.
As I mention in my prior blog about Forrester's prediction of convergence among BI, Business Process Management and Business Rules vendors, firms like Business Objects and SAP used to market against one another, the former espousing the benefits of an enterprise view of data, reporting and analysis, and the other the same, but with deeper functionality and built for the applications producing the data. A few years and many joint customers later, it’s easy to see why this consolidation is taking place, and it should only become more common as the remaining vendors continue to evolve their product sets around Services Oriented Architectures (SOA) and web services.
It would not be a great leap to say Cognos is next on the block and will probably get snapped up by Oracle. Although Oracle bought analytics vendor Hyperion earlier this year, that company was more known for its OLAP database and finance applications than broadly applicable BI reporting and analysis tools which is really the core of Cognos’ business. Such a scenario would leave Microstrategy as the sole large independent choice for customers not interested in sourcing everything from a single vendor. If the promise of SOA holds, however, the single vendor benefit promised by mergers may not be as valuable as it seems.
All this is consistent with what we’ve written about on the blog regarding Enterprise Decision Management (EDM), and its basis in SOA concepts rendered as Decision Services potentially blending rules and analytics. Remaining a component of a larger multi-source solution has numerous benefits to customers considering EDM solutions, primarily that providers can focus on developing their best of breed capabilities without dilution from a larger host business focused on a broader market. It will be interesting to watch and see how the 3 “Bs” converge as Forrester predicts, and how other trends such as Operational Analytics will be affected by changes to the marketplace.
Posted by James Taylor at 10:46 AM | Comments (0)
While Forrester Envisions Consolidation for the 3 "Bs", it's Happening for Apps and BI Vendors
(Posted by guest Blogger, Gib Bassett)
Cognos and Microstrategy are the two remaining independent Business Intelligence (BI) software giants following today’s news that SAP was purchasing Business Objects. Speculation was building online last week that a deal was in the works and in fact for much of this year since Oracle purchased Hyperion, such rumors have been the case.
As I mention in my prior blog about Forrester's prediction of convergence among BI, Business Process Management and Business Rules vendors, firms like Business Objects and SAP used to market against one another, the former espousing the benefits of an enterprise view of data, reporting and analysis, and the other the same, but with deeper functionality and built for the applications producing the data. A few years and many joint customers later, it’s easy to see why this consolidation is taking place, and it should only become more common as the remaining vendors continue to evolve their product sets around Services Oriented Architectures (SOA) and web services.
It would not be a great leap to say Cognos is next on the block and will probably get snapped up by Oracle. Although Oracle bought analytics vendor Hyperion earlier this year, that company was more known for its OLAP database and finance applications than broadly applicable BI reporting and analysis tools which is really the core of Cognos’ business. Such a scenario would leave Microstrategy as the sole large independent choice for customers not interested in sourcing everything from a single vendor. If the promise of SOA holds, however, the single vendor benefit promised by mergers may not be as valuable as it seems.
All this is consistent with what we’ve written about on the blog regarding Enterprise Decision Management (EDM), and its basis in SOA concepts rendered as Decision Services potentially blending rules and analytics. Remaining a component of a larger multi-source solution has numerous benefits to customers considering EDM solutions, primarily that providers can focus on developing their best of breed capabilities without dilution from a larger host business focused on a broader market. It will be interesting to watch and see how the 3 “Bs” converge as Forrester predicts, and how other trends such as Operational Analytics will be affected by changes to the marketplace.
Posted by James Taylor at 10:46 AM | Comments (0)
While Forrester Envisions Consolidation for the 3 "Bs", it's Happening for Apps and BI Vendors
(Posted by guest Blogger, Gib Bassett)
Cognos and Microstrategy are the two remaining independent Business Intelligence (BI) software giants following today’s news that SAP was purchasing Business Objects. Speculation was building online last week that a deal was in the works and in fact for much of this year since Oracle purchased Hyperion, such rumors have been the case.
As I mention in my prior blog about Forrester's prediction of convergence among BI, Business Process Management and Business Rules vendors, firms like Business Objects and SAP used to market against one another, the former espousing the benefits of an enterprise view of data, reporting and analysis, and the other the same, but with deeper functionality and built for the applications producing the data. A few years and many joint customers later, it’s easy to see why this consolidation is taking place, and it should only become more common as the remaining vendors continue to evolve their product sets around Services Oriented Architectures (SOA) and web services.
It would not be a great leap to say Cognos is next on the block and will probably get snapped up by Oracle. Although Oracle bought analytics vendor Hyperion earlier this year, that company was more known for its OLAP database and finance applications than broadly applicable BI reporting and analysis tools which is really the core of Cognos’ business. Such a scenario would leave Microstrategy as the sole large independent choice for customers not interested in sourcing everything from a single vendor. If the promise of SOA holds, however, the single vendor benefit promised by mergers may not be as valuable as it seems.
All this is consistent with what we’ve written about on the blog regarding Enterprise Decision Management (EDM), and its basis in SOA concepts rendered as Decision Services potentially blending rules and analytics. Remaining a component of a larger multi-source solution has numerous benefits to customers considering EDM solutions, primarily that providers can focus on developing their best of breed capabilities without dilution from a larger host business focused on a broader market. It will be interesting to watch and see how the 3 “Bs” converge as Forrester predicts, and how other trends such as Operational Analytics will be affected by changes to the marketplace.
Posted by James Taylor at 10:46 AM | Comments (0)
While Forrester Envisions Consolidation for the 3 "Bs", it's Happening for Apps and BI Vendors
(Posted by guest Blogger, Gib Bassett)
Cognos and Microstrategy are the two remaining independent Business Intelligence (BI) software giants following today’s news that SAP was purchasing Business Objects. Speculation was building online last week that a deal was in the works and in fact for much of this year since Oracle purchased Hyperion, such rumors have been the case.
As I mention in my prior blog about Forrester's prediction of convergence among BI, Business Process Management and Business Rules vendors, firms like Business Objects and SAP used to market against one another, the former espousing the benefits of an enterprise view of data, reporting and analysis, and the other the same, but with deeper functionality and built for the applications producing the data. A few years and many joint customers later, it’s easy to see why this consolidation is taking place, and it should only become more common as the remaining vendors continue to evolve their product sets around Services Oriented Architectures (SOA) and web services.
It would not be a great leap to say Cognos is next on the block and will probably get snapped up by Oracle. Although Oracle bought analytics vendor Hyperion earlier this year, that company was more known for its OLAP database and finance applications than broadly applicable BI reporting and analysis tools which is really the core of Cognos’ business. Such a scenario would leave Microstrategy as the sole large independent choice for customers not interested in sourcing everything from a single vendor. If the promise of SOA holds, however, the single vendor benefit promised by mergers may not be as valuable as it seems.
All this is consistent with what we’ve written about on the blog regarding Enterprise Decision Management (EDM), and its basis in SOA concepts rendered as Decision Services potentially blending rules and analytics. Remaining a component of a larger multi-source solution has numerous benefits to customers considering EDM solutions, primarily that providers can focus on developing their best of breed capabilities without dilution from a larger host business focused on a broader market. It will be interesting to watch and see how the 3 “Bs” converge as Forrester predicts, and how other trends such as Operational Analytics will be affected by changes to the marketplace.
Posted by James Taylor at 10:46 AM | Comments (0)
While Forrester Envisions Consolidation for the 3 "Bs", it's Happening for Apps and BI Vendors
(Posted by guest Blogger, Gib Bassett)
Cognos and Microstrategy are the two remaining independent Business Intelligence (BI) software giants following today’s news that SAP was purchasing Business Objects. Speculation was building online last week that a deal was in the works and in fact for much of this year since Oracle purchased Hyperion, such rumors have been the case.
As I mention in my prior blog about Forrester's prediction of convergence among BI, Business Process Management and Business Rules vendors, firms like Business Objects and SAP used to market against one another, the former espousing the benefits of an enterprise view of data, reporting and analysis, and the other the same, but with deeper functionality and built for the applications producing the data. A few years and many joint customers later, it’s easy to see why this consolidation is taking place, and it should only become more common as the remaining vendors continue to evolve their product sets around Services Oriented Architectures (SOA) and web services.
It would not be a great leap to say Cognos is next on the block and will probably get snapped up by Oracle. Although Oracle bought analytics vendor Hyperion earlier this year, that company was more known for its OLAP database and finance applications than broadly applicable BI reporting and analysis tools which is really the core of Cognos’ business. Such a scenario would leave Microstrategy as the sole large independent choice for customers not interested in sourcing everything from a single vendor. If the promise of SOA holds, however, the single vendor benefit promised by mergers may not be as valuable as it seems.
All this is consistent with what we’ve written about on the blog regarding Enterprise Decision Management (EDM), and its basis in SOA concepts rendered as Decision Services potentially blending rules and analytics. Remaining a component of a larger multi-source solution has numerous benefits to customers considering EDM solutions, primarily that providers can focus on developing their best of breed capabilities without dilution from a larger host business focused on a broader market. It will be interesting to watch and see how the 3 “Bs” converge as Forrester predicts, and how other trends such as Operational Analytics will be affected by changes to the marketplace.
Posted by James Taylor at 10:46 AM | Comments (0)
While Forrester Envisions Consolidation for the 3 "Bs", it's Happening for Apps and BI Vendors
(Posted by guest Blogger, Gib Bassett)
Cognos and Microstrategy are the two remaining independent Business Intelligence (BI) software giants following today’s news that SAP was purchasing Business Objects. Speculation was building online last week that a deal was in the works and in fact for much of this year since Oracle purchased Hyperion, such rumors have been the case.
As I mention in my prior blog about Forrester's prediction of convergence among BI, Business Process Management and Business Rules vendors, firms like Business Objects and SAP used to market against one another, the former espousing the benefits of an enterprise view of data, reporting and analysis, and the other the same, but with deeper functionality and built for the applications producing the data. A few years and many joint customers later, it’s easy to see why this consolidation is taking place, and it should only become more common as the remaining vendors continue to evolve their product sets around Services Oriented Architectures (SOA) and web services.
It would not be a great leap to say Cognos is next on the block and will probably get snapped up by Oracle. Although Oracle bought analytics vendor Hyperion earlier this year, that company was more known for its OLAP database and finance applications than broadly applicable BI reporting and analysis tools which is really the core of Cognos’ business. Such a scenario would leave Microstrategy as the sole large independent choice for customers not interested in sourcing everything from a single vendor. If the promise of SOA holds, however, the single vendor benefit promised by mergers may not be as valuable as it seems.
All this is consistent with what we’ve written about on the blog regarding Enterprise Decision Management (EDM), and its basis in SOA concepts rendered as Decision Services potentially blending rules and analytics. Remaining a component of a larger multi-source solution has numerous benefits to customers considering EDM solutions, primarily that providers can focus on developing their best of breed capabilities without dilution from a larger host business focused on a broader market. It will be interesting to watch and see how the 3 “Bs” converge as Forrester predicts, and how other trends such as Operational Analytics will be affected by changes to the marketplace.
Posted by James Taylor at 10:46 AM | Comments (0)
While Forrester Envisions Consolidation for the 3 "Bs", it's Happening for Apps and BI Vendors
(Posted by guest Blogger, Gib Bassett)
Cognos and Microstrategy are the two remaining independent Business Intelligence (BI) software giants following today’s news that SAP was purchasing Business Objects. Speculation was building online last week that a deal was in the works and in fact for much of this year since Oracle purchased Hyperion, such rumors have been the case.
As I mention in my prior blog about Forrester's prediction of convergence among BI, Business Process Management and Business Rules vendors, firms like Business Objects and SAP used to market against one another, the former espousing the benefits of an enterprise view of data, reporting and analysis, and the other the same, but with deeper functionality and built for the applications producing the data. A few years and many joint customers later, it’s easy to see why this consolidation is taking place, and it should only become more common as the remaining vendors continue to evolve their product sets around Services Oriented Architectures (SOA) and web services.
It would not be a great leap to say Cognos is next on the block and will probably get snapped up by Oracle. Although Oracle bought analytics vendor Hyperion earlier this year, that company was more known for its OLAP database and finance applications than broadly applicable BI reporting and analysis tools which is really the core of Cognos’ business. Such a scenario would leave Microstrategy as the sole large independent choice for customers not interested in sourcing everything from a single vendor. If the promise of SOA holds, however, the single vendor benefit promised by mergers may not be as valuable as it seems.
All this is consistent with what we’ve written about on the blog regarding Enterprise Decision Management (EDM), and its basis in SOA concepts rendered as Decision Services potentially blending rules and analytics. Remaining a component of a larger multi-source solution has numerous benefits to customers considering EDM solutions, primarily that providers can focus on developing their best of breed capabilities without dilution from a larger host business focused on a broader market. It will be interesting to watch and see how the 3 “Bs” converge as Forrester predicts, and how other trends such as Operational An








