← Industry Solutions

Auregis 2 Comply for Mining & Resources

In development

Structured assurance for complex regulatory environments.

Auregis 2 Comply for Mining & Resources is in development. The intent is to help mining and resources organisations translate regulatory, licence and site-specific obligations into structured requirements, verification activities, evidence, corrective actions and assurance. No mining-specific regulatory content, rule library or workflow exists today.

Register interest

This solution is not operational today. The regulatory content, rule library and industry configuration described here have not yet been developed or validated. It is published to show the platform's direction.

Industry challenge

What makes compliance hard here.

Obligations arrive from several directions at once

Legislation, licences, approvals, environmental authority conditions, site characteristics and operational risk each create requirements, and they rarely sit in one register.

Site-specific conditions are not generic

Two operations under the same legislation can carry very different conditions. A generic checklist cannot express what a particular approval actually requires.

Traceability between obligation and evidence is hard

Monitoring data, inspection records and contractor documents exist, but the line from the condition that required them to the evidence that discharges them is often reconstructed by hand.

Assurance has to be demonstrable

Being compliant and being able to demonstrate compliance, with an auditable trail, are different problems.

Regulatory environment

What the platform is configured against.

  • No mining regulatory content, rule pack or jurisdiction library has been developed or validated
  • Marketing language is deliberately jurisdiction-neutral at this stage
  • The intended model is Country → State / Territory → Mining jurisdiction → Site-specific approvals and conditions
  • Requirement libraries would be configured per jurisdiction and per operation, not shipped as universal coverage
How Auregis 2 Comply applies

The platform, configured for this environment.

  • The same core platform: entities, requirements, verification, evidence, corrective actions, assurance
  • Obligations held as structured, versioned requirements rather than documents
  • Verification and monitoring activity scheduled against requirements, assets and controls
  • Evidence connected to the obligation it discharges, verified by a person
  • Findings and corrective actions tracked to verified closure
  • Auditable trail behind every reported compliance position
Future capability areas

Where the platform would apply.

Intended application of the existing architecture. None of these areas is configured or available for this industry today.

Environmental & Licence Compliance

In development

Future capability to manage requirements originating from Environmental Authorities, licences, permits, approval conditions, environmental monitoring obligations, regulator requirements and site-specific conditions.

Intended lifecycle
Licence / ApprovalConditionRequirementMonitoring / ActionEvidenceVerificationCompliance

Critical Control Assurance

In development

Future capability to connect major hazards and their critical controls to structured verification activity. This is compliance and assurance functionality — it is not intended to replace specialist mine safety systems.

Intended lifecycle
HazardCritical ControlVerification RequirementInspectionEvidenceFindingCorrective ActionAssurance

Statutory Compliance

In development

Future capability to manage statutory obligations, required inspections, statutory positions and appointments, competencies and certifications, supporting evidence, renewal and expiry, and resulting compliance status.

Intended lifecycle
RequirementResponsible RoleActivity / VerificationEvidenceCompliance

Rehabilitation & Closure

In development

Future capability to manage rehabilitation requirements, closure obligations, milestones and due dates, evidence, verification, reporting and corrective actions.

Intended lifecycle
Requirement / PlanMilestoneActivityEvidenceVerificationStatus
Platform foundation

How the architecture would map.

This is the intended application of the existing Auregis 2 Comply architecture to mining operations. It has not been implemented for this industry.

  1. Organisation
  2. Operation / Portfolio
  3. Mine / Site
  4. Area / Facility / Asset / Critical Control
  5. Compliance Requirement
  6. Inspection / Monitoring / Verification
  7. Evidence
  8. Corrective Action
  9. Compliance & Assurance
Rules Engine opportunity

Requirements resolved from real characteristics.

The Rules Engine resolves what applies from the characteristics of the thing being regulated. Applied to mining in future, those characteristics could include the attributes below — so an operation's requirements are determined from its actual regulatory and operational profile rather than a generic checklist. No comprehensive mining rule content exists today.

JurisdictionCommodityMine typeSurface or underground operationActivities undertakenLicences and approvals heldEnvironmental authority conditionsPlant and assetsMajor hazardsCritical controlsStatutory rolesSite-specific regulatory conditions
Site-specific obligations

Site-specific licence and approval conditions

Mining compliance is not determined by general legislation alone. An individual site may carry its own licence conditions, Environmental Authority conditions, approval conditions, monitoring requirements, regulator directions and rehabilitation requirements. A future Mining & Resources solution would allow those to become structured, traceable compliance requirements rather than clauses in a PDF.

Conceptual example
Environmental AuthorityConditionMonitoring RequirementFrequency / TriggerEvidenceResultCompliance Status
AI, governed

AI-assisted obligation extraction.

Deterministic where compliance must be certain. AI-assisted where intelligence saves time. In future, the platform's AI-assisted architecture could help propose obligations extracted from regulatory documents, with a person reviewing and approving before anything becomes a requirement. AI does not determine statutory compliance.

Documents this could apply to
  • Environmental Authorities
  • Licences and permits
  • Regulatory notices
  • Approved plans
  • Rehabilitation plans
  • Site-specific approvals
Conceptual workflow
Upload regulatory documentAI-assisted obligation extractionHuman review and approvalStructured requirementDeterministic compliance workflow

A person reviews and approves every proposed obligation before it becomes a requirement. AI does not determine statutory compliance.

What this is, and isn't

Compliance assurance, not another operational system.

Auregis 2 Comply is not an EHS platform, a maintenance system, a mine planning system, an asset management system or an incident management system. It is a compliance assurance platform, and it exists to answer a specific set of questions.

What are we required to do?
Why are we required to do it?
Who is responsible?
When is it due?
Has it been completed?
Where is the evidence?
Were failures corrected?
Can we demonstrate compliance?
Compliance lifecycle

From obligation to evidence, end to end.

  1. 01

    Understand the operation, its sites, assets, hazards and approvals

  2. 02

    Resolve applicable obligations, conditions and critical controls

  3. 03

    Plan verification, inspection and monitoring activity

  4. 04

    Prove with connected evidence

  5. 05

    Verify results and control performance

  6. 06

    Correct findings through to closure

  7. 07

    Assure through live reporting and audit trail

Reporting and assurance

What leadership and regulators see.

  • Platform reporting and audit trail apply once the vertical is configured