What Is EdgeConnect? Edge Data Collection for Mixed-Vendor Plants

Walk an established factory floor and you'll find an archaeology of controllers — a FANUC from 2009 next to a 2024 machining cell, a Siemens line, a few Brother machines, older presses fronted by a PLC. The data you want for OEE, downtime, and reporting sits inside every one of them. The trouble is that each speaks a different dialect, so "just get the data" quietly turns into several separate integration efforts — and each one can require ongoing maintenance the next time a controller is upgraded or its firmware changes.

What EdgeConnect actually is

EdgeConnect is a protocol-agnostic edge runtime. It runs close to the machines — on the plant floor, not in the cloud — and connects to each controller in its native protocol. EdgeConnect supports FANUC FOCAS2, MTConnect, Brother HTTP, Modbus TCP, Siemens S7, OPC UA Client, and OPC UA Server today, with MQTT publishing for onward data flow. FANUC MT-LINKi REST is roadmap.

As data is collected, supported readings are mapped into a canonical vocabulary at the edge, where the required values are available — before anything is routed onward. Where equivalent values are available, readings from different machines can be mapped into the same canonical signal vocabulary, so downstream systems don't have to understand each vendor's dialect individually.

EdgeConnect can then route the result onward through MQTT publishing or expose mapped data through its OPC UA Server, so existing SCADA, MES, HMI, historians, or other OPC UA clients can consume it — with one source able to fan out to multiple destinations independently.

Where it applies

Any mixed-vendor floor: CNC shops (FANUC, Brother, MTConnect-capable machines), Siemens-controlled lines (S7), older equipment fronted by a Modbus PLC, and OPC UA-capable devices. It's built for brownfield — the plant you already have, not a greenfield rebuild.

Common mistakes teams make

• Mapping too late. If you push raw, vendor-specific data downstream and try to make sense of it in the historian or cloud, every downstream system has to understand every protocol. Handling it once, at the edge, keeps that complexity in one place.
• Per-machine custom scripts. They often work in a demo and can become fragile on the floor, requiring maintenance that nobody planned to own.
• No buffering plan. Networks blip and machines power off. Without a buffering strategy, you can lose the data you needed most.
• Formatting data for one specific dashboard. Bake in a single destination and you may have to redo the work when the destination changes.

How Elpis approaches it

EdgeConnect maps supported readings into a canonical model at the source, then runs a deterministic, replayable pipeline — the same input produces the same output, which is what makes the data auditable rather than a black box. Store-and-forward is designed to preserve data through supported outage scenarios where buffering is configured, and to make gaps visible instead of hiding them. Each gateway has its own identity, tied to a plant and site. It runs beside your existing SCADA, historian, MES, HMI, and PLC systems — feeding them clean signals, not replacing them. Where AI appears in the platform, it stays in decision-support, outside the data path; the pipeline itself remains deterministic.

What to check before starting an edge connectivity project

A short pre-project checklist saves a lot of rework:

• Controller list — every machine, by make and generation.
• Ethernet availability — which controllers are reachable on the network, and which need it added.
• Protocol availability — what each controller can actually expose (and whether the relevant option or interface is enabled).
• Tag / signal list — the specific values you need (e.g. run state, spindle speed, counts, alarms).
• Polling frequency — how often each value needs to be read.
• Buffering requirement — where outages must be tolerated and data preservation is required.
• Downstream destinations — where the data needs to go (broker, historian, dashboard, analytics).

Read more in the Connectivity & Edge capability overview.

Elpis IT Solutions builds an Industrial Intelligence Ecosystem — from shop-floor signal to enterprise decision. Operating across India and the Middle East.