Asset Library / FinOps Use Cases / Verify accuracy of provider invoices
In order to verify that the charges found in the FOCUS dataset match those of the providers invoices a FinOps Practitioner can aggregate cost data from providers for a billing period and compare it to invoices.
SELECT ProviderName, BillingAccountId, BillingAccountName, BillingCurrency, SUM(BilledCost) AS TotalBilledCost FROM focus_data_table WHERE BillingPeriodStart >= ? AND BillingPeriodEnd < ? GROUP BY ProviderName, BillingAccountId, BillingAccountName, BillingCurrency
Time (hours/days) between updates of cost data, e.g. the time since the last ETL run or sharing of data.
This time will become shorter at higher levels of maturity. It may be days or a month when done manually at the Crawl phase. At the Run phase, internal cost updates may happen as frequently as the CSP provides new data (e.g. AWS = up to 3x/day) or intentionally slower to reduce ETL execution cost.
Data Update Frequency = Time of Latest Cost Update – Time of Previous Cost Update
Data Sources:
Related Capabilities
This measures the cycle time taken to complete the ETL (Extract, Transform, Load) processes.
It should be faster than the frequency of data updates to avoid obsolete data being presented.
Processing Time = End Time – Start Time
Data Sources:
Related Capabilities
Time (hours/days) between the cost occurring and the cost being ingested, normalized, and displayed back to cloud stakeholders.
This time is shorter at higher levels of maturity. At the Crawl phase, it may be around one month. At the Run phase, internal cost updates happen as frequently as the CSP can provide accurate data (e.g. AWS = 2 days).
Cost Visibility Delay = Time of Displaying Cost – Time of Cost Generation
Data Sources:
Related Capabilities
FinOps Practitioner
Data Ingestion
