WITSML-Enabled Products

This Web page contains information about WITSML-enabled products as provided by product vendors.

The responsibility for the accuracy of this information and for the effectiveness of these products is entirely with the product vendors. Energistics provides this information to industry as an information service.

Product vendors should coordinate additions and updates to this information with Alan Doniger at the Energistics Houston office.

All other inquires about these products should be addressed to the individual product vendors.

Index to WITSML related Commercial Product Information:

Drillworks ConnectML (Knowledge Systems, Inc.)
GEO Software Suite (SDC Geologix)
DataLink (Independent Data Services)
SiteCom® (Kongsberg Intellifield)
Discovery™ Wells (Kongsberg Intellifield)
YieldPoint Realtime (RT) (Smith International)
Smith WITSML Store/Services (Smith International)

Drillworks ConnectML (Knowledge Systems, Inc.)
Product Description	Drillworks ConnectML Version 1.1.0 WITSML Object Specifications Version V1.2 WITSML API Specification Version V1.2 Drillworks ConnectML receives real time LWD and mud logging data for input into the Drillworks family to provide geopressure and geomechanical analysis as the well is drilled, or to a remote location.
	Knowledge Systems, Inc. WITSML is used in Knowledge Systems to transmit real-time drilling data from a rig to an office or other location where it can be imported into software applications for analysis. Contact Persons: Cary Purdy, Vincent Wu, Xiaomin Hu
Availability	From January 2005
Submitter Information	Cary Purdy Telephone +1 281 243 4344 One Sugar Creek Center Blvd., Suite 1100 Sugar Land, TX 77478 USA purdy@knowsys.com October 31, 2005

WITSML Function Coverage	Check all that apply. Explain limitations and/or special circumstances in the Comments area. Notes: Functional coverage is organized according to five kinds of product functionality with respect to the WITSML Standards: two kinds of client functions and three kinds of server functions. A product may exhibit multiple kinds of functionality. The terms client and server are used here exclusively with respect to the WITSML Server API interfaces. Clients issue requests to servers. Servers receive and respond to requests from clients. Behaviors for products that do not use the WITSML Server API are classified in an analogous manner. The five product classifications of WITSML functional coverage are: Client Products -- 1. WITSML Producer Client -- a product that generates or otherwise obtains data that is formulated as WITSML object instances and sent to a WITSML Server to be incorporated in that server's data population. Examples of such products include products that pick up real-time data from sensor devices, format it, and send it to a server; and products that extract data from data stores, format it, and send it to a server. 2. WITSML Consumer Client -- a product that issues requests for data as queries or subscriptions to a WITSML Server and then receives data as query responses or subscription publications. Examples of such products include products that acquire data from a server, possibly reformat it, and delivery it to an application program or viewer utility. 1&2. Products that exhibit combined Producer and Consumer Client functions may be application programs that operate directly on a WITSML Server, such as a mudlogging application or a pore pressure analysis application. Server Products -- 3. WITSML Receiving Server -- a product that performs WITSML Server functions in general and, in particular, acquires data from external sources. Data acquisition may be through WITSML API interfaces or other mechanisms. 4. WITSML Delivering Server -- a product that performs WITSML Server functions in general and, in particular, delivers data to external destinations. Data delivery may be through WITSML API interfaces or other mechanisms. 5. WITSML Managing Server -- a product that performs WITSML Server functions in general and, in particular, supports requests from authorized client applications to augment (extend), modify, or delete (part or all) WITSML object instances. 3&4. The general understanding and expectation is that a product characterized as a WITSML Server supports both Receiving and Delivering Server functionality. 3&4&5. The addition of Managing Server functionality allows a WITSML Server product to do more than store and forward data, such as supporting data quality management client applications that help ensure the integrity and quality of data content in a Server data population. General Functions -- 6. Virtually all products associated with the WITSML Standards will issue and/or process WITSML Server General Functions to determine the capabilities and version of a server product.
1. WITSML Producer Client	A product that (generates and) sends WITSML object instances to a destination process: 1a [_X_] Sends to a WITSML Server using AddToStore interface 1b [___] Otherwise
2. WITSML Consumer Client	A product that requests and receives WITSML data from a source process: 2a [_X_] Queries a WITSML Server using GetFromStore interface 2b [_X_] Subscribes to a WITSML Server using Publish interface 2c [___] Otherwise
3. WITSML Receiving Server	A product that performs the WITSML Server interfaces and receives data from source processes: 3a [___] Receives WITSML object instances via AddToStore interface 3b [___] Otherwise receives WITSML object instances 3c [_X_] Receives non-WITSML form data treated as if it were WITSML object instances or a virtual equivalent
4. WITSML Delivering Server	A product that performs the WITSML Server interfaces and delivers data to destination processes: 4a [___] Delivers WITSML data in response to queries via GetFromStore interface 4b [___] Publishes WITSML data in response to subscriptions via the Publish interface 4c [___] Otherwise delivers WITSML data 4d [___] Delivers non-WITSML form data derived from WITSML object instances or a virtual equivalent
5. WITSML Managing Server	A product that performs the WITSML Server interfaces and manages (augments, changes, deletes portions, or deletes entirely) WITSML object instances or a virtual equivalent: 5a [___] Processes modification requests via AddToStore, UpdateInStore, DeleteFromStore interfaces 5b [___] Otherwise processes modification requests
6. WITSML General Functions	A product that issues general WITSML Server interface requests to a WITSML Server: 6a [_X_] Issues GetVersion and/or GetCapabilities A product that performs the general WITSML Server interfaces: 6b [___] Processes GetVersion and/or GetCapabilities

