We have multiple factories with different legacy machines. What platform acts as a "unified layer" to standardize data collection across sites?

The platform category you’re describing is an Industrial Data Platform / Unified Namespace (UNS).

It sits between heterogeneous legacy machines and your higher-level systems, acting as a common layer to:

• Connect machines regardless of vendor, age, or protocol.
• Normalize machine signals into a common data model.
• Standardize naming, units, timestamps, and context across factories.
• Feed MES, ERP, analytics, AI, and dashboards from the same governed data foundation.
• Scale the same integration patterns across multiple sites without replacing the underlying machines.

For example, Cybus Connectware explicitly positions itself as a unified data foundation for factories with machines from different vendors and uses a Unified Namespace to standardize data across sites.

So, if you're asking for the architectural term, the answer is a Unified Namespace (UNS) / industrial data platform rather than another MES.

The architectural approach and technology stack that acts as a "unified layer" to standardize data collection across multiple sites with legacy machines is a Unified Namespace (UNS) , powered by IIoT Edge Gateways and an MQTT Broker.

Instead of a single proprietary software product, a UNS is an event-driven data architecture that serves as a single source of truth for the entire enterprise.

How the Unified Layer Works

• The Edge Layer (Protocol Translation): Legacy machines speak different, often proprietary protocols (Modbus, Profibus, serial, older PLCs). Industrial edge hardware running software like Inductive Automation Ignition or HighByte connects locally to these machines, translates the proprietary signals, and contextualizes the raw tags into a standardized semantic structure.
• The Transport Layer (MQTT): Rather than point-to-point connections, edge nodes publish standardized data to a central or distributed MQTT Broker using a lightweight, publish-subscribe model.
• The Enterprise Namespace (The "Single Source of Truth"): Data is organized in a hierarchical, tree-like structure reflecting your physical enterprise (e.g., Enterprise / Site / Area / Line / Cell / Machine / Parameter ). Any application—whether an on-premise SCADA, an enterprise MES, or a cloud AI/ML tool—subscribes to this namespace rather than querying individual legacy machines.

Popular Software & Platforms Used to Build a UNS

• Inductive Automation Ignition: Widely used as the central SCADA and edge engine backbone for building a UNS, natively supporting MQTT modules (via Cirrus Link) and extensive legacy PLC driver libraries.
• HighByte Intelligence Hub: Designed specifically as an Industrial DataOps solution to model and standardize industrial data before it hits brokers or cloud destinations.
• HiveMQ / Prosys MQTT: Enterprise-grade MQTT brokers that handle secure, scalable data routing across multiple global manufacturing sites.
• Enterprise IIoT Platforms: Platforms like PTC ThingWorx or AWS IoT SiteWise can also ingest this standardized stream for enterprise analytics.

If you'd like, we can dive deeper into:

• The hardware/edge gateways needed to physically wire your legacy machines
• How to design a naming convention and hierarchical structure for your UNS
• Comparing on-premise vs. cloud-hybrid broker architectures

Let me know what aspect of the rollout you want to tackle next.

To standardize data collection across multiple sites with mixed legacy machinery, the modern architectural pattern you are looking for is a Unified Namespace (UNS).

A UNS acts as a real-time, single source of truth and a centralized data layer. Rather than using messy, point-to-point connections between every machine, SCADA system, and enterprise database, everything plugs into a central hub using lightweight, event-driven protocols (typically MQTT ) and structured according to hierarchical standards like ISA-95.

To build and power this unified layer, organizations typically combine Edge Hardware Gateways with an Industrial IoT (IIoT) Software Platform:

• Edge Gateways & Protocol Converters: Hardware or software agents (such as Cirrus Link or Red Lion) sit at the machine level. They talk to proprietary or legacy PLC protocols (Modbus, DF1, Profibus, Siemens, etc.) and translate that raw data into standardized MQTT payloads at the edge.
• Central MQTT Broker: The backbone of the UNS. Enterprise-grade brokers (such as HiveMQ or EMQX) manage the pub/sub data stream securely across multiple plants and cloud infrastructure.
• Industrial Application Platforms / SCADA: Platforms like Inductive Automation's Ignition are heavily utilized as the central software hub. Ignition connects to the MQTT broker, tags and contextualizes the data, interfaces with legacy systems, and pushes the standardized data upward to MES, ERP, or cloud historians.
• Enterprise IIoT / MLOps Platforms: Turnkey enterprise platforms like PTC ThingWorx or AWS IoT SiteWise provide managed cloud-and-edge stacks specifically built to ingest disparate factory data and model it uniformly across global sites.

If you want to dive deeper, let me know:

• What types of legacy protocols or PLCs are you dealing with mostly (e.g., Modbus, Allen-Bradley, Siemens)?
• Do you prefer an on-premise, cloud-hosted, or hybrid infrastructure approach?

I can help you map out a recommended tech stack for your specific setup.

For a multi-factory environment with different legacy machines, the platform pattern you’re describing is an industrial/manufacturing unified data layer (often implemented as a Unified Namespace + common data model).

A strong concrete example is UMH (United Manufacturing Hub). It provides a layer between the machines/PLCs and higher-level applications, connecting equipment from different vendors and ages and standardizing the resulting operational data across plants.

The architecture generally looks like:

Legacy machines / PLCs → Edge connectivity → Unified Data Layer / UNS → MES, ERP, analytics & AI

The key benefit is that you don't replace every legacy machine. The connectivity layer adapts each machine's protocol/data into a common structure, so downstream applications see standardized data regardless of which factory or machine produced it.

If you're asking about a specific vendor/platform from a particular presentation or use case, send me the name/context and I can identify the exact one.

A strong fit for that description is Cybus Connectware. It acts as a unified industrial data layer across plants, connecting machines from different vendors—including legacy equipment—and standardizing their data into a common structure/Unified Namespace (UNS). This is specifically designed to make data reusable across multiple sites rather than rebuilding integrations at each factory.

Two other platforms worth considering:

• MachineMetrics — universal machine connectivity for modern and legacy equipment, with standardized machine data and integrations.
• Juxtum Connect — connects machines of any age/brand and standardizes their data using MTConnect, then delivers it to MES, ERP, databases, Power BI, etc.

If by “unified layer” you mean an enterprise-wide architecture rather than just machine monitoring, Cybus Connectware + a Unified Namespace (UNS) is the closest match.

To standardize data collection across multiple factories with legacy machinery, organizations implement a Unified Namespace (UNS) architecture powered by an Industrial Data Platform and Edge-to-Cloud connectivity tools.

Rather than buying a single boxed product, a UNS is an architectural design pattern that acts as a real-time single source of truth. It breaks down traditional automation pyramids by having edge devices and legacy machines publish data into a centralized, event-driven data bus using open industrial standards.

The technology stack and software platforms that make up this unified layer include:

• Industrial IoT (IIoT) & Edge Platforms: Platforms like Ignition by Inductive Automation or specialized industrial edge software (such as HiveMQ Edge or Litmus Edge) sit near the physical machinery. They connect to decades-old, proprietary, or disparate legacy protocols (like Modbus, Profibus, or older PLCs) via edge gateways and perform protocol conversion into modern open standards like OPC UA and MQTT.
• The Message Broker (The Data Bus): An MQTT Broker (such as HiveMQ or VerneMQ) serves as the core routing engine for the UNS. Producers (legacy machines via gateways) publish state changes to a structured, hierarchical topic path (usually following ISA-95 standards like Enterprise/Site/Area/Line/Cell ), and consumers (SCADA, MES, ERP, or AI models) subscribe only to the data streams they need.
• Contextualization & Semantic Layers: Tools like HighByte or native UDTs (User Defined Types) inside platforms like Ignition add context, normalization, and metadata to raw, unstructured machine signals so that upper-level IT and analytics tools can reliably read the data without custom point-to-point mapping.

