DESC:FIELD

The present disclosure relates to a water management system that efficiently manages the distribution of water from Primary Tanks to Secondary Tanks, tailored to meet the specific user requirements. More particularly, the present disclosure relates to a system and a method for facilitating real-time management, continuous monitoring, and controlling water levels in each tank using advanced sensor technologies and data analytics. Water level management relies on a predefined threshold, which can be customized by a user through a dedicated mobile application allowing for personalized control including water control.

BACKGROUND

Water is a precious resource, and managing water effectively is crucial, especially in diverse settings such as industrial complexes, commercial complexes, condominiums, office campuses, hotels, resorts, and residential buildings.

In various regions of India, municipal water supply is often regulated to specific periods each day. However, the start and end times of this water supply are frequently unpredictable and not consistently adhered to. The uncertainty creates anxiety among users regarding when water will be available and for how long, disrupting personal schedules and leading to missed opportunities to collect water.

Numerous systems and methods are currently employed by individuals to manage water resources, but none can match the comprehensiveness and sophistication of the present disclosure. Many people have devised a makeshift solution by attaching a pipe to a tank at a level above which water would overflow. The other end of the pipe is directed to various locations like the kitchen, bathroom, bucket, or another visible spot. When the water begins to flow from the pipe, it serves as an indicator that the tank is full. A user must manually shut off the water supply to the tank to control the overflow of the water.

In some implementations, a primary tank with a pump sensor is used as a wired solution for water management. The primary tank receives water from the municipal corporation, individuals install a sensor connected to a pump. The sensor is programmed to activate the pump at an estimated time of the water supply (e.g., 6:00 am). If the sensor detects the water, it keeps the pump running to fill the water tank, else it would stop the pump and repeat the same activity after some time. However, Primary Tank with Pump Sensor method can be somewhat trial-and-error.

In some implementations, tank sensors are equipped with a wired sensor, usually four in number, placed at different levels (25%, 50%, 75%, and 100%). The tank sensors are connected to a module located near a pump's switch. The module uses indicator lights to show the water level range (e.g., 25-50% or 50-75%). If the water level reaches 100%, the module triggers an alarm to alert the user to switch off the pump. Conversely, when the water falls below 25%, it sounds like an alarm, prompting the user to turn on the pump. Some systems even allow for automated pump control through the module, eliminating the need for human intervention. However, the systems suffer from messy wires, which are vulnerable to damage by pets, monkeys, birds, or weather-related issues like thunderstorms. Additionally, tank sensor corrosion and scaling are common problems that can contaminate the water or lead to sensor malfunction.

In some implementations, wireless modules with wired sensors are the recent solutions that incorporate wireless modules to enable the transmission of data through GSM technology. However, even in these systems, the sensors themselves remain wired.

Water leakage in a facility can occur unintentionally from various sources, such as when a tap is left open, a flush malfunctioning, or an internal pipe burst. The water leakage not only damages the building structure but also results in water wastage, potentially affecting the other users reliant on the same water tank.

The water tanks are equipped with water management Devices to monitor their water levels. Under certain conditions, if the pump is activated, it will start filling the tanks. However, if the water supply is interrupted and the desired water level in the water tanks is not reached, the pump may remain on, which could lead to dry run of the pump and a potential burnout.

Despite the variety of system and methods are available for managing water tanks, each has their limitations and drawbacks, ranging from manual control in the makeshift "Jugaad" approach to the issues of wire maintenance, sensor corrosion, and scaling in more advanced wired systems. Therefore, a need still exists to provide a comprehensive and user-friendly alternative that leveraging state-of-the-art technology to overcome these challenges.

SUMMARY AND OBJECTS:

The present disclosure relates to a system and a method for facilitating real-time management, continuous monitoring, and controlling water levels in each tank using advanced sensor technologies and data analytics.

One aspect of the present disclosure relates to a water management system comprising: a supply sub-system configured to receive water from a municipal source; a distribution sub-system designed to enable the flow of water from a primary tank to a secondary tank; a utilization sub-system used to distribute water to various facilities; a communication system to receive data from the supply sub-system, the primary tank, and the secondary tank, to enable real-time monitoring and adjustments to maintain a desired water levels in the tanks.

The water management system is integrated with a user interface that allows end-users to monitor the individual consumption and receive alerts regarding maintenance needs or abnormal water usage patterns.

The supply Sub-system further comprising: a smart water flow device to continuously monitor and provide data on a water flow rate; a pump activated by a smart water plug in response to the commencement of the municipal water supply; a primary tank to store water received from the municipal water supply; a smart water level device to monitor the water level in the primary tank and to deactivate the pump when the tank is full or when the municipal water supply ceases, whichever occurs first. The primary tank is equipped with a water level sensor to monitor the water levels and control mechanisms, to regulate the inflow and outflow of the water based on the usage demand.

The communication system further comprises a public network of LoraWAN to facilitate data transmission between a master device and IoT devices including, a smart water flow device, a smart water level device, a smart water valve, wherein the master device utilizes the LoraWAN protocol for communication, enabling data transmission over the public network and providing a fallback to GSM technology when the public network is unavailable.

The distribution sub-system further comprising: a secondary tank configured to serve as an immediate reservoir to distributes water to various end nodes including apartments, rooms, bathrooms, restaurants, kitchens, and pantries; a pump operatively connected to the secondary tank and activated through the smart water plug when the water level drops below a predefined minimum threshold; a water level sensor integrated within the secondary tank (36) to continuously monitor the water levels.

The water level sensor is designed to monitor the water level and communicate with a control mechanism to activate the pump timely, ensuring the secondary tank is replenished whenever the water level drops below a predefined minimum threshold.

The pump is configured to use the smart water plug to refill the secondary tank until either the water level reaches a maximum threshold, or the water level of the primary tank drops below a minimum threshold.

The utilization sub-system further comprising: a smart water level device installed at the inlet of each end node to continuously monitor the flow rate of the water; a smart water valve capable of being manually controlled by a user through a mobile application or being automatically shut off the water supply based on a predefined configuration when the abnormal flow rate is detected; a facility wherein the end node use the water.

The utilization sub-system further comprising an algorithm to analyze the data flow from the smart water flow device to differentiate between a normal and an abnormal flow rate. The event of the abnormal flow rate being detected, the system is configured to trigger an alert to notify the user about a potential leak or unusual water consumption patterns.

The smart water level device, comprising: a water level sensor configured to continuously monitor the water level in a tank; a firmware programmed to implement a dual-layer management approach i.e., a firmware level and a server level management, for ensuring reliable data transmission. The smart water level device further comprises an auto- correct feature that allows subsequent reading to adjust automatically for any discrepancies caused by an erroneous value that may have triggered an action.

The firmware level management approach, comprising: a Minimum_Value threshold representing the lowest acceptable water level; a Maximum_Value threshold representing the upper limit of water level detection; a predefined Measurement_Interval dictating how frequently the smart water level device checks the water level to balance timely updates with power consumption efficiency; a Significant_Change_Level parameter defining the minimum change in the water level that must occur for the smart water level device to consider it noteworthy, thereby preventing unnecessary data transmission from minor fluctuations.

The server level management approach is further configured to: perform a Buffer Value Check by comparing a Check Value with the predefined Buffer_Value; perform a Tank Size Check by comparing the Check Value with the Tank_Size; implement an appropriate action if both the checks (i.e., Buffer Value and Tank Size check) are passed, including updating system status or notifying a user.

One aspect of the present disclosure relates to a method for monitoring and managing water usage in the utilization sub-system, the method comprising the steps of: continuously monitoring of water flow rates at each end node using a smart water flow device; analyzing the monitored data in real-time to identify an anomaly indicative of potential leaks or excessive water usage; triggering an automated response to a user based on a user-defined threshold and conditions related to the water usage; notifying the user when the anomalies are detected and providing options for manual or automatic intervention through a smart water valve.

Another aspect of the present disclosure relates to a method for performing checks to ensure accurate water level management in a tank using a smart water level device, the method comprising the steps of: continuously measuring a water level and applying checks including a firmware level checks and a server level checks, to filter out erroneous readings based on a predefined threshold; transmitting a validated reading to a server for monitoring the water usage; triggering an alert system that notifies a user when a critical threshold is reached or when erroneous readings are detected, enhancing the user awareness and system reliability.

Another aspect of the present disclosure relates to a mobile application for the water management system, the application comprising: a user interface to allow a user to manage and monitor the water supply remotely, providing a control from any location; a dashboard comprising various user-friendly features including a pumping station synchronization, a scheduling capability, a scenario management, a "Do Not Disturb" mode, a timer function, a dry run detection, a leakage detection, and a notification feature for managing and visually representing the water usage data, system status, and alerts in real-time; a notification system to alert a user to a significant event including a low water level, leakage detection, or scheduled maintenance;

The pumping station synchronization feature comprising: initiating a switch-on command for a pump via an operator application; receiving the switch-on command at a server, indicating that the pump requires activation; identifying a user associated with a notification device linked to the pump; dispatching a "Switch On" notification to the user to inform the user of the impending activation of the pump; identifying a smart water plug which is associated with the pump; checking for any specified delay; creating a schedule to switch on the pump after the specified delay is detected; switching on the pump immediately through the Smart Water Plug if no delay is specified, ensuring efficient management of pump operations.

The pumping station synchronization, further comprising switching off a pump through continuous operation of a Cron Service, which periodically checks for any scheduled switch-off events.

The Do not Disturb feature comprising: specifying a start time and an end time for the DnD window through a mobile application; determining whether the activation coincides with the user-defined DnD window; activation of the pump is halted, if the current time falls within the DnD period; automatically turn off the pump if it is already operational at the onset of the DnD period using a Smart Water Plug. The mobile application further comprises an alert mechanism that notifies users when a DnD period is about to commence or has been violated.

