Recently, INT announced our partnership with Bluware and our integration of Bluware’s OpenVDS format into IVAAP, our enterprise data visualization platform. We are very excited about this partnership, as well as our collaboration with OSDU. This new format was designed to empower users to browse seismic data in the cloud with high performance and lower cost.
Interactive Network Technologies, Inc. (INT) a leader in advanced domain visualization in digital exploration and production (E&P) and Bluware Corp., the digital platform that enables the oil and gas industry to accelerate digital transformation initiatives and adopt cloud computing for subsurface data, are pleased to announce the integration of Volume Data Store (VDS), a data format with adaptive streaming technology for seismic data storage, into IVAAP, an upstream data visualization platform.
When doing demos of IVAAP, the wow factor is undeniably its user interface, built on top of GeoToolkit.JS. What users of IVAAP typically don’t see is the part accessing the data itself, the IVAAP backend. When we designed the IVAAP backend, we wanted our own customers to be able to extend its functionalities
INT is pleased to announce the latest release of its enterprise upstream visualization platform, IVAAP™ 2.5.
This version includes new production dashboards to enhance analysis and monitoring. Support for curve dictionaries and aliases makes it easier to build powerful log templates. IVAAP now fully supports the display of raster logs in well and correlation views (with support for TGS SmartRASTER® format).
As a non-developer living in a developer world, I wanted to understand more about why we develop our software to work with Kubernetes. So I sat down with INT’s Senior Product Manager Steven Reynolds and Senior Architect James Velasco to learn more about Kubernetes and the advantages of working with it.
Bluware Corp., the digital innovation platform for seismic data, is pleased to announce a strategic partnership with Interactive Network Technologies, Inc. (INT), a leader in multi-domain visualization in exploration and production (E&P). Bluware and INT are early members in the Open Subsurface Data Universe (OSDU), a forum focused on developing a standard that creates a common data platform for all exploration, development, and well data. The standard will transform the way subsurface data is captured, analyzed, and operated.
Programming is an activity that requires a special set of cognitive skills. While the industry has developed processes and tools to ensure the quality of software artifacts, the act of writing code is a craft in itself. Developers pride themselves on the “big picture” results they achieve, but the activity of programming is definitely a humbling experience: it’s easy to introduce bugs, and regardless of whether I catch them right away or later in the pipeline, I hate to be reminded I am inherently flawed and have introduced a defect. For this article, I will focus on simple methods to avoid bugs, not before or after you write code, but while you write that code.
One of the unique features of the IVAAP backend SDK is that you can develop your own data connectors and services with the IDE you are already familiar with. The data backbone of IVAAP is meant to be deployed in a cluster made of multiple nodes for scalability and reliability. However, despite the distributed nature of such a deployment, our SDK requires no particular plugin to compile or execute your code. The tools needed to develop a plugin for IVAAP’s backend are identical to the tools you would need to develop classic Java Servlets: a Java SDK (Oracle, OpenJDK), an IDE (Eclipse, NetBeans) and an application server (Tomcat, Glassfish).
Over the last few months, there have been a lot of activities and discussions with upstream majors on how to make subsurface data easier to search and discover and how to automate some of the geophysical and/or petrophysical workflows. This process has typically been very challenging. From a user experience perspective, the ideal scenario would be to do this from one system versus doing this very manually from current siloed applications. We’ve been able to do this successfully here at INT.
It’s been two years since Oracle announced the donation of the NetBeans source code to the Apache software foundation. This move was much more than a licensing change — it was a bit of a new beginning for NetBeans. With the release of NetBeans 10, now is a good time to look back and recognize the changes that this transition to Apache brought.
The purpose of IVAAP’s backend is to access data from many data sources and present this data in a unified manner to the IVAAP HTML5 client. Performance is key, and some data stores are faster to access than others. In a web service configuration, a smart caching strategy is required so that the same web/HTTP calls are not made to the same data store twice while a service request is being fulfilled, regardless of its complexity. This is where the concept of scope comes in.
As a new member of the software development team, I had no prior experience with development on IVAAP, INT’s HTML5 visualization framework for upstream E&P solutions. My first task was to add a data connector, so to gain knowledge of IVAAP and to understand more about the IVAAP software development kit, I used the IVAAP developer’s guide. I found this guide quite useful as it made the key points behind IVAAP easily understandable. Coding with IVAAP is actually easy, and I was surprised by several features of the platform and SDK that make it quite simple to learn.
With the explosion of storage capacity, cloud computing, and bandwidth availability, a trend has emerged in the oil and gas industry over the last few years. Data that was previously aggregated and discarded is now maintained and stored, creating an opportunity for the industry. Coupled with new advancements in machine learning and Al, this data availability is poised to drive more data driven decision making in well planning, drilling & completions, and well operations.