RESILIENT. MONITORED. DECISION-READY.

Critical Facilities Monitoring Intelligence

RAUZ connects geotechnical, structural, environmental, survey and InSAR data to detect movement, validate anomalies and support engineer-reviewed decisions for data centres, healthcare, energy and other critical sites.

Critical facilities

When continuity matters, monitoring has to explain more than movement.

Critical facilities can include digital infrastructure, healthcare and emergency facilities, energy and water assets, communications systems, government facilities and other sites where loss of function would have serious consequences. RAUZ focuses on the geotechnical, structural and environmental evidence that can affect the physical resilience and continued operation of these assets.

Digital infrastructure

Data centres & network facilities

Settlement, differential movement, foundation performance, groundwater, vibration and adjacent construction can all become operational concerns where equipment and service continuity are sensitive to change.

Health & emergency

Hospitals & emergency facilities

Monitoring can support resilience where facility access, structural behaviour, surrounding ground conditions or external works could affect the ability to keep essential services operating.

Essential services

Energy, water & utility sites

Substations, plants, tanks, buried services, retaining systems and supporting ground can require coordinated review where movement or groundwater change could affect service continuity.

Public function

Communications & government assets

Physical monitoring may form one part of a wider resilience programme where facilities depend on stable structures, reliable access and interconnected supporting infrastructure.

Official definitions differ by jurisdiction. CISA describes critical infrastructure as assets, systems and networks whose functions are necessary to society; the EU Critical Entities Resilience framework and the UK National Protective Security Authority likewise focus on continuity of essential services and the consequences of disruption. This RAUZ page uses “critical facilities” as an engineering industry category, not as a claim that every listed asset has a formal statutory designation.

Why monitoring matters

The physical risk is rarely one sensor or one threshold.

For a critical facility, an isolated reading has limited value without context. The practical question is whether the observed change is credible, whether it fits a plausible mechanism, whether independent evidence agrees, and whether the change could affect serviceability, access, equipment, utilities or the surrounding site.

Ground behaviour

Settlement & differential settlement

Review vertical movement across foundations, slabs, equipment areas, pavements and interfaces. Differential behaviour may matter even where absolute movement remains modest.

Water

Groundwater & pore pressure

Groundwater change can alter excavation response, effective stress, seepage conditions, uplift risk and consolidation behaviour. Interpretation has to follow the actual hydrogeological setting.

Construction interface

Adjacent excavation, tunnelling & piling

Deep excavation, dewatering, piling, demolition, utility works or tunnelling can change the ground and vibration environment around an operating facility.

Operations

Vibration & sensitive equipment

Where operational systems or equipment are vibration-sensitive, monitoring should be linked to project- and owner-specific acceptance criteria rather than generic limits.

External assets

Retaining walls, slopes & buried services

Access roads, retaining systems, cut slopes, tanks, ducts, utility corridors and buried services may influence resilience even when the main building remains stable.

Long-term condition

Slow or recurring movement

Seasonal groundwater response, gradual settlement, repeated vibration events or regional ground motion can be difficult to understand from occasional readings alone.

Ground & environmental context

No responsible monitoring strategy starts by assuming the geology.

A critical-facility monitoring plan should begin with the project location and the mechanism that could affect the asset. RAUZ therefore starts from the site investigation, foundation concept, groundwater regime, surrounding works and relevant environmental hazards rather than applying a standard instrument list.

Ground model to review

Fill / made ground Soil & rock profile Weak or compressible layers Bedrock variability Groundwater Slopes / retaining systems Legacy voids / subsidence context Foundation type & level

The IAEA’s site-evaluation standards for nuclear installations illustrate the level of care required for high-consequence facilities: soil and rock profiles, groundwater, settlement, slope instability, subsidence/uplift and liquefaction are all explicit geotechnical considerations. Those requirements are nuclear-specific, but the underlying lesson is broader—ground uncertainty should be investigated, not assumed.

