Skip to main content

Business Intelligence Tools

Cloudaware Cost Management supports exporting curated billing and allocation datasets to Business Intelligence (BI) platforms such as Tableau, Microsoft Power BI, Looker, BigQuery, Snowflake, or similar analytics tools.

Use this guide to choose a BI integration pattern, model Cost Management data consistently, and govern refresh, access, and official reporting views.

Design Principles​

When integrating with BI, follow these principles:

  • Treat Cloudaware as the source of truth for cost calculations, allocation, and effective cost metrics.
  • Keep BI models aligned with Cloudaware business mapping (BUs, products, customers, regions, environments).
  • Prefer a small number of well‑designed fact tables (cost, commitments, optimization, anomalies) over many overlapping extracts.

Common Patterns​

Typical integration approaches include the following patterns:

  • Scheduled report exports.
    • Use reports to produce CSV/Excel extracts of cost and allocation data on a schedule.
    • Ingest these files into BI via staged storage (for example, S3, Blob, GCS, or shared file locations).
  • API‑driven pipelines.
    • Use Salesforce/Cloudaware APIs to pull cost data into a data warehouse (for example, BigQuery, Snowflake, Redshift).
    • Build BI models on top of the warehouse tables.
  • Direct connectors.
    • Some BI tools can connect directly to Salesforce objects. When using this pattern, be mindful of API limits and performance.

Choose the pattern that best fits your data volumes, refresh needs, and existing data architecture.

Model Data in BI​

In your BI tool:

  • Represent cost datasets as fact tables with measures such as:
    • Effective cost, on‑demand cost, usage quantities.
    • RI/SP coverage and utilization metrics.
    • Optimization and waste metrics where relevant.
  • Represent BUs, products, customers, regions, and environments as dimension tables, ideally reusing the same codes and hierarchies as in Cloudaware business mapping.
  • Build semantic models (data sets, cubes, semantic layers) that:
    • Hide low‑level implementation details.
    • Expose clear, business‑oriented fields for analysts and self‑service users.

Ensure that BI calculations, such as unit costs and margins, are consistent with definitions agreed in your FinOps practice.

Governance and Refresh​

  • Align refresh schedules with your Cost Management billing cycles and export cadence.
  • Use BI access controls to mirror who can see which scopes (for example, BU‑specific datasets or row‑level security).
  • Document which BI dashboards and reports are “official” for financial or operational use, reducing the risk of conflicting views.

For more information about export mechanisms and coordination with finance and BI teams, see Exports.