WITSML Object Coverage	Mark D for Deliver and R for Receive, as applicable. If all functions do not apply, note either functions supported or functions not-supported, e.g. supported by 1a. Explain other limitations or special cases in the Comments area.
	[_R_] Realtime
	[_R_] Well
	[_R_] Wellbore
	[_R_] Log & WellLog
	[_R_] Trajectory & Traj. Stn.
	[___] Message
	[_R_] Mud Log
	[___] Rig
	[___] Survey Program
	[___] Target
	[___] Fluids Report
	[___] Operations Report
	[___] Risk
	[___] Formation Marker
	[___] Conventional Core
	[___] Sidewall Core
	[___] Cement Job
	[___] Tubular
	[___] BHA Run
	[___] Other, specify: ____________________________________________

Comments:	None.

Last Update	November 1, 2005 by Cary Purdy

GEO Software Suite (SDC Geologix)
Product Description	GEO Software Suite Version 5.70.xx WITSML Object Specifications Version V1.2 WITSML API Specification Version V1.2 GEO Software is a tightly integrated suite of applications that serve the recognized needs of wellsite and operations geoscientists for the collation, presentation, interpretation and sharing of well log data and information. Consisting of well log authoring tools (GEO™, GEOLite™ and GEOLogger™) each built upon the unique GEO dynamic document structure, the GEO Software Suite is augmented by functionality to simplify the sharing and collaboration of well log data, particularly with its now widely adopted GEOe-View™ interactive log viewing and printing software. The GEO applications are already capable of both importing and exporting data in WITSML format, and were independently reported to be the first software of its type on general release with this functionality. One of the typical uses of GEO is to create a Mudlog or Lithlog display by automatically loading sensor data through WITSML Log object(s) whilst allowing the user to speedily update the plot with both lithology and descriptive information. The facility to transmit such data as a WITSML Mudlog object means that it can be delivered to the right systems and the right people at the right time. Moreover, Geologix has demonstrated the use of Mudlog Object in not only recreating a mudlog plot but also in the generation of various mudlog reports.
	SDC Geologix is an independent software development company serving the oil & gas industry worldwide, from bases in the UK, USA and Indonesia since 1993. As a long-serving member of POSC, SDC Geologix has actively participated in the evolution of WITSML and embraced this data-transfer standard within the continuous development of all its software products. For more information about how WITSML is being deployed within the GEO Software applications, please contact SDC Geologix via their website at www.geologix.com. WITSML Activities: Steering/Technical committee involvement with specific focus on Mudlog and other relevant objects. Contact Persons: Samit Sengupta (steering committee), Edward Clements (technical committee)
Availability	From August 2005
Submitter Information	Samit Sengupta Telephone +44 1603 706900 Geologix Ltd., Rosebery Court, St. Andrews Business Park, Norwich, NR7 0HS, UK ssengupta@geologix.com November 2, 2005

WITSML Function Coverage	Check all that apply. Explain limitations and/or special circumstances in the Comments area. Notes: Functional coverage is organized according to five kinds of product functionality with respect to the WITSML Standards: two kinds of client functions and three kinds of server functions. A product may exhibit multiple kinds of functionality. The terms client and server are used here exclusively with respect to the WITSML Server API interfaces. Clients issue requests to servers. Servers receive and respond to requests from clients. Behaviors for products that do not use the WITSML Server API are classified in an analogous manner. The five product classifications of WITSML functional coverage are: Client Products -- 1. WITSML Producer Client -- a product that generates or otherwise obtains data that is formulated as WITSML object instances and sent to a WITSML Server to be incorporated in that server's data population. Examples of such products include products that pick up real-time data from sensor devices, format it, and send it to a server; and products that extract data from data stores, format it, and send it to a server. 2. WITSML Consumer Client -- a product that issues requests for data as queries or subscriptions to a WITSML Server and then receives data as query responses or subscription publications. Examples of such products include products that acquire data from a server, possibly reformat it, and delivery it to an application program or viewer utility. 1&2. Products that exhibit combined Producer and Consumer Client functions may be application programs that operate directly on a WITSML Server, such as a mudlogging application or a pore pressure analysis application. Server Products -- 3. WITSML Receiving Server -- a product that performs WITSML Server functions in general and, in particular, acquires data from external sources. Data acquisition may be through WITSML API interfaces or other mechanisms. 4. WITSML Delivering Server -- a product that performs WITSML Server functions in general and, in particular, delivers data to external destinations. Data delivery may be through WITSML API interfaces or other mechanisms. 5. WITSML Managing Server -- a product that performs WITSML Server functions in general and, in particular, supports requests from authorized client applications to augment (extend), modify, or delete (part or all) WITSML object instances. 3&4. The general understanding and expectation is that a product characterized as a WITSML Server supports both Receiving and Delivering Server functionality. 3&4&5. The addition of Managing Server functionality allows a WITSML Server product to do more than store and forward data, such as supporting data quality management client applications that help ensure the integrity and quality of data content in a Server data population. General Functions -- 6. Virtually all products associated with the WITSML Standards will issue and/or process WITSML Server General Functions to determine the capabilities and version of a server product.
1. WITSML Producer Client	A product that (generates and) sends WITSML object instances to a destination process: 1a [_X_] Sends to a WITSML Server using AddToStore interface 1b [___] Otherwise
2. WITSML Consumer Client	A product that requests and receives WITSML data from a source process: 2a [_X_] Queries a WITSML Server using GetFromStore interface 2b [___] Subscribes to a WITSML Server using Publish interface 2c [___] Otherwise
3. WITSML Receiving Server	A product that performs the WITSML Server interfaces and receives data from source processes: 3a [___] Receives WITSML object instances via AddToStore interface 3b [___] Otherwise receives WITSML object instances 3c [___] Receives non-WITSML form data treated as if it were WITSML object instances or a virtual equivalent
4. WITSML Delivering Server	A product that performs the WITSML Server interfaces and delivers data to destination processes: 4a [___] Delivers WITSML data in response to queries via GetFromStore interface 4b [___] Publishes WITSML data in response to subscriptions via the Publish interface 4c [___] Otherwise delivers WITSML data 4d [___] Delivers non-WITSML form data derived from WITSML object instances or a virtual equivalent
5. WITSML Managing Server	A product that performs the WITSML Server interfaces and manages (augments, changes, deletes portions, or deletes entirely) WITSML object instances or a virtual equivalent: 5a [___] Processes modification requests via AddToStore, UpdateInStore, DeleteFromStore interfaces 5b [___] Otherwise processes modification requests
6. WITSML General Functions	A product that issues general WITSML Server interface requests to a WITSML Server: 6a [_X_] Issues GetVersion and/or GetCapabilities A product that performs the general WITSML Server interfaces: 6b [___] Processes GetVersion and/or GetCapabilities

