GEOPHYSICAL SPECIAL INTEREST GROUP GEOPHYSICS SIG ENERGISTICS by OIL AND NATURAL GAS CORPORATION IND

1
GEOPHYSICALSPECIAL INTEREST GROUP(GEOPHYSICS
SIG)ENERGISTICSbyOIL AND NATURAL GAS
CORPORATIONINDIA
Asia South and SIG Meeting 14 January 2007
HotelLe Méridien, New Delhi
2
Expectations from SEIS-SIG

• Standards for
• Data loading to seismic interpretation projects
  irrespective of the HW platform, OS and
  application SW.
• Data transfer from data bases to workstations
  over networks avoiding export import through
  physical media.
• Transfer of interpreted results like horizon,
  fault grids and velocity data in the project to
  master database and vice versa.
• Uniform naming conventions for Surveys, Lines etc
  so that agencies working in the same block (at
  different times) follow the same naming
  conventions
• Details of observer reports, processing reports
  and other QC and link to the processed data
  (helps in taking decisions for reprocessing)

3
Expectations from SEIS-SIG contd..

• The bulk seismic trace data storage formats
  are well documented and updating all relevant
  information in SEGY data is sufficient to share
  and exchange data.
• Standards are to be specified for the compression
  algorithms for seismic trace data for transfer of
  data over networks.
• Standardization of velocity and interpretation
  can be based on XML that (Extensible Markup
  Language ) was designed to describe data and to
  focus on what data is.

4
Why XML based Standards?

• Lot of information is generated in various
  formats while acquiring and processing seismic
  data sets which need to be captured in a database
  environment to provide the same to the end-users.
• ASCII based standard format files are sensitive
  to S/W applications.
• Error or inconsistencies in formats may cause
  catastrophic data errors.
• Self defining data formats (with structural
  definitions and data contents) create a new
  opportunity for sharing and transmitting data in
  systematically accurate and consistent way.
• XML is a cross-platform, software and hardware
  independent tool for transmitting information.
  With XML, data can be exchanged between
  incompatible systems.

5
ENERGISTICS GEOPHYSICS STANDARDS
GeophysicalML Standard.developed as a learning
experience when XML data exchange use was new
around the year 2000.

• The Geophysics SIG
• Formed with leadership from ONGC in INDIA, may
  set requirements for a current (WITSML styled)
  seismic Header Data exchange standards.
• Possible avenue is to work with SEG Technical
  Standards Committee where interest has been
  expressed for XMLbased exchange standards.

6
Energistics-ONGC ACTIVITIES in INDIA

• IORS-2004, SPECIAL SESSION on SMART FIELDS
• Energistics-SIG MEET ,14TH JAN 2005 ,NEW DELHI
• COMMITTEE CONSTITUTED FOR SEISMIC DATA
  STANDARDIZATION
• SPG-2006, SPECIAL MEETING ON SEIS-SIG

• FOLLOW UP
• ONGC SEISMIC TASKFORCE SUBMITTED RECOMMENDATION
  ON STANDARDIZATION FOR THE PURPOSE OF LOADING
  DATA INTO WORKSTATIONS
• ONGC REQUIREMENTS FED TO SEG
• IN TOUCH SEG-CANADA (through Energistics) ON
  SEG-D REV 2 MODIFICATIONS AND TOWARDS SEG-D REV 3

7
KEY SEED LIST AREAS - SEIS SIG

• 2D ,3D 4D Acquisition Standards
• 2D ,3D 4D Processing Standards
• Interactive Interpretation Results
• Generalized seismic data flow
• Data compression and handling Voluminous 3D data
  over networks

8
Summary of 9th JAN 2006 Seis-SIG meeting

• There was general agreement that a number of
  issues around seismic data are in need of
  standardization in India and any solutions from
  India might be relevant globally. The SEG
  standards community should be involved with the
  Indian effort.
• Several participants pointed out the need for
  standards at the acquisition stage and
  subsequently for processed and interpreted data.
  It was recognized that priorities would have to
  be agreed and the work done in phases.
• As had been achieved with existing seismic
  standards, any new standards should incorporate
  sufficient flexibility to accommodate evolution
  of seismic technologies for some (undefined) time
  to come.
• The business need for portability of seismic data
  in exchanging and sharing it was stated, and
  compression techniques are important in this
  respect.
• The operators present agreed that there is a
  business case for standards in seismic data being
  generated to enable exchange and transfer in the
  expanding Indian EP industry. Service companies
  indicated their support dependent upon the
  operators commitment.

