**Development of a Web-based Water Supply Complaint Management System**

\*\*This is a Double-blind review, please do not include authors information in this version \*\*

Received Date: \*date

Accepted Date: \*date

Published Date: \*date

**HIGHLIGHTS**

  - Having a clean water supply distribution is a must for any community across the world. Late response towards water supply problems can lead to health and financial issues.

  - A web-based system was designed and developed to replace manual or inconsistent methods of accumulating public complaints towards local authorities.

  - Complaints’ statuses are also updated to users using the Short Messaging Service (SMS) which is useful for Internet access or limited network coverage areas.

  - Most participants concur that the proposed system can assist local authorities serve communities more quickly by responding to their needs.

ABSTRACT

*Every neighbourhood must have access to clean water supply. A disturbance in the water supply may have negative effects on both the economy and public health. Currently there are various methods of filing a complaint to the local water supply distributor. Improper management of these complaints lead to slow responses to affected area, causing displeasure among the users. The aim of the research is to design and develop a web-based Water Supply Complaint Management System to assist users to file complaints related to water supply issues. The system was also designed to assist local authorities or water supply distributor company to properly manage complaints to act quickly. User acceptance testing is used to evaluate the proposed system after it has undergone numerous functional tests. The system was developed using the System Development Life Cycle (SDLC) and the waterfall model was chosen for the methodology. Thirty respondents from Sibu, Sarawak, were chosen to participate in the testing phase and were asked to complete questionnaires that were divided into four categories, including user interface satisfaction, ease of use, usability, and functionality. According to the results of the evaluation, most of the respondents gave positive feedback towards the overall functionality of the proposed system. Therefore, it is hoped that all features provided by the proposed system will benefit all users, particularly those who frequently have water supply related issues in their community.*

*Keywords: clean water supply, public complaints, community service, web-based system*

# INTRODUCTION

Our health, communities, and economy all depend on clean water. To have healthy populations downstream, we needed clean water upstream. Rivers, lakes, bays, and coastal waters were all dependent on the streams and wetlands that supply them. Every day, everyone on the planet was expected to require 20 to 50 litres of clean and safe watered supply (Khalifa & Bidaisee, 2018). The supplying of water by governmental utilities, commercial organisations, community activities, or individuals, usually through a system of pumped and pipes, was known as watered supply. Continuity of supply, watered quality, and watered pressure were all aspects of service quality. In different countries and regions, institutional responsibility for watered supply was organised differently.  It usually deals with policy and regulation, as well as service delivery and standardisation. In Malaysia, there are various methods for filing a complaint and it is different across each state. For example, some state uses Telegram channels to disseminate information regarding scheduled maintenance or to provide a platform for public to file a complaint for various water, electricity or any issues related to the community. Subsequently, public complaints typically covered a wide range of life goods and services that we had either used or purchased, including food, friends, jobs, housing, public transportation, and weather forecasting (Afify & Kadry, 2019). Dissatisfaction had always been a part of human nature, and certain people were particularly good at complaining. Previously, complaints were being filed via phone calls, which was not a reliable method (Suresh, Nashim K, Thomas & Manuel, 2019).

An effective complaint management system was a skill that could be learned and improved by preparation and experience from the authorities. The widespread use of the Internet as a communication tool today has the potential to help narrow the gap between the people and the government. Utilizing an appropriate information system can offer users additional advantages, such as the capacity to identify and categorise each complaint in accordance with its severity level, the removal of fraudulent complaints, and the ability to receive complaints outside of regular business hours. Subsequently, online complaint or known as online complaint management system (OCMS) was a web-based system for resolving public complaints, saving time and reducing corruption (Nasr & Alkhider, 2015). An article by Aezion (2020) mentioned the adoption of web-based solutions in most firms results in the streamlining of corporate operations. Workflow-based solutions could frequently replace paper-based operations. Improvements in company processes could result in increased staff productivity and lowered cost.