The mobile application further comprising a notification feature to inform the user when an action is taken regarding activation or deactivation of the pump, including the notifications for both switch-on and switch-off events related to the pump.

The Dry run preventive feature comprising: continuously operating a Cron Service to monitor activities of the pump and water levels 24 hours a day, 7 days a week; configuring the Cron Service with a threshold time duration representing a maximum allowable time for the water level to change after an activation of the pump; monitoring the water level every minute for each running pump associated with a Smart Water Level Device installed in a destination tank(s) including a Primary Tank and a secondary Tank; proceeding to calculate an elapsed time since activation of the pump; resuming monitoring by returning to the continuous operation after executing the shutdown procedure. The step of calculating the elapsed time includes if the elapsed time exceeds the threshold time duration, triggering an automatic shutdown of the pump to prevent dry running. The dry run is configured to ensure that the pump operates within the safe parameters by proactively managing the pump operations to mitigate the risks associated with the dry running.

The leakage detection feature of the water management system comprising: continuously monitoring the water levels and record water usage on an hourly basis; maintaining a database to store a water usage data over a period of 6 to 9 months which serves as a foundational resource for analytics; processing the collected data to create an average water usage profile segmented into 24 distinct intervals throughout the day; categorizing hourly water usage into a predefined levels, including Level 1: No water usage; Level 2: Up to 5% water usage; Level 3: 5-10% water usage, and so on; comparing an actual water usage with a stored pattern mapping to identify an anomaly indicative of a potential leak or inefficiencies; sending a signal to a smart water valve to interrupt the water supply when the leakage is detected; triggering an alert to notify a user about the potential leakage; allowing the user to manually close the water supply using the mobile app or configuring the smart water valve to automatically shut off the water supply.

The step of triggering an alert includes the Smart Water Level Device checking whether actual usage exceeds expected levels, and if actual usage within a given interval surpasses the expected level, and to trigger based thereon to notify the user of potential leaks.

One of the objects of the present disclosure is to maintain the optimal water levels between a primary storage tank and a secondary storage tank, ensuring a steady and an uninterrupted supply to an end node, which can be any end node (including apartments, rooms, bathrooms, toilets, kitchens, pantries, restaurants, and more).

Another object of the present disclosure is to provide real-time data on the water levels in each tank, ensuring that the users have up-to-the-minute information about their water supply.

Another object of the present disclosure is to provide a feature where users can set specific water level thresholds based on their unique requirements, allowing for a tailored approach to water management.

Another object of the present disclosure is to provide adaptable system to perform various installations, including scenarios where one primary storage tank supplies one secondary storage tank, one primary storage tank supplies two secondary storage tanks, two primary storage tanks supply one secondary storage tank, and more. Flexibility meets the diverse needs of different premises.

Another object of the present disclosure provides a feature where the users gain access to hourly water consumption patterns for each tank, empowering them to make informed decisions about water usage and conservation.

Another object of the present disclosure provides a feature to continuously monitor the water flow to each end node and can promptly identify abnormal usage patterns. Monitoring the water flow is essential for detecting potential leaks or wastage of water.

Yet another object of the present disclosure is to provide the feature of prompting alerts and notifications to the users. In the event of abnormal water usage, the system has the capability to alert users, providing timely notifications about potential issues. Users can take proactive measures to address leaks or wasteful consumption.

Yet another object of the present disclosure is to enhance water conservation, the system allows end users to cut off the water supply to end nodes based on alerts received through the mobile app. This feature puts control in the hands of the users, enabling them to respond quickly to potential issues.

A further object of the present disclosure is to provide a wide range of innovations, from battery-efficient sensors devices to a feature-rich mobile app, making the present disclosure a comprehensive and forward-thinking solution for effective water management.

The primary goal of the present disclosure is to prevent water outages and overflow or wastage of water through proactive monitoring and automated control mechanism.

For better understanding, the following components of the water management system according to the present disclosure are explained below:

1. Primary Storage Tanks: A primary storage tank(s) are the initial reservoirs where the water is stored after being sourced from a municipal supply. The water is generally not consumed directly from primary tanks. Typically, the primary storage tanks are located underground or at ground levels.

2. Secondary Storage Tanks: A secondary Storage Tank(s) are usually situated on the top floors of the buildings, providing water supply to various end nodes within the establishment. The secondary tanks serve as an intermediate reservoir that distributes the water to apartments, rooms, bathrooms, toilets, kitchens, pantries, restaurants, and other areas.

3. End Nodes: End nodes are the final destinations where the water is consumed, encompassing apartments, rooms, bathrooms, kitchens, pantries, restaurants, and more.

In some examples, Smart Water Sensor devices have been meticulously crafted for maximum battery efficiency. With the help of unique algorithm in a firmware, the battery life extends from 12 to 18 months, eliminating the need for a wired sensor. Furthermore, a wireless sensor is IP67 compliant, allowing the wireless sensor to operate effectively even in hot and humid conditions. Being wireless, it is not susceptible to corrosion, ensuring that the water sensors don’t compromise with the water quality.

In some examples, the Water Management System's mobile app introduces a range of unique features previously unseen in any existing water management systems:

In some examples, multiple scenarios are implemented for maintaining and controlling water flow. The water management system can be effortlessly configured for various water tank setups, such as one-to-one, one-to-multiple, or multiple-to-single tank configurations.

In some examples, a Do not Disturb (DnD) feature is introduced to prevent automatic activation of pumps during night-hours. A groundbreaking feature ensures that pumps do not activate during Do Not Disturb hours, eliminating disturbances in the neighborhood.

In some examples, a configurable timer with the pump provides a backup system in case the primary system fails, or the user forgets to manually switch off the pump in time.

In some examples, the system is equipped to detect instances where there is no water supply to a particular tank and automatically shuts off the pump to prevent pump burnouts.

In some examples, the app displays real-time hourly water consumption data, providing a user with valuable insights into their water usage patterns.

In some examples, users can monitor the hourly water level through the mobile app, enabling them to plan the scheduling of the pump activation more effectively.

In some examples, the Water Management System integrates various crucial components, including water level monitoring, pump operation, and individual facility flow control, all tied to specific conditions. This holistic approach to water management represents a significant advancement in the field.

In some examples, the system leverages artificial intelligence and big data analytics to detect water leakage within a facility. A User is alerted to potential issues, and users can even use the system's built-in features to cut off the water supply if necessary. This proactive approach of water management is a game-changer, enhancing both efficiency and water conservation.

BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS

The aforementioned objectives, features, and advantages of the present disclosure will be elucidated through an in-depth analysis, which will be accompanied by illustrative figures. These figures have been meticulously crafted to facilitate a comprehensive understanding of the various components and mechanisms that constitute this disclosure and wherein:

Fig. 1 illustrates a partial view of water management solution in a typical Eco system, in accordance with some examples of the present disclosure;
Fig. 1A illustrates a partial view of a supply sub-system, in accordance with some examples of the present disclosure;
Fig. 1B illustrates a partial view of a communication protocol, in accordance with some examples of the present disclosure;
Fig. 1C illustrates a partial view of a Distribution Sub-system, in accordance with some examples of the present disclosure;
Fig. 1D illustrates a partial view of a utilization of Sub-system, in accordance with some examples of the present disclosure;
Fig. 2A illustrates a system for performing firmware-level checks by the Smart Water Level Device in accordance with some examples of the present disclosure;
Fig. 2B illustrates a system for performing server-level checks by the Smart Water Level Device in accordance with some examples of the present disclosure;
Fig. 3 illustrates a method for optimizing the battery embedded within the Smart Water Level Device in accordance with some examples of the present disclosure;
Fig. 4 illustrates features of a mobile app for a water management system in accordance with some examples of the present disclosure;
Fig. 5 illustrates a user-friendly scenario feature in the mobile app in accordance with some examples of the present disclosure;
Fig. 6 illustrates a mobile app feature for pumping station synchronization, specifically for switching on the pump via Smart Water Plug in accordance with some examples of the present disclosure;
Fig. 7 illustrates a pump control mechanism featuring a "Do Not Disturb" (DnD) functionality in accordance with some examples of the present disclosure;
Fig. 8 illustrates a mobile app feature for dry run pumps in accordance with some examples of the present disclosure;
Fig. 9 illustrates a mobile app feature for detecting leakage in accordance with some examples of the present disclosure.

DETAILED DESCRIPTION

In general, for example, embodiments of the present disclosure provide systems, methods, and devices for effective water management. Aspects of the present disclosure will now be described in detail with reference to the drawings wherein, like reference numerals designate identical or corresponding elements.

Referring to Fig. 1, a partial view of a water management system 10 of the present disclosure is illustrated. The Water Management System 10 plays a pivotal role in maintaining optimal water levels between a supply sub system 12, a distribution sub system 14, and a utilization sub system 16 ensuring a steady and uninterrupted water supply to the end nodes (for example: apartments, rooms, bathrooms, toilets, kitchens, pantries, restaurants, and more). Water Management System 10 oversees and controls the water flow 20 from a municipal supply to the primary tank 26 and from primary tank 26 to secondary tank 36 for distribution of water to each facility 38, where the water will be used. The Primary Tank 26 serves as the storage point for the water received from the municipal corporation, and the secondary tank 36 is responsible for supplying water to each facility 38 for consumption of the water. The water in the secondary tank 36 is sourced from the primary tank present in the distribution sub-system 14.

Water management system 10 comprises of the following five IoT devices specially designed to continuously monitor and control the water levels in each tank.

Smart Water Flow:

