Datamine Studio RM 3.2: Making Geological Boundaries Explicit in Grade Estimates

Whether samples across a geological contact should influence a grade estimate is a resource-geology decision with consequences for the block model. Studio RM 3.2 makes that boundary choice more explicit, which is a useful reason to evaluate the release beyond its visualization and speed claims. This research-based technical assessment uses official sources checked on November 8, 2026 UTC; we did not independently install or test the software.

Studio RM is Datamine’s geological modelling and resource estimation application. Constellation’s July 27, 2015 announcement records its acquisition of CAE’s mining division, Datamine, into Vela Software. The old CAE Datamine name therefore belongs to the product’s ownership history, not a separate current rival. The official documentation catalogue identifies 3.2 as the latest documented family verified here, replacing the earlier draft’s 3.0.374 baseline; a particular latest maintenance build was not established.

A grade estimate starts with a model and a sample basis

The grade-estimation manual describes an input prototype block model and a sample file containing X, Y, Z and at least one grade field. Samples may be desurveyed drillhole data with classification fields for zone control. Search-volume, variogram and estimation parameter files govern how grades are interpolated into model cells; the resulting model adds estimated-grade fields to the cell structure.

For a hypothetical deposit update, first reconcile new collar, survey, interval and assay data with the geological domains and compositing basis. Then establish the model prototype, estimation method, search and variogram parameters before running the estimate. Studio RM documents nearest-neighbour, inverse-distance and kriging workflows, but those methods are not interchangeable ways to produce a preferred tonnage. Their inputs and assumptions should be approved by the resource geologist and retained with the issued model.

The manual distinguishes GRADE, ESTIMA, INDEST, ESTIMATE and COKRIG rather than treating “estimation” as one uniform command. It also warns that shared supporting parameter files have subtle interpretation differences between ESTIMA and COKRIG. A team migrating a macro should verify its actual process and parameter semantics, instead of assuming that an unchanged filename establishes an unchanged estimate.

Use the semi-soft boundary to express geology

The 3.2 release notes, published July 15, 2026, document semi-soft boundaries in Advanced Estimation/COKRIG. Closed, non-overlapping wireframes and a distance parameter control whether samples just outside a domain can influence its estimate, with different distances for zone combinations. A zero distance gives a hard boundary. This makes cross-contact influence a recorded assumption rather than an informal explanation added after inspecting the result.

A gradational contact may justify investigating such a transition; a sharp geological break may justify keeping it hard. The feature does not establish which interpretation is correct. In a proposed acceptance exercise, compare agreed boundary distances on the same domain and samples, inspect contributing samples and local grade changes, and have the geologist explain the selected treatment. Those comparisons are suggested checks, not calculations performed for this article.

The earlier 3.1 announcement documents Show Samples support for contributing samples for any estimated field, including multi-domain parent cells. The 3.2 announcement adds implicit vein-gap controls, Studio Mapper import and further modelling changes. It describes COMPMAX compositing as experimental. Treat an experimental procedure as something to qualify on the project’s data, not a default replacement for an accepted compositing basis.

Trace the handover and the scripts

Datamine’s 3.1 material documents Leapfrog mesh/project-model imports retaining mesh names and a Geosoft voxel driver for geophysical inversion data. These are specific import routes, not a promise of a lossless shared geological interpretation. Check coordinate systems, units, domain attributes and the selected mesh or voxel data after transfer, and retain the source version alongside the derived model.

The automation documentation describes COM-aware scripting, commonly JavaScript embedded in local HTML, and execution of existing macros. It also documents the controlled CreateObject route replacing deprecated ActiveX instantiation and a script updater. An embedded customization window is not a browser-based cloud solver: the documentation restricts that window from loading internet content. Qualify existing scripts and their permissions during migration, particularly where they create application objects or call external components.

The 3.2 notes also warn that some functions generate field names longer than eight characters, which very old software may truncate when saving. This is consequential for a block-model handover: confirm that grade, density, domain and classification fields survive the actual receiving application. A successful import alone cannot show that downstream reports are using the intended fields.

Prepare the installed environment and the right key

The Studio RM requirements expect 64-bit Intel rather than ARM architecture and list Windows 10 Pro with security updates as the minimum desktop platform, while recommending a current Windows version. They distinguish portable, reporting, typical and big-data scenarios; the typical and big-data memory entries are 32 GB and 64 GB respectively. Use the full current matrix with IT, rather than treating the smallest portable scenario as a resource-modelling workstation recommendation.

The separate graphics guidance specifies OpenGL 3.3 or later and recommends supported professional NVIDIA hardware and suitable drivers. The requirements page recommends SSD storage, while the installation guide requires local administrative access and warns against downgrading the installed Datamine License Services. The delivered build, graphics driver, dataset size and backup arrangement need to be evaluated together.

Datamine’s public licensing migration note explains that version 2 and later use an “RM 2+” key registered locally or on a server; pre-November 2023 RM/Pro keys do not run those versions. Advanced Estimation became part of Studio RM, while RM Pro became a bundle involving RM, Supervisor and Isatis.neo under the described conditions. Do not treat RM Pro as a separate competing estimator or assume an older bundle automatically grants every current product. Obtain the precise commercial term, seats, support/maintenance and offline or remote-use entitlement in the vendor quote.

Compare the resource workflow, not the full mining portfolio

GEOVIA Surpac is a direct alternative for geological domains, compositing, block modelling and resource evaluation. Compare the actual estimation methods, sample-selection controls, geological-boundary handling, validation outputs and model exchange on the same deposit. Our Surpac technical assessment explains its role-based route from resources to design, while the Micromine Origin and Beyond article provides another shortlist context. Datamine’s Studio OP and UG address downstream design/scheduling tasks in the official product-family description; their shared brand does not make them substitute resource-estimation products.

Studio RM is a credible shortlist choice when the team needs its documented implicit/explicit modelling, parameterized estimation and macro workflow, especially when cross-domain sampling must be controlled and explained. Prefer an existing alternative when it already satisfies the accepted model and reporting requirements and a representative conversion exercise offers no clear benefit. Confidence is strong in the documented 3.2 estimation controls and installation requirements; the latest build, precise commercial entitlement and project-specific model behaviour still need confirmation. Ask the supplier to demonstrate the governing domain boundary and contributing samples, then carry that same model into the report and receiving planning tool.