8. Four standards define how FinOps operates, and most organisations are using the wrong combination

The situation

FinOps does not operate in isolation. It intersects with established IT financial management frameworks, asset management standards, sustainability reporting requirements, and an emerging open billing specification. The FinOps Foundation's 2026 survey shows 90% of practices now manage SaaS alongside cloud, 64% manage licensing, and 57% manage private cloud. As scope expands, the frameworks governing that scope become critical.

The complication

Four frameworks compete for attention and budget. Each has a different origin, a different audience, and a different definition of success. Finance teams default to TBM. IT operations default to ITAM and ITSM. Sustainability teams default to GreenOps. FinOps practitioners default to the FinOps Foundation framework. Without deliberate alignment, each team builds its own reporting, its own taxonomy, and its own governance process. The result: four versions of 'total cloud cost' that never agree.

The resolution: four standards mapped and aligned

FOCUS (FinOps Open Cost and Usage Specification)

FOCUS is an open-source technical specification for billing data, maintained by the FinOps Foundation under the Linux Foundation. Version 1.4 was ratified in December 2025. It defines a common schema for billing data across cloud providers, SaaS platforms, and on-premises infrastructure. Before FOCUS, every provider used different column names, different cost categories, and different discount representations. An organisation using AWS, Azure, and GCP had to build and maintain three separate data normalisation pipelines.

FOCUS eliminates that translation layer. AWS CUR, Azure Cost Management exports, and GCP billing exports can all be converted to a single FOCUS-compliant schema. 57% of practitioners plan to adopt FOCUS in the next 12 months (State of FinOps 2025). AWS, Azure, GCP, and Oracle now offer FOCUS-formatted exports natively. Version 1.2 (May 2025) added SaaS billing support. Version 1.4 (December 2025) added contract commitment tracking and split cost allocation methodology.

Practical impact: an organisation that adopts FOCUS reduces its data engineering overhead for FinOps by 40-60% (FinOps Foundation estimate). More importantly, it enables tool portability: a FOCUS-compliant dashboard works with any FOCUS-compliant data source, which reduces vendor lock-in in the FinOps tooling layer.

Implementation guidance for financial services: start with AWS CUR 2.0 exports in FOCUS format (available since mid-2024). Add Azure Cost Management FOCUS exports. Add GCP billing FOCUS exports from BigQuery. Store all three in a single data warehouse (Snowflake, BigQuery, or Redshift). Build dashboards against the unified FOCUS schema. The initial setup takes 2-4 weeks for a data engineer familiar with cloud billing data. The ongoing maintenance is minimal because FOCUS is a stable specification with backward compatibility commitments.

The versioning trajectory matters for planning. FOCUS 1.0 (June 2024) covered core billing columns. FOCUS 1.1 (August 2024) added region normalisation. FOCUS 1.2 (May 2025) added SaaS billing support, which is important for organisations managing SaaS spend alongside cloud. FOCUS 1.4 (December 2025) added contract commitment tracking and split cost allocation methodology. Each version is additive: adopting 1.0 now does not create rework when 1.4 columns become available. Start with whatever version your providers support and upgrade as new versions ship.

TBM (Technology Business Management)

TBM is a framework developed by the TBM Council (now part of the FinOps Foundation following the 2022 merger) for understanding the total cost of IT and communicating that cost in business terms. TBM uses a taxonomy that maps IT costs from general ledger accounts through IT towers (compute, storage, network, end-user) to business-facing services and applications.

TBM predates FinOps and was designed for a world of fixed IT costs: data centres, hardware depreciation, and software licences. Its strength is the cost model: TBM can allocate shared infrastructure costs across business units using activity-based costing. Its weakness is that it was not designed for variable, consumption-based cloud costs that change daily.

The alignment point: Apptio (now IBM) has integrated FinOps and TBM into a single platform. Organisations using Apptio Cloudability for FinOps can map cloud costs into TBM's IT tower taxonomy. NatWest uses this combined approach so the CFO sees cloud spend in the same framework as all other IT spend.

ITAM (IT Asset Management)

ITAM manages the lifecycle of IT assets: procurement, deployment, utilisation, and disposal. In the context of FinOps, ITAM is most relevant for software licensing and SaaS management. The average enterprise uses 100+ SaaS applications (Okta). Approximately 50% of SaaS licences are wasted or unused (Zylo). ITAM practices bring the discipline of licence compliance, contract tracking, and vendor management to the SaaS sprawl problem.

As FinOps expands scope beyond public cloud into SaaS and licensing (90% now manage SaaS per State of FinOps 2026), ITAM and FinOps increasingly overlap. The FinOps Foundation now lists ITAM as an allied persona. Practical integration means sharing a single licence inventory, aligning SaaS renewal cycles with FinOps budget forecasts, and using ITAM's vendor management processes for SaaS rationalisation.

GreenOps (Cloud Sustainability)

GreenOps applies FinOps principles to carbon emissions from cloud infrastructure. Cloud providers now publish carbon footprint data: AWS Customer Carbon Footprint Tool, Azure Emissions Impact Dashboard, and Google Cloud Carbon Footprint. The concept is straightforward: reducing cloud waste reduces both cost and carbon. A rightsized instance costs less and consumes less energy.

GreenOps introduces a tension that pure FinOps does not face. The cheapest region is not always the greenest region. A workload running in a region powered by renewable energy may cost 10-15% more than one in a coal-powered region. Organisations with net-zero commitments (most UK banks have 2030 or 2050 targets) need to factor carbon cost alongside financial cost. No FinOps tool currently optimises for both simultaneously.

The carbon accounting challenge mirrors the cost attribution challenge. Measuring Scope 1 and 2 emissions from on-premises data centres is relatively straightforward: you know how much power you use and the carbon intensity of your electricity supply. Measuring Scope 3 emissions from cloud providers is harder: the provider publishes aggregate figures, but attributing those emissions to specific workloads requires the same allocation models used for cost attribution. If your cost tags are broken, your carbon tags are broken too.

For UK banks, GreenOps is not optional. The PRA's SS3/19 supervisory statement expects firms to manage climate-related financial risks, which includes understanding the carbon footprint of technology operations. The Task Force on Climate-related Financial Disclosures (TCFD) reporting requirements cover Scope 3 emissions, which include cloud provider emissions. Banks that cannot report cloud carbon footprint accurately face regulatory scrutiny alongside reputational risk.

The practical recommendation: include carbon metrics alongside cost metrics in the Layer 5 governance pack. AWS, Azure, and GCP all provide carbon data through their billing consoles. Map carbon to the same allocation model used for cost. Report both to the executive team. The FinOps Lead should own the carbon data pipeline because the data sources, allocation logic, and governance cadence are identical to the cost data pipeline. Adding carbon reporting to an established FinOps practice takes weeks, not months.

Framework alignment matrix

Practical recommendations

Do not attempt to implement all four simultaneously. Start with FOCUS (data normalisation) because every other framework depends on clean, standardised billing data. Add TBM integration if your organisation already uses Apptio or has a mature IT finance function. Add ITAM alignment when SaaS rationalisation becomes a priority (it will, given 50% licence waste rates). Add GreenOps when executive reporting requires carbon metrics, which for UK banks with net-zero commitments is likely within 12-18 months.