Managing a citywide fountain network

Managing a citywide fountain network

Monitoring center, local control, water and energy management and maintenance organization

As the number of water fountains in a city increases, the problem of operation goes beyond the maintenance of a facility. The city manager must know which water fountains are ready to work, which ones need maintenance, how the consumption of resources changes and who is responsible for responding to each incident.

Integrated management can bring this information together in a common environment. Its value depends on the quality of measurement, control logic and the power of the operation team; Showing a few green marks on the map alone does not prove the correct functioning of the equipment.

This chapter presents the proposed multi-watershed management framework and examples of energy calculation, water balance, and service evaluation. All sample numbers are hypothetical and do not represent the specifications of an actual project or GSO product.

57–1. What is meant by the network of urban fountains?

In this chapter, "network" refers to a collection of independent fountains whose information and operation programs are managed in a common system. These fountains do not necessarily have a common tank, pipe or power source.

Three performance levels can be defined:

The project can start with monitoring first, and after local controls and tests are completed, it can become command capability.

Vortex introduces MaestroPro and the Link interface to manage one or more remote locations. This example shows the existence of such capabilities in the industry; The range of facilities for each project should be determined in the purchase specifications. Vortex water management systems ^[366]

57–2. Common birth certificate for all fountains

Before connecting the equipment, the identity of each asset must be clear. Using names like "main square fountain" is not enough; The local name may change or be used for multiple locations.

For each fountain, define a constant ID and associated file:

• Location and coordinates;

• Type of fountain and its use;

• Operation manager and maintenance contractor;

• Final drawings and equipment specifications;

• Water volume, pumping and treatment circuits;

• Water and electricity meters;

• Allowed programs to show;

• records of repair and change of settings;

• Stop and start instructions.

The original equipment should also have a separate ID. For example, the replacement of the pump should be recorded in the record of the same installation site so that the information of the previous pump is not mixed with the new equipment.

57–3. Proposed control architecture

For this book, the following three-level architecture is suggested:

Equipment level: sensors, pumps, valves, lights and related protections.

Local level: A controller that implements work sequences, constraints, and response to abnormal conditions locally.

Central level: receiving information, planning, reporting and sending commands within the allowed range.

The center sends a request to run a program; The local controller checks whether its execution conditions are met.

Introducing its professional control equipment, OASE explains digital programming and monitoring and remote access through the WECS controller. Communication capabilities should be designed together with the project's protection logic. Water fountain control and planning in OASE ^[367]

57–4. Information to be measured

The list of data is prepared based on the type of fountain. For example, the needs of a children's play fountain are not the same as a reflecting pool.

For each data, the unit, measurement location, range, accuracy check method and recording time should be specified.

A "pump on" command is not the same as proof of water flow. It is better for the system to separate the issued command, received status and measurable result from each other.

57–5. Data validity and time of last receipt

Data without recorded time can be misleading. The water level value of one hour ago should not be displayed as the current value.

For each value, one of the following states can be defined:

• authentic and fresh;

• old due to communication delay;

• Invalid due to measurement errors;

• out of service;

• Registered manually.

The unknown number must not be converted to zero. For example, meter disconnection does not mean zero consumption.

The sampling interval and data aging limit should be determined according to the application. Recording of daily consumption does not require the same time as protective reaction to a drop in level. Adequate safeguards must be in place with adequate response time.

57–6. Behavior when disconnected

Loss of communication with the center, power failure and sensor failure are three different events and should have separate responses.

The old decree should not be executed suddenly after a long delay. Each command can have ID, time of issue and validity period.

For the game fountain, the inability to prove the necessary operating conditions should lead to the stop of spraying or restriction of use according to the approved plan; The continuation of the show is not a priority over health conditions.

57–7. Manage alerts

An alert that does not have a responsible person and action is usually turned into a list of ignored messages.

For each alert, define the following:

"Receiving warning", "Accepting responsibility for proceedings" and "Fixing the cause" are three independent situations.

If a power outage at a location generates multiple sub-messages, displaying their relationship to the main event helps the operator. Eliminating or hiding independent causes is not the solution to reducing the number of warnings.

57–8. educational sample; The energy of six fountains

Let's assume that the display section of six fountains, including the equipment dedicated to the display, works with the following average power:

Calculation relationship:

$E=\sum P_i{t}_i$

Let's assume that the daily energy of purification and other supporting uses outside the table is 120 kWh:

$E_{\mathrm{کل}}=330+120=450kWh/day$

The powers in the table are educational assumptions about the average real power. In the project, using the rated power of the motor instead of measuring the input power can distort the estimate.

The measurement border should also be clear so that the lighting or purification power is not counted twice.

57–9. Modifying the display program and calculating the result

Now let's assume that after checking the usage request, the show hours change like this:

With the backing energy remaining constant in this example:

$E_{\mathrm{جدید}}=285+120=405kWh/day$

Daily reduction:

$\Delta E=450-405=45kWh/day$

Percentage reduction compared to the initial total consumption:

$\frac{45}{450}\times 100=10\%$

For the same 240 days:

$\Delta E_{\mathrm{سالانه}}=45\times 240=10800kWh$

This decrease is due to shortening of show hours; It does not mean increasing the efficiency of the pumps.

The report should also show the change in service level. Cleaning, disinfection and protection man-hours cannot be reduced simply in proportion to the reduction in display time.

Also, moving the starting hours may change the maximum power at the same time, but with the power and duration of work remaining constant, the energy consumption does not necessarily decrease.

57–10. Water balance sample to detect abnormal consumption