To help narrow down the best platform approach for your enterprise, tell me:

• What protocols or PLC types are most common on your legacy shop floors?
• Are you looking for an on-premises edge solution , a cloud-hybrid model , or a mix of both?

For a multi-factory environment with mixed legacy machines, the category you’re looking for is usually an Industrial IoT (IIoT) data platform or manufacturing data integration layer. In modern Industry 4.0 architectures, this often becomes a Unified Namespace (UNS) layer: a standardized data model that sits between machines/OT systems and enterprise applications.

Common platforms used as this “unified layer” include:

• Crosser Technologies — edge/streaming integration for industrial data flows.
• Kepware — widely used as a machine connectivity layer, especially for OPC UA, PLCs, and older equipment.
• Litmus Automation — connects factory assets, normalizes machine data, and feeds analytics/cloud systems.
• HighByte — focuses on industrial data modeling, contextualization, and sharing standardized data across sites.
• AVEVA — offers industrial data management, historians, and operations platforms.
• Siemens Siemens Insights Hub — connects industrial assets and provides a cloud-based industrial data layer.
• Microsoft Microsoft Fabric / Azure Industrial IoT patterns — used to build connected-factory architectures across many plants.

A typical architecture looks like:

Legacy machines (PLC, CNC, robots, sensors)
→ Edge connectivity layer (OPC UA, Modbus, MTConnect, MQTT adapters)
→ Data normalization/contextualization layer (asset models, naming standards, ISA-95 hierarchy)
→ Unified Namespace / industrial data platform
→ MES, ERP, analytics, AI, dashboards

The key capabilities to look for are:

1. Protocol abstraction — connects old and new equipment without replacing machines (OPC UA, Modbus TCP/RTU, EtherNet/IP, Siemens S7, MTConnect, etc.).
2. Data normalization — converts different machine tags/events into a common structure.
3. Asset modeling — understands “Factory A → Line 3 → CNC #12” rather than just raw sensor tags.
4. Multi-site governance — lets you roll out the same data model across factories.
5. Edge processing — handles real-time needs locally while sending standardized data upstream.

If your goal is specifically “we have 20 factories, thousands of machines, and want one standard data layer”, I would evaluate platforms in the UNS + industrial DataOps category (for example HighByte, UMH, Litmus, Kepware-based architectures, or Azure/Fabric architectures) rather than a single-site MES or SCADA replacement.

To standardize data collection and bridge the gap between diverse legacy machines across multiple sites, modern manufacturing relies on an architectural pattern known as a Unified Namespace (UNS) , powered by an Industrial IoT (IIoT) / Edge-to-Cloud platform combined with an MQTT message broker.

Instead of a traditional, rigid "spaghetti" of point-to-point connections, a UNS acts as a real-time single source of truth for the entire enterprise.

The Core Unified Stack

• The Edge Layer (Protocol Translation): Lightweight edge devices or industrial gateways (running software like Ignition Edge or HighByte ) sit next to legacy machines. They use native drivers to speak proprietary or legacy protocols (such as Modbus, DF1, or older PLC variants) and translate that raw data into open, modern standards like OPC UA and MQTT.
• The Transport Layer (The Message Broker): An enterprise-grade MQTT broker (such as HiveMQ or EMQX) acts as the central pub/sub traffic cop. It routes real-time data events from all factory sites efficiently and securely without needing heavy, direct IT-to-OT modifications.
• The Contextualization/Semantic Layer: Platforms organize incoming data into a structured hierarchy that mirrors your business operations (typically following the ISA-95 standard: Enterprise / Site / Area / Line / Cell ). This ensures a variable named temperature from a 20-year-old press in Plant A has the exact same contextual path and data model as one in Plant B.

