1. 7) COVID 19 Lessons Learrned/Improvements Required
1.1. Geospatial
1.1.1. Improvements
1.1.1.1. Migration to One Map Cloud Edition
1.1.2. Lessons Learned
1.2. Geoscience & Wells
1.2.1. Improvements
1.2.1.1. Migration to Stratus
1.2.2. Lessons Learned
1.3. Production
1.3.1. Improvements
1.3.1.1. EC/BO Migration to Cloud
1.4. Reservoir
1.4.1. Improvements
1.4.2. survdb to Cloud
1.5. Physical Data Management
1.5.1. Improvements
1.5.1.1. Migration to Global Physical Data Catalogue
1.6. Information Management
1.6.1. Analyze and effectively manage access to information from home.
1.6.1.1. Maximize Smart Search usability
1.6.2. Migration to single source of DM (TDS)
1.6.2.1. Migrate all existing data from NT shares into one common document management tool
2. 1) Getting to know Main Regional Stakeholder groups
2.1. Geospatial
2.1.1. GOO Offshore
2.1.1.1. IMT - Sevinj Alifkhanova
2.1.1.2. Logistics - Jamal Fathi-khoshginabi/Elshad Aliyev
2.1.1.3. Offshore Pipeline IM Team - Mukhtar Alimardanov
2.1.1.4. Subsea Operations - Vugar Efendiyev/Peter Williams
2.1.1.5. IMT (Aze) - Sevinj Alifkhanova
2.1.1.6. IMT (Geo) - Pridon Niguriani
2.1.1.7. Logistics - Jamal Fathi-khoshginabi/Elshad Aliyev
2.1.1.8. Subsea Operations (Engineering) - Vugar Efendiyev/Peter Williams
2.1.1.9. Offshore Pipeline IM Team - Mukhtar Alimardanov
2.1.2. GOO Onshore - Midstream
2.1.2.1. Midstream Pipeline IM Team - Nizami Aslanov
2.1.2.2. Midstream Operations (Aze) - Akif Ahmadov
2.1.2.3. Midstream Operations (Geo) - Gianluca Moscarda
2.1.2.4. Sangachal Subsidence - Zaur Zakiyev
2.1.2.5. Corrosion Team (Aze) - Kanan Kerimov
2.1.2.6. Corrosion Team (Geo) Dato Bejetadze
2.1.2.7. Sangachal Pipeline Team - Mehman Azimov
2.1.2.8. Environmental (Geo) - Zurab Topuridze
2.1.2.9. Environmental (Aze) - Nargiz Garajayeva/Nijat/Zaur Hasanov
2.1.3. Res Dev
2.1.3.1. Survey&Positioning Team - Elchin Teymurlu
2.1.3.2. SIM - Irada Huseynova
2.1.3.3. NWD - Emil Miraliyev (GHZ DB - R-script)
2.1.4. GPO
2.1.4.1. Survey Team - Chris Maw
2.1.4.2. Project Information Management - Rob Venn
2.1.4.3. Global Subsea Execution (GSE) - Adrian Walker/Grant Watson
2.1.5. C&EA
2.1.5.1. Permitting&Regulatory Affairs - Joseph Metreveli
2.1.5.2. Permitting&Regulatory Affairs - Ismayil Ibrahimov
2.1.5.3. Security (Aze) - Murad Abbasov
2.1.5.4. Security (Geo) - Sandro Chitatdze
2.1.6. Exploration - Nazim Abdullayev
2.1.7. Central Pipeline Engineering
2.1.7.1. Anomaly Tracking One Map Tool - Euan Davidson
2.1.8. Central Res Dev
2.1.8.1. Geohazard Team - Gareth Wood
2.2. Geoscience & Wells
2.2.1. Res Dev
2.2.1.1. RMT
2.2.1.1.1. ACG Area Teams - Jonathan Williams, Farana Hajinskaya, Farhad Sadigov
2.2.1.1.2. Shah Deniz Team - Firuz Salamov, Samir Sadigov
2.2.1.2. NWD- Okugbaye, Emmanuel
2.2.1.3. Geohazards Team - Okugbaye, Emmanuel; Tarlan
2.2.1.4. PAT- Bergbauer, Stephan
2.2.1.5. BMT- Azizov Ehtiram
2.2.1.6. Survey Positioning Survey- Elchin Teymurly
2.2.2. Partners
2.2.3. Exploration- Nazim Abdullayev
2.3. Production
2.3.1. Res Dev
2.3.1.1. RMT- Ibrahimov Turan
2.3.1.2. Performance Team- Aydan Ibrahimova
2.3.1.3. BMT
2.3.1.3.1. ACG Area Teams - Valera Gasanov, Ehtiram Azizov
2.3.1.3.2. Shah Deniz - Vusal Fataliyev
2.3.2. Corrosion Team
2.3.3. Hydrocarbon Management Team- Babayeva NArmina
2.3.4. Midstream Team
2.3.4.1. Gas Management Team
2.3.5. Partners
2.4. Reservoir
2.4.1. Res Dev
2.4.1.1. RMT
2.4.1.2. PAT - Bergbauer Stephan
2.4.1.3. Performance Team - Aydan Ibrahimova
2.4.1.4. BMT - Pashayev Ahad, Azizov Ehtiram, Valera Gasanov
2.5. Physical Data Management
2.5.1. Res Dev
2.5.1.1. SIM - Irada Huseynova
2.5.1.2. ACG FieldWide Modeling Team - Ismayilov Nariman
2.5.1.3. ACG FieldWide Projects and Appraisal Team - Guliyev Rufat
2.5.1.4. Azeri Reservoir Delivery Team - Farida Mammadkhanova
2.5.1.5. SD RD Area Team - Teymur Ibrahimzade
2.5.1.6. Res Dev
2.5.1.6.1. SIM - Irada Huseynova
2.5.1.6.2. ACG FieldWide Modeling Team - Ismayilov Nariman
2.5.1.6.3. ACG FieldWide Projects and Appraisal Team - Guliyev Rufat
2.5.1.6.4. Azeri Reservoir Delivery Team - Farida Mammadkhanova
2.5.1.6.5. SD RD Area Team - Teymur Ibrahimzade
2.5.2. Exploration - Nazim Abdullayev
2.5.3. SOCAR
2.5.4. Storage Service Vendors
2.5.4.1. UK Based
2.5.4.1.1. Iron Mountain
2.5.4.1.2. ALS
2.5.4.1.3. Expro
2.5.4.1.4. Stratum
2.5.4.1.5. CoreLab
2.5.4.2. Azerbaijan Based
2.5.4.2.1. AzLab
2.5.4.2.2. Global Interiors Group
2.5.5. ACG Partner
2.5.5.1. Exxon
2.5.5.2. Inpex
2.5.5.3. Itochu
2.5.5.4. Ongc
2.5.5.5. SOCAR
2.5.5.6. AzACG
2.5.5.7. TPAO
2.5.5.8. Chevron
2.5.5.9. Equinor
2.5.6. Physical Data Management Domain
2.6. Information Management
2.6.1. Cement & Fluids teams
2.6.1.1. Adil Bayramov
2.6.1.2. Mahmudov, Nurlan
2.6.2. Rig Mods & Maintenance
2.6.2.1. Colin Gunn
2.6.2.2. Darren Wrack
2.6.3. ResDev NWD
2.6.3.1. Murad Murtuzaliyev
2.6.4. ResDev BMT
2.6.4.1. Emin Babazade
2.6.5. SIM
2.6.5.1. Orkhan Hajiev
2.6.5.2. Irada Huseynova
2.6.6. HSE & Risk Management
2.6.6.1. Alysheva, Afag
2.6.6.2. Gunay Alkhasova
2.6.7. ACG wells ops & engineering
2.6.7.1. Ismayil Yusifov
2.6.7.2. Louise Jacobsen Plutt
2.6.8. SD wells ops & engineering
2.6.8.1. Joe Mellor
2.6.8.2. Aoudia Mohamed
2.6.9. Wells Area EA - S&OR
2.6.9.1. Carlos Schiavenato
2.6.10. Well Material Management
2.6.10.1. Natavan Mamedova
2.6.11. ACG & SD Completion / Intervention
2.6.11.1. Loboguerrero Santiago
2.6.11.2. Savelli Paul
3. 3) Understanding SIM Domains Work Management & Discussing ways of its Standardization/Simplification
3.1. Geospatial
3.1.1. Standardization
3.1.1.1. Separate DevOps Dashboards
3.1.1.1.1. Improvement
3.1.1.2. Internal DevOps Dashboards
3.1.1.2.1. Imrpovement
3.1.2. Simplifications
3.2. Geoscience & Wells
3.3. Production
3.3.1. Standardization
3.3.2. SImplification
3.4. Reservoir
3.5. Information Management
3.5.1. Standardization
3.5.1.1. DM & IM common processes for all domains is a must
3.5.1.1.1. Establish common document management process in Subsurface Area by implementing document management framework (under development by Central Team)
3.5.1.2. Finding ways to structure the information in a way that is easily accessible
3.5.1.3. Common KPIs should be established with visual dashboards
3.5.1.4. One common tool for document management lifecycle i.e creation, review, publish, retire.
3.5.1.4.1. Move all existing documents are storing in different areas (NT shares, SharePoint etc.) in one common document management tool
3.5.1.4.2. Set clear access management without multilayers and complexity
3.5.2. Simplification
3.5.2.1. Better communication promotion & collaboration which results in better informational accessibility between functions
3.5.2.2. Define levels of access through automated information classification, codifying
3.5.2.3. Easy access to required documents without searching in multiple areas by implementing one common document management tool
3.6. Physical Data Management
3.6.1. Standardization
3.6.1.1. Internal DevOps Dashboards
3.6.1.1.1. Improvement
3.6.2. Simplifications
3.6.2.1. Improvement
3.6.2.1.1. Aggregation of SIM DevOps Boards into 1
3.6.2.2. Separate DevOps Dashboards
4. 5) Understanding Domain Capability Successes/Gaps (CDF) & Improvements Needed
4.1. Information Management
4.1.1. Document Management
4.1.2. Information Management
4.2. Physical Data Management
4.2.1. Physical Data Asset Management
4.2.1.1. Successes
4.2.1.1.1. PDM Dashboard
4.2.1.1.2. AGT PDM Vendors Landscape
4.2.1.1.3. Storage Management
4.2.1.1.4. Warehouse Audit
4.2.1.2. Improvement
4.2.1.2.1. Contract Management
4.2.1.3. Gaps
4.2.1.3.1. Cost Management
4.2.1.3.2. Regional PDM Procedure
4.2.2. Digitisation of Physical Data Assets
4.2.2.1. Successes
4.2.2.1.1. SSA (Subsurface Scanning and Access) Project
4.2.2.2. Improvement
4.2.2.2.1. Embed Machine Leaning methods to extract data from scanned hard copies, well logs etc.
4.2.2.2.2. Review existing physical data sets for digitization and disposal
4.2.2.3. Gaps
4.2.2.3.1. Scanning quality
4.3. Geospatial
4.4. Geoscience & Wells
4.4.1. OneMap metadata and folder structure improvement
4.5. Reservoir
4.5.1. using FME for monitoring database
4.6. Production
4.6.1. Improve knowledge of Palantir
4.6.2. Improve knowledge of Production reporting system
5. 2) Understanding Business Requirements/Goals & Prioritization Mechanisms
5.1. Geospatial
5.1.1. Geospatial Data/Models Management
5.1.1.1. Offshore PODS 5.2.3 Migration
5.1.1.1.1. Per stakeholder plan
5.1.1.2. Onshore PODS 5.2.3 Migration
5.1.1.2.1. Per stakeholder plan
5.1.1.3. ESSM
5.1.1.4. SSDM
5.1.2. One Map Services Provision
5.1.2.1. Onshore PODS Web Services
5.1.2.1.1. Per stakeholder plan
5.1.2.2. Offshore PODS Web Services
5.1.2.2.1. Per stakeholder plan
5.1.3. Visualisation
5.1.3.1. Caspian Sea Level Dashboard
5.1.3.2. Sangachal Subsidence Dashboards
5.1.4. Domain Function Requirements
5.1.4.1. Implementation of GVcp Process
5.1.4.1.1. Per domain functional plan
5.1.5. Technical Support
5.1.6. Prioritization Mechanisms
5.2. Geoscience & Wells
5.3. Production
5.4. Reservoir
5.5. Information Management
5.5.1. Community of Practice
5.5.1.1. A collaborative net to connect with colleagues & bridge geographical locations to share information & experience
5.5.2. Document Management
5.5.2.1. Atlas
5.5.2.1.1. Current Control & Staging Document Storage
5.5.2.2. TDS
5.5.2.2.1. Upcoming Regional Control Document Storage
5.5.2.3. Document Neighborhood
5.5.2.4. Regional DM procedure compliance with Global procedure
5.5.2.4.1. Subsurface & GWO DM process integration
5.5.2.5. Embed common document management process in subsurface
5.5.3. Domain Functional Requirements
5.5.3.1. Smart Search
5.5.3.1.1. Search platform for a powerful collaboration and incremental improvement of engine
5.5.3.2. IM Landscape
5.5.3.2.1. Understanding how best to manage all information & associated tools is the key objective
5.5.3.3. Common Document Management Framework
5.5.3.3.1. Establish scope & guidelines for Attic (archive automated process)
5.5.4. Region Requirements
5.5.4.1. Group Audit
5.5.4.1.1. Ensuring documents & records are stored in the proper & control location
5.5.4.1.2. Ensuring function regional procedures & guidelines are complied with Global recommendations & practices
5.5.4.2. Knowledge sharing
5.5.4.2.1. Share our knowledge, leanings and success stories with major industry players in the region (SIM Q-newsletter)
5.6. Physical Data Management
5.6.1. Domain Function Requirements
5.6.1.1. AGT Storage Service Vendors List
5.6.1.1.1. Identify any vendors not currently capture in the Physical Data Management Dashboard
5.6.1.2. Identify opportunities for digitalization and disposal physically unique datasets
5.6.2. Region Requirements
5.6.2.1. Implement the latest storage requirements for storage service vendors
5.6.2.2. Warehouse audit per vendor each year
5.6.2.3. Support Physical Data Requests
5.6.2.4. Develop procedure/guideline for Region
6. 4) Understanding Domain Work Successes/Gaps & Improvements Needed
6.1. Geospatial
6.1.1. Works Well
6.1.1.1. SDE
6.1.1.1.1. One Map
6.1.1.1.2. SSDM Data Loading
6.1.1.1.3. Surveys
6.1.1.2. WebSites
6.1.1.2.1. Air Gap
6.1.1.3. SharePoint
6.1.1.3.1. Controlled Charts
6.1.1.4. Data Dashboarding
6.1.1.4.1. PowerBI
6.1.1.4.2. Spotfire
6.1.1.4.3. Ops Dashboard
6.1.2. Does not Work Well
6.1.2.1. Shared Drives Subsea Surveys
6.1.2.1.1. Subsea Survey Data
6.1.2.2. Unstructured Data
6.1.2.2.1. Charts Update
6.1.2.3. PODS Data Loading
6.1.2.3.1. ArcMap/Pro
6.1.2.3.2. FME
6.2. Geoscience & Wells
6.3. Production
6.3.1. System of Record ???
6.3.1.1. Production Reporting System
6.3.1.1.1. Imrpovement
6.3.2. Palantir /Foundary
6.3.2.1. Improvement
6.3.2.1.1. Aggregation of SIM DevOps Boards into 1
6.4. Reservoir
6.5. Information Management
6.5.1. Works Well
6.5.1.1. SmartSearch
6.5.1.1.1. Python
6.5.1.1.2. Incremental improvement of search features
6.5.1.1.3. Regular Share-point and addresses for indexation
6.5.1.2. Control pool significantly reduced. Release of 'good to have' information to HVBI area
6.5.1.2.1. Defined to Periodic, Record & Informal
6.5.1.3. Control Documents approval process through DocuSign.
6.5.2. Gaps
6.5.2.1. Regional functional procedures shall be assessed vs Global, regular process to be set
6.5.2.2. No clear document management process in ResDev
6.5.2.3. No clear document management tool to meet document management lifecycle requirements in ResDev
6.5.2.4. Archive process for Subsurface & DC&I as part of Document Control
6.5.2.4.1. ATTIC tool linkage to be set
6.5.2.5. B2B transmit electronic process to be set for ResDev & Wells functions
6.5.3. Improvement Needed
6.5.3.1. 100128 to be adjusted based on gaps
6.5.3.2. Regulatory Compliance process
6.5.3.3. Understanding sub-functional needs
6.5.3.4. Fitting stakeholders requirements into existing document management process
6.5.3.5. Access management for contractors
6.6. Physical Data Management
6.6.1. Works Well
6.6.1.1. PowerBi
6.6.1.1.1. AGT PDM Vendors Catalogue
6.6.1.1.2. ACG Partner Transmittal Tracker
6.6.1.2. Warehouse Audit plan for local storage service vendors
6.6.1.2.1. Xazar Office Storage
6.6.1.2.2. Sangachal Storage
6.6.1.2.3. Global Interiors Group Storage
6.6.1.2.4. AzLab Storage
6.6.1.3. Region Physical Data Management Requests
6.6.2. Does not Works Well
6.6.2.1. Direct access into vendors data, access only by specific third party site
7. 6) Understanding ways for development of Collaboration between SIM Domains
7.1. Geospatial
7.1.1. Subsurface Data Publishing to One Map
7.2. Geoscience & Wells
7.3. Production
7.3.1. Collaboration between all existing domains in frame of DM, IM access and Smart Search linkage, publish the subsurface and production data to OneMAp
7.4. Reservoir
7.5. Information Management
7.5.1. Collaboration between all existing domains in frame of DM, IM access and Smart Search linkage
7.6. Physical Data Management
7.6.1. Collaboration with Geoscience & Wells domain during physical data requests