Skip to main content

Monitor · Assess · Warn · Respond

SINOMACRO CloudSafety Monitoring & Early Warning Cloud Platform

From monitoring data to warning and response

The Safety Monitoring & Early Warning Cloud Platform connects multi-source monitoring, risk assessment, graded warnings and response tracking. Field data, trigger evidence, notification acknowledgements and response records are organized around each event, with project-specific inputs, rules and channels.

Command Center: network map, monitoring-point status and live warnings; English prototype interface with simulated data
Interface example · Demonstration data
Multi-source
Compare changes on a shared timeline
Four levels
Blue, yellow, orange and red warnings
Traceable
Review data, conditions and rule versions
Response tracking
Notify, acknowledge, act and review

Platform features

Understand changes. Review the evidence. Follow the response.

The following describes the platform’s functional design using demonstration interfaces. Screens, scenarios and values are simulated. Available functions, analysis models and notification channels are subject to project configuration and delivery confirmation.

01

Compare multiple data sources to understand the sequence of change

Locate a hazard site on the map and review its monitoring points, device connectivity and historical data. Compare rainfall, soil moisture, surface displacement and subsurface displacement on a shared timeline. Depth profiles and correlation analysis help assess the order, lag and persistence of changes.

Multi-source monitoring: rainfall, soil moisture and displacement on a shared timeline; simulated data
Interface example · Demonstration data · Open image to view details
02

Configure graded rules and review how warnings are triggered

The rule design covers thresholds, changes, rates, persistence, combined conditions and rainfall intensity–duration conditions. Configure blue, yellow, orange and red warnings to match the project response plan. Templates, historical replay and version records help review trigger times, notification volume and rule changes.

Graded warning rules: combined conditions, persistence, notification actions and historical replay; simulated configuration
Interface example · Demonstration data · Open image to view details
03

Make the evidence behind each warning available for review

Review abnormal readings, matched conditions, relevant curves and analysis results together. Check data quality, actual time intervals and model applicability before calculation. Correlation and extrapolation support professional assessment; measured and predicted information are identified separately. AI explanations do not determine warning levels.

Subsurface displacement: resultant and X/Y depth profiles compared across epochs; simulated data
Interface example · Demonstration data · Open image to view details
04

Track notification, acknowledgement and response

Configure responsible personnel and notification channels by warning level, and track sending, delivery receipts and acknowledgements. Unacknowledged events can prompt repeat reminders or escalation as configured. A timeline connects triggers, notifications, acknowledgements, actions and clearance review. On-site broadcasting requires compatible equipment; field actions follow the project response plan.

Warning response: trigger evidence, notification receipts and response timeline; simulated scenario
Interface example · Demonstration data · Open image to view details

Applications

Typical applications

Multi-parameter slope and landslide monitoring

Dams and hydraulic structures

Bridges, tunnels and building structures

Distributed sites and multi-project warning management

Platform functions

SINOMACRO Cloud Platform functions

SINOMACRO Cloud Platform functions
Data access and visualization
Access architectureBrowser/server (B/S) architecture; cloud deployment
Monitoring inputsRainfall, soil moisture, surface/subsurface displacement, water level, tilt and cracks, according to connected devices
Project overviewHazard-site map, monitoring points and device status; data organized by project
Curve viewsMulti-parameter comparison on a shared timeline, historical curves, subsurface displacement profiles and time histories at selected depths
Remote configurationRead and set supported device parameters, such as sensor address, data-update rate and baud rate
Warning rule design
Condition typesThresholds, changes, rates, persistence, combined conditions and rainfall intensity–duration
Levels and actionsBlue, yellow, orange and red; thresholds, durations and responses follow the project plan
Rule associationRules are associated with monitoring points and maintained through device replacement
Rule managementScenario templates, historical replay, version records and rollback
Historical replayReview trigger times, event counts and notification volume for configured rules using historical data
Assessment and data limitations
Data qualityCheck missing data, spikes, device status and data validity
Rate calculationDisplacement change divided by actual elapsed time, retaining timestamps and consistent units
Correlation analysisCompare inputs, correlation metrics and response lag; correlation alone does not determine a warning
Model useSubject to data completeness, parameters and applicability; criteria such as tangent-angle thresholds require project-specific validation
Information sourcesMeasured data, weather forecasts and extrapolated trends are identified separately
Supporting analysisTrend analyses such as the Saito method support professional assessment; AI assists explanation and reporting, without determining warning levels
Notification and response design
Notification configurationRecipients and channels configured by warning level
Delivery and acknowledgementTrack sending, delivery receipts and acknowledgement by responsible personnel
Overdue follow-upRepeat reminders or escalated notifications, as configured for the project
On-site broadcastingRequires compatible broadcasting equipment; notifications and equipment receipts are tracked
Response recordsTimeline of trigger evidence, notification, acknowledgement, response progress and clearance review
Device-triggered reportingRequires a supported device trigger; reporting latency depends on the device and field communications

Product support

Documents & selection

Contact our technical team for current product information and project configuration.

Discuss your monitoring requirementsOpen monitoring platform (Chinese)

Frequently asked questions

Which monitoring data can be connected?

Depending on device and interface configuration, inputs may include rainfall, soil moisture, water level, surface and subsurface displacement, tilt and crack measurements. Data fields, sampling rates and remote settings require project-specific confirmation.

Are warning levels and thresholds fixed?

Warnings use blue, yellow, orange and red levels. Variables, thresholds, calculation windows, persistence conditions and response actions are configured for the monitored asset, historical data and project response plan. Demonstration angle ranges and values are not universal criteria.

How is a warning followed through to a response?

The workflow design includes level-based notifications, sending and delivery records, acknowledgement by responsible personnel, overdue reminders or escalation, response tracking and clearance review. Channels and broadcasting equipment are configured for the project; field actions follow its response plan.

Can models or AI directly predict failure time and probability?

Extrapolation and stability analysis depend on suitable data, parameters and model applicability, and only support professional assessment. The proportion of unstable model samples is not a validated probability of a disaster in the next 24 hours. AI assists explanation and reporting without determining warning levels.

Do these screens show a measured project or a delivered product interface?

The illustrated interfaces demonstrate platform functions. Scenarios, data, rules and warning events are simulated; they are not field case evidence or validated prediction performance. Functions, deployment, redundancy, models and channels are subject to the project specification and delivery confirmation.