ESSO ANGOLA Geoscience Information Management Process Angola... · ESSO ANGOLA Geoscience...

1
ESSO ANGOLA Geoscience Information Management Process ESSO ANGOLA Geoscience Information Management Process Directory Structure Information Process Detail Well & Culture Geologic Models Geologic Models and Prospect Interpretation Data Directory Structure StanLAN Information Process Detail Well and Culture Data Seismic Data Well & Culture Data and Prospect Assessments Interpretation Data Reports & Datastore: U:\Assets\Ang_Oper\B15\Business\Admin\G_G Well and Culture Data 1. GeoTech receives data from Vendors, and or F.E 2. Data received via eRoom / FTP / Online Data Room from external drives sources Seismic Data U:\Assets\Ang_Oper\B15\Business\Admin\G_G Location of Final Files ready for use: Wellbook Master Final LAS files external drives sources 3. Geologist provides GeoTech with well operations geologic information. 4. All incoming data is stored on StanLAN. Final LAS files Final Deviation Surveys (Final reports and documents) Well Planning IHS/ Vendors/COV / Govmt OpsGeo/FE (LOGS, G&G Interpreters 4. All incoming data is stored on StanLAN. 5. Raw, Working, and Master (finalized) data is drawn from StanLAN into software interfaces to create ArcGIS, Geolog, and Petrel projects which are saved back to StanLAN. G&G Interpreters Well Data: U:\Assets\Ang_Oper\B15\SubSrfc\Well_Work\Well_Files\ or U:\Assets\Ang_Oper\B15\SubSrfc\Studies\OpsGeo\ Sur, KB) (WH, Dev Sur, KB) (Polygons) / Govmt (Polygons) Data) (LOGS, Pressure Data) G&G Interpreters (Horizon, Faults, Faults Petrel projects which are saved back to StanLAN. 6. Master data is taken out from localized StanLAN directory and stored in an XOM Repository. If well logs, they are stored in Modeling Core Group Well planning Drilling Vendors (ZGY, SEGY Files) (Exploration/ KizA / KizB / KizC / KSatellites / Xikomba) DDR/GDR Final LAS files (Horizon, Faults, Faults polygons, Tops, Contacts. ) Recall by GDS Team, all other data goes to EMSDB via DMC. 7. A Geoframe Master Project receives information from StanLAN and from XOM Repositories. Serves as a bridge between raw Drilling (Geologic Models) (ZGY, SEGY Files) Final LAS files Final Deviation Surveys Final reports and documents data & the Petrel Master project. 8. GeoTech loads basic data from GeoFrame Well Master to Petrel Well Master via OpenSpirit or ascii. Seismic: U:\Ref_Data\Ang\Seismic\B15_Kiz_A_2\3D\3D_Template… 1 2 3 2 0 Well Master via OpenSpirit or ascii. 9. GeoTech loads unique ascii data from LAN to various Petrel Well Master Well data utilizing the Proposed, Approved or Drilling data placement. 3 0 5 0 LINU U:\Ref_Data\Ang\Seismic\B15_Kiz_A_2\3D\3D_Template… User Directory: U:\Assets\Ang_Oper\B15\SubSrfc\Geo\Users… 0 2 3 Drilling data placement. GeoFrame to Petrel curve transfers do not maintain mnemonics correctly ‘Petrel specific’ ascii loading examples: Lithology code, Geo Tech/USG/DM Processing and Data QC Geo Tech/USG/DM Processing and Data QC Geo Tech/USG/DM Processing and Data QC Geo Tech/USG/DM Processing and Data QC Geo Tech/USG/DM Processing and Data QC Geo Tech/USG/DM Processing and Data QC 4D Group / GAPS 0 0 LINU X U:\Assets\Ang_Oper\B15\SubSrfc\Geo\Users… 4 ‘Petrel specific’ ascii loading examples: Lithology code, core data, casing diagram, dip data, etc. Directional surveys ascii loaded due to negative KB values ArcGIS: U:\Assets\Ang_Oper\B15\SubSrfc\Geo\Users SꜳLAN SꜳLAN SꜳLAN SꜳLAN A A A A Directional surveys ascii loaded due to negative KB values 10. Data from the Petrel Well Master is fed into multiple independent Petrel Working Projects via RPT. 11. Data Coordinator makes products available to the Team via 3 5 DM SWIM Petrel Petrel Master Projects (currently there are 2012 and 2013 A A A A 11. Data Coordinator makes products available to the Team via FTP/Online Data Room/external drives. 12. Data for COV’ and Sonangol. 3 1 Petrel Petrel Repository StanLAN Data Petrel Petrel Shared 4 Cꜳꝏ ꝏff Cꜳꝏ ꝏff Cꜳꝏ ꝏff Cꜳꝏ ꝏff Dꜳ Dꜳ Dꜳ Dꜳ DM C Petrel Master Projects (currently there are 2012 and 2013 masters) U:\LVS\Ang_Oper\Master Petrel Working 13. GeoTech updates well data (i.e., well tops) from Petrel Well Master to EMSDB. 14. GT RPT data from Petrel Well Master to Users Petrel Projects 5 1 Team Project (Luanda) Well Planning Data from operator (raw, working, master) Team Project (Houston) 1 U:\LVS\Ang_Oper\Master (All/KizA / KizB / KizC / KSatellites ) OM OM OM OM 6 Working (StanLAN LVS) Geologic Models 20. Geologic models from various sources are made available to the SCII 3 6 2 1 1 2 2 GeoFrame Seismic (Luanda) master) EEAL business (Houston) Petrel Work Directories U:\LVS\Ang_Oper\Work (All/KizA / KizB / KizC / KSatellites ) Geolog /Geo4 OM OM OM OM Dꜳꜳꜳ Dꜳꜳꜳ Dꜳꜳꜳ Dꜳꜳꜳ Rꝏꝏ Rꝏꝏ Rꝏꝏ Rꝏꝏ 6 team….the GT receives the data and works with USG for storage location and distribution 21. Data from the Petrel Well Master is fed into Petrel Models eismic OSP or AS 3 3 3 1 2 Masters (All/KizA / KizB / KizC / KSatellites ) GeoFrame Geolog /Geo4 Wind Geoapps Petroapps Recall ArcGIS/Petrel Culture 21. Data from the Petrel Well Master is fed into Petrel Models 22. Data from the Petrel Interpretation Master is fed into Petrel Models 23. Data Manager makes Petrel products available to the Team via Share to se 3 2 3 3 3 4 S Dꜳꜳ S Dꜳꜳ S Dꜳꜳ S Dꜳꜳ OS P Master Projects: /data/xom/userId Petroapps Recall LAS Files 23. Data Manager makes Petrel products available to the Team via FTP/Online Data Room/external drives 24. Data for COV’ and Sonangol Interpretation Data Geoframe Work Project S 5 2 S Dꜳꜳ S Dꜳꜳ S Dꜳꜳ S Dꜳꜳ ꝏffꝏ ꝏffꝏ ꝏffꝏ ꝏffꝏ P /data/xom/userId ao_wm_welmst (Master Well) Work Projects: Interpretation Data 30. Historic and current interpretations are received from …, documented and distributed to GT’s for loading. 31. GeoTech loads horizons, faults (interpretation products) to Petrel Shared Work Project (Linux) 3 7 2 Petrel Seismic /home/ang5001/ang_main/users1/UserID/proj_name Voxelgeo EMSDB 31. GeoTech loads horizons, faults (interpretation products) to Petrel Shared Team Project (only ascii). 32. GeoTech loads horizons, faults (interpretation products) to GeoFrame working projects. VoxelGeo (Linux) eismic or ASCII 2 2 3 5 7 1 Master (pmseis) 1 RP T U:\LVS\Ang_Oper\Work\B15all\Vg/ EMSDB Well Headers Dir. Srvys Core Info working projects. 33. GeoTech uses OSP or ascii to import interpretation to GeoFrame working projects. 34. G&G RPT’s interpretation data from Petrel Shared Team Project (Linux) RPT to se OSP 2 4 2 3 5 1 1 3 To EEAL To EEAL Team 1 2 Petrel Petrel Petrel Geo4Windows U:\Assets\Ang_Oper\B15\SubSrfc\Studies\OpsGeo\1_Composite_Logs\Working Pick Data To EEAL (Through 34. G&G RPT’s interpretation data from Petrel Shared Team Project to their Petrel working projects. 35. GeoTech loads interpretation data via OSP and/or ASCII to and from GeoFrame and Petrel. G&G may export interpretation data Peterolin k 3 9 Mileston e Products Petroli nk Petrel Master Interp Shared Team Project Geo CompLogs (Well composite Logs) 9 DM/GT) for & COV DM/GT) for Sngl & COV 1 3 7 from GeoFrame and Petrel. G&G may export interpretation data from VoxelGeo for GeoTech to load to GeoFrame or Petrel. 36. G&G shares seismic from the GeoFrame Seismic Masters. 37. G&G RPT’s seismic from the Petrel Seismic Master (pmcs). k 5 Products Products (pmi) Project (Houston) Petrel Well Master 3 7 37. G&G RPT’s seismic from the Petrel Seismic Master (pmcs). 38. Well planning changes from the working projects by G&G may need to be updated into the Petrel Well Master. Geoframe 3 8 40 5 3 8 DM C Master (pmw) 39. XFDB milestone products are made available from interpretation working projects. 40. Data Manager documents, and sends GeoFrame and Petrel Geoframe Well Master 8 40 To EEAL OSP or ASCII C OS P products to the Team. 41. Data share Between Luanda and Houston Seismic Data To EEAL (Through DM/GT) for 1 0 To EEAL (Through DM/GT) for Arch, Sngl & Considerations 1 4 P Seismic Data 50. Seismic data from Vendors is given to 4D / GAPS Re- Processing, then given to the SWIM Team for loading to DM/GT) for Sngl & COV for Arch, Sngl & COV Considerations: Data not incorporated into EEAL Development Plan Reservoir Engineering Petrel work Team 4 Processing, then given to the SWIM Team for loading to Geoframe masters. 51. SWIM team loads data into company-wide GeoFrame Seismic Master Projects. o Production Data o Surveillance o Pressure Data Team Projects Master Projects. 52. SWIM team creates Petrel seismic data (SEGY’s and ZGY’s) in the Ref_Data area from the GeoFrame Seismic Masters and creates seismic links into a single Petrel Master Seismic project GeoTech GeoTech Process Owners: Process Owners: SWIM SWIM Data Data = Data Manager = Data Manager creates seismic links into a single Petrel Master Seismic project (pmcs). 53. Geotechs sends the latest interpretation available to Modeling Group and partners. = Specialist (SWIM) = Specialist (SWIM) Master Project Master Project Data Source Data Source GeoTech (Mandatory) GeoTech (Mandatory) Owners: Owners: SWIM (Mandatory) SWIM (Mandatory) Data Process Data Process Synchronized with Synchronized with = Data Manager = Data Manager Group and partners. = GeoTech = GeoTech XOM Database Repository XOM Database Repository Data Output Data Output Working Project Working Project LAN Data LAN Data XOM Database Repository XOM Database Repository = G&G = G&G Repository Repository Data Data Repository Repository

