INT has been acquired by SLB! For more information on how our flagship products will continue to develop with expanded support and integration, read here.
Learn more

INT

Empowering Visualization

COMMUNITY BLOG
CONTACT US SUPPORT

ivaap

Navigating the Deployment Challenges You May Run into with the OSDU® Data Platform: A Few Strategies for Maximizing Value

The oil and gas landscape is constantly evolving, and the Open Subsurface Data Universe (OSDU) initiative stands at the forefront of this change. Its Data Platform promises to streamline operations and unlock valuable insights, but navigating its complexities can be challenging.

Since 2018, INT has been deeply involved in the OSDU journey, deploying our E&P data visualization platform, IVAAP, at every stage of the Data Platform’s development. This experience has given us unique insights and allowed us to participate in diverse deployments across scales — from proofs of concept and pilots to full-fledged production implementations. Whether you’re on AWS, Azure, GCP, or IBM Cloud, we have the expertise to guide you through your OSDU journey.

In this blog, we’ll dive deep into the insights gleaned by our team on the challenges operators face when adopting OSDU as a standard. We’ll explore the hurdles of connecting legacy applications and data with the platform and offer practical strategies to navigate this transformation and unlock its true value.

 

INT-OSDU-diagram

 

Overcoming Ingestion Challenges

While data ingestion is essential for unlocking OSDU’s power, hidden problems often lurk beneath the surface. Our experience across various implementations reveals a recurring issue: data definition and design flaws only surface after data is already ingested. This often stems from the lack of readily available visualization tools during the ingestion stage. Essentially, ingesting data “blindly” can lead to undetected errors that later derail progress.

The key to overcoming this challenge lies in early detection and proactive correction. By integrating data visualization tools like IVAAP directly into the ingestion process, we can identify issues like incomplete data sets and incorrect metadata in real time. This shift from “ingest first, fix later” to “visualize, identify, correct” can significantly streamline the process and prevent downstream complications.

Hence, it becomes essential to have a means of visualizing and quality-checking the data as early as possible in the process when dealing with the vast number of fields in OSDU. Some parameters essential for consumption may not be explicitly required in the specifications. As a native OSDU viewer, IVAAP Data Visualization platform has been used to mitigate this risk by enabling users to perform sanity checks and validate the quality of the data throughout the ingestion process to start assessing it even during the data design phase.

Simply displaying ingested data in a web browser early on can significantly improve error detection and streamline the entire process. In simple terms, a recipe can look right on paper, but having a way to taste it before serving it to 100 guests is a safer incremental approach.

Data Mapping and Enriching the OSDU Data Model

While operators embrace the standardized data models offered by OSDU, they also require flexibility to manage their unique data needs. This is where extensions come in, allowing operators to add custom metadata and data elements essential for their specific operations, geological decisions, and analysis.

However, introducing extensions can increase the complexity of OSDU adoption. Integrating these extensions requires all applications in the data pipeline and consumption ecosystem to be not only OSDU-compliant but also adaptable to exposing these unique data elements. This applies to both the submerged “iceberg” (foundation, ingestion, enrichment, infrastructure) and the exposed “tip” (user access, consumption, and visualization). 

Our experience shows that leveraging IVAAP SDKs effectively addresses this challenge. They enable extending and enriching the OSDU data model with client-specific requirements, ultimately presenting users with “their data” tailored to their workflows.

Connecting Non-OSDU Data, Legacy Applications with OSDU-Ready Data

While the promise of OSDU is clear, migrating all applications overnight isn’t feasible for many oil and gas companies. Many crucial legacy applications might take years to be fully “OSDU-ready” — and may never be. 

The OSDU Forum is making significant strides in standardization, but it’s an ongoing process with frequent updates and not all data types are currently supported. This can create a temporary gap between those ready for OSDU and those still relying on legacy systems.

The key challenge is preventing information silos during this transition. You might have some systems offering partial OSDU-ready data while others house crucial non-OSDU data. This fragmentation can negate the benefits of OSDU.

The temptation to stay on the sidelines, waiting for a perfect transition, is understandable. However, delaying adoption can hinder your ability to leverage the transformative power of OSDU. Instead, consider proactive solutions that can bridge the gap while providing a full picture of the entire data universe of interest.

The approach here is to take the data where it is. Data in the oil and gas industry can often be spread across different databases. To bridge this gap, companies can leverage two key strategies:

  1. Native Applications: Utilize existing applications that seamlessly integrate with your legacy systems, allowing you to access and utilize their data within the OSDU environment.
  2. OSDU-Friendly Applications: Choose applications designed to work harmoniously with OSDU, enabling data aggregation and interaction between OSDU-ready and non-OSDU data.

