Review the following links to load data, configure and review reports for IT Towers:
The Identifier for the Cost Source to IT Resource Master Data (which backs the Other Cost Pools object) is system generated and should not be altered. It includes:
- IT Resource ID
- OID Metafield
About the IT Resource ID
The IT Resource ID backs the IT Resource Towers object. It is system generated and should not be altered. It includes:
- IT Resource Tower Name
- IT Resource Sub-Tower Name
About the Keys in the Cost Source to IT Resource Master Data set
The keys in the Cost Source to IT Resource Master Data set are system generated and should not be altered.
Key | Field key is based on | Logic |
Cost Source_Other Cost Pool Key | Cost Center Cost Source Key Metafield | Append the text CC.Map to the Cost Center and Cost Source Key Metafield |
Other Cost Pool_ITRT Key | IT Resource Tower IT Resource Sub-Tower | Append the text ITRST.key with the IT Resource Tower and Sub-Tower |
About the Keys in the IT Resource Tower Master Data set
The keys in the IT Resource Tower Master Data set are system generated and should not be altered.
Key | Field key is based on | Logic |
IT Resource ID | IT Resource Tower Name IT Resource Sub-Tower Name | Concatenate the IT Tower Name and Sub-Tower Name |
Labor_Resource Key | IT Resource ID | Append the text Labor_Resource with the IT Resource ID |
ITRT_Vendor Key | IT Resource Tower Name IT Resource Sub-Tower Name | Append the text Vendor_ITRT to the IT Resource Tower Name and IT Resource Sub-Tower Name |
Other Cost Pool_ITRT Key | IT Resource ID | Append the text ITRST.key with the IT Resource ID |
ITRT_Cloud Key | IT Resource Sub-Tower Name | Append the text Public_Cloud with the IT Resource Sub-Tower Name |
ITRT_Project Key | IT Resource Sub-Tower Name | Append the text ITRT_Projects with the IT Resource Sub-Tower Name |
Asset_Resource Key | IT Resource ID | Append the text Asset_Resource with the IT Resource ID |
Common Computed Columns Needed for IT Towers
There are no specific computed column you need to create. It will vary on your data though, you may need to add in additional granularity in order to allocate to infrastructure or Services directly.
Map data to Cost Source to IT Resource Master Data set
Map your cost center to tower data to the Cost Source to IT Resource Master Data set. Most of the mapping should be self-explanatory at this point. There are no unusual mapping requirements. Just make sure to have the IT Resource Tower, IT Resource Sub-Tower and a percentage split across them based on the cost composition. In 12.7 you can now leverage the Column Map function in your raw dataset to map to the Cost Source to IT Resource Master Data (Map Columns )
Map data to IT Resource Towers Master Data set
Utilize one of the below methods to map IT Resource Towers to the “IT Resource Tower Master Data” set in Apptio. This gives you the opportunity to manage through any changes Apptio automatically makes in the "IT Resource Towers Reference List” in future versions and will not cause friction to upgrades. It is expected that the Reference List will be updated on an as needed basis to reflect the ever evolving IT landscape. As such, these updates would impact your historical IT Resource Tower taxonomy, and may potentially impact prior period allocations. Mapping files will need to be updated accordingly to align to the changing taxonomy. In 12.7 you can now leverage the Column Map function in your raw dataset to map to the Cloud Service Provider Master Data (Map Columns )
This assumes that you have not customized the Reference List. If you have customized it, please reach out to your Apptio representative for assistance if needed. The Out-of-the-Box IT Resource Tower Reference List should NOT be appended to the IT Resource Master Data, regardless of whether you are aligned to the ATUM Taxonomy.
Option 1: Use Apptio’s IT Resource Tower Reference List
- Export the raw “IT Resource Towers Reference List” to Excel and save in the .CSV file extension
- Create meta-field headers like “IT Resource Tower Owner”, “IT Resource Tower Quantity”, and other fields that exist in the IT Resource Towers Master Data set but do not exist in the Reference List
- If you choose, you may populate the rows of the meta-fields like “IT Resource Tower Quantity” directly in the raw dataset before uploading
- Upload your new raw file into Apptio as you would any other new raw data set and name the it “IT Resource Tower List Raw” or something similar
- Create a standard Transform of the newly uploaded raw file as you typically would for any other data-set, and name it “IT Resource Tower List Transform” or something similar
- Complete any Lookups in the Transform that are needed to fill in any meta-field data, if necessary
- Map the new “IT Resource Tower List Transform” to “IT Resource Towers Master Data”
Option 2: Use the Cost Source to IT Resource Tower Mapping
- Export the raw “Cost Source to IT Resource Tower Mapping” to Excel and save in the .CSV file extension
- Create meta-field headers like “IT Resource Tower Owner”, “IT Resource Tower Quantity”, and other fields that exist in the IT Resource Towers Master Data set but do not exist in the “Cost Source to IT Resource Tower Mapping”
- If you choose, you may populate the rows of the meta-fields like “IT Resource Tower Quantity” either directly in the raw dataset before uploading
- Create a standard Transform of the “Cost Source to IT Resource Tower Mapping” as you typically would for any other dataset and name it “Cost Source to IT Resource Tower Transform” or something similar
- If there are fields that do not currently exist in the “Cost Source to IT Resource Tower Mapping”, you may need to obtain and incorporate this data into either the raw mapping file (which you would load in the standard method) or you will need to create additional data columns in the Transform
- Map all appropriate columns from “Cost Source to IT Resource Tower Transform” to “IT Resource Towers Master Data”
NOTE: A similar caveat and approach is relevant for all other Reference Lists and System Created Data in Apptio, should you want to leverage them.
Review the IT Towers object on the models
Model | Actions |
Cost | From Labor to IT Towers, allocate using the Data-based Reference (which is the default). Some possible weighting strategies include: - Department mapping
- Employee % allocation to ITRT
- Activity mapped to ITRT, weighted by hours
From Fixed Asset Ledger to IT Towers, allocate using the Data-based Reference (which is the default). Some possible weighting strategies include: - Amortized projects (e.g. project “tail”)
- Depreciated assets (e.g. infrastructure)
- Weighted by monthly depreciation
From Vendors to IT Towers, allocate using Data-based Reference (which is the default). Some possible weighting strategies include: - Vendor mapping (such as Microsoft=40%, Workspace=35%, Windows Server=24%, etc.)
- Vendor-Cost Center mapping (such as Microsoft for End User Services department=100% to Workspace, Microsoft for Wintel Servers=70% to Windows Server and 30% to Database)
From Cost Source to Other Cost Pools, allocate using Data-based Reference and weighted by the % allocated (which is the default). From Other Cost Pools to IT Towers, allocate using Data-based Reference (which is the default). Some possible weighting strategies including: - 100% direct mapping (such as CC-0120 Help Desk is mapped 100% to Service Desk)
- % allocation to ITRT (such as CC-0150 Compute Operations is mapped 45% Wintel, 35% Linux, 20% Converged Infrastructure)
|
| Budget | From Labor to IT Towers, allocate using the Data-based Reference (which is the default). Some possible weighting strategies include: - Department mapping
- Employee % allocation to ITRT
- Activity mapped to ITRT, weighted by hours
From Fixed Asset Ledger to IT Towers, allocate using the Data-based Reference (which is the default). Some possible weighting strategies include: - Amortized projects (e.g. project “tail”)
- Depreciated assets (e.g. infrastructure)
- Weighted by monthly depreciation
From Vendors to IT Towers, allocate using Data-based Reference (which is the default). Some possible weighting strategies include: - Vendor mapping (such as Microsoft=40%, Workspace=35%, Windows Server=24%, etc.)
- Vendor-Cost Center mapping (such as Microsoft for End User Services department=100% to Workspace, Microsoft for Wintel Servers=70% to Windows Server and 30% to Database)
From Cost Source to Other Cost Pools, allocate using Data-based Reference and weighted by the % allocated which is the default). From Other Cost Pools to IT Towers, allocate using Data-based Reference (which is the default). Some possible weighting strategies including: - 100% direct mapping (such as CC-0120 Help Desk is mapped 100% to Service Desk)
- % allocation to ITRT (such as CC-0150 Compute Operations is mapped 45% Wintel, 35% Linux, 20% Converged Infrastructure)
|
Review IT Tower reports
The following reports are updated after you have configured the IT Towers object:
- IT Towers
- IT Sub Tower - Detail
- IT Towers - Account Composition
- IT Towers - Cost Pool Details
- IT Towers - Detail
- IT Towers - Purpose Details
- IT Towers - Quantity vs Unit Cost Details
- IT Towers - Variance Details
- Data Quality - Financials
- Data Quality - Summary
To see details of these reports (including navigation, roles, objectives, and questions answered for each report), please see the Cost Transparency User Guide in the Online Help.