FROM MONITORING DATA TO ENGINEERING DECISIONS.

Geotechnical Monitoring Intelligence for Infrastructure

GeoSmar turns monitoring, survey and satellite data into engineering intelligence through data QA/QC, trend analysis, trigger review, anomaly diagnosis and engineer-reviewed reporting for infrastructure worldwide.

Discuss Your Project Request a Quote

Monitoring Intelligence

The value of monitoring is not the number of readings. It is the quality of the engineering decision.

GeoSmar Monitoring Intelligence is a remote-first engineering service for projects and assets that already generate monitoring, survey or satellite-derived data. The service is designed to check whether the evidence is reliable, identify meaningful change, place that change in project context and communicate what deserves technical attention.

Monitoring evidence Instrument readings, survey observations, automated logger exports, monitoring reports, trigger tables, project records and satellite-derived ground-motion information.

Engineering review Data QA/QC, baseline checks, trend and rate review, trigger assessment, anomaly diagnostics, cross-checking and interpretation against the project mechanism.

Decision support Prioritised findings, traceable plots, technical commentary, limitations, review actions and a clearer basis for project discussion.

GeoSmar works above the measurement layer.

Installation, routine readings and equipment maintenance can remain with the client’s existing contractor or site team. GeoSmar adds a vendor-neutral analytical and engineering interpretation layer without requiring a project to replace monitoring systems that are already in place.

About GeoSmar Email a Monitoring Enquiry

What the review should answer

Five questions matter more than a crowded dashboard.

The Monitoring Intelligence workflow is built around engineering questions rather than around software features. The exact interpretation remains project-specific, but the review normally starts with the same fundamentals.

Where is movement occurring?Locate the instruments, structures, ground zones or wider deformation patterns that deserve closer review.

Is it changing?Examine direction, persistence, magnitude and rate of change instead of treating one reading as a complete conclusion.

Is the change credible?Check continuity, baseline behaviour, neighbouring instruments, survey references, data gaps and other factors that may affect confidence in the observation.

What is the engineering significance?Relate the observed behaviour to the ground model, groundwater, construction sequence, asset geometry, monitoring criteria and plausible mechanism.

What should be reviewed next?Define the next technical step: verify data, compare another dataset, increase review frequency, investigate a local mechanism or revisit the monitoring strategy.

Data inputs

Use the instruments and systems the project already has.

Monitoring Intelligence is not tied to one sensor manufacturer. Depending on the project and the available metadata, GeoSmar can review time-series information from common geotechnical, structural, survey and environmental monitoring sources.

Ground movement

Displacement & deformation

Inclinometers, in-place inclinometers, extensometers, settlement records, tiltmeters, crack meters, GNSS and total-station observations.

Hydro-mechanical

Groundwater & load response

Piezometers, water-level observations, load cells, earth-pressure cells, strain gauges and related construction records where available.

Remote & environmental

Context beyond one instrument

Vibration, rainfall and environmental records, along with satellite-derived InSAR ground-motion information where the method is suitable for the site and review objective.

Trimble’s official T4D documentation lists crack meters, earth-pressure cells, extensometers, inclinometers, load cells, piezometers, strain gauges, tiltmeters, water-level gauges, weather stations and other geotechnical sensors within a common monitoring environment. This is useful industry context for the multi-source approach, but it does not imply a commercial relationship with GeoSmar.

Official source: Trimble — Geotechnical sensors ↗

Instrument compatibility for a specific GeoSmar engagement depends on the raw data, timestamps, units, coordinate/reference system, metadata, calibration information and project context actually available. A list of sensor types is not a promise that every dataset can be interpreted to the same level of confidence.

Project context

Geology, groundwater and contract interfaces belong in the interpretation.

This is a global solution page, not a discussion of one named project. GeoSmar therefore does not assume a site geology or invent a ground profile. For an actual project, the monitoring interpretation should be anchored to the official project information supplied by the client, designer, employer or relevant public authority.

Ground and design information to review

Site investigation reports, borehole logs, geological sections, groundwater records, geotechnical design reports, construction drawings, excavation or tunnelling sequence, retaining systems, foundations and the defined zone of influence.

Monitoring information to review

I&M plans, instrument schedules, baseline records, trigger criteria, raw time series, survey-control information, calibration or maintenance records, monitoring reports and any documented changes to the monitoring arrangement.

Contract and interface points that should be made explicit

Raw-data accessWho owns the monitoring data, what format is available and whether GeoSmar can review source records rather than only screenshots or summary tables.

Baseline acceptanceWhich period is considered baseline, who accepted it and how resets, replacements or reference changes are documented.

Roles and authorityWho collects, validates, interprets, approves and acts on monitoring information, particularly where several contractors or consultants are involved.