Transcript of ESSO ANGOLA Geoscience Information Management Process Angola... · ESSO ANGOLA Geoscience...

Page 1: ESSO ANGOLA Geoscience Information Management Process Angola... · ESSO ANGOLA Geoscience Information Management Process ... Faults, Faults Petrel projects which are saved ... GeoTech

ESSO ANGOLA Geoscience Information Management ProcessESSO ANGOLA Geoscience Information Management ProcessDirectory Structure Information Process Detail

Well & Culture Geologic Models Geologic Models

and Prospect Interpretation Data

Directory Structure

StanLAN

Information Process Detail

Well and Culture DataSeismic DataWell & Culture

DataAssessments

and Prospect

Assessments

Interpretation Data

Reports & Datastore:U:\Assets\Ang_Oper\B15\Business\Admin\G_G

Well and Culture Data1. GeoTech receives data from Vendors, and or F.E

2. Data received via eRoom / FTP / Online Data Room from

external drives sources

Seismic Data

U:\Assets\Ang_Oper\B15\Business\Admin\G_G

Location of Final Files ready for use:

• Wellbook Master

• Final LAS files

external drives sources

3. Geologist provides GeoTech with well operations geologic

information.

4. All incoming data is stored on StanLAN.• Final LAS files

• Final Deviation Surveys

