Between a typed sentence and a correct answer sit five steps: recognise the intent and the business objects, frame the goal, find the tables your team mapped, write the query for one source or several, and run it with the asking person’s access.
Two steps settle the meaning; three steps fetch the facts.
The first two steps are about meaning. Recognising the intent settles what kind of answer the person wants: a list, a comparison, a cause, a forecast. Recognising the objects settles what the answer is about: components, production orders, plants, suppliers.
Framing the goal makes both explicit. Juno states the measure, the period, the grouping and the filters it will apply, and that statement travels with the answer. A reader who disagrees with the frame can see where it went wrong before looking at a single number.
The last three steps are about data. The knowledge index holds every registered table and column, the values inside each column, and the names your team gave them, so the step from an object to a table is a look-up.
The query is then written against the mapped columns, run through the federated query engine, and filtered by the rights of the person who asked. Juno keeps the question, the frame, the query and the answer, so the same question can be re-run tomorrow and compared.
Telling the four apart keeps a rule from being answered as if it were a measurement.
About a rule the company has set, such as the safety stock policy for a material class.
About a published plan, such as what the cancellation plan will do this week.
About the estate itself: which tables are registered, what is mapped, when a source was last read.
About the business: stock, orders, deliveries, suppliers. Answered by a query over your data.
| Kind of question | Example someone types | Where the answer comes from |
|---|---|---|
| Policy | “What is our safety stock rule for A-class materials at plant 1210?” | The policy register, with the named policy and its version |
| Plan | “What will the purchase order cancellation plan do this week?” | The versioned rule store, with the planning table |
| What Juno knows | “Which tables hold the supplier confirmed date, and when were they last read?” | The knowledge index and the registration record |
| Data | “Which components are short in the next ten working days at plant 1210?” | A query over the registered tables, read in place |
The kind of question is shown on the answer, so a reader knows whether they are reading a rule, a plan, a fact about the estate or a measured figure. Product.
Each phrase in the sentence lands on a business object, and each object on tables your team confirmed.
| Part of the question | Business object it names | Where it is read | What comes back |
|---|---|---|---|
| “components … for production orders” | Production order · component requirement | SAP S/4HANA · reservations and order items | required quantity and date for each component |
| “short” | Stock · open purchase order · supplier confirmation | SAP S/4HANA and Oracle Fusion | stock on hand and receipts due before the need date |
| “the next ten working days” | Production order start date | Planning suite | the working calendar of the plant |
| “at plant 1210” | Plant | all three sources | the same filter applied in every part |
SELECT c.material_id, c.material_name,
SUM(r.required_qty) - SUM(COALESCE(s.on_hand_qty, 0) + COALESCE(p.due_qty, 0)) AS short_qty,
MIN(r.requirement_date) AS shortfall_starts
FROM ontology.component_requirement r
JOIN ontology.material c ON c.material_id = r.material_id
LEFT JOIN ontology.stock s ON s.material_id = r.material_id AND s.plant_id = r.plant_id
LEFT JOIN ontology.purchase_order_line p ON p.material_id = r.material_id AND p.plant_id = r.plant_id
AND p.confirmed_date <= r.requirement_date
WHERE r.plant_id = '1210' AND r.requirement_date <= CURRENT_DATE + INTERVAL '14' DAY
GROUP BY c.material_id, c.material_name HAVING short_qty > 0 ORDER BY shortfall_startsThe query ChatLima wrote for the question in the hero figure, shown the way a reviewer sees it. Table names are ontology names; the engine resolves each one to the registered tables behind it. Showcase estate.
A single clarifying question costs seconds; a silently wrong assumption costs a quarter.
Two dates carry the meaning of “late” in your estate. Which basis would you like?
a. The delivery date you requested on the order. b. The date the supplier confirmed in the acknowledgement.
11 suppliers received goods after their confirmed date in August. Delta Fasteners Ltd carries the largest share of the late lines.
| Supplier | Lines due | Late lines | Late rate |
|---|---|---|---|
| Delta Fasteners Ltd | 162 | 14 | 8.6% |
| Corvid Plastics | 77 | 4 | 5.2% |
| 9 other suppliers | 612 | 10 | 1.6% |
Some words carry two meanings in one estate. “Late” can mean after the date you requested or after the date the supplier confirmed; vendor evaluation often uses a third date kept for statistics. A product that guesses produces a number that looks right and is wrong for half the room.
ChatLima asks one question, offers the readings it found, and keeps the choice for the rest of the thread. When your company settles on one meaning, it is taught once in the vocabulary and the clarifying question stops appearing.
When the registered data reaches only part of a question, Juno answers that part, says which part is missing and names what it would need: in this estate, a source that carries supplier confirmations for the acquired division.
Showcase estate.
L. Tan’s question named open purchase order lines, a cancellation window and a week. Juno framed the goal as open lines inside their window before Friday, grouped by supplier, valued at the open quantity times the net price.
The mapped tables sat in three systems: order lines and windows in SAP S/4HANA, the acquired division’s lines in Oracle Fusion, projected demand in the planning suite. One question became three queries, joined on material and plant, run with L. Tan’s rights on plants 1210 and 1220. The answer arrived in 4.2 seconds with the query one click away.
The same result as a table, a chart or a short narrative, with walkthroughs to re-run it and a route into your reporting tools.
Yes, against the ontology names your team confirmed. The engine resolves each ontology name to the registered tables behind it, so the query a reviewer reads stays in business language.
From the mapping your team confirmed and the knowledge index built at registration. Each business object points at the tables and columns that carry it, with the values profiled for recognition.
The federated query engine sends one query per source, reads each one in place, and joins the results on the keys the mapping recorded. The showcase estate joins three systems in about four seconds.
A person with the right role can open the query, copy it and run it in their own tool. Corrections to the meaning belong in the vocabulary, so every later question benefits.
Juno answers the part it can, states which part is missing and names what would be needed, such as a source carrying supplier confirmations.
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.