# Platform Criteria 4: FOCUS Adoption

| **Application** | Visual One Intelligence (VisualOne / VSI) |
| --- | --- |
| **Platform version referenced** | v6.0.0.1 |
| **Criterion** | FOCUS Adoption: publicly referenceable evidence that the platform has adopted a version of the FOCUS specification to produce, import, and/or export FOCUS datasets |
| **Source basis** | VisualOne reference documentation (VSI Screen Reference Guide, Section 14: FinOps → FOCUS Export) |

## Adoption statement

Visual One Intelligence has adopted the **FinOps Open Cost and Usage Specification (FOCUS)** as a supported output format for its cost and usage data. FOCUS support is delivered as a dedicated, first-class report in the FinOps navigation menu (**FinOps → FOCUS Export**) rather than as a generic export option, and presents the platform's normalized hybrid cost dataset in FOCUS-aligned schema for both on-screen review and file export.

| Attribute | Detail |
| --- | --- |
| **Specification** | FinOps Open Cost and Usage Specification (FOCUS) |
| **FOCUS version adopted** | v1.3 (ratified by the FOCUS steering committee, December 2025) |
| **Functionality supported** | Production and export of FOCUS datasets |
| **Delivery surface** | FinOps → FOCUS Export (/reports/finops/focus-export) |
| **Export format** | JSON, via an "Export FOCUS JSON" download action |

## Implementation detail

## Access and controls

| Element | Implementation |
| --- | --- |
| **Navigation** | FOCUS Export appears as a named report in the primary FinOps menu alongside Savings Report, Chargeback, Amortization, Cost YTD, and the other core FinOps reports |
| **Scope filter** | A **Source Type** filter with All, Cloud, Compute, and Storage options, allowing the FOCUS dataset to be produced for the whole hybrid estate or scoped to a single domain |
| **Export action** | A dedicated **Export FOCUS JSON** button triggering a file download of the underlying dataset in FOCUS-specification JSON format |
| **On-screen dataset** | The same dataset is rendered in the standard analytical grid, with search, saved views, row grouping, pivot mode, column selection, and aggregation, so the FOCUS dataset can be inspected and validated in-product before export |
| **Dataset scale observed** | 285 records in the reviewed environment |

## FOCUS-aligned schema

The FOCUS Export grid exposes the following columns:

| Field group | Columns |
| --- | --- |
| **Charge period** | Charge Period Start, Charge Period End |
| **Resource identity** | Resource ID, Resource Name, Resource Type |
| **Service identity** | Service Category, Service Name |
| **Charge classification** | Charge Category |
| **Cost** | Effective Cost, Daily Cost |
| **Billing account hierarchy** | Billing Account ID, Billing Account Name, Billing Account Type |
| **Sub account hierarchy** | Sub Account ID, Sub Account Name, Sub Account Type |
| **Allocation** | Allocated Method ID, Allocated Resource ID, Allocated Method Details, Allocated Resource Name, Allocated Tags |
| **Tagging** | Tags (raw JSON blob per resource) |
| **Device and platform** | Device Name, Device Type Code, Device Type Description |
| **Usage and capacity** | Price Per GB, Total Used, Usable, Used Pct |
| **Aggregations available** | Count, plus the full column set re-exposed for aggregation via the Columns side panel, for example sum(Effective Cost), max(Price Per GB), avg(Used Pct) |

## Representative record

A single exported record carries the full chain from cloud resource identity through to allocation metadata. One observed row: an Azure Databricks resource identified by its full Azure Resource Manager path (/subscriptions/.../VisualOne_Databricks_Dev), Resource Type "Other", Service Category "Azure", Charge Category "Usage", with Effective Cost, a Billing Account of tenant type, a Sub Account carrying the subscription ID, Device Name "Clear_Azure", Device Type Code "MICROSOFT_AZURE", and a raw Tags blob of {"BU":"IT","Operational Category":"Dev","Owner":"Ronaldo Marques"}.

## Why this adoption is significant beyond cloud

Most FOCUS implementations normalize public cloud billing data. VisualOne's FOCUS Export is produced from the platform's **hybrid** dataset, which unifies on-premises storage, virtualization, backup, and enterprise compute alongside public cloud in a single normalized cost model before rendering it in FOCUS schema.

| Aspect | Detail |
| --- | --- |
| **Hybrid scope** | The Source Type filter offers Cloud, Compute, and Storage, so on-premises infrastructure cost is expressible in FOCUS format, not only cloud billing data |
| **Common cost basis** | On-premises Effective Cost is derived from the platform's documented cost model (power, floor space, personnel, maintenance, and amortized capital) and presented in the same Effective Cost field as cloud charges |
| **Allocation carried through** | The Allocated Method ID, Allocated Resource ID, Allocated Method Details, Allocated Resource Name, and Allocated Tags fields carry the platform's allocation and shared-cost splitting logic into the exported dataset, so downstream consumers receive allocation context rather than raw charges alone |
| **Tag fidelity** | Both the raw source Tags JSON and the normalized Allocated Tags are exposed per resource, preserving the mapping between source-system tag vocabularies and the platform's unified tag keys |
| **Interoperability** | The exported dataset is designed for use in other tools, providing standards-based interchange out of the platform to complement the Cloudability and Right Size collector integrations that bring third-party FinOps data in |

## Ecosystem alignment

| Element | Detail |
| --- | --- |
| **Standard body** | FOCUS is a FinOps Foundation open standard for cost and usage data interchange |
| **Adoption posture** | Implemented as a named, permanently available report rather than an ad-hoc or beta export |
| **Practitioner benefit** | Aligning the organization's cost data to a recognized open specification builds transferable practitioner skill and reduces lock-in to a single tool's proprietary schema |
| **Inbound counterpart** | Third-party FinOps tooling is ingested through dedicated collector types (Cloudability, Right Size), so the platform both consumes from and publishes to the wider FinOps tool ecosystem |

## Summary

| Item | Position |
| --- | --- |
| **FOCUS adopted** | Yes: FinOps Open Cost and Usage Specification |
| **Version** | v1.3 |
| **Produce FOCUS datasets** | Yes: generated from the platform's normalized hybrid cost model |
| **Export FOCUS datasets** | Yes: Export FOCUS JSON action, with on-screen grid review, filtering, grouping, and aggregation prior to export |
| **Scope** | Whole estate or filtered to Cloud, Compute, or Storage source types |
| **Schema coverage** | Charge period, resource identity, service identity, charge category, effective and daily cost, billing and sub-account hierarchy, allocation method and resource fields, raw and allocated tags, device identity, and usage/capacity metrics |

---

Source: https://visualoneintelligence.com/docs/fof-platform-4-focus-adoption/