Video Illustration: The AI Knowledge Revolution

An Alternative Visual

This is my alternative visual narrative that explores how AI and specifically Agentic AI are fundamentally disrupting traditional manufacturing hierarchies. The video illustrates the "compression" (or collapsing) of the classic Data-Information-Knowledge-Wisdom (DIKW) pyramid, showing how AI now acts as an intelligent intermediary that instantly transforms unstructured "human language"—like deviation comments and work instructions—into actionable operational wisdom

Key themes include:

• Collapsing Complexity: Moving past the rigid, million-dollar data models of the 1990s to a system that understands context like a human.
• Knowledge Flow: Driving multi-site transformation through "Outbound" digital playbooks and "Inbound" frontline innovations.
• Augmented Lean: Democratizing expertise across the entire network so every site becomes both a consumer and a producer of wisdom.

I also talked about it in an interview for Tulip's "Human in the Loop" series.

Behind this is a body of work and a lot of written content that I will publish in the future. As I have written before I am experimenting with different formats to convey the message about composability. 

Stay tuned more content will be coming out in the future!

Agentic AI in Action: What I Learned Experimenting with Operational and Builder Agents

Over the last several months, I’ve been deepening my exploration of Agentic AI within Tulip, applying the concepts I laid out in my Agentic Framework and testing them in real operational scenarios. What started as curiosity has quickly become something else entirely: a recognition that we are opening a fundamentally new chapter in how manufacturing systems are built, operated, and scaled.

As I’ve experimented with both operational agents—those that support frontline teams in real time—and builder agents—those that help design, generate, and improve digital solutions—I am realizing how deep and wide the impact is going to be. The more I explore, the more use cases reveal themselves, and the more explosive the potential becomes. Its much more than I initially thought, and I have been thinking in terms of multi-agent systems for manufacturing since the 90's! Agentic AI (multi-agent systems powered by generative AI) are a much bigger step change than I would have imagined to how we think about creating and running manufacturing solutions.

Let's start with a brief recap. Operational agents extend the capability of the production system realizing digital twin capabilities in ways that introduce reasoning, interpretation, and contextual understanding directly into the work being done on the floor. Builder agents open the door to a multithreaded, parallel engineering process that fundamentally changes the speed and depth at which solutions can be created. It feels less like a “copilot” assisting a developer and more like a coordinated team of SMEs designing solutions - Augmented Lean at hyperspeed!

This combination—augmenting frontline execution while accelerating the design and iteration of digital systems—points to a future where humans orchestrate agent ecosystems rather than manually building every piece of a solution themselves. This brings me to the motivation for writing this post that became clear to me in a recent customer conversation about DCS integration in support of a digital solution for pharmaceutical manufacturing of clinical drugs.

Reimagining Composable Integration with DCS and ISA-88 Through Agentic AI

The question I was asked recently wasn’t the classic “How do you integrate an MES with a DCS?”—that problem has been addressed in many different ways in the traditional architectures. The real question was far more interesting: How do you integrate a Composable MES built on a Frontline Operations Platform with a DCS or other ISA-88 based batch system?

In a traditional MES world this integration immediately triggers a familiar debate about how to partition the recipe across systems, define boundaries of responsibility, and reconcile master data, recipe models and equipment hierarchies. And that debate is almost always constrained—if not outright dominated—by the rigidity of monolithic MES platforms. The architecture drives the discussion more than the operational needs do.

But in a composable environment, the constraints that shaped those historical debates simply don’t apply. Let's look at what happens when you apply a composable, agentic model.

1. Composable Apps Remove the Traditional Constraints

In a composable architecture, apps are not bound to a predetermined master data model or recipe structure. This means that there is no need for recipe model partitioning, no need to replicate equipment hierarchies, no predefined S88 recipe model to map into. 

This flexibility removes the most painful barrier in traditional MES ↔ DCS integration: the structural reconciliation of recipes and equipment models. The DCS can continue using its ISA-88 representations. Tulip apps can represent the process in the most intuitive and useful way. And the integration simply becomes the mapping of meaning and intent between the two worlds. You design the representation of the process that makes sense for your operation—not the one dictated by the systems.

Composable solutions also shift the perspective entirely by taking a human-centric, activity-based approach organized around the physical reality of the shop floor. I fully recognize that, in the traditional monolithic MES world, standard models like ISA-88 were considered essential—they provided structure, discipline, and a shared language for process-centric systems. But composability represents a fundamentally new paradigm. 

To democratize operational systems and bring them closer to frontline work, we must prioritize operator-first design rather than forcing every SME to become a master of S88 modeling. ISA-88 remains invaluable for process control, but the surrounding operational systems must be simplified and democratized so they can work hand in hand with the distributed nature of modern manufacturing. Composable platforms do exactly that: they allow process engineers, chemical engineers, and frontline teams to collaborate without being constrained by rigid, expert-only models.

This alone would dramatically simplify integration. But the real breakthrough comes with agents.

2. Builder Agents Enable Multithreaded, Generative Solutioning

Builder agents transform integration work from a linear, manual design activity into a parallel, iterative, and generative process. They don’t just help you “build faster”—they fundamentally change how solutions are conceived and engineered.

I experimented with builder agents that can ingest a full ISA-88 recipe structure and conduct deep introspection on it: understanding the procedural models, identifying phase logic, parsing parameter definitions, and extracting the relationships between equipment, units, and operations. It then suggested mappings, app contexts, and design patterns—not only based on expert interpretation of the ISA-88 standard, but also from what they’ve learned across existing apps, historical integrations, real-world performance of similar solutions and critically expert knowledge of composable design principles. In other words, these agent combines domain expertise with empirical insight, offering design options that reflect both best practices and operational realities.

