BI Architecture & Technical Specs

The report builder composes and executes BI reports with built-in comparison periods.

What a report configuration captures:

• A data source or collection to query
• Columns to display, each with its own label, data type, and format
• Filters (including date-range filters)
• Grouping (groupBy) for aggregated views
• Aggregations — count, sum, avg, min, max — per field
• Computed fields built from the formula evaluator
• Sort order and pagination

Comparison periods: every report can enable previous_period (the same duration immediately preceding the current range) or year_over_year (the same dates, one year back). Aeion computes the previous range automatically, executes both queries, and returns change, changePct, and a direction (up / down / flat) for every metric — no manual date math required.

Every execution result includes:

• The row data itself
• Metadata: total row count, execution time, columns, grouping, and aggregations applied
• The comparison block, when enabled: both date ranges, the previous period's rows, and a per-metric summary of the change

The alerting engine monitors metrics on a schedule and triggers alerts when thresholds are breached.

What an alert configures: which report and field to monitor, a condition (above, below, or percentage change), a threshold value, a check interval (hourly, every 6 hours, daily, or weekly), and one or more notification channels (email, Slack, webhook). An optional silenceUntil timestamp temporarily suppresses notifications — useful during a known maintenance window.

How the check runs: on each interval, Aeion evaluates every enabled, non-silenced alert that's due. If the condition is met, a notification fires. If an alert was previously triggered and the metric has returned to normal, the alert auto-clears — no notification needed, no manual dismissal required.

Auto-Clear Pattern:

`

1. Metric drops below threshold → alert "triggered"
2. Ops receives notification
3. Ops fixes the issue
4. Next check: metric back above threshold
5. Alert status auto-updated to "ok" (no notification needed)

`

Scheduled delivery ships reports via email, Slack, or webhook, on a recurring cadence.

What a delivery schedule configures: cadence (hourly, daily, weekly, monthly), delivery time in the recipient's timezone, specific delivery days for weekly/monthly schedules, output format (PDF, Excel, or CSV), one or more delivery channels, an optional BCC list for compliance visibility, and optional conditional delivery — only send when a linked alert is currently triggered.

PDF export with branding: choose page size and orientation, include charts, add your logo and company name, and set a custom header and footer — so a scheduled report reads as your company's report, not a generic export.

AI Explain: takes a chart's underlying data points (label, value, optional timestamp) plus any aggregated metrics, and returns a plain-language summary, a trend classification (up / down / stable), a list of specific anomalies with expected-vs-actual values, and categorized insights (trend, anomaly, correlation, seasonality) each with a confidence score. It's grounded entirely in the report's actual data — it can't fabricate a driver that isn't in the numbers.

AI Report Builder: takes a natural-language prompt ("Create a sales dashboard for Q1"), optionally scoped to a specific data source or chart preference, and returns a working report configuration plus a chart assignment per field and a plain-language summary of what it built.