Okay, so last time we had a chance to chat, I made the statement that running CMDB and Service Catalog projects can increase the acceptance of operating in a service-oriented fashion. If you recall, my reasoning was largely due to how foreign a service concept is to IT. So I proposed that by building a data model that integrates the service catalog and CMDB, one can establish a familiar reference point for IT which brings the adoption rate into acceptable portions.

In addition to creating an approach for adoption, you can now create an environment of continuous momentum as the Service Catalog and CMDB projects feed off each other. On one side the CMDB gains enterprise-level exposure and identity of importance. Alternatively, the Service Catalog goes from a simple document that requires continuous maintenance to a credible, customer-facing vehicle for IT to use to manage business relationships with its customers.

So does it sound good? Is there any interest in the challenge? Let me know your thoughts? I would love to help out. Take care, and until next time, keep up the good work.

Also, don’t forget to register for Evergreen’s change management webinar and learn how to Take Change Management from Firefighting to Fire Prevention

Check out our new White Paper on “How To Develop a Service Catalog”.

Technorati Tags: help desk software help desk helpdesk software it help desk desk itil helpdesk software