WITSML Object Coverage	Mark D for Deliver and R for Receive, as applicable. If all functions do not apply, note either functions supported or functions not-supported, e.g. supported by 1a. Explain other limitations or special cases in the Comments area.
	[___] Realtime
	[___] Well
	[___] Wellbore
	[D/R] Log & WellLog
	[___] Trajectory & Traj. Stn.
	[___] Message
	[D/R] Mud Log
	[___] Rig
	[___] Survey Program
	[___] Target
	[___] Fluids Report
	[___] Operations Report
	[___] Risk
	[___] Formation Marker
	[___] Conventional Core
	[___] Sidewall Core
	[___] Cement Job
	[___] Tubular
	[___] BHA Run
	[___] Other, specify: ____________________________________________

Comments:	None.

Last Update	November 2, 2005 by Samit Sengupta

DataLink (Independent Data Services)
Product Description	WITSML Server for IDS DataNet Well Reporting and Management System Datalink Version 1.0 WITSML Object Specifications Version V1.3.1 WITSML API Specification Version V1.3.1 The product uses the WITSML GetFromStore function to all the pickup of data.
	IDS is a company that provides well reporting and management services. Contact Persons: Jason Robinson (Steering Committee), Kenny Steele (Technical Team))
Availability	From November 21, 2005
Submitter Information	Jason Robinson Telephone +1 832 277 5010 Independent Data Services 534 Winter Oaks Dr., Houston, TX 77079, USA jrobinson@idsdatanet.com November 15, 2005

WITSML Function Coverage	Check all that apply. Explain limitations and/or special circumstances in the Comments area. Notes: Functional coverage is organized according to five kinds of product functionality with respect to the WITSML Standards: two kinds of client functions and three kinds of server functions. A product may exhibit multiple kinds of functionality. The terms client and server are used here exclusively with respect to the WITSML Server API interfaces. Clients issue requests to servers. Servers receive and respond to requests from clients. Behaviors for products that do not use the WITSML Server API are classified in an analogous manner. The five product classifications of WITSML functional coverage are: Client Products -- 1. WITSML Producer Client -- a product that generates or otherwise obtains data that is formulated as WITSML object instances and sent to a WITSML Server to be incorporated in that server's data population. Examples of such products include products that pick up real-time data from sensor devices, format it, and send it to a server; and products that extract data from data stores, format it, and send it to a server. 2. WITSML Consumer Client -- a product that issues requests for data as queries or subscriptions to a WITSML Server and then receives data as query responses or subscription publications. Examples of such products include products that acquire data from a server, possibly reformat it, and delivery it to an application program or viewer utility. 1&2. Products that exhibit combined Producer and Consumer Client functions may be application programs that operate directly on a WITSML Server, such as a mudlogging application or a pore pressure analysis application. Server Products -- 3. WITSML Receiving Server -- a product that performs WITSML Server functions in general and, in particular, acquires data from external sources. Data acquisition may be through WITSML API interfaces or other mechanisms. 4. WITSML Delivering Server -- a product that performs WITSML Server functions in general and, in particular, delivers data to external destinations. Data delivery may be through WITSML API interfaces or other mechanisms. 5. WITSML Managing Server -- a product that performs WITSML Server functions in general and, in particular, supports requests from authorized client applications to augment (extend), modify, or delete (part or all) WITSML object instances. 3&4. The general understanding and expectation is that a product characterized as a WITSML Server supports both Receiving and Delivering Server functionality. 3&4&5. The addition of Managing Server functionality allows a WITSML Server product to do more than store and forward data, such as supporting data quality management client applications that help ensure the integrity and quality of data content in a Server data population. General Functions -- 6. Virtually all products associated with the WITSML Standards will issue and/or process WITSML Server General Functions to determine the capabilities and version of a server product.
1. WITSML Producer Client	A product that (generates and) sends WITSML object instances to a destination process: 1a [_X_] Sends to a WITSML Server using AddToStore interface 1b [___] Otherwise
2. WITSML Consumer Client	A product that requests and receives WITSML data from a source process: 2a [_X_] Queries a WITSML Server using GetFromStore interface 2b [___] Subscribes to a WITSML Server using Publish interface 2c [___] Otherwise
3. WITSML Receiving Server	A product that performs the WITSML Server interfaces and receives data from source processes: 3a [___] Receives WITSML object instances via AddToStore interface 3b [___] Otherwise receives WITSML object instances 3c [___] Receives non-WITSML form data treated as if it were WITSML object instances or a virtual equivalent
4. WITSML Delivering Server	A product that performs the WITSML Server interfaces and delivers data to destination processes: 4a [_X_] Delivers WITSML data in response to queries via GetFromStore interface 4b [___] Publishes WITSML data in response to subscriptions via the Publish interface 4c [_X_] Otherwise delivers WITSML data 4d [_X_] Delivers non-WITSML form data derived from WITSML object instances or a virtual equivalent
5. WITSML Managing Server	A product that performs the WITSML Server interfaces and manages (augments, changes, deletes portions, or deletes entirely) WITSML object instances or a virtual equivalent: 5a [___] Processes modification requests via AddToStore, UpdateInStore, DeleteFromStore interfaces 5b [___] Otherwise processes modification requests
6. WITSML General Functions	A product that issues general WITSML Server interface requests to a WITSML Server: 6a [___] Issues GetVersion and/or GetCapabilities A product that performs the general WITSML Server interfaces: 6b [_X_] Processes GetVersion and/or GetCapabilities

