
InfotoIntell's Reasoning & Insight System
نظام الاستدلال والرؤى من InfotoIntell
User Guide & Reference Manual
Build the semantic layer once. Apply AI-powered KPI diagnostics, anomaly detection, and causal analysis to any business.
by InfotoIntell
Use arrow keys or click corners to navigate →
The KPI Intelligence Engine is a domain-agnostic analytics platform by InfotoIntell. It combines a business-owned semantic layer, AI-powered diagnostics, and an early warning system (EWS) into a single unified workspace — deployable across any industry once the semantic layer is built with your team.
The List View is your KPI registry. Switch to it from the KPI Designer using the view toggle in the top toolbar.

Click + New KPI in the List View. Fill in the required fields:
SUM(AMOUNT) - SUM(REFUND)COUNT(RETURNS) / COUNT(TXN_ID) * 100SUM(AMOUNT) / COUNT(TXN_ID)Every KPI must be reviewed and approved before it is used in analytics. This ensures data governance and prevents unvalidated metrics from influencing decisions.
Navigate to KPI Approval Inbox from the sidebar. This is where reviewers see all pending requests and cast their votes.
The Approval Canvas shows all KPIs in a visual board grouped by status. Drag-and-drop to move KPIs between stages, or use it as a read-only overview of the pipeline.

The Canvas is a visual graph of all approved KPIs and the relationships between them. It is the foundation for diagnostics and root cause analysis.
The legend at the bottom of the canvas is interactive. Click any relationship type to highlight only those edges and dim all others.
You can manually draw relationships between KPIs directly on the canvas to encode domain knowledge.

When a KPI moves unexpectedly, the Diagnostic engine explains why. It combines two evidence sources: the human-drawn relationship graph and statistically discovered Pearson r correlations.
There are two ways to start a diagnostic:
Once the AI completes the analysis, the Diagnostic page shows four key sections:

The platform detects two types of anomalies in KPI time series: statistical outliers (values far from the historical distribution) and trend breaks (sudden changes in direction or velocity).
Values more than 2 standard deviations from the rolling mean are flagged as anomalies. Shown as orange markers on the KPI trend chart.
A machine learning model trained on historical KPI snapshots. Detects multi-dimensional anomalies that Z-score alone would miss.
User-defined threshold rules (e.g. "Return Rate > 0.5%") that fire alerts in real time. Configure in the EWS Rules section of KPI Designer.

Domain experts — people who know the business — draw edges between KPIs directly on the Canvas. This encodes institutional knowledge: “when TXN_VOL rises, Net Revenue follows.”

Manual linking captures what experts already know. It cannot surface hidden statistical patterns, does not carry a strength signal (all edges look equal), and has no lag awareness — so it cannot tell you which KPI leads the other in time.
Every month the Snapshot engine computes Pearson r for every KPI pair at lag 0–3 months. Pairs with |r| > 0.6 that have no existing edge are surfaced as pending suggestions — ready for a domain expert to validate.

Creates a Direct edge in the Canvas. The edge carries the r-value and lag as metadata — visible in diagnostics.
Marks the pair as dismissed. It will not resurface in future Snapshot runs.
Where: KPI Designer → Correlations tab → AI-Discovered Relationships section below the heatmap.

r at lag 2 means KPI A predicts KPI B two months later — a leading indicator.
Click any cell → r per city/type. Orange bars = Simpson's Paradox (sign flips vs. aggregate).
When a KPI moves unexpectedly — or you ask "Why did Net Revenue drop?" — the WHY Engine assembles evidence from two sources: the Canvas graph (manual + AI-accepted edges) and the top 3 Pearson r pairs from the statistical layer, even if they are not yet in the graph.

Not all KPIs are equal in the graph. The WHY Engine classifies every KPI as a Pillar, Connector, or Leaf based on its structural position — and this classification directly changes the root-cause ranking.

pillar_score = in_degree × avg_abs_rWhere in_degree = number of edges pointing TO this KPI, and avg_abs_r = mean |Pearson r| across all its edges.
Manual linking and statistical discovery are not alternatives — they are complementary layers. Together they produce an enriched graph where every edge carries type, r-value, and lag metadata. That enriched graph is what makes the WHY Engine precise.


The Performance tab shows each KPI's value over time with period-over-period comparisons, target attainment, and trend indicators.
Snapshots are computed monthly by the background job. Each snapshot stores the KPI value, period, and any anomaly flags. You can also trigger a manual snapshot from the Snapshots tab.

Iris is InfotoIntell's AI assistant embedded in the KPI Intelligence Engine. It is grounded in your semantic layer — it knows your KPI definitions, formulas, relationships, and business context — and can answer questions, create EWS rules, and explain movements in plain language.