IVAAP was not just meant to be a web application “built for purpose”—we wanted it to be a platform that customers can extend on their own. With this goal is mind, the first component that we picked for IVAAP’s architecture was a “lookup” system. This system makes IVAAP easy to learn, yet versatile, and devops appreciate that they can leverage it when a fast turnaround is needed.
Traditionally, the oil and gas sector has been slower than other industries to adopt new software and technology. When the market is doing well, companies have little time or motivation to invest in change. When the market is bad, companies lack the appropriate resources and budget. Since 2015, the oil and gas sector has experienced significant changes. An aging workforce, low oil market price, and the pressure to transition to cleaner energy are among the many factors forcing the Exploration and Production industry to rethink how it works, recruits, trains, and operates in order to stay in business.
Storing and accessing large, sometimes sensitive geoscience data is one challenge many top E&P companies face. Local data storage is one option. But what about data that is not stored locally? How do you access it quickly, and can you still use INTViewer?
In our latest Tech Talk, E&P Visualization in the Cloud, we featured IVAAP, our cloud-enabled visualization and analytics development platform. We showed how it can be used to monitor and analyze well data as a critical part of your digital transformation. Thierry Danard, our VP of Core Platform Technologies, presented some of the technical aspects of IVAAP, so we asked him a few questions after the talk to dig a bit deeper.
A major feature of INTViewer 5.2 is the Python integration. Our development team worked very hard to ensure that our customers can get started easily and be productive once they are hooked. One consistent user feedback was that the Python terminal lacked autocompletion. It could become tedious to have to type the full name of each class, each method or each variable. We took this feedback to heart and implemented autocompletion in INTViewer 5.2.