WITSML Object Coverage	Mark D for Deliver and R for Receive, as applicable. If all functions do not apply, note either functions supported or functions not-supported, e.g. supported by 1a. Explain other limitations or special cases in the Comments area.
	[___] Realtime
	[_D_] Well
	[_D_] Wellbore
	[_D_] Log & WellLog
	[_D_] Trajectory & Traj. Stn.
	[_D_] Message
	[_D_] Mud Log
	[_D_] Rig
	[_D_] Survey Program
	[___] Target
	[_D_] Fluids Report
	[_D_] Operations Report
	[___] Risk
	[___] Formation Marker
	[___] Conventional Core
	[___] Sidewall Core
	[_D_] Cement Job
	[___] Tubular
	[_D_] BHA Run
	[___] Other, specify: ____________________________________________

Comments:	None.

Last Update	November 15, 2005 by Jason Robinson

SiteCom® (Kongsberg Intellifield)
Product Description	SiteCom® Version 2005 R1 WITSML Object Specifications Version V1.2 WITSML API Specification Version V1.2 The SiteCom® System products are designed to help the Oil Industry to meet the challenges of today's drilling operations. The SiteCom® System is a fault-tolerant solution for acquiring real-time depth and time-based data from any source on the rig independent of protocol and format. Data is distributed to any number of client applications for viewing and analysis of data. In addition the SiteCom® System is used for long-term storage of drilling data and enables secure access to all historical data from analysis and visualization tools as well as other enterprise data management tools. SiteCom® is designed to store, manage, server and distribute data collected by multiple SiteCom systems or other WITSML-based systems. SiteCom® supports all WITSML 1.2 objects and interfaces. All access to real-time and historical data is made through standard WITSML 1.2 interfaces. SiteCom® also accepts data from any upstream data source, not only WITSML and WITS sources. SiteCom® provides secure access to data through accepted user authentication and data encryption methods.
	Kongsberg Intellifield is an independent supplier of products, systems and solutions for real time remote operations to operators / contractors in the oil and gas industry. We are a leading provider of operations centers, "always on" collaboration, offshore / onshore integration, real time data management, visualization and analysis software and real time intelligence. For more information about how WITSML is being deployed within the SiteCom software applications, please contact Kongsberg Intellifield via their website at http://www.km.kongsberg.com/intellifield. WITSML Activities: Steering/Technical committee involvement with specific focus on log, realtime, trajectory, mudlog and other relevant objects. Contact Persons: Rune Skarbo (steering committee), Jan Stubstad (technical committee), Jan Kåre Igland
Availability	From November 2004
Submitter Information	Jan Kåre Igland Telephone +47 38 00 05 70 Andoyfaret 7 4623 Kristiansand, Norway jki@intellifield.no March 24, 2006

WITSML Function Coverage	Check all that apply. Explain limitations and/or special circumstances in the Comments area. Notes: Functional coverage is organized according to five kinds of product functionality with respect to the WITSML Standards: two kinds of client functions and three kinds of server functions. A product may exhibit multiple kinds of functionality. The terms client and server are used here exclusively with respect to the WITSML Server API interfaces. Clients issue requests to servers. Servers receive and respond to requests from clients. Behaviors for products that do not use the WITSML Server API are classified in an analogous manner. The five product classifications of WITSML functional coverage are: Client Products -- 1. WITSML Producer Client -- a product that generates or otherwise obtains data that is formulated as WITSML object instances and sent to a WITSML Server to be incorporated in that server's data population. Examples of such products include products that pick up real-time data from sensor devices, format it, and send it to a server; and products that extract data from data stores, format it, and send it to a server. 2. WITSML Consumer Client -- a product that issues requests for data as queries or subscriptions to a WITSML Server and then receives data as query responses or subscription publications. Examples of such products include products that acquire data from a server, possibly reformat it, and delivery it to an application program or viewer utility. 1&2. Products that exhibit combined Producer and Consumer Client functions may be application programs that operate directly on a WITSML Server, such as a mudlogging application or a pore pressure analysis application. Server Products -- 3. WITSML Receiving Server -- a product that performs WITSML Server functions in general and, in particular, acquires data from external sources. Data acquisition may be through WITSML API interfaces or other mechanisms. 4. WITSML Delivering Server -- a product that performs WITSML Server functions in general and, in particular, delivers data to external destinations. Data delivery may be through WITSML API interfaces or other mechanisms. 5. WITSML Managing Server -- a product that performs WITSML Server functions in general and, in particular, supports requests from authorized client applications to augment (extend), modify, or delete (part or all) WITSML object instances. 3&4. The general understanding and expectation is that a product characterized as a WITSML Server supports both Receiving and Delivering Server functionality. 3&4&5. The addition of Managing Server functionality allows a WITSML Server product to do more than store and forward data, such as supporting data quality management client applications that help ensure the integrity and quality of data content in a Server data population. General Functions -- 6. Virtually all products associated with the WITSML Standards will issue and/or process WITSML Server General Functions to determine the capabilities and version of a server product.
1. WITSML Producer Client	A product that (generates and) sends WITSML object instances to a destination process: 1a [_X_] Sends to a WITSML Server using AddToStore interface 1b [___] Otherwise
2. WITSML Consumer Client	A product that requests and receives WITSML data from a source process: 2a [_X_] Queries a WITSML Server using GetFromStore interface 2b [_X_] Subscribes to a WITSML Server using Publish interface 2c [___] Otherwise
3. WITSML Receiving Server	A product that performs the WITSML Server interfaces and receives data from source processes: 3a [_X_] Receives WITSML object instances via AddToStore interface 3b [___] Otherwise receives WITSML object instances 3c [_X_] Receives non-WITSML form data treated as if it were WITSML object instances or a virtual equivalent
4. WITSML Delivering Server	A product that performs the WITSML Server interfaces and delivers data to destination processes: 4a [_X_] Delivers WITSML data in response to queries via GetFromStore interface 4b [_X_] Publishes WITSML data in response to subscriptions via the Publish interface 4c [___] Otherwise delivers WITSML data 4d [___] Delivers non-WITSML form data derived from WITSML object instances or a virtual equivalent
5. WITSML Managing Server	A product that performs the WITSML Server interfaces and manages (augments, changes, deletes portions, or deletes entirely) WITSML object instances or a virtual equivalent: 5a [_X_] Processes modification requests via AddToStore, UpdateInStore, DeleteFromStore interfaces 5b [___] Otherwise processes modification requests
6. WITSML General Functions	A product that issues general WITSML Server interface requests to a WITSML Server: 6a [_X_] Issues GetVersion and/or GetCapabilities A product that performs the general WITSML Server interfaces: 6b [_X_] Processes GetVersion and/or GetCapabilities