Trigger governanceWhich contractual or design criteria apply, who can revise them and how exceedances are escalated.

Sensor downtimeHow missing data, failed instruments, replacements and periods of reduced coverage are recorded and communicated.

Reporting cut-offFrequency, data cut-off time, review period, response expectations and whether a routine report is distinct from an incident review.

Change controlHow construction sequence, dewatering, temporary works or monitoring-layout changes are passed to the reviewer so that data are not interpreted without context.

Liability boundaryMonitoring intelligence should be clearly distinguished from statutory design approval, construction supervision, emergency command or Engineer-of-Record duties unless those services are separately and formally appointed.

Project-specific geology, stratigraphy, groundwater levels, contract obligations and trigger values should come from the official documents for that project. GeoSmar should not substitute generic web information for project-controlled engineering records.

Engineering workflow

A repeatable review process, with the engineering context kept visible.

The sequence below is designed to make the review traceable. It separates data checking from interpretation and keeps automated processing as a support tool rather than a substitute for engineering judgement.

Register the evidence

Confirm datasets, units, timestamps, sensor identifiers, reference systems, review period and the project documents needed to interpret them.

Check data quality

Identify gaps, unusual jumps, resets, inconsistent references, flat-lines or other issues that may change the confidence placed in a result.

Review behaviour

Examine trend, rate of change, trigger proximity, spatial pattern and relationships with nearby or complementary measurements.

Interpret in context

Consider construction sequence, ground conditions, groundwater, asset geometry and the plausible mechanism before assigning significance.

Communicate clearly

Separate observation, interpretation, uncertainty and recommended follow-up so that the project team can see how the conclusion was reached.

Technology can screen and organise data. It should not hide the reasoning.

Trimble’s current monitoring documentation describes sensor management, data integration, analysis, visualisation, alarming and reporting as connected functions. GeoSmar applies a different business model: it focuses on the independent engineering layer that reviews what the monitoring evidence means for the project.

Official source: Trimble 4D Control Help ↗

Deliverables

Choose a review depth that matches the project question.

Monitoring Intelligence can begin as a focused technical review and develop into a recurring service once the data flow, review frequency and responsibilities are agreed.

One-off

Data Diagnostic Review

For a defined issue such as an unexplained jump, inconsistent instruments, apparent trigger exceedance, baseline concern or sudden change in rate.

Recurring

Monitoring Intelligence Review

Scheduled review of agreed monitoring datasets with trend commentary, priority issues, trigger context, limitations and items requiring follow-up.

Portfolio

Multi-Asset Review Framework

A consistent review structure across several sites or assets where data formats, monitoring criteria and responsibilities can be standardised.

Typical technical outputs

Data-quality observations, time-series plots, rate-of-change views, trigger comparison, cross-instrument review, key anomalies, engineering commentary, limitations and prioritised review actions.

Possible reporting formats

Technical review memorandum, monthly monitoring-intelligence report, incident data note, dashboard-supported review, portfolio summary or an agreed client template.

Any automated reporting component should remain engineer-reviewed before technical conclusions are issued. Automation is most useful for repetitive preparation, checking and presentation tasks; responsibility for interpretation should remain explicit.

Applications

One review method, different asset questions.

The monitoring inputs and engineering mechanism change by asset. GeoSmar keeps the review asset-led rather than country-led, allowing local contractors to continue field delivery while the interpretation framework remains consistent.

Rail & Metro

Track settlement, adjacent excavation effects, tunnel influence, groundwater change and movement affecting operational or third-party assets.

Tunnels & Underground

Surface settlement, convergence, retaining-wall response, nearby structures, utilities and groundwater-related behaviour during underground works.

Roads & Bridges

Embankment settlement, bridge approaches, foundation movement, cut slopes, landslide-prone areas and corridor-scale ground behaviour.

Slopes & Landslides

Review inclinometer, groundwater, rainfall, survey and wider-area ground-motion information where those datasets are available and suitable.

Mining & Tailings

Wide-area deformation, slope or embankment behaviour, piezometric change, inaccessible zones and long-term asset monitoring.

Critical Facilities

Settlement, tilt, vibration, groundwater and adjacent-construction effects where relatively small movement can carry significant operational consequences.

Official international case evidence

Three public examples show why monitoring intelligence needs more than one data stream.

The examples below come from the original providers’ official project pages. They are not GeoSmar projects and do not imply partnership, endorsement or commercial association. They are included to show established approaches to multi-source monitoring, remote acquisition and satellite-ground integration.

Thames Tideway Tunnel East

London, UK

Sixense’s official project page describes a monitoring programme combining software, settlement and deformation monitoring, tiltmeters, inclinometers/IPI arrays, piezometers, extensometers, environmental monitoring and Atlas InSAR.

