MONITOR. VERIFY. INTERPRET. APPLY.
Environmental & Engineering Monitoring Technical Guides
RAUZ Technical Guides explain monitoring instruments, data QA/QC, InSAR, environmental and ground behaviour, and engineer-reviewed interpretation across infrastructure, natural systems and agriculture.
Technical Guides
A practical reference library for people who need to understand monitoring evidence.
RAUZ Technical Guides are built around real monitoring questions rather than equipment catalogues. The library connects measurement principles, field context, data quality, remote sensing, engineering interpretation and operational decisions across ground, infrastructure, environmental and agricultural monitoring.
To help readers move from “what was measured?” to “what can the evidence actually support?” Each guide should explain the measurement question, the evidence needed, common failure modes, interpretation limits and the next check that would materially improve confidence.
Define the physical, environmental or operational question before selecting data.
Choose the instrument, survey, field record or remote-sensing product that can provide relevant evidence.
Check identity, reference, continuity, baseline, units, timing and physical plausibility.
Compare trend, rate, spatial pattern and independent evidence in the real project context.
State what is supported, what remains uncertain and what should be checked or acted on next.
This is a knowledge hub, not a project specification. Site geology, groundwater, climate, trigger levels, regulatory limits, crop conditions and asset tolerances should only be stated when supported by authoritative project records or official public information.
Guide Map
Four monitoring domains. One evidence discipline.
The physical systems differ, but the review logic is shared: define the question, select an appropriate observation, establish the reference or baseline, test data quality, interpret change in context and make uncertainty visible.
Movement, pressure and asset response
Excavations, tunnels, rail, roads, bridges, buildings, slopes, dams, levees, mines and other assets where ground or structural behaviour matters.
Water, weather, air, noise and soil
Environmental observations used to understand changing site conditions, construction effects, natural processes or long-term asset context.
Soil, water and growing conditions
Soil moisture, soil temperature, rainfall, weather and field observations used to understand agricultural environments and seasonal change.
Connect observations across scales
QA/QC, time series, rates, alerts, InSAR, spatial context, data integration, automated reporting and engineer-reviewed analytics.
A useful guide should explain not only what an instrument measures, but what can make the reading misleading.
Start by Question
Choose the guide from the decision you need to make.
Search behaviour is often question-led. RAUZ therefore organises technical content around the engineering or environmental problem first, then connects that question to suitable evidence, QA/QC and interpretation.
| Question | Typical evidence | Guide path | Common mistake |
|---|---|---|---|
| Is the ground or asset moving? | Survey, inclinometers, settlement, GNSS, tilt, crack monitoring, InSAR | Ground & Infrastructure → QA/QC → movement interpretation | Treating one isolated change as a confirmed physical mechanism |
| Is groundwater or pore pressure changing? | Piezometers, standpipes, rainfall, pumping records, construction events | Groundwater → baseline → response time → cross-source review | Ignoring sensor elevation, installation zone, datum or response lag |
| Has an environmental condition changed? | Weather, water, noise, vibration, air or soil observations | Environment → measurement method → temporal context | Comparing records without checking siting, method or averaging period |
| Does an alert represent a real event? | Raw series, metadata, neighbouring sensors, maintenance and site events | Data QA/QC → trigger verification → independent review | Equating an automated alarm with a complete engineering conclusion |
| Can satellite data add context? | InSAR time series, ground control, survey, geology and asset context | Remote Sensing → geometry → ground comparison → limitations | Treating line-of-sight displacement as direct three-dimensional movement |
| Is the field environment changing? | Soil moisture, soil temperature, rainfall, weather and field records | Agriculture → soil & weather → spatial and seasonal interpretation | Using one depth or one sensor location as the whole field condition |
Ground & Infrastructure Guides
Use the instrument that matches the mechanism you need to observe.
Geotechnical and structural monitoring remains a core RAUZ knowledge domain. The guide should explain the measurement principle, installation and reference system, common data problems, interpretation limits and which independent evidence can test the conclusion.
Lateral deformation with depth
Cumulative and incremental profiles, baseline selection, reference stability, casing behaviour, reading repeatability, apparent movement and comparison with construction or groundwater change.
Pore pressure and groundwater
Sensor elevation, installation zone, saturation, datum, response time, rainfall, dewatering or pumping context and correlation with deformation where relevant.
Vertical movement
Levelling, settlement points, extensometers, hydrostatic systems, GNSS and spatial profiles, including benchmark or reference stability and cumulative trend.
Three-dimensional movement
Network geometry, stable references, coordinate systems, line of sight, automation, vector interpretation and the difference between precision and engineering significance.
Local structural response
Mounting, orientation, local versus global response, environmental influences where applicable and comparison with the wider behaviour of the asset.
Event-based monitoring
Sensor location, coupling, event timing, peak and frequency information, source context and the specific project or jurisdictional criterion being applied.
Official engineering principle: FHWA guidance states that instrumentation and monitoring should answer specific critical questions, with the monitoring plan addressing justification, timing, data collection, record keeping and communication of findings. The guide therefore starts from the engineering question rather than the instrument catalogue.
Environmental Monitoring Guides
Environmental data only becomes useful when the measurement context is clear.
Environmental monitoring covers very different variables, time scales and siting requirements. RAUZ guides begin with the environmental question and measurement method, then explain the temporal, spatial and operational context needed before trends are compared.
Weather as context, not decoration
Temperature, humidity, rainfall, wind, pressure and solar observations can support infrastructure, natural-hazard and agricultural review. Siting, exposure, averaging period and continuity matter.
Hydrological context
Water level, pore pressure, rainfall and selected water-quality observations can be reviewed together when the technical question involves seepage, dewatering, recharge, flooding or environmental change.
Event, duration and criterion
A guide should distinguish the physical quantity measured, monitoring interval, equipment setting, source context and the specific project or regulatory criterion that actually applies.
Method and meteorology matter
Parameter, instrument method, location, wind conditions and averaging period all affect interpretation. RAUZ should not publish a universal limit when the governing jurisdiction or project basis has not been defined.
Spatial variability is part of the result
Soil moisture, temperature and site-specific land observations depend on depth, local drainage, soil variability and the objective of the monitoring programme.
Connect environmental systems
WMO’s WIGOS framework integrates diverse weather, water, climate and environmental observing systems around fit-for-purpose observations. RAUZ applies the same evidence discipline at project and asset scale.
Official WMO WIGOS ↗Agricultural Monitoring Guides
Monitor the growing environment as a system, not as one soil-moisture number.
Agricultural monitoring is a natural extension of environmental observation. Soil, water and weather records can be combined to describe changing field conditions, while final agronomic decisions remain crop-, soil-, irrigation- and site-specific.
Soil moisture & temperature
Depth, rooting zone, soil variability, sensor placement and seasonal context affect what any single reading can represent.
Irrigation monitoring
Soil moisture and field observations can support irrigation review, but a technical guide should state the crop, soil, irrigation method and management objective before interpreting the data.
Weather & microclimate
Rainfall, air temperature, humidity, solar radiation, wind and other meteorological variables can help explain changing field conditions and seasonal patterns.
Official example: USDA NRCS’s Soil Climate Analysis Network monitors soil moisture at several depths together with air temperature, relative humidity, solar radiation, wind, precipitation and barometric pressure. It is a useful example of why field interpretation benefits from multiple environmental variables rather than one sensor alone.
Data & Remote Sensing Guides
Before interpreting a trend, establish whether the data is complete, traceable and physically plausible.
More sensors and dashboards do not remove the need for data discipline. RAUZ guides treat QA/QC, monitoring analytics, InSAR and reporting as parts of the same evidence chain.
- Instrument identity, location, orientation and units are explicit.
- Raw, corrected and transformed data remain distinguishable.
- Missing periods and communications outages are visible.
- Baseline, re-zeroing and reference changes are documented.
- Calibration, maintenance and replacement history is retained where available.
- Timestamp and time-zone consistency is checked.
- Rate calculations state the window and method.
- Outliers, spikes, flat-lines and step changes are reviewed.
- Cross-sensor or independent-method checks are used where available.
- Construction, weather or operational events remain linked to the record.
Ground motion across wider areas
Repeat-pass radar can add spatial and historical deformation evidence, but viewing geometry, reference system, temporal coverage, coherence and comparison with ground observations remain essential.
Copernicus EGMS ↗Trend, rate and anomaly tools
Analytics can organise large monitoring datasets and flag changes worth reviewing. Detection alone does not establish mechanism, credibility or engineering significance.
RAUZ Monitoring Analytics →Automate repeatable preparation
Charts, completeness checks, rates and recurring tables can be automated while keeping interpretation, uncertainty and consequential conclusions under technical review.
RAUZ Automated Reporting →Useful caution from an official monitoring programme: USGS notes that telemetered landslide-monitoring data can be provisional and may contain inaccuracies due to instrument malfunction or physical changes at the measurement site. The broader lesson is important: real-time availability is not the same thing as final technical validation.
Regional Technical Context
Global guide structure. Local evidence before local conclusions.
RAUZ is based in Tbilisi and structured for international delivery. The same monitoring principle can be used across regions, but geology, climate, regulation, project practice and environmental context must come from authoritative sources for the actual location.
Build the strongest local evidence base first.
For Georgia, Armenia and Azerbaijan, named-project guides should use official geological, meteorological, environmental, infrastructure-owner and project records before making statements about ground, water or climate.
Use European public data where it fits the question.
Copernicus products such as the European Ground Motion Service can add regional deformation context. Project-level interpretation still requires asset, ground and local monitoring information.
Keep UK guidance and project requirements distinct from EU material.
Use the relevant UK public authorities, geological and meteorological sources, asset-owner requirements and project documents rather than assuming that European material automatically governs the project.
Climate and groundwater context can materially change interpretation.
Country pages and project guides should rely on the responsible national authorities, client records and project investigations for geology, groundwater, temperature, rainfall, dust or environmental criteria.
Avoid continent-wide assumptions.
Geology, rainfall regime, data availability and infrastructure conditions vary substantially. RAUZ should create country or project guides only where authoritative local evidence can support distinct technical content.
Local field evidence can stay local.
RAUZ can work above local monitoring, survey, environmental or remote-sensing delivery teams, adding data assurance and interpretation without claiming that central review replaces jurisdiction-specific professional roles.
SEO rule for regional guides: a country name is not enough to justify a new page. A regional or national guide should add distinct geology, climate, asset, regulatory, monitoring or public-data context that cannot be obtained by simply replacing the location name in a template.
Project-Specific Technical Guides
A named-project guide becomes more specific only as the evidence becomes more specific.
RAUZ can publish project-specific technical discussions for client education and search visibility, but factual statements should come from authoritative public information or client-approved records. Location alone is not evidence of geology, groundwater, climate or asset tolerance.
| Topic | Preferred evidence | A guide can discuss | Do not invent |
|---|---|---|---|
| Geology & stratigraphy | Government geological surveys, project GI, official EIA, tender or design documents | Likely mechanisms, groundwater implications, instrument depth or location considerations | Unpublished strata, unverified cavities, faults or soil properties |
| Climate & weather | National meteorological service, WMO-linked sources, project environmental records | Rainfall, temperature or weather context relevant to monitoring design and interpretation | Site microclimate or event values not supported by records |
| Groundwater & water | Project piezometric data, official hydrogeological reports, environmental monitoring | Monitoring needs, response time, seepage, dewatering or recharge context | Unverified levels, gradients or causal claims |
| Construction / operations | Owner publications, tender documents, approved client information | Baseline timing, monitoring zones, likely instrument combinations and review cadence | Unpublished sequence, temporary works or operating assumptions |
| Agricultural conditions | Official soil maps, agricultural agencies, weather records, client field observations | Monitoring variables, spatial sampling, soil-moisture and weather review logic | Crop response or irrigation prescription without an agronomic basis |
| Governance & triggers | Contracts, statutory guidance, owner requirements, approved monitoring plans | Reporting routes, trigger verification, data ownership and local professional interfaces | Legal responsibility or universal trigger values without governing documents |
Official Reference Library
Technical guides should point readers back to primary sources.
The sources below illustrate the type of evidence RAUZ uses to frame technical discussions. They are official public-agency or industry-standard resources. They are not RAUZ standards and do not imply project involvement, partnership or endorsement.
FHWA — Geotechnical Instrumentation & Monitoring
FHWA guidance links instrumentation to specific engineering questions, monitoring plans, data collection, record keeping and communication of interpreted findings.
Official FHWA source ↗USGS — Landslide Monitoring
USGS monitoring resources illustrate the combined use of ground movement, rainfall, soil-water and groundwater observations, and explicitly caution users about the provisional nature of some real-time data.
Official USGS source ↗USACE — EM 1110-2-1908
USACE’s Engineer Manual provides guidance for instrumentation, monitoring and performance assessment of embankment dams and levees.
Official USACE manuals ↗Copernicus — European Ground Motion Service
EGMS provides pan-European ground-motion products derived from Sentinel-1 and publishes product documentation, specifications, validation and quality-control material.
Official Copernicus EGMS ↗WMO — WIGOS
WMO’s Integrated Global Observing System provides a framework and guidance for weather, water, climate and related environmental observations across diverse observing systems.
Official WMO source ↗USDA NRCS — Soil Climate Analysis Network
SCAN combines soil-moisture measurements at several depths with meteorological observations to support natural-resource assessment and conservation activities.
Official USDA NRCS source ↗Global Industry Standard on Tailings Management
The Standard covers the tailings-facility lifecycle and integrates environmental, technical, governance, management and monitoring considerations.
Official GISTM resources ↗RAUZ Editorial & Engineering Method
The standard for a useful guide is whether the reader can use it without being misled.
The library is intended for asset owners, consultants, contractors, monitoring specialists, environmental teams, researchers and agricultural operators who need a technically defensible starting point before project-specific work begins.
- Start with a real technical or operational question.
- Prefer official primary sources and project-controlled records.
- Separate measured fact from interpretation and recommendation.
- State assumptions, uncertainty and evidence gaps explicitly.
- Explain instrument limitations, not only advantages.
- Do not invent geology, climate, limits or trigger values.
- Distinguish provider case studies from independent evidence.
- Use project-specific information only when it is supportable.
- Explain what additional evidence would materially improve confidence.
- Keep statutory and professional responsibility explicit.
- Update a guide when governing guidance or technical evidence materially changes.
- Keep AI-assisted outputs reviewable and traceable.
Boundary: RAUZ Technical Guides are educational and technical reference material. They do not replace a project-specific monitoring design, statutory approval, Engineer-of-Record decision, environmental permit, agronomic prescription or formally appointed professional service.
Frequently Asked Questions
How to use the RAUZ Technical Guides.
Are RAUZ Technical Guides project specifications?
Why do the guides cover ground, environmental and agricultural monitoring?
Can a guide recommend a specific instrument?
Will RAUZ publish named-project technical discussions?
Can manufacturer information be used as a source?
Can a Technical Guide replace independent technical review?
Is RAUZ limited to Europe or the Caucasus?
How are AI-assisted technical guides controlled?
Suggest a Technical Question
Have a monitoring question that deserves a deeper guide?
Send RAUZ the question, asset or environmental system, monitoring method, available evidence and the decision the monitoring needs to support. Where the topic can be discussed from reliable public or client-approved information, it can form the basis of a technical review or future guide.
Start with the decision problem.
Examples include an unexpected inclinometer profile, conflicting settlement data, a piezometric response that does not match construction events, an InSAR pattern that needs ground comparison or an environmental series that is difficult to interpret.
Show what the guide can rely on.
Official public records, project-approved information, representative monitoring data, instrument documentation, applicable criteria and a clear statement of what remains uncertain make the technical discussion more useful.