Therefore, the aim of this research was to develop a web-based Water Supply Complaint Management System to assist users who were experiencing watered supply issues. The system also informs the user that the complaint had been forwarded to responsible authorities, with added function such as receiving updates using Short Message Service (SMS) service. Local authorities can manage all complaints, thus enable them to respond more quickly. Moreover, users would also get news or information about when there would be water disruptions from the system, so they could prepare in advance.

# LITERATURE REVIEW

**Related works**

This section discussed and described past studies conducted by other researchers on the topic of Water Supply Complaint Management Systems.

**Electronic Complaint Management System for Municipal Corporation**

Sudhir, Regina & Sajidabhanu (2015) created the web system above which its major goal was to assist members of the public who were experiencing various challenges in their communities. This project had the ability to bridge the gap between citizens and government. It had the ability to control unethical bribing work while also reducing processing time. This project entails big problem-solving modules that serve as the best remedy for incoming large-scale concerns. The time solution varies depending on the type of complaint and category. To avoid receiving anonymous complaint details, it was required that the user provided their contact information while filing a complaint. The researcher continues to describe the situation by saying these organisations specify the kind of complaint-related services they gave to clients. As a result, we could argue that the definition of kind of complaint varies depending on the services supplied by various businesses. Meanwhile, the separation of functionality into layers was described by three tiers, with each piece being a tier that could be housed on a physically different computer. It was suitable for both web and distributed applications.

**Electronic-Customer Complaint Management System (E-CCMS)**

On the other hand, Afify & Kadry (2019) proposed a model structure to deal with e-complaints and capable of removing the downsides of poor service quality and delivery from the complaint procedure. The researchers discovered WSDM (Web Site Design Method) as an appropriate model for creating e-complaint web services in terms of an e-complaint model based on Service-Oriented Architecture (SOA) after conducting a series of evaluations on available researched approaches. The research reduces the concept for some of the services, the Rational Unified Process (RUP) was used as a reference for how to use the Unified Modelling Language (UML) successfully in research. The researchers divided the proposed model into three tiers to make it capable of handling complaints which were Storage-tier, Business-tier, and Presentation-tier. Its goal was to ensure that a business or organization's specific goals and requirements were met by a well-functioning system. The benefit of this proposed strategy was the ease with which citizens' complaints about what annoys them may be managed. To achieve this, a unique Complaint Management System was required to improve processes and ensure that all departments participate in the management of citizen complaints.

# METHODOLOGY

Figure 1 below shows the overview of methodology used in this research. There are a total of six phases including planning, analysis, design, implementation, testing, and documentation phase.

**Figure 1:** Methodology

The initiation part of the project begins with the planning phase. The area and title of the project has been discovered, including its objectives and context. The necessary prerequisites for building the system are derived from a literature review of different journal articles, conferences, and academic resources. Next is the design phase which involved designing the flow of the system as well as the user interface concept based on knowledge gathered in the previous phase. The development phase involves building the actual code based on various diagrams and interface mockups. Next, the testing phase is a mandatory phase to ensure the proposed system runs smoothly without errors and reach its intended purposes. The motive of the user acceptance testing is to get the feedback from real users so improvements can be made. Before articulating discussions, testing results are finally recorded and assessed during the final phase so that they can be thoroughly documented in the form of a report.

**System Architecture**

Figure 2 shows the system architecture for the proposed system.

![Graphical user interface, diagram Description automatically generated](6309095aec925_media/media/image1.png)

**Figure 2:** System Architecture for Water Supply Complaint Management System

The design of the proposed system involves setting up the actual online database in which details of the complaints can be recorded properly. Users must first register to enable them to file a complaint. Then after a complaint is successfully submitted, users can simply log into the system to check for the complaint status or progress. In addition, users can also receive a text message related to progress update. The admin can log in from the administration side to see the dashboard, which includes options to view all submitted complaints and modify the status.

The system is created using the Bootstrap CSS framework for the front end, while PHP is used to create the project's back end. To assist with SMS notification, a messaging system API is also incorporated into the code.

**DEVELOPMENT**

