in collaboration with building xml for daily drilling report arnt vegard espeland october 2006
TRANSCRIPT
In collaboration with
Building XML for Daily Drilling Report
Arnt Vegard EspelandOctober 2006
October 2006
2
In collaboration withUpstream Global Centre of Excellence
Arnt Vegard Espeland
Agenda
Background
The XML work
Profiles
XML sample
Background
October 2006
4
In collaboration withUpstream Global Centre of Excellence
Arnt Vegard Espeland
OLF intention: Establish an information pipeline that supports both IO generations
Field data Health, safety,
environment
Drilling & completion
Reservoir & production management
Operation & maintenance Vendor
Vendor
Semanticoil & gas web
Schemas for automaticexchange of data
Operator
Web portalsService libraries
Web services
TerminologyTaxonomyOntology
Automatic optimization
October 2006
5
In collaboration withUpstream Global Centre of Excellence
Arnt Vegard Espeland
Daily Drilling Report
Goal: Define terminology and XML schema for daily drilling reporting.
Base: All existing drill reporting applications from Peloton, Landmark, Statoil, Hydro and NPD/PSA
Scope and Constraint: • Norwegian authority reporting requirements.• CDRS
Terminology work• All operators at NCS were involved• Main industry players were involved• Finished by 31th March
The XML work
October 2006
7
In collaboration withUpstream Global Centre of Excellence
Arnt Vegard Espeland
Work organization and constraints
XML Task Force• Hans Stokka, NPD• Jonas Stokka, PSA• Pål Rylandsholm, DNV• Jostein Jåtten/Johan Thorsen, Statoil• Arnt Vegard Espeland, Capgemini
Key criteria• Provide reference to the terminology• Build and reuse WITSML data types, structures and standards• CDRS is the target
October 2006
8
In collaboration withUpstream Global Centre of Excellence
Arnt Vegard Espeland
First strategy
Important to deliver • Terminology and CDRS are key drivers for the XML• Build an ISO 15926 xml schema• 4 of 17 CDRS sections were covered by a XML draft (by early May)• XML draft did build on WITSML structures and data types
A parallel track for aligning ISO 15926 with WITSML is required
• opsReport not heavily adopted by the industry• Potential time consuming• Potential 2 standards; ISO 15926 and WITSML
October 2006
9
In collaboration withUpstream Global Centre of Excellence
Arnt Vegard Espeland
First strategy - why not WITSML?
Two purposes:• WITSML is oriented towards WITSML servers assuming a minimum
data set at both parties• DDR XML is report oriented. One document is standalone unit.
NPD/PSA and WITSML doesn’t group the information the same way
Validation requirements:• Cardinality of elements, i.e. mandatory vs. optional• Unit of measurements• Action codes
October 2006
10
In collaboration withUpstream Global Centre of Excellence
Arnt Vegard Espeland
Shift in strategy
Workshop with POSC 13 – 15. JuneGreat distance between the project and POSC.End of day 2, Mr. Doniger gave openings to enhance
WITSML opsReport.By end of the workshop the ISO 15926 drilling terminology
were mapped to WITSMLPOSC did create drillReport to be a replacement for
WITSML opsReportA Norwegian drillReport profile is created to constraint the
drillReport to NPD/PSA requirements.Consequences:
• No need for aligning DDR with WITSML• Operators will support the new drill report standard “out of the box”
WITSML Profiles
October 2006
12
In collaboration withUpstream Global Centre of Excellence
Arnt Vegard Espeland
What is a profile
A profile is a subset of some XML schema
Change an optional element to mandatory
Delete an optional item
Delete a value from lists (enum)
Can constraint data types
Add a pattern constraint.
Constrain the size of a value (shorten max length, etc)
October 2006
13
In collaboration withUpstream Global Centre of Excellence
Arnt Vegard Espeland
Profile
Profile map is defined in Excel spreadsheet
Profiled XML schema is generated from the profile map
Profiled schema is one single xml schema file!• No references to other WITSML files• Contains comments about the changes with respect to the origin.
A profiled drillReport schema is still a drillReport!!
XML sample
October 2006
15
In collaboration withUpstream Global Centre of Excellence
Arnt Vegard Espeland
Major enhancements
Most of the root leaf elements of opsReport are grouped into sections
New sections with new elements are added
Use copy of data rather then references.
October 2006
16
In collaboration withUpstream Global Centre of Excellence
Arnt Vegard Espeland
XML Sample
Drill report(s)
WITSML document info
new - controlIncidnetInfo
new - equiptFailureInfo
new - formTestInfo
new - bitRecord
October 2006
17
In collaboration withUpstream Global Centre of Excellence
Arnt Vegard Espeland
XML Sample – Header info
Measurement Datum, e.g. RKB
Geographic Datum, e.g. ED50
WITSML way for setting NPD
names
Report key data
October 2006
18
In collaboration withUpstream Global Centre of Excellence
Arnt Vegard Espeland
XML Sample – replace reference with data copies
October 2006
19
In collaboration withUpstream Global Centre of Excellence
Arnt Vegard Espeland
XML Sample - grouping of leaf elements into section
October 2006
20
In collaboration withUpstream Global Centre of Excellence
Arnt Vegard Espeland
In progress and next steps
Test the XML• A pilot for testing the XML is under construction
POSC activity• Approve the WITSML opsReport enhancements.
NPD/PSA is building the new drill reporting generation• The Norwegian profiled opsReport will become the reporting format
October 2006
21
In collaboration withUpstream Global Centre of Excellence
Arnt Vegard Espeland
?
Questions