Piloting DDR web services

Integrated Information Platform for reservoir and subsea production systems

Piloting DDR web services

DDR core team meeting

IBM Stavanger

Tuesday the 09th of January, 2007

Jone Aarre & Øystein Haaland

2


• High level project plan

• (MPR activity information)

• Web Services pilot - DDR

• ”Extending the Ontologies...”

• Identifying areas for good use of web services

Agenda

3


High level project planID Task Name Duration Start Finish

1 IBM & IIP Project plan 2007 272 days Thu 21.12.06 Fri 01.02.08

2 XML coding work - MPR domain 259 days Mon 22.01.07 Fri 01.02.08

3 Core teams complete with terminology 0 days Wed 31.01.07 Wed 31.01.07

4 Familirization with MPR (IBM) 4 days Mon 22.01.07 Thu 25.01.07

5 XML coding 50 days Thu 01.02.07 Fri 20.04.07

6 POSC referencing 10 days Thu 15.03.07 Wed 28.03.07

7 Testing 95 days Mon 23.04.07 Fri 31.08.07

8 Approval by OLF 40 days Mon 03.09.07 Fri 26.10.07

9 Approval by NPD 40 days Mon 29.10.07 Fri 21.12.07

10 Launch into production 0 days Fri 01.02.08 Fri 01.02.08

11 Semantic Web Services 250 days Thu 21.12.06 Wed 02.01.08

12 Call with R&D 1 day Thu 21.12.06 Thu 21.12.06

13 Preparatory work 3 days Thu 04.01.07 Mon 08.01.07

14 Meeting with DDR core team members 1 day Wed 10.01.07 Wed 10.01.07

15 US Workshop planning (R&D) 2 days Thu 11.01.07 Fri 12.01.07

16 US workshop - Watson labs 5 days Mon 15.01.07 Fri 19.01.07

17 Deploy necessary infrstructure incl. MW 5 days Mon 22.01.07 Thu 01.02.07

18 Generation of semantic web service - CDRS related50 days Mon 22.01.07 Mon 16.04.07

19 Core team to perform local testing 10 days Fri 30.03.07 Mon 23.04.07

20 Deployment scenario 1: Hosted solution 10 days Tue 24.04.07 Mon 07.05.07

21 Testing of scenario 1 20 days Tue 08.05.07 Mon 04.06.07

22 Deployment of scenario 2: Catalogue service10 days Tue 24.04.07 Mon 07.05.07

23 Testing of scenario 2 20 days Tue 08.05.07 Mon 04.06.07

24 SFA / Positioning / Production requirements2 days Tue 05.06.07 Wed 06.06.07

25 Approval by OLF 5 days Thu 02.08.07 Wed 08.08.07

26 Approval by NPD 5 days Thu 09.08.07 Wed 15.08.07

27 Commercial phase 90 days Thu 19.07.07 Wed 21.11.07

28 Launch into production 30 days Thu 22.11.07 Wed 02.01.08

29 IBM & IIP Project 2007 completed 0 days Fri 01.02.08 Fri 01.02.08

31.01

01.02

01.02

Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter

4


Web Services pilot - DDR

5


SOA and Web Services can also be implemented on SOIL

•Will requireSpecification and piloting of Web Service ArchitectureImplementation of Architecture

•Will facilitateWeb Service enablement of existing as well as new applicationsSharing of Web Services across companies

•Will supportIntegration of processes across companiesImplementation of Integrated Operations

SOIL

Web services onSOIL

• License adm. serv.• Production rep. serv.• Well mon. services• ...

• TietoEnator• Schlumberger• Baker• Halliburton• AK• ABB, SKF, • ROXAR• .

• Statoil• Hydro• BP• ConocoPhillips• NPD• ...

6


Background for choosing DDR...

• Given the availability of the DDR XML schemas, and the fact that the MPR project/data is still in it's early phase we agreed it would be smarter to focus on the former

• Thus we can obtain good assistance from CapGemini as they have performed the XML coding and is today actually working with services around DDR. (DNV input is also appreciated.)

• The CDRS (Common Drilling Reporting System) solution stands out as the best candidate area.

7


Web Service pilot - I

• To be implemented and hosted by IBM• Demonstration of usage / value of

performing an RDL->XML Schema mapping The schemas will be used ”as is” wrt web

service definitions Perform a Proof of Concept (PoC) of a

centralized catalogue-service• Pointer to each participant’s

implementation/application• The data shall as a principle be fetched from the

actual producer, i.e. No need for interim / temporarily / duplicate storage

8


Web Service pilot -II

• 2 – 4 suppliers (legacy + Peloton?) Statoil Hydro ExxonMobil ConocoPhillips