• (Final reports and documents)

Well

Planning

IHS/

Vendors/COV

/ Govmt

OpsGeo/FE

(LOGS, G&G Interpreters

4. All incoming data is stored on StanLAN.

5. Raw, Working, and Master (finalized) data is drawn from

StanLAN into software interfaces to create ArcGIS, Geolog, and

Petrel projects which are saved back to StanLAN.• G&G Interpreters

Well Data:U:\Assets\Ang_Oper\B15\SubSrfc\Well_Work\Well_Files\ or

U:\Assets\Ang_Oper\B15\SubSrfc\Studies\OpsGeo\ Sur, KB)

(WH, Dev

Sur, KB)(Polygons)

/ Govmt

(Polygons)Data)

(LOGS,

Pressure

Data)

• G&G Interpreters

(Horizon, Faults, Faults

Petrel projects which are saved back to StanLAN.

6. Master data is taken out from localized StanLAN directory and

stored in an XOM Repository. If well logs, they are stored in

• G&G Interpreters

• Modeling Core Group

• Well planning

• Drilling

Vendors

(ZGY, SEGY Files)U:\Assets\Ang_Oper\B15\SubSrfc\Studies\OpsGeo\

(Exploration/ KizA / KizB / KizC / KSatellites / Xikomba)

• DDR/GDR

• Final LAS files

Sur, KB)Sur, KB)(Polygons)(Polygons)Data)Data) (Horizon, Faults, Faults

polygons, Tops, Contacts. )

