GEOVIA Minex implementation and data migration
From a raw borehole database to a signed-off seam model and a mine plan your board will accept. Most operations do not fail at buying software — they fail at the eighteen months afterwards.
Four stages, eight to sixteen weeks
How long depends on how much historical data has to be reconciled, not on how many licences you bought.
Assessment
We read what you have: borehole database, existing grids, last reserve statement, and the scripts nobody has opened since the author left. The deliverable is a written finding, including when the finding is that your setup is sound and needs nothing.
Data and migration
Migration from Vulcan, Carlson and legacy grids. Database connection to acQuire, Oracle, SQL Server and Access. Validation before anything is modelled, because a model built on unreconciled data is a faster way to be wrong.
Model and workflow
Seam model rebuild with fault definition and quality curves, then the monthly cycle scripted in Tcl and SQL so the same numbers come out the same way every period.
Handover
Written procedures, scripted workflows and trained people. Retained support exists for model reviews and staff turnover, not to keep you dependent.
Coming from Vulcan or Carlson
Stratified data does not move cleanly between packages by default. The geometry survives; the meaning often does not.
- SourcesVulcan, Carlson, legacy grids
- DatabasesacQuire, Oracle, SQL Server
- Validationbefore anything is modelled
- Minex modelseams, faults, quality
- Reconciliationagainst the last statement
Nothing is modelled until the data behind it has been checked
- Grids and surfaces. Legacy grid formats rebuilt as Minex surfaces, with the interpolation assumptions written down rather than inherited silently.
- Borehole databases. Direct connection to acQuire, Oracle, SQL Server and Access, or a clean one-time import with a validation report attached.
- Quality and washability. The part generic packages express poorly and Minex expresses natively — and the part most likely to be lost in a careless migration.
- Reconciliation. The new model is checked against the last reported reserve statement before anyone signs it off. If the numbers move, you find out from us first.
Should you be moving to Surpac?
Not automatically, and we will say so even though the migration project would be ours to sell.
Surpac is the stronger choice for massive and vein deposits. It does not replicate the stratigraphic and washability depth that makes Minex worth using on coal. Where a migration genuinely makes sense — a group standardising across mixed commodities, for instance — established workflows exist for moving stratified and quality models from Minex into Surpac, and ACALA supplies both. We will scope that honestly rather than sell you a project you do not need.
What buyers ask about implementation
Can you work with our existing Vulcan or Carlson data?
Yes. Migration from Vulcan, Carlson and legacy grid formats is routine work, as is database connection to acQuire, Oracle, SQL Server and Access. The effort sits in validating and reconciling the data, not in the file conversion.
How long does a Minex implementation take?
Typically eight to sixteen weeks, driven by how much historical data has to be reconciled. A single-seam operation with a clean acQuire database is at the short end. A multi-seam site with fifteen years of spreadsheets and three abandoned modelling attempts is at the long end, and pretending otherwise helps nobody.
What happens after the implementation ends?
Every engagement ends with written procedures, scripted workflows and people who can run them. Retained support exists for model reviews and staff turnover. If you need us less each year, the work was done right.
Will our reserve numbers change after migration?
Sometimes, and that is the point of reconciling against the last reported statement before sign-off. If the new model produces a different number, you need to know why before it reaches a board paper — not after.
Does our borehole data have to leave our systems?
Only if you want it to. Where your policy keeps the data in place, we work on your infrastructure by screen share or on site. Where it does come to us, it is confidential by default with no separate instruction needed, used only for your engagement, never used to benchmark or to build our own library materials, and never exposed across clients. At the end we return it or destroy it on your instruction and confirm in writing which we did and when. Full controls are on our Data Protection & Compliance page.
Tell us about your deposit
Commodity, seam count, Minex version and user count. Those four lines are enough for us to answer with numbers instead of questions.
Related: Licensing & pricing · GEOVIA Minex training