A question about open purchase order lines reaches three systems: the orders in SAP, the orders of an acquired division in Oracle, and the weekly plan in a planning suite.
Two things travel: the query out to each system, and the result back.
A question arrives from ChatLima, from an agent run or from a report. Juno recognises the business objects in it: purchase order lines, a plant, a week, a value. The mapping made at the Map stage says which table in which system carries each one.
From that, Juno writes a query plan: the tables to read, the filter for each source, the keys that join the parts and the order of the work. The plan is kept with the answer.
Each source then receives a query in its own language, holding the narrowest filter Juno can state: one plant, one week, open lines only. The source runs it with its own indexes and returns a small result.
The federated query engine matches the parts on the shared keys, applies the row and column rules of the person asking, and presents the result. Every row stayed in its own system; the query and the result travelled.
One line per step, with the source, the filter, the result and the time.
| Step | Where it runs | What it reads | What comes back | Time |
|---|---|---|---|---|
| 1 · Read and plan | Lima | the ontology, the mapped tables and the filters | a query plan | 1.9 s |
| 2 · Open lines | SAP S/4HANA | EKKO · EKPO · EKET, plant 1210, open lines | 26 rows | 1.8 s |
| 3 · Open lines | Oracle Fusion | purchase order lines of the acquired division | 12 rows | 1.4 s |
| 4 · Cover | Planning suite | planned orders and demand for 38 materials | 38 rows | 0.9 s |
| 5 · Join | Lima federated query engine | matched on material, plant and supplier | 38 rows | 0.3 s |
| 6 · Access and present | Lima | row and column rules for L. Tan, supply planner | 38 rows | 0.2 s |
Steps 2, 3 and 4 run at the same time, so the longest of them sets the reading time. Showcase estate.
The plan is the audit record of an answer. It names each source, the filter sent to it, the rows it returned and the time it took. When an auditor asks where a number came from, this is what answers.
Response time comes from how much each source is asked to do, and from how much of the work runs together.
Reading in place is the default; a copy earns its place for history, for slow sources and for heavy repeated reads.
The read mode belongs to the data set, and one project can hold all three: read in place, a governed copy in your lake, and a file drop or a stream. Your team sets the mode when the data set is registered and can change it later.
Reading in place gives the state of the source at the moment of the question. A governed copy gives a fixed refresh, a steady response time and years of history in one place. Either way the ontology, the access rules and the audit record stay the same.
Showcase estate.
L. Tan asked ChatLima which open purchase order lines she could still cancel this week, and what they were worth. The purchasing data for her plant sits in SAP; the acquired division’s orders sit in Oracle Fusion; the cover for each material comes from the planning suite.
Juno read the question, found the mapped tables for each system, and sent one query to each with the plant, the week and the open status in the filter. SAP returned 26 lines, Oracle 12, the planning suite the cover for 38 materials. The engine joined them on material, plant and supplier, applied L. Tan’s access rights and presented 38 lines worth $412,000 in 4.2 s, with the query on show.
What a sync scan finds when a column is added, a table is renamed or a field goes away, and what happens to the mappings and rules that depend on it.
The effort moves from moving data to describing it.
The common route to a cross-system answer is a central copy. Every source gets a pipeline, the tables land in a warehouse, a modelling layer gives them meaning, and the question is answered from the copy. Each new source adds a pipeline to keep current, and the answer is as fresh as the last load.
Juno asks the systems directly and keeps the description, the mapping and the plan. A new source becomes answerable once it is registered and mapped. Where a copy serves the work better, Quanta lands a governed one under the same rules.
Any registered data set in the project is available to a question. In the showcase estate three systems answer a typical planning question; production estates connect more than 40 source systems.
Juno returns the parts it has, names the source it is waiting for and shows the time of its last good read. The person decides to wait for the full answer or to work with the parts that arrived.
Lima keeps the description of each table, the query plan and the record of each run. Rows are read for the question at hand and go to the person who asked. A governed copy lands in your own lake when your team chooses that mode.
Yes. An agent run reads through the same engine, with the same mapping and the same access rules. The rules engine evaluates its conditions on the rows that come back and records the plan with the run.
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.