QUESTION THE DATA. EXPLAIN THE MOVEMENT.

Geotechnical Monitoring Data Analysis & Diagnostics

GeoSmar investigates abnormal, inconsistent and unexplained monitoring data to distinguish credible movement from data issues, connect trends with engineering context and define the next technical questions.

Discuss Your Project Request a Quote

Monitoring Data Analysis & Diagnostics

When monitoring data looks wrong, the first task is not to explain it. It is to test it.

GeoSmar Data Diagnostics is a focused engineering review service for abnormal, inconsistent or unexplained monitoring records. The objective is to separate credible movement from data issues, reconstruct what changed, compare independent evidence and identify the next technical questions before a project team acts on a misleading trend.

Evidence

Start with the raw record

Review timestamps, units, baselines, instrument identity, missing readings, sudden steps, duplicate values, data conversions and known maintenance or site events before interpreting the movement itself.

Context

Put the trend back into the project

A reading becomes more useful when it can be compared with excavation sequence, groundwater change, loading, dewatering, rainfall, adjacent construction, survey observations or other monitoring points.

Judgement

State what is known and what is not

GeoSmar separates observation from interpretation, records limitations and avoids treating a dashboard alarm, isolated reading or automated comment as a complete engineering conclusion.

This page describes a diagnostic service, not a site-specific design. Instrument choice, trigger criteria and the significance of movement depend on the project ground model, asset type, construction method, monitoring specification and available evidence.
About GeoSmar Read GeoSmar Insights

Diagnostic questions

A useful review begins with a small number of precise questions.

The same dataset can support very different conclusions depending on whether the project is investigating an instrument problem, a construction response, an accelerating trend or a genuine trigger exceedance.

Is the movement real?
Check whether the apparent change is repeatable, internally consistent and supported by nearby or independent measurements. FHWA tunnel guidance specifically notes that excessive movement may require another set of readings to confirm that the change is real rather than a reading error or instrument malfunction.
Did the baseline or measurement system change?
Look for re-zeroing, probe replacement, calibration changes, survey-control changes, logger configuration, unit conversion, maintenance, power interruption or a revised reference point. A step in the dataset may be a measurement-system event rather than a ground event.
Is the rate of change increasing?
Compare magnitude with time. A movement value may be less informative than whether the rate is stable, reducing, increasing or changing after a construction or groundwater event.
Do different instruments tell the same story?
Compare compatible evidence where available: lateral movement with survey, pore pressure with groundwater and pumping records, settlement with levelling or GNSS, local sensors with wider-area ground-motion information, and nearby instruments with the same construction sequence.
What changed in the engineering context?
Review excavation stages, tunnelling advance, support installation, loading, dewatering, rainfall, adjacent works, foundation activity or other documented events that may coincide with the observed change.

Typical scenarios

The service is intended for the moments when a monitoring report raises more questions than answers.

The examples below are common diagnostic situations. They are not claims about any specific GeoSmar project.

Sudden inclinometer shift

A profile moves abruptly between two surveys. Review probe and project records, A/B axis behaviour, repeatability, depth pattern, nearby survey data and whether the change aligns with excavation or slope behaviour.

Unexpected piezometer change

A vibrating-wire piezometer steps or drifts. Review zero history, temperature, barometric or water-level context where relevant, pumping or recharge events, adjacent piezometers and installation details before attributing the change to pore-pressure behaviour.

Settlement acceleration

A settlement trend becomes steeper. Check survey control, baseline continuity, rate of change, construction loading, groundwater, neighbouring points and whether the trend is spatially coherent.

Trigger exceedance

A value crosses an alert level. Confirm the approved threshold, units, sign convention, baseline, current reading, rate and repeatability before deciding whether the exceedance is credible and what response the project procedure requires.

Conflicting datasets

Survey shows movement while local instrumentation appears stable, or vice versa. Review what each instrument actually measures, spatial coverage, reference systems, timing and the possibility that the datasets are observing different mechanisms.

Missing or irregular records

Gaps, repeated values, timestamp changes or inconsistent intervals can distort trend and rate calculations. Reconstruct the data history before applying automated trend logic.

What GeoSmar reviews

The diagnostic record is wider than the sensor spreadsheet.

A good review uses the smallest set of evidence needed to test the engineering question, while preserving where each value came from and how it was processed.

