TBM Framework & Taxonomy

We are struggling with how to break out 0365 in the TBM Model. Right now we are thinking about breaking out Email separate and the remaining 0365 products would then go into Base Productivity.

At a second glance though we realized that when benchmarking the cost at the Service Name, 0365 would be split. It wouldn’t be until Service Category that we would have the cost benchmarked together. We want to make sure we are taking the right approach in TBM and aligned for proper benchmarking.

Benchmarking as in comparing your results against peers\competitors etc is done at the IT resource tower level. Other types of benchmarking can be done at a more granular level.

Think about what is driving you to separate e-mail from the rest.  E-mail could be treated as a productivity tool. There is now wrong way to do it. The driver is your use case.

At Cisco, we treat Email as a service with various service offerings underneath (Outlook Web, Outlook, Eudora, etc). In fact, we call the service Email & Calendaring.

Feel free to contact me for additional information - tpietro@cisco.com

Tim

Thanks Tim. I would agree, if you think about services & offerings and these elements operational, financial, demand and performance. This requires you to break office 365 into different offering under the TBM Taxonomy.