Sustained rainfall is followed by rising soil moisture and faster slope movement. The team needs to establish where the change is occurring, whether it persists and what evidence justifies an alert. Once an alert is issued, they also need to know who has received it and what action follows.

This walkthrough uses a simulated 30-day sequence at the Jianshanying landslide site to explain how SINOMACRO Cloud Monitoring Software connects monitoring records, assessment, tiered alerts and response tracking.

All screens, measurements and alerts in this walkthrough are simulated examples of the platform design. Project use depends on the installed instruments, available data and response plan. Figures retain the original Chinese interface labels.

1. Locate the change and open the supporting data

The overview map shows monitoring sites and their current alert states. In this example, Jianshanying carries an orange alert. Its map marker opens details of the hazard, monitoring points, instrument counts, online status and nearby exposed assets.

From there, users can open a monitoring point and inspect its readings. Managers see project status, operators find the locations requiring attention, and technical staff review the corresponding instruments and measurements.

Figure 1. Simulated example: Site overview and individual monitoring-point details.
Figure 1. Site overview and monitoring-point details (simulated).

2. Put the measurements on the same timeline

Early in the simulation, rainfall raises soil moisture temporarily, then moisture falls without clear displacement acceleration. The configured alert conditions are not met, and recording continues.

Later rainfall is sustained. Moisture remains elevated, surface movement accelerates and the measurements at depth show changes requiring review.

A shared timeline brings rainfall, moisture, surface movement and subsurface displacement together. Engineers can examine the order of changes, delayed responses and whether a trend persists. Depth profiles add information about where the internal deformation occurs.

Figure 2. Simulated example: Rainfall and displacement at different locations on a shared timeline.
Figure 2. Rainfall and displacement on a shared timeline (simulated).

Correlation tools can compare rainfall with displacement, or groundwater level with subsurface movement. The coefficient r, fit statistic R² and time lag describe the relationship in the selected data. They do not establish a cause or independently trigger an alert; the configured conditions still govern that decision.

Figure 3. Simulated example: Time histories, correlation measures and response lag.
Figure 3. Time histories, correlation measures and response lag (simulated).

3. Define alert conditions that can be checked and replayed

In the simulation, the alert progresses from yellow to orange as the changes persist. Each transition is linked to measurements, duration and the configured rule.

Six condition types

Condition What it evaluates Example configuration
Value threshold A reading above or below a limit Moisture, water level or tilt against project limits
Change over a window Accumulated change in a defined period Displacement or crack-opening increment
Rate of change Speed of change over an interval Rates over 1 h, 6 h or 24 h windows
Persistence Continued occurrence of a condition Consecutive packets, windows or a set duration
Combined conditions Several conditions evaluated together Displacement, moisture and water level joined by AND/OR
Rainfall intensity–duration Duration of elevated rainfall Measured intensity over a specified period

A rule could require a moisture threshold, a displacement-rate threshold and persistence, then assign a blue, yellow, orange or red alert with notification actions. Set limits and durations using site conditions, historical records and the response plan.

The rule records its points, metrics, units, comparisons, combined conditions, duration, alert level, repeat interval and notification strategy. Associating rules with monitoring points allows those relationships to be maintained when a device is replaced.

Figure 4. Simulated example: First part of the original rule page: seven example rules and combination settings.
Figure 4. Seven example rules and combination settings (simulated).

Start from a template, then replay the rule

Templates are available for multi-parameter landslide monitoring, rainfall-induced landslides and unstable rock. Adapt each template to the installed measurements and project limits before use.

Historical replay applies a proposed rule to a chosen period of recorded data. Review the number and timing of triggers and the resulting notification volume. Version records allow changes to be reviewed and rolled back.

Figure 5. Simulated example: Templates, persistence settings, alert-level actions, historical replay and saving.
Figure 5. Rule templates, alert-level actions and historical replay (simulated).

Keep measured site rainfall, forecast rainfall and regional reference rainfall clearly labeled. Weather information adds context; gridded estimates are not direct measurements at the monitoring point.

Check input completeness

The model library identifies each method’s purpose, input completeness and availability. Saito analysis, for example, remains unavailable when the accelerating record is insufficient. The demonstration screen requires at least seven days of continuous acceleration; this is an example setting, not a universal standard.

Figure 6. Simulated example: Tangent-angle and Saito models, parameter completeness and persistence logic.
Figure 6. Model inputs, availability and persistence settings (simulated).

The purpose of the rule workflow is to make the trigger evidence reviewable and every change traceable.

4. Understand what each analysis can tell you

Calculate rate from elapsed time

The design calculates v = (current displacement − previous displacement) / actual elapsed time. Routine readings and additional event reports can have different intervals. Use the recorded timestamps and consistent units when calculating rate.

Check for missing observations, isolated spikes, invalid readings and instrument faults before using a series as model input. One anomalous point does not establish sustained deformation.

Improved tangent angle

This method normalizes displacement against time. A segment with approximately constant rate establishes a reference rate v₀. Cumulative displacement S is converted to T = S / v₀, followed by α = arctan(ΔT / Δt). Over a common calculation window, the result compares the current deformation rate with the reference rate.

The method is described in the improved tangent-angle study by Xu et al.. The demonstration uses the following stages:

Improved tangent angle α Demonstration stage Demonstration alert level
Approximately 45° Constant-rate deformation Blue: attention
45° < α < 80° Initial acceleration Yellow: caution
80° ≤ α < 85° Intermediate acceleration Orange: warning
α ≥ 85° Increasing acceleration / approaching failure Red: alarm

These ranges explain the demonstration grades. Applying them to a site requires an assessment of the deformation mechanism, reference segment, calculation window and response plan. The conditions behind the thresholds must be checked. The Xinhua landslide study discusses deformation and warning criteria in a project setting.

