5.1. Quality Assessment of Several Real Events
The application of MoFoDatEv leads to optimal results for
and
for each event. These parameters are optimized for the best time frame, based on
and
, out of a given grid. To classify the different real events,
Table 2 was created with the parameters
,
for the optimal time frame selected from all combinations and
for the start and
for the end of the pressure drop. Furthermore,
for the pressure level difference of the whole event and
for the time difference are presented.
Table 2 shows the events with the above-mentioned parameters. The table is sorted in ascending order with respect to
. In the first step, all events were neglected which have
or
. Larger absolute values mean that the pressure drop is extremely early before or after the LDTP and the difference between
and the LDTP is too large considering the speed of sound and the network size. Therefore, the third criterion from
Section 4.1 is not fulfilled and the PDTP and LDTP seem not to match in a physical sense. Furthermore, events with a negative value of
are winnowed. Negative values lead to a pressure rise, not to a pressure drop. Based on all 22 events, only 16 events remain. For these 16 events, a comparison is performed between
and
. The results are shown in
Figure 5.
The figure shows the pressure level difference
found by MoFoDatEv with respect to the refill mass flow level difference
for each event. A strong correlation is visible, which is indicated by the black dashed line. The pressure level difference is linearly related to the refill mass flow level difference. Experience shows that leakage localization is very hard below a change in the refill mass flow of 50
. It was assumed that pressure waves are not distinct enough in these cases. This matches well to the small pressure level differences extracted by MoFoDatEv in the case of these events. However, the greater the pressure level difference, the better the data set can be evaluated. Therefore, seven data sets (red, orange, yellow, and black) with
(red horizontal line) were considered in more detail.
Figure 4 shows an example of sensor data within each of the seven data sets to get an impression of the pressure curves. As a result, the point for event 14 was shifted (light green dotted circle in
Figure 5).
For the further analysis, these seven data sets are divided into four categories, which are presented in
Table 3.
The table indicates how well the data sets correspond to MoFoDatEv. The color red means a low consistency with the model and a low evaluability whereas orange and yellow show middle and high consistency with the model, respectively, but also low evaluability. At the end, the color green leads to a middle consistency with the model and a high evaluability. For each of these seven data sets, the different pressure curves were evaluated in detail.
Figure 6 shows the pressure curves for one selected sensor for each of the seven data sets where MoFoDatEv found a small pressure level difference
. MoFoDatEv can evaluate events with suitable results if the pressure level difference before and after the LDTP is large enough and if the change takes place reasonable fast. The seven events in
Figure 4 are sorted from left to right and top to bottom in ascending order of their value of
. The pressure curves are evaluated to find the start of the pressure drop. To this end, evaluation is easier for pressure curves with larger
values.
The first pressure curve is for sensor 1 from event 7 (top left, red). The data set does not match the model assumptions used in MoFoDatEv, hence the results of MoFoDatEv are not reliable. In contrast to
and
found by MoFoDatEv, the pressure in fact declines in between −50 and +20 s, which is a rather long period of time. As mentioned previously, the PDTP and LDTP do not match in this case and the data set is not taken into account for further considerations. Altogether, this event is colored red (cp.
Table 3) because the consistency with the model and the evaluability are low.
The next three events are number 10, 5, and 11, with selected sensors 35, 10, and 43 (top right and upper middle row, orange), respectively. Those three events present a middle consistency with the model but also a low evaluability. The refill process seems to be superposed by other processes in the DHN to a large extent. Furthermore, there are some large oscillations which lead to conspicuous pressure drops. Therefore, the pressure wave of the real event cannot be evaluated exactly. For event 11, the pressure values seem to be on the same level the whole time with only one exception around the LDTP. However, this is not interpretable because it does not correspond to the model conception with higher start than end values.
The following events, 9 and 8, with selected sensors 45 and 4 (lower middle row, yellow), respectively, show a high consistency with the model but a low evaluability. The pressure level difference is not very much larger than the noise of the pressure data. Furthermore, the data rate is low. Event 9 shows three plateaus and the pressure decreases slowly. A clear pressure drop is not visible which could be evaluated. Event 8 also shows no clear pressure drop. In the end, it seems that the pressure will further decrease.
The last dataset to be considered was event 14. The measurement data have a middle consistency with the model and a high evaluability. A clear pressure drop around the LDTP is recognizable. The pressure level difference found by MoFoDatEv is the largest here, with . However, it is clearly visible that MoFoDatEv underestimates the real change in pressure by a factor of almost two.
Based on this analysis, for the further evaluation, the six events 5, 7, 8, 9, 10, and 11 are excluded. However, event 14 will be further considered. This event is also light green in
Figure 6. Therefore, only 10 data sets are remaining. These 10 data sets are now compared with respect to the duration of the pressure drop
and the duration of the refill mass flow rise
. In
Figure 5, the results are presented.
Figure 7 shows the duration of the pressure drop
with respect to the duration of the refill mass flow rise
. Both durations seem to show a correlation but take place on two totally different time scales. The duration of the refill mass flow rise is constituted in minutes and the duration of the pressure drop in seconds. For the duration of the pressure drop
, the results were determined with MoFoDatEv. A strong correlation for the remaining ten data sets is visible. Large parts of the events are refill processes, which act like a real leakage on the entire network. The increase in the replenishment quantity during a refill process depends strongly on how the corresponding motor-driven or manually operated valve is moved. This can be opened quickly; hard and abruptly; or rather slowly, gently, and smoothly. In practice, both operations are possible because the management of leakages relies on the experience of the operators. The effects of a leakage are highly dependent on its position in the network [
24]. In the case of a real leakage, a fast pressure change in a short time period is expected.
These differences can be seen exemplarily in events 20 and 22. In event 20, the duration of the refill mass flow rise (35 s) and the duration of the pressure drop (10 s) are very small. However, the replenished quantity is 100.5
, which seems to be a larger leakage based on the refill mass flow (cp.
Table 1). In contrast, for event 22, the duration of the refill mass flow rise is about 3 min and the duration of the pressure drop is 28 s, which is very long. The green event 14 (cp.
Figure 6) is an outlier because MoFoDatEv extracts the values of
and
inexactly. If better values are extracted manually, the point also shifts upward by a factor of two (light green). During this event, the duration of the refill mass flow rise is very long, at 6:41 min, whereas the duration of the pressure drop covers only a short time period of 10 s. This leads to the fact that the consistency with the model is middle but, in contrast, the evaluability is high, as shown in
Table 3. Based on the detailed evaluation steps, all 22 events are classified in three different groups. The groups are presented in
Table 4.
The table shows the 22 events divided into three different groups. Each group is sorted based on their values of
, in descending order. Additionally, the table contains the values for
,
,
,
,
, and the length of the time window. The first group contains all events which have a high consistency with the model conception and also still have high evaluability. These were the remaining 10 best events. Each event has its own optimal time frame
,
with different time lengths. The average length is 121 s and
and
on average. Moreover, in the first group, all events have a high value of
, which indicates a high pressure difference between the start and end pressure values. Therefore, the pressure drop is expected to be better analyzable and these events can be well evaluated according to a small
. The second group contains all events which have a worse consistency with the model and a low evaluability. In addition, the whole time frame starts later with
but ends with
a bit later. These events have a low/middle/high consistency with the model conception and low evaluability (cp.
Figure 6). This is also reflected by the smaller values of
. The third group contains all events which are neglected based on
Table 2. For these events, the third quality criterion from
Section 4.1 is not fulfilled and the PDTP and LDTP seem not to match in a physical sense. Furthermore, the events 6 and 21, with a negative value of
, are neglected. The value of
is then also negative, which indicates a pressure rise instead of a pressure drop. This is not admissible. The evaluability with MoFoDatEv of these events is also not successful because the values of
are very high.
With the development of MoFoDatEv, it was possible to evaluate all 22 real events. Each event represents a leakage in the network. Most of them were refill processes, which act like a leakage on the network. Based on the different analysis steps, the events can be classified into three groups. Events which have a middle or high consistency with the model and also events which do not correspond to the model concept. MoFoDatEv cannot only be used to evaluate the events, but also to localize the leakages directly. The application is presented with artificial and real data in the following section.
5.2. Leakage Localization with MoFoDatEv
For the application of MoFoDatEv for leakage localization, the measurement data of event 22 are considered as well as artificial data. The overall best time frame is defined with
. For the generation of the artificial data, MoFoDatEv was applied to event 22. As a result, the values of
,
, and
are available. Furthermore, all
and
values are available. From the real data set, the time points and sensors are kept and only the pressure values are replaced with data generated by MoFoDatEv. These calculated values are then the “new real data”, the artificial data. For localizing the leakage, the aforementioned 28 TLs were placed in the whole network. For each TL
j, the start value search is determined as described in
Section 4.1. However, for the leakage localization, the overall best time frame is fixed and is not optimized. Therefore, only start values of
and
will be searched over with the rough map and then optimized. For both data sets, artificial and measurement, the leakage localization is performed with perfect start values as well as a rough map for the start value search. The advantages are presented in
Table 5.
The table shows four levels of difficulty for the application of MoFoDatEv to localize leakages. The first case is the usage of artificial data with perfect start values to localize the leakage with MoFoDatEv. This is the easiest case and is used to check the model for the localization task. The perfect start values are exactly the same values which were used to generate the artificial data. If this execution is not possible with the artificial data, the measurement data would not be suitable either. The second case also uses artificial data, but the start values are searched for over the rough map. Then, these values are optimized and used for the localization. This is a little bit more difficult because it is not clear whether reasonable start values or the optimum can be found. More difficult is the third case, where perfect start values are used with the measurement data. If it is possible to evaluate the measurement data with perfect start values to achieve suitable results, then MoFoDatEv is robust and can work with artificial and real data. The last case, with a rough map for the start value search for the measurement data, is even more difficult. No preconditions or other information are available. The start values have to be determined directly from the measurement data over the rough map and following optimization. For all four cases, the leakage localization was performed. The results of the achieved ranking are presented in
Figure 8 with a simplified network topology.
The figure shows the results of the leakage localization with MoFoDatEv with coloring of the EAs according to the ranking. For representation, the investigated DHN is shown with its simplified network topology and the right leakage of this event is located in the EA with the black lightning. The coloring indicates the ranking from Place 1 (red) to Place 28 (green) so that the leakage is in the respective EA. The color red means that this EA has the smallest
and the leakage will be in that EA. As the value for
increases, the color changes from red across orange and yellow to green. Top left presents the result of the artificial data with perfect start values for the following optimization. The EA affected by the leakage is found perfectly because it is colored red. The success of this case indicates that the model is now suitable for leakage localization and it could be continued to check the other cases. Top right shows the result of the artificial data with start value search and following optimization. For the data evaluation, the overall best time frame was determined (cp.
Table 2). For this purpose, the values for of
and
of the time frame
were also calculated. These values are now the start values for the optimization, which leads also to the correct localization of the leakage in the EA containing the black lightning. Therefore, reasonable start values were found over the rough map. After the investigation with the artificial data, MoFoDatEv was also applied to the measurement data of event 22. Bottom left presents the result for the measurement data with the same perfect start values for the optimization as with the artificial data. The affected EA is located as the EA with the color red, which is not the correct one but it is also next to the right EA with the black lightning (color orange). The deviation could be explained with measurement noise within the real data, which has an influence on the correct evaluability. However, a suitable result is achieved. The last result is presented at the bottom right in the figure, which shows the result of the measurement data with a start value search and following optimization. Here, the affected EA by the leakage is also located by the EA with the color red, which is the wrong EA but is also next to the right EA with the black lightning (color orange).
With artificial data, it is proven that the idea fulfils the task for the leakage localization and the application of MoFoDatEv works. For practical purposes, an optimization with perfect start values is not possible because they are unknown. However, with a start value search over a rough map, the model can be applied to real data, which leads to much more plausible results in the neighborhood of the right EA for event 22. In fact, there is no difference working with perfect start values or with ones from a start value search. Due to these plausible results, MoFoDatEv was also applied to all other events based on
Table 1. For each event, their start values were searched for with the rough map and then the optimization was performed. To compare all events, the aforementioned PC from
Section 1 was used. The results are presented in
Table 6.
The table shows the comparison of the leakage localization performance between the best BCP algorithm applied in [
3] and MoFoDatEv. The BCP algorithm was applied in the optimal time frame of
, and for MoFoDatEv the time frame
was selected. All 22 events were also categorized similarly to the result of
Table 4. Based on the PC values, all events were evaluated differently. The range of the PC is, for the BCP algorithm, from 100.0% (first place in the ranking) to 35.7% and, for MoFoDatEv, from 100.0% to 3.6% (last place in the ranking). With an average value of 77.3% for the BCP algorithm and 74.4% for MoFoDatEv over all events, suitable leakage localization results were achieved. Therefore, this novel method is not much worse than the BCP algorithm from the literature. In five cases, the affected EA by the leakage is in the first place. In contrast, BCP ranks the affected EA in the first place only for four events. Furthermore, for ten events, the right EA is in the first three places in the ranking (PC ≥ 92.9%) with MoFoDatEv. Only nine events are in the first places in the ranking with the BCP algorithm. However, events 9 and 10 show that there could be some improvements necessary within MoFoDatEv to reach higher PC values. The three different groups are established based on the quality assessment in
Section 5.1. If only the best ten events within the first group were considered, then MoFoDatEv achieved a higher average PC of 79.3% compared to 72.9% for the BCP algorithm. Only three times, for events 14, 20 and 22, did BCP reach a higher PC value. Within the second group, the BCP algorithm is, with 86.3%, on average better than MoFoDatEv, with 62.5%. For events 5, 9, and 11, the affected EA were ranked in the first place with the BCP algorithm. These three events were neglected, based on
Figure 6, for the following evaluation with MoFoDatEv, because the pressure difference
was not high enough. Therefore, events 9 and 10 reached only a PC value of 7.1% and 3.6%, respectively. The last group is based on the analysis of
Table 1. The value of
was inadmissible and the value of
was negative. BCP reaches 75.6% on average in this group whereas MoFoDatEv reaches a better value of 81.5%. This illustrates that, theoretically, even these data sets can be evaluated and lead to a suitable ranking result. It could be possible that the LDTP was determined falsely. If the pressure difference is high enough, then MoFoDatEv should be used for leakage localization because more information remains and both evaluation steps for the determination of the PDTPs and the attribution to EA could be combined.