In fields with many small measurement points scattered close together, giving every one of them its own long-haul communication link is expensive and unwieldy. A data concentrator solves that by gathering readings from many nearby devices and forwarding them upstream over a single shared link. This guide explains what a data concentrator is, how it works in an oilfield gathering system, and how it differs from a plain protocol gateway.
Data Concentrator in one line: A data concentrator is a field device that collects data from many downstream field devices - RTUs, meters, and sensors - over local links and consolidates it for transmission upstream on a single link to the SCADA host. It acts as a local sub-master and aggregation point, polling or receiving from the devices below it and presenting their combined data upward, which reduces the number of communication paths the central system has to manage.
A data concentrator sits at a point where many measurement devices are clustered - a pad, a gathering hub, or a metering site - and each of those devices connects to it over an inexpensive local link such as a short serial run, a local radio, or a local Ethernet segment. The concentrator continuously gathers their values into a local table, either by polling each device in turn as a local master or by receiving data the devices report to it.
Upstream, the concentrator has a single connection to the SCADA host or to a front-end processor. When the host polls the concentrator, it answers on behalf of everything below it, delivering the whole set of aggregated readings over that one link. This is why a concentrator is sometimes described as a sub-master: it plays the master role toward the small devices beneath it and the slave role toward the central system above it.
By collapsing many links into one, the concentrator cuts communication cost and complexity. Instead of the host maintaining a separate cellular plan, radio path, or licensed circuit for every meter, it maintains one link to the concentrator. That single link carries the traffic that would otherwise have been spread across dozens of connections, and it is often the only device at the cluster with a long-haul radio or cellular modem.
A data concentrator and a protocol gateway are easy to confuse because both sit between field devices and the host, but their jobs are different. A gateway translates between protocols - it lets a device speaking one protocol communicate with a system speaking another - and it generally passes data through without necessarily storing or aggregating it. Its purpose is compatibility.
A data concentrator's purpose is aggregation. It exists to combine data from many devices into one place and one upstream link, and it typically holds that data in a local table so the host can retrieve it all at once. A concentrator may also translate protocols along the way, and many devices do both jobs, but the defining feature of a concentrator is that it collects and consolidates many sources rather than simply relaying one.
Put simply, a gateway answers the question can these two systems talk, while a concentrator answers the question how do I get data from many field points to the host without running many links. In a real installation the same physical box can act as concentrator, gateway, and RTU at once, which is why the terms are often used loosely, but the concentrating role is specifically about many-to-one data aggregation.
A gathering system is a natural home for a data concentrator. On a multi-well pad or at a gathering hub there may be several wellhead controllers, tank level sensors, and flow meters within a short distance of one another. Rather than fitting each with its own cellular link, an operator installs one concentrator that gathers all of them locally and reports the whole pad upward on a single connection. That is cheaper to deploy, cheaper to run, and simpler to manage.
The concentrator also gives the pad a single, consistent point of contact. Firmware and configuration are managed at one device, communication troubleshooting focuses on one link, and the host sees a clean, organized set of tags for the whole cluster rather than a scattering of independent devices. When a new meter is added at the pad, it is wired into the concentrator rather than fitted with its own long-haul path.
For a cloud SCADA platform, the concentrator is what makes a dense field affordable to monitor. A system like Merobix receives one well-organized data stream per cluster instead of contending with a separate connection for every meter, so an operator can bring an entire pad or gathering hub online quickly and watch every point on it from a browser, backed by the concentrator that quietly aggregates the field beneath it.
A gateway translates between protocols so incompatible systems can communicate, usually passing data through. A data concentrator aggregates data from many field devices into one place and forwards it on a single upstream link, typically holding it in a local table. Aggregation is the concentrator's defining role, while translation is the gateway's.
Because it plays two roles at once. Toward the small field devices below it, the concentrator acts as the local master, polling or receiving their data. Toward the central SCADA host above it, it acts as a slave that answers when polled. That in-between position - master downward, slave upward - is what the term sub-master describes.
They are used wherever many measurement points cluster together, such as multi-well pads, gathering hubs, and metering sites. One concentrator gathers all the nearby wellhead controllers, meters, and level sensors over cheap local links and reports them upstream on a single long-haul connection, cutting communication cost and simplifying management of a dense field.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.