|Sign-Up for Free Exclusive Services:||Portals|||||eNewsletters|||||Web Seminars|||||dataWarehouse.com|||||DM Review Magazine|
|Covering Business Intelligence, Integration & Analytics||Advanced Search|
Analytic Applications and Decision-Centric BI
Research in psychology and decision sciences has challenged the assumption that people apply rational principles in making decisions that work to optimize expected results. This descriptive, empirical research has catalogued many of the biases that enter into decision making. Managers often seek to mitigate uncertainty by any means before committing to a decision.
One of the most famous examples of this line of research is the study of "anchoring" conducted by Daniel Kahneman and Amos Tversky in the 1970s. Through many experiments, they were able to show that managers make judgments by making adjustments from some initial value, even if that initial value is based on totally random information. (Professor Kahneman was awarded the 2002 Nobel Prize for Economics for his pioneering research.)
Decision-making processes need to be improved, but which processes are the best candidates for improvement?
Strategic vs. Operational Decision Making
There are two types of decisions - operational and strategic. Strategic decisions have broad organizational scope but are infrequent, while operational decisions have more restricted scope but repeat frequently. IDC research shows that progress is being made by capturing and automating decision-making processes for repeatable, operational decisions.
Here are some examples of operational decisions:
By contrast, here are examples of strategic decisions:
Strategic decisions are important. However, because they are infrequent, there is little opportunity to apply lessons learned on an ongoing basis and to provide software-based automation to support such a process. That is not the case with operational decisions which are repeatable.
Here are examples of operational decision-making initiatives across a variety of industries:
Traditional vs. Decision-Centric Business Intelligence
IDC has stressed the importance of the policy hub as the critical link between analytics and action in a closed-loop system. It is the point in a business process where decisions are made and where the results of the decision are communicated to the people and the operational systems that are impacted.
Traditional business intelligence (BI) concentrates on information access by and delivery to individuals. The classic issues are:
Decision-centric business intelligence (DCBI) extends traditional BI in the following ways:
The Learning Gap Between Information Delivery and Decision Making
The disconnect between the delivery of information and the processes of decision making, as shown in Figure 1, comprises what IDC calls the "learning gap."
The learning gap operates in two respects, from the upper half of the process (information monitoring and delivery) to the lower half (decision making) and from decision making to information monitoring.
First, there is a disconnect from information monitoring and delivery to decision making. Traditional BI ends at the "deliver information" stage, paying insufficient attention to forming a problem statement, searching for candidate solutions ("Hypothesize") and evaluating the likely outcomes ("Model"). The danger is that a decision-maker without information relevant to the decision at hand is likely to rely exclusively on intuition - a notoriously unreliable practice. (See Hammond, Keeney and Raiffa, "The Hidden Traps in Decision Making," Harvard Business Review, September-October 1998.)
Second, there is a disconnect from decision making to information monitoring and delivery. If decisions are not captured, there is no opportunity to track information relevant to measuring whether or not the decisions were effective. For example, a demand planner in a high-tech company is responsible every month for forecasting demand for each of the next six months. The forecast is then provided as input for a scheduling system, yielding a schedule that is used by a contract manufacturer. When there are last minute adjustments after the schedule is committed, the contract manufacturer can assess penalties. There was no tracking and analysis of past forecasts for learning and improvement. Then, the high-tech company implemented an analytic application that captured each forecast and analyzed deviations from actuals over time. With this type of feedback, the planner was able to improve accuracy to a significant degree.
If decisions are captured, criteria can be established for prioritizing information in order to track the effectiveness of the decision. This has two advantages:
In other words, if you know what decisions are made and who made them, you can be far more precise in tracking relevant information and alerting those decision-makers in time to revisit a decision. Here is where decision-centric BI intersects with business activity monitoring (BAM).
For example, consider a BAM offering such as Celequest with a sophisticated rules capability to monitor real-time or streaming data for events that meet defined predefined criteria. When the condition is detected, the rules engine sends an alert to responsible people. There is great flexibility in the types of views and event conditions that can be defined as a rule.
Linking such a BAM product to DCBI (decision-centric BI) would mean driving the definitions of the monitoring rules from the meta data on the actual decisions that were made and the individuals responsible for them. As new decisions are made, event monitoring/alerting rules would be defined or revised.
A Look Ahead: Vertical-Specific, Event-Based, Decision-Centric Analytic Applications
The ability to capture, monitor and analyze decisions and their impact requires rich, higher order meta data constructs for defining a decision and related events. These constructs must then be mapped to the meta data for the underlying structured and unstructured data that document the decision. This meta data mapping should enable access methods for end users who can search or query by specifying the relevant events and decisions. This convergence of DCBI and BAM would close the learning gap in a truly automated way.
As organizations recognize the need not just to deliver information but also to address decision-making processes, analytic applications will become more decision-centric. We already see evidence of applications in specialized areas - notably financial services. Applications for anti-money laundering (Mantas) or fraud detection (Fair Isaac) are examples. Other vendors are providing industry templates. The most logical choice is to start with financial services, as have BlackPearl and Orenburg. Spotfire, on the other hand, is a decision-centric vendor that began with pharmaceutical R&D and oil exploration.
DCBI is more than a vision. With an initial foothold in financial services, decision-centric analytic applications are beginning to appear across industries and domains. These applications will incorporate predictive, collaborative and event-based capabilities to optimize, automate and track decision-making processes.
For more information on related topics visit the following related portals...
Henry Morris is the group vice president and general manager for for IDC's Integration, Development and Applications Strategies (IDeAS) solution research group. Dr. Morris started the Analytics and Data Warehousing research service at ICD and coined the term "analytic applications" in 1997. Currently, he is exploring the relationship between business intelligence and business process automation. Morris may be contacted at firstname.lastname@example.org.