The water management system 10 comprises a smart water flow 20. The Smart Water Flow 20 is an IoT device, specially designed to measure the rate of water flow in real-time and is installed at both the inlet of the Primary Tank 26 and the inlet of each facility 38. The smart water flow 20 utilizes a LoRaWAN protocol for communication and operates on battery power. The LoRaWAN protocol is a low-power, wide area networking protocol that wirelessly connects devices to the internet and manages communication between-end-node devices and network gateways.

Smart Water Level:

The water management system 10 comprises a Smart Water Level Device. The Smart Water Level Device is an IoT device, designed to gauge or measure the water level in the tanks and is installed on each tank. The Smart Water Level Device is installed on each tank and utilizes LoRaWAN protocol for efficient long-range communication, while operating on low power consumption to ensure flexibility and ease of installation.

A Smart Water Level Device continuously measures water levels in real time. During the tank filling process, disturbances such as splashing, and turbulence can occur due to the water pressure and the operation of a float valves. The disturbances may lead to inaccurate sensor readings, potentially triggering erroneous actions from the connected server. To mitigate these issues, the present disclosure implements a dual-layer management approach to ensure reliable data transmission, i.e., a firmware level management and a server level management within the Smart Water Level Device.

A first level check is programmed on the firmware level within the Smart Water Level Device that ensures accurate measurement and reporting of water levels in tanks. The first level check is critical for maintaining the integrity of the data transmitted to the server and for ensuring reliable operation of the water management system 10.

The Smart Water Level Device is designed to measure water levels in tanks and specific set of rules are programmed into the Smart Water Level Device firmware to ensure only accurate readings are sent to the server. The Smart Water Level Device is programmed to recognize two critical thresholds including a Minimum_Value and a Maximum_Value. The Minimum_Value represents the lowest acceptable water level that can be detected by the Smart Water Level Device, and the Maximum_Value signifies the upper limit of water level detection, above which overflow conditions may occur, indicating potential malfunction or risk of flooding. The Smart Water Level Device is also configured with a predetermined Measurement_Interval, dictating how frequently the Smart Water Level Device checks the water level. The interval of measuring water level is essential for balancing timely updates with power consumption efficiency. Another crucial parameter is a Significant_Change_Level, which defines the minimum change in the water level that must occur for the Smart Water Level Device to consider it noteworthy. The Significant_Change_Level parameter prevents unnecessary data transmission caused by minor fluctuations which do not reflect meaningful changes in a tank status.

Now referring to Fig. 2A, illustrates a system for performing firmware-level checks by the Smart Water Level Device including the minimum value check, the maximum value check and significant change check. The firmware check initiates with the Smart Water Level Device determining a new water level reading (denoted as a Current_Value) at step 200. At step 202, upon taking the new reading “Current_Value”, the Smart Water Level Device compares the Current_Value against the Minimum_Value. After evaluating the current and minimum value, the smart water level device checks if the current value is below the minimum value at step 204. If the Current_Value is less than the Minimum_Value, indicating that the value is wrong. In this scenario, the reading is ignored to prevent erroneous data transmission that could mislead the users about an actual water level at step 206. Ignoring such reading helps to maintain the system integrity and prevents unnecessary alerts or actions based on potentially faulty or inaccurate data. Conversely, if the current value is not below the minimum value, the Smart Water Level Device compares the Current_Value against the Maximum_Value at step 208. After evaluating the current and maximum value, the smart water level device checks if the current value is above the maximum value at step 210. The step of Check Maximum Value ensures that a reading do not exceed a defined upper limit, which could indicate overflow or other issues. If the Current_Value exceeds the Maximum_Value, the reading is ignored to avoid sending misleading information to a server at step 212. By implementing the maximum check, the unnecessary responses from the users or an automated systems based on inaccurate data are effectively mitigated. At step 214, after successful checking of maximum value, the final check involves determining whether a significant change has occurred in the water levels, thereby conserving battery life and reducing unnecessary data transmission. The device compares the Current_Value with a previously recorded value (Last_Value) from the last measurement of the water levels. At step 216, the Smart Water Level Device checks if the absolute difference between the Current_Value and the Last_Value meets or exceeds a predefined threshold known as Significant_Change_Level. If the difference is smaller than the Significant_Change_Level, it indicates that any change in the water level is negligible and ignores the reading to prevent unnecessary triggering of alerts and conserving battery power at step 218. Conversely, if the difference meets or exceeds the threshold, indicating a meaningful change in the water level, the new reading is relayed to the server for further processing and monitoring at step 220.

Thus, the firmware checks effectively ensure that only relevant and accurate data regarding water levels are transmitted by the Smart Water Level Device. By implementing checks for both minimum and maximum values, as well as assessing significant changes, the system enhances reliability while optimizing performance and battery life. This approach minimizes false readings and ensures that users receive only critical information about their water management system 10.

The Smart Water Level Device is designed to effectively filter out erroneous readings caused by environmental factors like splashing or turbulence. This ensures that only reliable data is sent to the server for monitoring and analysis. For better understanding, a detailed explanation of how the Smart Water Level Device operates, particularly focusing on measurement criteria and a decision-making process for relaying data.

Consider, a sensor is configured to measure the water level every minute (Measurement_Interval) for a value between 3cm (Minimum_Value) to 200cm (Maximum_Value) only. The sensor will relay the value only if the change is +/- 5cm (Significant_Change_Value) from the last value. The sensor starts with an initial reading of 25 cm (Last_Value) and after a minute (Measurement_Interval), the sensor measures a new value for evaluating each value against the predefined thresholds. A possibility for relaying the Values to the Server is calculated as below:

Consider a Bad Random Values is 0cm or 210cm, a Right Values is any value between 20cm - 30cm and due to disturbance, a Good Random value is equal to10cm, 85cm or 140cm.

Case 1: 0cm
Step 1: the device checks if the value (i.e., 0 cm) is less than the Minimum_Value (i.e., 3 cm). Since the value is less than the minimum value, the reading is ignored.

Case 2: 210cm
Step 1: the device checks if the value (i.e., 210 cm) is less than the Minimum_Value (i.e., 3 cm). Since the value is not less than the minimum value, the device proceeds to the next check (i.e., step 2).
Step 2: the device checks if the value (i.e., 210 cm) is greater than Maximum_Value (i.e., 200 cm). Since the value is greater than the maximum value, the reading is ignored.

Case 3: 20cm
Step 1: the device checks if the value (i.e., 20 cm) is less than the Minimum_Value (i.e., 3 cm). Since the value is not less than the minimum value, the device proceeds to the next check (i.e., step 2).
Step 2: the device checks if the value (i.e., 20 cm) is greater than Maximum_Value (i.e., 200 cm). Since the value is not greater than the maximum value, the device proceeds to the next check (i.e., step 3).
Step 3: the device compares the change of value from the last recorded value (25 cm) to the new value (20 cm). The change is -5 cm, which meets the Significant_Change_Level threshold; thus, this value is sent to the server.

Case 4: 25cm
Step 1: the device checks if the value (i.e., 25 cm) is less than the Minimum_Value (i.e., 3 cm). Since the value is not less than the minimum value, the device proceeds to the next check (i.e., step 2).
Step 2: the device checks if the value (i.e., 25 cm) is greater than Maximum_Value (i.e., 200 cm). Since the value is not greater than the maximum value, the device proceeds to the next check (i.e., step 3).
Step 3: the device compares the change of value from the last recorded value (25 cm) to the new value (25 cm). The change is 0 cm, since there’s no significant change, the reading is ignored.

Case 5: 30cm
Step 1: the device checks if the value (i.e., 30 cm) is less than the Minimum_Value (i.e., 3 cm). Since the value is not less than the minimum value, the device proceeds to the next check (i.e., step 2).
Step 2: the device checks if the value (i.e., 30 cm) is greater than Maximum_Value (i.e., 200 cm). Since the value is not greater than the maximum value, the device proceeds to the next check (i.e., step 3).
Step 3: the device compares the change of value from the last recorded value (25 cm) to the new value (30 cm). The change is +5 cm, which meets the Significant_Change_Level threshold; thus, this value is sent to the server.

Case 6: 10cm
Step 1: the device checks if the value (i.e., 10 cm) is less than the Minimum_Value (i.e., 3 cm). Since the value is not less than the minimum value, the device proceeds to the next check (i.e., step 2).
Step 2: the device checks if the value (i.e., 10 cm) is greater than Maximum_Value (i.e., 200 cm). Since the value is not greater than the maximum value, the device proceeds to the next check (i.e., step 3).
Step 3: the device compares the change of value from the last recorded value (25 cm) to the new value (10 cm). The change is -15 cm, which meets the Significant_Change_Level threshold; thus, this value is sent to the server but could lead to an incorrect reading due to its classification as a Good Random Value.

Case 7: 85cm
Step 1: the device checks if the value (i.e., 85 cm) is less than the Minimum_Value (i.e., 3 cm). Since the value is not less than the minimum value, the device proceeds to the next check (i.e., step 2).
Step 2: the device checks if the value (i.e., 85 cm) is greater than Maximum_Value (i.e., 200 cm). Since the value is not greater than the maximum value, the device proceeds to the next check (i.e., step 3).
Step 3: the device compares the change of value from the last recorded value (25 cm) to the new value (85 cm). The change is +60 cm, which meets the Significant_Change_Level threshold; thus, this value is sent to the server but could lead to an incorrect reading due to its classification as a Good Random Value.

Case 8: 140cm
Step 1: the device checks if the value (i.e., 140 cm) is less than the Minimum_Value (i.e., 3 cm). Since the value is not less than the minimum value, the device proceeds to the next check (i.e., step 2).
Step 2: the device checks if the value (i.e., 140 cm) is greater than Maximum_Value (i.e., 200 cm). Since the value is not greater than the maximum value, the device proceeds to the next check (i.e., step 3).
Step 3: the device compares the change of value from the last recorded value (25 cm) to the new value (140 cm). The change is +115 cm, which meets the Significant_Change_Level threshold; thus, this value is sent to the server but could lead to an incorrect reading due to its classification as a Good Random Value.

