1. Baker Hughes & WITSML John Shields Software Projects Manager Baker Hughes Aberdeen

2. Baker Hughes WITSML Involvement  Original WITS committee members in 1980s  Participated in Statoil DART Project 1998-2001  Founder member of WITSML project in 2000  Hosted WITSML web site until handover to POSC  Commercial services with WITSML 1.1  Currently commercial worldwide with WITSML 1.2  WITSML deployed via commercial RigLink servers

3. Baker Hughes BEACON Services

4. BEACON/WITSML Wells in Norway Exploration19Grane 616 Njord 211 Oseberg 414 Troll Total 1964 Vale Total 219 Gullfaks Satelitter 16Guovca 15 Heidrun 525 Kristin 417 Sleipner 319 Tulipan 114 Visund Total 11 Valhall 28 Valhall Flank South 722 Valhall South 12 Total Wells 58 Runs 252

5. Software Integration via WITSML  BEACON uses internal and 3 rd party software  WITSML enables data interchange with 3 rd party applications for: – Wellbore stability – Directional Well planning – Geological modelling – Petrophysics

6. WITSML services delivered via RigLink  RigLink v3.0 – Delivers data and visualization – Supports WITSML 1.2 – In use worldwide – Providing WITSML worldwide – Local and global servers as required

7. Drilling Dynamics Display

8. Well stimulation monitoring – BOT

9. DTS Data – Luna Energy

10. WITSML GetFromStore INTEQ WITSML Server WITS/WITSML Data Feed WITSML Subscribe/Publish WITSML Subscribe/Publish Remote WITSML Servers (BH or 3 rd Party) RigLink/ WITSML Server

11. WITSML 1.3 Server  New server developed to support WITSML v1.3  Acts as data aggregator and buffer between real time acquisition system and WITSML clients  Stores all defined WITSML objects and custom objects  Can also store associated data (files, pictures etc)  Reads WITS data feeds – converts to WITSML  Reads WITS data feeds – converts to WITSML  Handles user & group data access permissions  Users able to access data in different units  Scaleable from individual wellsite systems to large installations with multiple web servers

12. WITSML v1.3 Data Explorer

13. Generic Data Editor

14. Real time display from WITSML API

15. Real Time Display from WITSML API

16. Challenges for WITSML  QA/QC Real-time data – Need to ensure quality of data for RT decisions without interrupting real time data flow – Well position data - compare real time to plan & geological model  Proprietary data sets – Everyone has them (well test, images, NMR data) – How do we incorporate these into WITSML workflows?  Issues with legacy processes – Operator specific reports, custom data formats  WITSML adoption – Many applications yet to be migrated – Time based data - issues with time zones – Different data access strategies (polling, subscription) for realtime and historical data

17. Summary WITSML is:  Driving work process improvements now  Generating value today  Enabling interoperation between data providers and software vendors  Enabling fair competition between real time service providers  A key part of BEACON operations at Baker Hughes

18. Questions?