Hi All

We are new to CLDY (and Total Cost) and are looking at using a metric that we've seen at both FinOps X and the Apptio Austin conference - commonly known as COIN

Has anyone done this in or using CLDY data?

We think others are doing it in TC, although we have something similar in Apptio BI, and when we look at the examples from Austin there are a couple of areas in the example that we are interested in knowing how others do, particularly:

• Realised savings (anyone got a view on how to calculate that), and
• Non-Prod Scheduling - how are people calculating that?

Thanks

Alec

Hi Alec - that's awesome that your team is interested in reporting on the COIN metric. We've seen quite a few customers build different variations of a COIN report; this is a Total Cost use case so the configuration for it has to be built in TBM Studio.

Tracking realized savings is tricky - I don't have an exact answer to this relative to the COIN report, but I have some customers who have tracked realized savings using the Rightsizing ROI tool in Cloudability. If you're not familiar with it, you can read more about it here: https://help.apptio.com/en-us/cloudability/product/jira-for-rightsizing.htm. There's also an API end point for Rightsizing ROI, so you can bring this data into TBM Studio and potentially build reports on it from there.

For Non-Prod scheduling, most of my customers will track any non-prod cost using an Environment tag, and they'll flag weekend cost using the Day of Week field in Cloudability. Any cost that is non-prod and incurred on the weekend would be flagged as an area for potential savings, assuming those resources could be spun down on the weekends.

Hope this helps!

Hi All

We are new to CLDY (and Total Cost) and are looking at using a metric that we've seen at both FinOps X and the Apptio Austin conference - commonly known as COIN

Has anyone done this in or using CLDY data?

We think others are doing it in TC, although we have something similar in Apptio BI, and when we look at the examples from Austin there are a couple of areas in the example that we are interested in knowing how others do, particularly:

• Realised savings (anyone got a view on how to calculate that), and
• Non-Prod Scheduling - how are people calculating that?

Thanks

Alec

Thanks Taylor

Yes - we are going through things with the delivery team - so I may even point them to you as we'd like to get COIN in asap (as other people use it)

Alec

Hi Alec - that's awesome that your team is interested in reporting on the COIN metric. We've seen quite a few customers build different variations of a COIN report; this is a Total Cost use case so the configuration for it has to be built in TBM Studio.

Tracking realized savings is tricky - I don't have an exact answer to this relative to the COIN report, but I have some customers who have tracked realized savings using the Rightsizing ROI tool in Cloudability. If you're not familiar with it, you can read more about it here: https://help.apptio.com/en-us/cloudability/product/jira-for-rightsizing.htm. There's also an API end point for Rightsizing ROI, so you can bring this data into TBM Studio and potentially build reports on it from there.

For Non-Prod scheduling, most of my customers will track any non-prod cost using an Environment tag, and they'll flag weekend cost using the Day of Week field in Cloudability. Any cost that is non-prod and incurred on the weekend would be flagged as an area for potential savings, assuming those resources could be spun down on the weekends.

Hope this helps!

Hi All

We are new to CLDY (and Total Cost) and are looking at using a metric that we've seen at both FinOps X and the Apptio Austin conference - commonly known as COIN

Has anyone done this in or using CLDY data?

We think others are doing it in TC, although we have something similar in Apptio BI, and when we look at the examples from Austin there are a couple of areas in the example that we are interested in knowing how others do, particularly:

• Realised savings (anyone got a view on how to calculate that), and
• Non-Prod Scheduling - how are people calculating that?

Thanks

Alec