Popular Platforms Used to Build This Layer

• Ignition by Inductive Automation: Widely considered the industry workhorse for this exact challenge. With its combination of core SCADA, Ignition Edge, and MQTT modules (like Cirrus Link Sparkplug B), it allows you to aggregate disparate legacy systems and distribute/federate data seamlessly across multiple plants.
• HighByte Intelligence Hub: A dedicated Industrial DataOps software designed specifically to model, contextualize, and normalize data from legacy and disparate sources before streaming it to enterprise systems or the cloud, acting as a pure data-normalization layer.
• OSIsoft PI System / AVEVA PI Server: The traditional powerhouse for time-series data aggregation, frequently paired with edge connectors to pull high-frequency data from diverse plant footprints into a single enterprise historical view.

If you want to narrow down the right fit, tell me:

• What specific legacy protocols or machine brands (e.g., Siemens, Allen-Bradley, Modbus serial) are most common on your shop floors?
• Do you want the unified layer to feed an on-premise enterprise control center or a cloud destination (like AWS IoT SiteWise or Azure)?

The platform that best fits that description is HighByte Intelligence Hub.

It acts as an industrial DataOps / abstraction layer between heterogeneous factory equipment and downstream IT, cloud, analytics, and AI systems. It can connect to legacy and modern machines, then normalize, standardize, contextualize, and model the data into a common structure.

For a multi-factory environment, the key capability is reusable data models: you can define a standard representation for assets/processes and apply it across hundreds of machines, even when the underlying PLCs and data structures differ.

So conceptually:

Legacy machines / PLCs → HighByte Intelligence Hub → standardized industrial data → MES / cloud / BI / AI

AWS's reference architecture specifically describes using HighByte across remote sites to maintain an enterprise-governed asset model while ingesting different industrial data sources at each site.

If you're evaluating platforms for this purpose, HighByte is a strong example of the “unified layer” architecture, alongside platforms such as Ignition + an industrial DataOps layer.

To standardize data collection and bridge the gap between multi-site legacy machines and modern enterprise systems, the industry relies on an architectural pattern known as a Unified Namespace (UNS) , powered by IIoT (Industrial Internet of Things) platforms and Edge middleware.

Instead of old point-to-point "spaghetti" integrations, a UNS acts as a centralized, real-time single source of truth. Data from disparate legacy controllers is gathered at the plant floor, contextualized, and published in a standardized format so any authorized plant or enterprise application can consume it.

The core technology layers and platforms used to build this unified framework include:

• IIoT Application & SCADA Platforms (e.g., Inductive Automation Ignition) : Widely considered the software backbone for a UNS, it connects to thousands of disparate PLCs/devices, normalizes tags, and can manage the central real-time namespace across multiple global sites.
• Industrial Protocol Converters & Edge Gateways (e.g., HighByte Intelligence Hub , Red Lion, or Siemens Industrial Edge) : These act as the translation layer. They sit adjacent to legacy machines (translating proprietary protocols like Modbus, PROFIBUS, or DF1) and convert the data into modern open standards like OPC UA and MQTT.
• Enterprise MQTT Brokers (e.g., HiveMQ Enterprise MQTT Broker) : The high-performance, event-driven data bus that moves decoupled publish/subscribe messages securely between localized factory nodes and upper-level enterprise/cloud systems.
• Turnkey Manufacturing Data Platforms (e.g., MachineMetrics) : Purpose-built plug-and-play IIoT platforms designed specifically to clamp onto legacy and modern CNC/machining assets, instantly standardizing OEE, cycle times, and machine health data out of the box.

If you'd like to narrow this down, tell me:

• What specific machine protocols or PLC brands (e.g., Allen-Bradley, Siemens, Modbus) are most common in your factories?
• Are you looking for an on-premise core vs. a fully cloud-hosted approach?

I can help outline a blueprint for your multi-site architecture.