Skip to main content
elan1 Ontology

Relationship intelligence

One model of how your business relates.

Objects, links, metrics and actions, each signed off by two named people. elan1 Ontology defines what exists and what may be changed. elan1 Govern decides each change and proves it.

Book a demo
ontology.elan1.ai/explorer

Explorer

Map view · List view

  • Customer · Kolam Components

    places → Order SO-8812

  • Order · SO-8812

    contains → Product Snacks 200 g

  • Product · Snacks 200 g

    made at → Plant Coimbatore

  • Metric · AR30

    reads → Invoice

Explorer screen: customer Kolam Components places order SO-8812, which contains the product Snacks 200 g, made at the Coimbatore plant; the metric AR30 reads invoices; the customer object has 14 properties, is signed off by two people and is read by three agents. Illustrative data. Illustrative data.

What is elan1 Ontology?

elan1 Ontology is relationship intelligence: one signed-off model of your business that every number, decision and agent reads. It defines objects, links, metrics and the actions allowed on them, and holds one golden record per customer, product and dealer. Two named people sign off each element, and elan1 Govern decides each change and proves it.

Updated

The challenge

Every system names the business differently.

The ERP calls them parties, the CRM calls them accounts, and finance calls them debtors. Agents and reports built on each system inherit the confusion, and give different answers to the same question.

A solutions architect maps layers on a glass wall as a colleague watches

  • 01

    Agents guess what words mean.

    Guesses become actions.

  • 02

    Every report re-joins the data.

    Every join adds a definition.

  • 03

    Changes break things silently.

    Nobody sees the impact first.

How it works.

  1. 01

    Start from your industry's pack.

  2. 02

    Map your systems to objects.

    Anything unmapped stays out.

  3. 03

    Sign off each object, link, metric and action: two named people, never your own change.

  4. 04

    Every product reads it.

  5. 05elan1 Govern

    Govern decides each change.

Take a look inside.

See your business as one map.

  • Objects and typed links
  • The same facts in a list view
  • Lineage to each source
ontology.elan1.ai/explorer?view=list

List view

Same facts as the map

  • Kolam Components

    Customer · places → Order SO-8812

  • SO-8812

    Order · contains → Product Snacks 200 g

  • Snacks 200 g

    Product · made at → Plant Coimbatore

  • AR30

    Metric · reads → Invoice

lineage to each source

Explorer list view: Kolam Components, order SO-8812, the product Snacks 200 g and the AR30 metric, each with its typed links and lineage to its source. Illustrative data. Illustrative data.
Take the tour

By the numbers.

  • 4

    things it models: objects, links, metrics, actions

  • 2

    named people per sign-off

  • 1

    model every product reads

An enterprise architect arranges paper cards in layers on a pale concrete table, one card crimson, in a bright architecture studio

Where it works.

All industries

How it fits

The meaning under every action.

Pulse, Decide, Act, Propel and Resolve all read elan1 Ontology, so “customer” means one thing in every answer and action. elan1 Govern decides what any agent may change.

Applications

elan1 Actelan1 Propelelan1 Resolveelan1 Pulse

Foundation

elan1 Ontologyelan1 Decideelan1 Governelan1 Run
elan1 Ontology on the elan1 platform.

Questions

elan1 Ontology, answered plainly.

Ask us anything

An enterprise ontology is one model of how a business relates: its objects, the links between them, the metrics that read them and the actions allowed on them. In elan1 Ontology, each object, link, metric and action is signed off by two named people, and every number, decision and agent reads the same model, so “customer” means one thing everywhere.

It is a signed-off model of your business: objects, links, metrics and the actions allowed on them.

No. Start from your industry's pack and add as you go.

Yes, in open formats.

Because every system names the business differently: the ERP calls them parties, the CRM calls them accounts and finance calls them debtors. Agents built on each system guess what words mean, and guesses become actions. elan1 Ontology gives agents a map they cannot step outside: an agent walks only the links in the map and cannot invent one.

Two named people sign off each object, link, metric and action, and nobody approves their own change. Before a change is signed, its impact on pages and alerts is listed first, and every version is kept. elan1 Govern then decides each change and proves it, so the model every product reads changes only as signed.

You can build an agent. The hard part is around it: rules that refuse by default, approvals that expire, credentials the agent never holds, and receipts your auditor verifies without trusting you. That part is the product.

Start with one process.

Bring one question. We'll draw its map.

Book a demo
  • Allowed · Approved by Asha R.
  • Held for CFO
  • Refused · rule 4.2
Illustrative data.

Start with one process.

Add the next when it holds.

Book a demo
Approvals · Kolam ComponentsIllustrative
  • Allowed · Approved by Asha R.
  • Held for CFO
  • Refused · rule 4.2
RCPT-0042 · signed · chained
A product view with three decisions: allowed and approved by Asha R., held for the CFO, and refused under rule 4.2. Illustrative data.