System Requirements

  • Home
  • System Requirements

Confirm compatibility before installation

GAEA Software System Requirements

Use this page to plan workstations, field devices, network licensing, storage and supporting software. Requirements vary by product, version, license type, data volume and workflow; confirm the intended configuration before procurement or production deployment.

Start with the Correct Platform

Separate current desktop, network and field requirements before evaluating hardware.

Desktop applications

Managed Windows Computer

Current GAEA desktop applications are designed for Windows environments. Use a currently supported 64-bit Windows release that has been confirmed for the specific product version.

Network licensing

Reachable Windows Host

Network deployments require a persistent host for the applicable license service, reliable name or IP resolution, and approved client-to-server connectivity.

Field application

Compatible Android Device

WinLoG Field Assistant is designed for Android. GAEA recommends at least 8 GB of device memory and a 1080p display for optimal clarity.

Legacy compatibility is not a current requirement

Older GAEA versions may run through Windows compatibility features, but that does not establish support for a new deployment. Use the current product version and confirm its operating-system compatibility.

Recommended Desktop Evaluation Baseline

This is a practical starting point for evaluating current GAEA desktop products, not a substitute for version-specific confirmation.

ComponentRecommended evaluation baselineWhen to increase or investigate
Operating systemCurrent, supported 64-bit Windows release approved for the product versionLegacy versions, controlled desktop images, virtualization or delayed Windows servicing
ProcessorModern multi-core x64 processorLarge imports, complex reports, modeling, gridding, cross-sections or 3D visualization
Memory16 GB RAM for a typical professional workstationUse 32 GB or more when representative projects show sustained memory pressure
StorageSSD with capacity for applications, active projects, temporary files and local working spaceLarge databases, core photographs, attachments, imagery, exports or offline project copies
Display1920 × 1080 or higher at a readable Windows scaling settingComplex template design, dashboards, multi-panel analysis, CAD-style editing or multiple monitors
GraphicsCurrent Windows-compatible graphics hardware and driver3D visualization, large imagery, remote sessions or display-driver instability
NetworkStable, low-latency access to required license, database and datastore resourcesVPN, Wi-Fi, remote offices, hosted environments or large shared files
PermissionsAuthorized administrator access for installation, plus appropriate user access for operationApplication control, endpoint protection, protected folders or nonpersistent desktops

Why this baseline is intentionally conservative

Project size and workflow have more influence on performance than the installer alone. A small standalone logging project and a shared database containing imagery, analytical results and 3D content should not be sized identically. Test a representative project before standardizing hardware.

Product-Specific Considerations

Use the common desktop baseline together with the dependencies relevant to each product.

GaeaSynergy Modules

WinLoG, WinFence, EDMS and GDMS may use connected project, database and datastore resources within GaeaSynergy deployments.

  • Windows client environment
  • Database and datastore capacity
  • Shared-path permissions where configured
  • Network license connectivity where applicable

WinLoG & WinFence

Logging, template design and section editing benefit from a full-HD or larger display. Size memory and storage for the number of logs, photographs, curves and section content.

  • Readable display scaling
  • Printer and PDF workflow testing
  • Image and curve-data capacity
  • Representative template testing

EDMS & GDMS

Environmental and geotechnical data-management performance depends on database size, concurrent activity, imports, calculations, documents and reporting.

  • Database capacity and maintenance
  • Reliable shared-data access
  • Import and report performance
  • Backup and restoration testing

POLLUTE & MIGRATE

Model runtime depends on the selected analysis, discretization, sensitivity work and output. Validate expected cases on the proposed workstation.

  • Modern multi-core processor
  • Sufficient memory for intended models
  • SSD working space
  • Representative runtime benchmark

E-ASR

E-ASR uses report templates prepared in Microsoft Word and generates reviewable Word documents. Confirm a compatible, licensed desktop Microsoft Word installation for template and report workflows.

  • Windows desktop environment
  • Microsoft Word workflow
  • Template fonts and styles
  • Document output location and permissions

WinLoG Field Assistant

For the Android field application, GAEA recommends a device with at least 8 GB of memory and a 1080p display. Field trials should also evaluate battery life, storage, camera use and outdoor readability.

  • Compatible Android device
  • At least 8 GB device memory
  • 1080p display
  • Field synchronization testing

