Otiox Command · Explorer & Dependency Map

The ontology, opened to view.

Otiox is built on an ontology: every supplier, order, material, machine and customer is a thing in its own right, and every relationship between them is a recorded fact — created by the work itself, kept in time, and read by every other part of the system. The Explorer and Dependency Map let you follow those relationships from any record, and see what is at risk when one of them strains.
app.otiox.comFig. 00
Explorer
One record and everything connected to it, up to two steps away. Click a record to put it in the middle.
SupplierPurchase orderManufacturing orderCustomer orderProductMaterialMachine
1 step2 stepsOpen records onlyAs of 26 Oct 2026
MO-PRED-0001MO-PRED-0002SO-PRED-0001PO-PRED-0001PO-PRED-0002RM-STEEL-04INV-S-0412Contract 2026Shenzhen Precision
01

Relationships as facts, not drawings.

Any tool can draw a graph. What matters is what the graph is made of. In Otiox every connection is created by the work itself — a receipt, a reservation, a schedule — kept in time, and used by every other part of the system to reason.
Explorer
One record and everything connected to it, up to two steps away. Click a record to put it in the middle.
SupplierPurchase orderManufacturing orderCustomer orderProductMaterialMachine
1 step2 stepsOpen records onlyAs of 26 Oct 2026
MO-PRED-0001MO-PRED-0002SO-PRED-0001PO-PRED-0001PO-PRED-0002RM-STEEL-04INV-S-0412Contract 2026Shenzhen Precision
01

Any record at the centre

Suppliers, purchase orders, manufacturing orders, customer orders, products, materials, customers, machines and invoices — any of them can be the starting point.

Begin wherever the concern lies

Explorer
One record and everything connected to it, up to two steps away. Click a record to put it in the middle.
SupplierPurchase orderManufacturing orderCustomer orderProductMaterialMachine
1 step2 stepsOpen records onlyAs of 26 Oct 2026
MO-PRED-0001MO-PRED-0002SO-PRED-0001PO-PRED-0001PO-PRED-0002RM-STEEL-04INV-S-0412Contract 2026Shenzhen Precision
02

One step, or two

Direct relationships, or two steps out to find the less obvious ones: the customer behind the order behind the material behind the supplier.

Exposure no one had accounted for

Dependency Map
Pick a supplier, material, product or purchase order to see what depends on it, and what is at risk.
4 at risk2 POs · 1 material · 2 MOs · 1 customer order · €48,200 revenue
Shenzhen Precision
PO-PRED-0001+33 d late
RM-BEARING-62Cover ends 4 Nov
MO-PRED-0001Start blocked
SO-PRED-0001 · Alpen GmbHDue 12 Nov
MO-PRED-0004
PO-PRED-0002+30 d late
03

Dependencies, with risk

From a supplier, material, product or purchase order, the full tree of what depends on it — every record at risk flagged, and the revenue involved.

Consequences understood before they arrive

Time Machine
Any record as it was at a moment, the same record at two moments, and stock of every item on a date.
A record thenCompare two momentsStock on a date
MO-PRED-0001as of 19 Sep 2026, 09:16
Status
In production
Planned finish
14 Sep 2026
Quantity
250 × GBX-40
Material reserved
RM-STEEL-04 · 180 of 250 kg
Machine
CNC-01
Last changed by
M. Novak · 18 Sep, 16:02
From recorded history only. History is archived permanently and never deleted.
04

As of any date

Relationships are kept in time, so you can see them as they stood on a past date — the context in which a decision was actually made.

Context for every decision, then and now

Command · impact
One late purchase order
Purchase order → builds → customer orders
LinkRecordState
Purchase orderPCB orderLate now
BuildManufacturing orderWaiting for material
CustomerSales orderAt risk
Customer orders affected
Simulate

Test a further slip before it happens.

Customers told days ahead, not on the day.

05

Missing links, surfaced

Because relationships are expected, their absence is visible: orders without a supplier, lots without a source, invoices without a receipt.

Gaps closed before they matter

Dependency Map
Pick a supplier, material, product or purchase order to see what depends on it, and what is at risk.
4 at risk2 POs · 1 material · 2 MOs · 1 customer order · €48,200 revenue
Shenzhen Precision
PO-PRED-0001+33 d late
RM-BEARING-62Cover ends 4 Nov
MO-PRED-0001Start blocked
SO-PRED-0001 · Alpen GmbHDue 12 Nov
MO-PRED-0004
PO-PRED-0002+30 d late
06

The same facts, everywhere

The relationships you explore here are the ones the Predictive Engine, the Causal Map and the Rules read from. One model, not a separate diagram.

No drift between picture and reality

02

If this supplier slips, what follows?

The Dependency Map follows recorded relationships downstream from a single starting point — every purchase order, material, manufacturing order and customer order that depends on it, with those at risk marked.
  1. 01
    Begin from a supplier, material, product or purchase order
  2. 02
    The full tree of dependants, level by level
  3. 03
    Records at risk flagged, with the reason
  4. 04
    Customer orders and revenue exposed, in total
app.otiox.com
Dependency Map
Pick a supplier, material, product or purchase order to see what depends on it, and what is at risk.
4 at risk2 POs · 1 material · 2 MOs · 1 customer order · €48,200 revenue
Shenzhen Precision
PO-PRED-0001+33 d late
RM-BEARING-62Cover ends 4 Nov
MO-PRED-0001Start blocked
SO-PRED-0001 · Alpen GmbHDue 12 Nov
MO-PRED-0004
PO-PRED-0002+30 d late
03

Following a relationship

A few steps from a concern to an answer.
  1. 01

    Choose a type

    Supplier, order, material, machine, customer…

  2. 02

    Find the record

    By name, number or any field

  3. 03

    Extend

    One or two steps, open records only, as of a date

  4. 04

    Follow a thread

    Select any related record to continue from it

  5. 05

    Act

    Open an investigation or rehearse a scenario from there

04

To know a business is to know its relationships.

The Explorer is how a team comes to understand its own operation: from a supplier to a purchase order, to the manufacturing order it feeds, to the customer who waits — each step a fact on the record.
  1. 01
    Nine record types, all related
  2. 02
    One-step and two-step neighbourhoods
  3. 03
    Open-records-only and as-of-date filters
  4. 04
    Records with missing relationships highlighted
app.otiox.com
Command · impact
One late purchase order
Purchase order → builds → customer orders
LinkRecordState
Purchase orderPCB orderLate now
BuildManufacturing orderWaiting for material
CustomerSales orderAt risk
Customer orders affected
Simulate

Test a further slip before it happens.

Customers told days ahead, not on the day.

07

Questions

01What is an ontology ERP?
An ERP that models the business as real things — suppliers, materials, machines, orders, customers — and the relationships between them, rather than only as rows in separate tables. Relationships become first-class facts the system can reason with.
02Do I need to build the relationships myself?
No. They arise from everyday work in Otiox and from connected systems: raising a purchase order, reserving material, scheduling a machine, invoicing a customer.
03Which record types can be explored?
Suppliers, purchase orders, manufacturing orders, customer orders, products, materials, customers, machines and invoices.
04Can I see relationships as they were in the past?
Yes. Set an 'as of' date and the Explorer shows the relationships as they stood, from recorded history.
Otiox

Follow the thread from any record.

Open the demo workspace, start from a supplier, and see everything that depends on it.