SITE. EVIDENCE. MONITORING. DECISIONS.

Discuss Your Environmental & Monitoring Project

Start with your project location, environmental and ground conditions, monitoring objectives and available evidence. RAUZ helps frame a practical monitoring, data and interpretation pathway before scope is fixed.

Project Discussion

Start with the project question before choosing the monitoring system.

A useful first discussion should connect the site, the physical environment, the asset, the ground model, the monitoring objective and the decision the project team eventually needs to make. RAUZ uses that context to define what evidence is relevant, what can be reviewed remotely and where local investigation or field specialists may still be required.

SITE

Where is the project?

Country, coordinates or corridor, terrain, climate exposure, nearby development, water environment and access constraints can all change what should be monitored and how evidence should be interpreted.

GROUND

What is the physical setting?

Available site investigation, stratigraphy, rockhead, groundwater, fill, weak layers, slope conditions and existing structures help define plausible mechanisms and the depth or location of useful measurements.

DECISION

What must the monitoring explain?

The monitoring objective should be stated as an engineering or environmental question: movement, pore-pressure response, settlement, asset performance, environmental change, trigger exceedance or another defined behaviour.

Important: this page is a pre-scope discussion framework, not a site-specific design. RAUZ does not invent geology, groundwater, climate conditions or project constraints that have not been verified from client records or authoritative public sources.

Site & Climate Context

Environmental conditions belong in the monitoring discussion from the start.

Before recommending a monitoring pathway, RAUZ first asks which environmental variables can reasonably affect the asset, the ground or the measurements. The relevant evidence may include rainfall, temperature, wind, soil moisture, surface water, groundwater, coastal exposure or other project-specific conditions.

Climate and weather

WMO climate-service guidance treats temperature, rainfall, wind and soil moisture as decision-support information that can be combined with infrastructure and other non-meteorological data. For a real project, RAUZ would prioritise the relevant national meteorological or hydrological service and other official sources for the project location.

Hydrology and groundwater

Where the engineering question involves slopes, excavations, embankments, foundations or dewatering, rainfall and groundwater may need to be considered together with movement data rather than reviewed as separate datasets.

What site information is useful at the first discussion?
Project location, terrain, nearby water bodies, known seasonal weather constraints, access restrictions, current construction activity, drainage or dewatering information, and any environmental limits already stated in project documents.
Why not rely on generic climate summaries?
A broad regional description may be useful for screening, but a monitoring scope should rely on authoritative location-specific records and project evidence where available. Climate context is used to frame the question, not to replace project observations.

Official context: World Meteorological Organization climate services describe the use of temperature, rainfall, wind, soil moisture and other climate information to support sector decisions and risk management.

Ground, Geology & Stratigraphy

Monitoring makes more sense when the measurements are tied to a plausible ground model.

RAUZ reviews available geological, geotechnical and groundwater information before interpreting movement. The preferred evidence is the project’s own site investigation and design information, supplemented where useful by official geological surveys, environmental assessments and other authoritative records for the project location.

Stratigraphy

Layer boundaries, fill, soft or compressible materials, granular layers, weathered zones and rockhead can affect where deformation or pore-pressure response may occur.

Groundwater

Groundwater level, pore pressure, dewatering, seepage and seasonal response may be relevant to both stability and interpretation of observed movement.

Geometry

Excavation depth, tunnel alignment, slope profile, retaining system, embankment geometry and neighbouring assets define where monitoring evidence is most useful.

Mechanism

The first discussion should identify credible mechanisms to test rather than select instruments before the engineering question is clear.

ISO 18674-1 frames geotechnical monitoring around ground behaviour, structures interacting with the ground, geotechnical works and the performance questions that monitoring is intended to test. RAUZ uses the same principle: define the behaviour first, then select evidence that can observe it.

Monitoring Strategy

A practical monitoring concept should connect risk, evidence, frequency and response.

The initial discussion is structured around what can change, how that change could be observed, how often the evidence is needed and what action the project team expects to take when conditions change.