A second level check is implemented at the sever level for the smart water level device. The second level check is crucial for ensuring the accuracy and reliability of the data received from the water level sensor. Once a correct value is transmitted from the Water Level sensor 28 to the server, an additional checks are performed by the server to validate the data. The server is programmed to identify any incorrect values; if a value appears valid upon initial inspection, further analysis is conducted to confirm its accuracy before taking any action.

A critical parameter known as Buffer_Level is maintained by the server. A buffer level represents the distance between the sensor's position and the maximum water level that the tank can hold. For example, if the distance from the sensor to the bottom of the tank is 125 cm (denoted as Tank_Size) and water can only be filled up to 105 cm, then the Buffer_Level will be 20 cm (Buffer_Level = 125 cm - 105 cm = 20 cm). The buffer level value serves as a safety margin, ensuring that any readings above the threshold are treated with caution, particularly in scenarios 102 where overflow might occur.

Now referring to the above example and Fig. 2B, illustrates a system for performing server checks by the Smart Water Level Device to validate incoming data and ensure accurate water level monitoring.

At 232, at the initial level a server performs the Buffer Value Check. The server initiates the process by comparing a relayed value (referred to as Check Value) with a predefined Buffer_Value (i.e., 20 cm). Specifically, the server evaluates whether the Check Value is less than the Buffer_Value. If this condition is satisfied, the reading is ignored. The buffer value check is critical for preventing erroneous low readings that may not accurately reflect the actual water level in the tank.

Subsequently, at 234, the server compares the Check Value with the Tank_Size. The server assesses whether the Check Value exceeds the Tank_Size. If this condition is met, the reading is also ignored. This tank size check serves to identify potential overflow situations or measurement malfunctions, ensuring that only valid data is considered for further action.

At 236, if the Check Value passes both the checks and is deemed likely valid, appropriate actions are taken based on the information provided by the Smart Water Level Device. These actions may include updating system status, notifying users, or initiating automated responses as necessary.

In a rare situation where a bad random value gets through and triggers an action, the next reading from the device will auto correct any discrepancies, thereby restoring accurate monitoring and functionality.

For instance, the values relayed by the water level sensor 28 to the server, as previously discussed in relation to firmware level checks, are illustrated through various cases. For example, consider a Bad Random Value represented by measurements such as 0cm or 210cm, a Right Values falls between the range of 20cm - 30cm, and due to disturbance, a Good Random values are equal to10cm, 85cm or 140cm

Case 1: 0cm
The value has not reached the server. Thus, no further action is required.

Case 2: 210cm
The value has not reached the server. Thus, no further action is required.

Case 3: 20cm
Step 1: the device checks if the values (i.e., 20 cm) is less than the defined buffer value and if the value is not less than buffer_value, the device proceed to step 2.
Step 2: the device checks if the values (i.e., 20 cm) is greater than Tank_Size. and if the value is not greater than buffer_value, the device proceed to step 3.
Step 3: The device checks if this value exceeds the tank size. If it does not, the device proceeds to take appropriate action based on this valid reading.

Case 4: 25cm
The value has not reached the server. Thus, no further action is required.

Case 5: 30cm
Step 1: the device checks if the values (i.e., 30 cm) is less than the defined buffer value and if the value is not less than buffer_value, the device proceed to step 2.
Step 2: the device checks if the values (i.e., 30 cm) is greater than Tank_Size. and if the value is not greater than buffer_value, the device proceed to step 3.
Step 3: The device checks if this value exceeds the tank size. If it does not, the device proceeds to take appropriate action based on this valid reading.

Case 6: 10cm
Step 1: the device checks if the value (i.e., 10 cm) is less than the buffer value and if the value is not less than buffer_value, the reading is ignored.

Case 7: 85cm
Step 1: the device checks if the values (i.e., 85 cm) is less than the defined buffer value and if the value is not less than buffer_value, the device proceed to step 2.
Step 2: the device checks if the values (i.e., 85 cm) is greater than Tank_Size. and if the value is not greater than buffer_value, the device proceed to step 3.
Step 3: The device checks if this value exceeds the tank size. If it does not, the device proceeds to take appropriate action based on this valid reading.

In cases where the random value passes through all the checks and balances but in the very next minute, the entire process of validation and correction will be repeated in subsequent readings, ensuring that anomalies are corrected with a success rate of approximately 99.99%. The process of automatically correcting the anomaly is known as an auto-correct feature disclosed in the present disclosure.

Moreover, the random value is unlikely to have any impact on the behavior of pump 24. The “No impact of Good Random Value” is presented below.

Case 8: 140cm
Step 1: the device checks if the values (i.e., 140 cm) is less than the defined buffer value and if the value is not less than buffer_value, the device proceed to step 2.
Step 2: the device checks if the values (i.e., 140 cm) is greater than Tank_Size. and if the value is greater than buffer_value, the reading is ignored.

The present disclosure also introduces an Auto-Correct feature in the water level management system which is designed to enhance operational efficiency and to prevent the overflow or underflow of the water in water tanks. The auto-correct feature is contingent upon a specific configuration that ensures that the water management system 10 operates effectively within defined parameter. For example, the Auto-Correct feature is elaborated with its configurations, and how it integrates with the overall water management system 10.

The system of Auto-Correct feature of the present disclosure is valid for the following configurations only:

Configuration 1: Up to 0.5 hp Pump 24 used for tanks with depths up to 150 cm. According to condition 1, the configuration 116 is suitable for smaller tanks where minimal water volume management is needed.

Configuration 2: Up to 1 hp Pump 24 used for tank with the depth between 150 cm -250 cm. According to condition 2, the setup allows for a moderate water level and is ideal for medium-sized tanks.

Configuration 3: More than 1 hp Pump 24 used for tanks with depth more than 250 cm. According to condition 3, the configuration supports larger tanks requiring significant water management capabilities.

The above three configurations ensure that the pumps 24 used are appropriate for the depth of the tanks, thus optimizing performance and preventing damage. The Auto-Correct feature of the present disclosure is crucial for maintaining optimal water levels by automatically adjusting pump 24 operations based on real-time readings. The auto correct feature minimizes human intervention and enhances reliability, ensuring that the water management system 10 can effectively respond to fluctuations in water levels.

No impact of good random value

The Smart Water Level Device is configured with a specific setting that govern the operation of the Auto-Correct feature for example, consider a measurement interval is 1 minute, a minimum value is 3 cm, a maximum value is 200 cm, and a significant change value is ±5 cm. When the Smart Water Plug 22 is installed in the Pump 24, the additional configurations are made for example:

In scenario 1, the minimum water level is predefined by a threshold of 20%. When the water level drops below this threshold, the water management system 10 activates the Pump 24 to turn on, ensuring that adequate water levels are maintained.

In scenario 2, the maximum water level is predefined by a threshold of 98%. When the water level reaches this threshold, the water management system 10 deactivates the Pump 24 to prevent overflow.

Thus, an algorithm embedded in the Smart Water plug 22 is predefined with a margin of ±5 cm which indicates that the Pump 24 will not switch on exactly at the minimum level (i.e., 20%) but will be able to switch on within a range of 20%-25%. Similarly, the Pump 24 will not switch off exactly at the maximum level (i.e., 98%) but will switch off within the range of 93%-98%. The margins between activation and deactivation thresholds are designed to prevent rapid cycling of the Pump 24, thereby enhancing the stability and efficiency of the water management system 10 in response to minor fluctuations in water level readings

Now, consider a scenario where the water level within a tank is rising and the water level has reached 94%. However, due to turbulence, an erroneous value (i.e., 55% or 77%) is transmitted. The system continues pumping because it interprets this value as indicating a low level. In the next minute, if the level rises to 96%, the auto-correct feature instructs the server to turn off the Pump 24. Despite receiving several erroneous values (like 55% and 77%), the system's design ensures that it will not allow overflow due to its reliance on actual measurements combined with auto-correction capabilities. The system operates correctly in approximately 99.99% of cases, demonstrating its robustness against disturbances.

Smart Water Plug:

The water management system 10 further comprises of a Smart Water Plug 22. The Smart Water Plug 22 is an IoT device used to link to every Pump 24 and is responsible for controlling the pump's on/off functions. The Smart Water Plug 22 utilizes a Wi-Fi protocol for communication.

Smart Water Valve:

The water management system 10 further comprises of a Smart water valve 30. The Smart water valve 30 is an IoT device serves the purpose of interrupting water supply and can be positioned at locations where the water supply needs to be either enabled or disabled based on specific conditions. This device also utilizes the LoRaWAN protocol for communication and is battery powered.

Master Device:

The LoRaWAN protocol is used in the Master Device 32 for communication purposes and operates on electricity. With the LoRaWAN communication setup, we can rely on the public network. However, in areas where the public network is not accessible, the present disclosure is deployed with the Master Device 32. This Master Device 32 is responsible for receiving data through the LoRaWAN protocol from IoT devices such as Water Flow 20, Water Level, and Water Valve 30, and it transmits this data to our cloud servers using GSM technology.

Referring to Fig. 1A, a partial view of a supply sub-system 12 of the present disclosure is illustrated. The portion of the supply sub-system 12 shown in fig. 1A are located underground or at ground level and directly source water from municipal corporation. The supply sub-system includes a smart water flow 20. The smart water flow 20 is a device that continuously provides data on the water flow rate. By utilizing the algorithm used in the present disclosure, a user can identify whether the water supply from the municipal has commenced or not. If the municipal corporation commences the water supply at their end, our system activates the Pump 24 through the smart water plug 22. After activation of Pump 24, the water level in the primary tanks 26 is monitored using smart water level device. As soon as smart water level device indicates that the primary tank 26 is full or the smart water flow 20 indicates that the water supply has ceased, whichever event occurs first, the disclosed system deactivates the Pump 24 using the smart water plug 22. This process ensures efficient water storage in primary tank 26 and prevents any potential water overflow.

