Author: Mathias Lia CarlsenEvery oil and gas company does this.
You spend 50k USD on a PVT report. Top-tier lab. Smart people. Months of work. Beautiful plots.
Then you ask a very basic question: Where does the data live?
A PDF on a shared drive? An attachment in someone’s email from 2019? A printed report in a binder nobody has opened in years?
This is way more common than anyone wants to admit.
PVT Reports Are Not Documents. They’re Assets. A PVT report is not something you read once and forget.
It feeds:
- Reservoir simulation
- History matching
- Forecasting
- RTA/PTA
- Reserves
- M&A diligence
It sits underneath almost every serious technical decision you make. And yet we treat it like a Word file.
PDFs Are a Terrible DatabaseHere’s the usual setup:
- One PDF per lab study
- Multiple revisions
- No standard structure
- No clear version control
- No easy way to compare fluids across wells or fields
Try answering this: “How does this oil compare to the offset well we tested five years ago?”
Now you are manually flipping through PDFs, copy-pasting tables, and hoping nothing was missed. 👉 That’s not engineering. That’s archaeology.
The Real Cost Isn’t 50k USD. The expensive part is not the lab work.
It’s:
- Re-running studies because data can’t be found
- Re-ordering PVT because nobody trusts the old one
- Engineers manually extracting tables
- Bad decisions made on partial or wrong inputs
- Knowledge walking out the door when people leave
That hidden cost compounds every year.
PVT Data Needs a HomeA real PVT system does not store documents. It stores fluids.
That means:
- Raw lab data in structured form
- EOS models with full version history
- Clear metadata and ownership
- Easy comparison across reports, wells, and vendors
- One source of truth
This turns PVT from tribal knowledge into institutional memory.
This Is Boring. That’s Why It Matters.Nobody gets promoted for building a PVT database. Nobody shows it off at conferences. It’s not flashy.
But the best technical organizations obsess over boring things that compound:
- Clean data
- Repeatable workflows
- Systems that survive people leaving
You already paid for the science.
If the data only lives in a PDF, part of that 50k USD is already wasted.
This Is Exactly Why whitsonPVT ExistswhitsonPVT is designed to database PVT reports and PVT models properly. It is a fluid management system first, not a document repository.
whitsonPVT:
- Databases PVT reports
- Stores raw lab data
- Manages EOS/PVT models and revisions
- Makes fluids searchable, comparable, and reusable
So your PVT data does not disappear into:
- PDFs
- Email inboxes
- Filing cabinets
The Simple TestAsk yourself this:
If your best PVT engineer left tomorrow, would your fluids still make sense?If the answer is anything other than “yes, instantly,” you do not have a people problem. You have a system problem.
Want a Demo? If you want to see how whitsonPVT treats PVT data the way it should be treated, reach out. Contact:
carlsen@whitson.comNo hype. Just fluid data that actually lives somewhere useful.