| LIOS Technology GmbH - DTS WITSML Data Interface |
| Product Description |
LIOS Technology GmbH - Linear Optical Sensors Version: V 1.0 WITSML Object Specifications Version: V1.3.1 WITSML API Specification Version: V1.3.1
LIOS Technology GmbH is the first DTS supplier with an approved WITSML data interface, which was successfully deployed at various on- and off-shore projects. The petrotechnical protocol standard, WITSML V1.3.1, ensures compatible data files containing distributed temperature profiles, backscattering profiles and event data. LIOS offers its DTS systems with integrated protocol converter, technologies to safely transfer data over TCP/IP networks and enable seamless integration into customized database structures or other data storage, reduction, interpretation and visualization infrastructures. |
 |
LIOS Technology is the global leader in the development and supply of state of the art frequency domain based distributed temperature monitoring systems (DTS). The LIOS Technology OTS product line comprises a range of real-time, fibre-optic based linear temperature measuring devices.
With its innovative solutions for optical in-well permanent monitoring, LIOS helps its customers to operate oil fields more efficiently. LIOS offers its DTS systems with integrated WITSML protocol converter, technologies to securely transmit data from well site and enable its integration into customized database structures for real-time field managment.
LIOS Technology is committed to the WITSML standards and continues to develop real-time data processing and optimization programs for use with WITSML protocols.
WITSML Contact Persons: Dino Simonits, Daan van Laar, Albrecht Dress, Malcolm Wildenauer
|
| Availability |
From: August 2005 To: |
| Submitter Information |
Dino Simonits LIOS Technology GmbH - Linear Optical Sensors Schanzenstrasse 6 - 20, 51063 Cologne, Germany Telephone: +49 221 676 3200 Fax: +49 221 676 2069 www.downhole-monitoring.com info@downhole-monitoring.com
|
|
|
| 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 [_X_] Otherwise |
| 2. WITSML Consumer Client |
A product that requests and receives WITSML data from a source process: 2a [___] 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 [___] 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 |
|
[___] Trajectory & Traj. Stn. |
|
[___] Message |
|
[___] Mud Log |
|
[___] Rig |
|
[___] Survey Program |
|
[___] Target |
|
[___] Fluids Report |
|
[___] Operations Report |
|
[___] Risk |
|
[___] Formation Marker |
|
[___] Conventional Core |
|
[___] Sidewall Core |
|
[___] Cement Job |
|
[___] Tubular |
|
[___] BHA Run |
|
[_D_] Other, specify: dtsMeasurement |
|
|
| Comments: |
The product creates and storew WITSML XML files on a built-in flash disk. Data files are transmitted on demand to a remote consumer application. The product uses a custom TCP/IP protocol to optimize the data transfer and to save network bandwidth. Optional scure authentication and encryption of the transfer is available.
The product is fully tested in permanent operation at on and off-shore wells.
|
|
|
| Last Update |
26 February 2007 by Dino Simonits |