Overview
Mathias Knop is a co-founder of Coretecs, a company he started in June 2022, and is based in Asse. Since April 2021 he has also been the owner of DX Consulting. His stated areas of expertise are IT/OT architecture, industrial digital transformation, smart manufacturing, solution architecture and the Industrial Internet of Things.
He worked at Yokogawa across two periods, first as an application engineer from July 2017 to August 2020 and as international lead business analyst from January 2019 to August 2020, then as a solution architect from April 2021 to May 2022. Between those spells, from August 2020 to April 2021, he was a business manager at ALTEN BELGIUM.
Knop studied at the Vrije Universiteit Brussel, where he completed a Bachelor of Science in applied engineering, electronics-ICT, from 2014 to 2017, followed by a Master of Science in applied engineering, electronics-ICT: networks, in 2017 and 2018.
Career history
Insights & ideas
The through-line
Across these posts, Mathias Knop keeps returning to one idea: raw, disconnected data is worthless until it is structured, contextualized, and put in the hands of people who actually understand a shop floor. He describes years of "connecting A to B, then to C. Always point-to-point" [6] before arriving at the Unified Namespace approach, and he frames Litmus, MQTT, and edge platforms as tools to fix that fragmentation rather than as ends in themselves [3][6][11]. Over the period covered, this preoccupation with structured data has widened into a broader stance on trust and adoption: he draws an explicit line from letting a car drive itself to letting a model run routine decisions in a factory, arguing that hesitation about automation is a psychological hurdle more than a technical one [10]. The through-line moves from "how do we architect the data" to "why won't people trust the systems we've already built."
On Unified Namespace and data architecture
Knop treats Unified Namespace as the most important and most misunderstood architecture pattern in European manufacturing right now: "Unified Namespace. Easily the most discussed topic in digital manufacturing in Europe right now" [6]. He is candid that the promise outpaces the standard: "the UNS reference architecture never included standards. You are entirely dependent on your integrator" [6]. His goal is data that is "contextualised and ready to consume, not the raw tag dumps nobody can interpret" [6], and he ties this directly to business outcomes: "Getting edge data structured and contextualized at the source is where so man[y projects succeed or fail]" [3]. His explainer work on MQTT reinforces this, breaking down how the protocol's broker and Quality of Service levels are what actually make a unified namespace function in practice [11].
On partnerships
Knop is explicit that he values proof over paperwork in how Coretecs works with vendors. Announcing the Litmus partnership, he wrote: "Some partnerships get signed. The good ones get earned first" [3], noting the companies had been "building up hands-on experience with the platform, sharpening our joint approach, and proving out the architecture well before any paperwork" [3]. He states his model directly: "Not two companies agreeing to 'explore synergies,' but two teams who already know how to deliver together, stepping into a project with confidence" [3]. The same logic shows up in his account of a Canary Labs visit, where he credits the relationship itself, not just the product: "The Canary Labs historian is great, but your approach is the real secret ingredient if you ask me" [5], and he underlines the value of face time: "it stresses the importance of meeting up in-person, spending time together, and sharing stories and experience" [5].
On trust in automation
Reflecting on supervised self-driving, Knop maps his own experience onto the resistance he hears in manufacturing. He notes his own surprise: "What surprised me most wasn't the technology. It was how fast my instinct to control everything started to feel outdated" [10]. He then lists the objections he hears from customers almost verbatim to the ones about self-driving cars: "What if the model gets it wrong?" "What about keeping a human in control?" "We'll wait until the AI is more mature" [10], concluding "The parallel is almost too perfect" [10]. He is careful to note the guardrail still matters, pointing to the word "supervised" and the idea that "the human is still responsible" [10].
On Belgian industry and growth
Knop frames Coretecs' growth as inseparable from finding people, not just closing deals: "Growing a company means one thing above all: finding the right people" [1]. He connects this to a regional strategy, expanding office presence "to being closer to our customers and reducing unnecessary travel time for our people" [7]. His pride in the broader ecosystem is explicit: "We have a complete ecosystem here" [2], and he pushes back on a narrow view of the Belgian economy: "This is not a country that only does services. We build things, and we build them well" [2].
Takeaways
- Unified Namespace only works if buyers understand it has no built-in standard and success depends heavily on the integrator's architecture choices [6].
- MQTT's value in a UNS comes from the broker and its Quality of Service levels, which determine whether message delivery is best-effort or guaranteed for critical operations [11].
- Knop prioritizes vendor relationships with prior hands-on, proven track records over newly signed partnership agreements, as seen in the Litmus rollout [3].
- In-person time with partners (e.g., the Canary Labs visit and roundtable) is treated as a deliberate relationship-building tactic, not just a nicety [5].
- He argues that resistance to AI/automation in manufacturing mirrors public hesitation about supervised self-driving cars, and that "supervised" systems keeping humans responsible is the practical bridge to adoption [10].
- Coretecs' growth strategy pairs hiring across specific technical roles (MES, industrial software, digital OT) with expanding regional offices to stay close to customers [1][7].
Media & appearances
- CoretecsYouTubeMQTT, the silent power behind Unified NamespaceMathias Knop discusses how MQTT is a publish-subscribe messaging protocol that enables the unified namespace by allowing devices and applications to communicate efficiently through a broker that routes messages to subscribed clients. He explains MQTT's three Quality of Service levels that determine message delivery guarantees, ranging from at-most-once delivery to exactly-once delivery for critical operations, and describes additional broker features like the retain flag.
In the news
- A folder of PDFs and Excel checklists went in. Thirty minutes later, a full production system was on screen. The most important comment came after. That was the live demo on day 1 of Tulip Interfaces Operations Calling, the first edition in Europe. Starting from the kind of document folder every plant hands you in week one, the Tulip team built a shop floor layout, a data model and two working apps with AI, live on stage. When asked what the hardest part was, the answer wasn't the tooling. It was that the folder contained no
- Off to Lyon for Tulip Interfaces Operations Calling Europe. Sold out, so it's going to be a full house. What I'm most curious about: how manufacturers are moving composable MES beyond the first apps. Because a frontline app is only as strong as the data underneath it. That's where most projects stall, and where the UNS makes the difference. Adrien Bousez, Brecht Van Boven, pierre malochet and I are there both days. Talking architecture, scaling across sites, or just a coffee between sessions? Send me a message and we'll find a
- A frontline app is only as good as the data it runs on and the systems it talks to. That's why composable MES isn't just about building apps. It's about connecting what happens on the shop floor to machines, historians, ERP and the rest of your IT/OT architecture. On 3–4 November, Mathias Knop, Adrien Bousez, Brecht Van Boven and pierre malochet are heading to Lyon for 𝗢𝗽𝗲𝗿𝗮𝘁𝗶𝗼𝗻𝘀 𝗖𝗮𝗹𝗹𝗶𝗻𝗴 𝗘𝘂𝗿𝗼𝗽𝗲: two days of customer stories, hands-on workshops and conversations about the future of frontline operations.
- Tired today, but looking back at ABISS 2026 with a lot of satisfaction. Standing on stage next to your customer is something completely different from presenting about them. Together with Tom Vergote from Unilin, I shared the story of our Unified Namespace journey across a multi-site organisation. Not the polished version, but the honest one: the architecture choices, the governance questions, and the lessons we learned along the way. The conversations afterwards confirmed something I keep seeing. The hard part of scaling isn't
- We’re live at #ABISS today! Let’s talk about what it really takes to scale IT/OT across your organisation. From connecting machines and making industrial data available, to building architectures that can be standardised and rolled out across multiple production sites. And if you want to see what that looks like in practice, join our session with Unilin: From point-to-point chaos to Unified Namespace: The IT/OT-Journey of Unilin 🕦 11:45–12:05 📍 Learn Hub We’ll share how Unilin went from its first UNS pilots to a standardised
- In bijna elke fabriek die we binnenstappen zit hetzelfde verborgen probleem: point-to-point spaghetti tussen machines en applicaties. Morgen op ABISS ontwarren we die. Live, op stand 90. → Untangle, onze IT/OT-game van 2 minuten. Maak van de spaghetti een Unified Namespace en klop onze teamscore van 3 600. → 11:45, Learn Hub 1: samen met Tom Vergote vertel ik over de IT/OT-journey van Unilin. Het echte verhaal, ook de moeilijke stukken. → Wat is er nieuw in Ignition 8.3, en een eerste blik op Ignition 2027. → Vier
- Every manufacturer I talk to wants Industrial AI. Very few have the data foundation to make it work beyond one pilot. That's why these two days at the Litmus Launch Workshop in Brussels, together with Steven Cox, felt so relevant. The question on the table wasn't which AI model to pick. It was how you build industrial data infrastructure that scales across lines, plants and teams, so the second, third and tenth use case don't each start from zero. That's exactly where our customers are putting their priorities right now. Less
- How do you move from point-to-point complexity to an IT/OT architecture that can scale across a multi-site organisation? That's the journey Unilin has been working on together with us. With 𝟯𝟱 𝗽𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻 𝘀𝗶𝘁𝗲𝘀 𝘄𝗼𝗿𝗹𝗱𝘄𝗶𝗱𝗲, Unilin had an IT/OT landscape that had grown organically over time. Point-to-point integrations, significant differences between plants and no shared reference architecture meant that the existing approach was reaching its limits. So rather than simply adding another technology to the stack,
Related profiles
This page shows public professional information only, each fact cited. Is this you? send a correction, or ask for removal within 24 hours, no questions asked.