
October 1st, 2012, 08:34 AM
|
|
Registered User
|
|
Join Date: Oct 2012
Location: U.K.
Posts: 3
Time spent in forums: 29 m 50 sec
Reputation Power: 0
|
|
Business case for Data Management Section
I'm in the middle of acquiring a new asset management system for my business. We've done all we can in terms of setting out the requirements, and have even received some bids (surprise!). The system is due to be introduced in the next 3-6 months.
The issue I have is that senior management have decided (in their infinite wisdom) that each section who will be using the system should be responsible for their own data. They do not foresee having a central data management team to monitor the databases, act on issues, compact data, ensure data management protocols are being met, etc etc etc...
I am trying to organise a list of reasons why this is a really bad idea, but am having trouble putting "it's going to cause utter chaos" into management weasel words and put a potential cost to it, either in cash value to the organisation or to the people who will be using the system. Is there anyone out there who can help me with some anecdotal evidence or perhaps some sage management advice gleaned from years of experience?
Literally any small tidbits would be massively helpful at this point.
Thanks everyone! 
|