Environmental and climate screening

Flooding Storms Heat Drought Sea-level exposure Wildfire context Drainage & water ingress Temperature / humidity

WHO guidance for climate-resilient healthcare facilities explicitly considers hazards including floods, storms, sea-level rise, droughts, heat waves, wildfires and cold waves. The relevant set will differ by facility and region, so the monitoring scope should be based on local hazard information and owner requirements.

Project input matters. For an initial review, useful records include borehole and CPT information, interpreted geology, groundwater records, foundation drawings, basement and retaining-wall details, utilities, adjacent construction, construction sequence, historical survey/monitoring data and the facility’s operational constraints.

Monitoring strategy

Start with the failure or serviceability mechanism. Then choose the measurements.

A useful programme defines what must be protected, what change could plausibly occur, where it would first appear, how quickly it might develop and what evidence is needed before escalation.

1 · DefineAsset, operational sensitivity, credible ground or structural mechanism and decision to be supported.
2 · BaselineEstablish pre-work behaviour, references, groundwater range, instrument health and known seasonal effects.
3 · ObserveSelect complementary measurements for movement, groundwater, vibration, structural response and wider-area deformation.
4 · ValidateCheck completeness, continuity, timestamps, baselines, reference stability and cross-sensor agreement.
5 · InterpretReview rates, anomalies, construction events and independent evidence before deciding what deserves action.
Construction phase

Protect operations during nearby works

Link monitoring frequency and escalation to excavation, dewatering, piling, tunnelling, heavy lifting, utility diversion or other activities that can change the ground or vibration environment.

Operational phase

Track slow change without alarm fatigue

Long-running facilities need traceable baselines, source-health checks and review logic that can distinguish gradual behaviour from data artefacts or recurring environmental effects.

Portfolio phase

Standardise evidence, not assumptions

A common reporting and QA/QC framework can support multiple sites while retaining site-specific geology, trigger criteria, instrumentation and responsibility boundaries.

Instrumentation & observation

Choose instruments for the question the facility needs answered.

No critical facility needs every instrument below. The monitoring mix should follow the ground model, structural system, surrounding works, required precision, access constraints, data latency and the consequences of missing a developing change.

Engineering question Possible measurement Typical instruments / methods Interpretation point
Is the facility or surrounding ground settling? Vertical displacement and differential movement Precise levelling, settlement markers, hydrostatic levelling where appropriate, robotic total station, GNSS for suitable applications Reference stability, spatial pattern and rate often matter as much as a single displacement value.
Is lateral ground movement developing? Subsurface or surface lateral displacement Inclinometers, in-place inclinometers, survey prisms, GNSS, extensometers where suitable Movement depth, direction and relationship to excavation, slope or retaining structure should be reviewed together.
Is groundwater contributing to risk? Groundwater level or pore pressure Standpipes, vibrating-wire piezometers, pressure transducers Hydrogeology, pumping/dewatering and response lag need project context.
Is the structure tilting, cracking or straining? Tilt, crack movement, strain or load response Tiltmeters, crackmeters, strain gauges, load cells, structural survey Temperature, installation details, baseline and structural load path can influence interpretation.
Are nearby works creating vibration exposure? Vibration level and event history Vibration monitors / seismographs with project-defined logging and event criteria Facility- or equipment-specific acceptance criteria should control the review, not a generic threshold copied from another project.
Is wider-area ground deformation occurring? Spatial ground-motion pattern over time InSAR, supplemented by suitable ground control or site instruments Satellite geometry, coherence, temporal sampling and local validation affect how the result should be used.
Are environmental conditions relevant to the facility? Weather, water ingress, temperature, humidity or other agreed environmental parameters Weather stations and project-specific environmental sensors Environmental data should be linked to a defined engineering or operational question rather than collected without a decision purpose.
Instrument selection is only one part of the system. Data ownership, calibration, maintenance, communications, baseline control, backup measurement routes and the party authorised to change trigger criteria should be defined before monitoring starts.