Monitoring records
Raw and processed readings, timestamps, units, instrument IDs, baselines, calibration information, logger settings, manual notes, alarms and report tables.
Project context
Drawings, monitoring plans, approved trigger framework, construction sequence, excavation or tunnelling stages, support installation, loading, dewatering and documented site events.
Ground model
Available borehole information, stratigraphy, fill, soft soil, granular layers, rockhead, groundwater conditions and relevant geotechnical interpretation. GeoSmar does not invent missing ground information; uncertainty is recorded explicitly.
Independent evidence
Survey observations, GNSS, total station, nearby instruments, pumping records, rainfall or environmental data, inspection notes and satellite-derived ground-motion information where suitable and available.
Existing reports
Contractor monitoring reports, consultant comments, previous incident notes and the reasoning already used to explain a change. These are reviewed as evidence, not accepted automatically as the final interpretation.
USACE Engineer Regulation ER 1110-1-8178, issued in 2025, formalises consistent reporting, storage and management of subsurface and performance-monitoring instrumentation data. That emphasis on traceable data management is directly relevant to diagnostic work: interpretation is only as reliable as the record being interpreted.

Diagnostic workflow

A repeatable path from suspicious reading to defensible engineering finding.

The exact sequence depends on the project, but a diagnostic review generally moves through the following checks before a conclusion is written.

1. DefineState the question and the claimed anomaly.
2. VerifyConfirm source, units, timestamps and instrument identity.
3. RebuildCheck baseline, continuity and processing history.
4. AnalysePlot trend, magnitude, rate and depth or spatial pattern.
5. CorrelateCompare construction, groundwater and related data.
6. TestConsider competing explanations and repeatability.
7. ReportState finding, limitations and next review action.

What the workflow avoids

It avoids starting with a preferred explanation, reading a single alarm in isolation, or using automation to generate certainty that the available evidence does not support.

What the workflow preserves

It preserves data provenance, project context, alternative explanations, uncertainty and a clear separation between measured fact and engineering interpretation.

Instrumentation context

Different instruments answer different parts of the movement question.

Instrument selection should follow the mechanism that needs to be observed. The table below is a diagnostic map, not a project-specific instrumentation design.

Engineering question Typical data sources Diagnostic checks
Where is lateral ground movement occurring? Manual inclinometer, in-place inclinometer, survey, total station, GNSS Depth profile, repeatability, reference stability, direction, nearby points, construction sequence
Is groundwater or pore pressure changing? Vibrating-wire piezometer, standpipe, water-level gauge, pumping records, rainfall Zero history, temperature, adjacent sensors, recharge/dewatering events, elevation reference
Is the ground or asset settling? Settlement points, settlement plates, levelling, extensometers, total station, GNSS Survey control, baseline, spatial consistency, rate of change, loading, groundwater
Is a structure tilting or opening at a joint? Tiltmeters, crackmeters, survey targets, displacement transducers Temperature, local versus global movement, mounting condition, adjacent observations
Are load or strain changes credible? Load cells, strain gauges, pressure cells, structural monitoring records Calibration, loading sequence, temperature, expected load path, correlated deformation
Is movement part of a wider spatial pattern? Survey networks, GNSS, InSAR-derived ground-motion data, distributed monitoring Spatial extent, reference frame, line-of-sight or method limitations, ground-truth comparison
Inclinometers Piezometers Settlement Tilt Crack GNSS Total Station Load & Strain Vibration InSAR
Why can inclinometer data require diagnostic review?
FHWA describes inclinometers as instruments for subsurface lateral deformation. Manufacturer guidance from GEOKON also documents probe zero-shift, calibration checks and the importance of paired readings. A diagnostic review therefore considers both the apparent ground profile and the measurement system that produced it.
Why can piezometer temperature matter?
GEOKON’s official vibrating-wire piezometer manual notes that its sensors can have a temperature coefficient and provides a correction method when installation conditions are not thermally stable. Temperature is therefore one possible check when a pressure trend is difficult to explain.

Official public cases

Real monitoring programmes show why interpretation needs more than one line on a chart.

The examples below are drawn only from official U.S. Federal Highway Administration publications. They are not GeoSmar projects and are included as technical reference cases.

Central Artery/Tunnel programme — pile driving beside an existing building

