Analytics Database¶
Why This Exists¶
This document defines conceptual database responsibilities for the Analytics Domain. It does not define physical SQL, warehouse, or BI implementation.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Business Value¶
Analytics storage must support dashboards, reports, snapshots, historical trend analysis, source lineage, and executive insights without becoming the owner of operational facts.
Conceptual Tables Or Collections¶
| Table or collection | Responsibility |
|---|---|
| analytics_kpi_definitions | KPI names, formulas, versions, thresholds, owners, and status. |
| analytics_dashboards | Dashboard metadata, audience, layout, status, and ownership. |
| analytics_dashboard_widgets | Widget definitions, data sources, filters, and display configuration. |
| analytics_report_definitions | Report purpose, audience, schedule, format, and included KPIs. |
| analytics_analytical_views | Reporting model definitions, source domains, refresh cadence, and schema. |
| analytics_metric_snapshots | Point-in-time metric values, periods, formula versions, and lineage. |
| analytics_performance_summaries | Period or domain summaries of performance, risks, and highlights. |
| analytics_insight_records | Insight observations, severity, evidence, explanation, confidence, and status. |
| analytics_ceo_briefings | Executive briefing records, period, audience, sections, and status. |
| analytics_source_lineage | Source event, aggregate, domain, and calculation references. |
| analytics_refresh_runs | Refresh execution status, duration, source watermark, and errors. |
| analytics_audit_log | Audit records for KPI, report, dashboard, insight, and briefing governance. |
Indexing Considerations¶
Analytics should support indexes for:
organization_id.reporting_period_startandreporting_period_end.kpi_id.dashboard_id.source_domain.source_reference_id.insight_severity.briefing_period.refreshed_at.
Analytical Storage Model¶
Analytics may begin with relational reporting tables and evolve toward analytical stores, materialized views, or warehouse-style models. Any future implementation must preserve source lineage and must not replace source domains as systems of record.
Audit Requirements¶
Audit logging is required for:
- KPI definition approval and revision.
- Dashboard publication.
- Report generation.
- Metric snapshot calculation.
- Insight creation and review.
- CEO briefing creation and publication.
Data Freshness¶
Each analytical view and dashboard should expose freshness metadata. Executive users should be able to distinguish current metrics from delayed, stale, or failed refreshes.