Two years ago a mill owner in Punjab told me his rejection rate was 0.8%. He'd held that number for eight quarters. The dashboard said 0.8. The MES said 0.8. The shift reports said 0.8.
Then a shipment came back from the buyer. 4 tonnes of fabric, rejected at destination. The buyer's quality team had measured the real defect rate at the receiving dock. It wasn't 0.8%. It was closer to 6%.
The shipment cost him ₹11 lakh. The data wasn't wrong. His measurement was wrong.
Punjab knitting mill, early 2023. Source: documented internal customer story.
I have now done some version of this calculation on roughly 30 production lines. Different industries, different countries, different MES vendors. The pattern is the same one. The number on the dashboard and the number actually happening on the floor are rarely the same number, and the gap is almost always wider than the operator running the plant believes.
That gap is the thing this whole essay is about. Every modern factory has spent millions on an MES, an ERP, and a stack of dashboards. The honest answer to what is happening on Line 3 right now is still, in nine factories out of ten: let me check.
MES is honest about yesterday. The floor is happening now.
MES is doing exactly what MES was built to do. It records what was produced, by whom, against which work order. The finance team needs that. The auditor needs it. The customer's quality team needs it. Nobody is arguing with MES.
What MES is not built to do is tell you what is happening on the floor in the next thirty seconds.
The reason isn't laziness or bad software. It's structural. MES updates on operator entries. Operators are honest, but they are not stenographers. The nine-minute stop at 3:14 a.m. gets logged as "around five." The changeover that ran twelve minutes long gets logged as on-time, because the line technically restarted before the shift ended. The MES isn't lying. It's recording what it was told.
That gap — between what the floor did and what the floor logged — is the gap Connected Factory Intelligence lives in.
What I mean when I say "Connected"
I don't mean integrated dashboards. I don't mean an API into MES. Almost every platform I have looked at uses the word "connected" to mean we have a SAP connector. That's not connection. That's a button.
What I mean is the system is watching the floor through three independent channels at the same time and reconciling them in real time.
The first channel is your cameras. You already have them. Most factories I walk into have between 50 and 300 IP cameras already streaming somewhere. They record into a VMS, the storage fills up, and once every few months somebody scrolls back to investigate an incident. Run AI on those same RTSP streams and the cameras stop being a tape recorder. They become the cheapest and most general-purpose sensor in your plant — one that sees product on the conveyor, operators at their stations, PPE on bodies, stoppages, idle time, anomalies nobody wrote a rule for. CCTV-GPT is the part of our platform that handles this channel.
The second channel is your machines. PLC tags over OPC UA. Cycle counts. Temperature. Vibration. Current draw. Energy. The data is already there. The bottleneck in most plants isn't the sensors — it's that the streams don't fuse into a coherent state anywhere.
The third channel is your enterprise systems. SAP, Oracle, Plex, Aveva, whatever your MES happens to be. The vision and the PLC data tell you what the factory is doing. ERP and MES tell you what it's supposed to be doing. You need both, reconciled live.
The last piece — the one most analytics projects get wrong — is rendering the result by role. Operator sees the alert in the moment. Supervisor sees the shift. Plant manager sees the cross-line. GM sees the cross-plant. CFO sees variance to plan. Same underlying data. Five different views, with the latency and aggregation each role actually needs.
One dashboard for everyone is the most common failure mode in this category. It serves no one well.
MES is a system of record. Connected Factory Intelligence is a system of signal. You need both. The first is honest about what happened yesterday. The second is honest about what is happening now.
The reported number and the real number are almost never the same number
The Punjab story is the canonical version of this problem, but the underlying pattern repeats almost everywhere we put cameras alongside an MES. The number on the dashboard is what the operator entered. The number on the floor is what the cameras saw. The two rarely match.
This is not a criticism of the operator or the MES. It is the structural limit of operator-entered data. Small stops disappear. Changeovers compress. Night shifts under-report. Multiply a few minutes per station, by a few stations per line, by three shifts, by 250 working days, and the difference between the two numbers is the most expensive number in the plant — and nobody is looking at it.
The first month of any honest Connected Factory Intelligence deployment isn't about features. It is about which version of your number you are going to defend in the next board meeting.
Why this is finally happening in 2026
Industry 4.0 has been a phrase for fifteen years. For most of those years, it meant a multi-year transformation program with eight-figure capital exposure and a vendor who wanted to replace half the stack. Most CFOs killed those projects, correctly.
The deployment model changed in the last two years. The version I run now looks like this:
The cameras stay. The VMS stays. The PLCs stay. The MES and ERP stay. The only new thing on the capital plan is an on-premise edge server per site, running inference and reconciliation. Live in a week. Pays back in a quarter.
That is the architecture I have shipped across more than 4,500 industrial cameras and 500-plus production machines across seven countries — mostly in textile so far, because that is the vertical where I started. The same architecture, the same edge-first stack, is what I am now bringing to plants in the US, UK and Australia who have a similar problem (an MES that under-observes the floor) and a similar existing stack (cameras already there, mostly doing nothing useful).
Edge, not cloud. Don't take a "we do both" answer.
If a vendor offers you cloud-first AI for the factory floor in 2026, they are selling you the 2018 architecture.
Three reasons. A stoppage alert that arrives 30 seconds late is operationally useless. Streaming hundreds of HD camera feeds to a cloud GPU is technically possible and economically absurd. And video of workers, processed offsite, is a GDPR / UK DPA / Australian Privacy Principles conversation your legal team will not enjoy.
The platforms that work in production keep the video on the floor. The only thing that leaves is metadata — events, counts, snapshots, with faces blurred where the local regulator requires it.
When you talk to a vendor, ask them: where does the raw video physically rest at the end of every hop? If any of the hops are outside your perimeter, that is a problem you don't want to inherit.
Want to see the gap on a line that isn't yours yet?
Start with a 30-minute call. I'll walk you through the MES-reported vs camera-observed numbers from real deployments (anonymised), and we'll sketch what the same comparison would look like on one of your own lines — no RTSP access required for the conversation. If the math is interesting enough that you want to run it on your own data, we move to a paid 4-week pilot with one of your lines. If it isn't, you have walked away with a sharper way to evaluate any vendor in this space.
Email Harsha directly →Goes to my inbox. Usually replies the same day.
What I would do if I were you, on Monday
Pick one line. Not the plant. Not OEE in the abstract. One line, one shift, one number you want to be able to defend.
Then ask the person who would run the project two questions. Are the cameras already pointing at that line? Do you have a network drop in the IT closet for an edge server? If the answer is yes and yes, you have everything you need to run a 14-day pilot. The rest is software.
The factories that get this right in 2026 will operate on a live signal on every line within a year. The ones that wait will keep making decisions about what to produce next based on shift-end reports — data from operations that already finished.
Frequently asked questions
So what is Connected Factory Intelligence, in plain English?
It is the live decision layer above your MES and ERP. The cameras already in your plant, the PLCs already on your machines, the MES and ERP you already paid for — the platform reads from all of them and reconciles what they are saying, in real time, against what is actually happening on the floor. The result is a single live picture of the plant that the operator, supervisor, plant manager, GM and CFO each see in the way that is useful for their job.
How is it different from MES?
MES is a system of record. It is honest about what was logged. Connected Factory Intelligence is a system of signal. It is honest about what is happening right now. You need both. The MES is your source of truth for traceability, audits, and finance. The intelligence layer is what you act on between now and the next shift change.
Does it replace MES or ERP?
No. I will not even quote you a price on that conversation because it is the wrong conversation. Your MES stays. Your ERP stays. The intelligence layer runs alongside them and, frankly, makes both of them more useful by feeding cleaner data back in.
What kind of factories does this work in?
Any plant with three things. Continuous or semi-continuous output. An MES or ERP already in place. Cameras and sensors already installed that aren't doing as much as they could. That is most modern manufacturers — textile, packaging, food, automotive components, pharma, paper, glass, electronics assembly. The architecture is the same regardless of vertical.
Why does it have to run at the edge?
Three reasons I have learned the hard way. A stoppage alert that arrives 30 seconds late is operationally useless. Streaming hundreds of HD camera feeds to a cloud GPU is technically possible and economically absurd. And the conversation your privacy team will have about worker footage processed in someone else's data centre will end the project. Edge inference is the only architecture that survives all three.
Curious how Connected Factory Intelligence ties together with vision-based defect detection and CCTV analytics? Read about Fac-AI, our intelligence platform, or CCTV-GPT, our AI retrofit layer for existing factory cameras. Or read why CCTV is the most underused asset on your factory floor.