Structure of FOCUS data export

This document provides reference information for the schema of the FOCUS usage cost export to BigQuery. The FinOps Open Cost and Usage Specification (FOCUS) is an open specification that defines clear requirements for technology billing data generators to produce consistent cost and usage datasets. The Columns in the FOCUS export generally map to the fields in the Detailed usage cost export .

FOCUS dataset and data table

In BigQuery, your FOCUS usage cost data is loaded into an immutable datasetcreated in the Google Cloud project that you specified when you enabled the FOCUS export , using this naming pattern:

gcp_billing_immutable_<BILLING_ACCOUNT_ID>_<Location>

The name of the datasetis comprised of three components:
1. gcp_billing_immutable - Dataset name for FOCUS export.
2. Billing_account_ID - ID of the Cloud Billing account where the FOCUS export is enabled.
3. Location - The specific region or multi-region Location that you selected when enabling the FOCUS export.
Dataset name example: gcp_billing_immutable_010101_F0FFF0_61C528_us
A FOCUS billing data tableis created in the FOCUS dataset, named:

gcp_billing_export_focus_<BILLING_ACCOUNT_ID>

Table name example: gcp_billing_export_focus_010101_F0FFF0_61C528

Schema of the FOCUS usage cost data

In the Google-provided immutable BigQuery dataset for the FOCUS export, your FOCUS usage cost data is loaded into a data table named gcp_billing_export_focus_<BILLING_ACCOUNT_ID> .

The columns in the FOCUS export schema generally map to the fields in the Detailed usage cost export , such as account ID, invoice date, services, SKUs, projects, labels, locations, cost, usage, credits, adjustments, currency, and additional fields that provide granular, resource-level cost data.

When you use the FOCUS usage cost data in BigQuery, note the following:

The table schema for the FOCUS Cloud Billing data export can change over time, such as when new fields are added to the FOCUS export. To protect your queries from future schema changes, rather than relying on queries that directly reference the exported columns, we recommend that you use BigQuery views to normalize the data so that the table presents the same schema to your queries. Learn more about this limitation .
When you enable the FOCUS usage cost data export for the first time in Cloud Billing, if you select a multi-region location (EU or US), Cloud Billing data will be available retroactively from the start of the previous month. Data is exported in chronological order. For the initial backfill of exported data, it might take up to five days for your retroactive Cloud Billing data to finish exporting before you start seeing your most recent usage data.
If you enable the FOCUS usage cost data export and select a region location , your Cloud Billing data will be available starting from the date when you enabled the export.
If you enabled, disabled, and subsequently re-enabled the FOCUS usage cost data export, the Cloud Billing data might not be available for the period when data export was explicitly disabled.
Learn more about the frequency of the data loads into your BigQuery tables .
See other limitations that might impact exporting your billing data to BigQuery.

FOCUS schema

The following information describes the schema of the Google Cloud FOCUS usage cost data that's exported to BigQuery.

`x_ConsumptionModelDescription`	STRING	NULLABLE	The description of the consumption model .	`consumption_model.description`

FOCUS conformance report

Not all FOCUS columns are supported. Not all values are supported for all columns. See details in the following table. Where columns are not supported, information might be available in the provider specific columns.

Provider specific columns

Column	Type	Mode
x_CostType	STRING	NULLABLE
x_Credits	RECORD	REPEATED
x_CurrencyConversionRate	FLOAT	NULLABLE
x_ExportTime	TIMESTAMP	NULLABLE
x_Labels	RECORD	REPEATED
x_Location	STRING	NULLABLE
x_Project	RECORD	NULLABLE
x_ProjectLabels	RECORD	REPEATED
x_ServiceId	STRING	NULLABLE
x_SystemLabels	RECORD	REPEATED
x_Tags	RECORD	REPEATED
x_SubscriptionInstanceId	STRING	NULLABLE
x_PriceEffectivePriceDefault	NUMERIC	NULLABLE
x_PriceListPriceConsumptionModel	NUMERIC	NULLABLE
x_CostAtEffectivePriceDefault	NUMERIC	NULLABLE
x_CostAtListConsumptionModel	NUMERIC	NULLABLE
x_ConsumptionModelId	STRING	NULLABLE
x_ConsumptionModelDescription	STRING	NULLABLE

Conformance gaps

Conformance gap type

FOCUS version

Affected column

Conformance gap description

Mitigation

Columns not supported

v1.0

Billing Account Name

Not provided

None

v1.0

Charge Frequency

Not provided

None

v1.0

Commitment Discount Type

Not provided