Scope & who owns this
This page applies to PT Acala Genesa Sumberdaya (“ACALA”) and to every engagement delivered under the MinexCoal name: licence supply, implementation, data migration, training and retained support.
The Director owns the risk process. That means one named person is accountable for the risk register existing, being reviewed, and being acted on — not for personally managing every risk in it. Accepting a risk is a decision the Director records, not something that happens by default when nobody raises it.
Individual risks have their own owners, because a process owner who cannot fix anything is a signature, not a control:
| Risk | Owner |
|---|---|
| Model, estimation and reporting quality | The senior geologist & mining engineer on the engagement |
| Key-person dependency, resourcing, competence | Director |
| Client data: confidentiality, transfer, destruction | Director, with the engagement lead |
| Platform and licence continuity | Director, through the Dassault Systèmes partnership |
| Commercial terms, scope and liability | Director |
Who this page is written for. Procurement, vendor onboarding and technical due diligence teams. If your questionnaire asks something this page does not answer, ask us rather than assuming.
How we run it
ACALA operates management systems certified to ISO 9001:2015 and ISO 14001:2015. Both require the organisation to address risks and opportunities, and both put that duty on top management rather than on a delegate. Our risk process sits inside those systems rather than beside them.
Risk is looked at three times, and the first is the one that matters most:
- When a proposal is scoped. Before a price exists. This is the only point at which the cheapest treatment — declining the work — is still available, and we do use it.
- When an engagement starts. Assumptions written into the proposal are tested against what the data actually looks like. Where they do not hold, the scope is re-cut and you are told before the work continues, not after it.
- At management review. The register is reviewed as a whole, and anything that materialised during the period is written up — what happened, what it cost, and what changed as a result.
- Proposal scopedBefore a price exists — declining is still on the table
- Engagement startsAssumptions tested against the actual data
- Management reviewThe register reviewed as a whole, in writing
One register, one accountable owner: the Director
Consequence is assessed by what a risk would do to your deliverable, not to our invoice. A modelling error that costs us three days and costs you a resubmission is a serious risk, not a small one.
Review interval: annually, at management review.
Model & reporting risk
This is the risk that matters most, because it is the one that does not announce itself. A seam correlation carried across the wrong fault block does not throw an error. It produces a tonnage, and that tonnage flows into a reserve statement, a schedule, and an RKAB submission — and is usually found at review, which is the most expensive moment available to find it.
What we do about it
- Nothing is handed over on the strength of looking right. Every model we deliver comes with the evidence a reviewer will ask for: variance and sample-count grids, variograms, QA/QC records, and a reconciliation against what was reported last period.
- Reconciliation is part of the work, not an extra. A model that cannot be reconciled against the previous statement is not finished, whatever it looks like on screen.
- Assumptions are written down where they are made, in the procedure rather than in someone’s memory, so the next person can see what was decided and why.
A boundary we do not cross. We do not sign off resources or reserves as Competent Person, and we are wary of any supplier who offers to. That is your appointment, and the responsibility is personal to the individual who takes it. Our job is to make sure that person walks into the review holding the evidence. See JORC, SNI & RKAB reporting.
Key-person risk
We sell against single-point-of-failure risk, so we had better be honest about running it ourselves. If one ACALA consultant carries your engagement in their head, you have not removed a dependency. You have moved it to a different payroll.
What we do about it
- Every engagement closes with written procedures and scripted workflows that your own team runs. That is the deliverable, not a by-product of it.
- We train more than one of your people, deliberately, so the model does not end up sitting inside a single head on your side either.
- More than one person here is briefed on an active engagement, and handover notes exist before anyone needs them.
The honest limit. We are a specialist firm, not a large one. We will not promise that a particular named individual is always available. What we do guarantee is that the work is written down — so continuity does not depend on who answers the phone.
Platform & licence continuity
GEOVIA Minex is on Continued Support at its current release. That is a published position in the vendor’s lifecycle, and it is a risk you are entitled to weigh before you buy, not after.
What we do about it
- We tell you where the platform stands before a licence is bought. A supplier who lets you find that out at renewal has made your risk into their revenue.
- Automation is written to outlive a version. SQL and Tcl workflows are documented so they survive an upgrade — and, if it ever comes to it, a migration to a different platform.
- Your model is yours. Data, models and procedures are handed over in forms you can keep using without us. See Intellectual property.
What is outside our control. We are an Official Dassault Systèmes Partner. We cannot vary the vendor’s licence terms, warranties, support commitments or roadmap, and we do not pretend otherwise. Where a vendor decision affects you, our role is to tell you early and help you plan around it.
Data & migration risk
Migrations are where data goes quietly missing. A legacy grid, a Vulcan or Carlson export, a borehole database with out-of-sequence depths — each can convert cleanly and still be wrong, because nothing in the conversion checks whether the result means the same thing.
What we do about it
- Nothing is modelled until the data behind it has been validated. Validation is a gate in the sequence, not a step we get to if time allows.
- The migrated model is reconciled against the last published statement before it is accepted as the working model.
- Your data does not have to leave your systems. Where your policy keeps it in place, we work on your infrastructure. Where it does come to us, confidentiality, transfer and destruction are covered in detail on our Data Protection & Compliance page.
Commercial & delivery risk
- Scope, assumptions and limitations are written into every proposal. An assumption that is not written down is a dispute waiting for a date.
- We decline work we are not competent to deliver, and we say so plainly rather than subcontracting the problem.
- Lead times are stated at quotation. If any part of the chain is going to run longer than that, you hear it from us then, not afterwards.
- Disagreements have a route. Escalation, governing law and forum are set out in our Terms & Conditions.
What this page does not cover
Stating the edges is part of managing risk, not an admission against it.
- Your operational and mine safety risk. We do not operate mines, and nothing here manages the hazards of one.
- The financial or market risk of your project. Commodity price, permitting and financing are yours.
- The legal allocation of risk between us. Liability limits, warranties, force majeure and termination live in our Terms & Conditions, and this page does not enlarge them.
- Information security detail. Technical and organisational measures, sub-processors, incident response and business continuity are on our Data Protection & Compliance page.
- Professional indemnity insurance. [cover and insurer, or a statement that none is held]
Review & contact
This page is owned by the Director of PT Acala Genesa Sumberdaya and reviewed alongside our ISO management systems.
For due diligence questionnaires, supplier onboarding, or a question this page does not answer: hello@minexcoal.com. For security incidents and vulnerability reports, use the route on our Data Protection & Compliance page.
Related: ESG & Sustainability · Data Protection & Compliance · Terms & Conditions