Operational views
Review work, evidence, exceptions and authorised decisions within a defined operating scope.
Mining & resources
Connect drill intervals, sample batches, laboratory custody, assay reconciliation and reviewed release of exploration data.
12 workspace menus · 5 role profiles · Connected records
Designed for exploration geology managers and laboratory coordination teams

Operational workspace and record review. Select a screen to inspect it in full.


Review work, evidence, exceptions and authorised decisions within a defined operating scope.
Connect drill intervals, sample batches, laboratory custody, assay reconciliation and reviewed release of exploration data. An assay result is useful only when it can be traced to the correct sample and reviewed against quality checks. The system follows sample identity and custody through dispatch, laboratory receipt and reconciliation, preserving exceptions before data is released for geological interpretation.
From intake to authorised completion, with evidence at each decision.
Register drill intervals and approved sample batches.
Track dispatch and laboratory custody.
Reconcile assay results and quality checks.
Release reviewed data to geological interpretation.
Permissions are configured and tested for the agreed responsibilities.
Interface scope, data mapping and testing are agreed for each engagement.
Capture sample identifiers and custody events in field views. Offline requirements need separate validation.
Access approved workflows through the Dalfin mobile app. Device tasks and permissions are confirmed for the deployment.
Core workflows and approval rules are defined with your business owners. Operational AI can be assessed separately against a specific business outcome and review requirements.
AI extensions are scoped around the required data, business outcome and review controls.
Connect requirements, roles, records, workflows and interfaces through the agreed Genesis engineering process.
Review dependency impact and validation requirements. Context Memory supports governed changes and accepted application revisions.
Agree customer cloud or on-premises requirements, device access, implementation acceptance and ongoing engineering support.
An example operating scenario
A sample batch is dispatched to a laboratory. An identifier mismatch is raised during reconciliation and corrected with custody evidence. The quality reviewer records the checks before the authorised data release, retaining the original exception and resolution.
Roles, approval authority, business rules, records and reporting are configured around your operating model. Scope definition connects the required business outcome to workflows, interfaces and acceptance criteria.
Operators, reviewers and authorised decision makers have defined responsibilities. Approval limits, exception handling and access permissions are agreed with your business owners and tested against the selected workflows.
Interface requirements cover your existing business systems, data ownership, mapping and authentication. Connection design and testing form part of the agreed implementation scope.
Start with a relevant business transaction, then review its approvals, an exception, role permissions and final records. Discuss the integrations, reporting and operating requirements that matter to your organisation.