BigQuery

Roiva writes these metric observations on each sync. Reference the key in a value formula to use this data in your ROI calculations.

Job Statistics

• Track how BigQuery compute consumption changes after introducing AI-driven data pipelines
• Measure query volume growth as a proxy for AI feature adoption
• Monitor bytes processed per month to understand infrastructure cost trends
• Use slot utilization as evidence of efficiency gains from automated query generation

1. In Roiva: Enter the Project ID of the project whose BigQuery jobs Roiva should read, and set the Region field if its jobs don't run in the US multi-region (us, eu, or a single region such as us-central1). INFORMATION_SCHEMA is read per region, so a mismatch returns no jobs rather than an error; the connection page's setup check says where your jobs actually run. Click Create Connection: Roiva creates a Google service account for this connection and shows its email on the connection page
2. In Google Cloud: Grant that service account two read-only roles on the project: BigQuery Job User, so it can run its query there, and BigQuery Resource Viewer, so it can read every user's jobs from INFORMATION_SCHEMA.JOBS. The connection page lists both gcloud commands, filled in, to paste into Cloud Shell or send to whoever administers your Google Cloud
3. Back in Roiva: The connection page checks each grant, and that Region matches where your jobs run, as the service account, and says what's still missing. Once they're all ticked, click Test Connection
4. Back in Roiva: Link this connection to an initiative on the Initiatives tab

• The Project ID is the short identifier in your Google Cloud console URL (e.g. my-gcp-project, not the numeric project number)
• BigQuery Data Viewer isn't needed, and isn't enough on its own — Roiva reads no tables, only job statistics, and INFORMATION_SCHEMA.JOBS needs the bigquery.jobs.listAll permission that BigQuery Resource Viewer carries
• Roiva holds no key or password for the service account and no Google sign-in, so nothing expires — access lasts until you remove its roles or delete the connection
• If your organization enforces domain-restricted sharing (the iam.allowedPolicyMemberDomains policy, on by default for Google Cloud organizations created since May 2024), Google refuses the grants until an admin allows Roiva's Google Workspace customer ID, shown on the connection page
• Roiva's nightly query runs in your project, so its small BigQuery cost bills there
• Google keeps 180 days of job history, so the first sync reads the whole months still inside it (about five) and the month so far. Roiva keeps every month it records, so the history grows from the day you connect
• Data in INFORMATION_SCHEMA has up to a 24-hour delay for the most recent day