We have our first data warehouse committee (seven people). Our task is to submit a recommendation to set a data warehouse/mart infrastructure in place and present it to our budget committee. We're having a tough time trying to justify the startup cost (for migration, transformation, administration tools, reporting technologies and OLAP tools). We have a list of the "benefits" in terms of soft dollars, but our recommendation will only be to set the infrastructure in place, not to build one as part of our assignment. Can someone help? We're not willing to let some of the tools go - our data is really dirty.
Sid Adelman's Answer: The problem with just implementing the infrastructure and not actually delivering anything to the users is that there are no tangible benefits you can point to, none at least that contribute to the bottom line. Your project is exposed. You need to identify a real application, ask for more money, more resources and more time and then build something that's useful.
Regarding dirty data - you should not give the users a data warehouse with dirty data. It has to be cleaned. Would it be possible to select an application that has reasonably clean source data and make that your first project?
Register or login for access to this item and much more
All Information Management content is archived after seven days.
Community members receive:
- All recent and archived articles
- Conference offers and updates
- A full menu of enewsletter options
- Web seminars, white papers, ebooks
Already have an account? Log In
Don't have an account? Register for Free Unlimited Access