Documentation

The reference every SRES user should keep open.

Ten reference sections covering the platform end-to-end — with tuning cheatsheets and code samples where relevant.

Section 01

Getting started

Every SRES tenant ships with an empty workspace and a single superadmin account. The onboarding flow guides your team through creating the first company, inviting users, and importing the first drillhole database.

Recommended path: create the workspace → invite two additional users (a geologist and a Competent Person) → import a sample dataset from the built-in library → run through the five-step pipeline (ingest → QAQC → statistics → variography → kriging → classification → CPR).

System requirements

Modern Chromium, Firefox or Safari. Screen size ≥ 1280 × 800 recommended. No desktop installs, no license servers, no dongles.

Account creation

Superadmins invite users via the Company Admin panel. Each user receives an email with a one-time link that forces a password reset on first login.

Sample data

Every new tenant includes the SRES sample project — a small Fe-ore drillhole database (12 holes, 400 assays) you can push through the full pipeline in under 30 minutes.

Section 02

Data ingest

SRES accepts Collar, Survey, Assay and Geology CSVs plus QAQC control samples (CRM, Blank, Duplicate). Column names are auto-mapped from industry aliases — most files import on the first try.

The ingest UI shows per-file row counts, a hole-count summary, and any validation issues categorised by severity (error / warning / info). Errors block downstream steps until resolved; warnings and infos are logged.

Column auto-map

Recognises BHID → hole_id, easting → x, northing → y, elevation → z, from/to intervals, grade columns, lithology codes and structural attributes.

Composite lengths

SRES exposes composite length as an explicit parameter — 1 m, 2 m, 3 m or custom. Composites are stored per project, not per file, so they survive re-ingest.

Domain scripts

Save reusable pandas queries per project and per user (lithology filters, grade cuts, spatial windows).

Section 03

QAQC & validation

Deep validation catches missing surveys, out-of-hole assays, geometry overlaps and negative depths before they contaminate a block model. QAQC analytics deliver control-chart envelopes on CRMs, blanks and duplicates.

Every batch produces a validation report (PDF + JSON) and a QAQC report. Both are versioned per project so a reviewer can see how data quality evolved through the drilling programme.

Validation categories

Errors (block further work), warnings (recommend fix), infos (visibility only). Every issue lists affected hole IDs and one-click drill-down.

Precision & bias

Half-Absolute Relative Difference (HARD), Sample Bias %, top-cut suggestion, log-probability plots and control-chart envelopes.

Section 04

Estimation engines

SRES ships three complementary interpolators: Inverse-Distance Weighting (IDW), Nearest Neighbour and Ordinary Kriging. All three support composite lengths, per-lithology density mapping and Measured / Indicated / Inferred classification.

Kriging supports fitted spherical, exponential and Gaussian variogram models. Anisotropy is detected from the experimental variogram and confirmed by the user before the block model is committed.

Ordinary Kriging

Search neighbourhood, minimum samples, maximum samples, per-domain variogram fits, slope-of-regression for classification.

Block model outputs

Grade, tonnage, classification and confidence per block. Exported as CSV, GeoJSON, SHP or DWG-ready formats.

Section 05

Variography

Experimental variograms are computed directly from your composites — no manual pair-list export. Fitted models are plotted alongside the experimental points so you (and your auditor) can eyeball the fit.

Every fit records the nugget, sill, range and model type into the CPR narrative. There is nowhere for a bad assumption to hide.

Model types

Spherical, exponential, Gaussian. Each fit exposes nugget, sill and range as adjustable parameters.

Anisotropy

Directional variograms and rotation angles supported per domain.

Section 06

Classification & confidence

SRES supports Measured / Indicated / Inferred classification based on search-neighbourhood coverage, number of informing samples and slope-of-regression thresholds.

Every block is stamped with its own classification and a confidence score. The CPR narrative surfaces the aggregate classification breakdown per lithology.

Classification rules

Configurable per project. Defaults follow JORC / NI 43-101 guidance.

Confidence audit

Every block links back to the samples that informed it. Auditors can drill down from tonnage to sample.

Section 07

Economics & sensitivity

Floating-cone pit optimisation runs on the block model with commodity-aware pricing and slope constraints. Cut-off × NPV sweeps are visualised as a live slider — no re-runs required.

Sensitivity sweeps span price, mining cost, processing cost and recovery. Monte-Carlo NPV supports triangular distributions with 1,000 – 10,000 trials.

Pit optimisation

Slope-constrained floating-cone. Outputs ore, waste, strip ratio and NPV per shell.

Monte-Carlo NPV

Configurable trial count, triangular distributions and P10/P50/P90 disclosures.

Section 08

Competent Person reports

SRES assembles a full CPR PDF (and DOCX) with cover, executive summary, methodology, findings, sensitivity and appendices. Signature blocks accept uploaded images for Prepared / Reviewed / Approved.

Every export is snapshotted. Watermarked public share links carry expiry, view counter and audit log.

Templates

JORC, NI 43-101, SAMREC, CIM and PERC-aligned templates ship out of the box.

Public share

Configurable expiry (7 / 30 / 90 days), IP allow-listing on request, per-token view count.

Section 09

REST API

Every UI action in SRES is backed by a documented REST endpoint. Enterprise tenants can wire SRES directly into their reporting pipelines and BI tools.

Full API reference is provided as an OpenAPI spec inside the workspace, plus curated code samples in Python and TypeScript.

Authentication

JWT bearer tokens plus optional API keys for machine-to-machine integrations.

Rate limits

Per-tenant rate limits are configurable in the Enterprise plan.

Section 10

CLI & automation

Long-running kriging or pit optimisation jobs can be triggered from the CLI and orchestrated by CI systems. Every job returns a snapshot ID that can be re-downloaded via the API.

Batch operations across projects (portfolio pit sweeps, bulk CPR regeneration) are supported for enterprise deployments.

Job orchestration

Async background jobs with progress feedback, cancellation and retries.

Batch operations

Portfolio-level pit sweeps and CPR regeneration across dozens of projects.

Need something not here?

Every SRES tenant ships with a named support geologist — ask them, don't fight the docs.

If a workflow you need isn't in this reference, tell us. We update the docs from customer conversations, not from marketing.

Contact support