Buyer questions

The questions buyers ask, answered straight.

These are the questions an operations, IT or procurement team asks before a first meeting with Aidecis, with straight answers.

Start with scope

Scope

What Aidecis is for, and what it is not.

Aidecis governs consequential supply-chain decisions. It does not run the plant, plan the network or replace the ERP.

Does Aidecis improve OEE, downtime or throughput?

Not directly. Aidecis does not measure equipment effectiveness, schedule the line or control machines. SAP Digital Manufacturing, Siemens Opcenter, Celonis and industrial AI tools do that. Aidecis governs the decisions that follow: who may approve a reschedule, a quality release or an expedite, within which limit, and what the result was. Where a decision affects throughput, its outcome is linked to it in your own measure.

Can it find production bottlenecks and recommend schedule changes?

Not as a planning or scheduling engine. When your APS, your MES or a planner proposes a schedule change, Aidecis compares the feasible options against their downstream effects, asks the production owner to approve, and reads back the change your own system executes. Production rescheduling is one of the decision families; the first focus is procurement and supply-chain decisions.

How does it work with MES, SCADA and machine data?

MES and quality systems can be sources of evidence and the place where your people or systems execute an approved action, which Aidecis reads back. Aidecis is not a SCADA layer and never controls a machine. Machine data enters only as evidence where a decision needs it, as agreed in the data contract for each project.

Does it replace SAP, our planning suite or our MES?

No. It sits on top of them. Your systems stay the systems of record, and Aidecis never writes into them: your people, systems or bots execute the approved action, and Aidecis reads each execution back and reconciles it against the approval.

SAP

How Aidecis meets your SAP environment.

The way in is read-only, and Aidecis never writes into SAP. Governed execution comes later, one action at a time, and only after evidence.

Which SAP environment do you support?

Aidecis is built for SAP S/4HANA. Other SAP releases are checked per project. To start, the assessment uses a read-only extract: purchasing documents and their history, goods receipts and change documents, with stock, production demand and invoice items where a chain is replayed. No connection to a live system is needed.

What happens when we move from SAP ECC to S/4HANA, or to another ERP?

Your decision rules, authority and decision record stay. Aidecis sits above the ERP, so a migration changes the connection, not the governance. That matters now that mainstream maintenance for SAP ECC ends in 2027.

Can you show a real integration with our SAP?

Yes, on your own data. The decision replay assessment replays six months of your purchasing decisions against your policy and delegation of authority, read-only. The public demo runs on simulated systems and a fictional company, and is labelled as such.

How does an approved action reach SAP?

Aidecis never writes into SAP. Your people, systems or bots execute the approved action, and Aidecis reads each execution back and reconciles it against the approval; the decision record points to the SAP document. With enforced control, your own integration checks Aidecis's signed, single-use grant before it executes: without a valid grant, the action does not run. The first governed execution runs in your SAP test system, after a shadow run.

Proof

What you can see, test and check.

Every answer below says what you can see for yourself.

How do founding clients work with Aidecis?

Aidecis works with a small group of founding clients. Founding clients get founding-client terms in exchange for real cases and, if the pilot succeeds, a reference. Every pilot is anchored to one hard measure agreed before it starts, such as disruption response time, premium freight spend or stockout hours.

Can you show a complete decision workflow, from problem to financial impact?

Yes. The demo follows a late delivery to the production order and the customer promise it puts at risk, weighs the options, finds the owner whose limit covers the decision, records the approval and the scoped action, and links the outcome. In a pilot the same chain runs on your own history, read-only first.

What is available at launch?

People, hybrid and bounded bot modes; enforced and observed control; the seven-step workflow from detection to recorded outcome; the decision replay assessment and evidence sprints; and the continuity package with open export, an open-source ledger verifier and escrow.

How do agent-to-agent chains start?

Agent-to-agent chains, where one bot hands off to the next without a person in between, start as a bounded pilot with a founding client, one chain at a time.

Control

How Aidecis governs people, bots and agents.

Two levels of control, and a strict gate before any decision moves from people to bots.

Can one agent hand off to another agent?

Only per chain, never by default. A chain qualifies when the process is closed, every agent in it runs under enforced control, with your integration checking Aidecis's grant before each step, one owner is accountable for the whole chain, a cap limits the total value at risk, every step can be reversed in your own system with a tested procedure that Aidecis records and reconciles, and the release conditions hold on your own replayed decisions. A breach at any step returns the whole chain to hybrid.

What happens when a vendor agent or our MRP writes straight into SAP?

Aidecis observes it. The write is detected from the change records, matched against the actor's registered role and limits, and flagged within minutes when it falls outside them. Observed control does not stop the action. You decide per decision type when an actor moves to enforced control, for example for every write above a set amount.

Do we have to change system permissions to start?

No. You start observed, with no change to write permissions, and measure how often writes fall outside role or limit. That evidence shows where enforcement is worth it.

Commercial

What it costs to start, and to run.

Published, indicative prices, excluding taxes. Implementation is always scoped with you first.

What does Aidecis cost?

A pilot or evidence sprint on one decision type costs €16,000 to €24,000 (10 to 15 engineer days at €1,600). The subscription is €45,000 per year, including the first site and two regions. Implementation is €1,600 per day, scoped separately. There is no per-user fee.

How do we build the business case?

Start from one decision type and one hard measure in your own terms. The calculator on the benefits page uses your own exposure, addressable share and reduction assumptions, net of review effort. It is a scenario estimate, not a savings forecast.

What if we stop?

Every subscription includes the continuity package: export in open formats, an open-source ledger verifier, escrow of the control kernel and gateway, and exit assistance at a published day rate.

Your own question

Ask what is not on this page.

Send us your question, or start with a read-only decision replay assessment on your own SAP history.