EVIDENCE. CONTEXT. ENGINEERING JUDGMENT.
Environmental & Engineering Monitoring Approach
RAUZ connects monitoring, survey, environmental and InSAR evidence through QA/QC, cross-source analysis and engineer-reviewed interpretation, turning observations into traceable intelligence for better decisions.
Engineering Approach
Start with the decision. Build the evidence around it.
RAUZ treats monitoring as an evidence-and-decision process rather than a stream of readings. The first question is what the owner, consultant, contractor or asset team needs to understand. The next is what evidence can answer that question reliably. Measurement, data quality, project context, analysis and professional review are then connected in a traceable chain.
Principles
Eight rules keep the monitoring chain technically useful.
The method is deliberately conservative. A polished dashboard is not a substitute for reliable evidence, and an automatic alert is not the same as an engineering conclusion.
Question before sensor
Choose measurements because they answer a defined question, not because a device happens to be available.
Context before causation
Interpret change against the verified ground, asset, environmental and construction context before assigning a mechanism.
Quality before interpretation
Check baseline, units, timestamps, continuity, metadata, references and obvious anomalies before analysing the trend.
Trend before isolated value
Magnitude matters, but so do rate, acceleration, persistence, seasonality and the behaviour of neighbouring evidence.
Multiple evidence where possible
Survey, instruments, groundwater, environmental data, project events and InSAR can answer different parts of the same question.
Observation separate from inference
Reports distinguish what was measured, what was calculated, what is interpreted and what remains uncertain.
Automation supports review
Automation can screen, compare, chart and report. Consequential interpretation remains subject to engineering review.
Traceability to the next action
A useful output explains the evidence, the limitation and the technical follow-up rather than ending with a colour-coded alarm.
Project Context
The site controls the interpretation. RAUZ does not invent the site.
For a named project, RAUZ builds the technical discussion from controlled project information and official public sources. Geology, stratigraphy, groundwater, climate, construction sequence and environmental constraints are treated as project inputs, not assumptions copied from a generic regional summary.
| Context | Preferred evidence | Why it can change the monitoring approach |
|---|---|---|
| Geology & stratigraphy | Ground investigation, geological survey, boreholes, interpreted ground model, official EIA or owner records. | Controls plausible mechanisms, instrument depth, reference zones, deformation pattern and how a trend should be interpreted. |
| Groundwater & hydrogeology | Piezometric records, standpipes, GI, hydrogeological studies, dewatering records and official water information. | Pressure and water-level change may affect settlement, stability, seepage and the timing of observed movement. |
| Climate & environment | Official meteorological records, rainfall, temperature, river/tide level, environmental monitoring and project observations where relevant. | Seasonality, rainfall, temperature, flooding, heat, dust or other environmental conditions may influence both the physical system and measurement reliability. |
| Construction & operations | Approved programme, excavation/tunnelling stage, loading, dewatering, piling, blasting, traffic or operating events. | Provides the timeline needed to test whether a change is consistent with project activity rather than coincidental in time. |
| Asset & surroundings | Drawings, geometry, utilities, adjacent structures, sensitive receptors, access and operational constraints. | Defines consequence, coverage, reference stability, access, telemetry, monitoring frequency and escalation needs. |
Evidence Hierarchy
Not every data source answers the same question or carries the same weight.
RAUZ combines sources where they are technically complementary, while keeping provenance visible. The objective is not to make every dataset agree. It is to understand why they agree, why they differ and which evidence is appropriate for the decision.
Measurement Strategy
Choose the parameter first. Then choose the instrument.
Monitoring design should begin with the behaviour that needs to be observed, the accuracy and response time required, the physical mechanism, installation constraints and the decision that will follow. The table below is an engineering discussion guide, not a project specification.
| Question | Possible measurement methods | What the method contributes | What still needs context |
|---|---|---|---|
| Lateral ground movement | Manual or in-place inclinometers, extensometers, survey; InSAR for suitable surface movement. | Magnitude, profile, depth-related deformation or wider surface pattern depending on method. | Ground model, shear mechanism, reference stability, construction stage and rate. |
| Settlement / heave | Levelling, settlement points, hydraulic settlement systems, total station, GNSS, InSAR where suitable. | Vertical or 3D movement at selected points or over a wider spatial area. | Datum/reference control, consolidation, loading, groundwater and asset tolerance. |
| Groundwater / pore pressure | Standpipes, vibrating-wire piezometers, water-level sensors. | Water level or pore-pressure response over time. | Hydrogeology, installation response zone, dewatering, rainfall and tidal/river influence where relevant. |
| Structural response | Tiltmeters, crackmeters, strain gauges, load cells, total pressure cells, survey/GNSS. | Rotation, crack opening, strain, force, pressure or displacement. | Structural mechanism, temperature effects, support conditions and load path. |
| Construction / environmental effects | Vibration, noise, weather, water level/quality, air or other project-specific environmental sensors. | Records external conditions or impact parameters that may correlate with project activity. | Applicable limits, receptor sensitivity, local requirements, calibration and causal interpretation. |
Data Trust
Interpretation starts only after the data survives basic scrutiny.
RAUZ uses QA/QC as an engineering control, not a cosmetic spreadsheet check. A suspicious trend may be real, but it may also arise from a baseline change, a reference movement, a timestamp problem, a unit mismatch, sensor drift, missing metadata or a processing step.
- Instrument identity, location and measured parameter are confirmed.
- Units, sign convention, coordinate/reference system and timestamps are consistent.
- Baseline or zero is traceable and changes to it are recorded.
- Completeness, gaps, duplicates, flat-lines and resets are screened.
- Calibration/check status and known instrument events are considered where available.
- Reference points and neighbouring instruments are reviewed for common-mode behaviour.
- Outliers are investigated before being deleted, corrected or accepted.
- Raw, processed and interpreted values remain distinguishable in the review trail.
Analysis & Interpretation
Magnitude is only one part of behaviour.
RAUZ reviews time, rate, spatial pattern and relationships between evidence before deciding whether a change deserves technical attention. The analytical depth depends on data quality, sampling frequency, project stage and the decision being supported.
Trend, rate & acceleration
Review whether movement is stable, persistent, accelerating, episodic or seasonal rather than relying only on the latest value.
Neighbouring & spatial behaviour
Check whether adjacent instruments, structures or wider ground-motion patterns support an isolated observation.
Correlation without forcing causation
Compare movement, groundwater, weather, survey, InSAR and project events while keeping coincident timing separate from proven cause.
Anomaly investigation
Separate potential physical change from instrument, reference, baseline, communication or processing issues using the available evidence.
Mechanism-led interpretation
Test whether the observed pattern is technically compatible with the documented ground, asset and construction mechanism.
State uncertainty explicitly
Identify what is supported, what is inferred, what is missing and what additional evidence would materially improve the conclusion.
Automation is useful when the reasoning stays visible.
RAUZ uses operational analytics, AI-assisted review and automated reporting to reduce repetitive work. The output remains reviewable: source data, checks, calculations, interpretation, limitations and consequential conclusions should not collapse into a black-box score.
Remote Sensing & InSAR
Extend the field of view without pretending satellite data answers every local question.
InSAR can provide a wider spatial and historical view of surface deformation where suitable radar targets and data quality are available. RAUZ uses it as an additional evidence layer, not as an automatic replacement for subsurface instruments, pore-pressure measurements or high-frequency local survey.
Historical and wide-area context
Look for pre-existing or distributed ground-motion patterns that may sit outside a conventional point-monitoring network.
Ground evidence + satellite evidence
Compare InSAR time series and spatial patterns with survey, GNSS, settlement, inclinometer, groundwater or project events where technically meaningful.
Geometry, cadence and coherence matter
Interpret line-of-sight geometry, point quality, temporal cadence, surface conditions and product reference before assigning engineering significance.
Decision & Governance
A trigger is a rule for attention. It is not the whole engineering conclusion.
Thresholds, alerts and escalation routes are useful only when the data behind them is credible and the response responsibility is clear. RAUZ separates automated detection from engineering interpretation and records what the evidence supports at the time of review.
Before a trigger
Define the parameter, baseline, threshold basis, frequency, data-quality rule, decision owner and response path before the monitoring system starts producing alarms.
At an apparent exceedance
Confirm the reading, baseline, reference, nearby evidence and relevant project event before escalating a single number as physical behaviour.
Independent review
Where required, RAUZ can review monitoring plans, contractor reports, anomaly handling, trigger logic and the technical basis of reported conclusions without replacing the local field team.
Engineer-reviewed reporting
Outputs separate observation, analysis, interpretation, uncertainty and recommended follow-up so the decision trail can be reconstructed later.
| Typical engagement | What RAUZ reviews | Typical output |
|---|---|---|
| Focused diagnostic review | Unexpected jump, conflicting sensors, baseline concern, apparent trigger or unexplained change. | QA/QC findings, plots, alternative explanations, evidence gaps and targeted follow-up. |
| Recurring monitoring intelligence | Agreed datasets, trends, rates, trigger events, cross-source behaviour and project context. | Structured recurring review with traceable observations, interpretation and priorities. |
| Monitoring design / assurance | Question, parameter, location, frequency, baseline, trigger, reporting and interface requirements. | Monitoring philosophy, design review, assurance comments or project-specific workflow. |
Official Technical Basis
The method is anchored to primary standards and public technical guidance.
These sources are used as technical context for the approach described on this page. They do not imply certification, endorsement or a project-specific requirement unless the governing project documents say so.
ISO 18674-1:2015
General rules for performance monitoring of ground, structures interacting with the ground, geotechnical fills and geotechnical works, including monitoring-system requirements, data processing, verification and reporting.
Official ISO source ↗Geotechnical instrumentation & monitoring
FHWA guidance describes instrumentation as a tool to characterise site conditions, verify design assumptions, monitor construction effects and provide warning of potential failures.
Official FHWA source ↗Monitoring review & evaluation
U.S. Bureau of Reclamation guidance distinguishes prompt review of new readings from periodic in-depth evaluation and stresses understanding why instruments were installed.
Official USBR source ↗ISO 14031:2021
Guidance for the design and use of environmental performance evaluation, relevant to structuring the collection, assessment and communication of environmental information.
Official ISO source ↗SensorThings API
An open, geospatial-enabled standard for managing and retrieving observations and metadata from heterogeneous IoT sensor systems.
Official OGC source ↗Ground motion & InSAR
Copernicus EGMS and ESA provide primary public documentation on Sentinel-1 radar interferometry, ground-motion products, measurement geometry, quality information and wide-area deformation monitoring.
Copernicus EGMS ↗ESA Sentinel-1 ↗Standards and guidance should be checked against the edition, jurisdiction, client specification and contract applicable to the actual project. This page is a general engineering-method statement, not a substitute for project-specific design criteria or statutory requirements.
FAQs
Engineering approach questions.
Does RAUZ require a project to replace its monitoring system?
How does RAUZ decide which instruments are appropriate?
How are geology, groundwater and climate used in interpretation?
Can one abnormal reading justify an engineering conclusion?
Can InSAR replace ground instrumentation?
Does AI replace engineering judgement in the RAUZ workflow?
What should a client send for a first technical discussion?
Start With the Evidence
Have monitoring evidence that needs a clearer technical interpretation?
Send RAUZ a short project brief, representative dataset or monitoring report and the decision your team is trying to support. The first discussion can define what evidence is usable, what is missing and whether the next step should be diagnostics, recurring review, InSAR interpretation, monitoring design or another specialist input.
What to send
Project location and asset, monitoring objective, instrument register, representative data, trigger table, drawings, project chronology and relevant controlled ground, groundwater or environmental information.
What RAUZ can define
Which datasets are usable, which comparisons are meaningful, the main evidence gaps, suitable review depth and the most practical route to a traceable engineering or environmental conclusion.