In order to put a Configuration Management model in place, you need to address certain areas of your infrastructure so as to ensure that the components within it are healthy and won't be detrimental to the whole unit. Some of the first things you need to evaluate and address are:
Ask yourself, Why are you implementing Configuration Management? Are you trying to improve Incident Response time? Reduce Outages? Prevent repeat outages? Improve service performance? What is your driver? This needs to be documented and made crystal clear to everyone via a marketing and communications plan.
What Already Exists:
Now that you know why, you need to figure out if you have the pieces in place to address the challenge. Is the domain/component specific data available? Is it reliable? Do you need to improve its quality? Do you need to supplement it with new/additional data? Can you do generate what is missing with manual processes or do you need more technology?
If you are a medium sized company or larger, you most likely have several repositories whose data overlaps with data in other repositories. Do you know which piece of data is most reliable? Can you eliminate a whole repository or are just some of the elements within it that is bad? Can you save money on licenses, resources and efficiency gains by consolidating some repositories?
Yes, that's right you need to be a real people-person to get this done. From day one, you need to build alliances like you've never built before. The guaranteed way to fail is by trying to be a dictator. In the role of Configuration Management leader, you are going to need to get people to do a lot of things that they probably don't want to do because it might threaten their fiefdom. You need to convince them to work for the greater good rather than the individual gain by showing them how they will benefit from it. If you fail on this, none of the other items will matter because everyone around you will undermine your effort.
Configuration Management is not a straight forward effort like the other service management process, it is much more iterative. It consists of a lot of moving parts working together in careful balance towards a known end goal. Start by addressing the four areas described above then reassess the challenge before setting out on your formal Configuration Management initiative, your likelihood of success will be much greater this way.