recfo /learn · runbooks/ · governance

Governance runbooks.

A-01 · Understand Usage & Cost

Data Ingestion & Normalization.

modelCentralised effort~14w wavefoundation stageReady ownershipCCoE/Platform builds and runs the pipeline centrally; teams consume.
why

Every FinOps capability — allocation, anomaly detection, forecasting — reads from this data. Each provider names the same cost column differently, so one cross-cloud question becomes three queries. And if billing stops arriving, every downstream report goes stale without anyone noticing.

what

You build one billing pipeline per provider, all landing daily in one store. Normalise to FOCUS so every source shares the same columns, run the FOCUS validator, and reconcile totals against invoices. Monitoring pages on stale sources; a written process handles provider schema changes.

how · click a step for detail

PlatformPLT
Cloud CoE / FinOpsCCE
start
done
start / end step decision flow rework

kpis · how you know it worked

  • Billing Data Freshness — Hours between provider usage and its availability in the FOCUS lake.24 hours · lower is better
  • Pipeline Success Rate — Successful daily pipeline runs / scheduled runs.99% · higher is better