I've been writing on this topic for a long time, so it's a bit like I've said all that I really wanted to say. Yet the cool thing is that there are many other points of view emerging at the intersection of cloud services and service management.
So i'm going to start pointing to some of them for logging purposes.
Star here. A topic I have discussed before, now with more voices.
Setting Up the Catalog
The first of these is often the hardest. Historically, IT has tended to build what they it was needed, with marginal input from the user community. Few organizations would have had discussions outside the developer community on growth projections, traffic analysis and response time requirements. This has resulted in an IT design founded on a “just in case” philosophy. The IT design team ensures that, to the best of their capabilities, the configuration they design and deploy will have a substantial safety factor to ensure they can meet their own (limited) perception of the needs of the organization. This often results in a gold-plated configuration: high-end storage systems when SATA2 drives would suffice; dedicated servers instead of virtual machines: low density virtualization instead of pooled high density environments. The permutations (and expenses) are endless.