can anyone provide more information on how to go about designing a CMDB to store documents only like how to g oabout desigining, facotrs we need to take into consideration, wha tkind of attributes we need to store.

any help/document opn this would be apprecuited. We would be using a CA Unicenter Service Desk for our CMDB.

So as to not have to build your CMDB to have all the features of a full fledged Document Management system, which is more work than I'm sure you want to undertake but what you will definitely need to do it right, you have two options:

1) Create loose couplings to documents in other Doc Mmgt systems or
2) Buy a CMDB that already has Doc Mgmt embedded within it.

We've done this in our own system. Trust me, building in your own DM features, linking it to the rest of the features in CMDB, and doing it all correctly is not easy. If you don't build in all the features of a real DM system, the users will not use it. You're better off building a loose coupling to documents in your own DM system and moving on to the next critical problem. You can do so by building categorized links that pivot off of your CMDB entities. So, for example, Products have Design Docs, Build Docs, Deployment Docs, Support Docs, etc. You can create simple web links for these categories to your DM system entries.