Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

GIS Practices Recommendations w voice-over

729 views

Published on

Practices & recommendations for GIS projects in oil&gas
(download to run the PowerPoint slideshow w voice-over)

Published in: Data & Analytics
  • Be the first to comment

GIS Practices Recommendations w voice-over

  1. 1. GIS Practice Recommendations Schlumberger GIS & Remote Sensing Webinar Andrew Zolnai, Kuwait City and Cambridge UK blog.zolnai.ca
  2. 2. The bottom line • Spatial Integrity and Data Model is • GIS Recommended Practice is for • Minimum Requirements 1. File Structure and Data Model 2. Layer and File Naming Convention 3. Minimum Attributes and Metadata 4. Spatial Integrity QC Requirements 5. Data Delivery Standards
  3. 3. Spatial Integrity and Data Model is • A set of guidelines for managing GIS data associated with all phases of development projects from initial planning to decommissioning
  4. 4. GIS data used in projects includes • Administrative and cadastral boundaries: • licenses, shipping lands, environmental areas • Surveys: • hazards, seismic, gravity, bathymetry, geotechnical, environmental • Facilities and infrastructure locations: • platforms, pipelines, assets, wells, integrity • Met ocean: • current, wind, tidal, wave • Geosciences: • subsurface structures, faults, wells, contacts, salt, seismic attributes • Imagery: • satellite, aerial photography, LIDAR, side-scan sonar
  5. 5. Data is collected from various sources • Head / project office • Third party contractors • Commercial data vendors • Government agencies • Partners and operators • Public domain data sources
  6. 6. Spatial integrity and metadata • Coordinate reference system and precision • Source and date of origin • Use restrictions • Naming conventions • Data model, attribute data, cross-reference / code tables, and symbol sets • Associated reports and descriptive (non- geographic) data
  7. 7. The bottom line • Spatial Integrity and Data Model is • GIS Recommended Practice is for • Minimum Requirements 1. File Structure and Data Model 2. Layer and File Naming Convention 3. Minimum Attributes and Metadata 4. Spatial Integrity QC Requirements 5. Data Delivery Standards
  8. 8. GIS Recommended Practice is for • Those involved in the design, implementation and use of GIS data or applications • Those directly involved in the selection and management of third party contractors who will deliver GIS data or application
  9. 9. 1: File Structure and Data Model • A Project Level folder structure shall be established at project inception to be used for the duration of the project • The folder structure defined in Appendix B should be used. • Additional subfolders may be added where further subdivision of data is required • Existing data models may be adopted for specific data types • Paths, folders and file names should avoid use of blanks and special characters • Paths and folders should always be specified using the UNC notation • Table attributes should always avoid the use of blanks and special characters
  10. 10. 2: Layer and File Naming Convention • Layer and files names should indicate the content of the data. • Paths, file names and attribute names should avoid use of blanks and special characters • Paths and files should always be specified using the UNC notation • Mapped drive notation should not be used, as drives vary from user to user. This includes sources for layer files, links to files and folders in attribute tables, hyperlinks in documents or Web pages • Updates to layers and files where previous versions should be retained for reference should be renamed with a suffix
  11. 11. 3: Minimum Attributes and Metadata • A specification of the Coordinate Reference System (CRS) must be included for geographic data • Metadata must also include entries for a minimum core set of entities • Additional requirements may also apply for specific data types
  12. 12. 4: Spatial Integrity QC Requirements • For Geodetic Control Networks, more exacting requirements apply • For Architecture, Engineering and Construction (A/E/C) facilities management projects (typically confined to small geographic areas typically less than 4,000 ha (10,000 acres) • For all other applications and data categories, requirements vary
  13. 13. 5: Data Delivery Standards • Acceptable formats • Metadata supplied with data must conform to requirements • All data received will require a project specified evaluation period to verify its completeness related to the contract specifications and Operator GIS Practice data standards and requirements • Each data collection activity requires a documented protocol that includes appropriate quality control procedures and quality assurance checks • Availability and archiving of confidential, restricted, and/or sensitive data will be addressed with individual agreements • All raw and processed data, field notes, samples, and sample collection forms generated or collected under are the property of the Operator unless explicitly specified otherwise in contract agreement
  14. 14. Intent and Scope • Intent: • Promote a methodical approach to managing the GIS data associated with development projects • To increase efficiency of finding and using GIS data • To minimize the risks that data will be used for the wrong purposes • Scope: • Applies to work on any operator premises • Other situations where there is a work relationship • As defined in operators’ reporting requirements
  15. 15. Auditing and Compliance • Monitoring and reporting on implementation and progress on meeting targets shall be locally owned and included as part of the annual HSSE self verification process for each Business, Functional and Regional Unit. • The Minimum Requirements of this GIS Recommended Practice will form part of the basis for the audit protocols to be used by the Safety and Operations Audit • Operator businesses and functions that are within the scope of this GIS Recommended Practice shall adopt or modify their procedures and practices to conform to the Minimum Requirements
  16. 16. Administration and Authorisation • Custodian : • Responsible for confirming the accuracy and integrity of content and proposed changes to the practice • Maintainer : • Responsible for the upkeep and continued integrity of the practice, including regular reviews and audits • Adjudicator : • Responsible for authorising and approving changes to the practice
  17. 17. The bottom line • Spatial Integrity and Data Model is • GIS Recommended Practice is for • Minimum Requirements 1. File Structure and Data Model 2. Layer and File Naming Convention 3. Minimum Attributes and Metadata 4. Spatial Integrity QC Requirements 5. Data Delivery Standards
  18. 18. 1: File Structure and Data Model • A project data structure will be established at project inception • The file structure defined should be used • Additional subfolders may be used where there are multiple areas, sources, generations or other subdivisions of data to be maintained distinctly • Existing data models may be adopted for specific data types • Paths, folders and file names should avoid use of blanks and special characters • Paths and folders should always be specified using the UNC notation. • Table attributes should always avoid the use of blanks and special • Note this includes those attributes which may be used for georeferencing purposes (for example, a table which will be joined to a geographic dataset) in text files and RDBMS tables.
  19. 19. 2: Layer and File Naming Convention • Layer and files names should indicate the content of the data • Paths, file names and attribute names should avoid use of blanks and special characters • Paths and files should always be specified using the UNC notation • Mapped drive notation should not be used, as drives vary from user to users • This includes sources for layer files, links to files and folders in attribute tables, hyperlinks in documents or Web pages • Updates to layers and files where previous versions should be retained for reference should be renamed with a suffix
  20. 20. • The Coordinate Reference System (CRS) must be defined, including: • Projection system • Units • Datum • Additional projection parameters (depends on system) 3: Minimum Attributes and Metadata
  21. 21. • Identification: • Purpose • Point of contact • Format • Descriptive keywords • Use Constraints • Status • Spatial resolution • Date and time • Use limitations • Constraint: • Access constraints • Use constraints 3: Minimum Attributes and Metadata
  22. 22. 4: Spatial Integrity QC Requirements • Geodetic control networks established to support • Well planning: • well pads, surface and bottom hole locations, well trajectories, • Platform planning, engineering, positioning: • related moorings, subsea assets, wires, chains, anchors, protection structures, manifolds, tie-ins, wyes, flanges, valves, etc. • Pipeline engineering: • gathering systems, umbilicals, crossings, rights-of-ways, compressor stations, etc. • Utility systems: • poles, power lines, substations, cable locations, rights-of-ways, crossings, etc.
  23. 23. 4: Spatial Integrity QC Requirements • Geodetic control networks established to support • Geophysical exploration surveys • Hazard surveys, including • Transportation systems: roads, railroads, airfields, canals • Flood control and navigation systems: dams, levees, locks • Architectural site or landscape plans • Engineering master planning studies • Hydraulic and hydrological studies
  24. 24. Standards Data type Data model References Well data PPDM www.ppdm.org Well data Energistics www.posc.org Pipeline data APDM www.apdm.net Pipeline data PODS www.pods.org Open Geospatial Consortium OGC www.opengis.org International Association of Oil & Gas Producers EPSG info.ogp.org.uk/geodesy
  25. 25. The bottom line • Spatial Integrity and Data Model is • GIS Recommended Practice is for • Minimum Requirements 1. File Structure and Data Model 2. Layer and File Naming Convention 3. Minimum Attributes and Metadata 4. Spatial Integrity QC Requirements 5. Data Delivery Standards Full document available upon request

×