This alone already feels like having a team of process engineers and MES architects working in hyperspeed. But the true power emerges when operational agents begin contributing dynamic intelligence into that design loop.

Operational agents provide real-time feedback about process variability, material availability, logistics implications, quality status, or unexpected delays. They can accommodate non-optimal or evolving recipes by dynamically dispatching materials, reallocating resources, or bringing the right expertise into the process at the right time. This dramatically increases operational resilience and reduces risk—because the system adapts rather than stalls when confronted with real-world complexity.

And then there’s compliance...

Specialized builder agents trained on GxP principles can support on-the-fly risk assessments, propose mitigation strategies, and generate validation documentation as part of the design cycle. Operational validation agents can take this further, enabling true continuous validation—monitoring execution conditions, evaluating deviations against risk models, and providing traceable explanations for decisions. Compliance becomes embedded, in fact native, in the system rather than layered on top.

When you step back and think about the implications, the potential is almost infinite. The combination of builder and operational agents elevates agility and compliance to levels we’ve never imagined in traditional MES architectures and design approaches. It enables systems that are not only faster to build, but continuously improving, self-aware, and aligned with both operational needs and regulatory expectations.

This is the beginning of a new era in how manufacturing solutions are designed, executed, and validated. It feels like a generative design process running at hyperspeed. Not a single assistant helping you code tasks faster — but a team of AI experts collaborating to create a complete solution.

And this unlocks something we have never had before in manufacturing software: the ability to rapidly iterate and explore multiple viable integration architectures before committing to one. This is enormously valuable in an ISA-88 context, where recipes, equipment logic, and operational variability rarely align perfectly.

Seeing the Explosion of Use Cases

If you let the builder and operational agents begin to work together, the number of possibilities just explodes - its the first step towards a Multi-Agent System (MAS). These agents don’t simply execute tasks—they learn, reason, and collaborate in ways that constantly reinforce and expand what’s possible. Suddenly, problems that used to take months of engineering effort can be tackled in days—or even hours.

Some of the notable and exciting use cases I’ve come across include:

• Automatically mapping process logic into app structures.
• Rapidly generating compliant workflows for regulated environments.
• Exploring recipe variants and operational scenarios through simulation.
• Using agents to assist in validation and documentation.
• Dynamically interpreting and adapting recipes at runtime.
• Applying cross‑system reasoning to catch inconsistencies early.
• Coordinating multiple agents to design complete production solutions.

Each one opens a new door—where imagination, not technical limitation, becomes the real constraint.

What stands out to me most is the sheer power of these systems and what they make possible. Seeing a builder agent reason through an ISA-88 recipe, or an operational agent adapt to a real-time process disruption, feels less like traditional programming and more like working alongside a tireless, highly capable collaborator. My role has shifted from hands-on integration to guiding and steering intelligent agents—and that shift fundamentally changes how we think about manufacturing systems. The emerging dialogue between human expertise and machine reasoning opens up an entirely new design space, one where adaptability, resilience, and scale are no longer constrained by human bandwidth.

I’m also starting to document and share some of these experiences through AI‑generated videos, another capability I’m learning to use. They’ve turned out to be a surprisingly powerful way to show what agentic systems can do—and to help others visualize these new forms of collaboration on the shop floor. It’s a learning journey in itself, but it feels like the right extension of this exploration: using AI not only to build better systems but to communicate and learn in entirely new ways.

Seeing all of this unfold up close, it’s clear we’re not just evolving automation—we’re watching Holonic concepts come alive, the manifestation of the new digital manufacturing reality.

Crossing the Digital Divide: Human-Centric Manufacturing in a Multi-Agent World

When you step back and look at what emerges from the combination of builder agents and operational agents, it becomes clear that this is not just another productivity boost or architectural evolution. It is a convergence point — one that aligns remarkably well with how manufacturing operations have always been run by humans.

Manufacturing has never been a purely deterministic, rules-based environment. It is adaptive, situational, and deeply human. Engineers design intent. Operators respond to reality. Supervisors balance constraints. Quality professionals manage risk. For decades, our digital systems have struggled to reflect this reality, forcing people to adapt to rigid models and monolithic workflows rather than supporting the way work actually happens.

Multi-agent systems change that equation by enabling digital systems to finally reflect the way manufacturing actually operates—through parallel problem solving, continuous adaptation, and coordinated decision-making across people, processes, and technology.

Builder agents mirror how engineering teams work: exploring options in parallel, iterating designs, learning from past outcomes, and continuously refining solutions. Operational agents mirror how plants operate: responding to variability, adjusting to constraints, coordinating people and materials, and managing risk in real time. Together, they form a digital system that finally behaves the way manufacturing organizations behave — collaborative, contextual, and resilient.

 

This is profoundly human-centric, because it aligns digital systems with how manufacturing teams actually operate — dynamically, collaboratively, and contextually.

It also brings into sharp focus a theme I’ve been writing and speaking about since the late1990s. For decades, we have tried to digitize manufacturing by automating tasks, enforcing standard models, and embedding rigid logic into systems. That approach delivered value, but it also created the very constraints that now limit agility, scalability, and innovation.

What we are seeing now is the realization of a different paradigm — one where digital systems augment human reasoning instead of replacing it, where composability replaces monoliths, and where intelligence is distributed across agents rather than centralized in static applications. This is the paradigm shift I’ve been pointing to for years, and it is finally reaching a practical, scalable form.

The convergence of composable platforms, agentic AI, and multi-agent collaboration marks a true inflection point. We are no longer just modernizing legacy systems. We are crossing the digital divide — moving from systems that support transactions to systems that participate in operations.

The potential here is vast! Agility, resilience, productivity, and compliance are no longer trade-offs. They become reinforcing outcomes of a system designed around human workflows, continuously learning agents, and real-world context.

This is not the end state — it’s the beginning. But for the first time, the tools, platforms, and paradigms are aligned. And that alignment is what makes this moment different from other transformative eras that came before. And it will not stop - that is why we call it continuous transformation! 

Composability, Governance, and the Future of Agentic AI in Manufacturing

We’ve all heard the stories: “Somebody created a solution in just a few hours with no-code or vibe coding…”.

It’s exciting, right? Engineers solving problems in record time, building digital tools with nothing more than intuition, creativity, and a bit of AI support. This is the promise of democratization—Agentic AI empowering everyone to innovate and improve.

And in many contexts, that speed is a superpower. But in manufacturing, the story is more complicated. Operations are inherently complex: machines, materials, people, processes, schedules, quality checks, and compliance requirements all interact in a dynamic web that is nonlinear, a complex adaptive system. In such environments, even small changes can cascade unpredictably, amplifying into disruptions far greater than their cause—an inherent feature of systems where interdependencies drive emergent outcomes.

This is where the risk lies. If an unguided agent makes the wrong decision in such an environment, things can go wrong very quickly—and often in ways that are difficult to anticipate or trace. The result might be downtime, compromised product quality, production delays and at worst safety issues. But the bigger danger is cultural: when something fails spectacularly, it doesn’t just cause operational damage—it can scare the organization away from using the technology at all.

Instead of unlocking incredible productivity, one misstep can trigger a mindset of “we don’t dare do this again…”. That’s not just a lost opportunity; it’s a setback that can stall digital transformation for years.

Digital Maturity Gaps

With the incredible pace of innovation of digital technologies and specifically Agentic AI, we have to acknowledge a hard truth: most manufacturers are still not fully ready to capitalize on this technology. The foundations are often shaky, and if we introduce solutions built by and with agents into this environment without addressing the gaps, the risks multiply.

Some of the most common issues include:

• Fragmented data that prevents end-to-end visibility.
• Disconnected IT and OT systems that block seamless collaboration.
• Cultural skepticism and lack of digital maturity that slow adoption and erode trust.

These are not new problems. I discuss them in detail in this blog.  Our traditional models both in technical architecture and deployment of operational solutions for manufacturing were never designed for the agile, composable, and connected environments we’re striving to build today. In addition we can't ignore that in any given manufacturing facility there are machines and systems of varying ages and legacy status.

Consider a Scenario

An enthusiastic engineer uses vibe coding to create an agent that dispatches materials to keep machines and operators as busy as possible. At first, everything looks good, machines are running at full capacity, operators always have work, and parts move quickly into assembly.

But no one realized the agent doesn’t properly recognize WIP limits or downstream capacity. It keeps dispatching jobs even when assembly stations and testers can’t keep up. The result: piles of excess material stack up between stations, overflowing into walkways and creating unsafe conditions for operators.

In a matter of hours, what was meant to boost productivity causes overproduction, flow disruption, and a serious safety hazard. The line is forced to stop because the system created too much of it, in the wrong place, at the wrong time. 

This isn’t hypothetical. It’s the kind of risk that emerges when Agentic AI is unleashed without governance. And unlike traditional tools, agents can act autonomously and at scale, amplifying errors at a speed we may not be able to react to.

Managing Complexity with Composability: Governance, Framework & Platform

Given this reality—where digital maturity is uneven, legacy systems abound, and the dynamic nature of manufacturing operations—the arrival of Agentic AI presents both an enormous opportunity and a serious risk. Agents are coming at us fast, and their power lies in democratization and speed. But those same qualities, in an environment as sensitive as manufacturing, can amplify problems just as quickly as they solve them.

This paradigm shift cannot be left to chance. To harness Agentic AI safely and effectively, we need to approach it in an organized, managed, and focused way. That requires: governance, framework, and platform all working together and grounded in composability.

• Governance gives us the rules, guidance, and guardrails to ensure reliability, safety, quality, and compliance are never compromised. Governance is not just about control; it actively helps organizations overcome barriers like fragmented data, siloed systems, and cultural skepticism by providing structure, discipline, and confidence. Done right, it helps in the transformation of the manufacturing environment from both a technical readiness (data integrity, system integration) and an organizational readiness (culture, mindset, trust).

• Framework provides the structure to make governance actionable. In A Composable Agentic Framework for Frontline Operations, I laid out how agents can be defined by type, given clear goals, and aligned through the artefact model. The framework ensures that agents are not just scattered tools but part of a purposeful, multi-agent system that reflects and supports real operations.

• Platform is the enabling layer. An Agentic manufacturing operations platform purpose-built for frontline operations makes it possible to apply governance and framework seamlessly—across both authoring (building digital solutions) and execution (running the production line). Unlike generic vibe coding environments, such a platform is designed specifically for process engineers and operations teams. It embeds an understanding of how manufacturing works—constraints, variability, compliance, and safety—and provides tools to build solutions quickly while remaining aligned with operational best practices. Most importantly, it enables the creation and deployment of operational agents at scale that are are integral parts of the production system itself.

And underlying all of this is composability. Composability ensures that agents and solutions don’t exist in isolation, but as modular, human-centric, bottom-up elements of a system that adapts as needs evolve. Digital transformation success depends on treating composability not as an IT concept, but as an operational paradigm. In fact, composability was conceived for multi-agent systems (MAS)—and Agentic AI now makes that vision practical.

Final Thoughts

I think that we all agree that Agentic AI despite all the hype is not a fad—it’s here, its real and it’s already reshaping how work gets done. But to harness it safely and effectively, we need to recognize the two distinct scenarios where agents play a role:

1. In building and engineering: where agents help create digital content, processes, and solutions. Here, governance ensures what gets built is valid, safe, and aligned with operational goals.

2. In live operations: where agents support and even run production activities, interacting with machines, data, and humans in real time. Here, governance ensures reliability, compliance, and resilience in execution.

Both scenarios are powerful—they are needed but both also carry risks if unmanaged. And in manufacturing, where operations are complex and dynamic, small missteps can cascade into detrimental consequences.

That is why governance, framework, and platform are critical. Governance provides the rules and guardrails; the framework gives agents structure, goals, and alignment through the artefact model; and the platform operationalizes it all, giving process engineers and frontline teams the environment to deploy agents as integral parts of the production system, and all of this at scale.

And beneath it all is composability. As I’ve argued before, composability was conceived for multi-agent systems—modular, autonomous, and collaborative components working toward shared goals. Agentic AI now makes that vision practical on the shop floor.

The challenge ahead is not whether manufacturers will adopt Agentic AI, but whether they will do so in a way that balances speed with safety, democratization with discipline, and autonomy with alignment. Done right, it promises resilience, reliability, and the kind of productivity gains that digital transformation has always aspired to deliver.

---

A Composable Agentic Framework for Frontline Operations

Over the last year, “agentic AI” has shifted from emerging concept to practical conversation. Everyone is now talking about agents, and with today’s tools, building one has become every person’s business. But that raises a much bigger question: what agents should we build, and how do we organize them into something meaningful?

This is a topic that is not new and I have reflected on it through a number of lenses, e.g. Why IIoT is Transformative - its not the technology! and The Genius of the Toyota Production System Explained. This post however offers my first reflections on what a Composable Agentic Framework could look like for operations in general and manufacturing specifically. It’s an attempt to give industry an initial perspective, a concept and maybe some guidance for applying agentic AI to frontline operations in ways that improve both productivity and adaptability. Notice I say "initial", there is clearly much more to this topic that needs to be explored, discussed and debated - in addition the technology is nascent and we can expect much more sophistication and depth as it evolves.

Why Agents? Why Now?

For decades my peers and I, as manufacturing thinkers, have dreamed of holonic systems and fractal factories—production environments that adapt in real time, scale seamlessly, and continuously self-optimize. But until recently, that vision stayed in the realm of theory. The technology just wasn’t ready.

Now it is. Today’s digital platforms, IIoT connectivity, cloud infrastructure, and AI capabilities make it possible to realize this vision in practice. Instead of rigid, monolithic systems, we can now compose operations out of, and with, autonomous, collaborative agents that interact dynamically.

And this matters because composability is built on the idea that continuous, incremental improvements add up to transformation. What’s new is that agentic AI can accelerate these improvements beyond what we can imagine. Large language models and agentic frameworks have already proven their ability to supercharge productivity in domains like software development, research, and customer interaction. The challenge—and opportunity—before us now is to understand and define how to bring that same acceleration into composability and frontline operations.

Agents make this possible. Each agent is discrete, goal-oriented, and autonomous, yet designed to collaborate with other agents. When composed together, they create systems that flex, adapt, and continuously optimize.

In earlier posts, I’ve argued that digital transformation is not about IT and OT learning to coexist, but about creating a new whole where the distinction ceases to matter. That’s the essence of composability. Agents are the next step: a way to make that vision practical, modular, and scalable.

An Agent Framework for Composable Digital Solutions

The starting point is simple: in new digital operations platforms like Tulip, apps already behave like agents.

• They have a clear goal (guide an operator, track a unit, log a machine event).
• They operate autonomously within their context.
• They collaborate with other apps and systems through shared data, triggers, and transitions.

Add AI into the mix, and these apps become agentic apps—supercharged digital teammates. And when multiple apps are composed together, they form a multi-agent system that mirrors the complexity of real operations, in other words they become digital twins in the true sense of the concept.

But in order for this "mirroring" to become a digital twin we need to define some rules and this is where the framework comes in. To move from scattered apps and automations to composable digital solutions, we need a structured way to think about agents.

Add AI into the mix, and apps evolve into agentic apps—supercharged digital teammates. Composed together, they form multi-agent systems that can mirror the complexity of real operations—becoming digital twins in the truest sense. But achieving that requires more than simply building agents; it requires structure and guidance. Without it, the risk is a proliferation of scattered apps and agents with no cohesive purpose—at best delivering little value, and at worst creating more complexity, reduced productivity, and even unsafe outcomes. The goal of this suggest framework is to provide the rules and design principles that ensure agents align toward a shared purpose. This reflects the essence of holonic structures: their power comes not just from autonomy, but from working together toward a common goal. That shared purpose is what makes them optimal, and what turns a collection of agents into a true composable digital solution that delivers measurable benefits.

In my earlier blog post “To Data Model or Not to Data Model”, I described the Artefact Model as a key element in composability: a scalable, flexible, interpretable representation of the operational system. The Artefact Model gives us the common context in which agents can interact—products, orders, machines, deviations, and operators all represented digitally and consistently.

A Perspective on Agent Types

Before diving into the types themselves, it’s important to recognize that agents serve two distinct scenarios in manufacturing:

Authoring / Building – Here, agents augment the creation process. They help engineers, developers, and even citizen builders design solutions faster and smarter. Think of them as co-pilots that propose app templates, generate artefact structures, suggest best practices, and automate repetitive setup tasks. These agents accelerate innovation and democratize solution-building.

Operations – Once deployed, agents act within day-to-day execution. They monitor machines, guide operators, coordinate workflows, manage deviations, and connect enterprise systems. These operational agents are the ones “living” in production, continuously working toward defined goals while collaborating with other agents and humans.

The framework presented here is focused specifically on the operations scenario. That being said there are commonalities and some agent types apply to both scenarios, but the context differs: in building, agents amplify human creativity and speed; in operations, agents amplify execution and adaptability. 

Agentic AI in operations enables a powerful ecosystem where "teams of experts" (agents) work together, demonstrating "collective intelligence". Crucially, operational agents, empowered by AI, transform what were once innate objects like machines and materials into active, intelligent members of the dynamic work environment. We are giving them the ability to be agents—autonomous and collaborative participants within the dynamic manufacturing operation network.

With that lets take a look at a shared taxonomy for the different types of agents in a composable agent framework:

Physical Agents: These agents are defined by their direct representation of physical manufacturing objects within the digital twin. They continuously mirror the real-world status, attributes, and behaviors of their tangible counterparts, enabling real-time monitoring, analysis, and control. Here are some examples:

• Product Agent: Represents a specific product or unit throughout its manufacturing journey. Its goal is to track the product's individual status, quality parameters, and genealogy, providing a comprehensive digital record for each item produced.
• Machine Agent: Serves as the digital twin of a specific piece of equipment or machinery on the shop floor. Its purpose is to monitor machine health, performance metrics (e.g., OEE, availability, performance, quality ), and predict potential failures, enabling proactive maintenance and optimized utilization.
• Tote Agent: Represents a tote or device that carries and conveys product or material on the shop floor. This agent's role is to track the movement of the material or products it carrier in the operations and facilitates traceability and location with ease.

Operational Agents: These agents are defined by their focus on tangible operational entities and processes used in manufacturing management. They manage the flow of work, information, and events, ensuring that manufacturing processes adhere to plans and respond effectively to deviations. Here are some examples:

• Order Agent: Represents a specific production or work order. Its goal is to oversee the end-to-end execution of that order, tracking progress against the schedule, managing material consumption, and ensuring all required steps are completed.
• Deviation Agent: Activated when a process or quality deviation occurs. Its purpose is to identify, classify, and manage the deviation, potentially initiating corrective actions, alerts, or escalation workflows to relevant personnel or systems.
• Schedule Agent: Responsible for dynamically managing and optimizing production schedules. This agent works to ensure resources are efficiently allocated and production targets are met, adapting to real-time changes in machine status, material availability, or order priorities.

System Agents: These agents are defined by their role in facilitating integration and intelligent interaction with broader enterprise-level systems and data repositories. They ensure data consistency, enable seamless workflow orchestration across different platforms, and provide access to critical business context. Here are some examples:

• ERP Agent: Manages the flow of information between Tulip and the Enterprise Resource Planning system. Its function includes receiving work orders, reporting production updates, and managing material consumption and inventory levels in the ERP.
• UNS Agent: Represents the integration with a Unified Namespace. This agent enables seamless, real-time data exchange across the entire operational landscape, ensuring that all systems have access to consistent and up-to-date information.
• Data Lake Agent: Responsible for managing the ingestion of operational data from Tulip into a central data lake and enabling access to this data for advanced analytics and further AI model training. It ensures that the rich data captured by Tulip's composable applications is leveraged for broader insights.
• Device Agent: Corresponds to a specific connected device, such as a scale, barcode scanner, or sensor. This agent's role is to facilitate seamless data exchange between the physical device and the Tulip platform, ensuring accurate data collection and enabling device-triggered actions.

Staff or Companion Agents. These are a general type of agent that augment the human's ability to find information, research topics, suggest improvements, and perform tasks. They are used in a variety of scenarios and serve as utilities in both the operational environment as well as the engineering or builder environments. Here are some examples:

• Quality Research Agent: Quickly finds documentation, suggests troubleshooting steps to an operator, or summarizes a quality history for a supervisor.
• App Builder Agent: Generates app templates, proposes table structures in the Artefact Model, or scaffolds connectors based on device specs—accelerating citizen developers and engineers.

What unites these agent types in this framework is the three core properties: it has a goal, it operates autonomously within a bounded scope, and it is collaborative—able to exchange data, signals, and intent with other agents and humans.

Crucially, these agent types do more than align with the Artefact Model — they enhance it. By consistent real time representation of artefacts (products, resources, orders, deviations), agents enrich the shared digital twin with actionable state, decisions, and provenance. That enriched Artefact Model becomes the lingua franca that lets agents interoperate reliably, enables composition, and prevents the classic failure mode: a landscape of scattered apps and ad-hoc bots with no unifying purpose.

In short: agents must be designed to work as an integral part of  the Artefact Model so that autonomy and collaboration add up to a cohesive, safe, and value-driving digital twin.

Beyond Incrementalism: The Future of Multi-Agent Collaboration Frameworks

Much of what we know about manufacturing improvements has historically been driven by incrementalism—step-by-step gains in efficiency, quality, or throughput. This mindset is not wrong; in fact, it is the foundation of continuous improvement and the heart of lean thinking. But incrementalism alone can only take us so far. To thrive in today’s volatile and complex operating environments, we need systems that don’t just get gradually better but can adapt dynamically to new conditions.

This is where multi-agent collaboration becomes transformative. Agents, by design, are autonomous but collaborative, and when they interact at scale, they exhibit something greater than the sum of their parts: collective intelligence.

The result is emergence and self-organization: a system-level intelligence and adaptability that was not explicitly programmed into any single agent. Emergent behavior is what allows multi-agent systems to flex and reconfigure in response to disruptions, market changes, or unexpected events. This is not just automation—it’s a new layer of operational intelligence applied directly to the frontline.

But to realize this potential, we must also reconsider the frameworks that structure our digital manufacturing systems. Such a composable, agentic world—where apps act as agents and operations are orchestrated by multi-agent systems—doesn’t fit neatly into traditional manufacturing systems standards and hierarchies definitions (see my earlier post, OK, Let’s Talk ISA-95).

That doesn’t mean throwing standards away, but it does mean rethinking or adapting them to this new reality. If emergence is the key to adaptability, then our models and standards need to evolve to describe systems that are dynamic, distributed, and composable rather than hierarchical and rigid.

In short: incrementalism is still essential, but it is no longer sufficient. Collective intelligence, powered by agents and guided by frameworks like the Artefact Model, is what will enable manufacturing to achieve adaptability at scale—and truly fulfill the promise of digital transformation.

Final Reflections

Building, authoring, creating agents is within everyone’s reach. But without structure and guidance, we risk ending up with a fragmented landscape of apps and bots—scattered efforts that deliver little value, or worse, add complexity, reduce productivity, and even create unsafe outcomes.

My hope is that this initial framework presented here provides that needed guidance. It should help us define what kinds of agents to build, how to compose them into systems, and how to ensure they align with a unifying purpose. It grounds agentic design in Composability and its Artefact Model, ensuring that agents not only adhere to but actively enhance the shared digital twin. This alignment is what keeps autonomy and collaboration from drifting apart and turns them into something greater: collective intelligence with emergent adaptability.

This is why composability and agent frameworks matter. They give us the structure to channel autonomy toward common goals. They offer to guide us on the path to increased productivity with adaptability. And they point to the need for new thinking in our standards and models—beyond the rigid boundaries of monolithic approaches, toward a more dynamic and composable reality.

In the end, the promise of agentic AI in operations is a the newest step in the digital transformation journey: Continuous Transformation - reinvention at scale of manufacturing operations.

And this is just the beginning. There is so much more to explore, define, and refine. I invite you—industry peers, practitioners, and thinkers—to engage in this discussion and debate. Let’s shape together what a composable agentic framework should look like in practice. After all, it takes a village... 

Why Are We Still Talking About MES–ERP Integration?

Every few months, I still come across discussions about how to integrate MES and ERP. And every time, I find myself asking: why are we still talking about this?

It’s a bit like asking whether a boat floats. The answer is obvious—yes, it does. The real question is where is it going and why are we on it?

Integration Isn’t the Problem

Let’s be clear: integration between MES and ERP is not new, nor is it unsolved. For decades, manufacturers have been connecting these systems to exchange the information that keeps their operations running. I challenge you—have you ever heard of an MES system that couldn’t integrate to ERP?

The technology is there. APIs, middleware, standardized data models, cloud-native platforms—the tools have only gotten better. Integration is no longer the hard part.

As I wrote in an earlier post "About Accountants and Production", ERP and MES have always been about different things. ERP is designed for financial management (order-to-cash) - transactions, costs, compliance, reporting. MES is built for the shop floor—real-time visibility, control, and execution. Each system has its domain. Integration ensures they don’t talk past each other.

But the value doesn’t come from whether or not you can connect the two. It comes from what you do with that connection.

From Technical to Value-Driven

When integration conversations remain technical—what middleware to use, which API calls to expose—we miss the bigger picture.

The true conversation should be:

• What processes, operations and decisions do we want to improve?
• What outcomes are we aiming to achieve?
• What value will the integration unlock for the business?

For example, integrating to have a streamlines and effective work order execution from ERP to MES is not valuable because the two systems are connected. It’s valuable because it eliminates manual re-entry, reduces errors, speeds up production scheduling, and ensures financial systems reflect operational reality in near real time.

Integration is the means. Value is the end.

Enter the Age of Digital and AI

We’re well into the era of digital, transformation is ongoing and constant, and AI in manufacturing is becoming a reality. Advanced analytics, machine learning, digital twins, and agentic AI are reshaping how operations are managed and humans work. Against that backdrop, spending time debating MES–ERP integration feels outdated.

The real opportunity is to ask: how do these systems, together, create the digital backbone that enables AI to bring operational insights that deliver business value?

ERP knows the plan. MES knows what actually happened. AI thrives when it can see both and spot patterns across them—optimizing schedules, predicting disruptions, and suggesting interventions. That’s the conversation worth having.

Time to Move On

So let’s put this to rest: MES and ERP can integrate. They do integrate. The technical questions have answers.

The real debate—the one that matters in the age of digital and AI—is about value. How do we design our digital architectures, processes, and cultures so that integration serves as the foundation for smarter, faster, and more agile manufacturing? Shift the focus from can we integrate? to what value will the integration deliver?

Orchestrating Digital Solutions With Multiple Perspectives

Contemplating the complexities of a manufacturing system has long been an area that I find deeply interesting. I find that its processes, equipment and technology relies on the contributions of diverse stakeholders, each with their own expertise. They work in concert with diverse technologies, physical and digital, to ensure smooth efficient operation that is continuously improving and adapting to changing business needs.

In the pre-digital world, manufacturing system design often operated in silos, as if orchestrating each instrument to play its part in isolation. The design process of monolithic solutions needed this approach. Engineers, the conductors of this orchestra, had to meticulously plan the production flow one instrument at a time in order to manage the complexity. The watchful eye of the project manager controlling scope, prioritizes and cost optimization meant allocation for different musical sections. Then when putting it all together the silos became painfully evident thus leaving it to the frontline operators, the tireless instrumentalists, to make it all work together and bring the production plan to life.

In the digital paradigm the complexity of a manufacturing system has to be understood using a multi-perspective design approach that dismantles these isolated sections and creates an orchestra where all instruments collaborate. Engineers contribute their technical knowledge, similar to the composer's understanding of musicality and frontline operators, with their firsthand experience, identify potential shortcomings and suggest improvements in workflow and ergonomics, akin to the instrumentalists providing feedback on the score's playability.

This collaborative approach fosters a holistic understanding of the system. It ensures that the designed solution translates seamlessly into the realities of the production floor.  Furthermore, the involvement of frontline operators, like the instrumentalists practicing together, fosters a sense of ownership, crucial for system adoption and success.

Agile iteration is the secret weapon that allows for continuous refinement throughout the building process. Just as an orchestra rehearses a piece, prototypes are built, tested on the shop floor, and feedback is rapidly incorporated. This ensures the design remains adaptable to unforeseen challenges and user needs. An agile approach allows for quick prototyping of the layout, followed by simulations and feedback from operators on ergonomics and workflow. This continuous loop of design, test, and refine leads to a more robust and user-friendly system. Therefore digital technology needs to support an iterative bottom-up adoption (design, deployment, implementation, integration, etc). In a way its the merging of Agile, from the software domain, and Continuous Improvement which are arguably the same fundamental concept. Both are "bottom up" methods to manage an ever changing environment, designing one step at a time, solving one problem at a time. 

Most pre-digital technology solutions used a top-down (waterfall) design everything first - then implement approach. This does not work in the digital paradigm and therefore digital technology has to not only allow but be a catalyst to these cycle of improvement and change. The magic ingredient here is the no-code frontline operations platform. These platforms empower non-technical personnel, like the frontline operators, to participate actively in the design process. Just as an easy-to-read score allows each musician to contribute their expertise, the platform allows operators to input data, propose changes to workflows, and visualize the impact of those changes. This democratizes the design process, ensuring valuable frontline insights are readily captured and integrated.

To support the bottom up approach - one that takes a problem by problem step wise path to building shop floor solution its important to have a consistent and repeatable design process. The core of the design should have set of  perspectives that effectively support the iterative process and allow for a holistic design. This is not as easy as you may think and needs a methodical study of design principles. This is another interest area of mine and I wanted to share some background before we come to the method that I find most effective. 

Let's start with a holistic design method such as the CATWOE framework that lays the foundation for a collaborative approach. Stemming from the Soft Systems Methodology (SSM), CATWOE stands for Customers, Actors, Transformation, Worldview, Owner, and Environment. By examining the system through these six lenses, we ensure all stakeholders are considered and their perspectives are integrated into the design process. This fosters a sense of shared ownership and leads to solutions that are not only technically sound but also operationally feasible and user-friendly. 

The CATWOE Framework

Another multi-perspective design approach that is interesting in this context is TOGAF (The Open Group Architecture Framework) standard. TOGAF promotes an enterprise architecture framework that considers the needs of various stakeholders across the organization.  Similar to the CATWOE framework, TOGAF emphasizes understanding the Business Architecture (customer needs, business goals), the Information Architecture (data flows), and the Technology Architecture (systems and infrastructure). By incorporating these diverse perspectives, TOGAF ensures a holistic view of the entire enterprise, just as the multi-perspective design approach ensures a holistic view of the manufacturing system. 

The TOGAF Standard

This synergy between the two approaches creates a robust foundation for designing efficient, adaptable, and user-centric manufacturing systems. SSM and CATWOE were the basis of methods I devised during my research in Holonic Manufacturing Systems, the archetype of modern IIoT solutions. The design approach I am defining here is inspired through CATWOE and a multi-perspective method that was developed by some of my mentors (Jens Bruun and Lief Poulsen) and based on TOGAF. Its a simple holistic design approach that allows a very effective way to move forward with the dynamic duo of agile iteration and no-code platforms.

The process has three sequential steps, each taking a unique perspective of the overall operations and that build on each other. Iterating through this sequence for each solution gradually uncovers the holistic design of the digital system. 

The three perspective for digital solution design:

