Chapter 5 followed one agent from a Friday sentence to confirmed cancellations on the Monday.
The purple arrows in the picture above are this path; the rest of the chapter follows it stage by stage.
One morning of registration gives every later stage the same tables.
Registration is how a table becomes something Juno can query. A. Novak, the data lead, picks a connector, gives the connection and chooses the tables; S. Iyer, the IT architect, sets up access and security. Juno keeps the names, types, keys and a sample of values; the rows stay in the source. Data registration
On the Monday of the first week, at 09:10, A. Novak opened read connections to SAP S/4HANA and Oracle Fusion. By noon the estate held 23 tables from five systems; the agent’s purchase order lines came from EKPO in SAP and PO_LINES_ALL in Oracle. Data in place
The stage that answers the question chapter 5 left open.
Chapter 5 closed on the agent reading purchase order lines from SAP and from Oracle and treating them as one thing. This is where that was settled. The supply chain ontology is Lima’s built-in map of supply chain things and how they relate: materials, plants, suppliers, purchase orders and their lines, stock, demand and their measures.
Mapping attaches your columns to that map. EKPO.MENGE in SAP and PO_LINES_ALL.QUANTITY in Oracle both became the ordered quantity of one object, the purchase order line. From then on a question, a policy and an approval queue all name that object. The ontology model
| Where it is held | What the field is called | What it means there | Ontology attribute |
|---|---|---|---|
| SAP S/4HANA | EKET.EINDT | The date the buyer asked for on the schedule line | Requested delivery date · schedule line |
| Oracle Fusion | PO_LINE_LOCATIONS_ALL.PROMISED_DATE | The date the supplier promised when the order was placed | Promised delivery date · purchase order line |
| Supplier portal | CONFIRMED_SHIP_DT | The date the goods leave the supplier’s dock | Supplier confirmed ship date · supplier confirmation |
One business word, three meanings. The ontology keeps them apart as three attributes, each with its own definition, and the cancellation policy names the one it tests. Showcase estate.
| Registered column | Ontology attribute | Confidence | Status | Why Juno proposed it | |
|---|---|---|---|---|---|
| EKPO.MENGESAP · 12,000.000 | → | Ordered quantityPurchase order line | 98% | confirmed · A. Novak | standard SAP field · numeric with a unit of measure |
| PO_LINES_ALL.QUANTITYOracle · 500 | → | Ordered quantityPurchase order line | 95% | confirmed · A. Novak | standard Oracle field · same value shape as EKPO.MENGE |
| EKPO.ZZ_CXL_WDWSAP · 21 | → | Cancellation window (days)Purchase order line | 62% | confirmed · D. Okafor | custom field · name suggests “cancel window” · whole numbers 0 to 90 · reviewed 09:20 |
| EKKO.BSARTSAP · NB | → | Purchase order typePurchase order | 71% | adjusted · D. Okafor | proposed as document category · the buyer set it to order type |
| CONFIRMED_SHIP_DTPortal · 2026-09-30 | → | Supplier confirmed dateSupplier confirmation | · | added · A. Novak | placed below 60% · mapped by hand at 09:42 |
Five of 412 columns. The last column holds Juno’s reason; the status names the person who decided. Showcase estate.
By Tuesday morning Juno had proposed a meaning for 371 of the 412 columns, each with a confidence and a reason. A. Novak opened the queue at 08:30 and confirmed 338 in one action. D. Okafor joined at 09:15, adjusted 33 and settled the custom field that decides the case, the cancellation window, placed at 62%. The team added 41 by hand; version 1 was published at 10:40. Mapping review
Every confirmation and correction is kept as evidence for the next table; Juno also links the same supplier numbers across SAP and Oracle. The published mapping is a version, so the Wednesday question and the Friday policy work from the same meaning. Linking across systems
The stage that changes the week first: the answer arrives while the window is open.
31 open purchase order lines worth $348,000 sit inside their cancellation window at plants 1210 and 1220, and the window closes on Friday 18 September. Two suppliers hold 24 of them.
| Supplier | Lines | Value | Window closes |
|---|---|---|---|
| Delta Fasteners Ltd | 15 | $186,200 | Friday 18 September |
| Brightline Metals SA | 9 | $121,300 | Friday 18 September |
| 4 other suppliers | 7 | $40,500 | Friday 18 September |
SELECT s.supplier_name, COUNT(*) AS lines, SUM(l.open_value_usd) AS value FROM ontology.purchase_order_line l JOIN ontology.supplier s ON s.supplier_id = l.supplier_id WHERE l.status = 'OPEN' AND l.cancel_window_end >= CURRENT_DATE AND l.projected_excess_weeks > 8 GROUP BY s.supplier_name ORDER BY value DESC
Five steps sit between the typed sentence and the answer. ChatLima recognises the intent and the business objects, frames the goal and finds the tables mapped to those objects. It writes the query across one source or several and runs it with the asking person’s access. The answer carries its working: the terms, the systems, the time and the query. From a question to the right query
The object in the query is the same purchase order line the agent acts on, with the same cancellation window and projected excess. A person asking and an agent acting read one meaning, so the Wednesday answer, that week’s 31 lines, and the Monday drafts, the 38 lines the push-out left, agree on what a line is. ChatLima has been in production since 2023.
Vocabulary is one half of teaching; feedback on answers and on drafts is the other.
| Term | What it means in this company | Kind | Added by | When |
|---|---|---|---|---|
| NCNR | Non-cancellable, non-returnable: a line the supplier holds to the agreed date | Acronym | D. Okafor · buyer | Thu 09:00 |
| LT fence | Lead time fence: the date inside which the plan stays firm | Abbreviation | L. Tan · supply planner | Thu 09:20 |
| “strat supplier” | The strategic class on the supplier record | Alias | P. Sharma · master-data steward | Thu 09:40 |
Three of the 96 entries in the first vocabulary file, which P. Sharma owns and reviews. Showcase estate.
Two Wednesday answers came back wider than expected: the questions used words Juno had yet to learn. On the Thursday three people added three terms in forty minutes: the buyer NCNR at 09:00, the planner the lead time fence at 09:20, the master-data steward the strategic supplier alias at 09:40. As owner of the vocabulary file, P. Sharma reviewed all three. Training
Training ran in the background in six minutes. From then on a typed acronym is understood on the first try. A later version of the policy can say “keep NCNR lines” and the rules engine reads the same definition, and the approval queue uses the buyer’s own words.
The two stages you watched most closely run on the four before them.
Act is the Friday and the Monday of chapter 5. L. Tan’s policy sentence became a five-row planning table, released by J. Ridley as version 3 at A2 with D. Okafor as the named approver. Each morning at 06:00 the Lima Rules Engine runs those rows the same way. On the first Monday 38 lines matched, 29 drafts reached the queue, and each approved cancellation was written back with the ERP’s acknowledgement. Planner Agent · Write-back
Learn is the loop chapter 4 drew. Each decision is stored with the rule version, the facts at that moment, the recommendation, what D. Okafor did and the outcome at day 14. After six weeks the record read 212 drafted, 203 as written, 9 edited, and it carried the level review that moved lines under $25,000 to A3. From the buyers’ behaviour Juno proposed the exclusion j.park approved as version 4. Learning loop · Audit trail
Four public standards supply the process names and identifiers your teams already use.
| Standard | What it covers | Where it shows in the ontology |
|---|---|---|
| SCOR Digital Standard | A process reference model for plan, order, source, transform, fulfil and return, with its performance metrics. | Process names and measure definitions such as the perfect order and cash-to-cash. |
| APQC Process Classification Framework | A common way of naming business processes, used across industries. | The phases and process steps the agent blueprint is organised by. |
| GS1 identification keys | Global identifiers for trade items, parties and locations. | Identity attributes that let one supplier or one location be recognised across systems. |
| ISA-95 · IEC 62264 | The vocabulary of the plant: equipment, material, personnel, operations schedule and performance. | Plant-side objects and the link from a production order to the line that runs it. |
Lima keeps its own business vocabulary and documents where it lines up with each of these, so an auditor can trace a measure back to a public definition.
Two registered systems with their columns mapped are enough for the first questions. Teaching, agents and the learning loop follow on the same data.
Yes. The built-in ontology takes your own objects, attributes and relationships as extensions, and a model of your own can be loaded as the target of mapping. The review screen is the same for both.
Where does the language model sit in all this, and what does it get to see?
Design time and run time, the boundary your row data stays inside, and the record an auditor reads.
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.