Platform
Integrations
All use cases
IndustriesPricingProductField Notes
Sign inGet started
Otiox Command · Investigations & Causal Map

Cause and effect, written into the model itself.

Get startedView platform
In the Otiox ontology, a supplier, a purchase order, a machine and a customer order are not rows in separate tables — they are things, bound by relationships, ordered in time. When an order runs late, the chain that led there already exists. The Causal Map makes it visible; Investigations let your team test competing explanations against the evidence until one stands.
app.otiox.comFig. 00
Causal Map
Each chain is a hypothesis until an investigation supports or refutes it.
ChainsDependenciesConfirmed links
Supplier delay → late productionConfirmedLinked recordsOrder in timeStrong
PO-PRED-0001
+33 d late
Shenzhen Precision
MO-PRED-0001
+24 d late
SO-PRED-0001
Machine down → late productionHypothesisLinked recordsOrder in timeModerate
CNC-01
Spindle bearing seized
MO-PRED-0001
+24 d late
SO-PRED-0001
01

Causality, not conjecture.

The relationships between your records already contain the explanation. Otiox makes them legible, and treats every explanation as a hypothesis until the evidence settles it.
Causal Map
Each chain is a hypothesis until an investigation supports or refutes it.
ChainsDependenciesConfirmed links
Supplier delay → late productionConfirmedLinked recordsOrder in timeStrong
PO-PRED-0001
+33 d late
Shenzhen Precision
MO-PRED-0001
+24 d late
SO-PRED-0001
Machine down → late productionHypothesisLinked recordsOrder in timeModerate
CNC-01
Spindle bearing seized
MO-PRED-0001
+24 d late
SO-PRED-0001
01

Causal chains

Known patterns — supplier delay to late production, machine down to late production, quality rework to late production — traced record by record, with the delay at each step.

The whole story, on one line

Causal Map
Each chain is a hypothesis until an investigation supports or refutes it.
ChainsDependenciesConfirmed links
Supplier delay → late productionConfirmedLinked recordsOrder in timeStrong
PO-PRED-0001
+33 d late
Shenzhen Precision
MO-PRED-0001
+24 d late
SO-PRED-0001
Machine down → late productionHypothesisLinked recordsOrder in timeModerate
CNC-01
Spindle bearing seized
MO-PRED-0001
+24 d late
SO-PRED-0001
02

Evidence on every link

Each chain lists what supports it: linked records, the right order in time, and whether the same pattern has occurred before. Its strength is stated as Strong or Moderate.

The weight of an explanation, made visible

Command · investigation
Why is production late?
All late manufacturing orders, last six months
SuspectLate casesAll cases
Inspection benchEvery late caseSame share
Component supplierA fifthA fifth
Pick-and-placeA fifthA fifth
Hypotheses with evidence for and against
Investigate

Test each explanation against all orders.

One supported cause fixes many delays.

03

Hypothesis until shown

Every chain begins as a hypothesis. It is confirmed only when an investigation supports it, and refuted when the evidence points elsewhere.

No conclusion without proof

Investigations
A question, the cases behind it, competing explanations with the evidence for and against each, and a conclusion.
+ New investigation
Control exception: PO approval above the thresholdHypotheses: 0 · evidence: 1Open
Why was MO-PRED-0001 late?Hypotheses: 2 · evidence: 2Open
Why are CNC-01 orders slipping?Hypotheses: 3 · evidence: 5Open
Why was MO-PRED-0003 late?Hypotheses: 1 · evidence: 2Concluded
04

Structured investigations

A question, the cases behind it, competing explanations with evidence for and against each, and a conclusion — all bound to the underlying records.

Understanding that survives a hand-over

Command · investigation
Why is production late?
All late manufacturing orders, last six months
SuspectLate casesAll cases
Inspection benchEvery late caseSame share
Component supplierA fifthA fifth
Pick-and-placeA fifthA fifth
Hypotheses with evidence for and against
Investigate

Test each explanation against all orders.

One supported cause fixes many delays.

05

Patterns across time

Chains filtered by cause and window — 30, 90 or 180 days — reveal whether one supplier or one machine keeps appearing behind late orders.

The recurring cause, not the passing symptom