stored in an XOM Repository. If well logs, they are stored in

Recall by GDS Team, all other data goes to EMSDB via DMC.

7. A Geoframe Master Project receives information from StanLAN

and from XOM Repositories. Serves as a bridge between raw

• Drilling

(Geologic Models)

(ZGY, SEGY Files)

• Final LAS files

• Final Deviation Surveys

• Final reports and documents

and from XOM Repositories. Serves as a bridge between raw

data & the Petrel Master project.

8. GeoTech loads basic data from GeoFrame Well Master to Petrel

Well Master via OpenSpirit or ascii.

(Geologic Models)(Geologic Models)

Seismic:

U:\Ref_Data\Ang\Seismic\B15_Kiz_A_2\3D\3D_Template…

1 2 3 2

0

Well Master via OpenSpirit or ascii.

9. GeoTech loads unique ascii data from LAN to various Petrel

Well Master Well data utilizing the Proposed, Approved or

Drilling data placement.

3

0

5

0LINUU:\Ref_Data\Ang\Seismic\B15_Kiz_A_2\3D\3D_Template…

User Directory:

U:\Assets\Ang_Oper\B15\SubSrfc\Geo\Users…

0

2

3

Drilling data placement.

• GeoFrame to Petrel curve transfers do not maintain

mnemonics correctly

• ‘Petrel specific’ ascii loading examples: Lithology code,

Geo Tech/USG/DM

Processing and Data QC

Geo Tech/USG/DM

Processing and Data QC

Geo Tech/USG/DM

Processing and Data QC

Geo Tech/USG/DM

Processing and Data QCGeo Tech/USG/DM

Processing and Data QC

Geo Tech/USG/DM

Processing and Data QC4D Group / GAPS

0 0LINU

X

U:\Assets\Ang_Oper\B15\SubSrfc\Geo\Users…

4

• ‘Petrel specific’ ascii loading examples: Lithology code,

core data,

casing diagram, dip data, etc.

• Directional surveys – ascii loaded due to negative KB valuesArcGIS:

U:\Assets\Ang_Oper\B15\SubSrfc\Geo\Users StanLANStanLANStanLANStanLAN

AssetAssetAssetAsset

• Directional surveys – ascii loaded due to negative KB values

