Your SlideShare is downloading. ×
Data Modelling and WITSML
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Data Modelling and WITSML

1,237
views

Published on

Visualising WITSML XML Data Structures in Data Models. ECIM E&P conference, Haugesund Norway, September 2012

Visualising WITSML XML Data Structures in Data Models. ECIM E&P conference, Haugesund Norway, September 2012

Published in: Technology

2 Comments
2 Likes
Statistics
Notes
No Downloads
Views
Total Views
1,237
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
67
Comments
2
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Replace last bullet with slide over?
  • Note that the model shows logical names (with physical names in brackets). This is especially important for the more cryptic names such as wbGeometry = Wellbore Geometry.
  • Note that the model shows logical names (with physical names in brackets). This is especially important for the more cryptic names such as wbGeometry = Wellbore Geometry.
  • Q. What do the square brackets mean? What about IMPLIED?This will be explained laterQ. Why does it show “DEPRECATED Grid Correction Used” and “Grid Correction Used”The model allows the use of a deprecated element called gridCorUsed, and a replacement element called gridConUsed.
  • Q. What do the square brackets mean? What about IMPLIED?This will be explained laterQ. Why does it show “DEPRECATED Grid Correction Used” and “Grid Correction Used”The model allows the use of a deprecated element called gridCorUsed, and a replacement element called gridConUsed.
  • Tools can sometime infer relationships based on the hierarchical structure of XML messages. But they can’t infer implied relationships between items in multiple messages or differing branches of the same message that are based on name references.
  • CurrentA Cement Stage may specify one and only one Cementing FluidA Cementing Fluid may be specified by one and only one Cement StageA Cementing Fluid may be delivered using one and only one Cement Pump ScheduleA Cement Pump Schedule may be for one and only one Cementing FluidProposedA Cement Stage may specify one or more Cementing FluidsA Cementing Fluid may be specified by one and only one Cement StageA Cementing Fluid may be delivered using one and only one Cement Pump ScheduleA Cement Pump Schedule may be for one and only one Cementing Fluid
  • Cement JobA single Cement Job. One of Primary, Plug, Squeeze. tickCement StageSet of stages for the Cement Job (usually 1 or 2).Cementing FluidThe cementing fluid used during the course of a Cement Stage. One of Mud, Wash, Spacer, Slurry.Cement Pump ScheduleRecords the elapsed time, fluid rate and other pump related properties for the Cement Stage.
  • Transcript

    • 1. 1 Use this layout for text on top of a horizontally striped picture. Visualising WITSML using Entity-Relationship Models Christopher Bradley Chief Development OfficerECIM 2012 Haugesund, Norway
    • 2. 2 Use this layout for a title with a vertically striped picture. Presenter Chris Bradley Chief Development Officer chris.bradley@ipl.com +44 1225 475000 My blog: Information Management, Life & Petrol http://infomanagementlifeandpetrol.blogspot.com @InfoRacer
    • 3. 3 Introductions Christopher Bradley Chief Development Officer Chris has spent 32 years in the Information management field, working for leading organisations in Data Management Strategy, Master Data Management, Metadata Management, Data Warehouse and Business Intelligence. Graduating in 1979 Chris worked for the MoD(Navy), Volvo, Thorn EMI (as Head of Information Management), Readers Digest Inc (as European CIO), and Coopers and Lybrand Management Consultancy where he established and ran the International Data Management practice. Chris heads IPL’s Business Consultancy practice and is advising several Energy, Pharmaceutical, Finance and Government clients on Business Process and Information Asset Management. Chris is a member of the MPO, Director of DAMA UK and holds the CDMP Master certification. He co-authored “Data Modelling For The Business – A Handbook for aligning the business with IT using high-level data models”. Chris is a columnist and frequent contributor to industry publications. He authors an experts channel on the influential BeyeNETWORK, is a recognised thought-leader in Information Management and regular key speaker at major International Information Management conferences. chris.bradley@ipl.com +44 1225 475000 Blog: Information Management, Life & Petrol http://infomanagementlifeandpetrol.blogspot.com @InfoRacer
    • 4. 4 Use this layout for text on top of a vertically striped picture. Who is IPL? Trusted, independent consulting & solutions co • 30 year track record • 300 staff, £28m+ turnover • High-stakes, business & mission critical contexts • Consistently exceed expectations Business Consulting Division • Information Management • IM Strategy • Information Security & Assurance • Data Governance • Information Exploitation • Master Data Management • Information Architecture • Business Intelligence • .......turning Information into a strategic asset • Enterprise Architecture • Business Process Management • Programme Management Business Sponsor IPL Consulting Clients
    • 5. 5
    • 6. 6
    • 7. 7 Use this layout for a title with a horizontally striped picture. I Introduction & Agenda
    • 8. 8 Agenda Introductions What is WITSML? How is WITSML defined? Making sense of WITSML From XML to ERD: Technique Usage Scenarios The Wider Landscape
    • 9. 9 What is WITSML? Energistics is industry recognised body that provides a neutral environment for the development of common data exchange standards Wellsite Information Transfer Standard Markup Language is one such standard XML-based markup language For the transfer of wellsite information
    • 10. 10 Supported Data Objects 1.4.1
    • 11. 11 Example: WITSML Wellbore Trajectory This message describes the trajectory of a wellbore (a unique, oriented path from the bottom of a drilled borehole to the surface of the Earth) Structured But a bit cryptic… dTimTrajStart aziVertSect For uninitiated, difficult see overall organisation … and it’s difficult to see the context. XML Message Q. Would you show this to a business person?
    • 12. 12
    • 13. 13 How is WITSML Defined?http://w3.energistics.org/schema/WITSML_v1.4.1.1_Data_Schema/witsml_v1.4.1.1_data/doc/witsml_schema_overview.htm 1. List of WITSML Data Objects
    • 14. 14 How is WITSML Defined? Click http://w3.energistics.org/schema/WITSML_v1.4.1.1_Data_Schema/witsml_v1.4.1.1_data/doc/witsml_schema_overview.htm 1. List of WITSML Data Objects
    • 15. 15 How is WITSML Defined? l The tree reflects the hierarchical structure. Each XSD defines a type of XML element. 2. Tree of Element Types (for a Data Object)
    • 16. 16 How is WITSML Defined? l The tree reflects the hierarchical structure. Each XSD defines a type of XML element. Click 2. Tree of Element Types (for a Data Object)
    • 17. 17 How is WITSML Defined? Each XSD defines a type of element including Attributes Nested Elements 3. XSD Element Definition
    • 18. 18 How is WITSML Defined? Each XSD defines a type of element including Attributes Nested Elements Click 3. XSD Element Definition
    • 19. 19 How is WITSML Defined? There can be many levels of nesting The schema for a single data object spans many files 3a. XSD Element Definition (Nested Element) Q. Would you show this to a business person?
    • 20. 20 How is WITSML Defined? There can be many levels of nesting The schema for a single data object spans many files 3a. XSD Element Definition (Nested Element) Q. Would you show this to a business person?
    • 21. 21
    • 22. 22 Look at the real world example
    • 23. 23 What is the problem?
    • 24. 24 XML message fundamentals XML is hierarchical ER models are relational ER models represent real world data
    • 25. 25 XML implementation of ER model An XML schema generated from this model must choose one “parent” We could choose BOOK as the root, in which case WRITER would become a child of BOOK AUTHORSHIP We could choose WRITER as the root, in which case BOOK would become a child of BOOK AUTHORSHIP
    • 26. 26 Book Constraints Book ISBN code Amazon URL Book name Category Publication date Publisher Recommended price Book Authorship Constraints Agreement id Book ISBN code Writer id Writer Royalty % Draft delivery date Profile delivery date Constraints Writer id Writer name Specialism Affiliation XML implementation of ER model Book Book Authorship Writer
    • 27. 27 WITSML Logical Model Objectives Digestible for business users Meaningful names for entities and attributes Appropriate level of detail – hide “noise” Show appropriate logical relationships or business rules Not just the tree structure Easy to review
    • 28. 28 WITSML Logical Model Objectives Precise for IT users Accurate reflection of the WITSML standard Traceable to the WITSML standard Detailed Distinguish between physical and logical constructs Normalised, but showing hierarchical structure of messages Rigorous, formal analysis and design process Precise meaning of terms and symbols and rules Definitions support rigour
    • 29. 29 WITSML Logical Model Objectives Incorporate within Enterprise Data Model (EDM) Map objects to the relevant layer(s) in EDM Link enterprise level data assets through to WITSML Objects…more on this later Baseline for data requirements analysis and data modelling efforts undertaken at the project level Reduce the time taken for impact analysis Minimise rework Promote reuse.
    • 30. 30 Making sense of WITSML 1. Submodel: WITSML Data Objects 1. List of WITSML Data Objects
    • 31. 31 Making sense of WITSML 1. Submodel: WITSML Data Objects 1. List of WITSML Data Objects
    • 32. 32 Making sense of WITSML 2. Submodel for a Data Object 2. Tree of Element Types (for a Data Object)
    • 33. 33 Making sense of WITSML 2. Submodel for a Data Object 2. Tree of Element Types (for a Data Object) Shows the tree structure (inside the box labelled “Data Object: Trajectory”) Also shows the context (outside the box labelled “Data Object: Trajectory”)
    • 34. 34 Making sense of WITSML 3. Entities 3. XSD Element Definition
    • 35. 35 Making sense of WITSML 3. Entities 3. XSD Element Definition
    • 36. 36 Making sense of WITSML Attribute Definition Azimuth: Azimuth used for vertical section plot/computations. Entity Definition Trajectory: A set of Trajectory Stations that describes the path of a section of a wellbore or of the entire wellbore.
    • 37. 37 Can we turn XSDs into E/R models automatically? Yes and No! Yes: Tools such as E/R Studio and PowerDesigner can create models by inspecting XSDs. They can… Identify entities, attributes, and data types Import definitions from <xsd:documentation> nodes Infer relationships based on nesting of element types. But the human touch is needed too!
    • 38. 38 Can we turn XSDs into E/R models automatically? No: Manual effort is needed to… Create logical names Identify implied relationships Normalise / denormalise Classify into subject areas and map to conceptual models Layout diagrams
    • 39. 39 XML versus E/R Structures XML Hierarchical - tree structure. Each entity has just one parent. Used for transfer of data. Shared data appears multiple times in multiple messages. E/R Structures Relational - network structure. Each entity can have many parents. Used for storage and maintenance of data. Shared data typically appears just once.
    • 40. 40 From XML to ERD: Techniques
    • 41. 41 Using the Logical Model Scenario 1: Impact analysis Proposal to allow multiple fluids to be specified in the schema for the cementJob object What is the overall organisation of things the object describes? What is the impact on the business rules? Do the definitions still reflect the essence of the object that are impacted?
    • 42. 42 Current Proposed
    • 43. 43
    • 44. 44 Relationships
    • 45. 45 Entity Definition Cement Pump Schedule: Records the elapsed time, fluid rate and other pump related properties for the Cement Stage. Definitions
    • 46. 46 So… Is the Cement Pump Schedule for the Cement Stage? or For each Cementing Fluid? …does relaxing the constraint require the definition of the Cement Pump Schedule to be revised? Remember, definitions add rigor to models!
    • 47. 47 So What? Reduces the time taken for impact analysis Definitions and business rules highlight issues/questions Informed response to proposal Better quality model/WITSML
    • 48. 48 Using the Logical Model Scenario 2: Fit with existing application architecture Requirements to integrate data supplied in XML messages with existing systems Inc. reporting, data warehouse Or when assessing suitability of a system/application with business data requirements, e.g. SiteCom
    • 49. 49 Existing Architecture Example Requirement to report on planned and actual wellbore trajectory
    • 50. 50 Identify candidate target objects Entity Definition A set of Trajectory Stations that describe the path of a section of a wellbore or of the entire wellbore.
    • 51. 51 Identify candidate target objects Entity Definition A set of Trajectory Stations that describe the path of a section of a wellbore or of the entire wellbore.
    • 52. 52 Benefits Can be used to highlight: Fit and Integration challenges early in project Gaps and redundancy Data element sourcing issues – data type and size Help estimate development effort Overlap points to reuse Gaps require development – understand size and complexity
    • 53. 53 The Wider Landscape WITSML doesn’t exist in a vacuum!
    • 54. 54 Enterprise Data Model Conceptual Domain Model Application Logical Data Model Physical Data Model Described in more detail by Generates schema of Described in more detail by Domain of an Enterprise data concept Within subject area/domain Reverse engineered into Implemented in Reverse engineered into Physical IT System Implementation focus (Low) (High) (High) (Low) Communication focus Data Model Levels” Models
    • 55. 55 Use this layout for a title with a horizontally striped picture. Summary
    • 56. 56 In Summary Representing WITSML through data models: Easy to review by business and technical alike – ‘a picture paints a thousand words’ Facilitates a shared understanding of concepts Rigorous, formal analysis and design process Reduce the time taken for impact analysis Minimise rework Promote reuse
    • 57. 57 Further information: Articles including: • Seven deadly sins of data modelling • The IT Credibility Crunch • Information Management Deficiency Syndrome • Modelling is not just for DBMS’s • Data mining - where’s my hard hat? • Master data mix-ups • Drowning in spreadsheets • Why bother with a semantic layer? • Business Intelligence in a cold climate • Data Management is everybody's business Download from: http://bc.ipl.com/
    • 58. 58 Contact details Chris Bradley Business Consulting Director Chris.Bradley@ipl.com +44 1225 475000 My blog: Information Management, Life & Petrol http://infomanagementlifeandpetrol.blogspot.com @InfoRacer
    • 59. 59 Questions? business knowledge technical depth engagement model excellence experience satisfaction value delivery quality relationship

    ×