This is, for instance, what IVAAP does with its back-end data connectors and SDK. Aggregation capabilities, pivotal to bridging the OSDU/non-OSDU gap, also enable deeper interoperability. An example of this is the integration of SLB’s DELFI platform with INT’s IVAAP, which connects applications and workflows, making them accessible to all users and enabling team members to build common workspaces for data, data models, and interpretations while respecting proprietary information boundaries and connecting them with OSDU. 

Bridging the gap between legacy applications and OSDU’s standardized data universe can be a complex challenge. Instead of forcing legacy data into a new mold, platforms like IVAAP and SLB DELFI embrace an “integrate to exist” approach. DELFI acts as a data hub, connecting these disparate databases and applications through native integrations and OSDU-friendly tools like IVAAP. This enriches the workflow with advanced visualization and data interactions, unlocking the full potential of your data universe.  

Navigating the Transition from On-Premise to Cloud

While cloud adoption is a driving force in digital transformation, not every company can make a complete jump immediately. Local regulations, connectivity limitations, and data residency requirements can create concrete roadblocks to full cloud migration and, consequently, OSDU Data Platform adoption. 

Fortunately, the Cloud Provider and ISV OSDU community are actively exploring various solutions to address these challenges and offer flexible deployment options. One such example is deploying IVAAP on IBM Red Hat OpenShift, which allows for a robust on-premise alternative to a full cloud solution. IVAAP supports on-premise deployments natively, whether for the standard or the OSDU configuration. 

Once the on-premise concerns are addressed, transitioning efficiently is crucial to avoid unnecessary costs. A hybrid solution connects both on-premise and cloud data sources and offers a flexible approach. Data aggregation and co-visualization become key components of this transition, allowing operators to harness the benefits of cloud infrastructure while maintaining their on-premise systems during the migration.

Challenges in the OSDU Business Model

Creating a healthy ecosystem of buyers and sellers within OSDU is essential for its long-term success. Increased adoption leads to deeper expertise and better utilization. To achieve this, operators must transition from proof of concept (POC) stages into production. 

Encouraging operators to invest in sharing their expertise, domain knowledge, experiences, and requirements, along with co-financing initiatives, is crucial for building a thriving OSDU ecosystem. In the same way that the energy transition cannot just rely on operators but requires the contribution of consumers and governing bodies, the OSDU transition cannot rely just on the R&D backbone of ISVs (Independent Software Vendors). 

The past four years have taught us valuable lessons about liberating data. There is plenty more to do, learn, and share amongst this very smart and dedicated community. This is an exciting time to be in this industry and shaping its future. 

From an INT perspective, one challenge we commonly encounter is that visualization is often thought of only at the end of the process. Thinking about consuming the data at the end of a very linear process represents significant risks such as poor user adoption, missed data, and delays, jeopardizing the business value of adopting OSDU. 

We have observed that the most successful projects integrate user experience, data search, and visualization early on alongside core workstreams like data infrastructure, definition, and ingestion. Each workstream even used data visualization as a core function to test the quality of their activity and maximize its success. 

Encouraging ISVs and Solution Creators

Finally, driving the participation of ISVs and solution creators in building for OSDU is vital. Operators can play a significant role by encouraging ISVs to design more open systems rather than relying on proprietary technology. This openness facilitates collaboration and accelerates the transition towards OSDU adoption.

Navigating OSDU deployments requires a strategic approach that addresses legacy systems, data mapping, and cloud migration complexities. By leveraging tools like IVAAP and fostering a collaborative spirit among operators, ISVs, and solution creators, the oil and gas industry can unlock the full value of OSDU: a more efficient and interconnected future.

Visit us online at int.com/ivaap for a preview of IVAAP or for a demo of INT’s other data visualization products. 

For more information, please visit www.int.com or contact us at intinfo@int.com.


Fundação Gorceix OSDU® Implementation: Experience, Challengers and the Road Ahead.

In our recent webinar, we had the privilege of featuring Débora Ribeiro Barretto, Geophysicist, and OSDU® Focal Point, who shared insights into their OSDU® implementation journey. Titled “Fundação Gorceix OSDU Implementation: Experience, Challenges, and the Road Ahead,” the session delved into the Foundation’s objectives, accomplishments, and the evolving role they envision within the OSDU Forum.