Network License Requirements

The documented GaeaSynergy network workflow uses a Network License Service on a reachable Windows host. Client workstations require the server name or IP address and access to TCP port 3000.

  • Persistent and monitored Windows host
  • TCP port 3000 allowed only within approved scopes
  • Reliable DNS or fixed addressing strategy
  • Client-to-server route and firewall approval
  • License service restart and recovery ownership
  • Concurrent-license testing with intended users

Read the network port guide →

Hosted and Virtual Environments

Windows virtual machines, Cloud PCs and remote-desktop deployments may be possible, but suitability depends on licensing, persistence, graphics, latency, database access, printing and storage paths.

Pilot the actual application, license type, data and peripheral workflow. Do not approve a nonpersistent or autoscaling design until registration, license-service and data behavior have been verified.

Storage, Database and Backup Planning

The software installation is only one part of the capacity requirement.

Application Files

Allow working space for installation, updates, temporary files and diagnostic material.

Structured Data

Size databases for projects, logs, samples, test results, monitoring records and expected growth.

Datastore Content

Account for photographs, documents, imagery, attachments, templates, exports and intermediate files.

Recovery Copies

Provide separate backup capacity and test restoration of databases, datastores and configuration.

A free-space figure is not a storage plan

Capacity should include expected data growth, temporary processing space, exports, retention, backups and restoration staging. Core photography and other high-resolution attachments can exceed the application footprint by orders of magnitude.

Pre-Installation Compatibility Checklist

Complete these checks before deploying to production users.

Workstation and Software

  • Product, version and license type confirmed
  • Windows release and architecture confirmed
  • Processor, memory, SSD space and display reviewed
  • Current graphics, printer and peripheral drivers installed
  • Microsoft Word available where E-ASR requires it
  • Administrator-assisted installation scheduled
  • Endpoint protection and application-control review completed
  • Representative output tested

Network and Data

  • License host and concurrent-user count confirmed
  • TCP port 3000 reviewed where applicable
  • Database and datastore locations approved
  • Service and user permissions established
  • VPN, remote-office and hosted latency tested
  • Backup scope and retention approved
  • Restore procedure tested
  • Pilot acceptance criteria documented

System Requirements Questions

Common questions from users, procurement teams and IT administrators.

What version of Windows should we use?

Use a current, supported 64-bit Windows release that GAEA has confirmed for the exact product version. Contact Technical Support before deploying a legacy version or a newly released Windows feature update.

Are 8 GB of RAM enough for a desktop workstation?

It may be adequate for smaller workflows, but 16 GB is a more practical evaluation baseline for a professional workstation. Large databases, images, complex sections, models or 3D work may justify 32 GB or more after testing.

Does the software require a dedicated graphics card?

A dedicated graphics card should not be assumed to be mandatory for every product. Current Windows-compatible graphics are required; evaluate stronger graphics hardware for 3D visualization, large imagery or demanding display workflows.

Can GAEA software run on macOS?

GAEA desktop products are designed for Windows. A Windows virtual machine or hosted Windows environment may be evaluated, but the complete workflow, licensing, performance, printing and support implications should be tested before adoption.

Can the software run in Azure, AWS or another hosted environment?

A persistent managed Windows environment may be possible. Confirm license type, server persistence, port access, latency, storage paths, database performance, printing and backup behavior through a pilot.

What network port is used for GaeaSynergy network licensing?

The documented network-license workflow uses TCP port 3000. Limit access to approved network scopes and verify the setting for the installed version.

Does E-ASR require Microsoft Word?

E-ASR report-template creation and generated-document workflows use Microsoft Word. Confirm the appropriate licensed desktop Word environment, fonts, templates and output permissions.

What Android device is recommended for WinLoG Field Assistant?

GAEA recommends at least 8 GB of device memory and a 1080p display. Also test outdoor readability, battery life, storage, camera use, protective cases and the intended synchronization workflow.

Related Planning Resources

Continue from compatibility review into procurement, deployment and implementation planning.

Confirm the Environment Before You Deploy

Send GAEA the product, version, license type, Windows environment, user count, deployment model and representative project details for a configuration review.