When two orientation lines do not match in the core tray, the structural geologist's question is always the same: which one do I trust?
SmartCore™ answers that question with data, not judgment. Each measurement is logged together with the signals needed to judge its reliability, and that judgment travels with the data all the way to the report.
This page explains, in plain language, what the instrument checks and when. It is written for anyone receiving the instrument for the first time.
The tool takes measurements inside the borehole and stores them in its internal memory. The application timestamps the moment, links it to depth, and downloads the data once the run is complete. That is why some checks happen before going downhole, others at the moment of the reading, and others when the data is retrieved at surface.
Nothing starts if the instrument is not in working condition or if the borehole information is missing. It is the only phase in which the operator can correct everything at no cost.
While it takes the reading, the sensor records the conditions under which it was taken. Afterward, at surface, the application guides the marking step by step.
When the memory is retrieved, the signals collected are resolved into a verdict for each measurement. That verdict is what the geologist reads afterward.
They are collected automatically during the orientation workflow and appear grouped together in the measurement list and in the reports. The geologist does not need to interpret raw signals: they read a field and know what happened.
Detects whether the drill string was vibrating or the barrel was still rotating when the orientation was taken. A reading taken while in motion is not representative of the core's true position, no matter how well it is marked afterward.
The sensor does not infer this from a single indicator: it cross-checks the stillness detected against the magnitude of the measured gravitational field. A magnitude outside the expected range reveals motion or a sensor anomaly, even when the stillness reading appears correct.
In addition to the orientation, the sensor determines the inclination at that same moment. The closer the borehole gets to vertical, the less well defined the bottom of the core becomes: the gravitational reference loses resolution, and the angular error increases sharply.
Captures the errors that can occur between the reading and the drawing of the line. The application guides rotation of the core with continuous feedback: vibration starts at ±45° and intensifies as it gets closer, and the screen changes once it enters the tolerance of ±5°, which is configurable.
If the tube has moved, if the core was loose or displaced, or if the core tray is tilted too much for the sensor reading to be reliable, the operator declares it before closing out. There is no default value: grading is a mandatory choice.
A single field that reflects the most severe result among the three flags above. It is the field used to sort and filter when a full run needs to be reviewed, and the one that determines whether the measurement enters the report without human intervention. It remains blank when orientation was skipped.
Along with the indicators, each measurement carries the specific reason for what happened. It is not a code: it is a sentence that the geologist can read months later and understand without having to ask anyone.
It also includes any steps that were skipped. Knowing that a step was skipped is just as informative as knowing that something failed.
Grading the measurement is the end of the process, not the beginning. Most of the data lost in a drilling program is not lost because of a sensor: it is lost because of a poorly written header, a wrongly assumed unit, or a questionable measurement that nobody flagged. These layers address that gap.
Each field is checked with every keystroke, not just when saving. Coordinates are verified against their real-world range, the bottom depth must be greater than the starting depth, and a field in error is never saved: the last valid value is kept.
The application never provides a position without stating where it comes from: satellite with satellite count, network, cloud, or the last saved borehole. If the position is old, it is flagged as such and the user is prompted to verify it.
All of it is recorded in the report header.
A list of common situations for routine cases, and free text of up to 150 characters for anything that does not fit. It can be corrected afterward from the measurement list.
Whatever does not pass the control is excluded from the report by default, but nothing is deleted. A No Pass measurement can be explicitly reinstated, and that decision is recorded together with the original reason.
PDF, Excel, and CSV are generated on the device itself, with or without network coverage. The quality columns travel in all three formats; Excel and CSV also add the comment and the grading of the mark.
The SPT API makes it possible to securely connect SmartCloud™ data with the platforms already in use. It integrates, synchronizes, and delivers information wherever it is needed.
Each measurement brings together the data recorded by the instrument, the quality control result, and the information provided by the operator. These fields make it possible to quickly check the status of each record before generating the report.
A No Pass does not mean the data is useless. It means that exactly what failed is known and, therefore, how much confidence it can be used with. It is the opposite of a silent data point.

A detailed record for each run (what was measured, under what conditions, who marked it, and what they observed) is what turns an orientation dataset into a useful historical reference when the project comes back to the table.