This section briefly explained some key important aspects of development of the Water Supply Complaint Management System. This system's two primary parts are the user side, where complaints are registered, and the administrative side, where complaints are handled in accordance with requirements and priorities. Using an online database is important to ensure the data is secured and accessible for authorized users only. The design and development aspects of the system's designated function are thoroughly detailed in the next section.

**Update SMS (Short Message Service) Page**

The snippet of source code for the Update SMS (Short Message Service) page is shown in Figure 3. SMS updates are used to keep registered users up to date on the status of their complaints. The MessageBird API was utilised to create this page. MessageBird is a firm that provides communications platform-as-a-service (CPaaS). Through a REST API, MessageBird's SMS API allows researchers to send and receive SMS messages to and from any country in the world. Users can always verify the status of a message using the supplied URL because each message is identifiable by a unique random ID.

![A screenshot of a computer Description automatically generated](6309095aec925_media/media/image2.png)

**Figure 3:** Coding for Update SMS (Short Message Service) Page

The administrator of the system can use the Update SMS page to inform users about the latest status of their submitted complaint, as well as to send warning messages regarding water disruptions or scheduled maintenance. Therefore, this function can help to notify users even if they are located at remote places with poor Internet connection. As a result, users will be able to make plans, including conserving water. Figure 4 illustrates the actual look of the Update SMS interface, while a preview of sent SMS content in a smartphone is shown in Figure 5.

![Graphical user interface, application Description automatically generated](6309095aec925_media/media/image3.png)

**Figure 4:** Update SMS Page Interface

![Graphical user interface, application Description automatically generated](6309095aec925_media/media/image4.png)

**Figure 5:** A preview of sent SMS on a smartphone

**Complaint Status Page**

After a user successfully registered into the system, he or she will be able to file a new complaint and then access the Complaint Status Page. Users can file more than one complaint and the system will display the list of complaints along with details such as complaint number, date and time submitted and current status. In addition, users can also click the "View Details" button to see the detailed view of a specific complaint. Figure 6 shows the interface mock-up design for the Complaint Status page its actual interface is shown in Figure 7.

![Graphical user interface Description automatically generated](6309095aec925_media/media/image5.png)

**Figure 6:** Mock-up Design of Complaint Status Page

![](6309095aec925_media/media/image6.png)

**Figure 7:** Actual Interface of Complaint Status Page

**FINDINGS AND DISCUSSIONS**

This section discussed the findings of this study. Before performing user acceptance testing, functionality testing is performed first to ensure all key components or modules of the proposed system to work properly.

**Analysis of User Interface Satisfaction**

The respondents were asked to score the system on a scale of one to five, with strongly disagree, disagree, neutral, agree, and strongly agree to be the most common responses. The scale of the usability testing questionnaire is depicted in Table 1. The mean was calculated using the respondents' input and a rating system ranged from one to five.

**Table 1:** User Acceptance Test Questionnaire Scale

| Strongly Disagree | Disagree | Neutral | Agree | Strongly Agree |
| ----------------- | -------- | ------- | ----- | -------------- |
| 1                 | 2        | 3       | 4     | 5              |

**Table 2:** Mean for User Interface Satisfaction Category

| Question                                                                               | 1        | 2 | 3 | 4  | 5  | Mean |
| -------------------------------------------------------------------------------------- | -------- | - | - | -- | -- | ---- |
| 1\. Interface for this system is simple to recognize.                                  |          | 1 | 2 | 12 | 15 | 4.36 |
| 2\. The text is easily accessible and understandable.                                  |          |   |   | 13 | 17 | 4.56 |
| 3\. The characters on this system's interface are clear to read.                       |          |   |   | 13 | 17 | 4.56 |
| 4\. The terminology used is the same throughout the system.                            |          |   | 4 | 16 | 10 | 4.2  |
| 5\. The system provided error messages that clearly explained how to resolve problems. |          |   |   | 16 | 14 | 4.46 |
| TOTAL MEAN                                                                             | **4.42** |   |   |    |    |      |