FHWA’s published case describes subsurface conditions consisting of approximately 3–4.6 m of fill, 3–6.1 m of organic silt and sand, 27.4–33.5 m of soft marine clay, 6.1–12.2 m of glacial silt and sand, with bedrock reported at about 48.8 m depth. During pile-driving works, deformation monitoring points were used on the nearby building; vibrating-wire piezometers, a multipoint heave gauge and an inclinometer were added to examine pore pressure, vertical movement with depth and lateral movement.

Diagnostic lesson: the official case does not reduce performance to one instrument. Surface deformation, pore pressure, vertical ground movement and lateral movement were considered together around a documented construction sequence. That is the type of multi-source reasoning a diagnostic review should preserve.

FHWA official source — Central Artery/Tunnel pile foundation case ↗

St. Lawrence County, New York — five-year bridge performance monitoring

FHWA instrumented a geosynthetic reinforced soil integrated bridge system and monitored it for more than five years. The programme included in-place inclinometers, survey targets, pressure cells and a remote data-acquisition system to assess lateral deformation, earth pressures, vertical movement and differential settlement.

Diagnostic lesson: long-term interpretation benefits from a clear link between the engineering question, instrument layout and measured parameter. The official programme selected sensors around specific performance questions such as deformation, pressure and settlement rather than collecting data without a defined purpose.

FHWA official source — 5-year bridge performance monitoring ↗

FHWA’s road tunnel manual also advises that apparently excessive movement may require repeat readings to confirm that the movement is real and not caused by a reading error or instrument malfunction. This principle is central to GeoSmar Data Diagnostics.

Scope & contract interface

Data diagnostics works best when the technical boundaries are agreed before the review begins.

For a one-off incident review or recurring diagnostic service, the engagement should define the evidence available, the response expected and the decisions that remain with the project’s appointed engineer, designer, asset owner or statutory authority.

Data responsibilityIdentify who supplies raw and processed data, calibration records, survey control, project chronology and revised datasets.
Baseline & revision controlState the approved baseline, instrument replacement history, re-zero events and document revision used for the review.
Trigger frameworkConfirm which project-approved alert, action or alarm criteria apply. GeoSmar should not silently create substitute contractual thresholds during a diagnostic review.
Review frequencyDefine whether the service is a one-off incident review, scheduled weekly/monthly review, or an agreed response to specific events.
Response timeUrgent monitoring events require an explicit service level. A normal engineering review should not be mistaken for continuous emergency monitoring unless that scope is separately agreed.
Decision authorityGeoSmar can provide independent engineering interpretation, but project hold points, statutory acceptance, design responsibility and site safety decisions remain with the parties appointed under the project contract unless expressly agreed otherwise.
Confidentiality & data rightsAgree what project information may be processed, retained, shared or used in anonymised technical work.
Known limitationsMissing ground information, incomplete records, damaged sensors or uncertain baselines should be recorded as limitations rather than filled with assumptions.

Deliverables

The output should make the next engineering discussion easier.

A diagnostic engagement can be scaled from a short incident memo to a recurring monitoring-intelligence workflow. Deliverables are defined to match the question and the quality of the available evidence.

Diagnostic Review Memo

Concise record of the issue, data checked, observations, possible explanations, limitations and recommended follow-up.

Reconstructed Trend Package

Cleaned and traceable plots showing baseline, magnitude, rate, relevant events and related monitoring datasets.

Trigger Event Review

Independent review of an apparent exceedance, including the applicable threshold, repeatability, data context and issues requiring escalation.

Cross-Instrument Correlation

Comparison of related instruments, survey, groundwater, construction and other project records to test whether the observed behaviour is coherent.

Monitoring QA/QC Findings

Identified issues with data continuity, units, baselines, timestamps, configuration, reference control or reporting logic.

Recurring Diagnostics

Scheduled review of exceptions, trends and significant changes as part of a wider GeoSmar Monitoring Intelligence engagement.

Discuss a Diagnostic Review Request a Quote

Why GeoSmar

An independent engineering layer between monitoring data and project decisions.

GeoSmar is the market-facing brand of Rauz Caucasus LLC, based in Tbilisi, Georgia and structured for remote-first international delivery. The Data Diagnostics service is deliberately designed to work with existing project systems rather than requiring GeoSmar to become the local installation contractor.

  • Independent review of third-party monitoring data
  • Vendor-neutral use of existing project systems
  • Geotechnical interpretation rather than dashboard-only reporting
  • Cross-checking between instruments, survey and project events
  • Explicit separation of observation, interpretation and limitation
  • One-off incident review or recurring monitoring intelligence
  • Remote-first delivery across international projects
  • Pathway into monitoring design, independent review and reporting automation

