Nobody can say what the system really does.
A decade of rules, exceptions and workarounds that nobody wrote down. Orlian reads the code, screens and database first, writes every rule down and flags what it can’t verify.
RulesEMS & SCMS Summit 2026· Munich · Stand 16
Up to 90% less project cost*, from requirement to production.
Orlian is our AI SDLC platform. Specialist AI agents carry a software project from the first requirement to production. A named person approves every hand-off, and one ID traces each change back to the goal it serves. Come and see it run on a real project at stand 16.
- From requirement to production
- A person at every gate
- Your servers, your AI model
*Up to 90%: tested and verified on real, independent application development. Results depend on the project’s scope, codebase and starting point.
We’re speaking · EMS Summit 2026
Do your systems own you, or do your processes own your systems?
Put the process back in charge, without ripping out your systems.
Marcelo on why the licence isn’t the real lock-in, and how to screen every platform as keep, connect or replace before your next renewal.
Wed 4 Nov12:50–13:20Room 1
Subject-matter expertMarcelo Navarro
Can’t make the session? Bring one platform to stand 16 →25+ years in international manufacturing across CNH, ZF, PepsiCo and Jaguar Land Rover, on the side of the table that signs off the spend.
The argument, in three beats
The licence isn’t the lock-in. Not knowing your own rules is.
Most manufacturers have renewed a platform because leaving felt riskier than paying. Three things keep a system in charge of the process, and none of them is the licence.
Everything downstream reads from it.
Reports, ERP, planning and pipelines. A rebuild has to serve every one of them exactly the same, or it creates a second truth. Orlian proves each rule, requirement by requirement, before cutover.
One truthRebuilding by hand used to cost more than years of licence.
So the renewal was signed again. Orlian takes up to 90% off the project cost, with a named person signing every gate, which is what finally makes the exit case add up.
Goal · LiveRead what you have. Prove every rule. Replace only what earns it.
How Orlian works
Seven wings, one red thread, a person at every gate.
Seven wings of specialist AI agents carry your project from the first requirement to production, and keep watching it after. A person approves every hand-off, and one ID ties every change back to the goal it serves, so the savings never cost you control.
Up to
90%*less effort and cost20specialist agents in 7 wings
5human gates, each signed and timed
Governedend to end, every action logged
The seven wings01 · Analyze3 agents02 · Plan5 agents03 · Build3 agents04 · Stage2 agents05 · Verify3 agents06 · Release1 agent07 · Operate3 agents
Where a person signs
- 1Analyze → Plan
Your team confirms it matches reality
- 2Plan → Build
You approve the requirements
- 3Build → Stage
An engineer approves every change that matters
- 4Stage → Verify
Readiness: live, migrated, smoke-tested
- 5Verify → Release
A person accepts the test evidence and signs the release
Every approval carries a name and a timestamp, for you and for your auditors. Errors in production come back to Build as new work, and go through the same gates.
We should talk if you have
Three reasons to stop by stand 16.
Bring the system you are thinking of rebuilding. We open Orlian on a real project and show you where a person approves, and what the record shows afterwards.
A legacy system nobody understands
Orlian reads the code, screens and database first, and flags what it can’t verify.
Code that can’t leave your building
It runs on your own servers, with the AI model you choose.
Auditors asking who approved what
One ID traces every change from goal to production. Every approval is signed and timed.
- Runs on your own servers, with the AI model you choose. Your code stays yours.
- Production is read-only by default. Patches ship only on approval.
- Every action is logged with actor, timestamp and correlation ID.
- Threats are modelled at design time, and every change gets security scanning.
- ISO/IEC 27001:2022 certified delivery, audited by TÜV Rheinland.
The red thread
One ID, from the goal to the running system.
When something breaks, Orlian tells you which requirement it violates, and which business goal is at risk.
- OBJ-0001goal
- BRQ-0014requirement
- #162ticket
- PR 250code
- AI-004test
- RC 1.4.0release
- ISS-0042prod error
Without the thread
Validation error on table 87.
Someone now has to find out which rule broke, and why it exists.
With the thread
Violates BRQ-0014, which realises OBJ-0001.
The rule, the goal at risk and the person who approved it, in one line.
Der rote Faden: the thread that runs through everything.
From Marcelo’s session
Screen every platform: keep, connect or replace.
Bring one platform to stand 16 and we will put it through the screen with you.
KeepConnectReplace
Licence and run costFair for what it doesFine; the process around it isn’tRising, used or not
Customisation depthMostly standardStandard core, side workaroundsDeep: your rules, not theirs
Where your rules liveInside the platform, documentedIn email and spreadsheetsDeep in vendor configuration
What the business getsA reliable system of recordLate, partial informationYour own logic, rented back
Where this usually starts
Bring the system, not the use case.
You don’t need an AI idea. You need the system that costs you every day. These are the ones we see most often on a plant’s list.
A legacy system nobody understands
Built years ago, documented badly and owned by one person. Orlian reads it first and writes down what it really does.
Starts with a readA platform renewal you’d rather not sign
The licence keeps rising, used or not, and your own rules are rented back to you from vendor configuration.
Keep, connect or replaceThe MES add-on stuck on the list for years
Or the supplier portal. Ideas that never got funded because the build estimate was too high.
Often the surpriseA large OutSystems estate nobody has scoped
Where the real question is what genuinely has to be rebuilt and what can simply be lifted.
Starts with a mapSomething else? That is fine. Name it and we will tell you honestly whether to keep, connect or replace it, including when the answer is keep. Name one system →
Who you will meet
Four of us, at stand 16 on both days.
Not a sales team. The people who would run the work on Orlian, so the conversation on the stand is the conversation you’d have on the project.
Venkat Ramakrishnan
Talk to Venkat about the business case: the system that never got funded because the build estimate was too high.
LinkedIn →Prasobh Veluthakkal
Talk to Prasobh about how a requirement becomes production code on Orlian, and where a person signs off.
LinkedIn →Marcelo Navarro
25+ years signing off the spend in international manufacturing. Talk to Marcelo about the platform renewal you’d rather not sign.
LinkedIn →Kai Hackbarth
Twenty-five years in industrial IoT, much of it at Bosch. Talk to Kai about the legacy plant system you can’t afford to replace the old way.
LinkedIn →If you would rather not book anything, come by stand 16. We are on the floor both days.
The ask · See it on a real project
Name one system. We’ll tell you whether to keep, connect or replace it.
Thirty minutes, no slides. We open Orlian, pick a live project and walk the thread with you: how a requirement becomes code, where a person approves, and what the record shows afterwards. Bring a system you are thinking of rebuilding.
EventEuropean Manufacturing & Supply Chain Summit
Stand16
VenueHoliday Inn Munich City Centre
Dates3–4 Nov 2026
European hours · no deck · a working conversation