Mining labs run on volume and turnaround. Drill core comes in by the truckload, each sample tied to a hole, a depth, and a campaign that an exploration team is making decisions on. The assay needs to be defensible, and the geologist needs the result back in a form they can plot. LabRelations builds LIMS for that work: sample registration with collar and depth context, prep, fire assay, ICP and XRF runs, QA/QC, and reporting in formats that load straight into your geological model. QMS sits alongside for ISO 17025 accreditation: documents, training, deviations, supplier qualification, and CAPA.
The bench team works in software designed for the bench, and QA works in software designed for quality. They share data where it counts (a deviation linked to the sample that triggered it, an SOP read by the analyst logged the same way as the assay), but each system stays focused on the team using it.
LIMS for the bench. QMS for accreditation. Used independently. Connected where it matters.
Samples are registered against the hole, collar, depth, and campaign at receipt. Splits, duplicates, and pulps inherit the parent context automatically. Geologists get results back tagged with the right metadata to load straight into their modelling tools.
Batches are built around the actual flow of the lab: crushing, splitting, pulverising, fire assay, digest, instrument run. Each step records its operator, equipment, and conditions. Fire assay trains and ICP/XRF runs are tracked at the level needed for QA/QC review.
Reference materials, blanks, and duplicates are inserted at configurable frequencies. Acceptance criteria are checked automatically. A QC failure blocks reporting on the affected batch and opens an investigation. The QC summary lands in the report as part of the package.
Methods, detection limits, and unit conventions are version-controlled. The right version applies to the right sample. Changes go through a controlled change with electronic approvals before they're live.
Documents, SOPs, training, deviations, supplier qualification, internal audits, and CAPA. The records the assessor wants (proficiency tests, equipment records, method validation files) are organised the way the standard expects.
Yes. Direct integrations with ICP, XRF, fire assay weigh stations, balances, and the rest of the standard kit, plus a generic interface for anything else. Results land against the right sample without manual entry.
Reports and exports are configured per client and per campaign. Detection-limit conventions, unit handling, and below-DL reporting are controlled centrally.
A mix of people who've actually worked in the industry supported by technical people for configuration needs inside the platform itself.