Fundação Gorceix: Pioneering Innovation in Brazil

Fundação Gorceix, a Brazilian institution dedicated to technology and science, operates at the forefront of mining, environment, and oil and gas sectors. The Department of Petroleum Geology, a key arm of the Foundation, is committed to evaluating Brazil’s oil potential. Managing geophysical data through the RDG (Rede de Dados Geofisicos), a sophisticated infrastructure, Fundação Gorceix optimizes communication among partner companies and operators in Brazil’s oil and gas sector.

OSDU Implementation: Transforming Workflows with AWS Cloud

Fundação Gorceix’s primary objective focuses on enhancing geophysical and geological data workflows through the OSDU Data Platform in the AWS cloud. A streamlined workflow illustrated the transition from on-premise data handling to a robust OSDU and AWS infrastructure. This transformation promises a more efficient process involving data ingestion into the OSDU Data Platform and consumption via the INT IVAAP platform.

Screenshot 2024-01-04 at 1.00.19 PM

The introduction of a virtual data room, facilitated by OSDU, emerged as a game-changer, providing global, secure access and ensuring legal and compliance entitlements. 

A glimpse of successfully ingested Brazilian data highlighted the platform’s capabilities in managing diverse datasets.

v3 FINAL INT Simplifies Machine Learning and Processing and Augments Analytics Capabilities with Latest Release of IVAAP Data Visualization Platform

For each project, some selected seismic and well data and other relevant streaming data will be available in IVAAP.

v3 FINAL INT Simplifies Machine Learning and Processing and Augments Analytics Capabilities with Latest Release of IVAAP Data Visualization Platform (2)

Example of ingested Brazilian seismic data

A Journey of Challenges and Triumphs

A candid exploration of the challenges encountered during Fundação Gorceix’s OSDU journey underscored the importance of dedicated teams and strategic focus. Issues with deployment time and operational functionality were met with resilience and a commitment to improvement. The transition to a fully dedicated team in the second semester of the first year proved pivotal, leading to a functional M11 release and the inaugural ingestion of Brazilian well and seismic data.

Screenshot 2024-01-04 at 2.05.48 PM

Shaping the Future: Automation and Collaboration

Transitioning to the forward-looking aspect of Fundação Gorceix’s OSDU journey, the organization redirected its focus to validating and enhancing seismic data ingestion in 2023. The incorporation of automation tools, engagement with other softwares, and active participation in forum groups showcased a commitment to continuous improvement. Looking ahead to 2024, the objective is to activate a virtual room with the OSDU Data Platform and IVAAP, presenting partners with seamlessly ingested data for consumption.

v3 FINAL INT Simplifies Machine Learning and Processing and Augments Analytics Capabilities with Latest Release of IVAAP Data Visualization Platform (3)

Fundação Gorceix, through its dedicated efforts and collaboration with the OSDU Forum community, partners, INT, IesBrazil, and AWS, made significant contributions to surmounting the intricate challenges of this transformative process. Their involvement included addressing time-consuming deployment, preparing Brazilian seismic data, navigating diverse coordinate reference systems, and overcoming the obstacles a lean, non-multidisciplinary team posed. 

Collaborative Success: A Call to Contribute

The presentation wrapped up with a compelling message — The OSDU Forum is not designed solely for its members; rather, it is formed collaboratively by the engaged participants within the community. The call for engagement and collaboration resonated profoundly, emphasizing the importance of collective contribution. Fundação Gorceix eagerly anticipates operating the OSDU virtual data room in the near future, reciprocating the support received by contributing to the community.

In embracing the journey of Fundação Gorceix, it becomes evident that challenges are inherent to innovation. With teamwork, resilience, and a collaborative spirit, shared success becomes an achievable and rewarding endeavor. The OSDU Data Platform stands as a testament to the strength derived from collaborative efforts to establish a platform for shared knowledge and mutual support.

Watch the on-demand webinar here to dive deeper into Fundação Gorceix’s OSDU journey.

Visit us online at int.com/ivaap for a preview of IVAAP or for a demo of INT’s other data visualization products. 

For more information, please visit www.int.com or contact us at intinfo@int.com.

____________

ABOUT INT

INT software empowers energy companies to visualize their complex data (geoscience, well, surface reservoir, equipment in 2D/3D). INT offers a visualization platform (IVAAP) and libraries (GeoToolkit) that developers can use with their data ecosystem to deliver subsurface solutions (Exploration, Drilling, Production). INT’s powerful HTML5/JavaScript technology can be used for data aggregation, API services, and high-performance visualization of G&G and energy data in a browser. INT simplifies complex subsurface data visualization.