9
Acquisition Standards - The Road Ahead
1.1 2D, 3D 4D Acquisition Standards Uniformi
ty in nomenclature by proper standardization in
respect of Survey names, Line-name/numbers. JOB S
tandard Naming conventions for Survey names,
Line-name / numbers. Action End-user
(ONGC-Taskforce recommendations) and Energistics
to match international standards with needed
flexibility. A single agency to look for
implementation.
10
Acquisition Standards - The Road Ahead
1.2 Line/Survey Summary Report and Observers
report /Logs
Simple Data variables such as navigation ,
equipment specifications, Observers and summary
report parmeters lend themselves to XML
standardization and can be exported simply as
attribute name value pairs. Public Petroleum data
model association is working on this line. The
XML standardization for seismic data enables
seismic data to be transferred between computers
far off in a most effective way.
The Summary report Observer reports also need
to be stored with data

• The Summary Report on tape in SEGD format as
  EXTERNAL HEADER

• The Observers report/LOG on Tape along with
  data in SEGD - Data Trailer at the end of the
  data after the shot

• The addition of the trailer will allow the
  accumulation of system faults,data Qc
  information, real time navigation and timing
  information on the same record and contiguous in
  with the shot point it relates to.

11
Acquisition Standards - The Road Ahead
1.2 Line/Survey Summary Report and Observers
report /Logs
JOB Original Equipment Manufacturer should
provide facility to format the HDR as per user
requirement in SEGD. ACTION OEMs under
Energistics Co-ordination.
JOB Utility to extract the Hdr report from
EXTERNAL Header / DATA Trailer. ACTION
Processing S/W Vendors under Energistics
Co-ordination.
JOB XML standardization of above header
parameters to enable ease in data
transmission. ACTION Energistics Co-ordination
with other S/W agencies and SEG.
12
Processing Standards - The Road Ahead
2.1 Standardization of header parameters
(EBCDIC / Binary / Trace headers of processed
SEGY data) Important information to be stored
like Processing agency, year, SI, record
length, Processing sequence, processing /full
fold grid with projection parameters and any
other special processing details etc and SP-CDP
relation in case of 2D seismic. 2.2 Standard
formats for Processed velocity data, Bathymetry
data standards and GM data and File
naming conventions.
13
Processing Standards - The Road Ahead
JOB Standard parameters to be stored in
EBCDIC / BINARY / TRACE headers. ACTION
End-user - What info is to be stored. ONGC has
finalized required info to be stored
Processing centers to implement. JOB
Storing of Line name in Binary / Trace
Headers ACTION Proper Coding for
Alpha-numerical character for writing to TRACE
HDR. ONGC Energistics SEG for allocating
BYTE positions. JOB XML standardization
of the header parameters to enable ease in data
transmission. ACTION Energistics
Co-ordination with other S/W agencies and SEG.
14
Results Magement Standards The Road Ahead
JOB Naming Conventions for all horizon Picks
for easy identification cataloguing of all
important actions with proper comments. ACTION
End-user, Energistics S/W vendors. JOB
Standards in Seismic data class at USERS END
for storing interpretation/intellectu
al results like time/depth structure maps as
image / ASCII, Horizons map grids with well
defined origin, calibrated velocities, porosity
prediction, seismic attributes like coherency,
semblance etc and impedance. ACTION End-user,
Energistics S/W vendors to Finalize the Outputs
to be stored and their formats for seam less
transfer of data from one workstation to
other. JOB Utility S/w for porting the
finalized outputs from IIWS to Master Database
and vice versa. ACTION S/W Vendors
Energistics and ONGC.
15
Generalized data flow seismic data
16
Generalized data flow seismic data
17
Data Compression
JOB SEIS SIGs main goal at attaining
standards in the whole life cycle of seismic
data from acquisition to end users so that the
data is used over web. ACTION Compression of
data Volumes or application of Citrix
Independent Computing Architecture (ICA) can
be taken up by SEG / Energistics
Through the use of its Citrix Independent
Computing Architecture (ICA) systems can allows
seamless interaction between most major operating
systems, including Microsoft Windows, Java, Unix,
Linux, Macintosh, DOS and OS/2 Warp. Using ICA
it is possible to Extend access to
business-critical applications to dispersed
users--regardless of connection, location or
device
18
The Way Forward

• Review of In-house standardization (Naming
  Standards / Conventions) efforts by Energistics.
• Requirement study of All the parameters to be
  stored in Observers report, Line summary, QC
  reports at Acquisition end parameter to be
  stored in EBCDIC/BINARY/TRACE Hdrs.
• The feasibility study of writing Observers
  report, Line summary, QC reports Navigation
  along with raw data in SEGD format.
• XML based data formats for Velocity data.
• XML based Data exchange standards for meta data.
• S/W for Porting Interpreted results to master
  Database and vice versa.

19
The Action Plan

• Identifying the coordinator for the coordination
  on these activities with Energistics (by
  30-01-2007).
