UC-799
Draft the End of Well Report as the Well Finishes to make the lessons searchable
Drafts the end of well report from the daily reports, the cost record and the action log as the well finishes, and turns the review into lessons the next well can search.
TBDBuild Duration
XXXXIndicative ROI
XXXXBuild Cost
XXXXValue
The Challenge
Daily drilling reports already exist in a machine readable schema under Resource Management Regulations section 18, which is the input the end of well report should be built from. None of OMV's 18 Sodir recorded operated exploration wellbores is a development well, so Berling's own end of well reports will be the first development precedent OMV has. Capturing them properly is worth more here than at an operator with fifty of them.
How It Works
- The engine drafts the end of well report as the well finishes, from the daily reports, the cost record and the action log.
- It runs the after action review structure over that draft and turns the findings into lessons tied to sections and operations.
- It does not sign the report; the Well Delivery Manager and the team own the content, and the engine gives them a complete draft instead of a blank page.
What It Removes
- End of well reports written months after the well
- Lessons that never reach the next planning cycle
- Manual reconstruction from daily reports
Input Data RequirementsDaily drilling reports in the Sodir DDRS Energistics XML schema, the AFE and actual cost record, the DWOP action log and validation checks, the non-productive time cause ledger, the well programme and the well specific risk register.
Output FormatWeekly pack setting out the draft end of well report, the after action findings and the lessons written in a form the next well can search.
“Berling gives me my first development wells and I am not going to lose what they teach us.”