All of this requires some analytical knowhow, and the Spendmatters blog promises a primer on the DelMonte approach. It's worth following because it ain't easy, it ain't simple, but it's how you get to spend control.
All of this requires some analytical knowhow, and the Spendmatters blog promises a primer on the DelMonte approach. It's worth following because it ain't easy, it ain't simple, but it's how you get to spend control.

Current @RISK 5.0 users will benefit from faster simulations — 2x to a remarkable 20x times faster than before — as well as new scatter plots from scenario analyses, a freehand distribution artist, and an Excel-style Insert Function dialog and graphs. @RISK 5.5 brings a range of new features to improve your analysis, save time, and encourage systematic adoption of risk analysis across your organization.
@RISK 5.5 is the best Monte Carlo simulation package available today, blending high-powered analysis with highly intuitive ease-of-use. The bottom line for you is a better understanding of what could happen and how likely it is to happen. Applications include value-at-risk, design and analysis of experiments, discounted cash flow analysis, exploration and production, option valuation, and more.
@RISK 5.5 has been fully translated into Spanish, German, French, Portuguese and Japanese.
» What's New in @RISK 5.5
» Download a free trial version
Question for today: What do you get when you run Monte Carlo software back in time? What's good about his recipe is that it walks you through the assumption stages of model building quite carefully. What's fun about his recipe is that his hypothetical example, which uses a straw man named Bob, is retrospective, and he constructs a model that begins in 2007 and runs forward from there. This means Considine has an opportunity to second-guess the assumptions--such as asset value, value-at-risk, and probabilities of worst-case scenarios--that brought down the house in 2008.
A high kurtosis figure is sometimes described as being associated with a distribution that has “fat tails”. However, by simply overlaying two Normal distributions with the same mean but different standard deviations (e.g. using @RISK to do so), it is visually clear that the distribution with the larger standard deviation has the “fatter tails”. However, every Normal distribution has a kurtosis of 3 (sometimes “excess kurtosis” is referred to, whereby any base calculation has three subtracted from it; this is the case when using the Excel KURT function to calculate kurtosis, for example), so the kurtosis figure does not pick up the idea that one of the distributions has more weight in the tail.
In fact, kurtosis is a simultaneous measure of the “peakedness” of a distribution and the extent to which it has “fat tails”; the Normal distribution with the larger standard deviation will have fatter tails, but will also be less peaked, and in terms of how kurtosis is calculated, these effects balance out. Kurtosis is then a bit like going for a workout, where you are required to push weights in a central direction whilst keeping your elbows up!
Another important aspect of kurtosis that is little appreciated is that the kurtosis of a binomial distribution (e.g. modelling an event risk that may or may not happen with a certain probability) increases as the probability of the event decreases. In this sense, distributions with high kurtosis figures are perhaps most easily understood as ones relating to events of low probability but high impact.
Such topics are very easy to explore with @RISK (risk analysis Monte Carlo software add-in to Excel), where the visual ability to view overlays, combined with the use of the RiskTheo functions to obtain in Excel the numerical values of statistics associated with distributions allows for a powerful environment to rapidly address such issues.
Yesterday I had an interesting conversation with a colleague who is a Six Sigma and DFSS Master Black belt who just returned from Europe where he conducted a Black Belt Training session. He pointed out how much different the Europeans are to the Americans when it comes to their expectations and commitment they show for new initiatives, particularly quality. He said when the European’s decide to introduce a program like Design for Six Sigma, they stick to it, even through the early failures and trials and tribulations. This is in contrast to many American manufacturers, who rattle through process improvement programs and philosophies like subscribing to the book of the month. (I have witnessed this firsthand, unfortunately.)
The moral of the story is do your research and make intelligent decisions on what tools you need to employ to make the necessary improvements to your company, for both its products and processes. Train your employees, implement and stick to it through good and bad. Give it the time and effort to be effective before abandoning it for another program.
Look at these programs as hiring employees - we all know hiring employees is a time consuming and costly endeavor, so by nature we don’t want to rehiring for the same position every month or year.
I believe Milevsky makes a great point, focusing on the modeling practices rather than the tools themselves in this case. Monte Carlo simulation tools are very important for applications like retirement planning, but even the best hammer can’t help an unskilled carpenter. Tools like @RISK include sensitivity and scenario analysis, enabling easy implementation of tests under different scenarios for portfolio value, inflation, longevity, or any combination of these.
Randy Heffernan
Vice President
In my view, named ranges are indispensible in some types of modelling situations. The most frequent of these in my experience are:
- When writing VBA code (macros) that refer to ranges in the workbook (as such code almost always would do at some point), the use if names provides a much more robust way of creating flexible code, rather than referring to the range using cell references.
- For general Excel modelling, it can be useful to name a small set of key ranges, so that the F5 key or the name box can be used to rapidly navigate around the model.
- Where the model process is not required as a process to experiment with or modify a model, but is purely required to implement a known situation which will never be changed. However, much Excel modelling involves the process of experimenting with different approaches, and the use of named ranges in such cases can create extra complexity.
Some disadvantages of using named ranges include: that their use too early on in the risk analysis modelling process can create cumbersome structures, that it can be easy to create models with far too many names that then become poorly labelled, and the possibility to inadvertently create links between models. The management of names (such as their deletion and their scope) has traditionally been cumbersome in Excel. It is important to note that Excel’s 2007 Name Manager has radically reduced some of these disadvantages (this change being one of the most important improvements made to Excel when moving from Excel 2003 to 2007, in my opinion).
This set of points is by no means complete; a deeper discussion of modelling in Excel, including robust and readily understandable risk analysis models or option valuation and price forecasting, is contained within my book Financial Modelling in Practice.
Dr. Michael Rees
Director of Training and Consulting
These arguments demonstrate a fundamental lack of understanding of what Monte Carlo simulation is. The underlying assumption that Monte Carlo simulation itself is somehow to blame fails to recognize that Monte Carlo simulation is simply a mathematical technique that takes into account many different possible scenarios – but only within boundaries set by the user. You can’t change the underlying math behind these “what-if” calculations.
When modelers set up retirement planning or financial models, the people doing the modeling must make assumptions about the likelihood of different things happening – like the market crashing, for example. People may make those assumptions based on historical evidence or expert opinion, but it’s people who make those assumptions – not Monte Carlo simulation software. People then enter their assumptions into a Monte Carlo simulation model, setting up probability distributions to reflect their chosen likelihoods of occurrence. If the assumed volatility is insufficient, that is the fault of the modelers, not the simulation itself.
In addition, Monte Carlo simulation does not always “use” a bell-shaped curve. Uncertainty can be modeled with dozens of different probability distributions, many of them not bell-shaped. And the call to include more scenarios and volatility can easily be met by existing Monte Carlo software such as @RISK. It’s simply up the user to change the model parameters to look at more possible outcomes. The Monte Carlo simulation package won’t fight it.
It’s disappointing to see esteemed financial organizations such as Morningstar and the Retirement Income Association missing the point. Calling for changes to Monte Carlo simulation itself is not only impossible but fails to recognize the problems with modeling practices that led everyone to miss the crash.
Randy Heffernan
Vice President
Here, I briefly mention some sources of skewness that arise in real-life processes, or in the associated modelling of risk:
- Multiplicative processes. A process in which random variables are multiplied will create a skewed output, tending to a Lognormal distribution when many such independent variables are multiplies, and often approximated by such a distribution in any case. Such process arise in cost budgeting (e.g. the total cost estimate as the product of an uncertain volume, unit cost, and perhaps a duration), in asset price forecasting (% changes to asset values over several periods work in a multiplicative sense), and in oil reservoir modelling (uncertain reserve estimation volume estimate being the product of uncertain spatial dimensions and some additional other factors, i.e. for exploration and production).
- Compound processes with event risks. When taking a pragmatic modelling approach in cost budgeting (e.g. using a Triangular distribution), one often simply assumes that the cost distribution of an item is asymmetric; that is we assume that (for unspecified reasons) the costs are more likely to be over the base estimate than below it. Often part of the underlying reason is the presence of event risks in the situation, where the occurrence of a specific event creates an additional (perhaps uncertain) set of costs in addition to a (perhaps uncertain and symmetric) base cost.
- Parameter estimation for small sample sizes. When estimating a probability from a set of observations (for example 5 occurrences of an event during 100 periods, or trials), one sometimes takes the “maximum likelihood” approach (i.e. assume 5%) or otherwise assumes that there is a distribution of possible probabilities (such as a Beta distribution). Either way, for small sample sizes, the distribution of the uncertainty of the true probability is not symmetric. Examples of this were given in the earlier blog about the difficulties in estimating the probability of low probability events.
Dr. Michael Rees
Director of Training and Consulting
The U.S. Federal Reserve recently released the results of a comprehensive assessment of the financial conditions of the nation's 19 largest banks, which hold two-thirds of American economic assets. This “stress test” was designed to determine the capital buffers required for the banks to withstand losses and maintain lending even in worsening economic conditions. Officially called the Supervisory Capital Assessment Program (SCAP), the test identified the potential losses, resources available to absorb losses, and resulting capital buffer needed. Monte Carlo simulation was used to determine the potential losses from further defaults on loans. According to Federal Reserve Chairman Ben Bernanke, “The assessment program was a forward-looking, ‘what-if’ exercise.”
Monte Carlo simulation is one of the most widely used methods of stress testing for capital and operations risk, according to Investopedia. It takes into account variables such as interest rates, lending requirements, and unemployment. As any @RISK software user will tell you, this type of sophisticated simulation can be accomplished easily within the Microsoft Excel environment. The result of a Monte Carlo software simulation is a look at a whole range of possible outcomes, including the probabilities they will occur -- a valuable tool when stress testing.
Randy Heffernan
Vice President
Since I was keen to try to replicate the results of the study for myself, I downloaded the eating survey data from the OECD web-site, but then for some reason was unable to find the same economic growth figures used in the article, and so searched for similar data myself, with the result that the time period covered in measuring economic growth was different to that used in the article… the key point being that I ended up in my analysis with a positive (+16%) correlation coefficient between eating time and economic growth, rather than a negative one (…maybe a bit of relaxation does help creativity?...back to the land of dreams…).
In fact, the reality is that correlation coefficients measured between data samples are not particularly stable until the data sets become very large. The @RISK (risk analysis using Monte Carlo simulation in Excel) tool can be used to explore this issue. For example, two data sets of a given size (e.g. 22 points) containing independent distributions can be set up, and for each random sampling of the points (each iteration of a simulation), the correlation coefficient between the sample points drawn from independent distributions calculated, with this correlation coefficient being set as the output call for the simulation. Having done this, a few observations and notes can be made from such reflections and calculations:
- Data sets containing only two points each will have a correlation coefficient which is either 100% or minus 100% (except in the rare case where two data points have exactly the same value), as the points are ordered either both low-high, or one is low-high and the other high-low. This already provides some intuition as to the lack of stability of the coefficient.
- The correlation coefficient as measured from two independent samples of 22 data points has a standard deviation of around 20% (and a mean of zero); in roughly one-third of cases, the measured correlation coefficient between these two independent samples will be more than 20% (in either the positive of negative direction)
- About 100 data points are required in each set before the standard deviation of the correlation coefficient drops to below 10%
- The inverse square-root law applies: a doubling of the sample size reduces the standard deviation of the correlation coefficient to approximately 71% of the value with a smaller sample size.
Referring back to the original article, my own feeling is therefore that the relationship discussed is driven by the inherent uncertainty in dealing with small sample sizes. As the article’s author states: “Such correlations may be nothing but coincidence, of course.” As we saw when @RISK was applied to the problem, any statistical analysis can be subject to these traps.
Undaunted, the author continues: “But if the data are genuine, a contribution to world growth is rendered by any institution that enables people to eat rapidly and gain weight. Take a bow, McDonalds.”
Dr. Michael Rees
Director of Training and Consulting
New Frontier now markets proprietary Monte Carlo software with a built-in resampling function to its institutional clients, and my own in-house experts tell me that resampling functionality is available in some commercial Monte Carlo Excel software as well.
This is true – the models for decision making under uncertainty gave a false sense of security. But that’s because the assumptions underlying the risk analysis models were flawed, not because the technique of Monte Carlo simulation was problematic. Monte Carlo simulation is simply a mathematical technique that recalculates many different possible scenarios – but only within boundaries set by the user. You can’t change the underlying math behind these “what-if” calculations.
The article comes close to making this distinction in one sentence: “Critics emphasize that the problem isn't Monte Carlo itself, but the assumptions that go into it.” It then goes on to describe efforts by firms to include “fatter tail” distributions that more accurately reflect the probability of extreme events occurring as an effort to improve Monte Carlo simulation. Tools like @RISK (risk analysis software add-in for Microsoft Excel) allow complete control over the definition of many dozens of distribution types, enabling users to create as fat a tail as they want. While these efforts make sense, it should be made clear that these are changes to underlying model assumptions, not changes to Monte Carlo simulation itself. To equate Monte Carlo simulation as a technique with the probability distributions people decide to use is to equate a carpenter’s choice of nails with his hammer.
Finally, the article cites the need to run tens or hundreds of thousands of scenarios, instead of just 100 or 1000. This too is user-defined, and tools like @RISK can run as many scenarios as desired.
Randy Heffernan
Vice President
| Next |
Subscribe to the Palisade Email Newsletter