Procedure for repair and supporting maintenance processes of water and wastewater networks

Abstract

Method to support the repair and maintenance processes of water / wastewater networks, where sensors are placed at certain points of the network, the sensors measure physical parameters and have a data transfer connection with a control system After data collection rules are defined, registered and evaluated, each rule contains at least three files: - a first file contains the logic of the given rule, - a second file is a parameter list to which the logic applies, - a third file is a template that contains a description of the detected error and / or a description of the necessary actions, where reference ranges or limit values are compared with the parameter list using the logic, risk probabilities are formed as a result of comparison, and if a predetermined risk probability is reached, it is placed together with the assigned template in a manual event log module in the control system.

Description

[0001] PROCEDURE FOR REPAIR AND SUPPORTING MAINTENANCE PROCESSES

[0002] OF WATER AND WASTEWATER NETWORKS

[0003] The invention is a method to support repair and maintenance processes of water and wastewater networks, where sensors are placed at certain points of the network, the sensors measure physical parameters and are in a data transmission connection with a control system, in order to data collection.

[0004] In more detail, the invention is the creation of automation between a production management system supporting water production, water distribution and waste water treatment, and a work management system supporting pipe network and facility error repairs and maintenance works.

[0005] The invention may be needed where production management software systems for drinking water or wastewater services are available, and there is also a software solution for work management. Reducing the occurrence of error events (thereby reducing costs as an outstanding goal), which unexpected events can be prevented by starting automated maintenance, and the turnaround time for error corrections can be shortened.

[0006] The goal of the invention is to develop the partial automation of drinking water production and distribution, as well as wastewater treatment processes.

[0007] In order to achieve the goal, the processes were assessed and the points of the process that could be automated were identified.

[0008] The operation of such systems can be divided into three phases F1-F3.

[0009] Phase Fl: The signals collected by the equipment that make up the drinking water and wastewater treatment system, and the sensors installed on the pipe network elements, are processed by locally field PLCs and sent to the central production control servers via various communication channels.

[0010] Phase F2: A manual event log module developed in the production control system monitors the value of the signals and analyzes the operation in accordance with the set rules in its complex context. If a given signal indicates an event based on a rule, it triggers the creation of a fault repair or maintenance job towards the work management system.

[0011] Phase F3: The work created in the work management system is performed and administered by the responsible technical unit, and then closes the work.

[0012] According to the invention, rules are defined, registered and evaluated. Each rule contains at least three files:

[0013] - a first file contains the logic of the given rule,

[0014] - a second file is a parameter list to which the logic applies,

[0015] - a third file is a template that contains a description of the detected error and / or a description of the necessary actions.

[0016] We show the following example in detail. a. Definition and registration of rules

[0017] In the case of an exemplary embodiment, the rules are defined on Excel sheets. The rules are transferred from the Excel tables to the database of control system, where they are stored in data tables. Each device, including sensors, has a separate row, which contains the reference range and limit values of the given measurement parameter (such as vibration, temperature) and the step to be taken if they are exceeded. The rules defined by the user evaluate the totality of the incoming signals (information from the measurement data collection system), i.e., it is possible that several signals from the same equipment run in parallel and that signals from several equipment are combined in one rule. b. Check measured values

[0018] Checking the values means checking the compliance of the signals coming from the given equipment (several sensors can belong to one equipment) as set out in the rules. If the given signals are considered acceptable based on the rule, the measurement continues and the event is not activated. c. Evaluating rules

[0019] If the given signals are considered acceptable based on the rule, the measurement continues and the event is not activated. d. Initiating works

[0020] When a rule is activated, a new workflow is created in the work control (maintenance) system.

[0021] Automation is implemented between the production management and work management systems through a so-called interface. In the work control system, the type of work fixed in the rule is created, it can be error correction, maintenance or plant inspection. A work request or release is automatically made if the installation team can be assigned to the resulting task, e.g., based on location (specific equipment or pipe section map record).

[0022] The collection of rules: records the acceptable range of parameters for normal operation and the actions to be taken in case of data outside this range, e.g., if the number of vibrations of the pump exceeds the prescribed number per second, it requires maintenance. It is more common that signals from the same type of equipment differ by more than a value limit, e.g., the flow capacity of one sewage pump is reduced compared to the others. In this case, the reason for the discrepancy must be investigated. The rule management solution was developed in the control system as part of the manual event log module.

[0023] The rules, e.g., are checked every 4-6 minutes. In the parameter file, it is possible to put all lines in the test state, and if the conditions are met (there is no open worksheet started by the given rule, in the case of a rule to be enabled, the authorization has been done) the event is forwarded to the work management system.

