I see it both ways because some people look at it and say, wow, it's going to put lot of tax on my information systems. Other people look it the other way and say, well, it's a dashboard. It's instantaneous. It must be getting the data very effectively and timely, and it's easy to do.
And what I see is that dashboards create more usage, CPU and disk utilization based on what triggers do I have and what should I do about it. But what they do is they remove all that wasted time of drilling down needless paths. So I think on average they will actually gain you performance and capability, but more importantly, they improve your productivity if designed correctly.
So the moral of that is if you deliver a smarter and better design it will actually tax the systems less because you are giving the user what they want perhaps on the first pass instead of the third or fifth.
So let me go back to my original analogy. What do you want on your dashboard? I gave the analogy when I talked with a car manufacturer, and they said, so what do you want, and I said, I want a real time traffic monitor that tells me what's happening in the next mile and a half ahead so I know which lane to be in, and that’s exactly what I want.
When my idiot light on the gas gauge comes on, I don’t want to know how many miles, I want to know where the next gas station is. Tap it into my GPS system, make it not what is the event but what can I do about the event. And of course I would like to have the police radar detector built in as well.