• Review of In house standardization efforts by
  Energistics.
• Requirement study (ONGC- Energistics TEAM) to
  finalize the details of parameters to be stored
  - say Line Summary, Observers Report, QC reports,
  Navigation details etc - Scope of Work.
• Finalizing the scope.
• Providing The Energistics with the scope.
• Chalking out the Implementation Plan with
  Energistics.

20
Seamless Data Delivery
LOAD IN INDUSTRY STANDARD DATABASE

• DISPLAY
• SELECT
• VERIFY
• TRANSFER

• GATHER
• VALIDATE
• APPROVE

EFFECTIVE EP DATA MANAGEMENT

• USE
• INTERPRET
• MODEL
• ETC.

Courtesy Schlumberger
21
ANY QUESTIONS ??PL.,.
Thank you for your attention!
22

• INITIATIVES at ONGC END
• Task force of representatives drawn from
  regional EPINET centers
• to formulate and standardize data loading
  procedures and formats.
• SEISMIC TASK FOCCE RECOMMENDATIONS
• Acquisition
• a) On land - Survey Name
• Survey name will be of max 20 characters
• i)                    Basin Code Four
  Characters  For Onshore-Two Characters i.e. ON
• iii)                 Separator-One Character
  Block Code-Three characters
• v)                  2D or 3D-Two characters  
  Separator-One Character
• vii)               State Code-Max two Characters
  Investigation No-Max five characters
• Example-CMBYON-MEH2D-G401 CMBYON-ANK3D-G423
• CMBYON-ANK3D-MERGE1

23
On land -Line Name The On land Line Name will be
of max 16 characters  i) State Code-Max two
characters ii) Investigation No- Max five
characters iii) Separator-One characteriv) Line
No. Example-G419-01 Offshore Survey
Name  Offshore Survey Name will be of max 20
characters  i) First two characters-2D or 3Dii)
Third Fourth characters-Year Code. iii) Fifth
Character-Separatoriv) Sixth to Twentieth
Character-NELP Block Name, in case the concerned
Survey falls within a NELP Block.   If the
concerned Survey does not fall within a NELP
Block then  v) Sixth seventh character- Block
code like BO, KK, and GK vi) Eighth Ninth
character - OS in case of shallow water DW in
case of deep water. vi) Tenth character-Separator
. vii) Eleventh to Twentieth characters-Old
Survey Name.  Examples 2D02-KK-OSN-2001-1
2D91-BOOS-BRANW
24
EBCDIC Header Standardization C 1 CLIENT OIL
AND NATURAL GAS CORPORATION LIMITED. 2D SEISMIC
DATA C 2 LINE M125-02
SURVEY xxxxxxxxxxxxxxxx AREAxxxxxxxxxxxxxxxxxx
C 3 SPHEROID EVEREST75 PROJECTIONUTM-44
CM 81 CP2 XX C 4 FSP
74 IS AT LAT 11 12 18.12 N LON 79
30 29.01 E C 5 LSP 1088 IS
AT LAT 11 01 26.84 N LON 79 20 42.52 E
C 6 FCDP 1 SP ON FCDP 1
LCDP 1088 SP ON LCDP 1088 C 7 ADDITIONAL
SP CDP RELATION PAIRS FOR CROOKED PROFILE
(OTHERWISE BLANK) C 8 ADDITIONAL SP CDP
RELATION PAIRS FOR CROOKED PROFILE (OTHERWISE
BLANK) C 9 BLANK
C10
ACQUISITION PARAMETERS
C11 RECORDING YEAR
2004 AGENCYONGC
VESSEL/PARTYGP-29 C12 SYSTEMDFS-IV
REC FORMATSEG-B
LOW/HIGHCUT 8/128 HZ C13 NO OF
CHANNELS 96 FOLD 48
SOURCE VIBROSEIS C14 SAMPLE INTERVAL 2MS REC
LENGTH 5000 MS REC START TIME 0MS
C15 SHOT INTERVAL 100 M GROUP INTERVAL 100 M
NEAR OFFSET 200 M C16
LAYOUTSPLITSPREAD BACK CHANNELS 72
FORWARD CHANNELS 24 C17 ENTER ADDITIONAL
INFORMATION HERE
C18 ENTER ADDITIONAL INFORMATION HERE
C19
BLANK
C20 PROCESSING
PARAMETERS AGENCY RCC, CHENNAI, ONGC
BASIC/REPROCESSING C21 to C34 PROCESSING
STEPS C35 BLANK
C36 PROCESSED OUTPUT STORED
IN THIS TAPEDMOSTK/MISTK/PSTM/PSDM
C37 DOMAINTIME/DEPTH REC LENGTH 4000
MS SAMPLE INTERVAL 4 MS C38 ADDITIONAL
INFORMATION C39 BLANK
C40
END EBCDIC
 
