Your accounting system is the worst place to answer the big questions about your business. That sounds backwards, because Business Central already holds every number that matters. In this episode of Simply Explained you will learn: What Business Central Really Is What Fabric and OneLake Are Why Analytics Live Outside the ERP Three Ways the Data Gets Across What the Flow Looks Like What Usually Goes Wrong When You Need It and When You Don't A Quick Recap and One Question Simply Explaine...

Predictive maintenance on Azure only pays off when a warning arrives early enough for your team to act on it. In this episode of the iFAKT series, we start with the maintenance decision and work backward to the evidence, data and process you need before choosing a model on Azure. We follow one hypothetical asset from sensor reading to approved work order and ask the questions most projects skip: What action should a warning trigger? How much warning horizon do spares, permits, isolation and pro...

1. THE SHOP FLOOR SYMPTOM & CORE CHALLENGETeams frequently send plant telemetry into Azure using whatever service sounds right in initial workshops, only to discover months later that the data path cannot support actual plant operations. This often results in multiple dashboards showing conflicting values (such as 5-minute averages compared against maximum values or alarms) derived from copies of the same signal. Ultimately, this technical disconnect creates an issue of trust rather than a simpl...

When a critical manufacturing bottleneck machine stops mid-shift, production lines default to a familiar, reactive scramble. Operators immediately call maintenance, supervisors check the master production schedule, and team members begin cross-referencing multiple digital systems. Someone opens the Manufacturing Execution System (MES), someone else queries the Enterprise Resource Planning (ERP) platform, and a brand-new dashboard inevitably appears because every factory floor crisis seems to de...

When a production line halts mid-shift, the real cost isn't just measured on a cloud billing dashboard. It manifests as physical scrap, operators standing idle at a stopped station, and networks flooded with unneeded data. Most cloud-first projects fail because they immediately push everything upward, ignoring the reality of the factory floor where milliseconds and local constraints dictate whether a product makes it or gets scrapped. THE FACTORY CLOCK: MATCHING WORKLOADS TO TIME HORIZONSA manu...

UNLOCKING FACTORY AI: WHY YOUR PLANT NEEDS PRODUCT-PROCESS-RESOURCE (PPR) KNOWLEDGE GRAPHSFactory artificial intelligence is often capable of reading massive amounts of data, yet it frequently lacks a fundamental understanding of the actual plant environment. Enterprise Resource Planning (ERP) systems know the orders, Manufacturing Execution Systems (MES) know the operations, and historians know the signals. However, none of these isolated records automatically explain how a product, process, an...

Here are the show notes based on the transcript provided, organized by key themes and structured to provide a clear summary of the core arguments against reactive machine purchases and for a systems-based approach using simulation. Episode Notes: Machine Capacity vs. System OutputOverviewA growing queue, slipping lead times, and sales demanding answers often trigger a reflex: "We need another machine." This reaction is rational—local activity looks busy, overtime is climbing, and that specific ...

UNTANGLING THE PLANT FLOOR: MQTT vs OPC UA & THE TRUTH ABOUT DISCONNECTED MANUFACTURING DATAWhy are modern factories still running on manual exports and guesswork despite having ERP, MES, and Azure systems in place? This episode cuts through the technology hype to address the core problem: a fundamental lack of trust in manufacturing data. People try to frame industrial connectivity as a winner-takes-all battle between MQTT and OPC UA, but that misses the point entirely. If your operators trust ...

REPLACING THE EXCEL BOTTLENECK: BUILDING A REAL-TIME DECISION PIPELINE A modern factory is a hive of real-time data, with sensors, controllers, and supervisory systems tracking every machine state, fault code, and temperature fluctuation. Yet, when a...

When a machine stops, a planner needs more than a red line on a dashboard. They need to know what stopped, why it stopped, which order sits on that line, and whether the production plan can still hold. Moving raw signals from a factory floor into cloud analytics requires a reliable architecture that spans field sensors, industrial gateways, message brokers, and cloud ingestion layers. CAPTURING THE SIGNAL AT THE EDGEA sensor signal is not yet manufacturing information. Picture a packaging line ...

Provisioning ten devices on a shop floor is simple, as a technician can easily punch in a connection string and confirm telemetry. However, trying that same manual approach with one hundred thousand devices spread across global factories and customer networks causes every shortcut to turn into an architectural failure. Moving beyond basic setups requires a robust understanding of device identity, trust boundaries, hub routing, and long-term fleet management. MANUFACTURING VERSUS OPERATIONAL IDE...

Welcome to a brand-new episode where we cut straight through vendor hype and tackle the real problems of digital twins on Azure. Everyone wants a digital twin, but almost nobody starts with the actual problem their plant needs to solve. Data already lives across your ERP, MES, historians, and IoT layers, yet operators still rely on manual phone calls, spreadsheets, and scattered alarms to figure out what a fault actually affects. START WITH THE DECISION, NOT THE ASSETBefore building elaborate a...

