A net oil computer is the device that takes a measured total liquid flow rate and a live water-cut measurement from the same stream and combines them to report how much of that liquid is oil and how much is water, moment by moment. During a well test it is what converts a raw gross liquid rate into the numbers that actually matter for allocation and reservoir management - net oil and net water. This page explains the simple calculation it performs, why it needs a good water-cut input, and how it fits into automated well testing.
Net Oil Computer in one line: A net oil computer is an instrument or software function that multiplies a measured total liquid flow rate by the oil and water fractions from a live water-cut measurement to compute net oil and net water rates in real time, typically during a well test. It turns a gross liquid measurement into the split that production accounting needs, so its accuracy depends jointly on the flow meter and on the water-cut reading, and it usually accumulates the results into volumes over the duration of a test.
At its heart a net oil computer does something conceptually simple. It receives two live inputs from the same liquid stream: the total, or gross, liquid flow rate from a flow meter, and the water cut - the fraction of that liquid that is water - from a water-cut meter. Multiplying the gross rate by the water fraction gives the net water rate, and multiplying it by the remaining oil fraction gives the net oil rate. Everything else the computer does is built on that basic decomposition of one liquid stream into its oil and water parts.
The reason a dedicated computer is worth having is that both inputs change continuously and must be combined instant by instant, not averaged separately. A well being tested does not produce at a perfectly steady rate or a constant water cut - slugging, changing conditions, and separator behavior all make both signals move. Because the split has to be computed on the live values and then integrated over time, a simple back-of-envelope multiplication of average rate by average water cut can be misleading; the computer does the continuous calculation so the accumulated oil and water volumes are correct even when the stream is unsteady.
The computer typically reports both instantaneous net oil and net water rates and running totals accumulated over the test period. Those totals are the deliverable of a well test - how many barrels of oil and how many of water a well made over the test window - and they feed directly into production allocation, where a field's total measured sales are divided back among wells according to how each tested. The net oil computer is the piece that produces those per-well oil and water numbers.
A net oil computer is only as good as its water-cut input, and this is where most of its error budget lives. Because net oil is the total liquid multiplied by the oil fraction, an error in water cut translates directly into an error in reported oil - and the sensitivity is worst exactly where it matters most. On a high-water-cut well, where oil is a small slice of a mostly-water stream, a small absolute error in the water-cut reading becomes a large percentage error in the tiny oil number, because that oil is the difference between two much larger quantities.
That sensitivity is why the water-cut measurement feeding a net oil computer gets so much attention. The water-cut meter must handle the emulsions, salinity changes, and flow regimes of real produced fluids, because if it misreads the water fraction, the net oil computer faithfully turns that misreading into a wrong oil allocation. The flow meter matters too, and a Coriolis meter is often favored because it also gives density, which can help characterize the fluid, but the water-cut term is usually the dominant uncertainty on watery wells.
It also means a net oil computer is not a way to escape the difficulty of measuring water cut - it is a way to use that measurement to produce net rates. The device does the arithmetic reliably; the engineering challenge is feeding it a trustworthy water-cut value across the full range of the well's life, from low water cut early on to very high water cut later. Getting the split right is a measurement problem in the water-cut instrument as much as in the computer that combines it with flow.
In modern field operations the net oil computer is usually part of an automated test separator or a multiphase test package rather than a standalone box. When a well is routed to test, the separator or metering skid measures the liquid flow and water cut, the net oil computer combines them, and the resulting net oil and net water totals are recorded for the test - all without anyone manually gauging tanks or timing flow into a vessel. This turns well testing from a labor-intensive periodic chore into something that can run on a schedule and report itself.
In a cloud SCADA system such as Merobix, the net oil and net water results from each test flow into the same platform that trends the well's pressures, rates, and status, so a test is not just a number on a sheet but a data point in a continuous history. That context is where the value compounds: an operator can see how a well's net oil and water cut have trended test over test, spot a well whose water cut is climbing or whose oil rate is falling off, and compare tests across a field to prioritize attention. The computer produces the split; the platform makes the trend of those splits visible.
Continuous visibility also helps catch when a test itself is suspect. If a net oil result looks out of line with a well's recent history, the surrounding SCADA data - the flow rate behavior, the water-cut trace, the separator conditions during the test - is right there to sanity-check it, so a bad water-cut reading or an unstable test can be recognized rather than blindly allocated. For remote wells that are tested without an operator standing by, that combination of automated net oil computation and archived, reviewable test data is what keeps allocation trustworthy.
It takes the total liquid flow rate from a flow meter and the water fraction from a water-cut meter, both measured live on the same stream, and multiplies the gross rate by the oil fraction to get net oil and by the water fraction to get net water. Because both inputs change moment to moment, the computer does the calculation continuously and accumulates the results into oil and water volumes over the test period. Those per-well totals then feed production allocation.
Net oil is the total liquid multiplied by the oil fraction, so any error in water cut passes straight through into the reported oil. The sensitivity is worst on high-water-cut wells, where oil is a small slice of a mostly-water stream and a small water-cut error becomes a large percentage error in the tiny oil number. That is why the water-cut meter feeding the computer, and its ability to handle emulsions and salinity, usually dominates the accuracy of the result.
A water-cut meter measures only the fraction of water in the liquid stream. A net oil computer takes that water-cut value together with a total liquid flow rate and computes the actual net oil and net water rates and volumes. In other words the water-cut meter supplies one of the two inputs, and the net oil computer combines it with flow to produce the allocation numbers a well test exists to generate.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.