Data Warehousing Community Forum
October 24, 2019, 01:22:26 am

Pages: [1]   Go Down
Author Topic: Business Case for Moving Silo Data into Corporate EDW  (Read 560 times)
DW Fresher

Reputation: +0/-0
Offline Offline

Posts: 1

View Profile
« on: March 29, 2019, 07:57:12 pm »


I'm trying to put together a business case (or product vision) to convince a department's director to give the go ahead to move their data into our corporate infrastructure and ultimately EDW. The problem is the department are currently executing a project for a new line of business application, or system of record, for their operation. Unfortunately, the supplier involved has recommended to them that they design/build a data warehouse for them in addition to the line of business application. To be honest the team in the department involved in executing the project is too close the supplier. So, there are competing forces at play. Whilst they are free to go down this route, however ill-advised, I need to put together a water-tight business case that explains the benefits in layman's terms of why we should have the data moving into the corporate infrastructure also to avoid a silo situation.

Some bullet points I've put together so far:

* Remove barriers to corporate BI/Analytics tools
* Remove barriers to access data both within the department, and across departments in the business
* Pathway to single source of truth from system of record - can trust the data

Does anyone have any advice or suggestions in regard to the business case?



Pages: [1]   Go Up
Jump to: