The OSI Model and AI in the Supply Chain: Why Layered Architecture Still Matters

AI in the supply chain is often approached as an application problem. In practice, it is more often an architectural one. The OSI model offers a useful lens for understanding why.

The Architecture Problem Behind AI in Supply Chains

Most discussions about AI in the supply chain begin at the top of the stack. They focus on copilots, models, dashboards, and use cases such as forecasting, routing, and risk detection. Those applications matter, but they are not the starting point.

The more important issue is the architecture underneath them.

This is where the OSI model becomes a useful reference point. Not because supply chains operate like communications networks in any literal sense, but because the OSI model solved a similar structural problem. It separated complexity into layers and clarified how those layers interact. That same discipline is becoming increasingly relevant as AI moves deeper into logistics and supply chain operations.

AI in the Supply Chain Is Best Understood as a Layered System

The most practical way to think about AI in the supply chain is as a layered system.

At the foundation is the data layer. This includes ERP, TMS, WMS, IoT signals, supplier feeds, and external data sources. If this layer is fragmented or inconsistent, the layers above it will underperform. That aligns directly with the data harmonization requirement described in ARC research. AI depends on clean, linked, and current data, and advanced systems are only as effective as the data they operate on .

Above that is the communication layer. In traditional systems, applications exchange information through rigid integrations, manual handoffs, and batch processes. In more advanced environments, data and decisions move through APIs, event streams, and increasingly through agent-to-agent coordination. ARC’s framework describes A2A as a way for autonomous software agents to interact directly, share data, assess options, and execute decisions across the supply chain . That matters because modern supply chains do not just need better analytics. They need faster coordination across functions.

Context Is the Missing Layer in Many AI Deployments

The next layer is context. This is where many AI initiatives begin to weaken. Systems may generate plausible recommendations, but without memory of prior events, supplier history, operational constraints, or previous failures, they remain limited. The white paper describes the Model Context Protocol as a way to embed memory, identity, and continuity into AI systems so they can retain operating context over time and carry that context across workflows . In supply chain settings, that kind of continuity is important because decisions are rarely isolated. They are part of a sequence.

Reasoning Must Reflect the Networked Nature of Supply Chains

Then comes the reasoning layer. This is where retrieval-augmented generation and graph-based reasoning become useful. RAG allows systems to retrieve current, domain-specific information before generating an answer. Graph RAG extends that by reasoning across interconnected entities and dependencies. ARC’s analysis makes the point clearly: supply chains are networks, not lists, and graph structures help AI navigate those interdependencies more effectively .

This is one of the more important distinctions in enterprise AI. A system that can retrieve a policy document is useful. A system that can understand how a supplier, a port, an order, and a downstream constraint relate to one another is more operationally relevant.

Why Many AI Initiatives Stall

At the top is the application layer, the part users actually see. This includes control towers, planning workbenches, copilots, and workflow assistants. Most companies start here. That is understandable, because this is the visible part of the stack. It is also why many AI initiatives produce narrow results. The application may improve, but the lower layers remain weak.

That is the main lesson the OSI analogy helps clarify. AI in the supply chain should not be treated primarily as a front-end feature. It is better understood as a layered architecture that depends on data quality, system interoperability, context retention, and network-aware reasoning.

This also helps explain why some AI deployments perform well in demonstrations but struggle in operations. The model itself may be capable, but the environment around it may not be ready. Data may not be harmonized. Systems may not communicate cleanly. Context may not persist. Knowledge retrieval may not be grounded in current enterprise information. In those cases, the problem is not that AI has limited potential. The problem is that the stack is incomplete.

The ARC Framework Points to a More Durable Model

The ARC framework points toward a more grounded view. A2A supports coordination between systems. MCP supports continuity across time and decisions. RAG supports access to relevant knowledge. Graph RAG supports reasoning across a networked operating environment. Together, these are not just features. They are components of an emerging architecture for supply chain intelligence.

What This Means for Supply Chain Leaders

For supply chain leaders, the implication is practical. AI strategy should begin with the question, “What layers need to be in place for these systems to work reliably at scale?” That shifts the focus away from isolated pilots and toward a more durable operating model.

In practical terms, that means improving data harmonization before expanding model deployment. It means designing for system-to-system coordination rather than relying only on dashboards and alerts. It means treating context as infrastructure rather than as a convenience feature. And it means building toward reasoning systems that reflect the networked nature of the supply chain itself.

Bottom Line

The OSI model is not a blueprint for AI in logistics. But it remains a useful reminder that complex systems tend to perform better when their layers are clearly defined and properly integrated.

That is becoming true of AI in the supply chain as well.

The companies that recognize this early are more likely to build systems that support better coordination, more consistent decision-making, and more useful intelligence across the network. The companies that do not may continue to add AI applications at the surface while leaving the underlying architecture unresolved.