One question arises: Should we make it grow and put further information into

We recommend: Don’t follow this path. As we believe that Cloud Computing will make its way into the companies, we expect that CMDBs will radically change if not completely disappear from the set of IT management tools in companies. The key points are:
- CMDBs were originally designed and created for static physical systems. In the old days a record was created in the CMDB once the server was setup up. In most cases it rarely changed until the server was shut down eventually. Nowadays virtualized and dynamic environments can change any second. They can scale up, scale down or change the location from one continent to another. Most CMDBs and their maintenance processes are simply not prepared for real-time data at all.
- Once companies start to use more and more Software-as-a-Service offers like Salesforce or Office 365, a different type of IT service management will emerge. Your company’s IT support does no longer need to know the servers which Salesforce operates on. A proper IT service management will rather need transparency on who is using which services rather than knowing the hardware it is running on.
Therefore we think that it’s not safe any longer to build the critical information base for your IT management decisions on a concept like the CMDB. Looking ahead, companies will prefer a platform which integrates all relevant information about your IT landscape, focusses on the right level of detail and allows you to collaborate to get to the right management decisions.