Before anyone specifies a remote terminal unit for a wellsite, they have to answer a plain question: how many signals does this well actually produce, and how many does it need to receive? That tally is the I/O count, and it drives which RTU model you buy, how the enclosure is wired, and how much room you leave for the future. This guide walks through the analog and discrete points a typical single-well RTU handles, why engineers deliberately leave spare points unused, and how the final count decides the hardware.
Wellhead RTU I/O Count in one line: A wellhead RTU I/O count is the tally of input and output points a wellsite terminal unit must handle: analog inputs for measured values like tubing, casing, and line pressure and temperature, and discrete inputs and outputs for on/off states like valve position, ESD status, and shutdown commands. Engineers size the count with roughly twenty percent spare points on hand and choose an RTU model whose channel capacity covers the total with margin.
The analog inputs are the continuously varying measurements. On a single producing well the common set is tubing pressure, casing pressure, and flow-line pressure, often with one or more temperatures - flow-line temperature, and on heated sites a heater or bath temperature. Add a transmitter for differential pressure or flow if the site meters gas locally, and perhaps a tank or vessel level, and a modest well quickly needs a handful of analog channels. Each of these arrives as a current-loop or voltage signal that the RTU digitizes, scales into engineering units, and either acts on locally or reports to the host.
The discrete points are the two-state signals. Discrete inputs report status: whether a surface safety valve is open or closed, whether an ESD system is tripped, whether a plunger has arrived, whether an intrusion switch or low-battery contact is made. Discrete outputs carry commands the other way: a relay that opens or closes a motor valve, energizes a solenoid, or resets a trip. A wellsite with a plunger controller, a safety valve, and a couple of status contacts can easily run to several discretes in each direction. Tallying the analog and discrete points separately, in and out, gives the raw I/O count the RTU must satisfy.
Almost no experienced integrator fills every channel on a new RTU. Leaving roughly twenty percent of the points unused is standard practice, and it pays for itself the first time the site changes. Wells get instrumented more heavily over their life: a chemical injection rate signal gets added, a second pressure point becomes useful, a new valve needs a status contact, or a metering upgrade brings a flow transmitter. If every channel is already committed, each of those additions means a new I/O card, a wiring rework, or a whole new RTU - an expensive truck roll for what should be a terminal-block change.
Spare capacity also absorbs the reality that field wiring is imperfect. Channels fail, terminal blocks corrode, and a technician needs somewhere to move a signal without waiting for parts. Carrying spare analog and discrete points on the installed RTU means a field fix can be a jumper move rather than a hardware order. The twenty percent figure is a rule of thumb rather than a code requirement, but the principle behind it is firm: size for the well you will have in a few years, not only the well you are commissioning today, because the marginal cost of a few spare points at install time is trivial next to a return trip later.
Once the point count plus spare is settled, it maps almost directly onto hardware. Every RTU model publishes a channel capacity - so many analog inputs, so many discrete inputs and outputs, often expandable with add-on cards. A well that needs six analog inputs and eight discretes plus spare might fit a compact fixed-I/O controller, while a multi-well pad or a site with heavy metering pushes into a larger modular unit with expansion slots. Getting the count right before selection avoids the two classic mistakes: buying a unit too small to grow into, or over-buying a large chassis where a small one would have served for years.
The I/O count also sets how much data the site pushes upstream. Every analog point becomes a trended value and a set of alarm limits; every discrete becomes a status and an event in the historian. With a cloud SCADA platform such as Merobix, the same points wired into the RTU appear as tags an engineer configures once and then sees across the whole field from a browser - pressures trending, valve states changing, ESD status live - without a poll list to maintain on a local server. Because spare points are already terminated in the enclosure, bringing a new signal online is often just a configuration change in the cloud rather than a hardware project, so a well-sized I/O count keeps the field flexible long after commissioning.
It varies with how the well is instrumented, but a common producing well runs a handful of analog inputs - tubing, casing, and line pressure plus a temperature or two - and several discretes for valve status, ESD state, and shutdown commands. Heavily instrumented or metered sites need more, and multi-well pads multiply the count. The right approach is to list every measured value and every on/off signal the site actually has, then add spare.
Because wells almost always gain instrumentation over their life - a new pressure point, a chemical injection signal, a valve status, or a metering upgrade. If every channel is already used, each addition forces a new I/O card or a whole new RTU and a truck roll. Carrying roughly twenty percent spare lets those changes be a terminal-block or configuration job instead, and gives technicians somewhere to move a signal when a channel fails.
Largely, yes. Each RTU model has a published capacity for analog and discrete channels, sometimes expandable with add-on cards, so the total point count plus spare tells you whether a compact fixed-I/O unit will do or whether you need a larger modular chassis. Settling the count before selection avoids both under-buying a unit you cannot grow into and over-buying a large chassis a small one would have covered.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.