WITSML Object Coverage	Mark D for Deliver and R for Receive, as applicable. If all functions do not apply, note either functions supported or functions not-supported, e.g. supported by 1a. Explain other limitations or special cases in the Comments area.
	[_DR_] Realtime
	[_DR_] Well
	[_DR_] Wellbore
	[_DR_] Log & WellLog
	[_DR_] Trajectory & Traj. Stn.
	[_DR_] Message
	[_DR_] Mud Log
	[_DR_] Rig
	[_DR_] Survey Program
	[_DR_] Target
	[_DR_] Fluids Report
	[_DR_] Operations Report
	[_DR_] Risk
	[_DR_] Formation Marker
	[_DR_] Conventional Core
	[_DR_] Sidewall Core
	[_DR_] Cement Job
	[_DR_] Tubular
	[_DR_] BHA Run
	[___] Other, specify: ____________________________________________

Comments:	None.

Last Update	March 24, 2006 by Jan Kåre Igland

Discovery™ Wells (Kongsberg Intellifield)
Product Description	Discovery™ Wells Version 2.0 WITSML Object Specifications Version V1.2 WITSML API Specification Version V1.2 Discovery™ Wells enables any number of users to view real-time data from any well site providing WITSML data. It accepts any type of signal, time and/or depth based, real-time or historical, and displays any mixture of signals in a highly configurable graphical user interface. It can integrate data from any number of sources such as MWD, LWD, mud, cement, weather, position data, mud logging, casing and other sources in real-time, always with the comfort of secure data transfer to your location. With Discovery™ Wells one viewer can be used throughout the company to access data in the operation center, in the office, at home, or any other place. Custom templates are easily designed with a minimum of skills (drag and drop) and can be distributed to anyone. Discovery™ Wells increases access to real time data, improves overview on well site status, improves collaboration, distributes information, reduces cost, reduces need for training, overcomes contractual and geographical hurdles. Discovery™ Wells is the all in one viewer for real time drilling and well data. The system build on the WITSML 1.2 standard and can connect to any compatible WITSML data source, including the Intellifield SiteCom® System.
	Kongsberg Intellifield is an independent supplier of products, systems and solutions for real time remote operations to operators / contractors in the oil and gas industry. We are a leading provider of operations centers, "always on" collaboration, offshore / onshore integration, real time data management, visualization and analysis software and real time intelligence. For more information about how WITSML is being deployed within the SiteCom software applications, please contact Kongsberg Intellifield via their website at http://www.km.kongsberg.com/intellifield. WITSML Activities: Steering/Technical committee involvement with specific focus on log, realtime, trajectory, mudlog and other relevant objects. Contact Persons: Rune Skarbo (steering committee), Jan Stubstad (technical committee), Jan Kåre Igland
Availability	From November 2004
Submitter Information	Jan Kåre Igland Telephone +47 38 00 05 70 Andoyfaret 7 4623 Kristiansand, Norway jki@intellifield.no March 24, 2006

