EVIDENCE. CONTEXT. ENGINEERING JUDGMENT.
Monitoring Intelligence Cases & Engineering Analyses
Explore RAUZ projects, technical demonstrations and public-source engineering analyses showing how monitoring, survey, environmental and InSAR evidence is checked, connected and interpreted for better decisions.
Cases
Evidence before conclusions.
The RAUZ Cases library shows how monitoring evidence can be checked, connected and interpreted before it is used to support an engineering or environmental decision. It is organised around the quality of the evidence, the physical context and the question being investigated—not around a sensor brand or a dashboard screenshot.
Show the reasoning, not just the result.
A useful case explains the problem, the records reviewed, the checks applied, the competing explanations, the limitations and the final technical takeaway.
Ground, infrastructure and natural systems.
Cases can involve geotechnical, structural, environmental, groundwater, survey, remote-sensing or agricultural evidence where those data streams are relevant to the question.
Above measurement. Before decision.
RAUZ is designed to work with existing monitoring arrangements and add an independent intelligence layer through QA/QC, cross-source analysis, interpretation and engineer-reviewed reporting.
Case Types
Three labels. Three different levels of evidence ownership.
The case type is stated before the technical story begins. This prevents a public project, a demonstration dataset and a commissioned RAUZ engagement from being presented as if they were the same thing.
First-party work delivered by RAUZ.
Used only where RAUZ has actually performed the stated scope. Client identity, project name, data and outcomes are published only where disclosure is permitted; otherwise the case may remain anonymised or unpublished.
RAUZ method demonstrated on clearly labelled data.
Used to show an analytical workflow, platform function or engineering method with public, anonymised or synthetic data. The dataset type and any assumptions are stated so the demonstration is not mistaken for a client project.
Independent analysis of an externally delivered project.
Built only from traceable official public records. The page identifies the original project owner or source and states explicitly that the project was not delivered by RAUZ unless there is separate evidence of RAUZ involvement.
No borrowed experience.
A third-party project may be technically valuable to analyse, but its achievements remain the achievements of the original project team. RAUZ uses public-source analysis to explain monitoring lessons, not to imply project participation.
Evidence
Every case starts with an evidence register.
The same chart can support very different conclusions depending on its baseline, instrument condition, reference system, project stage and physical context. A RAUZ case therefore records what evidence was available before explaining what the evidence may mean.
| Evidence group | Typical records | What the case needs to establish |
|---|---|---|
| Project definition | Asset, location, project stage, drawings, chronology | What is being monitored and which decision the monitoring is intended to support. |
| Ground & environment | Official geology, GI records, groundwater, environmental or meteorological information | Which physical conditions may control behaviour and which assumptions remain unverified. |
| Monitoring metadata | Instrument type, ID, coordinates, elevation, orientation, calibration, installation and baseline | Whether the measurement has a traceable reference and can be compared with the stated trigger or prediction. |
| Time-series data | Raw or processed readings, survey observations, logger exports, environmental data | Whether the change is persistent, rate-dependent, isolated, discontinuous or affected by data-quality issues. |
| Independent evidence | Neighbouring instruments, GNSS, survey, InSAR, inspection or other measurement methods | Whether separate observations support or contradict the same physical interpretation. |
| Project events | Excavation, tunnelling, dewatering, loading, rainfall, maintenance, operational changes | Whether the timing of the observed response is consistent with a plausible mechanism. |
- Data provenance and revision status identified.
- Baseline and reference changes made visible.
- Missing or suspect records separated from accepted data.
- Trigger values linked to their project basis where available.
- Observations separated from engineering interpretation.
- Limitations carried through to the final takeaway.
Project Context
A monitoring case is site-specific even when the method is repeatable.
RAUZ does not infer a project’s geology, groundwater regime, climate exposure or construction sequence from a city or country name. Case-specific interpretation is built from project records and official sources relevant to the actual location.
Environment and climate
Geology, strata and groundwater
Project type and construction sequence
Monitoring instruments and survey evidence
InSAR and remote sensing
Case Themes
Cases are organised around engineering questions.
The strongest case is not the one with the largest dataset. It is the one that makes a difficult monitoring question easier to examine, reproduce and discuss.
Is the apparent movement real?
Baseline shifts, sudden jumps, drift, missing data, inconsistent sensors and apparent exceedances require data-quality checks before a mechanism is assigned.
Does an exceedance support escalation?
A case can examine the threshold basis, measurement credibility, rate of change, neighbouring evidence, project events and the defined response route.
Does the wider ground-motion pattern agree?
Satellite-derived deformation can be compared with survey, groundwater and ground instrumentation when the datasets are technically compatible.
How did the ground respond to the works?
Excavation, tunnelling, dewatering, piling, loading and temporary works are reviewed against the timing and spatial pattern of monitoring change.
Is an environmental driver influencing the record?
Rainfall, temperature, groundwater, river level, seasonal effects or other environmental variables may need to be compared with engineering observations.
Can mixed monitoring systems tell one coherent story?
RAUZ can structure cases around vendor-neutral integration of logger exports, manual readings, survey, environmental sensors, InSAR and project records.
Official-Source Analysis
Public cases must start with primary or official records.
RAUZ uses official project, government, authority, research-agency or programme sources when developing a Public-Source Engineering Analysis. The source remains visible so readers can separate the original record from RAUZ’s later technical interpretation.
Crossrail — Review of Monitoring Methods
The Crossrail Learning Legacy paper compares automated and manual monitoring, discusses measurement error, environmental effects and the need for meaningful monitoring frequencies and thresholds.
Open official Crossrail source ↗ Original project and paper are not RAUZ work.FHWA — Road Tunnel Instrumentation Guidance
The Federal Highway Administration tunnel manual explains the role of geotechnical and structural instrumentation in monitoring construction performance and mitigating problems.
Open official FHWA manual ↗ Used as technical context, not as evidence of RAUZ project participation.Copernicus — European Ground Motion Service
The Copernicus Land Monitoring Service provides harmonised InSAR-based ground-motion products across Europe, with product documentation, datasets and stated quality information.
Open official Copernicus source ↗ InSAR suitability remains project- and dataset-specific.Case Method
A repeatable path from question to technical takeaway.
RAUZ case pages use a consistent review structure so a reader can see how the conclusion was reached and where uncertainty remains.
Challenge → Evidence → Method → Interpretation → Limitation → Outcome.
This structure keeps the technical reasoning visible and prevents the final result from being separated from the quality of the evidence that supports it.
A case can inform a decision without pretending to own every responsibility.
Formal design, statutory approval, Engineer-of-Record duties, emergency response and locally regulated professional roles remain with the parties appointed for those functions unless a specific contract states otherwise.
Regional Coverage
One review discipline. Different regional evidence.
RAUZ’s priority markets are the South Caucasus, European Union, United Kingdom, Middle East and Africa. Case pages use region-specific official information only where it adds real technical context; a country name is never used as a substitute for site investigation or project records.
South Caucasus
Cases may need to connect mountainous terrain, slope processes, transport corridors, hydropower, urban construction, groundwater or environmental evidence using official national and project sources.
European Union
Official geological, environmental and Copernicus ground-motion sources can provide useful regional context where compatible with project-level evidence and professional responsibilities.
United Kingdom
Public infrastructure learning resources and project records can support technical analysis of tunnelling, rail, asset protection, monitoring methods, thresholds and data management.
Middle East
Case interpretation may need to consider groundwater control, urban excavation, tunnelling, major infrastructure, temperature exposure and project-specific ground conditions without importing generic assumptions.
Africa
Project context can vary radically by geology, hydroclimate, infrastructure type and data availability. Country- and site-specific official sources are required before technical conclusions are drawn.
Global remote delivery
RAUZ can review project data remotely while installation, readings, maintenance, emergency response and locally regulated services remain with the appropriate local project parties.
Publication Rules
Trust depends on saying exactly what the case is.
The Cases library is designed to build technical credibility without overstating project ownership, data certainty or commercial outcomes.
- Client and project names appear only where disclosure is permitted.
- Anonymised work is labelled as anonymised; sensitive details are removed.
- Synthetic data is explicitly identified as synthetic demonstration data.
- Public-source analysis links to the official source used.
- Third-party project outcomes are never presented as RAUZ achievements.
- Quantitative claims are included only when supported by a traceable source.
- Observations, interpretation and uncertainty remain separate.
- Material limitations and missing inputs are stated.
- Case dates reflect real publication or substantive updates.
- Related RAUZ services are linked only where technically relevant.
A useful case should be auditable.
A reader should be able to identify the question, the evidence base, the analysis route, the point where engineering judgement was applied and the limits of the conclusion.
FAQs
How to read the RAUZ Cases library.
Are all cases on this website RAUZ projects?
Can RAUZ publish confidential client work?
Can a technical demonstration use synthetic data?
What makes a public-source engineering analysis credible?
Will every case include geology, climate and environmental context?
Can a case combine InSAR with ground monitoring?
Can I ask RAUZ to review a project that is not published here?
Start With the Evidence
Have a monitoring question worth turning into a defensible technical case?
Send RAUZ a concise project brief, representative monitoring information and the decision your team is trying to support. The first discussion can define what evidence is usable, what is missing and whether the issue needs diagnostics, independent review, InSAR interpretation, monitoring strategy or recurring intelligence.
Useful starting material
Project location and asset type, monitoring objective, representative report or dataset, instrument register, trigger table, relevant drawings, construction chronology and official ground or environmental information where available.
What RAUZ can define first
Evidence required, QA/QC depth, cross-source comparisons, technical assumptions, review boundary, deliverable, confidentiality route and the most useful next step.