<br />

This document explains how to use the **CUD analysis** report on the
Google Cloud console to understand the effectiveness and financial impact of your
committed use discounts (CUDs).

> [!NOTE]
> **Note** : This document discusses some spend-based committed use discounts (CUDs) that automatically migrate to a new consumption model, which leverages discounts rather than credits. The migration date is indicated by a notification in the Google Cloud console Billing Overview page. For more information about the improvements, the affected CUDs, and any required actions on your part, see [Spend-based CUDs](https://docs.cloud.google.com/docs/cuds-multiprice).

## Overview

You can purchase a commitment to receive committed-use discounts (CUDs). When
you purchase a commitment, you commit to a minimum amount of usage or spend on a
service or product for a specified term. In return, you receive discounts on
your usage. Google Cloud offers two types of CUDs:

- **Resource-based CUDs** : You get a credit back to offset the on-demand price in exchange for your commitment to purchase a minimum level of Compute Engine resources in a particular region. You can purchase resource-based commitments only for Compute Engine. Eligible resources include hardware resources (vCPUs, memory, GPUs, Local SSD disks, and sole-tenant nodes), software OS licenses, and block storage resources (Hyperdisk Exapools). However, CUD analysis reports are not supported for block storage commitments. For more information, see the [Resource-based CUDs documentation](https://docs.cloud.google.com/compute/docs/instances/signing-up-committed-use-discounts).
- **Spend-based CUDs** : You get a discount in exchange for your commitment to spend a minimum amount for eligible services for a specified time duration. Spend-based CUDs are available for a number of Google Cloud services. For more information, see [Spend-based
  CUDs](https://docs.cloud.google.com/docs/cuds#service-specific_spend-based_commitments).

> [!NOTE]
> **Note:** The CUD analysis experience is available for resourced-based CUDs and legacy CUDs. CUDs purchased prior to the migration may still display using the legacy credit-based model until their term expires. As a result, you won't see discount rates directly, instead you will see the legacy process that gives back credits to offset the price you paid. For the affected and unaffected CUDs, see [Products covered by spend-based commitments](https://docs.cloud.google.com/docs/cuds-multiprice#affected-cuds).

You can use the CUD analysis report to answer questions such as:

- How much money am I saving with my CUDs?
- Am I getting the most out of my current commitments?
- How much of my eligible usage is covered by commitments?
- Can I save more by purchasing more commitments?
- Can I optimize my costs with CUD sharing for resource-based commitments?
- Am I fully utilizing the CUDs I bought?
- What's my effective discount rate?

> [!IMPORTANT]
> **Important:** The CUD analysis uses only cost data to render charts, not utilization data. It makes no distinction between charges from resource usage or unused reservations. As a result, CUD analysis is suitable only to determine effectiveness of CUD subscriptions, not reservations effectiveness.

## Required permissions

To view the CUD analysis report for all projects in your Cloud Billing
account, you must be a
[Billing Account Administrator](https://docs.cloud.google.com/iam/docs/roles-permissions/billing#billing.admin)
or [Billing Account Viewer](https://docs.cloud.google.com/iam/docs/roles-permissions/billing#billing.viewer).
Specifically, you need the `permissions.billing.accounts.get` and
`billing.accounts.getSpendingInformation` permissions on your Cloud Billing
account.

You need different permissions to view the CUD analysis report than you need to
view the [Cloud Billing report](https://docs.cloud.google.com/billing/docs/how-to/reports). While Project
Owners, Project Editors, and Project Viewers can access Cloud Billing reports
for their projects, these roles don't include the permissions required to view
the CUD analysis report.

> [!NOTE]
> **Note:** If someone else manages your Cloud Billing account, you might not have the necessary Cloud Billing permissions. If this is the case and you think you should be able to view the CUD Analysis report for your Cloud Billing account, then contact the person in your organization who manages your Cloud Billing account.

For more information about Cloud Billing permissions, see:

- [Overview of access control](https://docs.cloud.google.com/billing/docs/how-to/billing-access)
- [Create custom roles for Cloud Billing](https://docs.cloud.google.com/billing/docs/how-to/custom-roles#resource_associations)
- [Understanding predefined IAM roles for Cloud Billing](https://docs.cloud.google.com/iam/docs/roles-permissions/billing)

## Access the CUD analysis report

To view the CUD analysis report for your Cloud Billing account:

1. In the Google Cloud console, go to the **CUD analysis** page.

   [Go to CUD analysis](https://console.cloud.google.com/billing/commitments/analysis)
2. At the prompt, choose the Cloud Billing account that you want to view.

You can also open the CUD analysis report for a resource or product from the
[**Committed use discounts (CUDs)**](https://docs.cloud.google.com/billing/docs/how-to/cuds-list-overview)
page. Click the row for the commitment to view its details, and then click
**CUD analysis**.

## Understand the CUD analysis report

You can use the CUD analysis report to view detailed information about your
chosen commitment, broken down by the time period and level of detail that you
need. The report includes summary cards, a stacked bar chart, and a summary
table of the commitment's savings and costs to accompany the bar chart.

The **CUD analysis** report has two tabs:

- CUD Coverage - Lets you analyze how much eligible spend is
  covered by your commitments. It shows usage at on-demand rates. For
  spend-based CUDs, this lets you see a normalized view of the spend covered,
  as they are already discounted.

  ![Example of a CUD analysis report with the utilization view.](https://docs.cloud.google.com/static/billing/docs/images/cuds-coverage.png)

  ![](https://docs.cloud.google.com/static/billing/docs/images/cuds-coverage.png)

  This lets you answer the following questions:
  - How much am I covering with CUDs?
  - How much am I paying at on-demand rates?
  - How much have I saved with CUDs?
- CUD Utilization - Lets you understand the efficiency of your existing
  commitment usage. This is displayed as a percentage graph over time. It has
  the capability to show the utilization for the following:

  - Each spend-based commitment (each purchase), which is only available for CUDs in the spend-based model, otherwise this granularity is unavailable.
- The utilization for each resource-based CUD application scope.

  This lets you answer the following questions:
  - Do I fully utilize my commitments?
  - What CUDs am I wasting?

  ![Example of a CUD analysis report with the utilization view.](https://docs.cloud.google.com/static/billing/docs/images/cuds-analysis-utilization.png)

  ![](https://docs.cloud.google.com/static/billing/docs/images/cuds-analysis-utilization.png)

All the metrics shown are computed based on the time period you select. However,
if you have commitments with different expiration dates, the analysis will show
only the data for commitments that were active in the selected time period. Data
from the last day might be incomplete due to data arriving late.

The new CUD Analysis lets you see multiple resources in an aggregated fashion.
For example, you can analyze all your resource-based CUDs.

> [!IMPORTANT]
> **Important:** The CUD analysis doesn't compute utilization when you aggregate more than one type of CUD, because the utilization might be on different resources (cores, RAM, etc.)

### Summary cards

Summary cards above the stacked bar chart show the following details for the
selected commitment type:

- **Active commitments**: The current quantity of active commitments you
  purchased for a selected resource. The date range doesn't affect the
  calculation. The metric always shows the value of active CUDs as of today.

  When you select multiple resource-based commitments, the card can't display
  the active commitment amount because of mismatched measurement units, for
  example, vCPUs compared to GiBs. In that case, the card displays the number
  of active commitments. You see something similar when you combine compute
  flexible CUDs and resource-based CUDs, which have separate units.
- **CUD savings**: The savings from the commitments you purchased for the
  specified period.

- **CUD coverage**: The percentage of your eligible spend for the specified
  period that's covered by the commitments you purchased.

- **CUD utilization**: The percentage of the commitments you purchased
  that were utilized during the specified period. The higher this value is,
  the more value you're getting from your commitments.

- **Potential savings**: The estimated savings you'll receive if you buy
  additional commitments for eligible services in your billing account.

### Stacked bar chart

The stacked bar chart appears below the summary cards and above the summary
table, and shows the following details for the selected commitment type:

- **Commitment-covered costs**: The average daily costs at on-demand eligible rates covered by CUDs (lower part of the bar, using blue for resource-based CUDs credits and green for spend-based CUDs discounts).
- **Eligible cost not covered**: The average daily cost of usage charged at the standard, non-discounted, on-demand rate (gray-colored section of the bar).

To view details for an individual day, hold your pointer over the bar for that
day.

> [!NOTE]
> **Note:** If you want to buy spend-based commitments to cover any gray portion shown in CUD analysis, you should manually calculate the discounted value based on the discounts provided by the CUD product, or use the CUD Recommendations for automated guidance.

### Summary table

The summary table appears below the stacked bar chart and displays the following
aggregate quantities for the selected filters and specified period:

- **Cost at on-demand rate**: The amount you would have paid without commitments. When you analyze resource-based CUDs for one resource (e.g. E2 Cores), the table will display the equivalent resource utilization averaged per hour, because resource-based CUDs are measured by resources, not cost.
- **Commitment cost**: The commitment fee for resource based CUDs (and also for spend-based commitments that use the legacy spend-based model). For analyzing new spend-based CUDs, this represents the portion of the CUD you didn't fully utilize and had to pay for. For example in a given hour, suppose that you commit to spending $10/hr, but only spend $8 on eligible discounted resources during a given hour. For that hour, you are charged $2 under this column to ensure you meet the $10/hr spend that you agreed per the commitment.
- **Effective discount**: The discount rate you obtained. This is calculated by dividing the savings by the cost at on-demand rates.
- **Savings**: The difference between Cost at on-demand rate and Net cost. Positive values represent your savings. Negative values indicate that you're not saving because you're underutilizing your commitments.
- **Net cost**: The total amount you paid, including on-demand plus CUD discounted resources plus commitment costs.

## Analyze your CUDs

To analyze the effectiveness of your CUDs, complete the following steps.

### Filter your report

Use the filters to adjust the scope of usage that's included in your report:

- **Time range** : The *usage date* range of the report. You can select a
  predefined range, or use a custom range (from one day to multiple years).
  Usage costs are shown by the actual usage date, which might differ from
  the invoice month when that usage is charged. See
  [data latency](https://docs.cloud.google.com/billing/docs/how-to/analyze-cuds#data_latency) for more information.

  For dates, in the CUD analysis and other Cloud Billing reports,
  a 24-hour time period starts at midnight US and Canadian Pacific Time
  (UTC-8), and observes daylight saving time shifts in the United States.
- **Analyze**: The type of commitment that you want to analyze. You can select
  from any active spend- or resource-based commitments or any areas with
  eligible usage.

- **Resource type** : The specific resources
  that you want to analyze. This is available when you select **Analyze**.

- **Regions**: The regions included in the report. You can select all
  (default), multiple, or a single region. This is only available for
  region-specific CUDs.

- **Projects**: The projects included in the report. You can select all
  (default), multiple, or a single project.

- **Resource based and Compute Flexible CUD**: Represents all resource-based
  commitments and compute flexible commitments together. This view takes
  Compute Engine resources that are covered by resource-based
  commitments and layers the compute flexible commitment coverage data onto
  those resources. This view lets you see the combined impact of both CUD
  types on the same resources. However, the view doesn't cover the following:

  - Compute Engine resources that are exclusively covered by compute flexible commitments
  - Non-Compute Engine usage that can be covered by a compute flexible commitment, which includes eligible usage from Cloud Run and Google Kubernetes Engine

  > [!NOTE]
  > **Note:** This combined view only provides accurate attribution in the spend-based CUD model. In the legacy model, CUD fees cannot be attributed to specific resource families. Because these fees are excluded from the combined view, the pre-migration savings might appear artificially inflated.

### Adjust groupings and data granularity

Adjust your bar chart settings to view the data that's most important to you.
You can edit the following settings:

- **Group by** : View bar chart data by CUD type, CUD type per region, service, and region. The **Group by** option is available for resource-based CUDs alone or resource-based CUDs and flexible CUDs.
- **Data granularity**: View commitment usage by daily (default) or hourly
  granularity. Select hourly granularity to analyze:

  - Usage patterns throughout the day.
  - When during the day you underutilized your commitment.
  - Fluctuations in daily usage.

  You can query 30 days for hourly data granularity and 3 years for daily
  granularity, but requesting large datasets might result in slower
  performance.

#### Commitment under-utilization

Your commitment utilization shows you how effectively you're using your CUDs.
Several factors can lead to underutilization, such as:

- Your overall usage for the day was below your commitment level.
- Your usage varied throughout the day and was lower than your commitment level for part of the day.
- Your usage and commitments were in different regions.
- Your usage and commitments are in different projects and CUD sharing is disabled on your Cloud Billing account.

Even if you underutilize your commitment, the discounted rate for your
commitment-covered usage can result in lower overall costs compared to paying
on-demand prices.

#### Commitment coverage

If your report shows **Eligible costs not covered by CUDs**, then you're not
maximizing your potential savings. This situation happens when your eligible
usage or spend exceeds the amount that can be covered by your commitments.
To maximize your savings, you can do the following:

- **If your commitments are being fully utilized** and your additional usage or spend comes from stable workloads, then consider purchasing additional commitments to cover the extra costs at discounted rates.
- **If your resource-based commitments aren't being fully utilized** and CUD sharing is disabled on your Cloud Billing account, then consider enabling resource-based CUD sharing. CUD sharing extends your resource-based CUDs to eligible Compute Engine usage across all projects within a Cloud Billing account. This action can help you save costs without buying additional commitments.

## Download your report

To download a CSV file of your CUD analysis report, click the **CSV** button in
the bottom right corner of the bar chart. The CSV provides the hourly granular
data that is used to render the graphs. It provides valuable information such as
each of the resource SKUs used, service, consumption model, start and end times
of usage, and more. The CSV export is limited to 10,000 rows.

## Resource-based CUD sharing for maximum savings

> [!NOTE]
> **Note:** CUD sharing is available only for resource-based CUDs.

If you use the same resource types across multiple projects and in the same
regions, then resource-based CUD sharing maximizes your savings. CUD sharing
applies CUDs from a single project to eligible usage across all projects in
the Cloud Billing account. CUD sharing provides the following
benefits:

- Reduce management overhead: Manage discounts across your billing account, rather than individually.
- Maximize discount usage: Pool resources to fully use your commitments and prevent commitment underutilization.

> [!CAUTION]
> **Caution:** If you have a shared reservation and CUD sharing is enabled on your commitment's Cloud Billing account, then Google recommends that you share your reservation only with projects that are linked to the commitment's Cloud Billing account. Otherwise, when projects outside the Cloud Billing account consume that shared reservation, their usage won't be eligible for this Cloud Billing account's shared resource-based CUDs and will be charged at on-demand rates.

CUD sharing is enabled by default depending on your Cloud Billing
account's creation date and active commitments. For more information, see
[Share resource-based CUDs across projects](https://docs.cloud.google.com/compute/docs/committed-use-discounts/share-resource-cuds-across-projects).

## Understand how CUDs impact your bill

Google Cloud uses a balance sheet format for your bill:

We display credits from savings programs, such as Committed Use Discounts
(CUDs), in your cost reports to provide a direct and transparent view of your
actual savings.

- The **Savings programs** column shows your **actual savings** . This is the final, bottom-line amount you saved compared to what you would have paid at on-demand prices.
  - This column is calculated as follows: Cost at on-demand rates - costs at CUD consumption rate + CUD Fees (if applicable).
  - A negative number indicates savings, while a positive number indicates the CUDs aren't generating savings (a loss).

### Direct savings calculation

We apply your discounted price directly to any usage covered
by a commitment. The **Savings Programs** column now directly shows you the
difference between the on-demand price and what you actually paid.
Using the same example: a CUD that costs **$5.50/hr** to cover **$10/hr**
of on-demand usage.

#### Example: 100% Utilization

In this example, you fully used the resources covered by your commitment.

1. **Discounted Cost** : Your cost for the resources is directly billed at the discounted CUD rate of **$5.50**. There are no separate fees or credits on the bill.
2. **Cost Calculation** : Your final cost is just **$5.50**.
3. **Savings Programs** : It now shows your actual, net savings.
   - **Calculation**: On-Demand Cost - Final Cost
   - $10.00 - $5.50 = $4.50
   - The column displays **-$4.50**.

### Savings presentation

The following table shows how savings are presented. In this example, your final
cost is $5.5/hr and your savings is $4.5/hr.

| Scenario | **Savings Programs** column |
|---|---|
| 100% utilization | -$4.50 (Net savings) |

## View CUD fees and credits in your data exports

If you [export your Cloud Billing data to
BigQuery](https://docs.cloud.google.com/billing/docs/how-to/export-data-bigquery), you can use
queries to analyze the data.

If you export Cloud Billing data to BigQuery, your queries must
account for both CUD models if you use a mix of products.

- **New model CUDs:** Do not look for usage credits. Use consumption_pricing_type to identify discounted usage and calculate cost using the direct rate. The fee for underutilization will appear as a net cost on the CUD fee SKU.
- **Legacy model CUDs:** Continue to sum usage cost (at list price) and credits to determine the final cost.

For examples of how you can use BigQuery queries to view your
commitment fees and credits in your Cloud Billing data exports, see
[Committed use discount queries](https://docs.cloud.google.com/billing/docs/how-to/bq-examples#cud-queries).

## Data latency

Delays exists between when you incur usage and when that usage is reported
to Cloud Billing and processed for costs and credits. This latency
can impact your CUD analysis and cost reports in the following ways:

### Commitment charges and CUD credits

Your Cloud Billing account receives reports of your VM usage costs multiple
times per day, but cost data for commitment charges, CUD credits, and [sustained
use discount](https://docs.cloud.google.com/compute/docs/sustained-use-discounts) credits can be delayed for
up to one-and-a-half days. This reporting difference can make your most recent
costs from the current and previous day appear higher than expected until the
credits to offset those costs are applied.

As new usage data arrives, Cloud Billing might revise the distribution of
your discount multiple times. This can increase the usage line items in your
[Cloud Billing data export to your BigQuery
dataset](https://docs.cloud.google.com/billing/docs/how-to/export-data-bigquery).

### Usage date costs might differ from invoice month costs

Google Cloud and billing-eligible products such as Google Maps Platform,
Google AI Studio, and Firebase report usage data to
Cloud Billing at varying intervals. Due to the complexity of our
billing and processing systems, you might see a delay between your use of
services, and the *usage and costs* being available to view in
Cloud Billing and other cost reports and billing dashboards.
Typically, your cost details are available within a day, but can sometimes
take more than 24 hours to appear.

At the end of a calendar month, late-reported usage might not be included on
that month's invoice and instead might roll over to the next month's invoice.

When you configure your CUD analysis report to view costs for a calendar month,
your usage costs are shown by the actual
[usage dates](https://docs.cloud.google.com/billing/docs/how-to/reports#usage-date),
which might include late-reported usage that is not included on the
invoice when viewing a [cost report](https://docs.cloud.google.com/billing/docs/how-to/reports) using an
[invoice month](https://docs.cloud.google.com/billing/docs/how-to/reports#invoice-month) time range.

## Related topics

- Learn more about [CUDs](https://docs.cloud.google.com/docs/cuds).
- Learn how to [calculate savings with Compute Engine flexible
  commitments](https://docs.cloud.google.com/billing/docs/how-to/cud-analysis-flexible).
- Learn how to [use your Cloud Billing reports to understand cost
  trends](https://docs.cloud.google.com/billing/docs/how-to/reports#credits).
- Learn how to [use cost breakdown reports to understand your
  savings](https://docs.cloud.google.com/billing/docs/how-to/cost-breakdown).
- Learn how to [use BigQuery queries to view your commitment fees and
  credits in your Cloud Billing data
  exports](https://docs.cloud.google.com/billing/docs/how-to/bq-examples#cud-queries).