A resource block model and a practical mine design must tell a consistent story about the deposit. If geological domains, estimated grades and design solids drift apart, a polished tonnage report can conceal a different planning basis. GEOVIA Surpac is worth evaluating where geologists, mining engineers and surveyors need to work across that handover. This research-based technical assessment uses official sources checked on November 8, 2026 UTC; we did not independently install or test the software.
Need This Software?
Contact us to request the software and receive download and access information.
Surpac is a current Dassault Systèmes GEOVIA product. Its older Gemcom lineage sits within that portfolio: Dassault Systèmes’ July 25, 2013 results explicitly identify the acquired Gemcom business as part of GEOVIA. For a present purchase, the relevant identity is the current Surpac role portfolio and the release and entitlements in the order, rather than an old distributor name.
Follow the deposit from drillholes into a design
Dassault documents drillhole-data management, geological and block modelling, statistics/geostatistics, mine design and production workflows for open-pit and underground operations. The product’s role breakdown is useful because it separates the work: Sectional Geology Modeler covers drillhole interpretation, compositing and geological domains; Block Modeler addresses volumetric models and resource evaluation; Mine Designer develops practical mining geometry; Surveyor updates as-built geometry and reconciliation outputs.
For a hypothetical underground evaluation, establish the drillhole positions and surveys, geological intervals, assays, density information and topographic or existing workings data before creating a resource model. The modelling brief should specify domains, compositing choices and the estimation method. A block grade is conditional on those choices; a software-generated resource report does not independently establish geological continuity or a reportable mineral reserve.
The official Surpac brochure describes variogram tools, compositing, wireframes, block models and an interface to GSLIB for kriging and conditional simulation. Its copyright is 2020, despite the newer hosting path. Use it as background on the documented workflow, not a version-2026 compatibility or algorithm-change record. During acceptance, trace selected blocks back to their domain, input samples and estimation parameters, and inspect the validation and classification basis with the responsible resource geologist.
Mine design then applies geometric and operating constraints to that model. The current product page documents benches, berms and ramps for surface mining, and stopes, tunnels, ramps and shafts underground. It describes Stope Optimizer separately, including mining widths, wall angles, dilution and cut-off inputs. Those constraints are part of the engineering basis; an optimized stope inventory is a candidate design output that still needs the project’s geotechnical and operational review.
2026 Refresh 2 is a release reference, not a benchmark
The official July 10, 2026 announcement confirms Surpac 2026 Refresh 2 and identifies Mine Design, Block Modeling and Caving changes, along with optional Python integration. It is the most recent release announcement verified for this article; the public summary does not establish a particular latest hotfix build or the complete technical scope of each enhancement.
The announcement’s performance and usability statements belong to Dassault Systèmes. No timing measurements or comparative result checks were made here. An existing operation should obtain the detailed What’s New material and relevant corrections for its installed and target builds, then have the model owner approve any changed resource or design output before issuing revised plans.
Automate a repeatable calculation and inspect the handover
The current Mine Contributor description documents record/playback scripting, while the Surpac 2026 offering terms define scripts in TCL/SCL. Refresh 2’s Python integration is explicitly optional. Before promising an automated reconciliation or grade-control routine, establish which role enables it, the supported Python environment and interfaces, and how failures or invalid inputs are reported. Existing TCL/SCL workflows should not be assumed to become Python workflows automatically.
The older brochure documents common GIS/CAD and survey-format exchange, data plug-ins and 3DEXPERIENCE storage/sharing with file versioning and check-in/check-out. Confirm the current connector, format version and licensed services with an actual drillhole database, design solid or block model. Preserve units, coordinates, attributes and model identity across that exchange; a file opening successfully is only one part of acceptance.
Our Oasis montaj assessment provides context for geophysical observations that may inform the geological interpretation. Its format list includes Surpac STR/DTM, but that is not evidence of a live shared resource model. GEOVIA’s product page also lists Whittle for strategic planning and MineSched for tactical scheduling. These are complementary workflow choices, not automatically interchangeable replacements for Surpac’s modelling and design roles.
Specify the workstation and licence architecture together
The GEOVIA support guidance describes DSLS roles rather than the older module licensing, with local node-lock, network concurrent and managed licensing options. Managed DSLS places licence management in Dassault’s cloud data centre; it does not establish that the Surpac modelling application is a browser service. Its VM guidance distinguishes the licence server from the application client, and places conditions on offline and node-locked use. Ask support to approve the exact client/server and remote-use configuration.
The release-2026 terms allow add-on or concurrent schemes as specified in the transaction, impose site/country conditions, and define several possible charging structures without promising that every structure is offered for every program. Obtain the actual role list, simultaneous-user count, term, support/updates and remote-use rights. The existence of older sentinel provisions does not prove that a legacy dongle is appropriate for a new DSLS role order.
An exact Surpac 2026 RF2 operating-system, memory, graphics and prerequisite matrix was not established from the public material reviewed. Dassault’s hardware/software certification overview covers several product families and routes customers to release-specific documentation; its Windows workstation entries alone are insufficient evidence for this Surpac build. Request the current installation requirements and supported database/graphics environment before selecting hardware, particularly for large point clouds or block models.
Need Access to This Software?
Need this software for your project? Contact us for download access, availability, and related information.
Compare one resource-to-design workflow
Micromine Origin and Beyond are a relevant alternative pairing: Micromine documents geological/resource modelling and geostatistics in Origin, with surface and underground mine design in Beyond. Compare the actual licensed combination against Surpac on domain construction, estimation review, block-model exchange, design constraints and repeatable reporting. Our Origin and Beyond assessment offers a separate, documented shortlist discussion. An established team should include the effort to validate converted models and retrain its scripts in that decision, without assuming that either vendor has universally better accuracy or speed.
Surpac belongs on the shortlist when its documented geology, resource, design and survey roles fit the operation’s connected work. Confidence is strongest in that role scope, the verified RF2 announcement and the published licensing distinctions; build-specific compatibility and Python integration details remain procurement questions. Ask the supplier to take one agreed deposit dataset through a resource model, a constrained design and an issued grade/tonnage report, showing which role and assumption governs each step. Prefer another workflow when that exercise exposes a required model or handover that the proposed Surpac configuration cannot demonstrate.