WITSML Function Coverage	Check all that apply. Explain limitations and/or special circumstances in the Comments area. Notes: Functional coverage is organized according to five kinds of product functionality with respect to the WITSML Standards: two kinds of client functions and three kinds of server functions. A product may exhibit multiple kinds of functionality. The terms client and server are used here exclusively with respect to the WITSML Server API interfaces. Clients issue requests to servers. Servers receive and respond to requests from clients. Behaviors for products that do not use the WITSML Server API are classified in an analogous manner. The five product classifications of WITSML functional coverage are: Client Products -- 1. WITSML Producer Client -- a product that generates or otherwise obtains data that is formulated as WITSML object instances and sent to a WITSML Server to be incorporated in that server's data population. Examples of such products include products that pick up real-time data from sensor devices, format it, and send it to a server; and products that extract data from data stores, format it, and send it to a server. 2. WITSML Consumer Client -- a product that issues requests for data as queries or subscriptions to a WITSML Server and then receives data as query responses or subscription publications. Examples of such products include products that acquire data from a server, possibly reformat it, and delivery it to an application program or viewer utility. 1&2. Products that exhibit combined Producer and Consumer Client functions may be application programs that operate directly on a WITSML Server, such as a mudlogging application or a pore pressure analysis application. Server Products -- 3. WITSML Receiving Server -- a product that performs WITSML Server functions in general and, in particular, acquires data from external sources. Data acquisition may be through WITSML API interfaces or other mechanisms. 4. WITSML Delivering Server -- a product that performs WITSML Server functions in general and, in particular, delivers data to external destinations. Data delivery may be through WITSML API interfaces or other mechanisms. 5. WITSML Managing Server -- a product that performs WITSML Server functions in general and, in particular, supports requests from authorized client applications to augment (extend), modify, or delete (part or all) WITSML object instances. 3&4. The general understanding and expectation is that a product characterized as a WITSML Server supports both Receiving and Delivering Server functionality. 3&4&5. The addition of Managing Server functionality allows a WITSML Server product to do more than store and forward data, such as supporting data quality management client applications that help ensure the integrity and quality of data content in a Server data population. General Functions -- 6. Virtually all products associated with the WITSML Standards will issue and/or process WITSML Server General Functions to determine the capabilities and version of a server product.
1. WITSML Producer Client	A product that (generates and) sends WITSML object instances to a destination process: 1a [___] Sends to a WITSML Server using AddToStore interface 1b [___] Otherwise
2. WITSML Consumer Client	A product that requests and receives WITSML data from a source process: 2a [_X_] Queries a WITSML Server using GetFromStore interface 2b [___] Subscribes to a WITSML Server using Publish interface 2c [___] Otherwise
3. WITSML Receiving Server	A product that performs the WITSML Server interfaces and receives data from source processes: 3a [___] Receives WITSML object instances via AddToStore interface 3b [___] Otherwise receives WITSML object instances 3c [___] Receives non-WITSML form data treated as if it were WITSML object instances or a virtual equivalent
4. WITSML Delivering Server	A product that performs the WITSML Server interfaces and delivers data to destination processes: 4a [___] Delivers WITSML data in response to queries via GetFromStore interface 4b [___] Publishes WITSML data in response to subscriptions via the Publish interface 4c [___] Otherwise delivers WITSML data 4d [___] Delivers non-WITSML form data derived from WITSML object instances or a virtual equivalent
5. WITSML Managing Server	A product that performs the WITSML Server interfaces and manages (augments, changes, deletes portions, or deletes entirely) WITSML object instances or a virtual equivalent: 5a [___] Processes modification requests via AddToStore, UpdateInStore, DeleteFromStore interfaces 5b [___] Otherwise processes modification requests
6. WITSML General Functions	A product that issues general WITSML Server interface requests to a WITSML Server: 6a [___] Issues GetVersion and/or GetCapabilities A product that performs the general WITSML Server interfaces: 6b [_X_] Processes GetVersion and/or GetCapabilities

WITSML Object Coverage	Mark D for Deliver and R for Receive, as applicable. If all functions do not apply, note either functions supported or functions not-supported, e.g. supported by 1a. Explain other limitations or special cases in the Comments area.
	[_R_] Realtime
	[_R_] Well
	[_R_] Wellbore
	[_R_] Log & WellLog
	[_R_] Trajectory & Traj. Stn.
	[_R_] Message
	[_R_] Mud Log
	[_R_] Rig
	[_R_] Survey Program
	[_R_] Target
	[_R_] Fluids Report
	[_R_] Operations Report
	[_R_] Risk
	[_R_] Formation Marker
	[_R_] Conventional Core
	[_R_] Sidewall Core
	[_R_] Cement Job
	[_R_] Tubular
	[_R_] BHA Run
	[___] Other, specify: ____________________________________________

Comments:	None.

Last Update	March 24, 2006 by Jan Kåre Igland

Yield Point Realtime(RT) (Smith International)
Product Description	Yield Point Realtime(RT) Version: WITSML Object Specifications Version: V1.2 WITSML API Specification Version: V1.2 Using the WITSML capabilities, the customer's data from the well site can be linked directly to Yield Point RT. The data can then be analyzed in near real time to make recommendations for the operator that can be implemented immediately. As a result, hydraulics can be optimized to maximize efficiency as the well is being drilled. Yield Point RT is another example of the commitment of Smith Bits to providing customers with solutions that reduce costs.
	Smith International, Inc. is a leading worldwide supplier of premium products and services to the oil and gas exploration and production industry, the petrochemical industry and other industrial markets operating through four business units, M-I SWACO, Smith Technologies, Smith Services and Wilson. The Company provides a comprehensive line of technologically-advanced products and engineering services, including drilling and completion fluid systems, solids-control equipment, waste-management services, production chemicals, three-cone and fixed cutter drill bits, turbines, fishing services, drilling tools, underreamers, casing exit and multilateral systems, packers and line hangers. The Company also offers supply-chain management solutions through extensive North American branch network providing pipe, valves, fittings, mill, safety and other maintenance products. Smith Technologies is committed to the WITSML standards and has been an active member of the WITSML. Smith continues to develop real-time simulation and optimization programs for use with WITSML protocols. WITSML Contact Persons: David Moran, Yashodhan Gidh
Availability	From: To:
Submitter Information	David Moran, Yashodhan Gidh +1 (281)233-5387, (281)233-5235 16740 Hardy Street, P.O.Box 60068, Houston, TX 77205-0068 dmoran@smith.com, ygidh@smith.com 10/24/2005