RAUZ platform layer

Connect the evidence. Check whether it can be trusted. Then interpret it.

Critical-facility projects often already have monitoring contractors, survey teams, dataloggers, BMS/DCIM systems and asset platforms. RAUZ is designed to sit above the relevant engineering measurement sources rather than force a replacement of working field systems.

Data Integration

One traceable engineering view

Connect approved CSV/Excel exports, APIs, monitoring systems, survey observations, environmental data, project metadata and InSAR where the interface and data rights permit.

QA/QC

Check before interpretation

Screen completeness, timestamps, units, discontinuities, baselines, source health, outliers and cross-sensor consistency so that a data problem is not mistaken for physical movement.

Monitoring Analytics

Trend, rate and anomaly review

Compare magnitude, rate of change, persistence, neighbouring observations and construction or environmental events to prioritise changes that deserve engineering attention.

InSAR Intelligence

Add wider spatial context

Where technically suitable, satellite-derived ground motion can provide historical or area-wide context and be compared with point-based ground measurements.

Alert Intelligence

Separate an event from a conclusion

A threshold exceedance can trigger review, but the engineering meaning still depends on data quality, reference stability, adjacent instruments, mechanism and project context.

Automated Reporting

Automate the routine, retain review

Charts, completeness checks, threshold overlays and recurring report assembly can be automated while technical interpretation, limitations and recommendations remain engineer-reviewed.

Regional delivery context

One monitoring framework. Different ground, climate and regulatory contexts.

RAUZ’s priority markets are the South Caucasus, European Union, United Kingdom, Middle East and Africa. The analytical framework can be consistent across regions, but the ground model, climate hazards, owner requirements, regulatory responsibilities and available datasets must remain local to the project.

South Caucasus

RAUZ is based in Tbilisi. For projects in Georgia, Armenia and Azerbaijan, the technical review should begin from site-specific geological, hydrogeological, seismic, climate and construction information. This page does not assign one ground profile or hazard level to the region.

European Union

The EU Critical Entities Resilience Directive establishes an all-hazards resilience framework for entities providing essential services and requires Member States to identify critical entities in covered sectors. For monitoring work, the practical implication is to define the project scope against the relevant national implementation, owner requirements and engineering responsibility chain.

United Kingdom

The UK National Protective Security Authority defines Critical National Infrastructure by the consequences that loss or compromise could have for essential services, public safety, national security or the functioning of the state. RAUZ’s physical monitoring role is narrower: ground, structural and environmental evidence where those factors are relevant to the facility or surrounding works.

Middle East

Critical-facility monitoring in the Middle East should be developed against the specific jurisdiction, operator standard, ground investigation, groundwater regime, temperature/environmental exposure, construction method and facility operating constraints. RAUZ does not apply a single regional geology or universal trigger schedule.

Africa

Africa spans very different geological, climatic and regulatory settings. Projects should therefore use country- and site-specific official information, local engineering data and owner requirements. Remote-first analysis can complement local field teams where reliable data transfer and responsibility boundaries are established.

Official evidence & international examples

Published industry evidence points to the same lesson: combine ground understanding with continuous, traceable monitoring.

The examples below are third-party official sources. They are included to show recognised industry practice and are not presented as RAUZ projects, partnerships or endorsements.

Hyperscale data-centre ground risk — Fugro GroundIQ®

Fugro’s 2026 official case study describes a planned hyperscale data-centre campus affected by variable subsurface conditions and historical underground mining. Fugro combined ambient-noise tomography with boreholes and CPT data to build a three-dimensional ground model and reduce uncertainty between point investigations. For RAUZ, the monitoring lesson is that sensor locations, baselines and trigger interpretation should be tied to the actual ground model rather than a generic facility template.

Official Fugro case study ↗

