Skip to content
MORDANEGROUP

The system

One model of your operation. One layer that runs it.

The Operational Model captures how your workflow actually runs. The Control Layer shows what is stuck and what has to happen now. Together they form a layer above your existing systems. Not a replacement, not a migration.

01 · The Operational Model

Your workflow as objects, not departments.

Your systems know articles and bookings. Your workflow knows more: a quote that has been open too long, a supplier that hasn't confirmed, a deadline that quietly slips. The Operational Model captures that reality.

Every object has an owner, a status and a deadline. Every relation is explicit. A question like 'which orders are at risk through one supplier' becomes a lookup, not a round of phone calls.

The objects in quote to delivery

Customerwho is asking, who is waiting, and what they are used to
Quotelines, margin, status, and how long it has been open
Orderthe promise made to the customer, with a date and an owner
Supplierwho has to deliver and whether that is confirmed
Deliverywhat actually arrives, when, and what is running late
Ownerthe one person whose move it is right now
Deadlineevery date that has been promised anywhere
Actionthe next concrete step, and who executes it
Operational Model · quote to delivery
CUSTOMERMolenberg Staal BV
owner: T. Molenberg
QUOTEQ-2417 · 18 lines
status: sent
ORDERO-8823 · confirmed
deadline: May 21
SUPPLIERHexa Metaal
confirmation: open
DELIVERYplanned: week 21
risk: 4 days late

NEXT ACTION

Call Hexa Metaal: confirm date

awaiting human approval

02 · The Control Layer

See what is stuck. Decide. Act with approval.

The Control Layer reads the model and puts three verbs on top. See: every order standing still, every confirmation that hasn't come in, every deadline about to break. Decide: AI summarizes the situation and proposes the next action, with the reasoning attached. Act: a person approves, and only then does the message go out or the order change.

Your team works from one view instead of six tabs. No more searching for what is going on. Only deciding what happens.

Control Layer · quote to delivery · todayAI proposal · awaiting approval
OrderCustomerStatusOwnerDeadlineNext action
O-8817Berkman BVin productionJ. SmitMay 28no action needed
O-8823Molenberg Staalwaiting on supplierT. MolenbergMay 21call Hexa: confirm delivery date
O-8831TechnoFluidquote sentT. MolenbergMay 23follow up: no reply in 6 days
O-8834Halewijnready to shipJ. SmitMay 20book transport

03 · The boundary

The boundary is a design decision, not a disclaimer.

AI here is fast, tireless and good at summarizing. People here are accountable. So the division of roles is built into the system, not promised in a policy document.

AI does

reads every object and relation

summarizes what is going on

drafts messages and orders

recommends the next action, with reasoning

AI never

sends anything on its own

changes an order, price or schedule

executes an action without approval

Map one critical workflow.

Within twelve weeks a control layer runs on your workflow. The first step is one working session: your workflow on the table, the model drawn live. The map is yours.