1

Define the question

Identify the asset, environmental system or ground behaviour that matters and the decision the monitoring must support.

2

Map the evidence

Review existing instruments, survey, GI, groundwater, environmental records, InSAR, inspection information and project chronology.

3

Identify the gaps

Determine whether missing spatial coverage, frequency, baseline, metadata or independent evidence prevents a defensible interpretation.

4

Define review and response

Agree how data will be checked, interpreted, escalated and reported, and which decisions remain with the project’s appointed parties.

Instrument & Evidence Options

Instrument choice follows the parameter that needs to be observed.

RAUZ is vendor-neutral. The first discussion is not about selling a fixed instrument package; it is about deciding which measurements can test the project question and how those measurements will be checked against independent evidence.

Evidence typeTypical questionPossible project use
Inclinometer / displacement profileWhere is lateral movement occurring with depth?Excavations, slopes, embankments, retaining systems, tunnels and other geotechnical works where lateral deformation is relevant.
Piezometer / groundwaterHow is pore pressure or piezometric level changing?Excavations, foundations, slopes, embankments, dams, tunnels and dewatering or consolidation questions.
Settlement / levelling / geodetic surveyIs the ground or asset moving vertically or spatially?Buildings, rail, roads, embankments, excavation influence zones and other assets where displacement needs to be tracked.
Strain or load measurementHow are structural or support forces changing?Piles, struts, anchors, retaining elements, tunnel linings and other structural components where the project design requires these parameters.
InSAR / satellite ground motionIs there a wider spatial pattern or historical deformation signal?Screening and wide-area context, particularly where satellite geometry, surface conditions and data availability are suitable.
Weather / environmental observationsCould rainfall, temperature, soil moisture or another environmental variable help explain the monitored response?Project-specific environmental correlation, slope or groundwater interpretation, natural systems and environmental monitoring.
The table is a discussion guide, not a design prescription. Final selection, layout, accuracy, frequency, redundancy and trigger logic depend on the project ground model, asset, risk, contractual requirements and local professional obligations.

Data & Monitoring Intelligence

The project can keep its existing field system and still add an independent intelligence layer.

RAUZ can begin with the monitoring information a project already has. The analytical task is to check data quality, reconstruct context, compare independent evidence and identify what the measurements can—and cannot—support.

CONNECT

Bring mixed sources together

Monitoring exports, manual readings, survey, environmental records, project events, InSAR and existing reports can be reviewed within one evidence framework without forcing the client to replace its field suppliers.

VALIDATE

Check the record before the story

QA/QC can include units, timestamps, gaps, duplicate values, baselines, instrument identity, resets, suspicious steps, metadata and data provenance before engineering interpretation begins.

INTERPRET

Test more than one explanation

Trend, rate, neighbouring instruments, construction activity, groundwater, environmental conditions, survey and wider-area evidence can be compared before a technical finding is written.

Official Public Evidence

What established monitoring practice tells us before a project is scoped.

The examples below are public technical references, not RAUZ projects. They illustrate why a useful project discussion often combines physical context, multiple datasets and explicit monitoring objectives.

USGS: rainfall, groundwater and slope movement

The U.S. Geological Survey’s Highway 50 landslide monitoring site presents rainfall, groundwater pressure and slope movement together. The lesson is not to copy the instrument layout; it is that related environmental and ground responses can be more useful when interpreted together.

ESA: wide-area ground deformation

ESA explains that Sentinel-1 radar interferometry can detect small ground movements across wide areas. InSAR can therefore provide spatial or historical evidence that may complement local instruments when the site and data are suitable.

ISO 18674: monitoring as a performance question

ISO 18674-1 addresses performance monitoring of ground, structures interacting with the ground and geotechnical works before, during and after construction. The practical implication is simple: monitoring should be tied to the behaviour that matters.

Collaboration Pathways

RAUZ can enter a project without taking over the entire delivery chain.

