UC-782
Challenge Every Non-Operated AFE Before the Consent Deadline
Reads each incoming non-operated AFE against the operator's own history and the licence terms, and drafts the challenge before consent is due.
TBDBuild Duration
XXXXIndicative ROI
XXXXBuild Cost
XXXXValue
The Challenge
Non-operated AFEs arrive with a consent deadline and a small team. They are usually approved because there is no time to test them, and OMV carries its share of an estimate nobody challenged. Value here is OMV's own, because the challenge is made on the licences OMV does not operate.
How It Works
- The engine reads the incoming AFE, its scope and its basis of estimate against the licence agreement.
- It compares the estimate against that operator's delivered cost on comparable work and against OMV's own benchmarks.
- It drafts the challenge letter with the specific lines queried and the evidence behind each, ahead of the consent date.
What It Removes
- AFEs approved because the deadline arrived
- No comparison against the operator's own delivery history
- Challenge points found after the money is spent
Input Data RequirementsIncoming non-operated AFEs and basis of estimate, joint operating agreements and consent terms, operator delivery history, OMV internal cost benchmarks.
Output FormatDrafted AFE challenge per notice with cited comparison, consent deadline calendar, and a tracker of challenges made and accepted.
“We carry the share either way, so the estimate deserves a question.”