Deformation and vibration during sensitive underpinning — Sixense

Sixense’s official University of Virginia Rotunda case describes near-real-time deformation monitoring and continuous vibration monitoring during underpinning, shoring and excavation, with measurements centralised in its monitoring system. The example shows why critical or sensitive buildings benefit from linking construction stage, deformation and vibration rather than reviewing each dataset in isolation.

Official Sixense case study ↗

Continuous structural monitoring — Trimble

Trimble’s official monitoring material describes automated continuous monitoring and the integration of geotechnical, geodetic and environmental sensors for buildings, structures and infrastructure. This supports the industry direction toward continuous data availability; RAUZ adds an independent interpretation layer focused on data quality, cross-source consistency and engineering significance.

Official Trimble monitoring page ↗

European wide-area ground motion — Copernicus EGMS

The European Ground Motion Service provides Sentinel-1 InSAR-derived ground-motion products across Europe and states that the data can support monitoring of assets including dams, bridges, railways and buildings. For critical facilities, InSAR can be a useful complementary spatial or historical layer when geometry, coherence, temporal sampling and local validation are appropriate.

Official Copernicus EGMS page ↗

High-consequence geotechnical monitoring — IAEA

IAEA safety guidance for nuclear installations addresses geotechnical and geological hazards, groundwater monitoring, structural displacement and long-term monitoring-device selection. The requirements apply to nuclear installations, not ordinary critical facilities, but they provide a useful official reference for the depth of ground and monitoring assurance expected where consequences are high.

Official IAEA guidance ↗

RAUZ role

An independent engineering-intelligence layer above the measurement system.

A critical facility can keep its established instrumentation supplier, survey team, field contractor, BMS/DCIM environment or client platform. RAUZ can work from the engineering data that are relevant to ground, structure and environment, adding a separate layer for validation, interpretation and reporting.

Monitoring Intelligence

Recurring technical review

Review trends, rates, thresholds, anomalies, source health and engineering significance across agreed datasets and reporting periods.

Independent Review

Second view of the evidence

Review monitoring plans, contractor outputs, trigger logic, baseline quality, unusual events and whether the reported interpretation is supported by the available evidence.

Data Diagnostics

Investigate disagreement or abnormal change

Focus on sudden jumps, conflicting instruments, baseline shifts, missing records or observed movement that does not fit the expected mechanism.

Monitoring Design

Design the evidence chain

Define instrument-selection logic, locations, baseline strategy, frequency, data architecture, QA/QC, trigger governance and reporting requirements.

InSAR Interpretation

Add area-wide context where suitable

Use satellite-derived ground-motion information as a complementary layer and compare it with ground monitoring where spatial and temporal compatibility is sufficient.

Reporting

Traceable, engineer-reviewed outputs

Automate repetitive preparation where useful while preserving source traceability, limitations, technical commentary and responsible engineering review.

Responsibility boundary. RAUZ can provide monitoring strategy, independent review, data diagnostics and technical interpretation. Jurisdiction-specific statutory design, regulated professional sign-off, Engineer-of-Record authority, site installation and emergency operational authority must be separately defined for the actual project and location.

Technical collaboration

RAUZ can complement the teams already responsible for the facility.

Critical-facility work is interface-heavy. A practical delivery model defines what each party measures, owns, validates, interprets and acts on before data begin to flow.

Owner / operator

Defines operational sensitivity, access, data governance, escalation routes and the decisions the monitoring must support.

Designer / consultant

Provides design assumptions, ground model, structural context, trigger basis and engineering responsibility.

Local monitoring contractor

Installs, reads, maintains and verifies field instruments under the project’s approved procedures.

RAUZ

Connects agreed data, performs QA/QC and analytics, compares evidence and provides independent engineer-reviewed interpretation.

