Mining & ResourcesCritical controls with their evidence attached.
The mining pack sets agents up around resource and project requirements, material unwanted events, critical controls, bowtie analysis, tailings and environmental obligations, changes, inspections and closure. They keep that record linked inside your Azure DevOps project, show what a change touches, and open the verification work it needs. Competent persons and accountable owners keep every decision.
No card required. Your data stays in your Azure DevOps tenant.
- JORC Code
- NI 43-101
- MSHA
- ICMM critical-control methodology
- Bowtie analysis
- ISO 45001
Change must keep the evidence behind every key decision.
Mining projects and operations combine resource confidence, critical controls, geotechnical and tailings risk, process and mobile equipment, environmental commitments, maintenance, monitoring, incidents and closure. Engineering and operational changes happen every week. Each one has to preserve the evidence behind competent-person, safety and environmental decisions, or the next review starts from a record nobody fully trusts.
- 01
A change weakens a control nobody linked.
A process or equipment change alters how a critical control performs, but the bowtie, the performance standard and the verification schedule still show the old picture.
- 02
Control verification goes overdue quietly.
Verification tasks sit across spreadsheets and inboxes. The first sign a control is overdue is an audit finding or an incident.
- 03
Environmental commitments drift from operations.
Tailings reviews, monitoring requirements and closure commitments are agreed once, then lose their links to the changes that affect them.
- 04
Incident actions close without proof.
Actions from an incident are marked done, but the control, procedure, training and verification evidence behind the closure are hard to find.
Your site's risk model, set up as configuration.
Four layers tell the agents how your operation classifies assets and risk, links the record, maps it to frameworks and gates it. Tailings and closure requirements follow those applicable to the operation.
- 01 Classification
Every item knows its site and its risk.
Asset, site and process, resource category, material unwanted event, critical control, consequence, operational and environmental risk, tailings and closure significance, change class, and evidence status.
- 02 Traceability model
From need to closure evidence.
Business, resource or operational need to requirement, hazard, bowtie and critical control, design, configuration or procedure, inspection, test or monitoring, change and approval, then operational and closure evidence.
- 03 Standards & frameworks
Mapped to the frameworks you report against.
JORC Code and NI 43-101 context, MSHA where applicable, the ICMM critical-control methodology, bowtie analysis, ISO 45001, and the tailings and closure requirements that apply to the operation. Mappings are reviewed by your subject-matter experts.
- 04 Lifecycle gates & evidence
Gates from model review to closure.
Resource and model review, critical-control verification, design and change review, commissioning, inspection and monitoring, incident action closure, tailings review, environmental commitments, and closure readiness.
The Mining chain, kept intact.
An equipment change breaks the link between a requirement and its critical control. The agent flags it, opens verification, and confirms the link is restored.
- Operational need
- Requirement
- Critical control
- Procedure
- Verification
- Change approval
- Closure evidence
Six mining workflows to hand over first.
Each one runs the same controlled sequence: trigger, context, decide, act, approve, verify, record. Output lands on the work item or wiki page your site team already uses.
Critical-control management
Link material unwanted events, causes, controls, performance standards, owners, verification, findings and evidence, so every control has a named owner and a current status.
Compliance Officer Agent
Bowtie and risk traceability
Maintain threats, preventive and mitigating controls, consequences, escalation factors and linked requirements, and flag a bowtie that a change has outdated.
Requirements Engineer Agent
Engineering change impact
Identify the hazards, controls, equipment, procedures, maintenance, monitoring, approvals and environmental obligations a change affects.
Business Analyst Agent
Inspection and control verification
Create and track verification tasks, findings, evidence and corrective actions, and report overdue controls before they become findings.
QA Engineer Agent
Tailings and environmental evidence
Link requirements, monitoring, reviews, changes, findings, commitments and closure actions, so obligations stay connected to operations.
Product Owner Agent
Incident and action follow-up
Connect incidents to controls, changes, maintenance, training and verification, and check that each action closes with accountable evidence.
Release Manager Agent
A resources advisor, working with the role catalog.
The supplied catalog includes a Mining Resources Advisor configured for this pack. It works alongside the role agents in the catalog, with explicit handoffs and approval boundaries between them.
Compliance Officer Agent
Keeps each critical control linked to its performance standard, owner, verification and evidence.
TraceRequirements Engineer Agent
Maintains bowtie links from threats and controls to requirements, and flags them as suspect after a change.
TestQA Engineer Agent
Schedules control verification, tracks findings and reports overdue controls by site and owner.
ReleaseRelease Manager Agent
Checks incident actions close with evidence: control, procedure, training and verification.
Mining roles in the catalog
- Mining Resources Advisor
A process change is proposed. Here is what follows.
A change request to raise conveyor speed on a crushing circuit is raised in Boards, and the advisor's trigger condition matches. It identifies the affected material unwanted events, critical controls, performance standards, procedures, maintenance, training, inspections, monitoring, environmental commitments, approvals and closure assumptions. It creates the verification and update actions for named owners, pauses for approval, then checks each action closed with evidence and writes the run record to Job Explorer.
run started · MOC-163 conveyor speed change
tracing: 2 MUEs · 4 critical controls
3 procedures · 1 monitoring commitment
verification and training actions drafted
checkpoint · awaiting control owner
record · run history in Job Explorer
- ✓ Critical controls linked
- ! Performance standards met
- ✓ Procedures and training
- ✓ Monitoring and environment
- ! Approvals named
The agent tracks the evidence. Accountable people decide.
Competent persons, engineering, geotechnical and tailings, safety, environment, operations, maintenance and regulatory authorities stay responsible for resource statements, risk, critical-control acceptance, field execution and closure decisions. The agent schedules, links, collects and checks. With Required Approval on, any step with side effects pauses and opens a task for a named approver, who can answer, attach files, and approve, edit or reject it. Every decision is kept in the run record.
[ Trusted by Microsoft and industry leaders ]
Mining and resources questions.
No. Qualified competent persons remain responsible for public reporting and technical conclusions.
It can schedule, track, collect and check available evidence against your configured performance standards. Field verification and accountable acceptance are still required.
Only through supported and approved routes. Agents work on Azure DevOps artifacts, and Bring Your Own Data lets them retrieve from uploaded documents, queries and wiki pages. Decide the sources, frequency, quality checks and action boundary before you rely on them.
Yes. Schedule an agent once, daily, on weekdays, weekly, monthly or yearly. It can still be run on demand at any time, and the dashboard shows run volume and failures.
Only where you want it. Conditional triggers combine field, operator and value rows with AND/OR logic, per work item type, so it runs on the change classes you pick and spends no credits on the rest.
No. Agents run inside your Azure DevOps environment with no separate portal or login, and your project data is not used to train models.
Nothing extra. Every plan includes the full catalog and all 15 industry packs. Credits cost $0.01 each, pooled across your organization with no per-user fees. A rule-based Execution Agent run is a flat 4 credits.
Bring one critical control to the demo.
Start a free trial with 2,000 credits, no card required. Or book a 30-minute demo with a real change, control, incident action or evidence gap, and watch the trace, approval point and run record live.