Referring to Fig. 1B, a Master device 32 utilizes a LoRaWAN protocol for communication with an IoT device and operates on electricity. The LoRaWAN communication protocol leverages a public network to transmit signals from a user device to a server, much like a GSM communication uses towers for signal relay.

In India, TATA Communications Limited stands as the sole large scale public LoRaWAN service provider and offers coverage in mostly Tier 1 and Tier 2 cities. In situations where the public network is unavailable, we employ our Master Device 32 to develop communication between the devices. The Master device 32 can receive signals from the devices including smart water level, smart water flow 20, and smart water valve 30 within a 200-meter range and further utilizes the GSM technology (2G/3G/4G/5G) to relay the data to the attached servers. The communication-based approach ensures that the system can be deployed across India, regardless of whether the public network is accessible or not.

Referring to Fig. 1C, a partial view of a distribution sub-system 14 of the present disclosure is illustrated. The portion of the distribution sub-system 14 shown in fig. 1C are situated on the top floors of buildings, providing water supply to various end nodes within the establishment. A secondary tank 36 serves as an immediate reservoir that distributes water to apartments, rooms, bathrooms, toilets, kitchens, pantries, and other areas. The secondary tank 36 receives water from the primary tank 26 and distributes the water to facility 38 for consumption of water. The secondary tank 36 may become empty several times a day, depending on the facilities usage. Each time the tank’s water level drops below a predefined minimum threshold, it necessitates replenishment from the primary tank 26. The water management system 10 of the present disclosure actively manages the process. Whenever the water level falls below the minimum threshold, it initiates the Pump 24 present in the distribution sub-system to refill the tank using smart water plug 22. This process continues until the water reaches the maximum threshold or until the primary tanks’ water level drops below the minimum threshold, whichever of these conditions occurs first.

Referring to Fig. 1D, a partial view of a utilization sub-system 16 of the present disclosure is illustrated. The portion of the water management system 10 shown in fig. 1D is the final destination where water is consumed by the various end nodes 38 (including: apartments, rooms, bathroom, kitchens, pantries and more). In this sub system the secondary tank distributes water to various facilities 38 within a building, which can be located on the same floor or across different floors. This distribution is managed through traditional plumbing systems. However, if a water tap is accidentally left open and unattended in a facility 38, it can lead to the depletion of all the water in the secondary tank, potentially causing a water outage. The system of the present disclosure takes a proactive measure to address the issue by assisting users in cutting the water supply to the suspected facility 38 with a possible leak. The Smart Water Flow 20 installed at the inlet of each facility 38 continuously sends us data regarding the flow rate of the water. Using our Artificial Intelligence algorithms, we can differentiate between normal and abnormal flow rates. In the case of an abnormal flow rate, we can promptly alert the user to either manually turn off the supply using our Smart Water Valve 30 or based on the configuration, automatically cut off the supply and notify the user. This approach effectively prevents water wastage and avoids water outages.

A Smart Water Level Device is installed in each tank to measure water levels in real-time. These tanks are typically located on the ground floor, underground, or on the terrace of buildings. The devices operate on battery power and are exposed to heat and humidity due to their open-air installation and proximity to water. To protect these devices, they are housed in IP67-rated casings, which also contain the batteries. This rating ensures that the devices are dust-tight and can withstand immersion in water up to one meter for a maximum of 30 minutes. To minimize the need for frequent battery replacements, a specialized algorithm has been implemented to extend battery life. This algorithm supplements existing electronic circuit optimizations, ensuring reliable, long-term performance of the water level monitoring system. This configuration not only safeguards the devices against environmental factors but also enhances their operational efficiency, making them suitable for various installation conditions.

The Smart Water Level Device continuously monitors the water levels at a regular interval. However, given that water usage is not constant every minute, minor fluctuations may not warrant reporting. For instance, using 100 liters from a 100,000-liter tank or 25 liters from a 1,500-liter tank within an hour may be considered insignificant. To address the minor fluctuations, a firmware is designed to compare the current water level with the previous reading and only relay data to a server if the change is deemed significant. The measurement intervals and thresholds for significant changes are pre-programmed in the firmware. The approach conserves battery power and extends the device's operational life.

For example, consider a 1,000-liter tank with a measurement interval of one minute and a significant change threshold of 25 liters, the device checks the water level 60 times per hour. If the water level changes by 50 liters during that hour, data will only be sent twice: once when the change reaches approximately 25 liters and again at 50 liters. The method effectively saves power by reducing unnecessary data transmissions, thereby conserving battery life by avoiding data sends for the remaining 58 checks within that hour. This efficient monitoring strategy ensures reliable performance of the water level monitoring system while minimizing energy consumption and prolonging battery life.

Now referring to Fig. 3, illustrates a method for optimizing the battery embedded within the Smart Water Level Device in accordance with examples of the present disclosure. At step 300, the height of a tank is measured and recorded in centimeters (cm). At step 302, a significant change level in centimeters (cm) is determined to trigger a data transmission. At step 304, a measurement interval in minutes for regular water level checks are set in the Smart Water level Device. The Smart Water Level Device is installed on the tank, ensuring that the values determined in Steps 300 to 304 are encoded into the firmware of the Smart Water Level Device's at step 306. At step 308, an initial water level value is relayed to a server and the water level value is stored within the Smart Water Level Device as a Last Value, Simultaneously, at every measurement interval, the Smart Water Level Device will check a current water level (i.e., Current Value) at step 310. After determining the last and current value, the difference between the current and last values are evaluated at step 312. At step 314, if the difference between the Current Value and the Last Value does not exceed the Significant Change Level, the Smart Water Level Device will ignore the Current Value and take no action. Conversely, if the difference between the Current Value and the Last Value exceeds the Significant Change Level, the Smart Water Level Device relays the Current Value to the server and stores the Current Value within the smart water level device as the Last Value at step 316 and the process then continues by monitoring the current value as described in step 310. The battery optimizing method ensures efficient and effective monitoring of water levels, allowing for timely data transmission while conserving a battery.

Referring to Fig. 4, illustrates one of the standout features of the present disclosure is the accessibility through a user-friendly mobile app called “Imvvy SmartTM” 118 available on Apple App Store & Google Play Store. Users can manage and monitor water supply from anywhere, at any time, ensuring convenience and having control at their fingertips. The mobile app 118 is designed to provide a seamless and intuitive experience, making water management effortless for users across various settings.

The real benefits of the present disclosure and Smart Devices (including Smart valve 30, water plug 22, water flow 20) is powered by the Mobile App 118. The mobile app 118 has many new implementations in the field of Water Management includes Scenario, Pumping Station Sync, Schedules , Do Not Disturb , Timer , dry run, leakage detection, Notifications, dashboard

Scenarios

The scenario 102 is crafted for use in various types of primary tank 26 and secondary tank 36 installations. Each user may have a unique configuration of the water tanks with a specific water storage requirement. The users can have a multiple Primary and a Secondary Tanks, each with a different minimum and maximum water level thresholds. For example, the configuration of water tanks includes the Primary Tank 26 with a capacity of 1,500 liters. The requirement for the Primary Tank 26 is when the water level reaches 98% (Maximum Threshold), the Pump 24 should cease filling this tank. Conversely, when the water level drops to 20% (Minimum Threshold), no water should be drawn from the Primary Tank 26. Simultaneously, the two secondary tanks are configured with each capacity of 1,000 liters. Both the tanks are filled using a Pump 24 that sources the water from the Primary Tank 26 to the secondary tank. For instance, the requirement of the secondary tank 1 is Stopped filling when the water level reaches 98%; resume filling when the level drops below 35% and the Secondary Tank 2 is stopped filling when the water level reaches 95%; resume filling when the level drops below 25%. To simplify the water management of tank configurations, the present disclosure introduces a unique feature called “Scenario” 102 within the system of Smart Water Plug 22. The Scenario 102 allow users to easily manage their specific water tank configurations and associated water level requirements, enhancing the operational efficiency and user convenience.

When the Smart Water Plug 22 is installed, the users can select a specific scenario 102 and configure 116 essential settings, including Minimum Threshold, Maximum Threshold, and the number of tanks in use. The several pre-defined scenarios 102 are available to accommodate various configurations, involving: one Primary Tank 26 connected to one secondary tank 36, one Primary Tank 26 to two secondary Tanks 36, direct from pumping station to Primary Tank 26, direct from pumping station to Primary Tank 26 or Secondary Tank 36 with Auto On and among others.

The flexibility between the different tanks allows the user to tailor the water management syste 10 according to their unique water management needs. The users can easily configure the setup and define their own minimum and maximum thresholds for each tank through Imvvy Smart AppTM 118, available on both Android and iOS platforms. The adaptability of the water tanks ensures that the Water Management System 10 can be effectively customized for diverse installations and user specifications, enhancing overall functionality and user experience.

Now Referring to Fig. 5, illustrates a user-friendly scenario 102 feature in the mobile app in accordance with some examples of the present disclosure. The Imvvy Smart AppTM 118, have is equipped with Smart Water Plug 22 option which can be further used by the user to adjust the scenario 102 according to their preferences. At step 400, the user device is configured with Imvvy Smart AppTM 118, using a 2.4GHz Wi-Fi connection. At step 402, the user can navigate the scenario 102 tab within the Imvvy Smart AppTM 118. At step 404, after navigating the scenario 102 tab the user can select the appropriate scenario 102 based on the user installation requirement. At step 406, upon selecting a scenario, a system of Imvvy Smart AppTM 118, will prompt the user to enter a specific value tailored to the user’s configuration 116. For example, if the user selects the "one primary Tank 26 to two secondary Tanks 36" scenario 102, the following details must be provided Source Tank Name, Source Minimum Threshold Value, Destination Tank 1 Name, Destination Tank 1 Minimum Threshold Value, Destination Tank 1 Maximum Threshold Value, Destination Tank 2 Name, Destination Tank 2 Minimum Threshold Value, Destination Tank 2 Maximum Threshold Value. At step 408, after entering all required values, users should click “Submit” button to finalize the scenario configuration which will help the user to have a concrete information of the water level. At step, 410, after clicking the submit button the system will then be prepared and ready for use.