According to the results, Question 2 and Question 3 had the highest mean scores in the User Interface Satisfaction category, which is 4.56. Nevertheless, Question 4 has the lowest mean results with a mean score of 4.2. As a result, based on the total mean of 4.42 in Table 2, it can be concluded that the participants were satisfied with the system's user interface because the characters and alert messages used throughout the system were understandable and helpful, and the system's interface was manageable and simple.

**Analysis of Usefulness and Ease of Use**

Table 3 displays the results of the respondents' responses to the question concerning usefulness and ease of use. The mean was derived using the respondents' responses and the ratings on a scale of one to five.

**Table 3:** Mean for Usefulness and Ease of Use category

| Question                                                                              | 1        | 2 | 3 | 4  | 5  | Mean |
| ------------------------------------------------------------------------------------- | -------- | - | - | -- | -- | ---- |
| 6\. Using this system, it reduces my time to make a complaint about the water supply. |          |   |   | 15 | 15 | 4.5  |
| 7\. I can quickly learn how to use this system.                                       |          |   |   | 17 | 13 | 4.43 |
| 8\. I think this system is very helpful.                                              |          |   |   | 17 | 13 | 4.43 |
| TOTAL MEAN                                                                            | **4.45** |   |   |    |    |      |

According to the results, all the questions had a mean value which is greater than 4.0. However, Question 6 has the highest mean result, which is 4.5, while the other two questions have the lowest mean result of 4.43. The total mean for the second category of Usefulness and Ease of Use is 4.45. As a result, the Water Supply Complaint Management System was found to be simple to use and convenient.

**Analysis of Usability of the System**

The question concerning the usability category is shown in Table 4, depending on the participant's response. The average was derived using the respondents' input and a rating system of one to five.

**Table 4:** Mean Result for the Usability of the System

| Question                                                                   | 1        | 2 | 3 | 4  | 5  | Mean |
| -------------------------------------------------------------------------- | -------- | - | - | -- | -- | ---- |
| 9\. In this system, I can easily navigate from one page to the other page. |          |   |   | 16 | 14 | 4.46 |
| 10\. This system contains all the features I expected.                     |          |   | 1 | 18 | 11 | 4.33 |
| 11\. It is simple to locate information in the system.                     |          |   |   | 18 | 12 | 4.4  |
| 12\. I found the system's several functions were well integrated.          |          |   |   | 22 | 8  | 4.26 |
| TOTAL MEAN                                                                 | **4.36** |   |   |    |    |      |

The highest mean result for Usability of the System category is Question 9 with a mean result of 4.56 while Question 12 has the lowest mean result of 4.2. The overall mean was calculated using the data obtained, and it was found to be 4.36. Therefore, it shows that the respondents agreed that the Water Supply Complaint Management System was simple to use and that it aided respondents in completing tasks when they were assessed.

**Analysis of Functionality of the System**

**Table 5:** Mean Results for Functionality

| Question                                                                                                                  | 1        | 2 | 3 | 4  | 5  | Mean |
| ------------------------------------------------------------------------------------------------------------------------- | -------- | - | - | -- | -- | ---- |
| 13\. Update the latest progress status of customer complaints in the system, as well as using SMS to do so, is necessary. |          |   | 1 | 17 | 12 | 4.36 |
| 14\. I found that the SMS notification system is beneficial to the users.                                                 |          |   |   | 18 | 12 | 4.4  |
| 15\. Overall, I am satisfied with the system's functionality and use.                                                     |          |   |   | 19 | 11 | 4.36 |
| TOTAL MEAN                                                                                                                | **4.37** |   |   |    |    |      |

Table 5 shows the findings of the functional analysis. According to the data compiled, all questions had achieved mean value greater than 4.0. However, Question 14 has the highest mean result, which is 4.4, while the other two questions have the lowest mean result with mean results of 4.36. The total mean for the last category is 4.37. As a result, it can be verified that updating the system's newest progress status of customer complaints, as well as using SMS to do so, is useful and beneficial to the respondents.

## 

## Result Summary

Table 6 displays the four major categories used in survey instrument for the user acceptance testing, as well as the respective value of average mean for each category.

**Table 6:** Summary Result from Questionnaire

