Mapping Cloud Spend

With Yarken you can use a Cloud Usage to allocate cloud spend to Towers and applications.

Note: This guide assumes applications are tagged in your Cloud environment. If applications are not tagged, alternative methods can be used to allocated spend.

Data required:

1. GL

   1. Transaction for cloud spend in the GL

2. Cloud Usage/Spend file

   1. This is a Cloud spend file which has been transformed for easier loading. It must have the following fields:

      1. Tower

         1. Usually determined by mapping Cloud services or products to a TBM Tower

      2. Sub Tower

         1. Use Cloud for all

      3. Asset.

         1. Use Applications for all

      4. Asset ID

         1. The ID used when you setup Applications

3. Applicaiton List

   1. Use the Cloud Usage file to convert the appliction tags to an Application list.

Setup Applications

1. Download the template

   1. Admin → Data Templates

   2. Download the Application Template

2. Populate the template

   1. Use your Cloud Usage file to populate the Application template. You may use the Application name/tag as both the App ID and App Name.

3. Upload Application list

   1. In Admin menu go to Yarken Designer

   2. Under the Assets menu on the left, select “Applications”

      1. This is where we manage our Applications for each month

   3. Click on the month and browse for your Application file.

   4. Upload and map the columns as required.

You now have applications setup and are ready to load spend onto them

Map spend to Cost Pools

1. Use the “Map Manually” option to allocate your full cloud spend to Cost Pool “Outside Services” and Sub Cost Pool “Cloud Service Providers”.

   1. For detailed instructions on how to do this, see How To Guide on Allocating Spend

You now have your cloud spend allocated to:

• Cost Pool: Outside Services

• Sub Cost Pool: Cloud Service Providers

Map spend to Towers and Applications

1. Select the “Map Manually” option when adding Tower rules

2. Choose your mapping strategy and identify your spend

3. Select Multiple Towers

4. Choose “Add Towers from Allocation File”

   1. This options allows your to spread costs to Towers and Applications in one step.

5. Upload your transformed AWS file

   1. Required fields on this file are: Tower, Sub Tower, Cost, Asset, Asset ID. (see notes in Data requirements above)

   2. Map the fields required

   3. Save

You now have your cloud spend allocated to:

• Towers: Each Tower based on usage of products/services (which are mapped to Towers)

• Sub Tower: all in Cloud Sub Tower

• Applications: Based on usage

Viewing your Cloud Spend

1. Applications → Application Portfolio

   1. Filter by vendor to see App portflio for that vendor

2. Technology → Cloud Overview