Governed data
- Data sources
- Saved queries
- SQL validation
- Semantic datasets
ບໍ່ພົບການເຊື່ອມຕໍ່ອິນເຕີເນັດ
ກຳລັງພະຍາຍາມເຊື່ອມຕໍ່ໃໝ່
ມີບາງຢ່າງຜິດພາດ!
ກຳລັງພະຍາຍາມເຊື່ອມຕໍ່ໃໝ່
ຂໍ້ມູນອັດສະລິຍະ ແລະ ການກຳກັບ
Governed analytics for semantic datasets, validated saved queries, KPIs, reports, dashboard layouts, pivots, charts, schedules, and exports.
| ພື້ນທີ່ | ສະຖານະ | ຫຼັກຖານ |
|---|---|---|
| Datasets | Semantic | Governed source |
| ລາຍງານ | Scheduled | Delivery proof |
| Dashboards | Persisted layout | Role variant |
ຂັ້ນຕອນຫຼັກ
Each workflow is written as an operational path, not a marketing claim, so buyers can understand the day-to-day module fit.
Feature checklist
How this module exchanges business context with the rest of ERPStack.
| Module | ຄວາມສຳພັນ |
|---|---|
| ບັນຊີ | Financial reports, close metrics, and budget analytics |
| ສິນຄ້າຄົງຄັງ | Stock, movement, replenishment, and aging analytics |
| ຂາຍ / CRM | Pipeline, forecast, customer, and revenue views |
| ປະຕິບັດການຄວາມປອດໄພ | SQL validation block and export edge incidents |
Controls and management visibility expected from a serious ERP module.
AI coverage policy
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
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.
Buyers can see concrete function groups instead of vague capability claims.
Workflows, users, and connected modules show where the module belongs.
RBAC, audit, SIEM, approvals, and reporting are surfaced as first-class concerns.
Public pages link back to app routes so reviewers can compare page claims to product surfaces.