Standard workflow
Most routine questionsQuestions that repeat every month follow the order written in the manual.
Example questions“What was line A’s yield yesterday?” / “What was last week’s average hourly rate?”
DARVIS · agentic workflow · week 3
Ask in one line and it passes through five stages to an answer that carries its evidence.
That flow is designed by our consultants, and the AI assistant works through it in order.
How it works
A step-by-step flow a consultant assembled from interviews with your veterans. The veteran’s instinct is not erased; we ask when it forms and what would make it wrong, then write that down as rules.
Written in business language, so it can be reviewed without any IT knowledge.
First, whether a close metric has left its usual range.
What it emitsList of flagged metrics→ into QUERY input
A plain-language question comes in, the data map (the ontology) is read as context,
and the right one of four tools is called.
Tables, charts and a summary — and every answer cites its evidence automatically.
If the evidence is thin, it doesn’t answer.
How does it run?
First we agree which metric moving out of range counts as a real problem.
with ConsultantYou receive the step-by-step manual and simply review it. No IT knowledge required.
with ConsultantThe manual you reviewed becomes the analysis steps as written. Nothing for you to build.
with AI engineerAn AI that reads your data map starts taking questions in plain language.
with AI engineerFour tools are attached — query, search, forecast, connect. Which one to use is the AI’s choice.
with Built into DARVISQuestions that repeat every month follow the order written in the manual.
Example questions“What was line A’s yield yesterday?” / “What was last week’s average hourly rate?”
For unknown problems with no manual, it explores the data map on its own — and a person reviews what comes back.
Example questions“Why is the margin wobbling this month?” / “I can’t tell what’s causing it”
The two questions that come first
A general AI doesn’t know your company. DARVIS works on your data map, and every answer arrives with its evidence.
| DARVIS | General AI | |
|---|---|---|
| Your company’s context | Takes your data map — equipment, materials, process relationships — as context | Doesn’t have it |
| Citing evidence | Every answer shows the table, row count and dates | Absent or unreliable |
| Tool use | Calls only the tools it is given (Text2SQL · RAG · AutoML · MCP) | The LLM answers directly |
| Data leaving | Nothing sent outside. Runs on your own servers | Sent to an external server |
It sits at a different layer. DARVIS is a layer on top, so it runs over whatever you have underneath. Leave your ERP and MES exactly as they are.
They ask in plain language and get an answer
The foundation that stores and processes data at scale
Where your operating data comes from
Whatever you choose for infrastructure, this goes on top of it.
Frequently asked questions
The ontology this screen reads
A question like “which products are heading for a stock-out, and what do we do” doesn’t end at one table. The answer comes from following relationships — product to inventory, inventory to orders and suppliers. That chain of relationships is what the workflow takes as context.
Entities in play — Product · Inventory · Supplier · Order
What an ontology is →Choose a stage
Back to the DARVIS overviewNext step