The method used in scenario 102 feature ensures that users can easily set up and customize their water management system 10 according to their specific needs and tank configurations, enhancing operational efficiency and user control.

Pumping Station Sync

The scenario 102 introduced a unique feature introduced in the present disclosure that notifies users when the water supply from the pumping station starts or stops. The pumping station sync operates independently of smart water flow 20, allowing the activation and deactivation of Pump 24 in response to the initiation or cessation of water supply from the municipal corporation. Additionally, a specific scenario 102 enables the users to synchronize the Smart Water Plug 22, connected to the tank, with the pumping station.

When the water supply begins or ends, a designated person at the pumping station can toggle a button in the Imvvy Smart AppTM 118, to indicate the start or stop of the water supply. Based on the toggle action by the pumping station operator (or designated person), all Smart Water Plug 22 linked to this pumping station will be switched on or off accordingly. Since the water supply does not reach to all the users simultaneously when it starts, nearby premises may receive water within a minute, while areas further away might experience a delay of 5-7 minutes, and distant locations could wait 15-20 minutes. To accommodate this delay, the Imvvy Smart AppTM 118, allows the designated person at the pumping station to enter the time it takes for water to reach their premises after the supply starts. An algorithm configured within the Imvvy Smart AppTM 118, will then delay the activation of the Pump 24 by the specified number of minutes when the water supply begins. However, the Pump 24 will switch off immediately as soon as the water supply stops.

A method embedded in the present disclosure manages the delays in the water management system 10 through a grouping approach. Various locations are grouped in the water management system 10 based on their distance from the pumping station including far-away locations form one group, middle-distance locations another, and nearby locations the third group. The operator can activate the far-away group with a single click on the operator screen. After an appropriate delay, the grouping approach allows time for the far-away locations to receive and fill with water, the middle group is activated, followed by the nearby group. The grouping approach ensures that an adequate amount of water reaches far away locations efficiently.

Referring to Fig. 6, illustrates a mobile app 118 feature for pumping station synchronization, specifically for switching on the pump 24 via Smart Water Plug 22 in accordance with some examples of the present disclosure. At step 500, the operator initiates a Pump 24 switch-on command using an operator app. Subsequently, at step 502, the server receives the command, indicating that a specific Pump 24 requires activation. The water management system 10 identifies the user associated with a Notification Device linked to the specified Pump 24. At step 504, a "Switch On" notification 110 is dispatched to the users, informing the user of the impending Pump 24 activation. At step 506, a Cron Service automatically switching on the Pump 24 based on a predefined schedule 108. After switching on the Pump 24, the system identifies the Smart Water Plug 22 associated with the Pump 24. The checks are performed for each Smart Water Plug 22 regarding the delay in pumping activation. At step 510, the Smart Water Plug 22 checks if there is a specified delay. At step 512, the Smart Water Plug 22 check if there is a delay specified for Pump 24 activation, a schedule 108 is created to switch on the Pump 24 after the specified delay. Conversely, if no delay is specified for Pump 24 activation, the Pump 24 is immediately switched on through the Smart Water Plug 22 to ensure efficient and timely management of Pump 24 operations in conjunction with user notifications 110 and scheduling capabilities at step 514.

Conversely, the Smart Water Plug 22 facilitates the switching off of the Pump 24 through a continuous operation of a Cron Service, which runs 24 hours a day, 7 days a week. The Cron Service periodically checks for any scheduled Pump 24 switch-off events.

Automated Pump control (Switch-Off): If a scheduled event is detected, the Pump 24 is switched-off. Conversely, if no event is found, no action is taken.

Smart Water Level Device Check: The water management system 10 verifies whether a Smart Water Level Device is installed on the tank. The Smart Water Level Device installed in the tank checks if the current water level is greater than or equal to the Maximum Level minus the Buffer Level. If the condition is satisfied, the Pump 24 is switched off and if not, no action is taken.

Operator-Initiated Switch-Off: The present disclosure includes an operator-initiated switch-off feature. If an operator manually deactivates the water supply, the water management system 10 will also deactivate the Pump 24.

The ensures that the Pump 24 is switched off based on the earliest occurrence of any of the aforementioned conditions. Additionally, the present disclosure identifies the users associated with a Notification Device linked to a specified Pump 24. A "Switch Off" notification 110 is sent to the users, informing them of the Pump 24 deactivation. The pumping station synchronizes method employed both the operations includes switch-on and switch-off operations, ensuring efficient and reliable control of Pump 24 functionality while keeping users informed and minimizing potential operational disruptions.

Do Not Disturb

A Do Not Disturb 104 represents a distinctive aspect of the water management solution. A Smart Water Plug 22 can be linked to a Pump 24 to automatically control its operation based on the water levels in the tank. However, the Pump 24 might start running in the middle of the night, which could disturb both the user and the neighbors. Preventive measures are taken to prevent the automatic activation of Pump 24 during night-time hours, a feature that can be adjusted by the user to prevent disturbances to neighbors. Nevertheless, in cases of emergency, users have the option to manually override the setting and activate the Pump 24 to ensure an ample water supply to their facilities.

To avoid such situations a Do Not Disturb 104 feature has been introduced in the present disclosure through the algorithm configured in the Pump 24. When the Pump 24 is turned on, the water management system 10 checks whether the action falls within the user defined Do Not Disturb 104 window. If the action falls in the user defined Do Not Disturb 104 window, the Pump 24 will not be activated. Additionally, if the Pump 24 is already running when the Do Not Disturb 104 period begins, the servers of the present disclosure will automatically turn the Pump 24 off using the Smart Water Plug 22.

For example, consider a scenario 102 in which a user sets a Do Not Disturb 104 period in the water management app (i.e., Imvvy Smart AppTM 118,) according to their preference, specifying the time frame from 10 PM to 5 AM:

In scenario 1, if the Pump 24 was turned on at 9:45 PM and is still running when the clock strikes 10 PM, our algorithm will detect that the Pump 24 has entered the Do Not Disturb 104 period. Consequently, our servers will trigger the Smart Water Plug 22 to switch off the Pump 24.

Referring to Fig. 7, illustrates a pump control mechanism featuring a "Do Not Disturb" (DnD) 104 functionality in accordance with some examples of the present disclosure. The system is designed to ensure that the pump 24 does not operate during specified quiet hours, enhancing user comfort and reducing unnecessary disturbances. At 800, the user can specify a start time and an end time for the DnD window through a mobile application. The customizable feature of specifying the time allows the user to tailor the operations of the pump 24 according to the preferences. When the pump 24 is activated, the system performs a critical check to determine whether the activation coincides with the user-defined DnD window at 802. Before proceeding with the pump activation at 804, the system verifies whether the current time falls within the DnD period. If the current time falls within the DnD period specified by the user, the activation of the pump is halted, ensuring compliance with the user preferences at 806. Else, where the pump 24 is already operational at the onset of the DnD period at 808, the system automatically intervenes to turn off the pump 24 using the Smart Water Plug 22 at 810. Additionally, the "Do Not Disturb" (DnD) 104 feature incorporates an alert mechanism that notifies users when a DnD period is about to commence or has been violated. For instance, if a user observes that the water level is low and wishes to refill the tank by activating the pump 24, the alert mechanism issues a warning indicating that the DnD window is currently active. The user is then prompted to either wait until the DnD period concludes or to deactivate the DnD window to proceed with the pump activation.

The integration of the Do Not Disturb 104 feature within the pump 24 control mechanism not only enhances user experience but also ensures that operations are conducted in accordance with user-defined schedules (i.e., start and end time), thereby promoting a peaceful environment during specified quiet times.

For example, if the DnD window is set from 10 PM to 5 AM, a schedule is established to deactivate the pump (24) at 10 PM. Consequently, the pump 24 will be turned off daily at this specified time, ensuring that it does not operate during the designated Do Not Disturb period at step 812. The structured approach of Do not Disturb 104 feature ensures that the user can manage the water supply effectively while respecting the preferences of the user for uninterrupted periods.

In scenario 2, in a setup where the Pump 24 is configured to turn on whenever the water level in a tank drops below 35%, if the water level falls to 32% at 11 PM, the servers would typically activate the Pump 24. However, before doing so, they will check the Do Not Disturb window. Since 11 PM falls within this period, the Pump 24 will not be turned on, even though the water level has dropped below the user-defined threshold of 35%.

The Smart Water Plug 22 is engineered to activate the water Pump 24 whenever the water level in the tank falls below a predefined Minimum Threshold (e.g., 35%). To enhance the accuracy of water level assessments, a Margin Value of 5% is stored within the water management system 10, providing a buffer that accounts for fluctuations in water levels. Upon receiving data from the server, the water management system 10 performs a comparison between the Current Value of the water level and the calculated threshold, which is defined as the Minimum Threshold plus the Margin Value. Specifically, if the Current Value exceeds the threshold (i.e., Current Value > Minimum Threshold + Margin Value), no action is taken regarding the pump's operation. Conversely, if the Current Value is less than or equal to the threshold (i.e., Current Value = Minimum Threshold + Margin Value), the water management system 10 proceeds to evaluate additional conditions. The water management system 10 checks whether the Do Not Disturb (DnD) 104 option is enabled by a user. If DnD 104 is activated, the system further verifies whether the current time falls within the designated DnD window. Should the current time be within this DND 104 window, any action to switch on the Pump 24 is disregarded, effectively preventing disruptions during periods designated for uninterrupted operation. Conversely, if the current time falls outside of the DnD window, the system activates the Pump 24 to restore water levels in accordance with user preferences and operational requirements. This dual-check mechanism ensures that Pump 24 activation is managed effectively while respecting user-defined periods of uninterrupted operation.