WITSML Function Coverage	Check all that apply. Explain limitations and/or special circumstances in the Comments area. Notes: Functional coverage is organized according to five kinds of product functionality with respect to the WITSML Standards: two kinds of client functions and three kinds of server functions. A product may exhibit multiple kinds of functionality. The terms client and server are used here exclusively with respect to the WITSML Server API interfaces. Clients issue requests to servers. Servers receive and respond to requests from clients. Behaviors for products that do not use the WITSML Server API are classified in an analogous manner. The five product classifications of WITSML functional coverage are: Client Products -- 1. WITSML Producer Client -- a product that generates or otherwise obtains data that is formulated as WITSML object instances and sent to a WITSML Server to be incorporated in that server's data population. Examples of such products include products that pick up real-time data from sensor devices, format it, and send it to a server; and products that extract data from data stores, format it, and send it to a server. 2. WITSML Consumer Client -- a product that issues requests for data as queries of subscriptions to a WITSML Server and then receives data as query responses or subscription publications. Examples of such products include products that acquire data from a server, possibly reformat it, and delivery it to an application program or viewer utility. 1&2. Products the exhibit combined Producer and Consume Client functions may be application programs that operate directly on a WITSML Server, such as a mudlogging application or a pore pressure analysis application. Server Products -- 3. WITSML Receiving Server -- a product that performs WITSML Server functions in general and, in particular, acquires data from external sources. Data acquisition may be through WITSML API interfaces or other mechanisms. 4. WITSML Delivering Server -- a product that performs WITSML Server functions in general and, in particular, delivers data to external destinations. Data delivery may be through WITSML API interfaces or other mechanisms. 5. WITSML Managing Server -- a product that performs WITSML Server functions in general and, in particular, supports requests from authorized client applications to augment (extend), modify, or delete (part or all) WITSML object instances. 3&4. The general understanding and expectation is that a product characterized as a WITSML Server supports both Receiving and Delivering Server functionality. 3&4&5. The addition of Managing Server functionality allows a WITSML Server product to do more than store and forward data, such as supporting data quality management client applications that help ensure the integrity and quality of data content in a Server data population. General Functions -- 6. Virtually all products associated with the WITSML Standards will issue and/or process WITSML Server General Functions to determine the capabilities and version of a server product.
1. WITSML Producer Client	A product that (generates and) sends WITSML object instances to a destination process: 1a [___] Sends to a WITSML Server using AddToStore interface 1b [___] Otherwise
2. WITSML Consumer Client	A product that requests and receives WITSML data from a source process: 2a [ Yes ] Queries a WITSML Server using GetFromStore interface 2b [ No ] Subscribes to a WITSML Server using Publish interface 2c [___] Otherwise
3. WITSML Receiving Server	A product that performs the WITSML Server interfaces and receives data from source processes: 3a [___] Receives WITSML object instances via AddToStore interface 3b [___] Otherwise receives WITSML object instances 3c [___] Receives non-WITSML form data treated as if it were WITSML object instances or a virtual equivalent
4. WITSML Delivering Server	A product that performs the WITSML Server interfaces and delivers data to destination processes: 4a [___] Delivers WITSML data in response to queries via GetFromStore interface 4b [___] Publishes WITSML data in response to subscriptions via the Publish interface 4c [___] Otherwise delivers WITSML data 4d [___] Delivers non-WITSML form data derived from WITSML object instances or a virtual equivalent
5. WITSML Managing Server	A product that performs the WITSML Server interfaces and manages (augments, changes, deletes portions, or deletes entirely) WITSML object instances or a virtual equivalent: 5a [___] Processes modification requests via AddToStore, UpdateInStore, DeleteFromStore interfaces 5b [___] Otherwise processes modification requests
6. WITSML General Functions	A product that issues general WITSML Server interface requests to a WITSML Server: 6a [ Yes ] Issues GetVersion and/or GetCapabilities A product that performs the general WITSML Server interfaces: 6b [ Yes ] Processes GetVersion and/or GetCapabilities

WITSML Object Coverage	Mark D for Deliver and R for Receive, as applicable. If all functions do not apply, note either functions supported or functions not-supported, e.g. supported by 1a. Explain other limitations or special cases in the Comments area.
	[_R_] Realtime
	[_R_] Well
	[_R_] Wellbore
	[_R_] Log & WellLog
	[_R_] Trajectory & Traj. Stn.
	[___] Message
	[___] Mud Log
	[_R_] Rig
	[___] Survey Program
	[___] Target
	[___] Fluids Report
	[___] Operations Report
	[___] Risk
	[___] Formation Marker
	[___] Conventional Core
	[___] Sidewall Core
	[___] Cement Job
	[_R_] Tubular
	[_R_] BHA Run
	[_R_] Other, specify: WBGeometry

Comments:

Last Update	10/24/2005 by <Yashodhan Gidh>
Smith WITSML Store/Services (Smith International)
Product Description	Smith WITSML Store/Services Version: V 1.0 WITSML Object Specifications Version: V1.2 WITSML API Specification Version: V1.2 The Smith WITSML Store/Services provides seamless flow of well site data between operators and service companies to speed and enhance decision-making. It provides secure data access, data storage and data archival capabilities.
	Smith International, Inc. is a leading worldwide supplier of premium products and services to the oil and gas exploration and production industry, the petrochemical industry and other industrial markets operating through four business units, M-I SWACO, Smith Technologies, Smith Services and Wilson. The Company provides a comprehensive line of technologically-advanced products and engineering services, including drilling and completion fluid systems, solids-control equipment, waste-management services, production chemicals, three-cone and fixed cutter drill bits, turbines, fishing services, drilling tools, underreamers, casing exit and multilateral systems, packers and line hangers. The Company also offers supply-chain management solutions through extensive North American branch network providing pipe, valves, fittings, mill, safety and other maintenance products. Smith Technologies is commited to the WITSML standards and has been an active member of the WITSML. Smith continues to develop real-time simulation and optimization programs for use with WITSML protocols. WITSML Contact Persons: David Moran, Yashodhan Gidh
