about the new energy industry metadata standards
TRANSCRIPT
Everything You Need to Know
About the New
© Energistics 2010© Energistics 2010
About the New
Energy Industry Metadata Standards
Initiative Update
ESRI PUG Conference
February 23, 2010
1
Energy Industry Metadata Standards Initiative
• What is it?
• Who is involved? Who can be involved?
• Why is it important?
• How will the standards be developed?
© Energistics 2010
• How will the standards be developed?
• When will version 1.0 of the standards be available
for use?
2
What: The Vision
Realize metadata standards and guidelines which enable
stakeholders in the energy industry (“the community”) to
effectively and efficiently discover, evaluate, and retrieve
information resources.
The standards and guidelines will support both proprietary
data management needs, and exchange of data between and
© Energistics 2010
data management needs, and exchange of data between and
within organizations.
Leverage existing standards to encourage adoption within the
community and integration into the business, and exploit
existing organizational resources needed for governance
and long-term maintenance.
3
What: Scope
User community:� Anyone cataloging, searching, evaluating or accessing information with
value to members of the energy industry:� Energy companies & consortia
� Data & Information providers
� Software vendors
� Government agencies & Academia
Resource types:
© Energistics 2010
Resource types:� Initial focus on structured and unstructured information resources which
have associated spatial coordinates. For example,
� Geospatial data sets & web services
� Mapping, Interpretation & Modeling project data sets
� Geospatial web services
� Long-term vision is to include resources with location specified using place names
4
Who: Initiative Participants
• Energistics – Serves as a custodian,
– Facilitates the development, and
– Encourages and supports adoption
• Asset/Data Mgmt SIG
• Active Participants– Serves as SMEs
– Provides feedback and input to the
development of the specifications
• Interested Parties
© Energistics 2010
• Asset/Data Mgmt SIG – Overall Energistics user
community for data management
– Reviews and endorses
• Metadata Work Group– Produces the specifications, and
– Steers the activities of the
participants
5
• Interested Parties– Reviews and plans for
implementation in their
organization
5
Who: Participants
AAPG
Apache
Arizona State Geol. Survey
Boise State Univ.
Carbon Lifecycle Technology
ConocoPhillips
DCP Midstream
Deloitte Services LP
Devon Energy
Maersk Oil1
New Century Software
North West Geomatics
Oracle1
ORNL
P2 Energy Solutions
PEMEX
PennWell
PetroWEB
Dave Danko, ESRI
Lisa Derenthal, Gimmal
Alan Doniger, Energistics1
Robert Graham, BHP Billiton
Scott Hills, Chevron1
Steve Richard, AZ Geol Survey1
Steering Team Active Participants (SMEs)
© Energistics 20106
Devon Energy
ETL Solutions
Exprodat
ExxonMobil 1
First American Spatial Solutions
Flare Solutions
Fugro Robertson
Geoscience Australia
Geosoft
Ies Brazil Consulting & Services
IHS Energy
PetroWEB
Pioneer Natural Resources1
PPDM1
Priemere Consulting Group
SAS Global Oil & Gas
Schlumberger1
Shell1
Univ. of Auckland, NZ
Virginia Dept of MM&E
Wood Mackenzie
1 Current Energistics member; organization Bold italics: Contributing to the current RFC
Why: The Opportunity
>40% of staff time devoted to finding, retrieving, and
verifying information, and data growing at 60-80%/yr
= Assembling information relevant to a question becoming more
problematic, impacting balance of cost and decision quality
Use cases include:
© Energistics 2010
Use cases include:
– What bathymetric maps1 are available for this area2?
– What geophysical information1 is available about Project X2?
– Is this the latest version2 of this dataset1?
– Does the copyright2 on this image1 allow me to use it?
1 or other information resource
2 or other selection criterion
7
Why: The Big Picture
ExternalMetadata Catalog
Online (Commercial,
Government,
& Academic)
Partner & Subscription
© Energistics 2010
Metadata Catalog
Subscriptiondelivery
Structured resources
Unstructured resources
Application auto-generated
8
How: Build on existing standards
Our approach leverages existing standards -
• ISO 19115 metadata standard for geographic information –internationally accepted
© Energistics 2010
• Existing profiles:
– North American Profile (NAP)-
adapts 19115 to FGDC standard
– European INSPIRE guidelines
– ANZLIC - Australia, New Zealand
• Use same approach to deliver a “Energy Profile” built on these
9
North America Profile (NAP) specifics:
� Promotion of selected optional fields to mandatory
� Extension of code listsAddition of values to existing code lists
How: Example Profile
© Energistics 2010
� Addition of values to existing code lists� Creation of new code lists
� Introduction of a multi-lingual register� Compliant to ISO 19135:2005 on registers� Metadata items & code lists� Register will be accessible on the Web
10
How: Key Metadata Packages
Metadata Entity
Portrayal Catalogue
Constraint Content
Distribution
Citation & Responsible
Party
Metadata Extension
Maintenance
© Energistics 2010
Extension
Reference System
ExtentUnits of Measure
Spatial Representation
Data Quality
Application Schema
Identification
11
How: Deliverables
• Documentation
– Profile Specification (normative document)
– Implementation Guidelines
• References Exemplars
• Exemplars
© Energistics 2010
• Exemplars
– Data (base)
– Associated XML
12
How: Guidelines & Exemplars
• Premise: metadata standards adoption and “usability” will be enhanced by exemplars
• Serves as “test set” to validate spec with real examples
© Energistics 2010
• Encourage organizations to develop an exemplar
– Donate a resource
– Work with us as we develop metadata for the dataset
13
When: Current Status
• Requirements Gathering (Jan 29 – Feb 28)
• Request for Comment (RFC) sent to Active Participants
• Two input methods:
1. Questionnaire seeking input on metadata requirements (requires no familiarity with ISO standard)
2. Detailed spreadsheet input form with ISO attributes and
© Energistics 2010
2. Detailed spreadsheet input form with ISO attributes and obligation levels (requires knowledge of ISO standard)
• Early Development of Profile Specification Deliverables
14
When: Metadata Initiative Timeline
Metadata Profile Development
Status Report @ PUG 2010
SIG Reviews
2009 2010 2011
© Energistics 2010
Status Report @ ESRI UC 2010
Pilot Projects
Stakeholder Reviews
Profile 1.0 Published
15
For more information …
• Go to www.energistics.org
– Asset and Data Management SIG under Communities
• Email: [email protected] or [email protected] or [email protected]
© Energistics 201016
Appendix
The following slides provide reference information for the metadata specifications:
– Data resources included
– Use case details
© Energistics 201017
What: Data Included & Priorities
Category Representative Information Resources
Profile ver.* Type Examples
File-based resources
1 GIS & CAD Maps & Layer representation .mxd, .mxt, .lyr, .pdf, .dwg, .dxf, .dgn
1 GIS data (Vector, Raster) ESRI® shapefile, GeoDatabase,.tif, .jpg
1 Mapping application projects Z-MAP Plus™, PetroSys
1 Modeling application projects (Subsurface properties & structure, Simulation) GOCAD®, Intersect™, Petrel™
1 Seismic projects data (2D, 3D/Navigation, Raw, Processed) SeisWorks®, EPOS®, PetroBank
1 Well logs (Raw and Processed) Geolog®, .las
2 Text documents (Publications, Reports, Bid packages) .doc, .pdf, .ppt, .txt
2 Tables spreadsheets, .dbf
2 Web sites .html
© Energistics 2010
Relational database resources
1 GIS data (Vector, Raster, TIN) SDE™, Oracle® Spatial, PostGIS
1 Production data (Historical, Real-time) Energy Components, TOW/cs®
1 Well data (Construction, Survey, Interpretation) OpenWorks®, Finder®, SeaBed, PPDM™
2 Document Management Systems Documentum®, FileNet®, OpenText™, SharePoint®
Web services
1 GIS data OpenGIS® WMS, WFS, WCS
1 Non GIS data WITSML™, PRODML™
2 Geoprocessing
2 Catalog metadata OpenGIS® CSW
Physical resources
1 Field samples & field documentation
1 Printed maps, logs, cross sections
2 Printed text documents
* Profile version: Resource types in-scope for version 1 have associated, explicit geospatial coordinates.
18
Why: Use Cases
3.2.1.1 Discovery A knowledge worker (user) must be able to discover and identify relevant data needed to perform his/her work tasks. Standard metadata associated with the data enables users to locate appropriate, available resources without knowledge of the locations, organization, or naming conventions of the repositories in which the data are stored.
3.2.1.2 Recall of Existing DataA user must be able to confirm that he/she has found all existing data as required in
© Energistics 2010
A user must be able to confirm that he/she has found all existing data as required in several scenarios. This situation arises frequently in the industry, with users new to the organization or in “look-back” scenarios where users are asked to revisit old projects, prospects, or areas given only information such as the area of interest (AOI) or project name.
19
Why: Use Cases (continued)
3.2.1.3 Evaluation of Data / Fit for PurposeIn the energy business, a user must know the relevance or pertinence of the data to be used in processing, modeling and analysis workflows. The knowledge worker needs to determine if the data is “fit for purpose”, by evaluating criteria such as vintage, source, quality, accuracy, lineage, etc.
3.2.1.4 On-going Data UpdatesOften data becomes obsolete because one or more of its ancestors has been updated. In
© Energistics 2010
Often data becomes obsolete because one or more of its ancestors has been updated. In this case, updating the dependent data set requires knowledge of the processing lineage, including the complete hierarchy of relevant ancestors, as well as tools, methods, and parameters used to process the data.
3.2.1.5 Data SharingCommon practices in the energy industry require users to share data externally (e.g., with JV partners) and internally (e.g., with other organizations). A user receiving the data must be able to determine the appropriate use of shared data and ensure that it is used properly and/or combined with other data without introducing errors.
20
Why: Use Cases (continued)
3.2.1.6 Use ConstraintsA knowledge worker needs to know the conditions under which they are permitted to access and use a particular dataset. Commercial or purchased data is often acquired under license with use constraints. Additionally, it now is increasingly common to find use constraints imposed by foreign governments which prohibit export of data produced to support operations within their boundaries.
3.2.1.7 Appropriate Use
© Energistics 2010
A user needs to understand the intended or recommended use for a given dataset. Metadata produced by the publisher is critical to the appropriate use of the content, whether published by a vendor, government agency, joint-venture partner, or internal organization within a company. Examples of this kind of metadata include scale-appropriateness and vintage. Lacking this metadata from the publisher, a user may use the data inappropriately or combine the content with other data in a manner that produces erroneous results.
21
The End
© Energistics 2010© Energistics 201022