VERIFY. DIAGNOSE. EXPLAIN.
Monitoring Data Diagnostics & Anomaly Investigation
RAUZ investigates abnormal, conflicting and unexplained monitoring data using QA/QC, cross-source analysis and engineering context to distinguish credible movement from data issues and define the next review action.
Monitoring Data Diagnostics
When the data looks wrong, test the evidence before explaining the movement.
Monitoring data diagnostics is the structured investigation of abnormal, inconsistent or unexplained monitoring records to determine whether a change is credible, whether the measurement chain is reliable, and what engineering or environmental evidence should be checked next.
Start with the record
Check source, timestamp, unit, baseline, instrument identity, continuity, processing history and known configuration changes before interpreting the physical behaviour.
Compare independent evidence
Test whether neighbouring instruments, survey, groundwater, environmental records, construction events or InSAR-derived movement support the same explanation.
Separate fact from inference
State what is directly observed, what is technically plausible, what remains uncertain and which follow-up action could reduce that uncertainty.
Diagnostic Questions
A useful review begins with a small number of precise questions.
The same graph can imply very different things depending on whether the real issue is sensor behaviour, a baseline change, a genuine ground response, an environmental influence or an incorrect comparison between datasets.
Is the movement real?
Check repeatability, internal consistency, nearby measurements and independent observations before treating an isolated reading as physical movement.
Did the measurement system change?
Look for re-zeroing, instrument replacement, survey-reference changes, calibration or logger configuration changes, unit conversion and revised processing.
Is the rate changing?
Review magnitude together with rate, persistence, acceleration, reversal and the timing of relevant construction, loading, pumping or environmental events.
Do different datasets agree?
Compare compatible evidence while respecting what each instrument measures, its reference system, spatial coverage, sampling interval and uncertainty.
What changed around the asset?
Reconstruct excavation, tunnelling, loading, dewatering, rainfall, groundwater, maintenance, nearby works or operational events that may coincide with the trend.
What should be checked next?
Define the minimum follow-up needed: repeat reading, field inspection, reference survey, calibration check, additional dataset, ground-model review or engineering escalation.
Data & Project Context
The diagnostic record is wider than the sensor spreadsheet.
A defensible interpretation depends on data provenance and project context. RAUZ can begin with a focused dataset, but deeper conclusions may require information about the asset, ground model, groundwater, climate, construction sequence and measurement system.
Monitoring records
Raw and processed readings, timestamps, units, instrument IDs, baselines, calibration information, logger settings, manual notes, alarms, report tables and revision history.
Survey & remote sensing
Total-station observations, levelling, GNSS, reference-control records and InSAR-derived ground-motion information where the geometry, temporal coverage and data quality are suitable for the question.
Environmental evidence
Groundwater, rainfall, temperature, water level, wind or other relevant environmental observations can help test whether the timing and direction of a change are physically plausible.
Engineering context
Ground investigation, stratigraphy, groundwater regime, drawings, monitoring plan, trigger criteria, excavation or tunnelling stages, loading, dewatering, support installation, maintenance and relevant site events.
Diagnostic Workflow
A traceable path from suspicious reading to engineering finding.
The exact sequence is adapted to the project, but the logic should remain reproducible: define the anomaly, verify the data chain, reconstruct the history, analyse the pattern, compare independent evidence, test competing explanations and report the limits of the conclusion.
What changed, where, when and why does it matter?
Source, units, time, instrument, reference and revisions.
Baseline, gaps, re-zero events and processing history.
Magnitude, rate, acceleration, depth and spatial behaviour.
Nearby sensors, survey, InSAR, groundwater and events.
Instrument issue, reference issue or credible physical response?
Evidence, uncertainty, limitations and next action.
- Preserve raw-data provenance and transformation history.
- Keep automated flags separate from engineering conclusions.
- Compare rate of change as well as absolute magnitude.
- Document exclusions, missing records and uncertain baselines.
- Use independent evidence when it can test the same mechanism.
- Escalate only within the project’s approved responsibility framework.
Common Diagnostic Scenarios
The moments when a monitoring report raises more questions than answers.
These are representative diagnostic situations, not claims about a specific RAUZ project. Each case requires its own data, ground model, instrument history and project context.
Sudden inclinometer shift
Unexpected piezometer or groundwater change
Settlement acceleration
Apparent trigger exceedance
Conflicting instruments
Missing, duplicated or irregular records
Cross-Source Evidence
Different instruments answer different parts of the same question.
Data diagnostics should not force every source into a single interpretation. The useful question is whether independent evidence is technically compatible and whether it supports, contradicts or leaves the proposed mechanism unresolved.
| Engineering question | Typical evidence | Diagnostic focus |
|---|---|---|
| Lateral ground movement | Manual or in-place inclinometer, total station, GNSS, deformation points | Depth profile, direction, repeatability, reference stability, nearby points and construction sequence. |
| Groundwater / pore pressure | Vibrating-wire piezometer, standpipe, observation well, pumping and rainfall records | Reference history, adjacent response, recharge/dewatering events, elevation and monitored stratum. |
| Settlement / heave | Levelling, settlement points/plates, extensometers, total station, GNSS | Survey control, spatial coherence, rate, loading, groundwater and reference stability. |
| Structural response | Tiltmeter, crackmeter, strain gauge, load cell, survey | Mounting/reference condition, temperature or operational effects, local-versus-global response and event timing. |
| Wider-area ground motion | InSAR-derived time series and velocity, GNSS, levelling, local instrumentation | Reference frame, line-of-sight geometry, spatial pattern, coherence/quality information and consistency with the ground mechanism. |
| Environmental anomaly | Water level, temperature, salinity, stream flow, wind or other project-relevant sensors | Range checks, continuity, sensor status, regional thresholds, quality flags and independent context. |
Deliverables & Collaboration
The output should make the next technical discussion easier.
A diagnostic engagement can be a focused incident review or a recurring Monitoring Intelligence workflow. The deliverable should match the question and the quality of the evidence supplied.
Diagnostic Review Memo
Issue definition, evidence reviewed, QA/QC findings, observed behaviour, competing explanations, limitations and recommended follow-up.
Reconstructed Trend Package
Traceable plots showing baseline, magnitude, rate, relevant events and related datasets, with processing changes documented.
Trigger Event Review
Focused review of an apparent exceedance, including threshold basis supplied by the project, repeatability, context and escalation questions.
Cross-Source Correlation
Comparison of instruments, survey, environmental records, construction events and InSAR where technically relevant to the same mechanism.
Monitoring QA/QC Findings
Documented data issues involving continuity, units, baselines, timestamps, reference control, metadata or reporting logic.
Recurring Diagnostics
Scheduled review of anomalies, trends, data-quality exceptions and significant changes within a wider Monitoring Intelligence scope.
Scope & Technical Boundaries
Independent interpretation without pretending uncertainty has disappeared.
A diagnostic conclusion is only as strong as the evidence chain. RAUZ can identify data-quality issues, compare evidence and provide engineering interpretation, but missing design information, uncertain reference conditions or damaged instruments remain limitations that must be stated.
What RAUZ can do
Review third-party monitoring records, diagnose anomalies, reconstruct trends, compare independent evidence, assess data confidence, document limitations and structure the next technical question.
What remains project-specific
Formal trigger approval, statutory acceptance, design responsibility, site safety decisions and regulated professional duties remain with the parties appointed under the governing contract and jurisdiction unless expressly included in a separate appointment.
No forced hardware replacement
The client can retain its own instrumentation supplier, survey team, logger, monitoring platform and local field contractor. RAUZ can be engaged specifically for the interpretation and assurance layer.
No universal geology or climate assumption
RAUZ does not infer site stratigraphy, groundwater, weather exposure or movement mechanism from a country name alone. The project location informs the questions; project evidence supports the conclusion.
Official Technical Sources
Public sources used to frame the diagnostic approach.
These references are official government or public-program publications. They provide technical context only and do not imply partnership, endorsement or a commercial relationship with RAUZ.
Data Management for Subsurface Investigations and Performance Monitoring Instrumentation
ER 1110-1-8178 establishes policy and standardized procedures for consistent reporting, storage and management of geotechnical, geological and performance-monitoring instrumentation data.
Soils and Foundations — Reference Manual
FHWA NHI-06-088 provides official geotechnical context for instrumentation including piezometers, settlement devices and slope inclinometers, and stresses the need to apply engineering judgement using local conditions.
QARTOD Real-Time Data Quality Control
QARTOD publishes authoritative QA/QC procedures and data-quality flagging guidance for environmental observations, illustrating how automated quality tests can be standardized while suspect data still require controlled review.
European Ground Motion Service Product Description
EGMS documentation describes Basic, Calibrated and Ortho InSAR products and associated quality-control documentation, providing an official reference for interpreting satellite-derived ground-motion information within its product limits.
Frequently Asked Questions
Questions to settle before an abnormal reading becomes a project conclusion.
What is monitoring data diagnostics?
Can RAUZ analyse data from an existing contractor or platform?
Can RAUZ automatically detect anomalies?
Can InSAR be used in a diagnostic review?
What should I send for a first review?
Does RAUZ replace the project designer, Engineer of Record or statutory reviewer?
Start With The Evidence
Have a monitoring trend that does not make technical sense?
Send a representative monitoring report, sample dataset, trigger table or short project brief. RAUZ can first define the diagnostic question, identify the minimum evidence needed and advise whether the issue is best handled as a focused Data Diagnostic, an Independent Monitoring Review or recurring Monitoring Intelligence.