A drilling-data handover needs agreed hole identifiers, coordinate and depth conventions, record status and a way to return rejected records. Check planned holes, contractor shift reports and accepted geological records separately, because a profile that mentions import or synchronisation does not prove that all three move correctly.
Drilling data crosses more boundaries than most mine data. A hole starts as a design, becomes a collar and a survey, then a set of daily shift records, then a validated geological record, then an input to a resource model. Each step can use a different system, a different identifier and a different idea of what "approved" means.
This article maps the three handovers, shows what a dated audit of MSR listing descriptions can and cannot establish, and sets out the records to request before a mine accepts the workflow. The exploration drilling management buying guide and the geological database management software guide cover selection; this article stays on acceptance at the boundaries.
Map the three drilling-data handovers
Separate the chain into three handovers. Each has its own owner, failure mode and acceptance test.
Planned hole and collar to field crew
The first handover turns a hole design into a location the drill crew can find. The design defines a collar coordinate, a target depth, an inclination and an azimuth. The field crew needs the collar position on the ground, a unique hole identifier and a way to record that the hole was collared as planned or with a revision.
The questions start early. Which coordinate reference system and datum does the design use, and which does the survey device use? Are depths measured along the hole or vertically? Who assigns the hole identifier, and is it ever reused? What happens when the collar moves because of ground conditions? A revised collar is normal. A revised collar that arrives under a new identifier is a data problem.
Rig shift record to operations office
The second handover carries the contractor's daily record: metres drilled, activities, delays, samples, consumables and timesheets. Contractors may use their own formats, their own rigs and their own supervision. The operations office has to consolidate those records across rigs and compare them with the plan.
Ask how a shift record is submitted, whether it is captured offline and synchronised later, who reviews it and who approves it. Ask what a rejected record looks like: is it returned with a reason, or does it wait in a queue? The handover is complete when the office can reconcile the file to the hole and the shift.
Validated geological record to database and model
The third handover moves logged and validated geology into the database and then into the model. Logging may happen in a core shed, on a tablet at the rig or in a scanning system. Validation applies dictionaries, rules and approvals. The database holds the accepted record. The model consumes it.
Each step can hold a different status. A logged interval is not an approved interval. An approved interval in a database is not necessarily the version the model used. Ask for the status model and the audit trail: who changed a record, when, from what value to what value, and on what authority.
Direction matters as much as status. In its 9 October 2026 IMARC coverage, International Mining reported that acQuire says its BlackFox drilling management software is integrated with GIM Suite, and that "hole collar details captured in GIM Suite can be transferred directly into the drill hole planning interface within [BlackFox]". The article quotes acQuire saying the integration reduces manual data transfers and helps teams initialise drill programs faster.
Treat those statements as vendor claims. The described direction is from GIM Suite to BlackFox, for collar details, at the start of a program. That is not evidence that the reverse transfer works, that revised collars reconcile, that shift records move, or that a rejected record can be returned. The MSR descriptions for BlackFox and GIM Suite do not document the transfer either.
What the directory descriptions actually document
MSR screened the exploration-drilling and database-management listings supplied on 10 November 2026: 24 exploration-drilling listings and 15 database-management listings, 39 distinct slugs. The table records literal wording under three codes. A listing counts once per code, codes overlap, and the counts describe descriptions, not vendors or tested systems. The descriptions are vendor claims and are visibly truncated, so a missing word means unknown.
| Code | Coding rule (literal wording in the listing description) | Exploration mentions (n=24) | Database mentions (n=15) |
|---|---|---|---|
| C | Literal "collar" | 0/24 | 3/15 |
| P | Explicit drill-program planning or drillhole plans, not generic mine planning | 2/24 | 0/15 |
| T | Explicit import or export, sync, transmitted field data, direct data feed, or named cross-system integration carrying geoscience records | 6/24 | 6/15 |
Totals by code: C 3/39, P 2/39, T 12/39. Do not add the codes together. They overlap, and the result would not be a coverage rate.
Dated coding table, scope and unknowns
C, literal "collar" (3/39). Three database listings name collar data: 1point, DataShed5 and GIM Suite. No exploration-drilling description in the snapshot uses the word. That does not mean exploration products cannot hold collar data. It means the supplied text does not say so.
P, drill-program planning (2/39). CorePlan says it lets geologists "plan drill programs". Datamine Discover provides "drillhole plans". Neither database listing describes program planning. The code is about planning wording, not scheduling or rig allocation.
T, transfer wording (12/39). Exploration-drilling mentions (6/24): Breeze Geo describes exporting results; Datamine Discover imports and centralises geoscience data; GeoticMine is directly linked to the GeoticLog database; KruxLog describes "syncing data" when a connection returns; LogChief synchronises automatically; Minalyzer CS feeds scanner data directly to Minalogger.
Database-management mentions (6/15): DataShed5 imports geoscience data; GIM Essentials produces validated, export-ready datasets; IMDEXHUB-IQ shows field data transmitted from IMDEX instruments; Plexer lists "assay result import"; Seequent Central integrates with named applications; Seequent Evo brings products together with open APIs.
The code covers different jobs, from scanner feeds and field capture to database import and model management. It does not establish raw collar exchange. Four exclusions show the rule. BlackFox captures daily drilling data but does not describe a transfer in the supplied text. Datamine LIMS mentions barcode and QR code integration for laboratory sample handling, which is not geoscience record exchange. NextMaps mentions spatial exports for tenement maps, not geoscience records. Strata describes an ecosystem that links Veracio products, which is a product-family connection rather than a named record transfer.
Three near misses sit outside the code for the same reason. MinePortal describes three integrated solutions inside one product. Matrixx Xchange standardises contractor DDR data without using a transfer term in the supplied text. TruStructure analyses core imagery captured by Veracio's TruScan system but does not describe the feed. A wider reading of transfer would move these cases and the four exclusions above, which is why the rule is stated literally.
Specify a handover contract
A handover contract is a short document that says what must survive each boundary. It gives the mine a way to test the supplier's interface documentation.
IDs, coordinate reference system, units, timestamps and approvals
Define the hole identifier once. State the format, the issuer, the lifetime and whether an identifier can be reused after a hole is abandoned. Map every system's identifier to it and keep the map.
State the coordinate reference system and datum for collar coordinates, and the transformation used when a system expects a different one. State whether depth is measured along the hole or vertically, and what the elevation reference is. Give the units for every numeric field.
Define timestamps: local time or UTC, the shift date convention, and the precision. Define the approval roles: who can log, who can validate, who can approve, and what evidence the approver sees. A record without an approver is a draft, whatever the file says.
Revisions, duplicate submissions and rejected records
Revisions are normal in drilling. Collars move, depths change, assays are re-run, and a shift report can be submitted twice. The contract needs a version rule and a duplicate rule.
A revised collar should carry the original identifier, a version number, a reason and a timestamp. It should not become a second hole. A duplicate shift report should be detectable, either by a submission key or by the combination of hole, rig, shift and contractor.
A rejected record needs a return path. Define the rejection codes, who can raise them, what the submitter sees, and how a corrected record is linked to the original. Test that a corrected row can be re-submitted without creating a second accepted record. If the only return path is an email or a phone call, say so, and name who handles it.
Ask for a traceable sample transfer
Ask each supplier to run a small transfer with records the mine supplies. Use as many records as it takes to trace one source record to one accepted record, with every change visible.
One planned hole, one revised collar and one rejected row
Build a sample pack with three cases. First, a planned hole with a collar, target depth, inclination and azimuth. Second, a revised collar that moves a short distance, with a reason. Third, a row that should be rejected under the mine's validation rules, such as a missing assay value or an impossible depth.
Ask the supplier to transfer the pack into the target system, then show the resulting records. Check the hole identifier, the coordinate values after transformation, the units, the timestamps and the status. Check that the revision is linked to the original and that the rejected row is returned with a reason. Export the accepted records and compare them with the source.
Repeat the transfer with one field changed and one record repeated. A traceable transfer can be explained line by line. An untraceable one produces a file that looks right and cannot be audited.
Evidence to request before accepting the workflow
Ask for documents the mine can keep, with dates and named owners.
- Interface documentation that names supported objects, formats, direction and versions.
- A compatibility statement for the systems and versions in use, with a date.
- The permission model: which roles can read, write, approve or reverse a record.
- Offline and synchronisation behaviour, including how conflicts are resolved.
- Error handling: rejection codes, return paths and retry behaviour.
- A test log from the sample transfer, with timestamps and the records produced.
- Support ownership: who fixes an interface fault, the response time, and the change notice for updates.
- Data export and exit terms, including formats and retention.
Then re-run the sample transfer after any version change. Treat the handover as an ongoing workflow, and every change to a system at either end as a reason to check that the three handovers still work.
Sources: MSR exploration-drilling and database-management listing descriptions supplied on 10 November 2026 (24 and 15 listings, vendor-written and truncated in the source data). International Mining, "What's new and what's hot at IMARC 2026", 9 October 2026, quoting acQuire (read 10 November 2026). Product names link to their MSR profiles. Listing descriptions and the quoted integration are vendor claims. MSR has not tested these systems or the transfer described.
This article is general guidance, not engineering, procurement or geological advice. Test any data transfer with your own records, systems and validation rules, with your own geologists, database managers and drilling supervisors.
Related Categories
Explore the software categories referenced in this article.
Related Buying Guides
Our guides to what to check before you shortlist software in these categories.