1. Identify and clarify Business Objectives to find and prioritize the use cases in scope. Solutions should be designed to support frontline activities and business processes that a company has put in place in order to accomplish some specific strategic goals, i.e. the Business Objectives.
2. Define and understand the Physical Operations where the use cases of the digital solution will be implemented. Understand how the physical space, processes and value stream are laid out to meet the defined objectives. What is the physical flow of materials and operators, where are operators performing activities, what equipment is being used, and how the overall process integrates, material flow, equipment sharing, and frontline operators.
3. Understand the Activities and Business Processes that have been implemented to drive the operational value stream in the physical operations space. What activities do the operators perform in order to execute the manufacturing process, what systems and data are used and needed, where does an operation start and end, how is material moved and what are the production control mechanisms, what are the logistics of the operations and how do frontline operators interact with materials and equipment.  

The synergy between these three elements creates a dynamic and responsive design process. The multi-perspective approach fosters inclusivity, agile iteration ensures continuous improvement, and the no-code platform empowers frontline participation. This collaborative environment leads to the creation of digital solutions that are not just efficient but also user-friendly, sustainable, and adaptable to future challenges.

In conclusion, a successful manufacturing system requires a conductor – a multi-perspective design approach with agile iteration and a no-code frontline operations platform. This approach fosters a collaborative environment where diverse voices are heard, leading to a more robust, efficient, and user-centric manufacturing system. As manufacturing landscapes continue to evolve, this dynamic and responsive approach will be instrumental in ensuring long-term success, just as a well-rehearsed orchestra delivers a powerful and moving performance.

Taming the Lone Wolf: How to Avoid a Custom Monolith

The Perils of the Custom Monolith

Imagine a tightly packed toolbox – everything you need, but jammed together. Changes become risky domino effects. Deployments are slow and cumbersome. Scaling? Forget about it. Combine this with a single person heroically building a massive, all-encompassing solution or application that the operations is critically dependent on - we have all experienced it. This is called a "custom monolith".

While the effort and dedication of the lone wolf is admirable and commendable, this "custom monolith" approach usually ends up being expensive and risky to unravel. The custom monolith situation is typically more likely to happen with tools and platforms that offer a democratized approach. Its not only modern platforms that this pertains to, I have seen this phenomena with SCADA/HMIs, Access, MatLab, Quickbase, Retool, Tulip, etc., and of course the beloved Excel (or any spreadsheet).  

With the advent of no-code/low-code platforms that are fast becoming the norm in digital transformation the custom monolith phenomena is happening more often and faster. After all that is one of the characteristics of digital technology - order of magnitude faster. Its both a blessing and a curse, we all love the early adopter - the person who embraces the technology and creates the initial value for all. But then that initial solution grows and becomes an unwieldy custom monolith that only that person knows how to tame. Even more problematic is that the aura of the custom solution is that its complex and has a narrow scope. It can critically stall your digital transformation by alienating the platform, where people are fearful that they can't master the technology and dismissive of its relevancy to their other use cases. 

I have experienced countless times where customers bring in other technologies to solve a problem that their existing no-code platform excels in because it was used for one specific use case solved by a custom monolith. In one example a solution was built for inventory replenishment of manual assembly lines that became a big money saver for the company. The solution was built on a no-code platform and grew in scope to cover more and more lines such that it was intricate and complex - of course by one person. This was touted as a great success story in the companies digitalization journey but on the flip side shoehorned the digital platform to be an "inventory replenishment" system. When I visited the facility I noticed another technology being used for digital work instruction, which was a core capability of the digital platform. When I inquired about their choice of technologies the process engineers said; "well the platform is an inventory solution and we needed work instructions". They then added; "the technology we choose did not require the lone-wolf's [reference to the person who built the inventory solution] level of expertise". This was a clear case of a complete stall in technology adoption because of the "custom monolith" phenomena.

Breaking Free: Fostering Collaboration and Adoption

So how do we avoid these situations, and more importantly how do we setup of successful adoption of democratized digital technologies? The key is to divert the early adoption motion into a sustainable broad citizen development motion and thus prevent a lone wolf situation. Here are a few things to consider:

• Teamwork Makes the Dream Work
  Don't let one person become an island. Start building a community of citizen developers with a diverse backgrounds from all over the company. A culture of collaboration fosters peer reviews, knowledge sharing, and a sense of shared ownership. This is kind of obvious but sometimes hard to realize. 

• Embrace Shared Content
  The community should have a common collaboration hub, a center of excellence that they can use to network and share content. Establish clear guidelines for how to use the digital platform including selected use cases, content development practices, template, data structures, and integrations. This creates a foundation for future content developers to build upon, preventing them from becoming an unmaintainable labyrinth.

• Communication is Key
  Regular discussions about content goals, relevant use cases, technical roadblocks, and future features are crucial. This keeps everyone on the same page and helps identify opportunities to break down the monolith into smaller, more manageable pieces. It is also critical to establish a set of rules about what makes for good vs bad content - specifically around monolithic vs composable solution. These rules should be made part of the culture so that people regularly discuss content based on them.

• Governance
  Regular evaluation and discussions about goals, content effectiveness, solution value, technical roadblocks, and future features are crucial. Create an internal a process where content can be vetted and then shared for reuse across the company. Establish simple rules about how to create libraries of content, how to manage this content and how to disseminate it. Establish a simple but effective set of principles that define teamwork, use and development of shared content and communication, ie the combination of the key points listed above. 

Accelerated Digital Transformation

It sometimes goes unnoticed - by spreading the effort of building digital content broadly in an organization you essentially crowdsource your digital transformation. Done right this is an immense force that can accelerate your digital transformation beyond anything that you may have imagined. Of course managing and guiding this force is not trivial and requires strong leadership, effective governance and clear strategic objectives.