Processing
25
Processing
MANDATORY LOCATIONS TO BE UPDATED IN BINARY
HEADER 17 - 18 SAMPLE INTERVAL IN MICRO
SECONDS. 21 - 22 NUMBER OF SAMPLES PER DATA
TRACE. 25 - 26 DATA SAMPLE FORMAT CODE. 27 -
28 EXPECTED NUMBER OF TRACES PER ENSEMBLE.
SHOULD BE 1 FOR POST STACK DATA. 29 -
30 TRACE SORTING CODE. SHOULD BE
4 FOR STACK DATA 55 - 56 MEASUREMENT SYSTEM.
1 FOR METERS 2- FEET (RECOMMENDED TO
UPDATE THIS FIELD) 301 - 302 SEGY FORMAT
REVISION NUMBER SHOULD BE 0 303 -
304 FIXED TRACE LENGTH FLAG. SHOULD
BE 0 305 - 306 EXTENDED TEXTUAL FILE HEADER
RECORDS AFTER BINARY HEADER. SHOULD
BE 0
26
MANDATORY LOCATIONS IN TRACE HEADER   1 - 4
TRACE SEQUENCE NUMBER WITHIN THE LINE 21 - 24
CDP NUMBER  29 - 30 TRACE IDENTIFICATION
CODE. SHOULD BE 1 FOR SEISMIC
DATA  71 - 72 SCALAR TO BE APPLIED TO
COORDINATES IN 181-188 TO GIVE THE REAL
VALUE. POSSIBLE VALUES ARE 1, 10, 100, 1000 OR
10000. IF VE MULTIPLIER IF -VE,
DIVISIOR. SHOULD BE 1 IF X,Y ARE
GIVEN TO THE NEAREST METER. 115 - 116 NUMBER
OF SAMPLES IN THIS TRACE 117 - 118 SAMPLE
INTERVAL IN MICRO SECONDS FOR THIS TRACE. 181 -
184 X COORDINATE OF CDP I85 - 188 Y
COORDINATE OF CDP 197 - 200 SHOTPOINT NUMBER
CORRESPONDING TO THE CDP 201 - 202 SCALAR TO BE
APPLIED TO THE SHOT POINT NUMBER IN 197-200. IF
0, THE SP IS TAKEN AS SUCH. IF VE, MULTIPLIER
IF -VE, DIVISIOR.  EXAMPLE IF SHOT
POINT ABOVE CDP 101 IS 50.5, IT SHOULD
BE STORED AS 505 IN LOCATIONS 197-200
AND -10 AS SCALAR IN LOCATION 201-202
27
DIFFRENET SIGS

• Energistics Data Store Solutions SIG
• The purpose SIG is to conduct collaborative
  dialogue among the active participants, to find
  consensus requirements, and to advocate good
  practices, improved solution products and
  services, and improved industry standards the
  essence of Energistics SIG's in the domain of
  products and services that address the storage
  and management of EP data and information
• Energistics Geoshare SIG
• The purpose is to foster and encourage the use
  of Geoshare as a standard mechanism for exchange
  of data between software products in use in the
  petrotechnical industry.
• It shall guide and direct the development of
  Geoshare as a standard both with respect to the
  data model and encoding specification being used
  and with respect to the programming standards
  and data transfer methods supported

Contd.
28
Expectations from SEIS-SIG

• Standards in Seismic data class at USERS END for
  storing interpretation/intellectual results like
• structure maps in both time and depth ,
  Isopach, isochron both as image /ascii.
• Calibrated velocities
• Porosity prediction in SEGY
• Coherency (Semblance) Cube SEGY
• Impedance cube in SEGY

29
DIFFRENET SIGS
Energistics WITSML SIG The purpose is to
represent the users of well-site generated
drilling data as this relates to the WITSML data
transfer standard. SIG's objectives are to
raise new consensus needs and requirements , to
review new and evolving aspects of the
standards, and to promote the use of the
standard by exchange experiences and other
means.  Integrated Operations SIG The agreed
objectives for the SIG included helping
Energistics to develop and publish a directory
of relevant industry activities, assisting in
the creation and publication of an annotated
glossary, developing a framework description of
functionality and components, and sponsoring a
number of implementation pilot projects.
Contd.
30
(No Transcript)
31
Energistics Board Members

• Mike Benjamin, Schlumberger

32
(No Transcript)
33
DIFFRENET SIGS
Energistics eRegulatory SIG The purpose of the
eRegulatory SIG is to for the regulators and oil
companies in the Energistics community to
recognize and promote collaborative activities
that will improve the efficiency and
effectiveness of technical regulatory actions,
including reporting results, obtaining
permissions, and monitoring operations.