Potential technical interfaces may also include survey teams, InSAR providers, datalogger/IoT vendors, environmental specialists, geologists, local professional engineers and facility-control teams. Integration should follow approved data-access and cybersecurity requirements; RAUZ does not need unrestricted access to operational control systems to review exported monitoring evidence.

Frequently asked questions

Critical facilities monitoring — practical questions.

What is critical facilities monitoring in the RAUZ context?

It is the engineering review of ground, structural, environmental, survey and remote-sensing evidence around facilities where service continuity is important. RAUZ focuses on whether the data are reliable, what mechanism they may represent and what deserves further review.

Does RAUZ replace the facility BMS or DCIM platform?

No. BMS and DCIM platforms primarily manage facility systems and operations. RAUZ can sit alongside existing systems and focus on the relevant engineering evidence—such as settlement, groundwater, deformation, vibration, survey or InSAR—without forcing replacement of established operational platforms.

Can monitoring continue while the facility remains operational?

Often yes, but access, installation method, communications, cybersecurity, maintenance windows and operational constraints must be coordinated with the facility owner. Remote or automated monitoring can reduce routine site access where the project arrangement supports it.

Does every critical facility need InSAR?

No. InSAR is useful where satellite geometry, surface coherence, spatial scale, temporal sampling and the decision question make it appropriate. It should be treated as complementary evidence, not as an automatic substitute for site instrumentation or survey.

Can RAUZ analyse data from an existing monitoring contractor?

Yes, where the client has the right to provide the data and the exports contain enough metadata, baseline and project context for a defensible review. RAUZ is designed to work with existing field-delivery arrangements.

Does RAUZ set universal trigger values?

No. Trigger criteria should follow the project design, asset sensitivity, ground conditions, monitoring uncertainty, construction stage and the requirements of the responsible engineer or owner. Generic values should not be copied from unrelated projects.

What information is useful for an initial technical discussion?

A monitoring plan, recent reports, raw or exported time-series data, trigger criteria, relevant drawings, geotechnical information, construction sequence and a short explanation of the concern or decision to be supported are usually a useful starting package.

Can RAUZ review a portfolio of critical facilities?

Yes. A portfolio can use common data-quality, reporting and review rules while preserving the site-specific ground model, thresholds, instrumentation and responsibility structure for each facility.

Official public references

Sources used for this technical discussion.

These sources provide the official regulatory, resilience, monitoring or case-study context used on this page. Third-party references do not imply a commercial relationship with RAUZ.

  • CISA — Critical Infrastructure Security and Resiliencecisa.gov ↗
  • European Union — Directive (EU) 2022/2557 on the resilience of critical entitiesEUR-Lex ↗
  • UK National Protective Security Authority — Critical National Infrastructurenpsa.gov.uk ↗
  • World Health Organization — Climate-resilient and environmentally sustainable health care facilitieswho.int ↗
  • World Health Organization — Climate-hazard vulnerability checklists for health care facilitieswho.int ↗
  • IAEA — Geotechnical Aspects in the Siting and Design of Nuclear Installationsiaea.org ↗
  • Copernicus Land Monitoring Service — European Ground Motion Serviceland.copernicus.eu ↗
  • Fugro — GroundIQ® hyperscale data-centre ground-risk case studyfugro.com ↗
  • Sixense — University of Virginia Rotunda monitoring case studysixense-group.com ↗
  • Trimble — Structural stability monitoring solutionstrimble.com ↗
  • Bentley Systems — Data centre site intelligence, geotechnical analysis and digital twinsbentley.com ↗

Technical lead: Dr. Xuefeng (Jason) Nong — Founder of RAUZ. Project-specific advice should be based on the actual site data, design documents and applicable local requirements.

Start a technical discussion

Planning monitoring for a critical facility?

Send the project brief, monitoring plan, available ground information, existing report or a sample dataset. RAUZ can help define the monitoring question, review the evidence chain and identify where independent interpretation, QA/QC, InSAR or automated reporting may add value.

Scroll to Top