Canal diversion is a critical link in water resource allocation, agricultural irrigation, and regional water supply.
For water resource management units, the diversion process is far more complex than simply "opening the gates."
Different intake points correspond to different management scopes, control requirements, and water level conditions. When water levels exceed permitted ranges, monitoring data fluctuates abnormally, or alerts remain unattended for extended periods, the complexity of daily supervision and scheduling work increases significantly.
In the past, this type of work relied heavily on manually reviewing monitoring reports, phone communication, and on‑site verification.
When the number of intake points is large and monitoring data is continuously updating, management personnel not only need to identify anomalies from vast amounts of data, but also need to further confirm:
- Which intake point has an anomaly?
- Has the actual water level exceeded the upper limit, or fallen below the lower limit?
- Which management station does it belong to?
- When did the alert occur?
- Has it been resolved?
From "detecting an anomaly" to "locating the object," and then to "verifying data and follow‑up handling," there are often multiple information lookup steps in between.
To address this type of business need, the platform has built a Canal Diversion Exceedance Alert function. It aggregates real‑time monitoring data from each intake point, automatically makes judgments based on configured upper and lower thresholds, and presents anomaly information in a centralised manner through statistical cards, lists, maps, alert details, and scrolling prompts.
Its core purpose is to further transform the data supervision process — which previously relied on continuous manual attention — into:
Real‑time Monitoring → Automatic Judgment → Centralised Alerting → Rapid Localisation → Detail Verification → Follow‑up Handling
Enabling canal diversion supervision to gradually shift from "manually searching for anomalies" to "anomalies proactively presented."
01 Why Canal Diversion Supervision Needs to Move Beyond "Viewing Data" to "Viewing Anomalies"
In cases where water level monitoring equipment has already been deployed, management personnel do not actually lack data.
The real question is:
How to more quickly identify changes worth attention from continuously generated monitoring data.
For example, a management area may have multiple intake points distributed across it.
Each intake point has its own real‑time water level, and may also correspond to different permitted ranges and supervision requirements.
If management personnel primarily rely on reviewing reports line by line, the actual workflow often becomes:
Check monitoring station → Check water level → Compare against thresholds → Determine if anomalous → Find the responsible management station → Contact relevant personnel → Continue monitoring changes
As the number of monitored objects increases, this approach places high demands on personnel's ability to continuously pay attention to data.
The role of an alert mechanism is to hand over the repetitive judgment work to the system.
Based on the upper and lower water level limits configured for each intake point, the platform continuously evaluates real‑time monitoring data.
When a monitored value triggers the corresponding conditions, the system generates an active alert and organises the alert object, time, type, level, measured data, and triggering threshold information in a unified manner.
This way, what management personnel see first is no longer a large volume of raw monitoring values, but rather:
Where current canal diversion anomalies requiring attention exist.
This is the fundamental logic behind the design of the Canal Diversion Exceedance Alert function.
02 An Alert Dashboard That First Answers "What Is Happening Now"
Upon entering the Canal Diversion Exceedance Alert page, the first thing presented is an overview dashboard of all alert information.
The dashboard is not simply displaying a few sets of numbers — it brings together:
- Alert statistics
- Related function entry points
- Map alert points
- Management station categories
- A pending alert list
All organised within a single business interface.
For scheduling and on‑duty personnel, this page allows them to first establish an overall understanding of the current alert status, and then drill down further as needed.
Left‑side statistics: How many alerts are there currently, and what are the main types?
The left side of the dashboard features an alert statistics area.
The platform displays alerts by type:
- All alerts
- Canal Diversion Exceedance
- Other alert categories
While simultaneously showing the corresponding count for each type.
Management personnel can view the current total alert volume and the proportion of canal diversion exceedance events without needing to navigate to multiple business pages.
After clicking "View All" or a specific alert type card, the page will also dynamically update based on the current filter conditions.
Correspondingly: the management station list and pending alert list will update in sync with the filter conditions.
At the same time, the counts on the statistical cards will refresh along with the alert data.
This means the statistics area serves not only as a "displaying numbers" function — it also acts as a quick filtering entry point for the entire alert dashboard.
03 How Are Alerts Determined? Clarifying the Rules First
For an alert system to truly participate in business supervision, an important prerequisite is:
Business personnel need to understand why the system is alerting.
If they can only see a red or yellow alert indicator without being able to understand the triggering conditions, the alert information can hardly further support actual business judgment.
Therefore, the platform provides a "View Alert Rules" entry point in the alert statistics area.
After clicking, users can view the currently enabled alert rules.
The list displays:
- Alert type
- Rule name
- Associated object
- Object type
- Alert cycle and other information
Through this content, business personnel can first understand which rules are currently enabled in the system, and which business objects each rule applies to.
If further understanding of a specific rule is needed, users can click "View" in the list to enter the rule details.
The rule details further display:
- Rule status
- Judgment parameters
- Remarks
For the canal diversion exceedance business, this step helps business personnel clarify the judgment basis behind the current alert, rather than only seeing a final alert result.
04 Different Intake Points Have Different Conditions — Alert Thresholds Need to Be Configured Separately
Canal diversion management cannot easily be covered by a completely uniform water level standard across all intake points.
Different intake points vary in location, engineering conditions, and supervision requirements, so alert judgment needs to be applied to specific monitoring objects.
The platform provides alert threshold management capabilities.
Upon entering the Canal Diversion Exceedance Threshold Settings window, the system displays the corresponding configurations organised by intake point.
These include:
- Affiliated management station
- Monitoring station name
- Whether alerting is enabled
- Whether it is a key focus point
- Lower water level limit
- Upper water level limit
Management personnel can decide whether to enable alerting for specific intake points and maintain the corresponding upper and lower water level limits.
Thresholds do not need to be configured on both sides simultaneously.
In actual business scenarios, some intake points may focus more on the maximum allowable water level, while others may focus more on the minimum water level.
Therefore, the platform supports setting a single‑side threshold only.
For example:
- Setting only the upper water level limit focuses judgment on whether the upper limit is exceeded.
- Setting only the lower water level limit focuses judgment on whether the lower limit is fallen below.
If both upper and lower limits are configured simultaneously, the system will further validate:
The lower water level must be less than the upper water level.
Through basic configuration validation, unreasonable thresholds are prevented from entering the actual alert judgment process.
After configuration is completed and saved, subsequently generated real‑time monitoring data will participate in canal diversion exceedance judgment according to the latest configuration.
This way, alert rules are no longer just a fixed set of logic at the platform level, but can be further applied to specific intake points.
05 From "Viewing Alerts by Type" to "Viewing Alerts by Management Station"
For water conservancy management business, different roles often focus on different information scopes.
Platform‑level scheduling personnel may need to oversee all alerts, while specific management station staff typically focus more on the intake points within their own area of responsibility.
Therefore, in addition to alert type statistics, the dashboard also provides an alert list categorised by management station.
The list directly displays:
Management station name + current alert count.
This approach forms a different business perspective compared to filtering by alert type.
The former answers:
What types of alerts are currently occurring?
While categorisation by management station further answers:
Which management stations currently have alerts, and how many does each have?
Management personnel can therefore quickly locate their responsible management station, reducing the process of repeatedly searching through all alert information.
06 Pending Alerts Displayed Centrally — Making Current Anomalies Easier to See
After detecting an anomaly, the next step is to clarify:
Which alerts currently still require attention?
Therefore, the right side of the dashboard features a pending alert list.
The list displays by time:
- Management station
- Alert time
- Alert type
- Alert content
This section of information leans more toward specific events.
Statistical cards tell management personnel "how many," while the pending list tells management personnel: which specific ones.
For on‑duty personnel, they can move directly from the overall alert situation into individual events.
By clicking "Details" on a specific record, the corresponding alert detail window can be opened.
Through this approach, current anomalies requiring attention do not remain only at the statistical number level, but can continue into specific business objects and monitoring data.
07 Entering Alert Details to Determine Exactly "How Much Exceedance and Where It Occurred"
When actually conducting business verification, management personnel ultimately need to return to specific data.
Therefore, the alert detail window centrally displays the core information of a single alert.
For canal diversion exceedance alerts, the most critical set of relationships is:
Measured Value ↔ Triggering Threshold ↔ Upper and Lower Water Level Limits
Management personnel can directly compare the current monitoring data against the configured thresholds.
From this, they can determine: Is the current situation an upper limit exceedance, or a lower limit drop?
As well as when the anomaly specifically occurred, which object it corresponds to, and what the current status is. If the alert has been resolved, the corresponding resolution time can also be viewed.
This way, the alert details do not merely tell management personnel "an anomaly occurred here," but further provide specific data basis for on‑site verification, scheduling adjustments, and subsequent closed‑loop handling.
08 From List to Map: Anomalies Need to Be Known Not Just by "What" but Also by "Where"
For canal and intake point supervision, spatial location is itself important business information.
When multiple intake points experience anomalies simultaneously, viewing object names through a table alone may not be enough to quickly determine which areas the alerts are concentrated in.
Therefore, the platform further converts current active alerts into alert markers on a map.
Each alert point is labelled with the corresponding alert object name, and displays the corresponding icon based on alert level.
Scheduling personnel can directly view from the map:
- Where are the current alert points distributed?
- Which areas have relatively concentrated alerts?
- Which points require key attention?
After clicking an alert marker on the map, the same alert details as in the list can also be opened.
This creates a linkage between: Spatial Location → Alert Object → Specific Business Information.
For smart water conservancy business involving canals, reservoirs, intake points, and other objects with clear spatial attributes, this type of spatial presentation can establish a more intuitive connection between monitoring data and actual management objects.
09 During Continuous Dashboard Monitoring, Scrolling Prompts Reduce Alert Oversight
A typical usage scenario for smart water conservancy dashboards is continuous display in dispatch centres or duty stations.
In this situation, staff do not continuously click through pages — instead, the dashboard itself needs to continuously communicate the current anomaly status.
Therefore, the platform features a scrolling alert prompt bar at the bottom of the dashboard.
Based on current active alerts, the system automatically generates prompt content such as: "Alert occurred at [Management Station] + Alert occurrence time," and displays it through continuous scrolling.
At the same time, the bottom scrolling prompt maintains source‑synchronised refreshing with: map alert markers, left‑side statistics, and the right‑side alert list.
In other words, the same active alert is not maintained separately across multiple modules — it is the same alert information presented across different display areas.
This design is better suited for continuous dashboard overview scenarios, enabling on‑duty personnel to maintain awareness of newly occurred or unresolved canal diversion exceedance events without needing to actively enter detail pages.
10 What Supervision Problems Does Canal Diversion Exceedance Alerting Specifically Solve?
From a business value perspective, this set of functions is primarily reflected in two aspects.
First, making anomalies more centralised and easier to discover.
Through: Statistical Cards + Management Station Category List + Pending List + Map Alert Markers
The platform presents the current canal diversion exceedance situation from different dimensions in a centralised manner.
The core change is transforming the original:
"Searching for anomalies from monitoring data"
Into:
"The system identifies anomalies first, then management personnel conduct focused verification of anomalies."
Thereby shortening the anomaly discovery process.
Second, enabling alert information to further support verification and handling.
Alerting is not the endpoint.
True water resource supervision also needs to know why the anomaly occurred, on what object, how long it has persisted, and where to begin verification.
The platform incorporates real‑time monitoring values, upper and lower thresholds, alert levels, occurrence time, resolution time, and other information uniformly into alert details and related records.
Management personnel can quickly drill down from a single prompt on the dashboard to a specific intake point and view the corresponding data.
When on‑site verification, scheduling adjustments, or subsequent process tracing is needed, there is no need to search for event context across multiple systems again.
Alerts therefore evolve from simple "reminder information" into an information entry point connecting: Real‑time Monitoring — Business Judgment — Problem Verification — Scheduling Handling.
Final Thoughts
Smart water conservancy construction is not simply about displaying more monitoring data on screens.
As sensing devices continue to increase, the real problem that needs to be solved is gradually shifting from: Can we see the data? To: Can we timely discover problems from the data and quickly enter the handling workflow?
Canal diversion is no different.
Real‑time water level data solves "knowing what the current value is," while the alert mechanism further solves: When is it worth paying attention? Where needs attention? And why does it need attention?
By aggregating real‑time monitoring data from intake points, configuring upper and lower thresholds for different objects, and combining statistical cards, management station categories, pending lists, alert details, map markers, and scrolling prompts, canal diversion supervision can form a more coherent anomaly discovery and verification process.
Its value does not lie in simply adding an alert module, but in further connecting what was previously scattered: Data Viewing, Threshold Judgment, Anomaly Discovery, Spatial Localisation, and Business Verification.
For daily duty monitoring, diversion scheduling, and water resource supervision, this capability enables management personnel to devote more energy to anomaly events that truly require attention, making monitoring data serve specific management work more directly.
Top comments (0)