Technical paper
From source file to asset decision
How Nexus selects the right input, carries assumptions through the calculation and makes the technical review easier to follow.
Read the paper →Resources
The engineering behind the product.
Our papers explain how Nexus handles source selection, technical assumptions and cross-discipline review—and what changed after thirteen public-data cases.
Technical papers
Written so a domain professional can challenge the work.
Run identifiers, hashes and module receipts stay in the internal verification pack. The public papers concentrate on the engineering method and the lessons that matter outside one test run.
Technical paper
What thirteen public-data cases taught us
The recurring problems: wrong-file risk, missing calibration, unit ambiguity, weak joins and results that should stop before a forecast.
Read the paper →Published case
Start with the field question, not the audit record.
The Volve brief explains why late-life water is clear in the production history and why a shut-in survey cannot locate the flowing source interval.
Volve 15/9-F-1 C
Why logs, production history and a shut-in production log can narrow the water question without identifying a flowing source interval.
Read the case →15/9-11: good reservoir signs, poor well delivery
Why the well-test result shifts the appraisal question toward near-wellbore impairment and condensate behaviour.
Read the case →Kansas: one missing value changes the answer
Why formation-water resistivity matters more than the central screened interval.
Read the case →Case library
Explore all thirteen public-data evaluations.
Each brief starts with the field question, follows the technical reasoning and ends with the decision the evidence supports.