| Category                    | Mean |
| --------------------------- | ---- |
| User Interface Satisfaction | 4.42 |
| Usefulness and Ease of Use  | 4.45 |
| Usability                   | 4.36 |
| Functionality               | 4.37 |

According to the findings, the Water Supply Complaint Management System was evaluated in four categories which are user interface satisfaction, usefulness, and ease of use of the system, usability, and functionality. Most respondents agreed that the proposed system's user interface, functions, and ability to update the status of user complaints in real-time as well as support for SMS notifications were all satisfactory. This is because the total mean results for all four categories were greater than 4.

**CONCLUSION AND RECOMMENDATIONS**

As a conclusion, the Water Supply Complaint Management System was able to assist users to make proper complaints related to water supply problems in the community more easily. Furthermore, using the proposed system, users can view all submitted complaints and their status by logging into the system or via SMS notification. SMS notification is considered essential for areas with limited Internet coverage. Our daily lives depend on having access to clean water, so it is critical that local authorities act immediately whenever a water problem arises. For recommendation or future work, a better user interface is needed to improve the user experience while using this system as suggested by few respondents. For example, a few users would also love to have multiple languages support for the system.

**ACKNOWLEDGMENTS**

**This is a placeholder for authors to include acknowledgements, please DO NOT include acknowledgement in this manuscript as it is meant for Double Blind Review. Only include acknowledgement in the finalized manuscript.**

**  
**You can acknowledge help from colleagues, other institutions or disclose any funding from governmental organization or third-party organization here.

**CONFLICT OF INTEREST DISCLOSURE**

**\*\*\* Please do not include statement of conflict of interest in the initial submission for DOUBLE BLIND review. Only includes them in the finalized manuscript**

Ethically, the authors need to disclose any competing interests related to the subject matter of the article. These competing interests can be financial or non-financial in nature which may be perceived to influence the results or motivation of the research.

Example of competing interests includes, but not limited to:

Employment, involvement in organization that may directly benefit from the research or its findings. Collaboration with advocacy groups relating to the article content. Grants from industrial or commercial entity paid to the authors or their organization, stocks or share ownership, any payment or royalties received by the authors or their institutions for the writing of the article.

If the authors do not have any conflict of interests. Then the conflict-of-interest statement should be written as “The authors declared that they have no conflicts of interest to disclose.”

If any author has conflict of interests, then a statement identifying the nature of conflict of interest like this should be written:

“Author 2 is a shareholder in the company ABC, which co-develop the apparatus/framework Y which is the subject of this research”, or

“Author 3 is a part time consultant for organization ABC, which may benefit from the result of this study.”

**REFERENCES**

Aezion. (2020). The Benefits of Web-Based Systems for Business.

https://www.aezion.com/blogs/the-benefits-of-web-based-systems-for-business/

Janom, Afify, E. A., & Kadry, M. A. (2019). Electronic-Customer Complaint Management System (E-CCMS) – a Generic Approach. International Journal of Advanced Networking and Applications, 11(01), 4125–4141. <https://doi.org/10.35444/ijana.2019.11011>

Khalifa M & Bidaisee S (2018) The Importance of Clean Water. Sch J Appl Sci Res. Vol: 1, Issue: 7 (17-20). <https://www.innovationinfo.org/articles/SJASR/SJASR-7-176.pdf>

Nasr, O. A., & Alkhider, E. (2015). Online Complaint Management Systems Online Complaint Management System. International Journal of Innovative Science, Engineering & Technology, 2(6). www.ijiset.com

Sudhir, B., Regina, B., & Sajidabhanu, (2015). Electronic Complaint Management System for Municipal corporation. Communications on Applied Electronics, 2(8), 8–11. https://caeaccess.org/research/volume2/number8/sudhir-2015-cae-651817.pdf

Suresh, A., Nashim, KN., Thomas, B. & Manuel, N. (2019). IoT based public water complaint management system. International Journal of Networks and Systems, 8(3), 50–54. https://doi.org/10.30534/ijns/2019/13832019
