MEASURE. VERIFY. INTERPRET. DECIDE.
Environmental & Engineering Monitoring Knowledge Base
RAUZ Monitoring Knowledge Base explains how to plan, validate and interpret ground, infrastructure, environmental, agricultural and InSAR evidence through practical, engineer-reviewed guidance.
Monitoring Knowledge Base
Start with the decision. Then work backwards to the evidence.
Monitoring is most useful when every reading is tied to a clear question: what is changing, where, how quickly, under what environmental or project conditions, and what evidence would confirm or challenge the interpretation. This knowledge base brings ground, infrastructure, environmental, agricultural and remote-sensing observations into one practical framework.
Start by Question
The instrument comes after the question.
The same sensor can be useful in one project and unhelpful in another. Before selecting a device or interpreting a chart, define the behaviour that matters, the scale of change that would be meaningful, the response time required and the independent evidence available for confirmation.
| Question | Evidence that may help | Typical technical challenge |
|---|---|---|
| Is ground or an asset moving? | Survey, settlement points, inclinometers, tilt, crack, GNSS, InSAR. | Separating genuine movement from reference, baseline, installation or data-processing effects. |
| Is groundwater or pore pressure changing? | Standpipes, piezometers, rainfall, pumping records, construction sequence. | Understanding response time, installation zone, datum, drainage and hydrogeological context. |
| Has an environmental condition changed? | Air, water, weather, noise, vibration, soil and other environmental observations. | Checking siting, calibration, averaging period, maintenance, local weather and data quality. |
| Does an alert represent a real event? | Raw series, metadata, neighbouring sensors, maintenance logs, survey and site events. | Distinguishing an automated threshold event from a technically credible change. |
| Can satellite data add useful context? | InSAR time series, survey, GNSS, ground instruments, geology and asset context. | Understanding line-of-sight geometry, spatial coverage, temporal sampling and ground truth. |
| Is soil or irrigation condition changing? | Soil moisture, soil temperature, rainfall, weather, irrigation and field observations. | Accounting for spatial variability, rooting depth, soil type and the scale represented by each sensor. |
Context Before Interpretation
A reading without site context can be technically correct and still be misleading.
Monitoring interpretation should be anchored to the physical system being observed. For an actual project, RAUZ reviews the official project information supplied by the client, designer, employer, public authority or other responsible source rather than inventing a ground model, climate condition or project mechanism.
Geology & stratigraphy
Soil and rock units, fill, weak layers, weathering, faults, interfaces and spatial variability influence which movements or groundwater responses are plausible.
Groundwater & hydrology
Water levels, pore pressure, drainage, pumping, rainfall, river or reservoir conditions can change ground behaviour and instrument response.
Weather & seasonal conditions
Rainfall, temperature, freeze–thaw, drought, humidity, wind and seasonal cycles may affect the monitored system, the sensor and the interpretation.
Construction & operational stage
Excavation depth, tunnelling advance, loading, dewatering, blasting, traffic, impoundment, maintenance or irrigation events provide a timeline against which measurements can be tested.
Geometry & sensitivity
A tunnel, slope, bridge, retaining wall, building, dam, mine, water body or agricultural field each requires a different relationship between measurement location and decision.
People, data & responsibilities
Instrument owner, field team, survey control, data platform, designer, contractor, operator and reviewer must use the same identifiers, units, timestamps, baselines and escalation rules.
Measurement Evidence
Different observations see different parts of the same system.
A monitoring programme is stronger when the measurement method matches the decision and when independent evidence can test the same hypothesis from another angle. RAUZ is vendor-neutral: the knowledge framework is organised around what an observation represents, not around a preferred hardware brand.
Deformation & displacement
Inclinometers, settlement systems, extensometers, convergence, tilt, crack monitoring, GNSS and survey observations can describe movement at different depths, locations and spatial scales.
Pressure & water level
Standpipes and piezometers are used to observe groundwater level or pore-pressure behaviour. Their meaning depends on installation zone, datum, response characteristics and site hydrogeology.
Load, strain & response
Load cells, strain gauges, tilt, crack and survey systems can help track structural response where the measurement point, installation detail and expected behaviour are properly defined.
Air, water & physical conditions
Air-quality sensors, water-quality sensors, weather stations, noise, vibration and other environmental measurements require fit-for-purpose siting, QA/QC and interpretation.
Soil, moisture & agriculture
Soil moisture, soil temperature, weather, irrigation and remote-sensing observations can support water-management and growing-condition decisions when field variability is considered.
Wide-area ground motion
SAR interferometry can add spatial and historical context over large areas. It should be interpreted with its geometry, temporal sampling and suitability for the surface being observed.
Ground & infrastructure instrument families
Common evidence may include inclinometers, piezometers, standpipes, settlement points or plates, extensometers, tiltmeters, crackmeters, vibration monitoring, GNSS and total-station survey. Instrument choice is project-specific and should follow the behaviour or risk being tested.
Environmental observation families
Depending on the monitoring objective, relevant observations may include rainfall and weather, groundwater or surface-water level, water-quality parameters, air-quality indicators, noise, vibration, soil condition and other project-specific environmental parameters.
Remote & spatial evidence
InSAR, GNSS, conventional survey and mapped project information can provide different spatial frames. Agreement between sources can strengthen an interpretation; disagreement can be equally useful because it identifies where reference systems, geometry, scale or physical mechanisms need closer review.
Data Quality & QA/QC
Before asking what a trend means, ask whether the evidence can be trusted.
Data QA/QC is part of technical interpretation. A clean graph can still contain the wrong unit, baseline, timestamp, reference point or instrument identity. A valid monitoring workflow keeps source data, metadata, corrections and reviewer decisions traceable.
- Instrument ID, location, depth, orientation and observed parameter
- Calibration, installation, maintenance and replacement records
- Accepted baseline, datum, sign convention and reference stability
- Units, timestamp, time zone and sampling or averaging period
- Completeness, missing readings and communication outages
- Range, spikes, step changes, flat-lines, repeated values and drift
- Raw versus corrected, filtered, averaged or derived values
- Cross-checks against neighbouring or independent observations
- Known construction, rainfall, pumping or operational events
- Documented exclusions, corrections, assumptions and reviewer status
Automated QC is useful, but it is not the final interpretation.
U.S. EPA air-sensor guidance recommends planning for data quality, frequent data review, maintenance, validation and checks for issues such as units, timestamps, completeness, outliers, rate of change and drift. EPA also cautions that automated checks can miss subtle problems or flag real events as bad data.
Keep the data-quality decision visible.
RAUZ separates source observation, automated or rule-based screening, engineering review and final interpretation so that a flagged value is not silently converted into a technical conclusion.
Interpretation
Separate observation, inference and uncertainty.
A monitoring record can show that a value changed. It does not automatically establish why it changed. The interpretation should test repeatability, trend, rate, spatial pattern, neighbouring evidence, site events and plausible physical mechanisms before escalation.
Observation
What was measured? By which instrument, at what location, time, reference and unit?
Pattern
Is the change persistent, accelerating, seasonal, local, widespread, correlated or isolated?
Context
Does the pattern agree with geology, groundwater, weather, construction, loading or operational events?
Confidence
What independent evidence supports the interpretation, what contradicts it and what remains unknown?
Magnitude is not enough: review rate and persistence
A large historical movement may be stable; a smaller movement that is accelerating may deserve closer review. The appropriate metric depends on the project, the parameter being monitored and the response framework defined by the responsible project parties.
Trigger exceedance is an event, not a mechanism
A threshold event should prompt the verification and response actions defined for the project. Technical interpretation then asks whether the measurement is credible, whether related observations agree, and whether the behaviour is consistent with the project mechanism.
Cross-source disagreement can be useful evidence
If an inclinometer, survey point and InSAR time series do not agree, the correct response is not to force them into one story. Check whether they observe the same location, direction, depth, spatial footprint and time period, and whether reference systems or data quality can explain the difference.
Remote Sensing & InSAR
Use wide-area satellite evidence as context, not as a substitute for every ground measurement.
Sentinel-1 carries C-band synthetic aperture radar and can image the Earth in day or night and through cloud. ESA explains that radar interferometry combines repeat radar images to detect ground deformation over wide areas. The engineering value comes from matching that spatial evidence to the project question and comparing it with suitable ground information.
Where is movement concentrated?
Use spatial patterns to identify areas that may deserve deeper review, field inspection or targeted instrumentation.
Did movement predate the current works?
Where suitable archive data exist, historical deformation can add context to a project baseline or help identify longer-term behaviour.
Does the wider pattern agree with ground data?
Compare InSAR with survey, GNSS, settlement, inclinometer, groundwater or other observations only where the geometry, location and time period support a meaningful comparison.
Knowledge Paths
Choose the next page from the question you need to answer.
This page is the entry point. Deeper RAUZ pages separate monitoring strategy, data quality, diagnostics, remote sensing, analytics and reporting so that each subject can develop its own evidence, examples and technical depth without duplicating the same generic explanation.
Monitoring Intelligence
Recurring review of mixed monitoring evidence, data quality, trends, anomalies, context and technical significance.
Data Diagnostics
Focused investigation of jumps, drift, baseline concerns, conflicting sensors, apparent exceedances and unexplained trends.
Monitoring Design
Connect engineering or environmental questions with measurement methods, baseline, frequency, data route and response logic.
Quality & Data Assurance
Metadata, calibration, baseline, validation, traceability, correction control and review discipline before interpretation.
Data Integration
Structure monitoring, survey, environmental, project and remote-sensing information without forcing a replacement of working field systems.
Automated Reporting
Automate repeatable checks, charts and report preparation while keeping engineering interpretation and limitations under review.
Official Technical Sources
Use public technical guidance to frame the question; use project evidence to answer it.
The sources below are official government or intergovernmental publications used to frame this knowledge page. They do not imply partnership, endorsement or a commercial relationship with RAUZ. Project-specific conclusions still require the relevant site information, monitoring records and appointed professional responsibilities.
- Federal Highway Administration — Project Development and Design Manual, Chapter 6: Geotechnical
Official FHWA guidance on using instrumentation to answer specific project questions, monitoring seasonal or expected variation, standardized records and communication of findings. - Federal Highway Administration — Geotechnical Site Characterization
Official reference covering geotechnical site characterization and documentation of field-instrumentation observations such as groundwater, inclinometer and settlement evidence. - U.S. Geological Survey — Real-Time Monitoring for Potential Landslides
Official USGS example showing how rainfall, water content, tensiometers, piezometers, inclinometers and other observations can be combined to monitor slope behaviour. - European Space Agency — Sentinel-1 Instrument
Official ESA explanation of Sentinel-1 synthetic aperture radar and radar interferometry for wide-area ground-deformation monitoring. - U.S. Environmental Protection Agency — Quality Assurance for Air Sensors
Official EPA guidance on monitoring objectives, QA/QC planning, siting, calibration, timestamps, completeness, outliers, drift, validation and data management. - U.S. Environmental Protection Agency — Water Monitoring
Official EPA resources describing how water-quality monitoring supports trend identification, emerging-problem detection, programme assessment and emergency response. - World Meteorological Organization — WMO Integrated Global Observing System
Official WMO framework emphasising fit-for-purpose observations, integration of diverse observing systems and environmental, weather, water and climate applications. - Food and Agriculture Organization — Rapid Appraisal Procedure
Official FAO example of combining physical, water-balance and management information to diagnose irrigation-system performance and prioritise improvement.
Frequently Asked Questions
Monitoring knowledge questions that come before the dashboard.
What is a monitoring knowledge base?
A monitoring knowledge base is a structured technical resource that explains how monitoring questions, measurement methods, data quality, physical context and interpretation fit together. RAUZ uses it as a learning and reference layer across engineering, environmental and natural-system monitoring.
How is this different from a list of instruments?
An instrument catalogue starts with hardware. This knowledge base starts with the decision. It asks what behaviour or environmental condition matters, what evidence can resolve it, how the evidence should be checked, and what limitations remain before any conclusion is made.
Can RAUZ work with an existing monitoring system?
Yes. RAUZ is designed as a vendor-neutral intelligence layer. The technical scope can use existing project data, survey outputs, environmental observations, InSAR products, reports or platform exports where the underlying records and metadata are sufficient for the agreed review.
Does a trigger exceedance prove that dangerous movement is occurring?
No single conclusion should be inferred from the threshold event alone. The project response defined by the responsible parties should be followed, while the technical review checks data credibility, repeatability, rate, related instruments, site events and the physical context.
Can InSAR replace ground instrumentation?
Not as a general rule. InSAR and ground instruments observe movement differently and at different spatial, directional and temporal scales. In some projects satellite data can screen large areas or add historical context; ground measurements, survey or inspection may still be needed to answer a local engineering question.
Why are weather, groundwater and geology included in a monitoring knowledge page?
Because a time series has no physical meaning in isolation. Rainfall, temperature, groundwater, stratigraphy, construction or operational events can change the monitored system or the sensor response. Relevant contextual records help test whether an observed pattern is technically coherent.
Does RAUZ provide statutory approval or replace the Engineer of Record?
No such replacement should be assumed from this website. RAUZ provides monitoring intelligence, analysis, independent review and related technical support within an agreed scope. Statutory approvals, site-safety responsibilities and jurisdiction-specific professional duties remain with the appropriately appointed parties unless expressly defined otherwise in a separate engagement.
What should I send RAUZ for an initial technical discussion?
A useful starting package is a short project brief, monitoring objective, instrument register, representative dataset or report, trigger table, asset or site drawing, project chronology and the official ground, groundwater, environmental or operational information needed to understand the question.
Technical Discussion
Have monitoring evidence that needs a clearer interpretation?
Send a representative dataset, monitoring report, InSAR output or short project brief. RAUZ can first define the question, identify missing context, explain which comparisons are technically meaningful and suggest whether the next step is diagnostics, independent review, monitoring redesign, remote-sensing analysis or a recurring Monitoring Intelligence workflow.