IT Service Modeling. What do you really know about your business?

[admitrovic]

My team had a great discussion today with one of our customers regarding IT Service Modeling. I think it is important to understand some of the key considerations that drive should drive practical philosophy around the model, and the CMDB.

1. The reason we create models in the first place is to allow us to categorize and report on information in a meaningful manner. Full stop.
2. The models need to make sense in your organization, and drive understanding of fundamental elements of your organization. This is how we learn and grow.
3. CI levels provide a logical representation of your organization and its business practices. This hierarchy is the key to understanding business impact.
4. CI relationships are the driving force of the model and the CMDB. They are a critical piece of the information puzzle when making decisions.
5. CI attributes are driven by inheritance of information upstream and downstream in the model.
6. Creating a model blueprint that is flexible will ensure consistency over time. Think big, act in the moment.

Do you have any insights, or lessons learned, that you would like to share. Please comment, and share.