An urgent customer request sounds simple: sales promises a fast delivery date, marks the order as priority, and asks production to fit it in. But the new order does not enter an empty factory. It enters a schedule already filled with machine reservations, material allocations, setup plans, qualified people, inspection capacity, maintenance windows, and promises made to other customers. The real question is therefore not simply whether the urgent order can be produced, but which existing commitme...

A machine stops in the middle of production. ERP knows the customer orders and due dates, MES knows which operation stopped, maintenance knows the repair status, and the machine layer knows the fault code and exact timestamp. Then someone asks the obvious question: what should we do now? AI can summarize the alarm, find patterns in historical downtime, and explain what probably happened. But unless it also understands which product was running, which orders depend on that operation, which machi...

A production schedule can look correct while the factory has already moved on. A machine runs slower than expected, a setup takes longer, material is still waiting for release, or an urgent order enters the plan. ERP still shows the original dates, MES shows current execution, and the supervisor has already started adjusting the sequence on the floor. The real challenge is keeping the schedule connected to what production can actually do now. FROM PRODUCTION PLAN TO EXECUTABLE SCHEDULE A produc...

A factory can collect enormous amounts of data and still struggle to answer a basic operational question: what does this event actually affect? ERP knows customer orders, materials, planned dates, and inventory. MES knows what is executing on the shop floor. PLCs and SCADA know machine states, alarms, and process values. Maintenance knows asset condition and service history. Quality knows inspection and release status. Engineering knows the product definition. The problem is not usually a lack ...

Getting machine alarms, sensor values, production counters, and fault events into the cloud is easier than ever. OPC UA exposes the machine signal, an edge layer collects it, MQTT can distribute it locally, and Microsoft Fabric can ingest and analyze the resulting stream. The difficult part starts after the data arrives: how do you turn raw telemetry into enough production context to support an actual decision? This episode follows one machine signal from the factory floor through the Microsoft...

A connected factory can move machine signals in milliseconds and still fail to answer the operational questions that actually matter. A packaging machine stops, the PLC reports the fault, OPC UA exposes the event, MQTT distributes it, and the dashboard updates immediately. Maintenance receives an alert and everything appears connected. Then the planner asks which customer shipment is now at risk, and suddenly the answer requires MES data, ERP records, maintenance history, quality status, product...

Continuous improvement is supposed to create learning that compounds over time. In many factories, however, improvement work still depends heavily on workshops, spreadsheets, isolated reports, and what people remember from the previous shift. A Kaizen event can create visible progress, but a few weeks later the same loss often appears again under slightly different production conditions. The issue is not always the quality of the improvement idea. The bigger problem is that teams often cannot pr...

A temperature reading, a vibration sample, a machine cycle, and a device disconnect may all be described as events, but they do not represent the same architectural problem. In industrial IoT and manufacturing environments, confusing continuous telemetry with discrete events can create noisy workflows, incomplete production histories, unnecessary processing, and systems that react without enough context. In this episode, we break down the architectural difference between Azure IoT Hub Message R...

Your production schedule can look perfectly reasonable when it leaves the ERP system. Order dates line up, routing times make sense, capacity appears available, and material status suggests that production is ready to go. The problem is that the schedule is still only an assumption about the future.The moment production begins, the factory starts generating new facts. Material arrives later than expected, a batch is still waiting for quality inspection, a fixture is unavailable, an operator with...

A machine sends temperature readings, vibration data, cycle counts, power consumption, and operating states every few seconds. Then the gateway suddenly disconnects. Are all of those messages simply “events”? Technically, you could describe them that way. Architecturally, that can create serious problems. Azure IoT Hub Message Routing and Azure Event Grid solve different problems. One path is designed around preserving and distributing operational data. The other is designed around notifying sys...

Cloud storage may look cheap. Sending factory data to the cloud may look cheap. But the real cloud bill often starts when that data begins moving. In this episode, we break down the hidden costs behind modern Industrial IoT, manufacturing cloud, edge computing, and factory data architectures — from data egress and cross-region replication to NAT gateways, backups, dashboards, and high-frequency sensor data. A single MQTT stream from a factory can quickly become multiple data flows once telemetry...

Your ERP can calculate production dates, explode demand through MRP, manage routings, inventory, purchase orders, and production orders. But that does not automatically mean it can create a production schedule that your factory can actually execute. In this episode, we break down the gap between ERP planning and finite production scheduling — and explain why a schedule can look perfectly reasonable in the ERP while multiple orders are competing for the same machine at the same time. THE INFINIT...