INT, the INT logo, and IVAAP are trademarks of Interactive Network Technologies, Inc., in the United States and/or other countries.






INT Achieves SOC 2 Compliance

HOUSTON, TX – INT, a leader in data visualization software for the Energy industry, is proud to announce a significant milestone in its commitment to data security and customer trust. We have achieved SOC 2 compliance, underscoring our unwavering dedication to safeguarding your data and upholding the highest standards in information security.

What is SOC 2 Compliance?

SOC 2 (System and Organization Controls 2) compliance is an internationally recognized standard that assesses an organization’s ability to securely manage customer data. Achieving SOC 2 compliance means that INT has undergone rigorous third-party audits to validate our adherence to strict security controls and practices.

Why SOC 2 Compliance Matters

At INT, we understand that data is one of your most valuable assets. SOC 2 compliance assures you that we have implemented robust measures to protect your sensitive information from unauthorized access, data breaches, and other security threats. Your data’s confidentiality, integrity, and availability are our top priorities.

Our Commitment to Data Security

Our journey to SOC 2 compliance involved comprehensive assessments of our security practices across key areas, including security, availability, processing integrity, confidentiality, and privacy. These assessments have allowed us to identify and address potential vulnerabilities, ensuring that your data remains in safe hands.

Third-Party Validation

To earn our SOC 2 compliance certification, we enlisted the services of The Johanson Group, a renowned third-party auditing firm to thoroughly assess our security controls and practices. This independent validation demonstrates our unwavering commitment to transparency and accountability in data security.

What SOC 2 Compliance Means for You

By choosing INT, you gain a trusted partner that not only values your data but also takes concrete steps to protect it. Our SOC 2 compliance reflects our dedication to earning your trust and providing you with a secure environment for your data.

For more information about our SOC 2 compliance or to access our SOC 2 documentation, please visit our dedicated compliance/security page at int.com/security. If you have any questions or require further information, please contact us at int.com/contact-us/.

5 Key Designs of the IVAAP Backends

When you are getting ready to embark on a multi-year journey of software development, technical design matters. You don’t just want to take into account the requirements of a minimum viable product, you have a roadmap for this product, and this roadmap gives you constraints. Over the years, a product evolves and so do the constraints. With the 2.11 release of IVAAP, now is a good time to revisit early technical design decisions for the IVAAP backends, decisions that have stood the test of time over the entire lifecycle of the product.

1. Designed to Mesh Data

IVAAP has very strong visualization features. Some customers use IVAAP only to visualize data from their PPDM database, or from their OSDU deployment. Many others use IVAAP to visualize data coming from multiple data sources. This “multiple data sources” aspect of IVAAP has been part of the DNA of the product from the start. It gives users the ability to compare data across multiple systems, in one deployment, and in one consistent user interface. 

Technically, this feature imposes architectural constraints. First, from a reliability standpoint, when you access multiple data sources at the same time, you can’t assume all of them are available. And the failure of one data source shouldn’t affect access to data from another source. For example, if a PPDM database goes down, this shouldn’t affect access to WITSML data. This is one of the reasons why IVAAP has been designed as a “mesh” of multiple Java Virtual Machines. Even in the most basic deployment, each data source type (PPDM, WITSML, OSDU, etc) has its own dedicated sandbox, and it’s the role of the IVAAP cluster to make these sandboxes cooperate to give users a seamless experience.

Sandboxing access to each data source type also provides a simple way to scale. Whether the components of IVAAP are deployed with Kubernetes or with Docker Compose, you can customize at deployment time how each data source type scales. 

The ability to access multiple data sources also permeates the way URLs are designed. The URLs of the IVAAP Data Backend are designed so that the cluster can easily route HTTP requests towards the right component. This routing doesn’t just affect the URL of REST services, but also the URL of real-time channels used in web sockets. These “mesh-friendly” URLs have stayed stable since the first version of IVAAP.

2. Container Agnostic

An architecture where multiple JVMs run in parallel is complex to deploy as a developer. 99% of the development time is spent on developing or modifying a service meant to execute within a single JVM. As a platform, IVAAP needed to be powerful, but also easy to use for the most common tasks. This is why it was designed to run on top of multiple containers.

The container used in production is made of a Play server and an Akka cluster. Each data source type is associated with a so-called “node” that is part of that cluster. The container used in development is an Apache Tomcat server, running Java Servlets. This is a configuration that most developers are already familiar with, and that IDEs support well. 