The project shows why a tunnel programme may need ground, structural, environmental and satellite information in one review environment.
For GeoSmar, the transferable lesson is not the hardware package: it is the value of comparing multiple evidence streams before interpreting movement.

Official Sixense project page ↗

Eppenberg Tunnel

Switzerland

Worldsensing’s official success story describes permanent and reliable geotechnical monitoring for the 3,114 m Eppenberg railway tunnel, with wireless acquisition used to gather readings from instruments across the works.

The project highlights the importance of dependable data acquisition where monitoring is continuous and infrastructure remains operational.
For GeoSmar, acquisition quality is the starting point; the next layer is determining which changes are credible and significant.

Official Worldsensing success story ↗

Trunk Road T2 — Cha Kwo Ling

Hong Kong SAR

Sixense Asia’s official reference describes InSAR monitoring at Cha Kwo Ling Village during TBM works, where conventional manual monitoring was difficult because of access and disturbance constraints.

The case demonstrates how remote satellite observations can extend spatial coverage where physical access is difficult.
For GeoSmar, InSAR is most useful when its limitations and ground-monitoring context are both kept visible in the engineering interpretation.

Official Sixense Asia reference ↗

A fourth industry pattern is visible in Trimble’s current T4D documentation: total stations, GNSS, geotechnical, vibration and environmental sensors can be integrated with analysis, visualisation, alarming and reporting. GeoSmar’s intended role is not to reproduce those platforms, but to provide an engineering-review layer that remains useful across different data systems.

How GeoSmar can collaborate

Add engineering intelligence without replacing the project’s delivery chain.

GeoSmar is structured so that asset owners, consultants, contractors and monitoring companies can keep their existing field arrangements. The collaboration scope can sit above those arrangements and focus on the part that is often hardest to standardise: interpretation.

Owner / Asset Operator

Independent review of monitoring performance, portfolio trends, contractor reports and issues that need escalation or deeper technical investigation.

Consultant / Designer

Monitoring strategy, trigger framework review, data interpretation, cross-checking against design assumptions and focused incident analysis.

Contractor / Monitoring Provider

Additional engineering review capacity, data diagnostics, automated reporting workflows and independent interpretation where the project team needs a second technical layer.

InSAR + ground monitoring review

Where suitable satellite-derived information exists, GeoSmar can compare wider-area movement patterns with local instrument and survey data to support a more complete engineering discussion.

Monitoring design feedback

If the available evidence is not adequate to answer the risk question, GeoSmar can help identify data gaps and discuss whether additional monitoring, different frequency or another measurement method should be considered.

Email GeoSmar WhatsApp GeoSmar

Frequently asked questions

Questions before starting a Monitoring Intelligence review.

What is Geotechnical Monitoring Intelligence?

It is an engineering review service that takes monitoring, survey and, where appropriate, satellite-derived data and turns it into a structured view of data quality, trends, anomalies, trigger context, engineering significance and required follow-up.

Does GeoSmar need to install the instruments?

No. The GeoSmar model is designed to work with data produced by the client’s existing monitoring contractor, survey team, instrumentation provider or asset-management system, provided the underlying data and project context are sufficient for the agreed review.

Can GeoSmar review data from different sensor brands?

Potentially, yes. The important issue is not the brand name but whether the data, units, timestamps, references, metadata, calibration information and project context are available and reliable enough for the intended engineering question.

Can GeoSmar review only a monthly monitoring report?

A report can be reviewed, but access to the underlying time-series data and relevant project information usually allows a stronger technical assessment. The required inputs depend on the question the client wants answered.

How does GeoSmar use trigger levels?

GeoSmar can compare observed data with the trigger criteria formally supplied for the project and review whether an apparent exceedance is credible, persistent and consistent with the surrounding evidence. GeoSmar does not invent project trigger levels from generic web guidance.

Does GeoSmar replace the Engineer, Designer or statutory reviewer?

No, unless a separate formal appointment explicitly creates such a role. Monitoring Intelligence is an analytical and engineering-review service. Contractual authority, statutory approvals, emergency command and design responsibility remain with the parties formally appointed to those duties.

Can Monitoring Intelligence be provided as a recurring service?

Yes. Once the data flow, review scope, responsibilities and reporting frequency are agreed, a one-off diagnostic review can develop into recurring project, site or portfolio-level monitoring intelligence.

Start with the evidence

Have monitoring data that needs an independent engineering view?

Send a sample report, anonymised dataset or project brief. GeoSmar can first define what information is required, what can be concluded from the available evidence and whether the right next step is a diagnostic review, recurring Monitoring Intelligence, InSAR interpretation or monitoring-strategy review.

For project-specific technical discussion, include the monitoring objective, asset type, project stage, available datasets and the official project documents that define the ground conditions and monitoring criteria.

Email Your Project Brief WhatsApp GeoSmar