Platform

Platform

A place for Apptio product users to learn, connect, share and grow together.

 View Only

TBM Taxonomy v2.1 Spreadsheet 

Fri March 23, 2018 06:05 PM

Update on 5/09/2018 to include "Purpose" for the IT Resource Towers in v2.1.

 

This spreadsheet contains the following TBM Taxonomy v2.1 Reference Lists:

  • ATUM v2.1 Cost Pool Reference list
  • ATUM v2.1 IT Resource Tower Reference list 
  • ATUM v2.1 Services Reference list

To download the file

  1. Right-click on the file attachment below and click Save Link (or Target) As.
  2. Choose where you want to save the file, and then click Save.
  3. Extract the individual files from the zip file.

 

Updated 03 Jan 2019 to change unit of measure for Mainframe Database sub-tower from "Database Instances" to "Databases"

Updated 28 Jan 2020 to correct (swap) the Storage Online and Offline definitions for public cloud.



#ATUM

Statistics
0 Favorited
0 Views
1 Files
0 Shares
0 Downloads
Attachment(s)
xlsx file
TBM_Taxonomy_V2.1 FINAL.xlsx   53 KB   1 version
Uploaded - Tue October 29, 2024

Comments

Tue January 15, 2019 09:36 AM

Hi Ed,

 

Is there any plan to add ATMs? If not, do you know what the best practice across the industry is?

 

Cheers

 

Jo


#ATUM

Thu August 30, 2018 06:16 PM

Hi @Ed Hayman, have you done any polling or do you have any stats on taxonomy 2.1adoption? Will organisations that adopt 2.1 have any benchmarking Issues (I.e. a smaller pool to benchmark against)?


#ATUM

Fri May 11, 2018 09:15 AM

Many thanks, Ed. All looks good now.


#ATUM

Thu May 10, 2018 01:03 PM

Jim,

Thanks for calling this out.  I replaced the special character with a standard space throughout the spreadsheet.  Please let me know if you see any that I missed.

 

Also, I posted a zip file yesterday, TBM Taxonomy v2.1 Reference Lists  that has the Cost Pool, IT Tower and Services reference lists in CSV format.   


#ATUM

Thu May 10, 2018 04:56 AM

Please could you update the Excel to make sure only "normal" space characters are used throughout? There are several instances where "non-breaking" spaces (\xa0 character code) are used in the data, and this causes issues for Apptio to import as a clean .csv file, and lookups based on string matches will fail.

 

 

Thanks,

Jim


#ATUM