The DnD 104 method enhances user control and comfort by allowing users to define specific times when Pump 24 operation should be suspended. By integrating both water level monitoring and user preferences through DnD settings, this approach optimizes water management processes and minimizes unnecessary disturbances, thereby contributing to efficient and reliable water supply management.

Schedules

A Schedule 108 enables the users to establish a specific time for initiating and/or halting the Pump 24 operation as per their requirement.

Timer

The Users have the option to configure a timer 112 that will automatically stop the Pump 24 after a designated duration, regardless of the other settings. The timer 112 feature is especially beneficial in cases where users manually initiate the Pump 24 and may forget to turn it off, as the timer 112 will ensure it stops as planned.

Dry Run

When a Pump 24 is activated via a Smart Water Plug 22, and the destination tank is equipped with a Smart Water Level Device, a "Cron Service" designed to continuously monitor the changes in water levels within the tank. If no increase in the water level is detected within a predefined time duration, the Cron Service will automatically trigger the Pump 24 to switch off. The mechanism used for automatically triggering the Pump 24 to shut down effectively prevents dry running of the Pump 24, thereby mitigating the risk of potential burnout.

When activated, the dry run 106 feature guarantees the automatic shutdown of the pump 24, regardless of any other configurations, as soon as it detects a lack of water flowing into the tank. The dry run 106 functionality is achieved solely through our algorithm.

Now Referring to Fig. 8, illustrates a mobile app 118 feature for dry run 106 pumps in accordance with some examples of the present disclosure. At step 600, a Cron Service operates continuously, monitoring Pump 24 activities, including water levels, 24 hours a day, 7 days a week to ensure constant oversight of the pump's operational status. At step 602, the Cron Service is configured with a threshold time duration, which represents the maximum allowable time for the water level to change after the Pump 24 has been activated. At step 604, the Cron Service monitors the water level every minute for each running Pump 24 associated with a Smart Water Level Device installed in the destination tank(s). At step 606, the Cron service checks if the water level has decreased since the last recorded measurement, the process returns to step 604 to continue monitoring the water level. Conversely, if the water level has increased since the last recorded measurement the process proceeds to the next step 608. At step 608, the Cron service calculates the time elapsed since the Pump 24 was activated. At step 610, if the elapsed time is less than the threshold time duration, the process returns to step 604 for ongoing monitoring. However, if the elapsed time exceeds the threshold duration, the process moves to step 612. At 612, The Cron Service triggers an automatic shutdown of the Pump 24 to prevent dry running, thereby mitigating potential damage or burnout. After executing the shutdown procedure, the Cron Service resumes monitoring and returns to step 604 for continuous operation.

The dry run 106 method described in the present disclosure effectively ensures that the Pump 24 operates within safe parameters. By facilitating proactive management of Pump 24 operations, it significantly reduces the risk of dry running and enhances the overall system reliability.

Leakage Detection

The leakage detection feature 114 is engineered to provide a software-based solution that integrates with the Smart Water Level device, enabling the water management system 10 to detect the water leaks and notifying the users of potential issues. Additionally, the present disclosure introduces a Smart Water Valve device capable of automatically shutting off the water supply to the affected area, thereby aiding in water conservation.

The leakage 114 detection system can identify water leakage 114, whether it occurs intentionally or unintentionally, such as leaving a tap open or detecting faults in the plumbing within a facility 38. This dual capability enhances the system's effectiveness in safeguarding infrastructure and conserving resources.

Referring to Fig. 9, illustrates a mobile app 118 feature for detecting leakage 114 in accordance with some examples of the present disclosure. At the initial stage a Smart Water Level Device is installed in the water tank to continuously monitor the water levels and to record water usage on an hourly basis at step 700. The ongoing monitoring ensures that a comprehensive dataset is available for data analysis, which is essential for identifying trends and anomalies in water consumption. At 702, a database is maintained to store water usage data over a period of 6 to 9 months, which serves as a foundational resource for analytics, enabling the water management system 10 to establish a benchmark and assess normal water usage patterns. After maintaining the database based on the water usage data, the collected data is processed to create an average a water usage profile segmented into 24 distinct intervals throughout the day at step 704. The hourly usage is categorized into predefined levels, including Level 1: No water usage; Level 2: Up to 5% water usage; Level 3: 5-10% water usage; and so on. At 706, the resulting usage patterns are stored in the database as a reference for normal water consumption behavior, facilitating effective comparison during real-time monitoring. Simultaneously the Smart Water Level Device continuously monitors actual water consumption on an hourly basis. At 708, after detecting actual water consumption, the actual water usage is compared with the stored pattern mapping to identify anomalies indicative of a potential leaks or inefficiencies. At 710, the Smart Water Level Device checks for leaks by determining whether actual usage exceeds expected levels. If the actual usage within an interval exceeds the expected level in the pattern mapping, it triggers an alert to notify the user of potential leaks or unusual consumption. For example, if the pattern mapping indicates Level 1 (no water usage) while actual usage registers at Level 3, an alert is triggered to notify the user about potential leak at 712. Conversely, if actual usage does not exceed expected levels, the Smart Water Level Device continues to compare current water levels with stored patterns. When leakage 114 is detected at 714, a signal is sent to a smart water valve 30, which interrupts the water supply. The smart water valve 30 can be positioned at various locations where the water supply needs to be enabled or disabled based on specific conditions. If the leakage 114 is confirmed, a user using the water management system 10 have the option to manually close the water supply using the Imvvy Smart AppTM 118. Alternatively, the smart water valve 30 is configured to automatically shut off the water supply without the user intervention at 716. Conversely, if actual usage does not exceed the expected level of water leakage114, the Smart Water Level Device continues to compare current water levels with stored patterns.

The leakage 114 detection method integrates advanced data collection and analysis techniques with real-time monitoring and response capabilities, ensuring effective leakage 114 detection and prevention in smart water management system 10. By leveraging continuous monitoring, categorization of usage levels, and automated responses, the system promotes efficient water use and conservation practices while minimizing waste due to leaks.

Dash Boards

A Mobile dashboard 100 accessible to the users offers insights into the hourly water levels and consumption patterns for each individual tank.

Notifications

In the event of abnormal water usage, the system has the capability to alert end users, providing timely notifications 110 about potential issues. Users can take proactive measures to address leaks or wasteful consumption.

The present disclosure provides a communication system (18) that enhances operational functionality by ensuring network availability from various service providers. The system (10) effectively supports the operations of sensors, flow devices, and valves, which are designed to function optimally in conjunction with a LoRa gateway in areas with a public network access. To further strengthen the system's (10) capabilities, a master device (32) is introduced in the present disclosure, which serves as a reliable substitute for the LoRa network, thereby enhancing overall connectivity.

In instances where the public LoRa network is unavailable, the master device (32) seamlessly relies on GSM network connectivity, ensuring uninterrupted operation and data transmission. Additionally, the water management system (10) incorporates smart plugs (22) that efficiently utilize a Wi-Fi connection to function efficiently.

To address potential inaccuracies in sensor (28) readings due to external factors such as vibrations or splashes of water, the water management system (10) is designed with maintenance considerations and may include a cover over the sensor (28). For example, if a pressure pump (24) is installed near the water tank where the sensor (28) is mounted, the vibrations can disrupt sensor (28) accuracy. Additionally, splashes of water on the sensor (28) can also lead to incorrect readings. Any instance of the sensor (28) getting wet can cause anomalies in the readings. To mitigate the inaccuracy, the sensors (28) can be easily cleaned with a cloth to maintain optimal performance and accuracy.

Moreover, the sensor (28) is engineered to operate effectively within a temperature range of -10 degrees Celsius to 60 degrees Celsius. The sensor (28) not only ensures reliable performance but also allow for straightforward installation in appropriate environments, minimizing the risk of sensor failure due to temperature extremes.

Overall, the present disclosure emphasizes enhanced connectivity, operational flexibility, and robust performance across diverse conditions, making it an innovative solution for water management system (10) and related IoT application.

Although there has been shown and described the preferred embodiments/examples of the present disclosure, it will be readily apparent to those skilled in the art that modifications may be made thereto which do not exceed the scope of the appended claims. Reference numbers recited in the claims are exemplary and for ease of review by the patent office only and are not limited in any way. In some embodiments, the figures are represented only, and the claims are not limited by the dimensions of the figures.

While the principle of the disclosure has been described above in connection with specific system and methods, it is to be clearly understood that this description is made only by way of example and not as limitation on the scope of the disclosure.

List of reference numerals:

10 Water management system
12 Supply sub-system
14 Distribution sub-system
16 Utilization sub-system
18 Communication system
20 Smart Water Flow
22 Smart Water Plug
24 Pump
26 Primary Tank
28 Smart Water level sensor
30 Smart Water Valve
32 Master Device
34 Public gateway
36 Secondary Tank
38 Facility
100 Mobile dashboard
102 Scenarios
104 Do not Disturb (DnD)
106 Dry run
108 Schedule
110 Notification
112 Timer
114 Leakage
116 Configurable
118 Mobile App- Imvvy Smart AppTM

,CLAIMS:WE CLAIM:

1. A water management system (10) comprising:
a supply sub-system (12) configured to receive water from a municipal source;
a distribution sub-system (14) designed to enable the flow of water from a primary tank (26) to a secondary tank (36);
a utilization sub-system (16) used to distribute water to various facilities (38);
a communication system (18) to receive data from the supply sub-system (12), the primary tank (26), and the secondary tank (36), to enable real-time monitoring and adjustments to maintain a desired water levels in the tanks.

2. The system (10) as claimed in claim 1, wherein the water management system (10) is integrated with a user interface that allows end-users to monitor the individual consumption and receive alerts regarding maintenance needs or abnormal water usage patterns.

3. The system (10) as claimed in claim 1, wherein the supply Sub-system (12) further comprising:
a smart water flow device (20) to continuously monitor and provide data on a water flow rate;
a pump (24) activated by a smart water plug (22) in response to the commencement of the municipal water supply;
a primary tank (26) to store water received from the municipal water supply;
a smart water level device to monitor the water level in the primary tank (26) and to deactivate the pump (24) when the tank is full or when the municipal water supply ceases, whichever occurs first.

4. The system (12) as claimed in claim 3, wherein the primary tank (26) is equipped with a water level sensor (28) to monitor the water levels and control mechanisms, to regulate the inflow and outflow of the water based on the usage demand.

5. The system (10) as claimed in claim 1, wherein the communication system (18) further comprises a public network of LoraWAN to facilitate data transmission between a master device (32) and IoT devices including, a smart water flow device (20), a smart water level device, a smart water valve (30), wherein the master device (32) utilizes the LoraWAN protocol for communication, enabling data transmission over the public network and providing a fallback to GSM technology when the public network is unavailable.

6. The system (10) as claimed in claim 1, wherein the distribution sub-system (14) further comprising:
a secondary tank (36) configured to serve as an immediate reservoir to distributes water to various end nodes including apartments, rooms, bathrooms, toilets, kitchens, and pantries;
a pump (24) operatively connected to the secondary tank (36) and activated through the smart water plug (22) when the water level drops below a predefined minimum threshold; and
a water level sensor (28) integrated within the secondary tank (36) to continuously monitor the water levels.

7. The system (14) as claimed in claim 6, wherein the water level sensor (28) is designed to monitor the water level and communicate with a control mechanism to activate the pump (24) timely, ensuring the secondary tank (36) is replenished whenever the water level drops below a predefined minimum threshold.

8. The system (14) as claimed in claim 6, wherein the pump (24) is configured to use the smart water plug (22) to refill the secondary tank (36) until either the water level reaches a maximum threshold, or the water level of the primary tank (26) drops below a minimum threshold.

9. The system as claimed in claim 1, wherein the utilization sub-system (16) further comprising:
a smart water level device (20) installed at the inlet of each end node (38) to continuously monitor the flow rate of the water;
a smart water valve (30) capable of being manually controlled by a user through a mobile application or being automatically shut off the water supply based on a predefined configuration (116) when the abnormal flow rate is detected;
a facility wherein the end node use the water.

10. The system (10) as claimed in claim 1, wherein the utilization sub-system (16) further comprising an algorithm to analyze the data flow from the smart water flow device (20) to differentiate between a normal and an abnormal flow rate.

11. The system (10) as claimed in claim 10, wherein in the event of the abnormal flow rate being detected, the system (10) is configured to trigger an alert to notify the user about a potential leak or unusual water consumption patterns.

12. The system (10) as claimed in claim 3, wherein the smart water level device, comprising:
a water level sensor (28) configured to continuously monitor the water level in a tank;
a firmware programmed to implement a dual-layer management approach i.e., a firmware level and a server level management, for ensuring reliable data transmission.

13. The system (10) as claimed in claim 3, wherein the smart water level device further comprises an auto- correct feature that allows subsequent reading to adjust automatically for any discrepancies caused by an erroneous value that may have triggered an action.

14. The system (10) as claimed in claim 12, wherein the firmware level management approach, comprising:
a Minimum_Value threshold representing the lowest acceptable water level;
a Maximum_Value threshold representing the upper limit of water level detection;
a predefined Measurement_Interval dictating how frequently the smart water level device checks the water level to balance timely updates with power consumption efficiency;
a Significant_Change_Level parameter defining the minimum change in the water level that must occur for the smart water level device to consider it noteworthy, thereby preventing unnecessary data transmission from minor fluctuations.

15. The system (10) as claimed in claim 12, wherein the server level management approach is further configured to:
perform a Buffer Value Check by comparing a Check Value with the predefined Buffer_Value;
perform a Tank Size Check by comparing the Check Value with the Tank_Size;
implement an appropriate action if both the checks (i.e., Buffer Value and Tank Size check) are passed, including updating system status or notifying a user.

16. A method for monitoring and managing water usage in the utilization sub-system, the method comprising the steps of:
continuously monitoring of water flow rates at each end note using a smart water flow device;
analyzing the monitored data in real-time to identify an anomaly indicative of potential leaks or excessive water usage;
triggering an automated response to a user based on a user-defined threshold and conditions related to the water usage;
notifying the user when the anomalies are detected and providing options for manual or automatic intervention through a smart water valve.

17. A method for performing checks to ensure accurate water level management in a tank using a smart water level device, the method comprising the steps of:
continuously measuring a water level and applying checks including a firmware level checks and a server level checks, to filter out erroneous readings based on a predefined threshold;
transmitting a validated reading to a server for monitoring the water usage;
triggering an alert system that notifies a user when a critical threshold is reached or when erroneous readings are detected, enhancing the user awareness and system reliability.

18. A mobile application (118) for the water management system (10), the application (118) comprising:
a user interface to allow a user to manage and monitor the water supply remotely, providing a control from any location;
a dashboard (100) comprising various user-friendly features including a pumping station synchronization, a scheduling capability (108), a scenario management (102), a "Do Not Disturb" mode (104), a timer function (112), a dry run detection (106), a leakage detection (114), and a notification (110) feature for managing and visually representing the water usage data, system status, and alerts in real-time;
a notification system (110) to alert a user to a significant event including a low water level, leakage detection (114), or scheduled (108) maintenance;

19. The mobile application (118) as claimed in claim 18, wherein the pumping station synchronization feature comprising:
initiating a switch-on command for a pump (24) via an operator application;
receiving the switch-on command at a server, indicating that the pump (24) requires activation;
identifying a user associated with a notification device linked to the pump (24);
dispatching a "Switch On" notification to the user to inform the user of the impending activation of the pump (24);
identifying a smart water plug (22) which is associated with the pump (24);
checking for any specified delay;
creating a schedule to switch on the pump (24) after the specified delay is detected;
switching on the pump (24) immediately through the Smart Water Plug (22) if no delay is specified, ensuring efficient management of pump operations.

20. The mobile application (118) as claimed in claim 18, wherein the pumping station synchronization, further comprising switching off a pump (24) through continuous operation of a Cron Service, which periodically checks for any scheduled (108) switch-off events.

21. The mobile application (118) as claimed in claim 18, wherein the Do not Disturb (104) feature comprising:
specifying a start time and an end time for the DnD window through a mobile application;
determining whether the activation coincides with the user-defined DnD window;
activation of the pump is halted, if the current time falls within the DnD period;
automatically turn off the pump if it is already operational at the onset of the DnD period using a Smart Water Plug.
22. The mobile application (118) as claimed in claim 21, further comprises an alert mechanism that notifies users when a DnD period is about to commence or has been violated.

23. The mobile application (118) as claimed in claim 18, further comprising a notification (110) feature to inform the user when an action is taken regarding activation or deactivation of the pump (24), including the notifications for both switch-on and switch-off events related to the pump (24).

24. The mobile application (118) as claimed in claim 18, wherein the Dry run (106) preventive feature comprising:
continuously operating a Cron Service to monitor activities of the pump (24) and water levels 24 hours a day, 7 days a week;
configuring the Cron Service with a threshold time duration representing a maximum allowable time for the water level to change after an activation of the pump (24);
monitoring the water level every minute for each running pump (24) associated with a Smart Water Level Device installed in a destination tank(s) including a Primary Tank (26) and a secondary Tank (36);
proceeding to calculate an elapsed time since activation of the pump (24);
resuming monitoring by returning to the continuous operation after executing the shutdown procedure.

25. The mobile application (118) as claimed in claim 24, wherein the step of calculating the elapsed time includes if the elapsed time exceeds the threshold time duration, triggering an automatic shutdown of the pump (24) to prevent dry running.

26. The mobile application (118) as claimed in claim 24, wherein the dry run (106) is configured to ensure that the pump (24) operates within the safe parameters by proactively managing the pump (24) operations to mitigate the risks associated with the dry running.

27. The mobile application (118) as claimed in claim 18, wherein the leakage detection (114) feature of the water management system (10) comprising:
continuously monitoring the water levels and record water usage on an hourly basis;
maintaining a database to store a water usage data over a period of 6 to 9 months which serves as a foundational resource for analytics;
processing the collected data to create an average water usage profile segmented into 24 distinct intervals throughout the day;
categorizing hourly water usage into a predefined levels, including Level 1: No water usage; Level 2: Up to 5% water usage; Level 3: 5-10% water usage, and so on;
comparing an actual water usage with a stored pattern mapping to identify an anomaly indicative of a potential leak or inefficiencies;
sending a signal to a smart water valve (30) to interrupt the water supply when the leakage (114) is detected;
triggering an alert to notify a user about the potential leakage (114);
allowing the user to manually close the water supply using the mobile app (118) or configuring the smart water valve (30) to automatically shut off the water supply.

28. The mobile application (118) as claimed in claim 27, wherein the step of triggering an alert includes the Smart Water Level Device checking whether actual usage exceeds expected levels, and if actual usage within a given interval surpasses the expected level, and to trigger based thereon to notify the user of potential leaks.

Dated this 30th day of October 2024.