EVIDENCE. CONTEXT. ENGINEERING JUDGMENT.
Geotechnical Monitoring Engineering Approach
GeoSmar combines data QA/QC, monitoring analytics, ground-model context, independent review and engineer-reviewed reporting to turn monitoring, survey and InSAR evidence into clear engineering decisions.
Engineering Approach
Start with the engineering question. Use monitoring evidence to test it.
GeoSmar approaches monitoring as an engineering feedback system. The objective is not to collect the largest possible volume of readings. It is to establish what behaviour matters, gather evidence that can test the relevant design assumptions or performance questions, verify the data, interpret changes in context and communicate what the project team should review next.
Core principles
Ten principles guide how GeoSmar reviews monitoring.
- Define the engineering question before selecting the instrument
- Check data quality before interpreting movement
- Use a project-specific baseline and reference system
- Review trend and rate of change alongside magnitude
- Compare neighbouring and independent datasets where available
- Interpret measurements against the ground model and project events
- Separate measured observation from engineering inference
- State limitations and uncertainty with the conclusion
- Connect alerts to an agreed verification and response process
- Keep final technical reporting subject to engineering review
Evidence hierarchy
Not every data source carries the same weight for every conclusion.
GeoSmar reviews evidence according to what the source actually measures, how it was obtained and how directly it relates to the engineering question. A dashboard value, for example, is not automatically stronger evidence than a verified raw survey record simply because it is available in real time.
| Evidence source | What it can contribute | Important checks | How GeoSmar uses it |
|---|---|---|---|
| Ground investigation & geological model | Stratigraphy, material behaviour, groundwater and plausible mechanisms | Source, coverage, age, interpretation and uncertainty | Frames which movement mechanisms are physically plausible |
| Instrument raw data | Direct measurements from the installed monitoring system | Calibration, installation, units, baseline, timestamps, maintenance and configuration | Primary quantitative evidence where the instrument is suitable and functioning |
| Survey / GNSS | Geodetic movement relative to an established network | Reference stability, adjustment, geometry and environmental effects | Independent or complementary movement evidence |
| InSAR-derived ground motion | Wide-area surface deformation patterns and historical time series | Viewing geometry, coherence, geolocation, reference frame and temporal coverage | Spatial and historical context, not a substitute for all ground instruments |
| Construction / operational records | Timing of excavation, loading, dewatering, grouting, deposition or maintenance | Completeness, exact timing and scope | Tests whether observed changes are consistent with project events |
| Inspection & visual records | Physical evidence such as cracks, seepage, distress or changed site conditions | Date, location, scale, observer and photographic context | Supports or challenges an instrument-only interpretation |
Ground model first
Monitoring cannot explain a mechanism that the project context has never defined.
For geotechnical monitoring, the ground model is the bridge between a measured change and a credible engineering explanation. The same settlement curve can imply different mechanisms in compressible fill, soft clay, weathered rock, karstic ground, an embankment foundation or a mined area.
Geology & stratigraphy
Review documented layers, weathering, structure, discontinuities, fill, weak zones or other features that can control deformation.
Groundwater
Consider piezometric conditions, seepage, dewatering, recharge, drainage and the response time of the monitoring system.
Construction mechanism
Relate excavation, tunnelling, loading, support installation, embankment construction or other documented activities to the expected ground response.
Monitoring design
Instrumentation should be designed around expected behaviour and potential failure modes.
FHWA guidance treats geotechnical and structural instrumentation as a means of monitoring underground construction performance and reducing problems. USACE EM 1110-2-1908 connects instrumentation planning with performance assessment and potential failure modes. GISTM similarly requires engineering monitoring systems to verify design assumptions and monitor potential failure modes.
Define what can change
Movement, groundwater, pore pressure, load, strain, vibration, seepage or another parameter should be linked to a defined mechanism.
Select the measurement
Choose the sensor, survey method or remote-sensing product that can observe the required parameter with suitable range and resolution.
Place it where it can answer the question
Depth, location, orientation, datum and reference system can be as important as the instrument model itself.
Define how the result will be used
Baseline, frequency, verification, trigger framework, reporting route and response ownership should be agreed before monitoring starts.
Data QA/QC
Before asking what a reading means, ask whether the reading can be trusted.
Data quality is not a separate administrative task. It is part of the engineering interpretation. Modern platforms such as Bentley iTwin IoT explicitly combine sensor-data validation with analysis and alerts; GeoSmar keeps that validation step visible in the engineering workflow.
- Instrument identity, position, depth and orientation
- Calibration and installation records
- Baseline, datum and sign convention
- Units and calculation method
- Timestamp and time-zone consistency
- Missing data and communication outages
- Spikes, flat-lines, drift and step changes
- Maintenance, replacement and re-zeroing events
- Reference-point or benchmark stability
- Raw versus corrected or derived values
- Manual verification where appropriate
- Traceable exclusions and data corrections
Engineering interpretation
A measurement becomes engineering intelligence only after it survives context and cross-checking.
GeoSmar separates observation, verification and interpretation. This prevents a chart, anomaly flag or single threshold crossing from becoming a causal conclusion too early.
Observe
What changed? By how much? Over what time? At what depth or location? Is the movement persistent, episodic, seasonal or accelerating?
Verify
Is the instrument reliable? Do neighbouring sensors, survey, groundwater, inspection or InSAR show compatible behaviour?
Interpret
Is the change physically consistent with the documented ground model, structural system, construction stage or operating condition?
Why can a single abnormal reading be misleading?
Why review rate of change?
Why separate observation from inference?
Triggers, alerts & response
A trigger is a decision rule, not a coloured line on a chart.
A useful trigger framework defines the monitored parameter, reference, threshold or trend criterion, verification step, notification route and engineering response. The same principle appears in GISTM, which requires performance outside expected ranges to be addressed through Trigger Action Response Plans or critical controls.
Define
Set project-specific criteria from the design basis, impact assessment, asset tolerance, risk framework or approved monitoring plan.
Verify
Confirm instrument health, reference stability, neighbouring data and relevant project events before assigning engineering significance.
Respond
Increase review frequency, inspect, escalate, mitigate or change operations according to the agreed project response procedure and authority structure.
InSAR integration
Use satellite ground-motion information to widen the field of view, not to replace every ground instrument.
Copernicus EGMS uses Sentinel-1 InSAR to provide ground-motion information for infrastructure and geohazard applications. GeoSmar treats InSAR as one evidence layer within the engineering review: useful for historical and wide-area deformation, but subject to viewing geometry, coherence, geolocation, reference and temporal limitations.
Screen
Look for distributed or historical movement across corridors, slopes, mines, dams, urban areas and other large assets.
Compare
Review satellite time series alongside GNSS, survey, inclinometers, piezometers, settlement and project-event information where available.
Focus
Use coherent deformation patterns to prioritise ground investigation, monitoring review or field verification rather than treating every radar point as a diagnosis.
Independent monitoring review
Independence is most useful when the reviewer can follow the evidence from raw data to conclusion.
GeoSmar can review monitoring performed by another contractor or generated by a client-owned system. The purpose is not to duplicate the site team. It is to provide a separate technical layer that examines whether the monitoring plan, data quality, trigger logic and engineering interpretation are supported by the available evidence.
Plan review
Monitoring objectives, instrument roles, layout, baseline, frequency, redundancy, triggers, reporting and response responsibilities.
Data review
Completeness, trends, anomalies, apparent exceedances, conflicting instruments, calculation methods and relation to construction or operating events.
Report review
Whether observations are distinguished from interpretations, whether important limitations are stated, and whether conclusions follow from the evidence presented.
Engineer-reviewed reporting
The report should show the reasoning, not hide it behind automation.
Digital monitoring platforms increasingly automate data acquisition, calculations, alerts and reporting. Bentley iTwin IoT describes an Acquire → Transform → Understand → Inform → Analyze workflow, while Trimble 4D Control combines measurement management, analysis and alerts. GeoSmar uses automation to reduce repetitive preparation while preserving engineer review around the final interpretation.
Automate routine preparation
Charts, tables, data-completeness checks, threshold overlays, rates and recurring comparisons can be prepared automatically where the data structure is reliable.
Keep commentary reviewable
Technical text should distinguish measured facts, engineering interpretation, assumptions, limitations and recommended next steps.
Preserve traceability
Reports should be able to trace important findings back to the relevant data period, instrument, calculation and project event.
Governance & contract interfaces
Good monitoring engineering requires clear ownership of data, decisions and response.
A technically sound monitoring system can still fail operationally when responsibilities are unclear. GeoSmar therefore treats governance and data interfaces as part of the engineering approach.
- Who owns and controls the raw data?
- Who installs, maintains and replaces instruments?
- Who approves the baseline and any re-baselining?
- Who defines and approves trigger criteria?
- Who verifies an apparent exceedance?
- Who receives alerts and within what time?
- Who has authority to change construction or operations?
- What data, drawings and project events are provided to the reviewer?
- How are corrections and superseded records documented?
- What review and reporting frequency is required?
- Which conclusions require local professional sign-off?
- How are third-party software and data limitations allocated?
Official engineering context
Across standards, asset owners and monitoring platforms, the direction is consistent: connect measurement to performance and decision-making.
The references below are official sources and are included as technical context only. They do not imply a partnership, endorsement or commercial relationship with GeoSmar.
FHWA — instrumentation as construction control
FHWA’s road-tunnel manual describes geotechnical and structural instrumentation as a tool to monitor construction performance and help avoid or mitigate problems.
USACE — monitoring asset performance
USACE EM 1110-2-1908 provides guidance for instrumentation, monitoring and assessment of embankment dams and levees, linking monitoring to performance and risk-informed engineering.
GISTM — monitoring design assumptions and failure modes
GISTM Principle 7 requires an integrated engineering monitoring system appropriate for verifying design assumptions, monitoring potential failure modes and addressing performance outside expected ranges.
Copernicus EGMS — wide-area ground-motion evidence
Copernicus EGMS uses Sentinel-1 InSAR to provide ground-motion information and identifies infrastructure and geohazard applications including dams, bridges, railways, buildings, landslides and subsidence.
Bentley — data to contextual infrastructure insight
Bentley iTwin IoT combines data acquisition, transformation, visualisation, alerts, analytics and reporting to support infrastructure-health decisions.
Sixense — measurements to decision support
Sixense’s monitoring and testing material describes accurate data and engineering methodologies as the basis for reducing risk and supporting decisions across construction and asset-management lifecycles.
Project-specific application
The engineering approach becomes more specific only when the project evidence becomes more specific.
This page defines GeoSmar’s general engineering method. It is not tied to one country, one project or one geological setting. For a named infrastructure project, GeoSmar can extend the same method into a site-specific technical discussion using verified primary-source information.
| Topic | Preferred evidence | What GeoSmar can assess | What GeoSmar should not assume |
|---|---|---|---|
| Geology & strata | Government geological survey, GI, official EIA / tender or client design records | Monitoring mechanism, depth, location and interpretation implications | Unverified strata, rockhead, cavities, weak layers or properties |
| Groundwater | GI, piezometric records, hydrogeological studies and project monitoring | Pressure / head response, dewatering, seepage and monitoring requirements | Unverified groundwater levels or causal relationships |
| Construction | Owner publications, tender / design records and supplied construction sequence | Monitoring zones, timing, frequency, event correlation and response interfaces | Unpublished temporary works or sequence |
| Contracts | Employer requirements, specifications, statutory documents and appointment scopes | Data ownership, review responsibility, triggers, reporting and assurance interfaces | Legal responsibility not supported by governing documents |
Frequently asked questions
How the GeoSmar engineering approach works in practice.
Does GeoSmar require its own instruments or monitoring platform?
Does GeoSmar rely on AI to make monitoring decisions?
How does GeoSmar decide whether movement is real?
How does GeoSmar use InSAR?
Can GeoSmar review another contractor’s monitoring report?
Does GeoSmar provide statutory approval?
What is useful for a first technical review?
Discuss the evidence
Have monitoring data, a trigger event or an engineering interpretation that needs a second view?
Send GeoSmar the project brief, monitoring report or sample dataset together with the question you need answered. The first step is to establish the evidence available, the limits of that evidence and the most useful form of review.