Figure 7. Simulated example: Model reading, stage criteria, trend and references; site-specific validation is required.
Figure 7. Model readings, stage criteria and trends (simulated).

Saito and inverse velocity

Saito analysis estimates a possible failure time from accelerating creep. Inverse velocity (INV) examines 1/v against time. Where the acceleration behavior supports an approximately linear trend, fitting 1/v = a·t + b gives an extrapolated intercept of t_f = −b/a.

The result depends on data quality, the fitting window and site conditions. Update the estimate as readings arrive and express it as a time range. Carlà et al.’s guidance explains processing and limitations.

Within this platform design, explicit rules and improved tangent angle contribute to alert-level decisions. Saito and the planned INV analysis assist technical assessment. AI helps explain the information and assemble reports. These supporting tools do not directly set the alert level.

Factor of safety and uncertainty

Where geological and monitoring inputs are sufficient, an infinite-slope model is used to examine factor of safety Fs. The inputs include effective cohesion, friction angle, slope angle, slip-surface depth, soil unit weight and pore-water pressure.

Monte Carlo sampling explores Fs under specified input distributions. The fraction of samples with Fs < 1 describes instability within that model and its assumptions. It does not establish a landslide probability for the next 24 hours. A prediction over a stated period would also require time-varying inputs and field validation.

Figure 8. Simulated example: Indicators, analysis and timing in an alert explanation.
Figure 8. Indicators, analysis and timing behind an alert (simulated).
Figure 9. Simulated example: Risk card showing 23.5% and a time interval; this is not validated 24-hour failure prediction.
Figure 9. Risk card showing 23.5% and a time interval; not validated 24-hour failure prediction (simulated).

Rainfall response and trend projection

Effective rainfall and correlations at different lags help examine the delay between rainfall and movement. The design calculates Eₜ = Pₜ + k·Eₜ₋₁, with Pₜ representing rainfall in the current interval and k a configurable decay coefficient.

Further assessment may combine forecast rainfall, simplified infiltration and water-balance calculations, and displacement extrapolation. Forecast regions and dashed lines separate these estimates from observations. New measurements are used to update the estimates.

An alert explanation should identify the location of the change, the conditions met and the observations behind the decision.

5. Review events between routine readings

Crackmeters and other instruments with on-device event reporting can send additional records when their configured conditions are met. The mechanism and reporting delay depend on the model and communication conditions.

The interface places those events alongside routine readings and alert times so that their sequence can be examined. Historical observations, forecast rainfall and extrapolated trends remain distinguishable in the display.

This evidence can inform field checks, inspections and emergency preparation. The response itself follows the site conditions and project plan.

Figure 10. Simulated example: A red outlined circle marks an extra-report event for review.
Figure 10. Additional event report highlighted for review (simulated).

6. Track the alert through acknowledgment and response

The demonstration mobile page shows the location, alert level, triggering conditions and points requiring attention. Responsible staff can then acknowledge receipt.

The workflow assigns recipients and channels by alert level, records delivery and acknowledgment, and tracks response progress. Overdue acknowledgments can prompt repeat reminders or escalation. If field broadcast equipment is installed, its notification and receipt status can also be recorded.

The alert timeline records:

  • Trigger time and supporting measurements
  • Recipients and delivery status
  • The person who acknowledged the alert
  • Response progress and the review required before closure
Figure 11. Simulated example: Mobile alert details and acknowledgment progress.
Figure 11. Mobile alert details and acknowledgment progress (simulated).

7. Match the analysis to the available evidence

A site may measure only rainfall and surface movement, or also include subsurface displacement, moisture, groundwater and cracks. Those measurements determine which comparisons and analyses can be made.

The platform organizes displays, rules and correlation tools around the available data. Stability analysis additionally needs suitable geology and model parameters. Where inputs are insufficient, the design identifies what is missing rather than presenting a result without an adequate basis.

8. Use references within their stated scope

Standards address monitoring practice, data organization, communication and equipment testing. Research describes assessment methods. The project establishes the applicable parameters, warning thresholds and response procedures. Check the edition and scope of each reference before using it.

Reference standards

  • DZ/T 0460—2023, automated instrument monitoring and early warning for geological hazards: monitoring practice. Effective January 1, 2024. Official record.
  • DZ/T 0442—2023, database construction for geological-hazard monitoring and early warning: data organization. Effective November 1, 2023. Official record.
  • DZ/T 0450—2023, technical requirements for geological-hazard monitoring data communications: system integration. Effective January 1, 2024. Official record.
  • DZ/T 0439—2023, testing requirements for geological-hazard monitoring and early-warning equipment: equipment testing. Effective August 1, 2023. Official record.

Standard titles are summarized in English. Applicability and conformity must be assessed for each project.

Research methods

  • Xu Qiang, Zeng Yuping, Qian Jiangpeng et al., 2009: improved tangent angle and landslide-warning criteria, Geological Bulletin of China, 28(4), 501–505. DOI.
  • Xu Qiang, Dong Xiujun and Li Weile, 2019: integrated space–air–ground identification, monitoring and warning of major geological hazards, Geomatics and Information Science of Wuhan University, 44(7), 957–966. Journal article.
  • Saito (1969), tertiary creep and failure-time prediction, and Fukuzono (1985), inverse-velocity analysis: method history and references are covered in the guide below.
  • Carlà et al., 2017: inverse-velocity analysis for warning thresholds and prediction of landslides or structural collapse, Landslides, 14, 517–534. Journal article.

The illustrated sequence is locate the site → review the measurements → assess the change → issue a tiered alert → notify and acknowledge → track the response. The shared alert record lets each team member carry out their assigned role using the same evidence.

Contact us for a demonstration or a project configuration review.