Availability	From: To:
Submitter Information	David Moran, Yashodhan Gidh +1 (281)233-5387, (281)233-5235 16740 Hardy Street, P.O.Box 60068, Houston, TX 77205-0068 dmoran@smith.com, ygidh@smith.com 10/24/2005

WITSML Function Coverage	Check all that apply. Explain limitations and/or special circumstances in the Comments area. Notes: Functional coverage is organized according to five kinds of product functionality with respect to the WITSML Standards: two kinds of client functions and three kinds of server functions. A product may exhibit multiple kinds of functionality. The terms client and server are used here exclusively with respect to the WITSML Server API interfaces. Clients issue requests to servers. Servers receive and respond to requests from clients. Behaviors for products that do not use the WITSML Server API are classified in an analogous manner. The five product classifications of WITSML functional coverage are: Client Products -- 1. WITSML Producer Client -- a product that generates or otherwise obtains data that is formulated as WITSML object instances and sent to a WITSML Server to be incorporated in that server's data population. Examples of such products include products that pick up real-time data from sensor devices, format it, and send it to a server; and products that extract data from data stores, format it, and send it to a server. 2. WITSML Consumer Client -- a product that issues requests for data as queries of subscriptions to a WITSML Server and then receives data as query responses or subscription publications. Examples of such products include products that acquire data from a server, possibly reformat it, and delivery it to an application program or viewer utility. 1&2. Products the exhibit combined Producer and Consume Client functions may be application programs that operate directly on a WITSML Server, such as a mudlogging application or a pore pressure analysis application. Server Products -- 3. WITSML Receiving Server -- a product that performs WITSML Server functions in general and, in particular, acquires data from external sources. Data acquisition may be through WITSML API interfaces or other mechanisms. 4. WITSML Delivering Server -- a product that performs WITSML Server functions in general and, in particular, delivers data to external destinations. Data delivery may be through WITSML API interfaces or other mechanisms. 5. WITSML Managing Server -- a product that performs WITSML Server functions in general and, in particular, supports requests from authorized client applications to augment (extend), modify, or delete (part or all) WITSML object instances. 3&4. The general understanding and expectation is that a product characterized as a WITSML Server supports both Receiving and Delivering Server functionality. 3&4&5. The addition of Managing Server functionality allows a WITSML Server product to do more than store and forward data, such as supporting data quality management client applications that help ensure the integrity and quality of data content in a Server data population. General Functions -- 6. Virtually all products associated with the WITSML Standards will issue and/or process WITSML Server General Functions to determine the capabilities and version of a server product.
1. WITSML Producer Client	A product that (generates and) sends WITSML object instances to a destination process: 1a [Yes] Sends to a WITSML Server using AddToStore interface 1b [___] Otherwise
2. WITSML Consumer Client	A product that requests and receives WITSML data from a source process: 2a [ Yes ] Queries a WITSML Server using GetFromStore interface 2b [ No ] Subscribes to a WITSML Server using Publish interface 2c [___] Otherwise
3. WITSML Receiving Server	A product that performs the WITSML Server interfaces and receives data from source processes: 3a [Yes] Receives WITSML object instances via AddToStore interface 3b [___] Otherwise receives WITSML object instances 3c [___] Receives non-WITSML form data treated as if it were WITSML object instances or a virtual equivalent
4. WITSML Delivering Server	A product that performs the WITSML Server interfaces and delivers data to destination processes: 4a [Yes] Delivers WITSML data in response to queries via GetFromStore interface 4b [___] Publishes WITSML data in response to subscriptions via the Publish interface 4c [___] Otherwise delivers WITSML data 4d [___] Delivers non-WITSML form data derived from WITSML object instances or a virtual equivalent
5. WITSML Managing Server	A product that performs the WITSML Server interfaces and manages (augments, changes, deletes portions, or deletes entirely) WITSML object instances or a virtual equivalent: 5a [___] Processes modification requests via AddToStore, UpdateInStore, DeleteFromStore interfaces 5b [___] Otherwise processes modification requests
6. WITSML General Functions	A product that issues general WITSML Server interface requests to a WITSML Server: 6a [ Yes ] Issues GetVersion and/or GetCapabilities A product that performs the general WITSML Server interfaces: 6b [ Yes ] Processes GetVersion and/or GetCapabilities

WITSML Object Coverage	Mark D for Deliver and R for Receive, as applicable. If all functions do not apply, note either functions supported or functions not-supported, e.g. supported by 1a. Explain other limitations or special cases in the Comments area.
	[_R/D_] Realtime
	[_R/D_] Well
	[_R/D_] Wellbore
	[_R/D_] Log & WellLog
	[_R/D_] Trajectory & Traj. Stn.
	[_R/D_] Message
	[_R/D_] Mud Log
	[_R/D_] Rig
	[_R/D_] Survey Program
	[_R/D_] Target
	[_R/D_] Fluids Report
	[_R/D_] Operations Report
	[_R/D_] Risk
	[_R/D_] Formation Marker
	[_R/D_] Conventional Core
	[_R/D_] Sidewall Core
	[_R/D_] Cement Job
	[_R/D_] Tubular
	[_R/D_] BHA Run
	[_R/D_] Other, specify: WBGeometry

Comments:	Fully tested with Smith Product Offerings

Last Update	10/24/2005 by Yashodhan Gidh

Site maintained by Energistics. Contact: gary.masters@energistics.org Phone: +1 713 267 5111
Copyright (c) 2007 Energistics. All rights reserved.
Energistics® and the Energistics logo® are registered trademarks and WITSML™ and the WITSML logo™ are trademarks of Energistics