1. Challenges - Operation and Support
Real Time Data
Challenges - Operation and Support

2. Overview Since October 2005 Service companies End users
Grane, OSC, OSE, Troll, Njord, Fram Vest
20 wells, 62 wellbores
Service companies
Baker
Halliburton
End users
RMS
GeoFrame
DrillWorks/Predict
Bore
Morning Status Check
Daily before 08:00

3. OPC - Bringing it All Together

4. OPC - West Venture at Sandsli

5. Right Time Data Update speed Operational Support
< 5 mins is accepable
Operational Support
(not Operational Control)
Drilling and Well Operations
WITSML
WITSML
Well
Wellbore
Trajectory
Trajectory Station
Log
Rig
Realtime
bhaRun

6. Status pr 19 october 2006
Generally 10 – 15 parallell drilling operations with WITSML.
WITSML in operations for nearly 3 years, in total 87 wells so far.
This year 51 wells so far.

7. Service Companies Deliveries
Stable deliveries most of the time
Still some erroneous data
Wrong wellbore
Data too deep
Missing data
Re-load of data
Conclusion: This will always happen  We need better data management tools
Issues with the WITSML delivered from service companies
SiteCom in Hydro based on active wellbore flag
Do we read the same data over and over again from the service companies?
Append mode versus overwrite mode
Conclusion: The goal is automated data transfer with as few re-reads as possible

8. WITSML Data Model in Hydro
Plus
Central WITSML Server in Hydro
SiteCom
One place to handle WITSML interface to service companies
Internal software, only one WITSML dialect
SiteCom agents
Splice log run
Composite logs
- Estimated trajectory station
SiteCom monitoring
SiteCom Alaram Manage
Service company WITSML
SiteCom WITSML
New wellbores
Splice/Composit log status
Minus
WITSML several dialects
Software not original designed for real time data
OpenSpirit, GeoFrame, Bore, Predict, RMS
New feature

9. Daily Work Routine Daily check before 08:00 A lot of tools involved
Give end user a daily status before morning meeting
Any problems encountered will be fixed during the day
A lot of tools involved
RigLink or Insite
DrillWorks WITSML Explorer
SiteCom Monitoring
SiteCom Splice Log Explorer
RMS
OpenWire
OpenSpirit
GeoFrame
GeoFrame web status

10. Example of Error Resolution
If something goes wrong
Error in data in GeoFrame
Full refresh of data from service company
Check data OK at service company
Stop the append OpenWire GeoFrame pipe
If error in survey, delete it from GeoFrame
Stop SiteCom Splice
Delete SiteCom Splice Log
Delete wellbore from SiteCom
Wait for SiteCom to re-load correct data
Start SiteCom Splice
Wait for SiteCom Splice to create new splice log
Create and run overwrite curve pipe in OpenWire for GeoFrame
Verify data is OK
Re-start the append OpenWire GeoFrame pipe
GeoFrame
RigLink/Insite
DrillWorks WITSML Explorer
OpenWire Append
GeoFrame
Windows Service Manager
SiteCom Splicelog Explorer
SiteCom WITSML Client
DrillWorks WITSML Explorer
(SiteCom Syncronizer)
Windows Service Manager
SiteCom Splicelog Explorer
DrillWorks WITSML Explorer
OpenWire Overwrite
GeoFrame
OpenWire Append

11. Challenges, Real Time Data in Hydro
Continuos stable delivery from service companies
Active wellbore + update date wanted
Better quality check of data before delivered to Hydro
If wrong data, need to do full refresh of all data on SiteCom and end user applications
New WITSML data types
Amount of data for time logs/curves
When will service companies be able to deliver new data types
Update speed from service companies
Transfer all data only once
Error recovery speed
Errors will happen, important to recovery quickly
WITSML 1.3
2007/2008
Memory data
Best data available for end users