From a code point of view, it makes no difference whether a service will be deployed in Tomcat or in Play. But being “container agnostic” goes beyond the benefits of seamlessly switching between development and runtime environments. The services written with the IVAAP Backend SDK may also be deployed on containers such as Amazon Beanstalk or Google App Engine. JUnit itself is considered a container, making it easy to unit test REST services without having to launch a HTTP server.

Introduced later, the Admin Backend benefited from the SDK’s versatility. While this SDK was initially designed with an Akka Cluster in mind, it is also used by the Admin Backend running Apache Tomcat.

IVAAP is a feature-rich platform, with hundreds of REST services. One of the reasons INT was able to implement so many services is the versatility of IVAAP’s SDK. Making abstraction of the underlying runtime environment was an early SDK decision, key to making IVAAP developers instantly productive.

3. Modular

When you develop microservices, there is one keyword that is the antithesis of the type of product you are creating: a monolithic application. To borrow from Wikipedia, “a monolithic application is a single unified software application which is self-contained and independent from other applications, but typically lacks flexibility.” A monolithic application is often used along proprietary data silos. From an architecture point of view, IVAAP is the opposite of a monolithic application — it attempts to free users from the proprietary data silos by providing the flexibility that silos lack. This is where a modular architecture helps.

With a modular architecture, optionalism is not limited to configuration, but also depends on the presence or absence of a module. From a development perspective, it is sometimes easier to develop and test a module that implements an option than to modify (and risk breaking) an already well-tested existing code.

Modularity is particularly useful when 99% of the product fits a customer needs, but the remaining 1% needs to be customized. With a modular architecture, the IVAAP code doesn’t need to be changed to implement a proprietary authentication mechanism. A custom authentication module can be deployed instead.

The benefits of modularity were well understood before INT started working on IVAAP. It’s really how it was implemented that turned out to have staying power. The IVAAP Backend SDK used a simple Lookup system to let developers plug or unplug implementations. This Lookup system was actually the first line of code I wrote when I started working on IVAAP. In a nutshell, a single annotation governs how classes are registered into the lookup at startup. It’s an API that is incredibly powerful, but also simple to learn. The entire IVAAP Backend code was built around it.

4. Developer-Friendly Data Models

IVAAP supports multiple types of data sources. Many of these data sources contain well data, but they all have their own way of storing that data. The role of a connector’s implementation is to expose this data to the rest of IVAAP, using a standard data API.

A typical way to do this is to use the concept of “Data Access Object.” To quote Wikipedia again, “a data access object (DAO) is a pattern that provides an abstract interface to some type of database or other persistence mechanism.” The IVAAP SDK follows this DAO concept, but while keeping developers in mind. 

A typical DAO implementation indicates which interfaces need to be implemented. A developer working on a connector would code towards these interfaces, then start testing the code. This approach has several problems. One of them is that a developer cannot start testing his/her work until all interfaces have been implemented. The second problem is that there may be lots of interfaces to implement, delaying further the availability of the work.

IVAAP’s DAO approach introduces the concept of “finders” and “updaters.” Finders are in charge of performing “read-only” data accesses, while “updaters” are in charge of updating this data if needed. Finders and updaters are added to the lookup at startup. Unlike a classic DAO implementation, developers only need to plug finders and updaters that will be actually used, that actually match data in the data source they are working with. 

For example, a WITSML store may contain “well risk” data and INT’s WITSML connector implements a “well risk finder.” A PPDM database doesn’t contain “well risk” data and INT’s PPDM connector doesn’t need to implement a “well risk finder.” By splitting the code requirements into fine-grained finders and updaters, the IVAAP SDK implements a DAO system that requires only the minimum amount of code for developers to write.

Paired with well-defined data models, the now battle-tested concept of finders and updaters has been a key element for new developers to learn the IVAAP SDK and develop connectors fast.

5. Circle of Trust

Going back to the idea of a “monolith,” one of the pitfalls of building a monolith is that a monolithic application can often only talk to itself. Since IVAAP is based on microservices, it is, by design, a system that is easy to integrate with. There is however a constant hurdle to such integration: authentication and security.

When authentication is simple, many systems use the concept of a “service account” to consume microservices. But “service accounts” often break when multi-factor authentication is required. When integration with other systems is a concern, we found that microservices need to be able to clearly differentiate human interaction from automated interactions.

