Skip to content
ERPStack

Intelligence And Governance

Business Intelligence

Governed analytics for semantic datasets, validated saved queries, KPIs, reports, dashboard layouts, pivots, charts, schedules, and exports.

Implemented Evidence-first module page
Primary users
BI analyst Executive Department manager Report owner
/app/analytics
App-derived visual
Business Intelligence workspace
Open app route
SQL
Validated
Dashboards
Role scoped
Export
Audited
Area Status Evidence
Datasets Semantic Governed source
Reports Scheduled Delivery proof
Dashboards Persisted layout Role variant

Core workflows

What the module helps operators complete.

Each workflow is written as an operational path, not a marketing claim, so buyers can understand the day-to-day module fit.

Step 1
Model semantic datasets and governed query sources
Step 2
Build saved queries, KPIs, reports, pivots, charts, and dashboard layouts
Step 3
Schedule report delivery and export evidence
Step 4
Review audit, role-scoped variants, and validated execution paths

Feature checklist

Capabilities grouped the way operators look for them.

3 capability groups

Governed data

  • Data sources
  • Saved queries
  • SQL validation
  • Semantic datasets

Analytics authoring

  • KPIs
  • Reports
  • Pivot presets
  • Chart layouts

Delivery and audit

  • Schedules
  • Export
  • Role variants
  • Audit trail

Connected module map

How this module exchanges business context with the rest of ERPStack.

Module Relationship
Accounting Financial reports, close metrics, and budget analytics
Inventory Stock, movement, replenishment, and aging analytics
Sales / CRM Pipeline, forecast, customer, and revenue views
Security Operations SQL validation block and export edge incidents

Governance and reporting

Controls and management visibility expected from a serious ERP module.

Governance
  • Validated SQL execution
  • Tenant/RBAC scoping
  • Role-scoped dashboards
  • Export audit evidence
Reports
  • Executive dashboards
  • KPI scorecards
  • Scheduled reports
  • Export audit

AI coverage policy

What ERPStack can honestly claim for this module today.

AI claims are tied to the official Agent Tool Registry, evaluation evidence, safe-mode controls, and scheduled-agent monitor readiness. Roadmap modules only show planned coverage until module-native tools are implemented.

AI L3 ready
Coverage claim Current AI coverage: BI and Analytics L3/L3 ready through the official Agent Tool Registry.
Governance evidence Governance evidence: 3 registered tools, 4 evaluation cases, tenant/RBAC/safe-mode registry controls, and AI log evidence.
Scheduled monitor Scheduled monitor readiness: 1/1 ready (BI Dashboard Publish Monitor).
L4/L5 boundary Remaining L4/L5 gap: no autonomous execution or self-optimizing agent behavior is claimed; write paths remain permissioned, previewed, and confirmable.

Evidence-first standard

Module pages explain value, workflow, control, and proof in one place.

This page structure supports the current public module catalog with app-derived visuals, connected-module evidence, governance proof, and report context that can be compared against real product routes.

Feature clarity

Buyers can see concrete function groups instead of vague capability claims.

Operational fit

Workflows, users, and connected modules show where the module belongs.

Governance proof

RBAC, audit, SIEM, approvals, and reporting are surfaced as first-class concerns.

Review path

Public pages link back to app routes so reviewers can compare page claims to product surfaces.