Embed Size (px)
Citation preview
Practical Well Log Standards
Paul Maton, POSCJim Theriot, POSC
Outline
• Business Drivers, Challenges• Phase 1 outcomes• Phase 2 approaches, results, examples• Next Steps
Well Logs: Business IssuesHuge numbers of curves (information overload)
Most oil company customers only load a small sub-set of curves into their data stores
Huge numbers of curves (information overload) Most oil company customers only load a small sub-set of curves into their data stores
Complex naming at BOTH Curve and Tool level Confusing even to petrophysicists Others got lost years ago!
Complex naming at BOTH Curve and Tool level Confusing even to petrophysicists Others got lost years ago!
Hard to find up to date information in public domain Isolated lists, complex language
Hard to find up to date information in public domain Isolated lists, complex language
Expert (petrophysicist) and generalist users have different requirements
Expert (petrophysicist) and generalist users have different requirements
Information Overload - Business Value
Most CommonlyLoaded
RarelyLoaded
Loaded Curve Names
Load Frequency High Business ValueMost oil company customers only load a small sub-set of curves into their data stores
Medium Business ValueLoaded for specialist applications
Note: Business Value does not take account of usage. It deals with the ‘average’ case
Log Data Management: Challenges• Nomenclature
– Logging companies’ Vocabularies– Oil companies’ Dictionaries
• Classification– Tool types– Curve types
• Value– Who uses ...– Which logs...– How often ...– For what ...
PWLS Version 1
• Classified ~2500 curves for ~100 tools from 3 logging companies
• Defined business value – high, medium, low• Classifications published at www.posc
.org/technical/PWLS/pwls_10.htm
PWLS Version 2 Objectives
• Clarify Curve Class and Classification• Emphasize two primary use cases:
– Classify curve instances based on logging company mnemonics
– Use curve classifications to search for relevant curve instances
Users and Usage Patterns - General• Geologist, Geophysicist, Engineer
– Get log(s) by Field, Block, Well, Log type– Store interpreted work
• Petrophysicist– Get Curve set for editing, processing, analysis
• Log Data Manager– QC and load old, and/or new logs– Classify logs and compile log catalogue
Users and Usage Patterns – PWLS V2
• Geoscientist, Engineer, Log Data Manager– Understand and classify log curves in industry terms starting
from mnemonics on log header• Logging Company Dictionary Administrator
– Submit company catalogue (initial or replacement) to POSC– Submit incremental change or addition to POSC
• POSC– Maintain company and industry (classification) data– Accept new and revised data from logging companies
Approach• Understand nomenclatures• Identify, share and adopt good practices
– “Never change original document or its data”• Produce and maintain the standards
– Logical, generic, high-level classification– Map logging and oil companies’ dictionaries to the
generic classification– Make it easily understood and available– Keep it up-to-date: this needs Oil Co. support
Company, Industry Data‘Company’ nomenclature
?
Company-defined codes, mnemonics
company-specificdynamiccryptic (?)
‘Industry’ nomenclature
Industry-agreedclasses
common namecommon definition(definition exists)stable (managed)
Channel, Curve and Property‘Company’nomenclature
Maps to
Company Channel Class
RP66 Org codeCo. MnemonicDescriptionBusiness valueClassificationQuantity & UoM
‘Industry’ nomenclature
Well Log Curve Class
NameObjectPropertyTechniqueModifier(s)Function
Property Class
NameParent ClassDescription
Maps to
Curve Type Queries• What is the object (or thing) whose properties we are
measuring?– Formation, casing, cement, wellbore, acquisition, etc.
• What (pure) property of the object are we measuring?– Density, porosity, velocity, etc.
• What technique are we using to make the measurement (with the tool)?– Neutron, acoustic, etc.
• Modifiers (or qualifiers) qualifying the (pure) Property– Deep / shallow; maximum / average / minimum, etc.
• Function– Mathematical derivation / calculation, e.g. ratio, std. deviation
Some Company Curve ClassesRP66 Org.code
Mnemonic Description Value Classification Units Class
150 GR Gamma Ray HIGH Gamma_Ray API_Gamma_Ray
440 SP Spontaneous Potential HIGH Spontaneous_ Potential
Low_Electric_Potential
150 CAL Caliper HIGH Caliper Cylinder_Diameter
150 RD Deep resistivity MED Deep_Laterolog_Resistivity
Resistivity
150 RS Shallow resistivity MED Shallow_Laterolog_Resistivity
Resistivity
150 RMLL Micro-laterolog resistivity HIGH Micro_Laterolog_Resistivity
Resistivity
More Company Curve ClassesRP66 Org.code
Mnemonic Description Value Classification Units Class
150 RMLL Micro-laterolog resistivity HIGH Micro_Laterolog_Resistivity
Resistivity
150 CNC Borehole CorrectedCompensated Neutron Porosity
HIGH Neutron_Porosity
Porosity
150 ZDEN Compensated Bulk Density
HIGH Bulk_Density Density
150 ZCOR Bulk Density Correction HIGH Bulk_Density_ Correction
Density
150 PE Photo-electric cross section
HIGH Photoelectric_Factor
Photoelectric_Factor
Channel, Curve Example 1
‘Company’nomenclature
Maps to
Company Channel Class
RP66 Org code: 150Co. Mnemonic: GRDescription: Gamma RayClassification: Gamma_Ray Units Class: API_Gamma_Ray
‘Industry’ nomenclature
Well Log Curve Class
Name: Gamma_RayObject: Formation Property: Gamma Ray Technique: (Spectrometry)Modifier(s): -Function: -
Channel, Curve Example 2
‘Company’ nomenclature
Maps to
Company Channel Class
RP66 Org code: 440Co. Mnemonic: PCALDescription: Caliper from Phase Shift ImbalanceBusiness Value: HighClassification: Electromagnetic _Caliper Units Class: Cylinder_Diameter
‘Industry’ nomenclature
Well Log Curve Class
Name: Electromagnetic_CaliperObject: Borehole Property: Caliper Technique: Electromagnetic Modifier(s): - Function: -
Links
• Property Type Browser• Company Data Views• Industry Data Views• Schema for PWLS Reference Data
Current Focus: Usage• Users
– Oil companies– Log analysts, Consultants– Data management repositories, companies
• Suppliers– Logging contractors (Acquisition, Processing …)– Software developers and vendors
• Evolve– User communities use PWLS and provide feedback– Revise specifications and implementations– Maintain Property, Curve and Tool catalogues
Conclusions• Version 2 published at
http://www.posc.org/technical/PWLS/pwls_20.htm• Active usage encouraged• Future direction and evolution through PWLS SIG
– Version 2.1 planned for release by year-end 2004• PWLS SIG meetings:
– Stavanger 15-16 June– Houston 23-24 June
• Additional info from www.posc.org or contact [email protected] or [email protected]
