Datalink (Classic) Integrate Cloudability cost data into TBM Studio

◆ Applies to: Costing Standard , Billing Standard , and Hybrid Business Management on TBM Studio 12.8.3 and later.

Cloudability cost data can be integrated with cost data in other Apptio applications, such as Costing Standard , Hybrid Business Management , and Billing Standard . This integration simplifies setup and maintenance by providing a single point of connection for cloud providers across all Apptio applications.

ATUM support

• ATUM 3.0 columns are mapped by default
• Versions 2.0 and 2.1 can be configured, although you need to file a support ticket for this
• ATUM 1.0 is not supported

Initiate the integration and set up the Cloudability connector

The Cloudability connector can be integrated with Costing Standard in TBM Studio 12.8.3 and later. To initiate the integration process and set up the CLoudability connector, see the Cloudability Connector Guide . This step is required before you configure TBM Studio .

Configure TBM Studio to ingest Cloudability data

1. Load Cloudability data with the Cloudability connector. For more details, see the Cloudability Connector Guide .

   The CTF-Cloud component creates a separate table for each of the cloud providers connected to Cloudability . You can find these in the Cloudability group:

   • For AWS: cldy_monthly_aws
   • For Azure: cldy_monthly_azure
   • For GCP: cldy_monthly_gcp
2. Check the three tables, appended in CLDY Transform Master Data , to ensure all the required fields are appended.

1. Check the Cloud Service Provider Master Data table and remove all appends.
2. Update the first formula step to the following formula:
   • CUR Allocation Filter =0
3. Clear the formulas in the following columns in the first formula step
   • Instance Type
   • Platform
   • Service Category
   • Service Name
   • Service Type
   • Tower
   • Subtower
   • Type
   • Unit
4. Delete the following columns in the first formula step:
   • Instance Type Lookup
   • Service Category Lookup
   • Service Name Lookup
   • Service Type Lookup
   • Subtower Lookup
   • Tower Lookup
   • Type Lookup
   • Unit Lookup
5. (Optional) The following columns aren't required for the integration, so we recommend removing them from the Cloud Service Provider Master Data table to improve performance:
   • From the first formula step: \
   • Amortized Reserved Instance_Cloud Key
   • Azure Preprocessed Data Loaded
   • Cash-Based Reserved Instance_Cloud Key
   • All Completeness columns
   • CUR Blended Reserved Instance_Cloud Key
   • CUR Loaded
   • Primary Unit of Measure
   • Primary Usage Qty
   • Region Code
   • RI Allocation Filter
   • Reserved Instance Weighing
   • All Validity columns
   • From the second formula step:
   • Reserved Instance_Cloud Key
   • All Validity columns
6. In the Append step, append the CLDY Transform Master Data table into the Cloud Service Provider Master Data table with the following mappings:
   • Application =<desired Application dynamic field, if any, otherwise leave blank>
   • Business Unit=<desired Business Unit dynamic field, if any, otherwise leave blank>
   • Cost =<desired Cost column> OR Base Currency Total Cost if cost is non-USD
   • Environment =<desired Environment dynamic field, if any, otherwise leave blank>
   • Instance Type =Instance Type
   • Invoice Amount =Cost
   • IsSharedService =”NO”
   • IS CLDY = “Yes”
   • Location =<Availability Zone or Region>
   • Platform =Platform
   • Product =Product
   • ProductCode =Product Code
   • Provider =Provider
   • Provider Region =Region
   • Purpose =<desired Purpose dynamic field, if any, otherwise leave blank>
   • RecordID =Row ID
   • Service Category =Service Category
   • Service Name =Service Name
   • Service Type =Service Type
   • Subtower =SubTower
   • Tower =Tower
   • UID Metafield =Row ID
   • Unit =Unit
   • Usage Qty =Effective UsageQuantity
7. Check the Servers Master Data table.
8. On the append from the Cloud Servers Transform , update the following column:
   • OID Metafield = ITRT_Cloud_Resource_Key Metafield}&&RecordID
9. Validate and update allocation strategies as needed.
10. Check in your changes.

The Apptio preprocessor will now import Cloudability data and create grouped files with ATUM mappings and specified dynamic fields (if provided) in Apptio S3.