60 likes | 190 Vues
This document outlines the role of the WITSML Support Team as discussed in November 2008 in Dubai, led by David Johnson and Frode Jansen Lande. It emphasizes understanding business drivers, team logistics, and sub-team structure to address issues and enhancements. The support team is structured around various active sub-teams focusing on automation, performance, and maintenance services. The document encourages participation and provides insights on future growth, outlining tasks, and improvements that can be made to the existing framework.
E N D
Use Case / Support Team WITSML SIG Dubai - November 2008 David Johnson / Frode Jansen Lande
Use Case / Support Team Overview • Understand the Business Drivers or Business Implications of issues and enhancements • Team Logistics • 1 con-call / quarter • Reset priorities • Review over-all direction • Rebuild, Refocus sub-teams • Sub-teams meet as needed • Understanding the issue / idea • Review options • Build proposal • Present back to Steering Cmt for direction or Tech Team for action
Use Case / Support Sub-teams • Active Teams • Automation - Frode Lande • Depth correction & multi-pass - Yash Gidh • Server Profiles – • Performance & Certification - Nigel Deeks • Future Growth • Workover & Maintenance Services – Colin Tait • Takeup Improvement - Julian Pickering • (Currently) Inactive Team • Geodetic & Trajectory - Alan Doniger/Herve Vigor • Change Log Usage (DJ)
AFTER this conference Sub-teams • Active Teams • Automation - Frode Lande • Depth correction & multi-pass - Yash Gidh • Server Profiles – Frode and DJ (for now) • Data Organization • Server Behaviour • Performance & Certification - Nigel Deeks • Workover & Maintenance Services – Colin Tait • Takeup Improvement - Julian Pickering • Future Growth - DJ • New: Trajectory behavior discussion - Jim B • New: Visual Parameters for Log viewing - Nick • New: EVENT information - Roland
What can you do? • Get involved • Pick up a bat • Help the horse