• Every supplier can be a consumer as well Including PSA of course (Petoro is also key.)

• Would like to use DDR (CDRS) as a service It’s already in use, well-known and terms and

definitions are understood & available

9


Required components

• Service Registry Containing information about services (WSDL)

• Authentication service Secure(d) access to a central hub Encrypted communication (SSL)

• Lightweight web-client For any participants who does not want or can

set up their own, dedicated servers for web services

For uploading of DDR XML files Requires corresponding web service front-end

10


”Extending the Ontologies...”

11


Semantic Web Services for IIP

1) DiscoveryFinds reporting web service for given report and

data provider

2) MappingMaps inputs/outputs and does any required

conversions

3) CompositionExample:

Adds and sequences signing and encryption services to satisfy policy requirements and constraints.

12


Discovery

Find the best overall match using available clues• WordNet based similarity matching • Domain heuristics (i.e. camelCaseNames)• Ontology based inferencing

– Cards, slots and chips are different things in Las Vegas and Silicon Valley

– “Høy” in the agro-cultural area means something else than what it does to a Wall-Street broker….

– “Christmas tree”…..ho-ho

Semantic Service Discovery

UPCCode, Due Date, Qty

ACME Inc.

Check Inventory

XYZ Inc.

FindItemAvailability

Check Availability

13


Mapping

ACME Inc.

Check Inventory

UPCCode

Delivery Date

Qty

Yes/No

XYZ Inc.

FindItemAvailability

EANCode

Due Date

Qty

Yes/No

Check Availability

UPC

Date

Qty

Yes/No

14


Mapping: Semantics can help disambiguate

EANCodeEANCode

UPCCode

UPC Version A UPC Version E

EANCodeEAN 8

EANCodeEAN 13

subClassOf

is a is a

is a

is a

Due Date

Delivery Date

sameAs

15


Request ACME Inc.

Signed&EncryptedOrderDocument Purchase Order

Processor Service

Order ConfirmationDocument

DigitalSigning Service

Encryption Service

OrderDocument

SignedDocument

Plain TextDocument

is an instanceOf

Semantic Web Service Composition using AI Planning

OrderDocument

Order ConfirmationDocument

input

output

Composition

Acme policy requires that all POs be signed and encrypted

16


Example: Oil Field Sensor Ontology

recognizes

Detector

Parameter

Channel ParameterOps ParameterReport Parameter

hasParameter

subClassof

Configuration ontology

Event

Event ontology

Well

Product Area

Device

Channel

hasProductionArea

hasDevice

hasChannel

Data ontology

hasTarget

pointsTo

DownholePressure

WellheadAcoustic

WellheadChoke

Type A

Type B

Type X

Type Y

Type P

subClassOf

subClassOf

IBMDetector B

DHP Channel

Acoustic Channel

Choke Channel

Sand Production

EUROPA A4

EUROPA A4DHP

EUROPA A4Acoustic

EUROPA A4Choke

MARS A24

MARS A24DHP

MARS A24Choke

MARS A24Acoustic

Partial ontology for oil wells sensors

17


Oil Field Ontology - Details

RecognizerWell Event

Product Area

Device

Channel

Engineer

Parameter

Channel Parameter Ops Parameter Report Parameter

hasTarget recognizes

hasProductionArea

hasDevice

maintains

hasParameter

pointsTo

hasChannel

subClassof

18


Service Requester

Semantic Service Registry

OntologyRepository

Annotate services

Select suitable ontologies or Create domain ontology

Annotate service requests

Select suitable ontologies

PublishDiscover

Inferencing Engine

Registry P

ublisher

Semantic Matcher

Service F

inderService Composer

Service Provider

Semantic Annotation Parser

Query P

rocessor

Semantic Directory Services & Composition

Semantic Web Services: Architecture

20


Identifying areas for good use of web services

21


WebService usage scenario

SOAP

PartnerReporting

Application

Partner

ReportingApplication

Web Service

Internet

SOAPBaseline Info

SOAPSecure Access

IIP ServicesBroker

(w/orchestration & governance) WSDL

Description

Publish

Fin

d

SO

AP

22


For our understanding

• The DBR data generation process Collection Formatting Reporting/Distribution

• Usage of XML schemas Current Target

23


Issues to cover

24


Objectives

• Identify (and define??) viable web service candidates

Usage scenarios (brainstorming)

• Understand data flow• Agree on pilot implementation team & resources

Data sources Connectivity Security (SOIL / Internet access) Infrastructure Hosting / Catalogue services

• Relation to MPR ++ (for potential re-use)• Verified project plan

Piloting DDR web services

Documents

Transcript of Piloting DDR web services