Let's assume that in a three-hour period without any show or rain:

• The meter registers the entry of 0.27 cubic meters of compensation water;

• The surface of the tank with a fixed horizontal area of 4 square meters should be lowered by 20 mm;

• Evaporation in this interval should be estimated as 0.03 cubic meters;

• A planned evacuation is not registered.

Changing the volume of the tank:

$\Delta V=A\Delta h$

$\Delta V=4\times (-0.020)=-0.080m^3$

If we call the unexplained output $U$:

$\Delta V=M-E-U$

Therefore:

$U=M-E-\Delta V$

$U=0.27-0.03-(-0.08)=0.32m^3$

Average rate:

$\frac{0.32}{3}\approx 0.107m^3/h$

It means about 107 liters per hour of unexplained output.

This result does not prove a leak. Unrecorded discharges, overflows, meter errors, level gauge errors, or inaccuracies in evaporation estimates should also be investigated.

The central system should identify this situation for handling and put together relevant records.

57–11. Appropriate indicators for comparison

Ranking fountains based on total consumption alone does not provide a fair comparison. A large display and a small pond do not provide the same service.

The suggested indicators are:

• Energy per hour of specific program execution;

• Compensatory water compared to the baseline of the same fountain;

• Service delivery hours according to schedule;

• The duration of handling the failure;

• number of repeated failures;

• The cost of maintaining each asset;

• Contribution of valid data in the reporting period.

For example, if 240 hours of service are scheduled in a month and 18 hours are not provided:

$A_s=\frac{240-18}{240}\times 100=92.5\%$

This indicator only shows the fulfillment of the service plan. The reason for the 18-hour stoppage must be recorded separately; A proper protective stop is not the same as failure due to improper maintenance.

Intervals with unknown data should also not be considered "successful" without explanation.

57–12. Convert information to maintenance plan

Data acquires operational value when it leads to a trackable action.

A suggested workflow:

1. Registering an unusual event or observation; 2. Initial review of data; 3. Determining the person in charge and priority; 4. Remote dispatch or support; 5. Record the cause and action; 6. Test after repair; 7. Close the work and check the repetition.

Crystal Fountains introduces remote support services, troubleshooting and commissioning of some projects with the cooperation of the on-site force. This pattern shows that central support and local presence can complement each other. Crystal Fountains technical support ^[368]

An increase in electric current or a drop in flow rate is not the only definitive diagnosis of pump failure. Program changes, valve status and channel blockages should also be checked. Analytical warning is better to show the probable cause and its evidence.

57–13. Remote access security

Access to fountain controls allows you to influence real equipment. In the Operational Technology Security Guide, NIST emphasizes limiting access, network isolation, and maintaining security controls over remote access. NIST Guide SP 800-82 Rev. 3 ^[369]

For the project, these measures should be checked in the system specification:

• specific account for each user;

• Separation of the right to view, change the program and change the settings;

• Multi-factor authentication for remote access;

• Protected communication path;

Limited and timed access of the contractor;

• Registration of commands and changes;

• The possibility of disconnecting remote access on site;

• Backup and restore test.

Connecting the controller to the Internet should not be done by making its management page directly available. The update should also be accompanied by a compatibility check and the possibility of returning to a workable version.

57–14. System purchase and information ownership

In purchase documents, terms such as "smart" or "smart city connectable" should be translated into testable capabilities.

Essential subjects of the contract:

The same name of the communication protocol does not prove the complete compatibility of two devices. List of data, units, commands and limitations should be checked before purchase.

57–15. Phased implementation and delivery test

For an existing set, a test run in a few select locations can reveal bugs before widespread deployment.

The delivery test should go beyond displaying the image in the center:

• matching identifiers with actual equipment;

• Comparison of system data with local measurements;

• Controlled disconnection and location behavior check;

• Checking communication return and recording records;

• Sending an invalid command and seeing its rejection;

• User access level test;

• review of water and energy reports;

• Test restore backup.

Remote initiation must be coordinated with the service status and on-site staff presence. Choosing the necessary repair and locking mode should prevent unwanted startup.

After the test period, the list of data and warnings will be modified and then the system will be expanded to other fountains.

57–16. Suggested images for layout

Figure note from the source manuscript

Figure 57-1: Management map of city fountains

Draw a sample map with the statuses "Running", "Scheduled Stop", "Requires Handling" and "Invalid Communication". In addition to color, statuses have labels.

*Subtitle:* "Common view of the status of water fountains, along with the time of the last information received."

Figure note from the source manuscript

Figure 57-2: Three-level management structure

Equipment, local controller and management center are shown. The place of implementation of protections and the path of data exchange should be clear.

*Subtitle:* "Central coordination with appropriate control and protection in each location."

Figure note from the source manuscript

Figure 3–57: Energy diagram of six water fountains

Draw two accumulated columns: initial consumption 450 and new consumption 405 kWh per day. Show and support parts are separate.

*Subtitle:* "The decrease in energy in the example is the result of changing the show hours; The backup consumption is assumed to be constant.

Figure note from the source manuscript

Figure 4–57: File of a water consumption incident

Compensating water meter, tank level diagram, balance calculation and visit result are displayed on a sample page.

*Subtitle:* "From registering abnormal consumption to investigating the cause and documenting the action."

For actual images from the GSO archive, include the project name, location, date, and installed capabilities based on documentation. A picture of a panel or control panel alone should not be taken as proof of integrated multi-site management.

The delivery system should allow the user to check the status of each water fountain with evidence, identify the person in charge and measure the effect of their decisions on service, water and energy.

Equipment reference