An Overview of the Energy Industry Metadata Initiative ECIM’2009 Conference, Workstream C: GIS Haugesund, Norway September 15. 2009 Alan Doniger Chief Technology Officer, Energistics
An Overview of the Energy Industry Metadata Initiative
ECIM’2009 Conference, Workstream C: GIS
Haugesund, Norway
September 15. 2009
Alan Doniger
Chief Technology Officer, Energistics
Session Outline
• Overview
• Basic Concepts
• Origins
• Current Initiative
• Foundation
• Profiles
• Approach
• Energistics
• Participation
• Questions
2
Session Outline
• Overview
• Basic Concepts
• Origins
• Current Initiative
• Foundation
• Profiles
• Approach
• Energistics
• Participation
• Questions
3
Enabling data discovery, evaluation, and access in the community.
– Reducing amount of time devoted to finding, retrieving, and verifying geographically relevant datasets, documents, and other resources is a recognized industry need.
– The term metadata refers to that which is useful to consistently characterize geographically relevant consistently characterize geographically relevant resources.
– Objective is to enable the energy community to adopt standard approaches to such metadata – specifying, assigning, and using – covering internal and external data exchanges and leveraging relevant technologies and trends.
4
Enabling data discovery, evaluation, and access in the community.
– Initial focus is on resources that have coordinate-based location references; later expand to place-name location references.
– The facilitator and custodian of this initiative is Energistics. Energistics.
– Active participants and interested parties are being sought.
– Progress will be made incrementally over time.
– Data management principles will be applied.
5
Energistics Role in the Industry
• Energistics
– serves as a custodian,
– facilitates the development, and
– encourages and supports adoption
• of open data, information and process standards standards
• in the upstream oil and gas industry
6
Energistics
Board of Directors Management & Staff
Advisory Council
Membership, Standards and SIGs
PRODML SIG
SIGs are standards
user communities
Advisory CouncilMembership
Other SIGs
RESQML SIG
WITSML SIG
Participants
Energistics Standards
7
Energistics Subject Areas
Reservoir
Engineering
Expl Petrophysics Petroleum
Production
Geology
AssetManagement
Reservoir
Engineering
Expl Petrophysics Petroleum
Production
Geology SIGGeologySIG
Asset/DataMgt SIG
• Global Unique Well Id
• Industry Metadata
eRegulatorySIG
Industry Services SIG• Technical Architecture• Energy Identity Trust
Expl
Geology
Petrophysics Petroleum
Engineering
Drilling
Engineering
Production
Engineering
Facilities
Engineering
Production
OperationsGeophysics
Drilling
Operations
Completion &
Workover
Expl
Geology
Petrophysics Petroleum
Engineering
Drilling
Engineering
Production
Engineering
Facilities
Engineering
Production
OperationsGeophysicsDrilling
Operations
Completion &
Workover
Geophysics SIG SIG SIG
<<EnergyMLEnergyML/>/> ™™
8
G. Develop
T. ManageAsset
Q. OperateWells & Facilities
Business Process Reference Model
ADMSIG<<EnergyMLEnergyML/>/> ™™
G. DevelopConcepts
F. ExecuteSurvey
H. ConstructFacilities
R. MaintainWells &
Facilities
E. ConstructWells
I. Goods & Services, J. Logistics, K. Financial Services, L. A/D, M. Trade Hydrocarbons, N. HR, O. IT, P. Lab
GeophSIG
GeolSIG
eRegulatory SIG, Industry Services SIG
9
Session Outline
• Overview
• Basic Concepts
• Origins
• Current Initiative
• Foundation
• Profiles
• Approach
• Energistics
• Participation
• Questions
10
What is Metadata?
• The US FGDC explains that Metadata for a ‘thing’ what a news reporter would report about the ‘thing’:
– WHO created it?
– WHAT is it about? What is its form & size?
WHEN
11
– WHEN was it created? When is it useful?
– WHERE is it geographical relevance?
– HOW did it come to be as it is?
– WHY did it come to be as it is?
Why have and use Metadata?
• Searching for ‘things’ to learn about
• Researching subjects involving ‘things’
• Qualifying ‘things’ as relevant to a task at hand
12
task at hand
Metaphors for Metadata?
• Context – versus content
• Catalog entries
• Directory entries
• Tags
13
• Tags
• Indexes
Challenges for using Metadata effectively?
• Metadata models
• Metadata formats
• Metadata vocabulary
14
• Scope of ‘things’
• Scope of searchers, users
• Understandability among catalogers, between catalogers and users, and among users
Surprise, Surprise !!
• Success requires
– Good planning
• Well defined purpose and scope
– Good requirements
• Avoid purpose and scope creep
15
– Effective (automated) cataloging
• Diligent management and controls
– Full-scale data management
• Versioning
• Aliases
• Translations
• etc.
Best Practice Guidelines
• Generate nominal metadata asa by-product of ‘thing’ creation
– Whether the ‘thing’ is itself data or even if it is a physical resource
• Purposefully adapt nominalmetadata in directories / catalogs
16
metadata in directories / catalogs/ etc.
• Include metadata in data exchange messages
• Treat quality validation actively
• Expect change; manage change
Session Outline
• Overview
• Basic Concepts
• Origins
• Current Initiative
• Foundation
• Profiles
• Approach
• Energistics
• Participation
• Questions
17
ESRI Petroleum User Group: Metadata Workshop Took Place in 2006
• Objective was to define
• minimal metadata standards and supporting applications[post 9.2 ESRI applications]
• necessary within the petroleum industry
• to enable effective and efficient discovery and retrieval of geospatial information items (“things”).geospatial information items (“things”).
• Support both
• proprietary uses of geospatial data, and
• the exchange of geospatial data between companies.
• Leverage existing specifications
• This was a one-time event.
18
ESRI Petroleum User Group: 2006 Workshop Participants
� Anadarko
� APSG/OGP
� BHP Billiton
� BP
� Chevron
� ExxonMobil
� Geodynamics
� Hess
� New Century Software
� EnSoCo� Chevron
� ConocoPhillips
� Deloitte & Touche
� ESRI
� EnSoCo
� Petrosys
� Schlumberger
� Shell
19
Session Outline
• Overview
• Basic Concepts
• Origins
• Current Initiative
• Foundation
• Profiles
• Approach
• Energistics
• Participation
• Questions
20
Energy Industry Metadata Work Group:Tentative restart in early 2009
• Objective was changed from 2006 to 2009• work on supporting applications and tools was dropped out
• scope of ‘things’ expanded beyond geospatial ‘things’however first focus is on GIS, maps, and subsurface datasets
• First: explicit coordinates; later, place names
• Still support both proprietary uses and exchanges between companies.between companies.
• Still leverage existing specifications
• Operate as Energistics Asset & Data Mgt SIG Work Group
• Activities to encourage adoption and integration into business processes
• Long-term support, evolution, and maintenance
21
Energy Industry Metadata Work Group:Intended deliverables and scope impact
• Intended deliverables
– Metadata standards and usage guidelines
– For discovery, evaluation, and access
– Attributes - mandatory/optional/conditional
– Value Lists – open/recommended/required
• Impact of scope growth
22
• Impact of scope growth
– More attributes
– More values
– More diverse usage rules on attributes and values
– Challenge to work incrementally
– Challenge to balance flexibility and reliability
22
Energy Industry Metadata Work Group:Early Timeline
• January ‘09 – Steering Team formed
– Chevron, Shell, BHP Billiton, Gimmal Group, Energistics, ESRI, US GIN Project
– Revised objectives drafted for validation
– ISO 19115 and related specifications identified as foundation
• February 25 – ESRI Petroleum User Group Session
– Interest Parties group formed
– Initial reference use cases defined
• March 31 – Workshop
• July – ESRI User Conference – Two sessions
• September 14 – Informational documents published
• September 30 – Workshop
– Formal development activities begin
23
Energy Industry Metadata Initiative
• Objectives – January through August 2009
– Build awareness of this industry metadata standards development effort.
– Solicit input on the proposed vision and scope.
– Attract participation from industry organizations and individuals.
24
Energy Industry Metadata Work Group:Initial Use Cases
• Find GIS (shape) files for an area of interest without knowing the local filing / directory system.
• Learn the vintage of a layer of data on a map without this information being printed on the map.
• See complete list of datasets available for a region, basin, or field.basin, or field.
• Determine which datasets were acquired from a given service company.
• Evaluate datasets that were used in a past drilling, completion, maintenance, or other type of project.
25
Session Outline
• Overview
• Basic Concepts
• Origins
• Current Initiative
• Foundation
• Profiles
• Approach
• Energistics
• Participation
• Questions
26
ISO 19115-2003. Geographic Information - Metadata
• Content specifications
– Data model (UML)
– Elements
– Terminology
• Extension procedure• Extension procedure
• Scope
– Geographic information and services
– Identity, extent, quality, time, and place
27
fileIdentifier: 3A2234641211B12
Metadata
Identification informationConstraint information
Maintenance information
Reference system information
Spatial representation infoData quality information
Distribution informationContent InformationComposed of Packages
fileIdentifier: 3A2234641211B12language: encharacterSet: (default = "utf8“)parentIdentifier: National Map TopoSeries 864hierarchyLevel: (default = "dataset“)hierarchyLevelName: (not needed)contact : CI_ResponsiblePartydateStamp : 20060417metadataStandardName: ISO 19115:2003metadataStandardVersion: x.y
Page 12
34
5
67
89
28
Annex A schema object model:Identification Information Package
MD_TopicCategoryCode
+ farming+ biota+ boundaries+ climatologyMeterologyAtmosphere+ economy+ elevation+ environment+ geoscientificInformation+ health+ imageryBaseMapsEarthCover+ intelligenceMilitary+ inlandWaters+ location+ oceans+ planningCadastre+ society+ structure+ transportation+ utilitiesCommunications
<<CodeList>>
MD_Usage+ specificUsage : CharacterString+ usageDateTime[0..1] : DateTime+ userDeterminedLimitations[0..1] : CharacterString+ userContactInfo [1..*] : CI_ResponsibleParty
MD_Metadata(from Metadata entity set information)
MD_Constraints(from Constraint information)
MD_Identification+ citation : CI_Citation
+ abstract : CharacterString+ purpose [0..1] : CharacterString+ credit [0..*] : CharacterString+ status [0..*] : MD_ProgressCode+ pointOfContact [0..*] : CI_ResponsibleParty
<<Abstract>>
+resourceFormat
0..*+resourceSpecificUsage
0..*
1..*+identificationInfo
1..*
0..*
+descriptiveKeywords
0..*
0..*+resourceConstraints 0..*
MD_BrowseGraphic+ fileName : CharacterString+ fileDescription[0..1] : CharacterString+ fileType[0..1] : CharacterString 0..*
+graphicOverview
0..*
MD_KeywordTypeCode
+ discipline+ place+ stratum+ temporal+ theme
<<CodeList>>
MD_ProgressCode
+ completed+ historicalArchive+ obsolete+ onGoing+ planned+ required+ underDevelopment
<<CodeList>>
MD_Format(from Distribution information)
MD_MaintenanceInformation(from Maintenance information)
MD_Keywords+ keyword[1..*] : CharacterString+ type [0..1] : MD_KeywordTypeCode+ thesaurusName[0..1] : CI_Citation
0..*0..*
0..*+resourceMaintenance
0..*
0..*0..*
MD_Resolution
+ equivalentScale : MD_RepresentativeFraction+ distance : Distance
<<Union>>
MD_CharacterSetCode
+ ucs2+ ucs4+ utf8+ utf16+ isoIec8859oneTo15+ jis+ shiftJIS+ eucJP
<<CodeList>>
MD_DataIdentification+ spatialRepresentationType [0..*] : MD_SpatialRepresentationTypeCode+ spatialResolution [0..*] : MD_Resolution+ language [1..*] : CharacterString+ characterSet [0..1] : MD_CharacterSetCode = "utf8"+ topicCategory [1..*] : MD_TopicCategoryCode+ geographicBox [0..*] : EX_GeographicBoundingBox+ geographicDescription [0..*] : EX_GeographicDescription+ environmentDescription [0..1] : CharacterString+ extent [0..*] : EX_Extent+ supplementalInformation [0..1] : CharacterString
SV_ServiceIdentificationSee ISO 19119
MD_RepresentativeFraction
/+ denominator : Integer
<<DataType>>
Scale(from Units of Measure)
/ScaleWhere MD_RepresentativeFraction.denominator = 1/Scale.measure And Scale.targetUnits = Scale.sourceUnits
characterSet: documented if ISO 10646-1 is not used
{MD_Metadata.hierarchyLevelCode = "dataset" implies count (geographicBox) + count (geographicDescription) >=1}
MD_SpatialRepresentationTypeCode
+ vector+ grid+ textTable+ TIN+ stereoModel+ video
<<CodeList>>
29
Annex B:Metadata Data Dictionary
Name/Role
Name
Short
Name
Definition Obligation/
Condition
Maximum
occurrence
Data type Domain
29 MD_Identific
ation
ident basic
information
required to
uniquely identify
a resource
Use
obligation
from
referencing
object
Use
maximum
occurrence
for
referencing
object
Aggregated
Class
(MD_Metadata)
<<Abstract>>
Lines 30-41
30 citation idCitation citation data for
the resource
M 1 Class CI_Citation
<<DataType>>
(B3.2)
31 abstract idAbs brief narratiave M 1 CharacterString Free text 31 abstract idAbs brief narratiave
summary
M 1 CharacterString Free text
32 purpose idPurp summary of the
intentions with
which the
resource was
developed
O 1 CharacterString Free text
33 credit idCredit recognition of
those who
contributed to
the resource
O 1 CharacterString Free text
34 statusCode idStatCode status of
resource
O N Class MD_ProgressCode
<<CodeList>>
(B.6.26)
30
Session Outline
• Overview
• Basic Concepts
• Origins
• Current Initiative
• Foundation
• Profiles
• Approach
• Energistics
• Participation
• Questions
31
ISO 19115 Community Profiles
• A custom implementation of ISO 19115 tailored to a specific “community” for better and/or easier use.
ISO 19115Broad/complex
ProfileNarrow focus/often simplerBroad/complex
Generic
Optional
Undefined domains
Narrow focus/often simpler
More Specific
More Mandatory
More Explicit Domains –code value lists
32
32
Regional & organizational profiles
ISO Standard 19115ISO Standard 19115
Geographic Information Geographic Information -- MetadataMetadata
Navigation ProfileNavigation ProfileAfrican ProfileAfrican Profile
ANZLIC ProfileANZLIC Profile
North American Profile North American Profile
HydroHydro--geosciences Africa geosciences Africa
European ProfileEuropean Profile
Perfil Latinoamericano de MetadataPerfil Latinoamericano de Metadata
NATO ProfileNATO Profile
Profiles Enable Interoperability Within Communities
Navigation ProfileNavigation ProfileAfrican ProfileAfrican Profile
33
North American Profile
Canada: CAN/CGSB 171.3-95
North American
Profile
USA: FGDC CSDGM
Profile
Geospatial Metadata
Based on ISO 19115/19139
34
� Selection of items from ISO 19115:2003
� Promotion of selected optional fields to mandatory
� Extension of code lists� Addition of values to existing code lists� Addition of code lists
� Introduction of a multilingual register� Compliant to ISO 19135:2005 on registers
North American Profile
� Compliant to ISO 19135:2005 on registers� English and/et Français (and potentially Spanish)� Metadata items� Code lists
� Register will be accessible on the Web� XML document� Web Services� Web Browser
35
North American Profile Values: Examples
Extension
replacing free text
NAPMD_DateTypeCode
36
Session Outline
• Overview
• Basic Concepts
• Origins
• Current Initiative
• Foundation
• Profiles
• Approach
• Energistics
• Participation
• Questions
37
Development, Adoption,& Maintenance Process
� Development
� Capability focused (use cases, stakeholders)
� Avoid becoming self-absorbed
� Iterative and Progressive
� Road map, liaisons, openness, resilience
� Maximal input and participation
� Layered participation model, multi-level communication modes
� Strongly seek consensus
� Test, demonstration, and communicate throughout
� Keep to announced scheduled milestones
� Use Energistics processes and tools
38
38
Development, Adoption,& Maintenance Process
� Adoption
� Plan for adoption from the outset
� Develop material to reach stakeholders and users
� Lead, but federate activities with groups and organizations
� Organize for adoption
� Use various approaches to building awareness and usage� Use various approaches to building awareness and usage
� Collaboration (Sharepoint)
� Web
� Conference papers, presentations, and exhibit stands
� Demonstrations, tutorials, toolkits
� Try to keep everyone’s expectations ahead of us and in the right direction
39
39
Development, Adoption,& Maintenance Process
• Maintenance
– Use Energistics standards life cycle methods
• Cycles
• Stages
• Version / release management
• Change requests and issues management
• Collaboration tools• Collaboration tools
• Certification: software, services, professionals
• Mappings
– External usage – standards, de facto, etc.
– Version-to-version
– Taxonomy horizons
40
40
Shell Exploration & Production
Shell Metadata Standard
� Based on ISO 19115 – International support
� Minimize user impact
� 12 mandatory fields
� 8 recommended fields
� Standard taxonomy where not defined by ISO
� Custom metadata editor� Custom metadata editor
� Smart defaults
� Pick lists
� All other ISO fields optional
� Custom metadata toolbox
� Programmatic population through Python & Model Builder
41
41
Field name ISO SHELL ISO Tag
Wh
at
is it?
Dataset Title M M ResTitle
Abstract M M idAbs
Supplemental Information O R suppInfo
Lineage Statement R R dataLineage - statement
Dataset topic category M M TopicCatCd
Theme keyword O M Keyword
Distribution format R R PresFormCd
Dataset language M M dataLang
Dataset character set R M dataChar – CharSetCd
Status of the dataset O R status – ProgCd
Wh
o &
Wh
en
?
Dataset Reference Date M M RefDate
Dataset responsible party R M idPOC - details
Shell Metadata Standard
M: mandatory, R: recommended, O: optional
Wh
o &
Wh
en
? Dataset responsible party R M idPOC - details
Online resource R R onLineSrc, geometObjs
Maintenance Frequency O R MaintFreqCd
Metadata Point of Contact M MMdContact: rpIndName and/or rpOrgNamerpCntInfo,
cntAddressrole, cntPhone…
Metadata date stamp M M mdDateSt
Data usage O R SecConsts - useLimit ClasscationCd
Wh
ere
? Geographic Reference System R R refSysID - identCode
Bounding box R M westBL, eastBL, northBL, southBL
Place Keyword O M Keyword
Inte
rnal U
se
Metadata language O R mdlang, languageCode
Metadata character set O R mdChar, CharSetCd
Metadata Standard Name O R mdStanName
Metadata Standard Version O R mdStanVer
Graphic File Name O R bgFileName
Graphic File Type O R BgFileType
42
Session Outline
• Overview
• Basic Concepts
• Origins
• Current Initiative
• Foundation
• Profiles
• Approach
• Energistics
• Participation
• Questions
43
Energistics Standards
• Energistics – other relevant initiatives
– Web Services / Data Exchange (XML) Standards Families
• WITSML – Drilling, completions, and interventions
• PRODML – Production operations, optimization, and reporting
• RESQML – Earth models and reservoir models
• EnergyML – Overarching foundation
• Others in the future
– E&P Catalog Standards
• Universal scope – structured, semi-structured, unstructured
• Universal scope – data, information, knowledge
• Originally published stand-alone
– Adaptable for other contexts: Dublin Core, FGDC, ISO 19115, etc.
44
44
WITSML “cs_documentInfo”
� documentName� documentAlias� documentDate� documentClass� fileCreationInfo…
� date
� softwareName
� documentSecurityInfo…� class
� system
� endDate
� comment
� extensionNameValue� disclaimer
� softwareName
� creator
� Comment
- Standard metadata included in all WITSML, PRODML, and RESQML data object schemas
� disclaimer� auditTrail…
� Event… [date, type, party, …]
� owner� comment
45
Project/AFE
“Control”
Retention
Published Status
Security Entitlement
Revision Code
Review Date
Approved By
“Bibliographic”Title
Recipient
AuthorDescription
Source Organisation
Published Date
Language
Content Owner
Cross References
Unique Ref Tag/EDCC
“Coverage”
“Usage”
Location Representation
E&P Catalogue Standards: Attributes
“Contextual”
Product Type
Consumer Discipline Class
Producer Discipline Class
Information Asset Class
Info Item Class
“Relationships”
Compound Document
Collection
“Coverage”
Datum
Scale
Geographical Cords/polygon
Cord System
“System”
File SizeCreated By
Last Modified System UID
Media Logical Format“Contextual”
Product Type
Business Process
Customer DisciplineProducer Discipline
Product Group
KID Type
Asset Type
Asset UID
Product Type
Producer Business Process Class
Information Item Role
Information Class
Asset Class
Asset Identifier
The ‘Information Item Class’ has a unifying role as the compositionof the orthogonal dimensions (blue)
Info Item Class
46
E&P Catalog Context Attributes
• Information [KID] Item Class (or Business Item Class)
– A composition of the following
• Producer Business Process Class {Energistics EPBPRM}
• Producer Discipline Class {taxonomy}
• Information [KID] Item Role (or Business Item Role) {taxonomy}
• Asset Class {taxonomy}
• Information [KID] Class {taxonomy} • Information [KID] Class {taxonomy}
– The composition fosters ease of use and understanding
• Standardized titles, templates, etc.
• Selection by Business Process
– The individual classification dimensions are orthogonal and fosters effective searching
47
KID = knowledge, information, and/or data
47
Session Outline
• Overview
• Basic Concepts
• Origins
• Current Initiative
• Foundation
• Profiles
• Approach
• Energistics
• Participation
• Questions
48
Work Group Participation
• Participants
– Energy companies
– Industry vendors
– Government agencies
• Commitment
Steering Team (4-6)
Active Working Group (6-10)
49
• Commitment
– Roles
• “Owner”
• Contributor& Reviewer
• User
Interested Parties
49
Steering Team
• Arizona State Geol. Survey
• BHP Billiton
• Chevron
• Energistics
• ESRI
• Gimmal Group• Gimmal Group
• Shell
50
Current Requests to be Active Participants or Interested Parties
• AAPG
• Anadarko
• Apache
• BP
• ConocoPhillips
• Data East LLC
• DCP Midstream
• Geoscience Australia
• Hess
• North West Geomatics
• OilIT Journal
• Oxy
• P2 Energy Solutions
• Pioneer Nat. Res.• DCP Midstream
• Devon Energy
• ETL Solutions
• Exprodat
• First Amer. Spat. Sol.
• Flare Solutions
• Fugro Robertson
• Pioneer Nat. Res.
• PPDM Assoc.
• Premier Consulting
• SAS Global O&G
• U of Auckland
• US Geol Survey
• Wood Mackenzie
51
Proposed Timeline
Develop Position Paper
Status Report @ ESRI UC 2009
Develop Industry Metadata Profile
2009 2010 2011
52
Develop Industry Metadata Profile
Status Report @ PUG 2010
Stakeholder Reviews
Status Report @ UC 2010
Early Adoption Support
52
Session Outline
• Overview
• Basic Concepts
• Origins
• Current Initiative
• Foundation
• Profiles
• Approach
• Energistics
• Participation
• Questions
53
Thank You
Alan Doniger
Energistics Chief Technology Officer
24 E. Greenway Plaza, Suite 1315
Houston, TX 77042 USA
+1 713 267 5124
www.energistics.org