Here’s a confession: none of our flow meters actually measure volumetric flow rate.
Yep, not a single one.
They all measure something else, a pressure drop, a vibration, an induced voltage, and then turn that into a flow rate through a chain of calculations, assumptions, and calibration constants.
Sounds simple? Not quite. This is where things get juicy (and occasionally messy).
The Coriolis Example – Straightforward? Not Really
Take the Coriolis flow meter. Brilliant bit of kit. Ask around and people will tell you it’s super accurate, even for multiphase. And it is, if you understand what it’s actually doing and measuring.
Here’s the secret:
- The meter isn’t “counting litres”.
- It’s measuring a phase shift (time delay) between two sinusoidal voltage signals from sensors on vibrating tubes.
- That time delay is proportional to mass flow rate. The conversion constant? Baked in at the factory or during proving.
But hang on, we normally want volumetric flow rate. To get that, we need density.
How’s that worked out? From the oscillation frequency of the tubes, using calibration constants. Neat, right?
Up to this point, it’s all in the wheelhouse of your friendly ICE engineer.
Oil + Water = Trouble
Now picture this: you’ve got oil with some water carry-under coming out of a separator. Easy fix, you reckon, just let the Coriolis do its magic, it measures density too.
Except… density here is mixture density.
To split that into oil and water rates, you need:
- Assumption #1: Phases are immiscible (ha, good luck in the field! Remember that bloke called Emulsion?).
- Assumption #2: No or low slip between phases, so volumetric fractions of your phases add up to 1
- Mass conservation: m_mixture = m_oil + m_water.
- Inputs: densities of water and oil.
Water density? You might have another Coriolis on the water leg. Sweet… unless you also have oil carry-over (Oh dear… get someone to tune your LCV’s!!!)
Oil density? That’s the $$$ question.
Get the PVT guy
I’ve seen some engineers grab an oil sample from the oil outlet, measure its density in the lab, and call it a day.
That’s when your PVT mate will scream:
“Noooo, you can’t use stock tank density for live oil at line conditions!”
Because at separator pressure and temperature, live oil is much lighter. Use the wrong density and you’ll happily “calculate” that you’ve produced more oil than you really have. Great for your ego (maybe your bonus, until someone checks), but not so great for production accounting and the other JV partners.
Sure, you could start taking proper sample bombs regularly, but if your separator is commingling fluids from multiple fields or zones, you’ll need to sample often. Not very sustainable, is it?
Putting on my data scientist hat, I might have an idea here. NO, it’s not AI, NO. But let’s save that for another yarn.
Error Propagation – Perfection lies in the Infamous Error
Every step, every assumption, every meter constant, every secondary sensor, introduces error. Those errors propagate in very funky ways. Remember my past rant on error propagation? It can be where it bites you the most. When dollars ride on the flow number, you’d better know how error snowballs through your calculation chain. It’s not about being too academic. It’s about protecting value for your business.
Moral of the Story
At first glance, flow measurement looks like a single-discipline job for an ICE engineer or metering tech. But scratch the surface and suddenly you’re calling your chemical engineer mate, your reservoir engineer mate, and maybe even your data scientist mate.
Because without enough cross-disciplinary understanding, you’ll just tell the operator:
“Take another sample and send it to the lab.”
And that’s not engineering, that’s outsourcing curiosity.
👉 So next time you look at a flow meter, remember: it’s not just numbers on a screen. It’s physics, chemistry, fluid dynamics, thermodynamics, error analysis, and a healthy dose of humility, all rolled into one.
P.S. The only true (nearly) volumetric measurement? The good old tank tape. Climbing up on an oil tank might sound fun until you’ve actually done it ha! Still, every young engineer should see it once. Builds character (and a healthy respect for automation).