Application Overview

What Minex Drill models, and the ideas behind it

Core Chains

Project → ExplorationLicence → ExplorationProgram → Target
  → DrillPlan / DrillSite → Drillhole
Drillhole → DrillingShift → DrillingActivity / DrillingDelay / BitRun
  → DailyDrillingReport;  Drillhole → HoleCollarSurvey / DownholeSurvey
Drillhole → GeologyLog / AlterationLog / MineralisationLog
  / StructureLog / GeotechnicalLog → CoreRun → CoreTray → CorePhoto
Sample → SamplingBatch → SampleDispatch → ChainOfCustodyEvent
  → LaboratoryJob → AssayResult → QaqcEvaluation → AssayValidation
Rig / Equipment → Inspection → InspectionResult → CorrectiveAction;
  MaintenancePlan → WorkOrder;  InventoryItem → InventoryTransaction
RiskAssessment → Hazard → Control;  Incident → CorrectiveAction
DrillSite → RehabilitationPlan → RehabilitationActivity / Inspection
SourceAuthority → SourceDocument → Requirement → RequirementApplicability
RegulatoryReport → DataSubmission → SubmissionFile → ValidationIssue

Key Concepts

The drillhole is the spine. Twenty-four models hang directly off Drillhole — surveys, shifts, daily reports, intervals, every logging type, core handling, samples, rehabilitation, risk, incidents and expenditure. A hole carries its planned geometry (azimuth, dip, depth) alongside what actually happened (final depth, status, outcome), and daughter holes wedge off a parent via parent_hole_id.

Plan and actual are both first-class. Programs carry planned vs actual dates and budgets; drill plans carry planned holes/metres/cost with an approval trail; shifts reconcile opening/closing depths into metres drilled, productive hours and classified delays — the numbers a drilling contract is settled against.

Depth intervals are the geological truth. Geology, alteration, mineralisation, structure and geotech logs all key on from/to depth (or point depth for structures) against the hole, with logger, reviewer and an approval status — so a relog can supersede without deleting history. Core runs reconcile drilled vs recovered length; trays are barcoded into storage locations; photos carry wet/dry/UV type and a retake flag.

Assays earn their status. Samples (with blanks, standards and duplicates inserted into every batch) travel under chain-of-custody events to a laboratory job. Each assay result records detection limits and qualifiers; QA/QC evaluations compare standards against certified reference values and duplicates against tolerance. A failed standard raises a corrective action and holds the job at conditionally accepted — grades are usable for targeting but not for external reporting until re-assay confirms.

From regulation to evidence. Source authorities publish source documents containing typed requirements; requirement applicability binds each one to a project, licence or program with a responsible person, due date, compliance status and evidence document. Regulatory reports bundle validated digital data submissions (collar/geology/assay files with per-file validation status and correctable issues) — mirroring how a jurisdiction's exploration reporting portal actually works.

Safety closes its loops. Risk assessments decompose into hazards and controls with verified effectiveness; inspections score template items and spawn corrective actions on failure; incidents drive actions to completion and verification; and every disturbed site gets a rehabilitation plan whose activities and inspections run until sign-off — the same corrective-action model serving QA/QC, inspections, incidents and environment alike.