Skip to main content

Product tour · Relationship intelligence

Follow one customer through elan1 Ontology.

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.

Start the tour

5 steps · about 3 minutes · illustrative data

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

The tour

elan1 Ontology, step by step.

Step through at your own pace. Nothing moves on its own.

01 / 05 · Start

Start from your industry's pack.

  • No need to model everything first: add as you go
ontology.elan1.ai/packs

Industry pack

Starting point

  • Customer · Order · Product

    objects

  • Plant · Invoice

    objects

  • AR30

    metric

Add as you go

Industry pack: the starting objects Customer, Order, Product, Plant and Invoice, and the metric AR30, ready to map. Illustrative data. Illustrative data.

Text alternative

The tour as text.

Every step and every screen, written out for screen readers, print and anyone who prefers to read.

  1. 01 Start from your industry's pack.

    On screen: Industry pack: the starting objects Customer, Order, Product, Plant and Invoice, and the metric AR30, ready to map. Illustrative data.

    • No need to model everything first: add as you go

  2. 02 Map your systems to objects. Anything unmapped stays out.

    On screen: Mapping: the ERP's parties, the CRM's accounts and finance's debtors all map to one Customer object; fields left unmapped stay out. Illustrative data.

    • Lineage to each source

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

    On screen: Change control: a change to the Customer object with its impact on pages and alerts listed first, signed off by Asha R. and Ravi K., and the author's own approval refused. Illustrative data.

    • Impact on pages and alerts listed first
    • Versioned
    • Nobody approves their own change

  4. 04 Read: Every product reads it.

    On screen: Explorer: 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.

    • Objects and typed links
    • The same facts in a list view

  5. 05 Govern decides each change.

    On screen: Simulate and share: a new plant simulated with nothing written, a slice of dealers and SKUs shared with a key supplier, and a partner agent's request on that slice held for approval under elan1 Govern. Illustrative data.

    • Simulate a new plant, price or hire
    • Share a slice with a key supplier
    • Partner agents run on it under Govern

What you just saw

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 platform, with elan1 Govern on the one path every action takes.

Start with one process.

Bring one question. We'll draw its map.

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

Questions

The Ontology tour, answered.

Yes. These are elan1 Ontology's own screens, rebuilt for the web, with illustrative data: Kolam Components and the people named are fictional. The tour is ungated and takes about 3 minutes, and its last screen offers Book a demo with elan1 Ontology pre-filled, so you can see the same screens on one process of your own.

No. The elan1 Ontology tour is ungated: no form, no sign-up and no email address. It takes about 3 minutes, and nothing you click changes a real system, because the data is illustrative. When you reach the last screen, Book a demo opens with elan1 Ontology pre-filled, if you want to see it on your own process.

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.

By two named people, and nobody approves their own change. Each object, link, metric and action is signed off on its own, with its impact on pages and alerts listed first, and every sign-off is versioned. In the tour, an illustrative Customer object with 14 properties is signed off by 2 people and read by 3 agents.

Anything unmapped stays out. You map your ERP, CRM and finance systems to objects, with lineage to each source, and the model sets the actions allowed on each object. elan1 Govern decides each change, and partner agents run on the ontology under Govern, so an agent works only within what was signed off.

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.