The system requirements are provided as general guidelines. Hardware requirements will vary considerably, depending on the types of projects, project sizes, the number of users, and network infrastructure/traffic. Contact your technical sales representative or technical support to discuss your requirements.
- Geologic Suite (DataManager, GeoAtlas, Geology and Petrophysics)
- Geophysical Suite (Geophysics, LogM, pStaX, and SCAN)
- New users or users upgrading from other versions of GeoGraphix also need valid licenses. Refer to the GVERSE GeoGraphix License page to request new license. For information on license requirements for GVERSE applications, refer to their respective release notes and installation documents on the GVERSE GeoGraphix Support Portal > Knowledge Center > Release Notes and Installation Guides page.
- The License Management Tool (LMT) must be installed to configure the license. Download the latest LMT from the GVERSE GeoGraphix Downloads page. See the Licensing section of the Installation Guide for more information.
- Discovery on OpenWorks is compatible with OpenWorks for Windows 5000.10.6.03 and SeisWorks 5000.10.
- Windows® 7 Professional x64
- Windows® 7 Enterprise x64
- Windows® 7 Ultimate x64
- Windows® 10 Professional x64
- Windows® 10 Enterprise x64
- 8 GB Minimum
- 16+ GB recommended
- Core i5 Minimum
- Core i7 Quad-core and above (Recommended)
Note 1 – GVERSE® Geophysics and GVERSE® Geomodeling specifically require Windows platform update package KB2670838 installed on the machine, in case the operating system is Windows 7.
Additional System Requirements for GVERSE Modules
- 2.4 GHz 64-bit processor
- 8 GB RAM
- 1366 x 768 screen resolution
- Hard Disk Drive
- 1 GB VRAM (Nvidia® GeForce GTX 430 comparable)
- DirectX 11.1 capable hardware (see note 2)
- Quad 3.2 GHz 64-bit processor
- 32 GB RAM
- 1920 x 1080 screen resolution
- Solid state hard disk
- 6 GB VRAM (Nvidia® GeForce GTX 1060 comparable)
- DirectX 11.1 capable hardware (see note 2)
Note 1 – Microsoft DirectX End-User Runtime (June 2010) is required to run Discovery 3D, advanced 3D visualization (Pro 3D), GVERSE® Geomodeling and GVERSE® Geophysics.
Note 2 – To run Discovery 3D, advanced 3D visualization (Pro 3D), and GVERSE® Geomodeling, it is recommended that any DirectX 11.1 is used. DirectX is not shipped with GeoGraphix. You must download and install it separately. We recommend using the latest video drivers and Microsoft updates for your system.
Note 3 – GVERSE® Geophysics and GVERSE® Geomodeling specifically require Windows platform update package KB2670838 installed on the machine, in case the operating system is Windows 7.
Note 4– Microsoft® .NET Framework 3.5 and 4.7.2 are required
- Geologic Suite (DataManager, GeoAtlas, Geology and Petrophysics)
- Geophysical Suite (Geophysics, logM, pStaX, and SCAN )
- Windows® Server 2012 R2 Standard x64
- Windows® Server 2016 R2 Standard x64
- 32 GB Minimum
- 64+ GB recommended
- SSD Drives Recommended
- Intel Xeon Processor or Equivalent
- Quad 2.4GHz 64-bit or better
Note: We recommend using the latest Microsoft service packs and security patches.
Server performance is subject to a large number of variables. It is impossible to give specific recommendations here, but these are some guiding principles to use. In general, multi-user performance of a GeoGraphix Project Server is best when the server is dedicated to GeoGraphix and not shared with other applications, especially database applications. In addition, consideration should be made for the number of GeoGraphix users and the size and number of concurrently accessed projects. At some point, having multiple project servers becomes a better solution than having all users on one server. Generally, somewhere between 10 and 20 users is when a second server might be suggested.
Network performance depends on the number of users trying to access a server simultaneously, as well as the bandwidth requirements for those users. Recommendations for server bandwidth typically specify server connectivity at a higher bandwidth than an individual user. For instance, users running at 100 Mbit should be accessing a server running on a 1-Gbit backbone. If users are at 1 Gbit, consider running multiple 1-Gbit connections or a single higher-bandwidth connection on the server.
A large database cache is an important factor to consider when dealing with multiple users accessing large databases. The database engine is capable of addressing a practically unlimited amount of cache memory. The best way to size the memory is to estimate the memory requirements for other running applications and allow the database cache to dynamically allocate any remaining free memory. The engine will only allocate what it needs when using dynamic allocation up to the maximum specified. It is highly recommended that you let the database engine use as much cache memory as it requires on the host server. Increasing database cache memory is the quickest and most effective way to improve database-related performance on large network projects. On a workstation, it might be appropriate to reserve 1 to 2 GB for the OS and file system cache and 2 to 4 GB for other running applications. On a dedicated project server, not much memory needs to be reserved for other applications. The ideal maximum varies by the project size, the number of users, and other load considerations. But as a general rule, the higher you can set the maximum, the better.
A great deal of GeoGraphix access patterns on a server deal with file I/O. Database access, raster images, and seismic data are examples of files that benefit substantially from a fast disk sub-system. Server environments also place a high importance on data integrity and reliability. At a minimum, consider using a RAID 5 (striped with parity) array. As the size of disks increases, you may also want to consider a hot swap drive and/or RAID 6 (striped with dual parity). Using a controller card with its own cache can also help improve performance.
Network Attached Storage (NAS), Storage Area Networks (SAN), and Other Non-Windows Storage Solutions
There are two typical methods used for accessing external storage devices from a project server: iSCSI and CIFS.
- iSCSI allocates a block of storage on the external device and makes it appear to be a physical disk on the project server. This has the advantage of a 100% compliant file system. However, since the external device sees the allocation as one big file, it makes backup and restoration of individual files using the external device's capabilities more difficult. Standard backup and restore procedures from the server will still work.
- Using CIFS for external storage devices depends greatly on the vendor’s implementation of the CIFS protocol used by the Windows platform. In general, a 100% compliant implementation of CIFS for a performant system is required. In particular, the vendor's implementation of the "File Change/Notify" functionality has been problematic. Devices based on the Windows Storage Server should be 100% compatible, since it shares its components with Windows. Implementations based on UNIX/Linux are where problems occur, due to the fact that the kernel level support is not present. Due to these uncertainties with CIFS implementations, GeoGraphix does not technically support CIFS.
This release has several prerequisites that are required to run the software, as well as prerequisites that are used to enhance the software. The prerequisites can be downloaded from the GVERSE GeoGraphix Downloads page.
Microsoft .NET Framework 3.5
This is specifically required if you are using smartSECTION on a Microsoft Windows® 10 operating system. The Microsoft .NET 3.5 can be downloaded from Microsoft's website and then installed. It is also available in the 3rd Party installers shipped with GeoGraphix.
Microsoft .NET Framework 4.7.2
GeoGraphix must have Microsoft's .NET 4.7.2 installed. The Microsoft .NET 4.7.2 can be downloaded from Microsoft's website, and then installed. It is also available in the 3rd Party installer shipped with GeoGraphix.
MATLAB Runtime R2018a (9.4)
GVERSE® Field Planner requires MATLAB Runtime R2018a (9.4). The MATLAB Runtime R2018a (9.4) software can be downloaded from MATLAB's website and then installed. It is also available in the Downloads section of the GVERSE GeoGraphix website.
ESRI ArcGIS Runtime Engine
Functionality within GeoAtlas related to geo-referenced images and CAD files requires the ESRI ArcGIS 10 Engine with ESRIArcGIS 10.2.x through 10.8.x. ESRI ArcGIS license must be configured by running ArcGIS Administrator with administrative rights, and selecting the ArcGIS Engine Runtime (Single Use) option in the wizard. If the ArcGIS Engine is not installed, a message box will appear but the setup will continue.
The ArcGISConfigurationTool.exe utility is provided in Utilities shipped with GeoGraphix. IT Support teams can program and run this utility to remotely configure GeoGraphix on network machine(s) that have ArcGIS Runtime installed. For details, refer to the Utilities documentation.
ESRI ArcGIS Engine 10.6.1 Patch Installation
If ESRI ArcGIS Engine 10.6.1 is installed on the machine, you must also install the ESRI ArcGIS Engine patch (ArcGIS-1061-E-BDP-Patch.msp) to ensure smooth execution of various Field Planner and GeoAtlas workflows. The patch can be downloaded from the ESRI website here
Microsoft DirectX 11 End-User Runtimes
Discovery 3D, Pro3D, smartSECTION, GVERSE® Geophysics and GVERSE® Geomodeling require Microsoft's DirectX 11 June 2010 End-User Runtimes to work properly. The Discovery 3D application works only on the Windows 7 (64-bit) or higher operating system. Discovery 3D is not installed unless the computer has Windows 7 (64-bit) or higher. Further Discovery 3D requires a DirectX 11 compatible display card. DirectX 11 June 2010 End-User Runtimes can be installed by downloading the GeoGraphix Third Party Installer.
Microsoft Internet Explorer 10 or 11
Microsoft Internet Explorer 10 or 11 must be installed in order to launch GVERSE® NOW.
Optional Software Requirements
|License Management Tool (LMT)||LMT must be installed to configure the license. Download the latest LMT from the GVERSE GeoGraphix Downloads page.|
|Spreadsheet Import Utility in WellBase, SeisBase, and LeaseMap||Excel 2007, 2010, 2013, 2016 or 2019 (32 or 64 bit), including office 365 (offline version). In case the macros are not working in Excel, ensure the gxdb.xla file is present in the relevant Microsoft Office Library installation folder.|
|Selected Help files||Adobe Reader|
|For Discovery on OpenWorks, GridXchange, and SeisXchange||OpenWorks for Windows 5000.10.6.03 – Basic or Full (recommended) Install available on Landmark’s LSM. (See Notes below), and SeisWorks 5000.10 (for seismic workflows)|
|ESRI geo-referenced images and ESRI CAD file import in GeoAtlas||ESRI ArcGIS Runtime Engine 10.2.x or 10.3.x or 10.4.x or 10.5.x or 10.6.x 0r 10.7.x or 10.8.x (included in the 3rd Party Installer).|
|For LOGarc™ Version 220.127.116.11 access in smartSECTION||To use the LOGarc™ feature, the LOGarc™ Version 18.104.22.168 software must be downloaded from IHS LogTech Canada, LTD and a valid account must be in place. You must have administrator rights to the computer on which you will load the software.|
|GeoGraphix Plug-in for TIBCO® Spotfire® Analyst||Spotfire Version 10.6, 10.8, 10.10 must be installed.|
|For GVERSE NOW||Internet Explorer 10 or 11 must be installed.|
Notes for Discovery on OpenWorks - The OpenWorks Full installation requires Hummingbird Exceed. The Oracle client installation in use with the OpenWorks Full installation requires that the “Administrator” option be selected. The “Administrator” option type includes the SQL Plus and the Oracle Database Utilities components, which are needed to run Discovery on OpenWorks, as part of the total OpenWorks package.
Note - Hummingbird Exceed is not required for the OpenWorks Basic installation. If the OpenWorks Basic installation is used, the Oracle client installation can use the “Administrator” option, which will include all of the needed components. Or, the Oracle client installation for the OpenWorks Basic installation can use the “Custom” installation type. However, with the Custom installation type, the following components must be installed:
- Oracle Database Utilities 22.214.171.124
- SQL *Plus 126.96.36.199
- Oracle JDBC/THIN Interfaces 188.8.131.52
- Oracle Net 184.108.40.206
The SQLLoader.exe error may generate when working with Filters in GeoGraphix due to a missing Oracle DLL file. This is a known issue of Oracle 220.127.116.11 where oranfsodm12.dll is not shipped with the installer.
Workaround: After Oracle installation, create a copy of the oraodm12.dll file, rename it as oranfsodm12.dll, and then place the renamed file in the BIN folder of both 32-bit and 64-bit Oracle installations