What is Apptio’s recommendation for how to map labor for cloud applications to subtowers?  For example, we are just starting a Service Now implementation... should labor for that effort be flagged as “App Dev” since you really are developing the app, or should it be “Cloud Apps” since you want the cost to be tied to your overall Public Cloud spend?

The thing that got me thinking about this is, on the IT Management – Public Cloud report, there is a KPI:

If you flag labor for a cloud app as App Dev or App Support, how would you be able to tie that labor into your total Cloud labor spend?  But on the other hand, if you call it Cloud Apps, are you potentially understating your App Dev/Support costs?

Great question.  The recommendation would be to map those labor costs into Cloud Apps in order to be able to see the labor spend associated with developing, configuring, or maintaining your cloud services.  This choice does require a more specific definition of the App Dev tower (another logical choice), where that would be considered application development costs for on-prem applications, either custom-built or packaged.

Thanks, Randall.  That makes sense and was the direction I was leaning... just wanted to make sure I was in alignment with best practices.