Presentations made at the ESRI European Petroleum User Group (PUG) illustrated how widely GIS is now used in a variety of upstream and midstream contexts. Esri’s GIS has become a popular development platform for a range of projects from shale play evaluation to real time vessel tracking and situational awareness. But it is not an out-of-the box solution and project costs greatly exceed licensing fees.
Total’s Arthur Gayazov showed how GIS has proved to be the tool of choice in the context of shale new ventures in Russia. Evaluating the potential for non-conventional (shale) plays involves a very wide range of data types. These include sedimentology, shale petrophysics, kerogen maturity and more. Russia’s West Siberian basin covers some 2million km2, larger than any current US play. There is proven overpressure and recoverable reserves in the 30-70 billion barrels range. Map-based play assessment starts with a selection of basins and geological proxies for modeling and mapping in ArcGIS and Petrel. Common risk segment and common volume segment maps were created using Exprodat’s TeamGIS extension for ESRI’s Spatial Analyst. GIS works as an integration platform as it provides quick access to multiple in-house data sources. Oil in place has been calculated displayed along with cultural data (satellite imagery, published maps) to get an idea of accessibility. All can be viewed as ‘effective area’ and ‘chance of success’ maps using TeamGIS. The results look promising with up to 4.5 million bbl/km2 for the area of interest. TeamGIS Unconventional Analyst was also used to investigate drill spacing and timing constraints. ‘GIS is the best tool for extensive unconventional drilling programs.’
Jeff Allen (Novara) offered an insight into different pipeline data models. Different segments of the industry from gathering, through midstream to transmission and distribution deploy variously APDM, PODS relational, PODS Oracle spatial, PODS Esri, ISAT or proprietary vendor models. The APDM model has morphed into UPDM (utility and pipeline distribution model) that includes ‘ALRP*’ risk data. UPDM is ‘pipeline centric’ and geodatabase-based. In the ‘moderately normalized’ model, each component is explicitly represented as single database table object.
Data from tankers’ automatic identification systems (AIS), a VHF signal captured by a worldwide network of receivers, is ‘big.’ Karl-John Pedersen showed how DNV GL has kitted up to track and use such data in oil and gas. AIS data provides detailed tracks of vessel movements around offshore facilities or busy ports and loading facilities. Analytics of such data sets provides risk reduction to DNV’s oil and gas clients. AIS shipping data is captured to an IBM Neteeza appliance, a ‘big data’ solution that includes ESRI spatial. The Neteeza data warehouse is coupled to DNV’s Cognos environment. Data is accessed via ArcToolbox query or Python. Maps of ship tracks are served from ArcGIS Server. ESRI Maps for Cognos also ran. There are some limitations: ArcGIS can’t write to Neteeza, there is a lack of raster support and a limited user base. The system has improved AIS data availability and enables non GIS users to perform analytics.
Catherine Hams showed how Cairn Energy has built an emergency response web portal for its Moroccan venture leveraging a hybrid ArcGIS online, ArcGIS Server/desktop. The portal, a ‘logistics game changer’ is now available directly from the Cairn Enery portal alongside data sources including Petroview, Tellus and FRogi.
A presentation from GXMaps addressed challenges in map management, in particular the thorny problem of version control and how to avoid decisions based on out-of-date maps. The answer is to use online, quality assured web maps and mobile endpoints. If you have to use paper, make sure there is a QR code for version checking.
Willbros’ Peter Veenstra wants to make GIS work for folks ‘without a GIS inclination’ by bridging the gap between GIS and engineers. Which means linking to documents, ‘the ultimate repository for ‘real’ information.’ Engineering information is meticulously collected and assembled but as it transitions to the GIS, much is ‘lost in translation.’ Terminology is different, data model footprints may not match. Engineers say, ‘just give us our data’ and ‘where is the easy button?’ The answer is to use the ESRI model builder to provide hyperlinks from the GIS to engineering documents in Maximo, Documentum, Sharepoint, Scada and corrosion management systems. ‘GIS does not need to store these items,’ ‘everything is the new data model!’
Keith Winning has taken a similar approach in CBI’s advanced engineering GIS ‘AEGIS,’ for pipelines. Winning is lead pipeline engineer on the BP operated Baku-Tbilisi-Ceyhan pipeline which is using an extended PODS model to bridge the gap between engineering/CAD and GIS. AEGIS integrates CAD and GIS systems by data sharing.
Sylvain Bard-Maïer warns that in a large GIS project such as Total’s online catalog, ‘E&P Maps,’ the direct cost of development is just the tip of the iceberg. For such a large GIS project, perhaps 15% of costs go on software licenses while 85% is ‘hidden’ involving data QC, standardization and GIS portal administration. ArcMap Document (.mxd) data files embed corporate standards for layers and symbology. Here, Total has developed an FME-based toolset to help and has established workflows and training for users. Maps can now be delivered across the Total network to mobile users.
The concept of a common operating platform (COP), as presented by Tullow’s Colleen Abell, was derived from a US Government requirement for a single overview of operations such as oil spill mitigation that gives on and off-scene personnel the same information and view. Tullows crisis management team used to rely on Google Earth and paper maps. Tullow now is developing a proof of concept COP with ArcGIS Online. A test scenario involves a blowout on a West African deep water well followed by a spill. The COP dashboard shows ship positions and ROV video of the BOP. The map shows locations of hospitals and shelters, vessels, aircraft, relief well locations and dispersant stockpiles. The COP also provides KPIs for executives and a post-exercise analysis and review (PEAR) function. Storytelling templates have been authored for communication with the public.
Boudewijn Possel showed how Fugro has used GIS to manage risks of offshore infrastructure. One case history involved a site survey and risk analysis of client Taqa’s loading terminal offshore Netherlands. GIS lets Fugro blend site survey data with pipeline features and rock dumps. The terminal management system includes 10 years of historical data on pipeline depth of burial, free spans, sandwave migration and more. Fugro offers analytics and a risk matrix for events such as dropped/dragged anchors and trenching. A ‘reciprocal of risk’ map was used to re-evaluate survey design. Data is also available remotely using web map services. ‘PINS,’ an acoustic pipeline inspection methodology originally developed for BP, has also been deployed.
Berik Davies outlined Shell’s implementation, with help from Willbros, of the ArcGIS pipeline data model (APDM) for use in its integrity management program. What problem is APDM solving? Davies showed some scary photos of the 2014 Kaohsiung, Taiwan gas pipeline explosion which killed 32. ‘We want to be able to say our pipelines are safe and to keep the hydrocarbons in the pipe.’ This is being achieved by using APDM as single system of record that fits with other tools. APDM is an auditable, global ‘public’ standard for Shell. The data model is neither too light (as per the default APDM 6 template) nor too heavy (as in APDM 4). The ideas is to store external document references in an APDM table to ‘avoid geodatabase bloat.’ The model needs to tie with Shell standards for symbology, geomodeling, enterprise GIS and with IT guidelines. The model embraces SAP functional location tags, document numbering to tie to the engineering data warehouse and to the LiveLink DMS. The solution, built on the latest APDM 6.0 release modeled in Enterprise Architect, will be Shell’s system of record for all pipeline activity. Notably including pipe integrity management and risk based assessment with w-PIMS. Data will be accessible through the Shell ‘MyMaps’ portal and, for engineers, as a quick view engineering report. APDM is ‘strong and fit for purpose.’ Moreover there is a ‘strong pull from the business to make this happen.’ The solutions is to be deployed on the troubled Kashagan project where production was halted last year following a pipeline leak!
Renaud Laurain (Statoil), has used ArcGIS to characterize and filter seismic interference from other seismic vessels operating simultaneously in the neighborhood. During the summer of 2014 in the North Sea Tampen area, up to 10 vessels were in operation. The technique involves modeling seismic arrivals from ‘foreign’ shots which can then be filtered. The approach has proved effective and Statoil is now developing similar functionality in ArcObjects.
Mark Hoogerwerf from Netherlands-headquartered engineer Royal Haskoning DHV showed how GIS is being used across the design and build phases of the 870 km long Trans Adriatic Pipeline. GIS, alongside the engineering document management, underpins specialist tools and activities. TAP’s IT philosophy is to (mostly) configure COTS** tools and add some development. These include ESRI-based mapping tools from Conterra for security and mapping and Jira for workflow. These have been linked to documents and photos in a land workflow to calculate landowner compensation. This is no small task as the complex project spans three countries with different languages and legislations.
Exhibitor Geocento was showing its EarthImages online search engine for worldwide satellite imagery. EarthImages allows users to discover what satellite imagery is available for their area of interest from suppliers all over the world and from a vast range of sensors.
Read the presentations from the EU
PUG here.
* As low as reasonably
practicable.
** Common off-the-shelf.
© Oil IT Journal - all rights reserved.