Posts

The complexity of installing and integrating three layers (MES, MOM, ERP) separately, the challenges of air-gapped and on-premises solutions, and why a coordinated approach is essential.

Every week, a manager, IT admin, or employee opens a new AI tool. Nobody sets its rules, boundaries, or owner. The accumulation of small decisions, shadow entities, and organizational blindness.

In demand-driven production, variable recipes and routing choices, operation sequence uncertainty, and the gap between standard cost and actual cost make dynamic recipe and real-cost engines essential.

Understanding the real foundation of organizational AI through integrated role, policy, delegation, and version control.

Data flow, integrating ERP systems like Netsis, Odoo, Logo, Paraşüt with MOM and MES, and how infab.cloud bridges the integration layer.

Agents are now in the organization. But how does a team actually work when humans and agents are mixed together? Who decides the work split? Who holds approval responsibility? Where are all these rules written down?

MOM wraps MES and orchestrates production, quality, maintenance, and inventory decisions together.

A human manager delegates work to a subordinate. Do agents do the same? How does A2A (agent-to-agent) delegation work? What is the approval flow and result verification process?

MES captures actual time, stoppages, and scrap data from work order open to close in real time.

Where do you write an agent's operating rules? In policy.md. What are agent states (Draft, Active, Inactive), skill types (builtin, MCP, HTTP, function), and policy boundaries?

ERP handles finance, sales, procurement, and inventory. For real-time shop-floor operations, it is not sufficient on its own.

In made-to-order production, every order is unique. When operations begin, where does the information go? Split between paper, Excel, the foreman's memory, WhatsApp, and phone calls—the cost of fragmented knowledge.