Risk Inbox
What is likely to go wrong next, why the engine thinks so, and what you can do about it.
Run engine
Open · 14Acted on · 6Came true · 3Averted · 5
RecordRiskLikely
MO-PRED-0001Late production82 %
SO-PRED-0004Promise at risk71 %
LOT-2026-118Lot expiring64 %
INV-2026-0213Payment late58 %
RM-STEEL-04Stockout47 %
06

Confirmed links inform the future

Once a cause is confirmed, the Predictive Engine gives it weight in future predictions. Each investigation sharpens the next forecast.

A system that learns from every answer

02

From a question to a conclusion.

Open an investigation from a late order or a control exception. Otiox gathers the related records and proposes explanations; your team adds evidence for and against until the answer is clear.
  1. 01
    Begin from any record, risk or control exception
  2. 02
    Competing hypotheses, each with its own evidence
  3. 03
    Evidence that points to real records, not screenshots
  4. 04
    A conclusion that confirms or refutes the chain
app.otiox.com
Command · investigation
Why is production late?
All late manufacturing orders, last six months
SuspectLate casesAll cases
Inspection benchEvery late caseSame share
Component supplierA fifthA fifth
Pick-and-placeA fifthA fifth
Hypotheses with evidence for and against
Investigate

Test each explanation against all orders.

One supported cause fixes many delays.

03

How an investigation unfolds

From a late order to a confirmed cause.
  1. 01

    Ask

    Why was this order late? Begin from the record itself

  2. 02

    Trace

    Otiox follows the chains that lead to it

  3. 03

    Hypothesise

    Set competing explanations side by side

  4. 04

    Weigh

    Attach the evidence for and against each

  5. 05

    Conclude

    Confirm or refute — and every view updates

04

Reasoning that remains readable.

Open and concluded investigations sit together with their question, type, hypotheses and evidence. Anyone who joins later can follow how an answer was reached, and why.
  1. 01
    Typed questions, such as 'Why is production late?'
  2. 02
    Hypothesis and evidence counts at a glance
  3. 03
    Open and concluded status, with age
  4. 04
    Linked to the decisions that followed
app.otiox.com
Investigations
A question, the cases behind it, competing explanations with the evidence for and against each, and a conclusion.
+ New investigation
Control exception: PO approval above the thresholdHypotheses: 0 · evidence: 1Open
Why was MO-PRED-0001 late?Hypotheses: 2 · evidence: 2Open
Why are CNC-01 orders slipping?Hypotheses: 3 · evidence: 5Open
Why was MO-PRED-0003 late?Hypotheses: 1 · evidence: 2Concluded
05

The idea, applied.

Scenarios from the demo workspace, walked through step by step — on the same data you receive when you sign up.
01

Recurring delay cause

Why orders keep running late, with evidence.
02

Supplier slip impact

Everything downstream of one late supplier.
03

Machine breakdown

A key machine stops mid-week. Who is affected.
06

One ontology, seven ways of seeing it.

Every Command view reads the same things, the same relationships and the same history. An answer found in one becomes evidence in all the others.
01

Predictive Engine

Risks, forecasts and what-if scenarios, explained
02

Accuracy & Calibration

Every prediction frozen and judged against what happened
03

Decisions & Interventions

Who decided, on what evidence, and whether it worked
04

Explorer & Dependency Map

Everything a record is related to, and what is at risk
05

Time Machine

Any record or stock exactly as it was on a date
06

Rules & Controls

Company rules monitored, with attested control runs
07

Questions

01Where do the causal chains come from?
From relationships already present in your records: a purchase order supplies a material, the material is reserved for a manufacturing order, the order builds goods for a customer. Otiox examines timing and history to judge the strength of each chain.
02What distinguishes a hypothesis from a confirmed link?
Every chain begins as a hypothesis. It is confirmed only when an investigation concludes in its favour, and refuted when the evidence goes against it.
03Can we investigate more than late production?
Yes. An investigation can begin from any record, risk or control exception — a purchase order approved above its threshold, for example.
04Does this replace our quality or 8D process?
It supports it. Investigations keep the question, explanations, evidence and conclusion beside the real records, which makes formal reports faster to prepare and easier to defend.
Otiox

Understand why — once, and for good.

Open the demo workspace and follow a supplier delay all the way to the customer order it placed at risk.

Get startedLearn more