[0024] In the manual event log, events are recorded and displayed, e.g., in tabular form. Events can be filtered and sorted. In the manual event log, events can be enabled per area, and users can only see events from their own area. The system sends a notification about the events that can be enabled, but in case of locking, new events are not recorded.

[0025] For practical designs, approximately 2-300 logic files are expected per production control system. A parameter file belonging to a logic file usually contains 50-200 parameter sets (lines). The number and name of parameters belonging to a parameter set may differ from rule to rule.

[0026] In summary, in the most general form of the invention procedure according to the introductory paragraph, rules are defined, registered and evaluated after data collection. Each rule contains at least three files:

[0027] - a first file contains the logic of the given rule,

[0028] - a second file is a parameter list to which the logic applies,

[0029] - a third file is a template that contains a description of the detected error and / or a description of the necessary actions, where the logic compares reference ranges or limits with the parameter list. As a result of the comparison, we form risk probabilities, and if a predetermined risk probability is reached, we place it together with the assigned template in a manual event log module in the control system.

[0030] In the following, the invention is discussed by an exemplary embodiment in a flowchart figure.

[0031] Figure 1 : a flowchart of the method according to an exemplary embodiment of the invention. In Figure 1, we can see that in step SI of the phase Fl, we initiate data collection, which is transferred to a production control system database. In the following phase F2, in step S2, we evaluate the rules that have been made according to the invention. A rule contains a parameter file, a collection of rule logic and a template for the given element. In the next step S3, we check if there is an open entry for this error in a manual event log. Note here that the manual event log is a table that contains all the aspects necessary to conduct a maintenance or repair event.

[0032] In step S4, we check if there is an entry update. If yes, then we have reached the end of the procedure, if we do not make an entry in the manual event log in step S5. After that, in step S6, we check whether prior approval is required. If so, in step S7 we check whether the problem is real. If not, the process is over. If yes, in step S8, the work request is recorded in the work management system. After that, in step S10, feedback is given in the manual event log.

[0033] In phase F3, we reach the end of the process and in step S9 we implement the management of the actual work. This can be repair, maintenance or other interventions in the water or wastewater system.

[0034] In some embodiments, the physical parameters measured by the sensors are selected from the following: pressure, temperature, vibration number.

[0035] The logic of the rule may include the method of comparing reference ranges or limit values and the method of forming risk probabilities.

[0036] In some embodiments, we sort the manual event log items according to risk probabilities.

[0037] In the template, we can prioritize the importance of the detected error and sort the elements of the manual event log according to importance. The definition and registration of the rules can be done, e.g., in Excel tables.

[0038] In several cases, the sensors are at least partially connected to the control system via wireless data transmission. Sensors are usually placed on pipes, pipe connections, pipe branches, valves, pumps or other water engineering elements.

[0039] The solution according to the invention is suitable for carrying out repair and maintenance works in a rational manner. The procedure covers the pipe network and facility processes of drinking water production and wastewater treatment.

Claims

CLAIMS1. A procedure to support repair and maintenance processes of water and wastewater networks, where sensors are placed at certain points of the network, the sensors measure physical parameters and are in a data transmission connection with a control system, after data collection step (SI), rules are defined, registered and evaluated in a step (S2), each rule contains at least three files:- a first file contains the logic of the given rule,- a second file is a parameter list to which the logic applies,- a third file is a template that contains a description of the detected error and / or a description of the necessary actions, where reference ranges or limit values are compared with the parameter list using the logic, risk probabilities are formed as a result of the comparison, and if a predetermined risk probability is reached, it is placed together with the assigned template in a manual event log module (S5) in the control system.

2. The method according to claim 1, where the physical parameters measured by the sensors are selected from the following parameters: pressure, temperature, vibration number.

3. The method according to claim 1, where the logic of the rule includes the method of comparing reference ranges or limit values and the method of forming risk probabilities.

4. The method according to claim 1, where the elements of the manual event log are sorted according to the risk probabilities.

5. The method according to claim 1, where the importance of the detected error is ranked in the template and the elements of the manual event log are sorted according to importance.

6. The method according to claim 1, where rules are defined and registered in standard Excel tables.

7. The method according to claim 1, where the sensors are at least partially in a wireless data transmission connection with the control system.

8. The method according to claim 1, where the sensors are placed on pipes, pipe connections, pipe branches, valves, pumps or other water engineering elements.

Images