Mathias Knop

Mathias Knop's public writing circles around one core conviction: real value in digital manufacturing comes from proximity, both to the people who make things and to the technical detail that most vendors gloss over. He returns again and again to frontline operations, whether recruiting for roles "close to the people who actually make things" or spending a day discussing "augmented lean using Tulip Interfaces frontline operations platform" . This is not abstract digital transformation talk. It is grounded in shopfloor apps, MES engineering, and the data backbone that connects PLCs, SCADA, and the digital layer above them .

That same insistence on substance over hype shapes his view of the Unified Namespace debate, which he calls "easily the most discussed topic in digital manufacturing in Europe right now" . He is skeptical of the marketing gloss around it, pointing out that "the UNS reference architecture never included standards" and that adopters are "entirely dependent on your integrator" . His account of how he arrived at this position is personal and specific: a customer once handed him a UNS flyer and said "This is what I want," and after years of connecting systems point to point, "it clicked immediately" . He treats MQTT not as a buzzword but as plumbing worth explaining properly, breaking down its publish-subscribe model, its three Quality of Service levels, and features like the retain flag as the actual mechanics that make a unified namespace work ¹¹. In his framing, getting "edge data structured and contextualized at the source is where so man[y projects succeed or fail]" , which is the same instinct that drives his suspicion of "raw tag dumps nobody can interpret" and "the cloud bucket full of cryptic PLC telemetry your IT team is so proud of" .

Partnerships, in his account, are earned through work done before any contract exists. Announcing the Litmus partnership, he writes "Some partnerships get signed. The good ones get earned first," describing years of hands-on experience and joint architecture work that preceded the paperwork . He frames the resulting Litmus Edge rollout, starting with an Energy Management use case across European sites, as proof that "this isn't us learning on the job" but "the moment where preparation meets a real, measurable business case" . He states his philosophy directly: he does not believe in "two companies agreeing to 'explore synergies'" but in "two teams who already know how to deliver together, stepping into a project with confidence" . The same emphasis on relationship over transaction shows up in his reflection on time spent with Canary Labs partners, where he credits the historian technology but adds "your approach is the real secret ingredient if you ask me," and stresses that "meeting up in-person, spending time together, and sharing stories and experience" is what makes collaboration work .

Knop is also explicit about growth and geography as deliberate choices rather than incidental facts. Expanding into a new flex office in Hasselt, he frames it as reducing "unnecessary travel time" for staff and strengthening regional presence so the company stays close to both people and customers, noting Coretecs now operates from four active locations: Kontich, Ghent, Leuven, and Hasselt . He ties this to a broader belief in Belgian industrial capacity, arguing on Belgian National Day that the country "is a serious force, and it's built on something hard to replicate," pointing to academics working with private industry, port infrastructure, a skilled labor pool, and companies "deeply local while being fully global" . His summary line, "This is not a country that only does services. We build things, and we build them well" , reinforces the same theme that runs through his hiring posts and partnership announcements: industrial substance matters more than image.

On emerging technology adoption, his stance is pragmatic and impatient with hesitation dressed up as caution. Describing his own experience letting a car drive itself, he notes that what surprised him "wasn't the technology" but "how fast my instinct to control everything started to feel outdated" . He draws a direct parallel to manufacturing, where he hears the same objections weekly: "What if the model gets it wrong?" and "We'll wait until the AI is more mature" . He is careful to note the qualifier in Belgium's approval of Tesla's supervised self-driving, stressing that "the human is still responsible" and that "the system handles the routine, the person handles the exception" , which suggests his takeaway is not blind automation but a recalibrated division of responsibility, the same logic he applies to digital OT roles evolving beyond traditional DCS and PLC work into platforms like Ignition .

Taken together, his recurring message is that digital manufacturing progress is won through groundwork rather than proclamations: technical fluency in the plumbing (MQTT, edge contextualization), partnerships proven before they are announced, and a willingness to let systems take on routine control while people focus on exceptions. The concrete takeaway for readers is that credibility in this space is built the same way in every domain he writes about, whether hiring, partnering, or adopting new technology: put in the hands-on work first, then talk about it.