OLAP and Planning
My name is Tony and I'm a planner. There I said it. Six years ago I was describing the work I was doing to someone and he said, "Oh, you're a planner." I was shocked to be called such a name. Today I am out of the closet. I am not a planner though in the mold that most organizations think of planners. In many places, planning is a combination of very mechanical rollups and dysfuctional negotiations; collect sandbagged data, add it all together, twist arms until people go back to what they were willing to live with, repeat yearly. This type of planning adds little if any value, but is very common. In many places, even the adding up of the data is extremely painful. We used to use Excel for adding up all our data. I have no problem with Excel, when used as designed. Once you start to treat it as a database, all kinds of bad things can happen. First, Excel has capacity limitations. The tool I had built in Excel had to contain 500 assets, 20 to 50 years looking forward of...