The automation visibility gap: why FactoryOps is becoming the missing layer in manufacturing stacks

A plant can run robots, programmable controllers, and supervisory software across every line and still not know, in real time, why a machine went down or how much production it lost during the last shift. That gap is well documented and, in 2026, increasingly costly.

Guidewheel, a manufacturing operations software company, published a detailed map of the modern industrial automation stack this month, laying out why automation and visibility are not the same thing and where a newer category of software, called FactoryOps, fits in. The piece, authored by Lauren Dunford, is aimed squarely at plant and operations leaders evaluating where to invest next.

The stack most plants already have

Industrial automation in 2026 is best understood as a set of accumulated layers rather than a single system. PLCs, which replaced hardwired relay logic starting in the late 1960s under what became the IEC 61131 standard, handle real-time machine control and sequencing. SCADA and HMI systems give engineers and control-room operators a supervisory view across a line or site. MES, formalized under the ISA-95 standard, connects the floor to scheduling, work orders, and production tracking. IIoT connectivity moves machine data up to cloud analytics platforms.

Each layer solved a real problem. None of them was designed to give a shift supervisor or a regional VP a single, live view of what every machine is doing right now. That's the gap FactoryOps is built to close.

Why siloed data persists despite sophisticated controls

Rockwell Automation's State of Smart Manufacturing report found that more than half of plants still rely on spreadsheets or manual entry for production, downtime, and scrap data, even at facilities with significant automation already in place. The finding points to a structural problem: PLCs produce control data, SCADA produces supervisory data, and MES produces order-and-WIP data, but these streams often sit in separate systems that don't share a common timestamp or definition of a production event.

The result is what operations teams know as the Monday morning data fight, where shift logs, MES reports, and supervisor memory produce conflicting accounts of what actually happened the week before. Decisions get made on stale or disputed numbers, and the real cost of downtime stays invisible until it shows up in margin.

What FactoryOps adds and where it sits

FactoryOps platforms sit between the plant floor and ERP. Rather than replacing PLCs, SCADA, or MES, they read each machine's electrical signature through clip-on current sensors and convert that signal into live operational data: uptime, downtime, cycle time, scrap counts, and OEE. Alerts push to operators and supervisors the moment a machine stops, rather than surfacing the loss hours later in a report.

Guidewheel's own implementation data describes sensors being installed and producing data in roughly 40 minutes, with complete line setups live within a day or two of receiving hardware. The non-invasive sensor approach means no PLC reprogramming, no OT network configuration, and no dependency on a machine's age or brand. A 20-year-old press and a recently installed CNC both look the same to a current sensor.

The company reports one customer facility reduced average lost production time from four hours to under 1.5 hours within two months of deployment, a 62% reduction, by enabling faster response to machine stops. The same visibility also flags idle-but-running equipment, which surfaces an energy reduction opportunity alongside the throughput gain.

Where the FactoryOps layer fits in the full stack

• Sensors and I/O: measure variables and execute actions, but provide no historical context on their own.
• PLCs: handle real-time control and sequencing, but are not designed for long-term analytics.
• Drives: control motor speed and torque, but don't surface performance trends.
• HMIs: give operators a local screen view, but offer no cross-line or cross-shift picture.
• SCADA: supervises machines across a line or site, but lacks order and WIP context.
• MES: tracks orders, WIP, and quality, but doesn't capture granular machine-state data.
• IIoT connectivity: moves machine data to the cloud, but doesn't produce floor-ready action.
• FactoryOps: delivers real-time uptime, downtime, cycle time, and OEE visibility to operators, supervisors, and leaders, but is not a replacement for ERP or MES.

Who the layer is built for

Guidewheel positions the FactoryOps layer for mid-market to enterprise manufacturers running multi-shift, production-heavy operations with mixed equipment fleets. The target condition is straightforward: facilities where an unplanned stop on one machine can cascade into a missed delivery commitment or a margin variance that only appears at month-end.

The practical entry test the company suggests is blunt. If the team is still walking the floor to collect downtime and scrap data by hand at the end of a shift, the visibility layer is the next investment worth evaluating, regardless of how much automation already runs underneath it.

What this means for your team

• Audit your data collection process: if shift-end production, downtime, or scrap numbers are collected manually, you have a visibility gap that PLCs and SCADA were not designed to fill.
• Evaluate FactoryOps platforms against your existing control stack before buying new machines or upgrading PLCs. The visibility ROI can arrive faster and with less integration friction.
• Confirm sensor compatibility with your oldest equipment first. Non-invasive current sensors attach to the power line, so machine age and brand are not barriers, but verifying that assumption with a vendor demo on legacy assets is worth the time.
• Set a response-time benchmark for machine stops today. If average time-to-response is measured in hours, use that as the baseline for any FactoryOps pilot evaluation.