The supply chain ontology is Juno’s built-in map of supply chain things and how they relate.
The ontology exists before your first source; your team reviews proposals against it.
The ontology is the target of every mapping. Your team reviews proposals against a model that is already there, in place of defining one from a blank page. The objects are the ones a supply chain conversation uses: material, plant, supplier, purchase order and its lines.
Each object carries four parts. Attributes are its properties. Relationships say how it connects to other objects. Measures are the numbers calculated from it. Synonyms are the words your people use for it, which is how a question in plain language finds it.
Questions and agents read the same ontology, so a term means one thing everywhere. Days of supply is calculated one way for ChatLima, for the safety stock agent and for the weekly digest. A change to that calculation reaches all three at once.
Your own objects join the same map. Juno keeps your additions beside the ones that ship with the product and marks which is which, so a later release of the built-in ontology arrives alongside your work.
Attributes, relationships, measures and synonyms: one object, fully described.
A question in plain language lands on this description. L. Tan’s Wednesday question about the open lines she can still cancel needs the object, the open state, the cancellation window, the schedule line date and the open value. Juno reads them here, then finds the mapped columns that carry them.
Objects, attributes and relationships for the whole chain, from partners to finance links.
Supplier, supplier site, customer, carrier, contact.
Material, material at plant, bill of materials, where-used, product group.
Plant, storage location, distribution centre, port, customer site.
Purchase order, line, schedule line, sales order, scheduling agreement, delivery schedule.
Stock on hand, stock in transit, batch, goods movement, reservation.
Planned order, production order, forecast, exception message, safety stock.
Delivery, shipment, freight order, container, tracking event.
Inspection lot, quality notification, defect, usage decision.
Invoice, payment term, price condition, cost centre, currency.
Measures ship with the objects they belong to. On-time in-full, days of supply, forecast error, open order value and supplier late rate each carry one calculation, written once and read everywhere. Each measure names the attributes it uses, so a reader checks the arithmetic on the screen.
One object, defined by the people who own the data, published as a version.
| Part of the object | What the team defined | Where the values come from |
|---|---|---|
| Object name | Cancellation window | added by P. Sharma on Tuesday 11:20 |
| Attributes | Supplier · material group · window in days · valid from · source document | the supplier agreement register and SAP EKPO.ZZ_CXL_WDW |
| Relationships | Applies to a purchase order line · agreed with a supplier | chosen from the objects already in the ontology |
| Measures | Days left in the window, counted from today | the window with the requested delivery date |
| Synonyms | “cancel window”, “NCNR window”, “free cancellation period” | typed by the team and taught again as vocabulary |
| Status | Published as ontology version 4 | reviewed by D. Okafor and J. Ridley |
A custom object takes minutes to define and stays in your estate. It behaves like any other object: questions find it, mappings point at it, agents read it, and the review screen confirms the columns that fill it.
Custom attributes and custom relationships follow the same route where a whole object would be too much. The cancellation window began as one attribute on the purchase order line and became an object once the team needed windows by supplier and material group.
The ontology keeps an append-only history. A new object, a changed measure or a renamed synonym each write a version with an author and a time. Questions and agents read the published version, and restoring an older one writes a new version, so the history stays complete.
Two routes, one published version at the end of each.
Most teams take the first route. The built-in ontology carries the supply chain objects and the dictionaries behind the mapping proposals, so the first proposals arrive strong. Extending it costs an afternoon for each subject area.
The second route suits a company that already runs a published data model and wants answers in its own terms. The model document describes each object, its attributes and its relationships; Juno takes it as the target and your team confirms the result on the same screen.
Showcase estate.
The team had mapped ZZ_CXL_WDW to the cancellation window attribute of the purchase order line. On Tuesday D. Okafor pointed out that three suppliers agree their window in the contract, by material group, while the ERP field carries the days a buyer typed on the line.
P. Sharma defined a custom object at 11:20: cancellation window, with supplier, material group, days and a valid-from date. Two relationships tied it to the purchase order line and to the supplier. The ontology went to version 4, and the purchase order cancellation policy later read the contract window where one was agreed.
How Juno indexes every table, every column, the values inside them and the words your people use.
The supply chain arrives described; your judgement goes to the parts that are yours.
The usual route to business meaning is a modelling project. A team defines entities, metrics and joins for its own estate, agrees them across departments and maintains them as sources change. Practitioners describe that work in quarters for a large estate.
Juno arrives with the supply chain already described. Your team reads the objects, keeps what fits, and spends its judgement on the parts that are yours: your custom fields, your agreements, your words. The published result is a model your own people signed.
Two routes work. Extend the built-in ontology with your own objects and attributes, or load your own model as the target of the mapping. The review screen confirms either one.
Your objects and attributes sit in their own space with your name on them. A later release of the built-in ontology arrives beside them, and the mapping keeps pointing where it pointed.
It uses its own business vocabulary and keeps documented alignments: SCOR for processes and metrics, GS1 keys for identity, ISA-95 for the plant, and each ERP’s own objects for write-back.
With the objects they are calculated from. One calculation serves ChatLima, the agents and the weekly digest, and the screen names the attributes it used.
Each one builds on the one before it.
Reads your rows in place.
Connect and move ↗One record per real thing.
Master and govern ↗Apps for every decision.
Operate and decide ↗Asks and acts, at your level.
Ask and act ↗Bring two systems and one decision your planners make every week. In the first week we register the data, confirm the mapping with your team, answer your questions in ChatLima and run the first agent at the level you choose.