10. Data from the Petrel Well Master is fed into multiple independent

Petrel Working Projects via RPT.

11. Data Coordinator makes products available to the Team via 3

5DM

SWIMPetrel

Petrel Master Projects (currently there are 2012 and 2013

AssetAssetAssetAsset 11. Data Coordinator makes products available to the Team via

FTP/Online Data Room/external drives.

12. Data for COV’ and Sonangol.

3

1Petrel Petrel

Repository StanLAN DataPetrel Petrel

Shared 4

Creation of Creation of Creation of Creation of

DeliverablesDeliverablesDeliverablesDeliverables

DM

C

Petrel Master Projects (currently there are 2012 and 2013

masters)

U:\LVS\Ang_Oper\MasterPetrel

Working

12. Data for COV’ and Sonangol.

13. GeoTech updates well data (i.e., well tops) from Petrel Well

Master to EMSDB.14. GT RPT data from Petrel Well Master to Users Petrel Projects

5

1

Repository

Team

Project(Luanda)

• Well Planning

• Data from operator

(raw, working,

master)

Shared

Team

Project(Houston)

4

1

U:\LVS\Ang_Oper\Master

• (All/KizA / KizB / KizC / KSatellites )

XOM XOM XOM XOM

6

Working

(StanLAN

LVS)

14. GT RPT data from Petrel Well Master to Users Petrel Projects

Geologic Models20. Geologic models from various sources are made available to the

OS

P o

r A

SC

II

3

62

1

1

2

2

GeoFrame

Seismic

(Luanda)(Luanda)master)

• EEAL business

(Houston)(Houston)

Petrel Work Directories

U:\LVS\Ang_Oper\Work

• (All/KizA / KizB / KizC / KSatellites ) Geolog/Geo4

XOM XOM XOM XOM

Database Database Database Database

RepositoryRepositoryRepositoryRepository

6LVS) 20. Geologic models from various sources are made available to the

team….the GT receives the data and works with USG for

storage location and distribution

21. Data from the Petrel Well Master is fed into Petrel Models

Sh

are

to

se

ism

ic

OS

P o

r A

SC

II

33 3

61 2

Seismic

Masters

• (All/KizA / KizB / KizC / KSatellites )

GeoFrame

Geolog/Geo4

Wind• Geoapps

• PetroappsRecall

ArcGIS/Petrel• Culture

21. Data from the Petrel Well Master is fed into Petrel Models

22. Data from the Petrel Interpretation Master is fed into Petrel

Models

23. Data Manager makes Petrel products available to the Team via Sh

are

to

se

ism

ic

3

2

3

3

3

4

Seismic Data Seismic Data Seismic Data Seismic Data

OS

PGeoFrame

Master Projects:

/data/xom/userId

• PetroappsRecall

• LAS Files

23. Data Manager makes Petrel products available to the Team via

FTP/Online Data Room/external drives

24. Data for COV’ and Sonangol

Interpretation Data

Geoframe

Work Project

Sh

are

to

se

ism

ic

5

2

Seismic Data Seismic Data Seismic Data Seismic Data

WorkflowWorkflowWorkflowWorkflow

P

/data/xom/userId• ao_wm_welmst (Master Well)

Work Projects:

Interpretation Data30. Historic and current interpretations are received from …,

documented and distributed to GT’s for loading.31. GeoTech loads horizons, faults (interpretation products) to Petrel Shared

Work Project

(Linux)

3

7

2Petrel

Seismic • /home/ang5001/ang_main/users1/UserID/proj_name

VoxelgeoEMSDB

31. GeoTech loads horizons, faults (interpretation products) to Petrel Shared

Team Project (only ascii).

32. GeoTech loads horizons, faults (interpretation products) to GeoFrame

working projects.VoxelGeo

(Linux)

RP

T t

o s

eis

mic

OS

P o

r A

SC

II

223

5

7

1

Seismic

Master

(pmseis)1

RP

T

U:\LVS\Ang_Oper\Work\B15all\Vg/EMSDB

• Well Headers

• Dir. Srvys

• Core Info

