FOCUS Mappings

Learn how Ternary maps native cloud billing data to the FOCUS format to enable consistent, multi-cloud cost reporting across AWS, Azure, Google Cloud, and Oracle.

FOCUS (FinOps Open Cost and Usage Specification) is an open standard designed by the FinOps Foundation to normalize cloud cost and usage data across providers, making multi-cloud cost analysis more consistent and comparable.

Ternary supports the FOCUS format by ingesting native FOCUS exports provided directly by cloud providers or by ingesting original billing files such as AWS Cost and Usage Reports. When original billing files are used, Ternary automatically maps them to the FOCUS schema. This approach provides access to all standard FOCUS fields while preserving provider specific columns for deeper cost analysis where required.

Within Ternary reports, fields are clearly distinguished based on their origin. Standardized FOCUS fields are presented as multi-cloud fields and identified using a cloud icon, while fields sourced directly from provider billing exports are labeled with their vendor of origin, such as “AWS bill_invoicing_entity” or “GCP consumption_model_id,” and marked with the corresponding provider logo. This visual distinction makes it easy to differentiate standardized fields from cloud native attributes, even when field names overlap across providers.

For more information on what FOCUS enables in Ternary, visit BYOD.

FOCUS fields in Ternary

FOCUS Billing is the primary data source in the Ternary Reporting Engine. Its standardized fields follow the column names of the FOCUS 1.1 specification, alongside a small set of Ternary and provider-specific fields listed further below.

Reports, filters, and API requests use the field names on this page.

FOCUS columns

The table below lists every FOCUS column available in FOCUS Billing, with the name it is shown under in Ternary and whether it is used as a dimension (for grouping and filtering) or a measure (for aggregation).

Ternary display nameFOCUS columnType
Billed CostBilledCostMeasure
Commitment Discount QuantityCommitmentDiscountQuantityMeasure
Consumed QuantityConsumedQuantityMeasure
Contracted CostContractedCostMeasure
Effective CostEffectiveCostMeasure
List CostListCostMeasure
Pricing QuantityPricingQuantityMeasure
Availability ZoneAvailabilityZoneDimension
Billing Account IDBillingAccountIdDimension
Billing Account NameBillingAccountNameDimension
Billing CurrencyBillingCurrencyDimension
Billing Period EndBillingPeriodEndDimension
Billing Period StartBillingPeriodStartDimension
Capacity Reservation IDCapacityReservationIdDimension
Capacity Reservation StatusCapacityReservationStatusDimension
Charge CategoryChargeCategoryDimension
Charge ClassChargeClassDimension
Charge DescriptionChargeDescriptionDimension
Charge FrequencyChargeFrequencyDimension
Charge Period EndChargePeriodEndDimension
Charge Period StartChargePeriodStartDimension
Commitment Discount CategoryCommitmentDiscountCategoryDimension
Commitment Discount IDCommitmentDiscountIdDimension
Commitment Discount NameCommitmentDiscountNameDimension
Commitment Discount StatusCommitmentDiscountStatusDimension
Commitment Discount TypeCommitmentDiscountTypeDimension
Commitment Discount UnitCommitmentDiscountUnitDimension
Consumed UnitConsumedUnitDimension
Contracted Unit PriceContractedUnitPriceDimension
Invoice IssuerInvoiceIssuerDimension
List Unit PriceListUnitPriceDimension
Pricing CategoryPricingCategoryDimension
Pricing UnitPricingUnitDimension
ProviderProviderNameDimension
PublisherPublisherNameDimension
Region IDRegionIdDimension
Region NameRegionNameDimension
Resource IDResourceIdDimension
Resource NameResourceNameDimension
Resource TypeResourceTypeDimension
Service CategoryServiceCategoryDimension
Service NameServiceNameDimension
Service SubcategoryServiceSubCategoryDimension
SKU IDSkuIdDimension
SKU MeterSkuMeterDimension
SKU Price DetailsSkuPriceDetailsDimension
SKU Price IDSkuPriceIdDimension
Sub Account IDSubAccountIdDimension
Sub Account NameSubAccountNameDimension
TagsTagsDimension
📘

Differences from the FOCUS 1.1 column names

  • Invoice Issuer uses the column InvoiceIssuer (FOCUS 1.1: InvoiceIssuerName).
  • Service Subcategory uses the column ServiceSubCategory (FOCUS 1.1: ServiceSubcategory).
  • Provider and Publisher are the display names for ProviderName and PublisherName.
  • Display names spell identifiers as "ID" (for example, Billing Account ID for BillingAccountId).

Additional Ternary and provider fields

These fields are available in FOCUS Billing but are not FOCUS columns. Ternary fields are added by Ternary; provider fields come from that provider's billing export and are labeled with the provider in reports.

SourceFields
TernaryAbsolute Credits (measure); Cloud ID (cloud_id), Cloud Name (cloud_name), Data Source, Fiscal Week, Fiscal Month, Fiscal Quarter, Fiscal Year, Invoice Month, Service ID, Sub Account Number (dimensions)
Ternary (AI)AI Input Tokens and AI Output Tokens (measures); AI Provider, AI Model, AI Model Family, AI Model ID, AI Model Version, AI Publisher, AI Modality, AI API Key ID, AI Interface, AI Data Fidelity (dimensions)
Google CloudAncestry Names (ancestry_names), Credit Type (credits_type)
Microsoft AzureCustomer Tenant ID (customerTenantId), Department Name (DepartmentName), Invoice Section ID (invoiceSectionId / InvoiceSectionId), Invoice Section Name (invoiceSectionName / InvoiceSectionName)
AWSProduct Group (user-defined tag ProductGroup)

How to build a Ternary report using FOCUS Fields?

Reports can be built using a combination of Measures, Groupings, and Filters.

In the report builder, open a measure or grouping picker. FOCUS fields are listed under FOCUS in the picker's Sources sidebar, which is selected by default, and you can type a field name, such as Billed Cost, to search for it.

Notes and considerations

  • Where a direct FOCUS equivalent does not exist, the closest standardized field is used.
  • Provider-specific metadata remains accessible and clearly labeled in reports.

What’s Next

Did this page help you?