This is essentially the purpose of the Circle of Trust. When deploying IVAAP, the software components that require special access can authenticate themselves as such. For example, a Python or Shell script that scoops up the monthly activity report would identify itself as a member of the Circle of Trust to access this report.

As IVAAP matures, many of the solutions proposed today by INT to its customers involve the Circle of Trust. The Circle of Trust is a simple but secure way of integrating third-party software with IVAAP. While it is a recent introduction to IVAAP’s design, it has become a key tool to meet customer needs.

 

Conclusion

The designs above made IVAAP’s journey possible, but IVAAP’s journey is not over. What they all share is a focus on users. Whether these users are geoscientists or programmers, these designs were meant to empower them. Empowering doesn’t just mean catering to today’s needs — it also means anticipating tomorrow’s requirements and making them possible. These five designs were strong enough that they were the gifts that kept on giving.

Visit us online at int.com/ivaap for a preview of IVAAP or for a demo of INT’s other data visualization products. 

For more information, please visit www.int.com or contact us at intinfo@int.com.


INT Simplifies Machine Learning and Processing and Augments Analytics Capabilities with Latest Release of IVAAP Data Visualization Platform

The latest release of IVAAP by INT introduces an array of exciting new features and enhancements, providing users with unparalleled capabilities to extract deeper insights from their subsurface data.

Houston, TX — August 10, 2023 — INT announced today the launch of IVAAP™ 2.11, the latest version of our Universal Cloud Data Visualization Platform. With powerful features and enhanced capabilities, IVAAP™ 2.11 takes subsurface data exploration and visualization to new heights, empowering users to make critical decisions with confidence and efficiency.

Some of the key highlights include: 

  1. External Workflows to Support Machine Learning and Data Processing: With IVAAP™ 2.11, users can now seamlessly integrate external processing workflows and ML capabilities, unlocking the true potential of their data through advanced analytics and data automation.
  2. Unit System Management: IVAAP™ introduces Unit System Management, offering users enhanced control over data consistency and clarity by efficiently managing unit conversions.
  3. WellLog Enhancements: WellLog module sees significant improvements, including support for stacked patterns curve, curve editing, lithology editing, and discrete raster files.
  4. Dynamic Range Intervals: Selected depth intervals can be highlighted in multiple widgets like cross-plot, pie charts, histograms, and more. Moving intervals along the depth are reflected automatically across all widgets.
  5. OSDU™ Data Platform Compatibility: IVAAP now offers full support for perforation intervals, stratigraphic columns, well-core images, hole sections, and collections on the OSDU Data Platform. Additionally, KPIs are now available on the IVAAP Home page.

“IVAAP 2.11 represents a significant milestone in our journey towards providing the oil and gas industry with the most advanced and comprehensive data visualization platform. With the introduction of external workflow support for machine learning and data processing and full compatibility with the OSDU Data Platform, IVAAP continues to empower geoscientists and engineers to explore, visualize, and automate their data like never before,” said Hugues Thevoux, VP of Cloud Solutions at INT. “This release underscores our commitment to delivering cutting-edge solutions that drive efficiency, foster innovation, and enable our clients to make smarter decisions with confidence.”

IVAAP 2.11 is now available for all existing users. To experience the power of IVAAP or to schedule a personalized demo, visit int.com/demo-gallery/ivaap/ or contact our sales team at intinfo@int.com.

To learn more about IVAAP 2.11, please visit int.com/products/ivaap/ or contact us at intinfo@int.com.

Read the IVAAP 2.11 Release Notes.
Read the press release on PRWeb.

____________

ABOUT IVAAP:

IVAAP™ is a Universal Cloud Data Visualization Platform where users can explore domain data, visualize 2D/3D G&G data (wells, seismic, horizons, surface), and perform data automation by integrating with external processing workflows and ML.

ABOUT INT:

INT software empowers the largest energy and services companies in the world to visualize their complex subsurface data (seismic, well log, reservoir, and schematics in 2D/3D). INT offers a visualization platform (IVAAP) and libraries (GeoToolkit) developers can use with their data ecosystem to deliver subsurface solutions (Exploration, Drilling, Production). INT’s powerful HTML5/JavaScript technology can be used for data aggregation, API services, and high-performance visualization of G&G and petrophysical data in a browser. INT simplifies complex subsurface data visualization.

For more information about IVAAP or INT’s other data visualization products, please visit https://www.int.com.

INT, the INT logo, and GeoToolkit are trademarks of Interactive Network Technologies, Inc., in the United States and/or other countries.