working projects.33. GeoTech uses OSP or ascii to import interpretation to GeoFrame working

projects.

34. G&G RPT’s interpretation data from Petrel Shared Team Project

(Linux)

RP

T t

o s

eis

mic

OS

P o

r A

SC

II

2

4

2

351

1

3

To EEAL To EEAL

Team

1

2

Petrel Petrel Petrel

Geo4Windows U:\Assets\Ang_Oper\B15\SubSrfc\Studies\OpsGeo\1_Composite_Logs\Working

• Core Info

• Pick DataTo EEAL

(Through

34. G&G RPT’s interpretation data from Petrel Shared Team Project

to their Petrel working projects.

35. GeoTech loads interpretation data via OSP and/or ASCII to and

from GeoFrame and Petrel. G&G may export interpretation data

Peterolin

k

3

9

Team

Mileston

e

Products

Petroli

nk

Petrel

Master

Interp

Petrel

Shared

Team

ProjectU:\Assets\Ang_Oper\B15\SubSrfc\Studies\OpsGeo\1_Composite_Logs\Working

Geo CompLogs

• (Well composite Logs) 9

DM/GT) for

& COV

(Through

DM/GT) for

Sngl & COV 1

37

from GeoFrame and Petrel. G&G may export interpretation data

from VoxelGeo for GeoTech to load to GeoFrame or Petrel.

36. G&G shares seismic from the GeoFrame Seismic Masters.

37. G&G RPT’s seismic from the Petrel Seismic Master (pmcs).

k

5

ProductsProductsnk Interp

(pmi) (Houston)

Project(Houston)

Petrel Well

Master

37

7

37. G&G RPT’s seismic from the Petrel Seismic Master (pmcs).

38. Well planning changes from the working projects by G&G may

need to be updated into the Petrel Well Master.

Geoframe

3

840

5

38

DM

CMaster

(pmw)39. XFDB milestone products are made available from interpretation

working projects.

40. Data Manager documents, and sends GeoFrame and Petrel

Geoframe

Well Master

840

To EEAL

OSP or ASCII

DM

C

OS

P 40. Data Manager documents, and sends GeoFrame and Petrel

products to the Team.

41. Data share Between Luanda and Houston

Seismic Data

To EEAL

(Through

DM/GT) for

1

0

To EEAL

(Through DM/GT)

for Arch, Sngl & Considerations

1

4

P

Seismic Data50. Seismic data from Vendors is given to 4D / GAPS Re-

Processing, then given to the SWIM Team for loading to

DM/GT) for

Sngl & COV

for Arch, Sngl &

COV Considerations:

Data not incorporated into EEAL Development Plan• Reservoir Engineering

Petrel work

Team

4

Processing, then given to the SWIM Team for loading to

Geoframe masters.

51. SWIM team loads data into company-wide GeoFrame Seismic

Master Projects.

• Reservoir Engineering

o Production Data

o Surveillance

o Pressure Data

Team

Projects

Master Projects.

52. SWIM team creates Petrel seismic data (SEGY’s and ZGY’s) in

the Ref_Data area from the GeoFrame Seismic Masters and

creates seismic links into a single Petrel Master Seismic project GeoTechGeoTech

Process

Owners:

Process

Owners:SWIMSWIM Data Data

= Data Manager= Data Manager

creates seismic links into a single Petrel Master Seismic project

(pmcs).

53. Geotechs sends the latest interpretation available to Modeling

Group and partners.

= Specialist (SWIM)= Specialist (SWIM)Master ProjectMaster ProjectData SourceData SourceGeoTech

(Mandatory)

GeoTech

(Mandatory)

Owners:Owners:SWIM

(Mandatory)

SWIM

(Mandatory)

Data

Process

Data

ProcessSynchronized

with

Synchronized

with

= Data Manager= Data Manager Group and partners.

= GeoTech= GeoTechXOM Database

Repository

XOM Database

RepositoryData OutputData Output Working ProjectWorking Project

LAN

Data

LAN

Data

XOM Database

Repository

XOM Database

Repository

= G&G = G&G

RepositoryRepositoryDataDataRepositoryRepository