A project may already have a designer, monitoring contractor, survey team, sensor supplier, local consultant or environmental specialist. RAUZ can add a defined analytical or independent-review layer and work with those parties where responsibilities are clear.

Independent technical review

Review monitoring strategy, data quality, trigger logic, unusual trends, reports or evidence supplied by another project party.

Monitoring intelligence

Provide recurring review of agreed datasets, anomalies, trends, cross-source evidence and engineer-reviewed reporting.

Remote sensing integration

Bring satellite-derived ground-motion information into the same engineering discussion as survey, instrumentation, groundwater and project records.

Monitoring design support

Discuss monitoring objectives, parameters, instrument classes, baseline strategy, frequency, data flow and reporting requirements before the final design is fixed.

Data and reporting workflow

Structure QA/QC, analytics, alerts and repeatable reporting so that the project team spends less time rebuilding the same information manually.

Local field partnership

Where site installation, readings, survey, statutory work or jurisdiction-specific sign-off is required, RAUZ can define the technical interface while appropriate local parties retain those responsibilities.

Project Brief Builder

Send the site, the evidence and the question you need answered.

You do not need a finished specification before contacting RAUZ. A concise first brief is enough to decide what information should be reviewed next and whether the project needs diagnostics, monitoring strategy, InSAR, recurring monitoring intelligence or another specialist route.

Open Blank Email

This form does not upload project files or submit data to a RAUZ server. It prepares a message in your own email application. Agree an appropriate confidentiality and transfer route before sending sensitive drawings, raw project data or proprietary documents.

Official Technical Sources

Public references used to frame this discussion page.

These sources are official standards-body, intergovernmental or government publications. They are used for technical context only and do not imply endorsement, partnership or a commercial relationship with RAUZ.

Author: RAUZ Technical Team  ·  Technical review: Dr. Xuefeng (Jason) Nong  ·  Updated: 4 October 2026

FAQs

Before the first project discussion.

Do I need a complete monitoring specification before contacting RAUZ?
No. A useful discussion can start with the project location, asset type, current stage, known ground or environmental conditions, existing monitoring information and the question the team needs the monitoring to answer.
Can RAUZ discuss a project before instruments are selected?
Yes. Early discussion is often the right time to define the behaviour or environmental variable that matters, what evidence already exists, what gaps remain and which classes of measurement could address those gaps.
Can RAUZ review a project that already has a monitoring contractor?
Yes. RAUZ is designed to work as a vendor-neutral analytical and independent-review layer. Existing field suppliers, survey teams, instruments and local contractors can remain in place where that arrangement is working.
Can climate, rainfall or groundwater information be considered with movement data?
Yes, when those variables are relevant to the engineering or environmental question and suitable evidence is available. The purpose is to test plausible relationships, not to assume causation from coincidence alone.
Can InSAR be discussed even if the project already has ground instruments?
Yes. InSAR can provide a wider spatial or historical evidence layer where technically suitable. Its role should be defined alongside the geometry, resolution, surface conditions and the local monitoring question rather than treated as a substitute for every ground measurement.
Does RAUZ provide local statutory certification in every country?
No such assumption should be made. Jurisdiction-specific professional registration, statutory certification, site safety authority and Engineer-of-Record responsibilities must be defined separately. RAUZ can work with appropriate local parties where those functions are required.
What should I send first if the project is confidential?
Start with a high-level brief that does not disclose sensitive details. The parties can then agree confidentiality requirements and an appropriate transfer route before detailed drawings, raw datasets or proprietary documents are exchanged.

Start the Conversation

Bring the site, the evidence and the question. We can define the next technical step together.

A first discussion can be short. Tell RAUZ where the project is, what is being built or monitored, what you already know about the ground or environment, what instruments or datasets exist and what decision the monitoring needs to support.

Vendor-neutralIndependent reviewEnvironmental + engineering contextInSAR + ground evidenceRemote-first deliveryEngineer-reviewed outputs
Scroll to Top