Islands of data across the Enterprise.
This post is one of a series dealing with common Enterprise Wide Data Governance Issues. Assess the status of this issue in your Enterprise by clicking here: Data Governance Issue Assessment Process
In many large organisations, tactical localised projects over many years has resulted in multiple databases of similar but inconsistent and unlinked data (e.g. multiple customer databases).
Historically, business area owners have been reluctant to share “their data” with other business areas – for fear of data corruption, or occassionally for reasons of “empire building”.
– Information Management nightmare
– Multiple versions of “the truth’.
– No ‘single view of customer’.
– Difficulty in meeting regulatory requirements in the area of ‘Know Your Customer’.
CIO to define and implement the following Policy:
- New data stores must only be created in consultation with the Enterprise Data Architect, taking into account the target Enterprise Data Model.
- Measures are required to replace local islands of operational data with Enterprise wide operational databases, and to implement an Enterprise wide data warehouse.
Does your organisation have “islands of data” – if so, what problems do they cause you?
If not, how did you get rid of them? Did you build “bridges”? Do your data islands feed into a central “Information Warehouse”. Please share your experience.