Your lines talk. We listen.
Your software engineering team for machines, data and AI. We connect your lines, make data usable and build tools your operators actually use.
Ask Vlegel
We build the digital engine for the physical world.
No one-off jobs, no hefty reports. A dedicated team that knows your machines, your people and your data. Close by: based in Genk.
Is there a machine, a line or a warehouse at the other end? Then let’s talk.
01 · Who we work with
Three worlds. One dedicated team.
Your software could look like this.
Screens that operators, service engineers and managers actually use.
Pattern occurs just after format changeover. Sensor S-14 reports misalignment.
- [PLC] tag vibration_drive normalised
- [MES] order 24-1187 started
- [Operator] shift B logged in
- [Datalaag] 1.284 tags synchronised
Analysed 8 hours of data ›
Guide G2 is set 1,5 mm too wide after changeover. Suggestion: add a check to the operator checklist.
Example screen with fictional data. This is what software we build for you could look like.
What we do.
Six verbs. From the sensor to the boardroom.
- 01
Connect.
Machines, sensors and lines talk to each other.
> PLC → OPC UA → MQTT → UNS
- 02
Collect.
One Unified Namespace (UNS). Every tag has a place and a name.
> site/line3/oven/temp
- 03
Understand.
A semantic model gives your data meaning, from operator to boardroom.
> OEE at a glance.
- 04
Predict.
Through an MCP-server, AI reads your data, never your control system. That way, AI spots anomalies before things go wrong.
> Vibration rising. Schedule maintenance.
- 05
Control.
Machines and processes do what they’re meant to do.
> Recipe loaded. Line starting.
- 06
Protect.
Secure, up to date and quick support when something goes wrong.
> Patch deployed. Zero downtime.
> PLC → OPC UA → MQTT → UNS01/06
AI with both feet on the shop floor.
- 1
AI never controls a machine directly.
- 2
The data layer (UNS + MCP-server) is the wall between AI and your process.
- 3
A human always signs off.
- 4
No chatbot talking without supervision.
How we work.
First we get to know each other. Then we build. Just like in real life.
- 01
Date
An on-site scoping session or workshop. Do we click?
- 02
Engagement
A short, focused project on one line or machine.
- 03
Marriage
Your dedicated team. The same faces, every week.
- 04
Maintenance
We stick around. Updates, support and improvements.
Real people. Not AI.
Engineers, developers and data people who like being on the shop floor. No account managers between you and the people writing the code.
Frequently asked.
+What does Vlegel do?
Vlegel is your software engineering team for machines, data and AI. We connect machines, make their data usable and build software and Industrial AI on top.
+Who does Vlegel work for?
Factories, production lines and machine builders, from our base in Genk. Mainly in Flanders, Wallonia, the Netherlands and western Germany.
+How are you different from a consultant or IT agency?
We don’t hand over a report and disappear. We become your dedicated team, there to keep building, maintaining and improving.
+How do we get started?
With a 15-minute chat with Jorg or Yannic. Then comes a Date of around two weeks, with a working result.
+What are a UNS and an MCP-server?
A Unified Namespace (UNS) puts all machine data in one place, with one logical naming structure. A semantic model gives that data meaning. An MCP-server lets AI and tools query that data securely, with read-only access.
+Do you use AI on our machines?
Only where it adds value, and never directly in the control system. A human always decides.
15 minutes. No slides.
Tell us about your machine, line or warehouse. We’ll be honest about whether we can help.
Rather call? +32 89 39 35 46