Potential collaboration pathways

One-off incident data review, independent review of a contractor report, recurring monthly diagnostics, monitoring QA/QC framework, trigger-framework review, InSAR-to-ground-data comparison, or an automated reporting pilot.

What GeoSmar does not need to control

The client can continue using its own instrumentation supplier, installation contractor, survey team, logger, platform and local monitoring staff. GeoSmar can be engaged specifically for the interpretation and assurance layer.

How GeoSmar Works Technical Insights

Official references

Public technical sources used to frame this page.

The external sources below are official government or manufacturer publications. They are provided for technical context and do not imply partnership, endorsement or a commercial relationship with GeoSmar.

  • FHWA — Soils and Foundations, NHI Course 132012. Official guidance describing slope inclinometers and other instrumentation used where stability and settlement are critical. Official FHWA PDF ↗
  • FHWA — Technical Manual for Design and Construction of Road Tunnels. Official guidance noting the need to confirm excessive movements where reading error or instrument malfunction may be possible. Official FHWA PDF ↗
  • FHWA — Central Artery/Tunnel driven pile foundation case. Official project publication documenting subsurface conditions and the use of deformation points, vibrating-wire piezometers, a multipoint heave gauge and an inclinometer. Official FHWA case ↗
  • FHWA — St. Lawrence County GRS-IBS 5-year monitoring. Official research project using in-place inclinometers, survey targets, pressure cells and remote data acquisition. Official FHWA case ↗
  • USACE — ER 1110-1-8178, Data Management for Subsurface Investigations and Performance Monitoring Instrumentation. Official 2025 regulation on consistent reporting, storage and management of geotechnical and monitoring instrumentation data. USACE official publications ↗
  • Trimble — Monitoring and T4D Control. Official product information on bringing total-station, GNSS and geotechnical sensor measurements together for movement monitoring and analysis. Trimble official monitoring page ↗
  • GEOKON — Digital Inclinometer System. Official manual covering zero shift, self-calibration checks, data backup and probe configuration. GEOKON official manual ↗
  • GEOKON — 4500 Series Vibrating Wire Piezometer. Official manual covering zero readings, temperature measurement and temperature correction. GEOKON official manual ↗

Frequently asked questions

Questions clients usually ask before sending a dataset.

Can GeoSmar review data from instruments installed by another company?
Yes, subject to an agreed scope and sufficient records. The GeoSmar model is intended to work with client-owned systems and third-party monitoring data. Raw data, processing history, baselines, project context and relevant instrument records should be provided where available.
Can GeoSmar determine whether a trigger exceedance is false?
GeoSmar can review whether the available evidence supports the apparent exceedance and identify data-quality or measurement issues that may need to be checked. The project’s approved response procedure and decision authority remain important, particularly where safety or statutory obligations apply.
Do you need raw data or is a monitoring report enough?
A report may be enough for an initial review, but raw or minimally processed data is often needed to test baselines, timestamps, missing readings, rate calculations and other diagnostic questions.
Can GeoSmar review inclinometer and piezometer anomalies together?
Yes, where the datasets are relevant to the same engineering question. Cross-instrument review can be useful when movement, groundwater and construction sequence may be related.
Can diagnostics become a recurring service?
Yes. A one-off review can be extended into scheduled Monitoring Intelligence where GeoSmar reviews exceptions, trends, trigger events and significant changes at an agreed frequency.
Does GeoSmar replace the project designer, Engineer of Record or statutory reviewer?
No such replacement should be assumed. GeoSmar provides monitoring analysis and independent engineering interpretation within the agreed scope. Formal design, statutory acceptance, site safety and contractual decision authority remain with the parties appointed for those duties unless a separate engagement expressly states otherwise.

Start with the evidence

Have a monitoring trend that does not make engineering sense?

Send a monitoring report, sample dataset, trigger table or short project brief. GeoSmar can first define the diagnostic question, identify the minimum information needed and advise whether the issue is best handled as a one-off review or a recurring Monitoring Intelligence engagement.

Discuss Your Project Request a Quote

Scroll to Top