text: would like opinions on weather a cmdb shoud be developed in-house or purchased from vendor?   good question!  and one we could ask about any large software app.  i think the question to ask yourself when looking for this answer is, "what is in greater supply?  money or the talent to build and support the application?"  for example: if you're flush with cash and have little available talent (don't have the right skill sets or the right skill sets are busily doing other things), then a purchase is the best option.  if cash is in short supply and you have idle talent, then a system developed in-house may be a good option.  keep in mind the in-house development doesn't end after deployment.  someone will need to maintain the application over time.  this is, imho, the biggest failure of most in-house implementations - an organization forgets to allocate cycles/money for this.  another reason to build your own may be your own processes.  if there's no prepackaged system capable of conforming to your processes and the business is unwilling to change for the system, then you may have to develop your own.  a cmdb is a huge undertaking.  i'm not familiar with the talent you have available, but i would shudder to think how complex of an undertaking it would be to roll your own.  i would compare it, in scope, to a financial system and i would always buy in that instance.  dave