2.1. Survey Results
The questionnaire that was conducted surveyed responders on multiple breakdowns in the water network and on their decisions. Forty-six top management employees from water utilities participated including CEOs, CTOs, and also consultants, IT specialists, and water distribution system modelers. The survey included a diagram of a water supply network (
Figure 2) that was an excerpt of the BPDRR model. Breakdowns were marked in red, leaks in black, and critical points (hospitals, fire-flow nodes) were highlighted.
Questions concerned the determination of the sequence order repair tasks were to be completed on that water network. The key focus of this survey was to understand how, in such cases, real life decisions are made. There were two assumptions we decided to make:
Each repair crew was assigned 4 tasks. The answer provided most frequently has been bolded.
Table 1 presents a matrix of responses: breakdown IDs versus the sequence in which they should be overhauled, with a focus on 4 initial tasks.
Survey results were used to determine the order of tasks assigned to each of the crews.
Table 2 presents the determined order of task delivery.
The following rough approach could be drawn upon the analysis of responses to the questionnaire: breaks on the way to strategic points should be repaired first, followed by breaks on the pipes with a larger diameter, and then all other breaks closing the list. Additionally, responders were asked to assign weights (from 0 to 10) to 4 defined criteria that addressed the rapidity of recovery, number of nodes without service, and volume of water lost. Such an approach derived from the need to simplify the questionnaire and to acquire potential preferences in the decision-making process.
It was not the purpose of this paper to publish questionnaire results since, due to the limited number of responses received, it did not have adequate statistical power. Instead, the intent behind the questionnaire was to receive some ‘voice of the decision makers’. Survey results were applied as the direction in the decision-making process, not as the decision made arbitrarily.
2.2. Developing the Ranking
The research that we undertook was conducted on a hydraulic model provided by BPDRR organizers [
23]. It contained 4909 junctions, 6064 pipes (402 km), 1 reservoir, 4 pumps, and 5 tanks.
During the first hours of the simulation, in some nodes there were firefighting demands—35 L/s (please check ‘Damage_Scenarios.xlsx’ attached into
Supplementary Materials). As dictated, each site on fire was extinguished with precisely 756 m
3 of water. However, since pressure-deficient conditions were met in the network during most of the restoration time, the demand could not be fully supplied. To model partial supply, a pressure-driven analysis (PDA) must be used.
Water supply (
Qi) in node
i is, therefore, the function of the pressure head (
pi), the demand in node
i (
QDi), and the pressure head required (
preq) to fulfill that demand in node
i (
preq = 20 m). Results of each of five scenarios were evaluated using provided EPANET2 [
24] models. In order to solve the PDA model of a WDN with regards to the flow–pressure relationship, Wagner’s power relationship (1) was used.
To solve this equation, four types of artificial Epanet elements: Flow Control Valve (FCV), Throttle Control Valve (TCV), Check Valve (CV) and reservoir (R) were added to all demand nodes in the model, allowing this algorithm to enforce pressure-driven demand. This noniterative method allowed us to calculate the available flow during failure conditions. Further details on PDA calculations in Epanet can be found in article [
25]. Various failure scenarios were analysed using this model as the basis. The main goal of this task was to determine the work schedule for 3 teams that could repair different breakdowns in parallel.
The detailed description of the problem along with required tasks are presented in the ‘Problem description’ in [
23]. Having the target to find the solution to the BPDRR problem, hydraulic analyses on the obtained base model were performed.
Analyses were conducted on that water network, and flows were read at 9:00 AM—the peak time of maximum demand. The results are presented in this paper in
Figure 3 and
Figure 4.
Figure 3 focuses on the distribution of diameters, and
Figure 4 focuses on hydraulic conditions and the distribution of flow.
An analysis of the network’s hydraulics may lead to the assumption that, due to a high value of diameter/flow, only a limited number of pipe sections are hydraulically important, whereas the significance of the other ones is similar. Our approach to finding the solution to the stated problem assumed that first a list of water pipes should be created and then each classified with various parameters (i.e., A—diameter, B—diameter and distance from source, C—diameter and velocity, etc.).
The setup of the prioritization of rankings had to fulfill the following assumptions:
Rankings had to be developed on the provided water distribution network model that had been built under normal working conditions (BPM-EPS).
Rankings had to be created as a part of a strategic document (i.e., the water safety plan). The prioritization scheme had to address all types of possible accidents (earthquakes, floods, wars, etc.) that could cause numerous breaks in water networks. All elements of water distribution networks had to be taken into account (water intake, water treatment stations, and water distribution networks).
Development of the ranking had to be ‘as easy as only possible’. The key issue water utilities face, especially those from Central and Eastern Europe, is a lack of detailed data related to their networks. Only selected utilities possess reliable data on their networks and also calibrated models. Thus, the root cause behind the development of any ranking is that, in case of any damage, the strategy for network operators to follow had to be clear and intuitive. Events as extreme as earthquakes give no time to compute various scenarios, search for lacking data, research for operational hydrants, and so on. In our opinion, such events required ‘ready to do’ lists set up beforehand that covered the most critical pipes that, in turn, determined the sequence of next actions to be performed.
During development of the rankings it was possible to include the application of compensational tanks, yet only under the condition that the volume of water collected for emergency purposes had been clearly defined.
The proposed method of ranking approach to scheduling repairs of water distribution system consisted of three steps: The goal of the first one was to select prioritization criteria and construct the ranking. The purpose of the second step was to calculate values for all criteria that had been provided in the problem descriptions to evaluate the performance of the target solution, while the third step focused on choosing the best ranking for the scenario. These are the criteria we proposed to set up rankings for the given problem:
A—Diameter
This ranking is based on the pipe diameter only.
Figure 5 presents the choice of five main pipes with largest diameters that should be repaired first, followed by the others with smaller diameters (
Figure 6).
Rankings based on the ‘diameter size methodology’ gives maintenance priority to pipes with the largest diameters. The main advantage of this method is its simplicity, and that such a ranking can be developed without a calibrated model of a given water distribution system. The main disadvantage, however, is that it does not take into account hydraulics nor topology of the network (flows, velocity). It is also not possible to distinguish the importance of pipes of the same diameter (the search for pipes with the same diameter randomizes their position in the ranking).
B—Diameter and distance from source
According to this methodology, two criteria can be taken into account: pipe diameters and distance between their counterpoints and the source. This simple method does not require a calibrated model of a water network, yet it partially includes hydraulic characteristics of the network and its topology.
C—Diameter and velocity
This methodology sets the pipe diameter as the key criterion. Prioritization is calculated based on the hydraulic load of pipes. It is assumed that for pipes of the same diameter, higher velocity shifts their priority in the ranking.
D—Flow
This ranking methodology sets priority to pipe sections with the higher flow at the time of maximum demand (
Figure 7). Network hydraulics are taken into account.
E—Flow (including strategic points)
The logic behind the D ranking makes use of the flow in the network—pipes with higher flows (at the time of maximum demand) are set higher on the repair sequence list. The E ranking additionally includes the priority of strategic points (for hospital and fire flow nodes, an additional flow of 35 liters per second is added). Due to negative pressure, such a model does not correspond to reality, but it allows us to determine a hydraulic path to the strategic points. Using this method, it is possible to include all types of strategic points.
Figure 8 presents the distribution of water fire flow where this type of ranking is based.
F—Impact of pipe closures on network hydraulics
This approach is based on an assumption that in every network there are pipe segments where any break causes a pressure drop in the whole network. In the analysed network, closure of pipe #168 caused a negative pressure across the entire network (
Figure 9), while closure of pipe #88 only resulted in a local drop of pressure (
Figure 10).
During normal system exploitation, the water supply to every node and in all time steps was met. Thus, closure of a single pipe results in decreased pressure. In the course of analysis for certain nodes, negative pressure was received. This is interpreted as a lack of water supply to consumers that have been assigned specific nodes. Consumers with no access to water supply (calculated as the sum of water usage in out of service nodes) is the measure of the influence of a pipe’s closure on network hydraulics.
2.3. Calculation Methods
The
Figure 11 presents the general calculation flowchart for the delivery of the repair schedule.
Input data upon which calculations were to be based were provided via a file that contained the hydraulic model of the damage scenario and the list of breaks and leaks. Simulations were conducted using the Matlab environment. Epanet’s model calculation was executed directly in Matlab with the Epanet–Matlab toolkit installed [
26]. This package utilizes the Epanet.dll library for hydraulic calculations, which enables further processing of objective functions. Setup of controls within the hydraulic model was required to model the maintenance of brakes and leaks (isolation, reparation, and replacement). A dedicated Matlab script was prepared solely for that purpose. Calculation of the objective functions for 6 criteria required around 1 h. It is worth mentioning that the complete calculation process was realized on a standard PC (Intel i5, 16Gb) with average processing speed. If any real deployment were to be found for solutions of this type, it would be required to specify the time necessary for an operator to make a decision with the use of our solution as the decision support system.
Our solution’s purpose was to generate the sequence of tasks that in the following steps needed to be assigned to individual repair teams. A separate list of tasks was then generated for each pipe damage.
Table 3 presents such a sample tasks list.
During the next stage, the list of tasks to be repaired was sorted by pipe ‘importance’, in accordance with the selected ranking. The team that became available was then assigned a sequence of repair works. This process was complete once all teams received their task lists. These, initially as text files with controls, were then imported into the Epanet model. During simulation of the repair schedule model, objective functions were calculated, and results were saved as a file. To sum up, for all 6 proposed rankings and 5 different sample scenarios, repair works were scheduled and simulated for all teams in accordance with the method that has been presented above.
2.4. Evaluation of the Ranking Solutions
In order to find out which of the rankings appeared to best answer all given scenarios, Visual PROMETHEE was used to evaluate them, based on weights assigned to criteria [
27]. PROMETHEE I and II are relatively simple ranking methods that were initially delivered by Brans in 1982 [
28], with latest VI generation on the market today. There are several specialized software programs, including PROMCALC, DECISION LAB 2000, Visual PROMETHEE, and D-Sight [
29], where PROMETHEE methods have been applied and delivered to the market as tools that could be used to provide needed solutions and to decrease the decision-making time.
The choice of Visual PROMETHEE was made because of its key ability to handle differences among evaluations of variants, made for all criteria. Multicriteria decision analysis (MCDA) helps decision makers incorporate various, often conflicting, priorities into an evaluation of alternatives. The best solution is selected out of all alternatives in the process of performance assessment that is based on preselected criteria [
30,
31,
32,
33].
In the PROMEHTEE II method, the search for the optimal solution has been included in five implementation steps:
Step 1—designation of preference function values for all variants and all criteria. This function needs to be separately defined for each criterion, and each needs to receive a value from the range between 0 and 1. The smaller the function the greater the indifference of the decisionmaker; the closer to 1 the stronger their preference.
Step 2—designation of equivalence thresholds for all variants and all criteria.
Step 3—designation of preference thresholds for all variants, individually for each criterion.
Step 4—determination of the multicriteria preference index and, finally, the matrix of indicators, based on the preference degree:
where
k represents the total number of criteria,
h = 1, 2, …,
k,
a,
b ∈
K is the quantity of alternatives, and
Ph(
a,
b) expresses the preference function between
a and
b alternatives.
Step 5—settlement of the ranking of variants based on net dominance flows, defined as:
A positive net flow (outgoing flow) expresses the degree to which the considered variant outmatches all the other ones—Equation (3). Negative net flow (incoming flow) expresses the degree to which the considered variant is outranked by all others—Equation (4). For this BPDRR case it is the PROMETHEE that was chosen, mainly because the analysed alternatives (
Section 2.2 Developing rankings) were not comparable in this method. To apply the PROMETHEE method, Visual Promethee Academic Edition [
34] was selected to rank all six types of alternatives (
Section 2.2).
The following are indispensable to sequence available alternatives by Visual Promethee:
- (a)
Preference measure (evaluation matrix),
- (b)
Weights,
- (c)
Preference function.
Ad. a) Preference measure (evaluation matrix)
Input evaluation matrix for PROMETHEE is the result of calculations described in
Section 2.3 ‘Calculation Method’.
Table 4 presents the formulated evaluation matrix. This matrix lists alternatives ranking from A (diameter), B (diameter and distance from the source), C (diameter and velocity), D (flow), E (flow including strategic points), and F (impact of pipe closures on network hydraulics).
Results that best met the required criteria are bolded and framed. In the green background, however, these alternatives were listed that met the highest number of criteria at a time, under the condition that all weights are equal. Having reviewed feedback received from water utility staff, it turns out that decision makers subjectively applied different weights to six criteria already discussed. Objectively, alternatives marked green are not optimal in all cases. Following this input, the influence of applied weights on achieved results has had to be considered (Table 6).
Ad. b). Weights:
The values of weight of each of six defined criteria were determined on the basis of responses to the conducted survey. The reason the same weights were applied to criteria C_03 and C_06 and also C_04 and C_05 was due to responders’ actual misunderstanding of questions that had been stated in the poll. The reliability of the questionnaire survey can be leveraged by looking at the small number of responses received. Yet, since questions required clear answers, only highly ranking professionals with daily insight into modeling could have been accepted as relevant responders. Despite the target team being relatively small, there were professionals behind all feedback received. The goal set for this article was solely to illustrate possibilities in how alternatives could be compared via the PROMETHEE method. The purpose was not, then, to deliver any set of unequivocal weights of criteria that in turn should be applied into the decision-making process. Questions in the questionnaire addressed very fine details, and already having received answers, we found out that responders had not really noticed these fine details we had asked them. Thus, in the case of the points mentioned above, they were clubbed, and the responses received are shared for these pairs (
Table 5).
At this point, the question should be asked if these six criteria that had been predefined by the BPDRR committee proved to be sufficient to enable a correct evaluation of alternatives. According to the authors, there were numerous other factors that had to be applied to analyse a problem of such complexity. During discussions with responders, it turned out material availability in the warehouse, road conditions, issues related to occupation of traffic lanes, access to industrial hydrants and fire tanks, and the need to supply water to the largest industrial consumers appeared to be the factors that had the greatest degree in deciding the sequence of repairs to be undertaken.
Ad. c) Preference function:
Visual Promethee enables the preference function to be expressed in six different types: linear, usual, V-shape, U-shape, level, and Gaussian (
Figure 12). This function is based on three thresholds: preference, incomparability, and equivalence. Definition of threshold values is the key input required to measure the strength of preferences. In effect, the preference function values range between 0 and 1. In the case we analyzed, the usual type of the preference function was defined for all six criteria.
The choice of the usual type implies that the decision maker would have strict preference for the alternative of the greatest value. Even in case of small differences among criterion values, the alternative with the higher value is selected [
29].
Summing up the applied method, it should be highlighted that, rather than pointing out the ‘right’ decision, PROMETHEE and GAIA (Graphical Analysis for Interactive Aid) methods help decision makers find the alternative that best suits their goals and their understanding of the problem [
35]. It leads to a comprehensive understanding of the structure of the decision problem, identification and quantification of its conflicts and synergies, clusters of actions, and highlights the main alternatives and the supported structured reasoning [
33].