Design and Implementation of Electrical Fault Reporting System for MAU Yola

By

DEBORAH KALEJAIYE

(IMT/18U/2160)

Project Report Submitted to Department of Information Technology, Modibbo Adama

UniversityYola, in Partial Fulfilment of the Requirements for the Award of Bachelor of
Technology (B.Tech.) Degree Information ManagementTechnology

October, 2024.

1
 APPROVAL
This is to certify that this project work “Design and implementation of electrical fault reporting system
for MAU Yola” was carried out by Deborah Kalejaiye, (IMT/18U/2160), read and approve to have met
the requirement for the award of Bachelor of Technology degree in Information Management
Technology at Modibbo Adama University, Yola by the undersigned:

______________________ ________________________

Dr Haruna Dahiru Usman Date

(Project Supervisor)

______________________ ________________________

Dr. M. B. Ribadu Date

(Head of Department)

2
 DEDICATION

This work is dedicated to God the Father, the Alpha and Omega of my faith, my teacher, provider and
comforter.
To God be the glory, honour and adoration for ever and ever Amen.

3
ACKNOWLEDGEMENT

4
 ABSTRACT
The Electrical Fault Reporting System is designed to streamline the process of reporting and managing electrical
faults, aiming to enhance efficiency and user satisfaction within utility services. This system addresses common
challenges faced by users and administrators, such as delays in reporting, ineffective communication, and lack of
real-time tracking. The development of the system involved a comprehensive analysis of user requirements,
followed by a structured design phase that established a robust architecture using a multi-tier approach. Key
features include user-friendly interfaces for reporting faults, an admin backend for managing complaints, and
secure user authentication processes. The system was successfully implemented using HTML in designing the
user interface, while PHP programming language for designing the interface of the application and MySQL
server for designing database. The system is developed to provide a secured efficient and effective Electrical
Fault Reporting System for MAU.

5
 TABLE OF CONTENTS
APPROVAL..............................................................................................................................................................2
DEDICATION...........................................................................................................................................................3
ACKNOWLEDGEMENT........................................................................................................................................4
ABSTRACT................................................................................................................................................................5
CHAPTER ONE.......................................................................................................................................................8
INTRODUCTION.....................................................................................................................................................8
1.1 Background of the study................................................................................................................................8
1.2 Statement of the Problem.............................................................................................................................10
1.3 Aim of the Study............................................................................................................................................10
1.4 Significance of the Study..............................................................................................................................10
1.5 Scope of the Study.........................................................................................................................................11
1.6 Definition of Operational Terms.................................................................................................................11
CHAPTER TWO....................................................................................................................................................12
LITERATURE REVIEW......................................................................................................................................12
2.1 Introduction...................................................................................................................................................12
2.2 Causes of Power System Faults...................................................................................................................12
2.2.1 Detecting and locating faults.................................................................................................................12
2.2.2 Common power system faults...............................................................................................................13
2.2.3 Types of faults........................................................................................................................................13
2.2.4 Open circuit faults..................................................................................................................................13
2.2.5 Causes......................................................................................................................................................14
2.2.6 Effects......................................................................................................................................................14
2.3 An overview on the pre-existing fault reporting techniques.....................................................................14
2.3.1 Time domain reflectometry...................................................................................................................14
2.3.2 Surge generator cable thumping..........................................................................................................15
2.4 Specific advantages of the proposed technique over the pre-existing techniques...............................16
2.5 Fault Management System...........................................................................................................................17
2.6 Technological Innovations......................................................................................................................18
2.7 Database Management System....................................................................................................................18
2.7 Management Information System (MIS)....................................................................................................19
2.8 Review of Related Works.........................................................................................................................22
CHAPTER THREE................................................................................................................................................24
METHODOLOGY.................................................................................................................................................24
3.1 Introduction...................................................................................................................................................24
3.2 Software Development Life Cycle (SDLC) Model.....................................................................................24
3.3 System Analysis.............................................................................................................................................25

6
 3.3.1 Fact Finding Techniques.......................................................................................................................26
3.3.2 Interview.................................................................................................................................................26
3.4 Overview of the System................................................................................................................................26
3.4.1 Functional Requirement Specification.................................................................................................26
3.4.2 Non-Functional Requirement Specification........................................................................................27
3.5 System Design................................................................................................................................................27
3.6 Flowchart.......................................................................................................................................................27
3.7 Use Case Diagram.........................................................................................................................................29
3.8 Database Design............................................................................................................................................30
3.8.1 Database schema (Tables).....................................................................................................................30
3.8.2 User Table...............................................................................................................................................30
3.8.3 Reports Table.........................................................................................................................................31
3.8.4 Feedback Table......................................................................................................................................31
CHAPTER FOUR...................................................................................................................................................32
RESULTS AND DISCUSSION.............................................................................................................................32
4.1 Introduction...................................................................................................................................................32
4.2 System Requirements...................................................................................................................................32
4.2.1 Hardware Requirements.......................................................................................................................32
4.2.2 Software Requirements.........................................................................................................................32
4.3 Results............................................................................................................................................................33
4.3.1 Home Dashboard...................................................................................................................................33
4.3.2 Emergency Report Page........................................................................................................................34
4.3.3 Registration Page...................................................................................................................................34
4.3.4 Login Page..............................................................................................................................................35
4.3.5 Report Page............................................................................................................................................36
4.3.6 View Complaint Page............................................................................................................................38
4.3.7 Feedback Page........................................................................................................................................38
4.3.8 Frequently Ask Question Page.............................................................................................................39
4.3.9 Admin Registration Page......................................................................................................................40
4.3.10 Admin Back End Page.........................................................................................................................41
4.3.11 Logout Page..........................................................................................................................................41
4.4 Discussion.......................................................................................................................................................42
CHAPTER FIVE....................................................................................................................................................44
SUMMARY, CONCLUSION AND RECOMMENDATIONS...........................................................................44
5.1 Summary........................................................................................................................................................44
5.2 Conclusion.....................................................................................................................................................45
5.3 Recommendations.........................................................................................................................................45
References................................................................................................................................................................45

7
 CHAPTER ONE

INTRODUCTION
1.1 Background of the study
In an electric power system, a fault or fault current is any abnormal electric current. For example a
short circuit is a fault in which a live wire touches a neutral or ground wire. An open-circuit fault
occurs if a circuit is interrupted by a failure of a current-carrying wire (phase or neutral) or a blown
fuse or circuit breaker (Jorge, 2016). In three-phase systems, a fault may involve one or more phases
and ground, or may occur only between phases. In a "ground fault" or "earth fault", current flows into
the earth. The prospective short-circuit current of a predictable fault can be calculated for most
situations. In power systems, protective devices can detect fault conditions and operate circuit breakers
and other devices to limit the loss of service due to a failure. In a polyphase system, a fault may affect
all phases equally, which is a "symmetric fault". If only some phases are affected, the resulting
"asymmetric fault" becomes more complicated to analyze. The analysis of these types of faults is often
simplified by using methods such as symmetrical components. The design of systems to detect and
interrupt power system faults is the main objective of power system (Pravesh, 2018). Electrical
networks, machines and equipment are often subjected to various types of faults while they are in
operation. When a fault occurs, the characteristic values (such as impedance) of the machines may
change from existing values to different values till the fault is cleared. There may be lot of
probabilities of faults to appear in the power system network, including lighting, wind, tree falling on
lines, apparatus failure, etc. A fault in an electric power system can be defined as, any abnormal
condition of the system that involves the electrical failure of the equipment, such as, transformers,
generators, bus bars, etc.
The fault inception also involves in insulation failures and conducting path failures which results short
circuit and open circuit of conductors. Under normal or safe operating conditions, the electric
equipment’s in a power system network operate at normal voltage and current ratings. Once the fault
takes place in a circuit or device, voltage and current values deviates from their nominal ranges
(Nicopoulos and Hassan, 2018).
The faults in power system causes over current, under voltage, unbalance of the phases, reversed
power and high voltage surges. This results in the interruption of the normal operation of the network,
failure of equipment’s, electrical fires, etc. Usually, power system networks are protected with
switchgear protection equipment’s such as circuit breakers and relays in order to limit the loss of

8
service due to the electrical failures. One of the major challenges associated with Modibbo
Adama University, Yola (MAU) electric cables is the difficulty in locating the actual point of
fault and consequently prolonged ‘out of service’ time. Currently there is no perfect fault
reporting system for Modibbo Adama University, Yola (MAU) electric cable and this introduces
an issue to fault reporting in the marine and the expected Modibbo Adama University, Yola
(MAU).

1.2 Statement of the Problem

The process of fault detection, reporting and fixing appears much more difficult and time
consuming in Modibbo Adama University, Yola (MAU) systems as compared to overhead
systems solely because the utility currently lacks a proper fault reporting technique. This project
has aimed at designing and building an accurate and affordable system of Modibbo Adama
University, Yola (MAU) electric fault reporting system.

1.3 Aim of the Study

The general aim of this study is to examine the Design and Implementation of Electrical Fault
Reporting System in MAU Yola. The study’s specific aims are:

i) To conduct system analysis of electrical fault reporting system for MAU Yola.
ii) To design a model that can depict electrical fault for MAU Yola.
iii) To implement proposed system.

1.4 Significance of the Study

The current system of reporting fault is done by capturing details in a note book at the
station/unit, the information captured would later be used in the preparation of the charge sheet,
the same may also be used as the evidence presented to during operation. This takes too much
time processing the incident statement of fault connection or disconnection. Unlike the
application system, manual data collection method would be trimmed down, in that all the
information of an electricity fault would be captured directly to the server at the static system.
Currently an engineer would prefer not to report a fault because of the nature of the system. In
most cases, reporting the incident may be time consuming.

9
1.5 Scope of the Study
Though faults occurring in electric systems include both short and open circuit faults, this project
concentrated on reporting of the entire university schools and offices electric faults. The major
reasons to omission of other types of faults were the ones stated under the section of constraints.

1.6 Definition of Operational Terms

Electrical Fault: A malfunction, damage, or failure of any electrical component, circuit, system, or
equipment that results in disruption or interruption of electricity supply or poses a safety hazard.
Fault Report: A detailed record of an identified electrical fault, including description, location,
severity, and any relevant information such as time and date, equipment involved, and impact on
operations.
Reporting System: A structured and organized mechanism used to report, track, and manage
electrical faults from identification to resolution.
User: An authorized individual or group responsible for reporting, monitoring, and/or resolving
electrical faults through the fault reporting system.
Administrator: A designated individual or team responsible for managing and maintaining the fault
reporting system, including user access, system configuration, and data management.

10
 CHAPTER TWO

LITERATURE REVIEW
2.1 Introduction
A fault is any abnormal condition in a power system. The steady state operating mode of a power
system is balanced three-phase A.C. However, due to sudden external or internal changes in the
system, this condition is disrupted.

2.2 Causes of Power System Faults

A fault occurs due to failure insulation of a conductor at one or more points or a conducting
object comes in contact with the live part of the system. There are a number of causes for the
occurrence of a fault in the power system (Ravi, 2019). Some of the possible causes of faults are;

1. Overvoltage due to switching surges.

2. Lightening
3. Aging of conductor
4. Heavy wind, rain, and snowfall
5. Falling trees on the transmission line
6. Accident of vehicle with towers or poles of transmission line
7. Chemical pollution
8. Accidental short circuit due to string, snake.

2.2.1 Detecting and locating faults

Overhead power lines are easiest to diagnose since the problem is usually obvious, e.g., a tree
has fallen across the line, or a utility pole is broken and the conductors are lying on the ground.
Locating faults in a cable system can be done either with the circuit de-energized, or in some
cases, with the circuit under power. Fault location techniques can be broadly divided into
terminal methods, which use voltages and currents measured at the ends of the cable, and tracer
methods, which require inspection along the length of the cable. Terminal methods can be used
to locate the general area of the fault, to expedite tracing on a long or buried cable (Saha et al.,
2019)
In very simple wiring systems, the fault location is often found through inspection of the wires.
In complex wiring systems (for example, aircraft wiring) where the wires may be hidden, wiring
faults are located with a Time-domain reflectometer (Smith, et al, 2018) The time

11
domain reflectometer sends a pulse down the wire and then analyzes the returning reflected pulse to
identify faults within the electrical wire. In historic submarine telegraph cables, sensitive
galvanometers were used to measure fault currents; by testing at both ends of a faulted cable, the fault
location could be isolated to within a few miles, which allowed the cable to be grappled up and
repaired.
Sometimes an insulation fault in a power cable will not show up at lower voltages. A "thumper" test
set applies a high-energy, high-voltage pulse to the cable. Fault location is done by listening for the
sound of the discharge at the fault. While this test contributes to damage at the cable site, it is practical
because the faulted location would have to be reinsulated when found in any case (Tyler, 2019).

2.2.2 Common power system faults

Power system faults may be categorized as one of four types; in order of frequency of occurrence
(Zhang et at., 2018) they are:
1. Single line to ground fault
2. Line to line fault
3. Double line to ground fault
4. Balanced three phase faults

The first three types constitute severe unbalanced operating conditions which involves only one or two
phases hence referred to as unsymmetrical faults. In the fourth type, a fault involving all the three
phases occurs therefore referred to as symmetrical (balanced) fault.

2.2.3 Types of faults

Electrical faults in three-phase power system are mainly classified into two types namely; open and
short circuit faults. Further, these faults can be symmetrical or unsymmetrical faults.

2.2.4 Open circuit faults

These faults occur due to the failure of one or more conductors. The figure below illustrates the open
circuit faults for single, two and three phases (or conductors) open condition. Open circuit faults are
also called as series faults. These are unsymmetrical or unbalanced type of faults except three phase
open fault (Yalcin et al., 2019)

12
Consider that a transmission line is working with a balanced load before the occurrence of open circuit
fault. If one of the phases gets melted, the actual loading of the alternator is reduced and this cause to
raise the acceleration of the alternator, thereby it runs at a speed slightly greater than synchronous
speed. This over speed causes over voltages in other transmission lines.
Thus, single- and two-phase open conditions can produce the unbalance of the power system voltages
and currents that causes great damage to the equipment’s.
2.2.5 Causes
Broken conductor and malfunctioning of circuit breaker in one or more phases

2.2.6 Effects
1. Unusual operation of the system
2. Danger to the personnel as well as animals
3. Exceeding the voltages beyond normal values in certain parts of the network, which further
leads to insulation failures and developing of short circuit faults.
Although open circuit faults can be tolerated for longer periods than short circuit faults, these must be
removed as early as possible to reduce the greater damage.

2.3 An overview on the pre-existing fault reporting techniques

This section tries to sort out various existing fault reporting systems and some of their drawbacks in
relation to the proposed system. Two modern techniques of fault reporting have been selected for
evaluation to show their drawbacks. These are Time Domain Reflectometry (TDR) and Surge
Generator Cable Thumping.

2.3.1 Time domain reflectometry

Time Domain Reflectometry (TDR) uses a pulse echo range-finding technique, similar to that used by
sonar systems, to measure the distance to changes in the cable structure (wikipedia). It works by
transmitting short-duration low-voltage (up to 50 V) pulses at a high repetition rate into the cable and
measuring the time taken for them to reflect back from areas where the cable has low impedance, such
as at a fault. The reflections are traced on a graphical display with amplitude on the y-axis and elapsed
time, which is directly related to the distance to the position of the fault, on the x-axis. The TDR sends
a low-energy signal through the cable, causing no insulation degradation. A theoretically perfect cable
returns the signal in a known time and in a known profile. Impedance variations in a "real-world"
cable alter both the time and profile, which the TDR screen or printout graphically represents. This
graph (called a "trace") gives the user approximate distances to "landmarks" such as opens, splices, Y-
13
taps, transformers, and water ingression.
One weakness of TDR is that it does not pinpoint faults. TDR is accurate to within about 5% of testing
range. Sometimes, this information alone is sufficient. Other times, it only serves to allow more
precise thumping. For instance, a 500 m fault can be located at a distance range of 475 m to 525 m.
That means for the 50 m distance, another method such as thumping may be required to pin point the
fault reporting.
Another weakness of TDR is that reflectometers cannot only detect faults with resistances much
greater than 200 ohms. So, in the case of a "bleeding fault" rather than a short or near short, TDR is
blind.

2.3.2 Surge generator cable thumping

The high-voltage surge generator, or ‘thumper’, is a portable device that injects a high voltage DC
pulse (typically up to 30 kV) at the surface termination of the cable to be tested.

14
Historically, fault reporting was carried out by various measuring techniques and by setting the
surge generator to thump repeatedly, and then walking the cable route until the thump could be
heard. The higher the DC voltage applied, the louder the resulting thump and the easier it
becomes to find the fault.
However, for longer cables, it could take days to locate a fault using this method – during which
time the cable is exposed to potentially damaging high-voltage thumping. So, while the existing
fault might be located, other areas of the cable could have been weakened in the process. Cables
that have been thumped tend to fail sooner than would otherwise have been expected.
Generally, the existing fault reporting techniques face the following challenges:

i) All are off-line methods in that they are used to detect fault reporting after it has
occurred and the cables have been de-energized while the proposed system is an online
technique.

ii) The overall cost of the locator unit can be much higher than the proposed system.

iii) Result interpretation can be very tricky.

iv) The process of fault reporting can be very tedious in more complex electric systems
compared to single line cables.

Fault is any abnormal condition in a power system. A fault occurs due to failure insulation of a
conductor at one or more points or a conducting object comes in contact with the live part of the
system. Overvoltage due to switching surges is one of the cause of electrical fault.
Some related work have been reviewed, which include; proposed of an intelligent, low-cost
system, which monitors the behavior of electrical magnitude of domestic appliances of real
time. Also proposed a self-diagnosis technique for fault node identification in large-scale
internet of a thing. The technique is based on lightweight processor-level architectural support to
minimize the performance overhead.
It tries to sort out various existing system. Time domain reflectometry have been selected as the
modern technique of fault reporting. Time domain reflectometry can be used to characterize and
locate electrical fault.

2.4 Specific advantages of the proposed technique over the pre-existing techniques
These are specific advantages of the proposed system compared to the existing methods once in
use:
i) Fault reporting will be an on-line process since it will be possible to locate the fault

15
office based on the report given.
ii) Result interpretation is easy and straight forward unlike TDR whose screen displays are
uneasy to be interpreted by lay people.

2.5 Fault Management System

Operators in the telecommunications industry are saddled with increasing competition worldwide
and their ability to provide uninterrupted services keeps them at the edge of the market flow
(Rahul, 2016). To ensure the system are properly monitored most Telecommunication outfit have
a Network operations center where all faults are monitored adequately, logged for management
purpose and escalated to the field engineers for immediate actions. According to Rahul (2016)
there are various methods used by various telecommunications operations center to report and
manage faults also vary depending on the scale of operations and the best way to provide
management with informed decisions on the best way to improve a Network.

Network Operation Centre (NOC): A Network Operations center (NOC) can be referred to as a
place where various teams or administrators supervise, monitor and maintain a
telecommunications network in order to ensure availability and optimal performance per time.

Fault Management: it is important to distinguish between faults and failures. A fault is any kind of
defect that leads to an error. A failure is a state of a system when it deviates from specification
and is unable to deliver its intended functions. Fault tolerance can be classified into four levels
from a system point of view such as: hardware layer, software layer, network communication
layer, and applications layer. Fault management as a component of the of the network
management which is concerned with the detection, isolation and resolution of problems.

Fault Management Phases: To provide a resilient network in faulty situations proffers three main
actions (Fault detection, fault diagnosis and fault recovery)

Fault Detection: This is the first stage of a Fault management system, Fault detection in sensor
networks depends on the type of failures that occur on a network.

Fault Diagnosis: Fault Diagnosis is the process of properly identifying the cause of problem or
cause of the alarm. It is the process of properly troubleshooting the failure or fault in the system to
know the root cause failure.

16
Fault Recovery: This is the way faults are treated, this is the stage the network is restructured or
reconfigured such that failures do not affect or impact the network performance any further.

Network Map: The network map is a view on the network server application that displays the
network being managed as well as the status of the network elements (NE) within. The NEs are
displayed as icons and the colors of the icons represent their status. Updates are sent to the
network map from the network status monitor module. This permits the operators to navigate
through the managed network and isolate the network elements generating the problem
conditions.

2.6 Technological Innovations

Technological advancements have significantly enhanced the capabilities of Electrical Fault
Reporting Systems, making them more efficient, accurate, and user-friendly (Dowds &
Farrington, 2020). Leveraging data analytics tools and reporting functionalities can enable remand
home administrators to monitor key performance indicators, track program outcomes, and make
informed decisions to optimize operations (Mears et al., 2018).

2.7 Database Management System

The introduction of computer into information technology has massively improved the
information need of organization; the success of this machine is dependent on the knowledge
base.
Coles, (2021) Defined database is an organized collection of data. The data is typically organized
to model relevant aspects of reality, in a way that supports processes requiring this information.
Database management systems (DBMS) are specially designed applications that interact with the
user, other applications, and the database itself to capture and analyze data. A general-purpose
database management system (DBMS) is a software system designed to allow the definition,
creation, querying, update, and administration of databases. A database is not generally portable
across different DBMS, but different DBMS can inter-operate by using standards such as SQL
and ODBC or JDBC to allow a single.
Kiln, (2020) defined computerization is a social process for providing access to and support for
computer equipment to be used in activities such as teaching, accounting, writing, designing,
circuits, file processing etc. computerization entails social choices about the levels of appropriate
investment and control over equipment and expertise, as well as choices of equipment. In the
early 1990s, computing and telecommunications accounted for half of the capital investments
made by private firms.
17
However, McCorduck, (2017) stated that the most fervent advocates of computerization have
argued that the actual pace of computerization in schools, factories and homes is too slow.
Kling, (2019) others emphasize labor-market pragmatism that we label “vocational matching”. In
this view, people will need computer skills, such as programming, to compete in future labor
markets and to participate in a highly automated society; a responsible school will teach some of
these skills today. Advocate of computer- based education promotes a heaven image of computer-
using schools as places where students learn in a cheerful, cooperative setting and where all
teachers can be supportive, enthusiastic mentors.
Therefore, a computerized database management system is usually a system, which is
implemented with a computer to achieve the utmost efficiency and desired goals. Russell, (2016)
dealt extensively on the need for the use of computers on such database system like database
management system. In the words of David, (2020), at the center of any information system is a
database, which is any collection of related information grouped together as a simple item. The
term can also apply to the ways in which information is catalogued, analyzed, stored and used
manually.
In the words of Yourdon, (2019) Database management systems (DBMS) have become a standard
tool for shielding the computer user from details of secondary storage management. They are
designed to improve the productivity of application programmers and to facilitate data access by
computer-naive end users. There have been several database models. Whichever conceptual
model or database management system is adopted, the use of a central database management
system has a number of advantages and some costs compared to the commonly employed special
purpose data files. A data file consists of a set of records arranged and defined for a single
application system. Relational information between items in a record or between records is not
explicitly described or available to other application systems. For example, a file of project
activity durations and scheduled times might be assembled and manipulated by a project
scheduling system. This data file would not necessarily be available to the accounting system or
to corporate planners.

2.7 Management Information System (MIS)

Gallangher, (2021) Define the concept of the MIS has evolved over a period of time comprising
many different facets of the organizational function. MIS is a necessity of all the organizations.
The initial concept of MIS was to process data from the organization and presents it in the form
of reports at regular intervals. The system was largely capable of handling the data from
collection to processing. It was more impersonal, requiring each individual to pick and choose the
18
processed data and use it for his requirements. This concept was further modified when a
distinction was made between data and information. The information is a product of an analysis
of data. This concept is similar to a raw material and the finished product. What are needed are
information and not a mass of data.
However, the data can be analyzed in a number of ways, producing different shades and
specifications of the information as a product. It was, therefore, demanded that the system
concept be an individual- oriented, as each individual may have a different orientation towards
the information. In addition, Gallangher, (2021) cited that this concept was further modified, that
the system should present information in such a form and format that it creates an impact on its
user, provoking a decision or an investigation.
It was later realized then even though such an impact was a welcome modification, some sort of
selective approach was necessary in the analysis and reporting. Hence, the concept of exception
reporting was imbibed in MIS. The norm for an exception was necessary to evolve in the
organization. The concept remained valid till and to the extent that the norm for an exception
remained true and effective. Since the environment turns competitive and is ever changing,
fixation of the norm for an exception becomes futile exercise at least for the people in the higher
echelons of the organization. The concept was then evolved that the system should be capable of
handling a need-based exception reporting. This need maybe either of an individual or a group of
people. This called for keeping all data together in such a form that it can be accessed by anybody
and can be processed to suit his needs.
The concept is that the data is one but it can be viewed by different individuals in different ways.
This gave rise to the concept of database, and the MIS based on the database proved much more
effective. Over a period of time, when these conceptual developments were taking place, the
concept of the end user computing using multiple databases emerged. Williams, (2014) cited that
this concept brought a fundamental charge in MIS. The change was decentralization of the system
and the user of the information becoming independent of computer professionals. When this
becomes a reality, the concept of MIS changed to a decision making system. The job in a
computer department is to manage the information resource and leave the task of information
processing to the user.
Secmba, (2014), define the concept of MIS in today’s world is a system which handles the
databases, databases, provides com-putting facilities to the end user and gives a variety of
decision-making tools to the user of the system.
Williams, (2021) define the concept of MIS gives high regard to the individual and his ability to
use information. An MIS gives information through data analysis. While analyzing the data, it

19
relies on many academic disciplines. These include the theories, principles and concepts from the
Management Science, Psychology and Human Behavior, making the MIS more effective and
useful. These academic disciplines are used in designing the MIS, evolving the decision support
tools for modeling and decision - making.
Laudon, (2021), define the foundation of MIS is the principles of management and if its practices.
MIS uses the concept of management Information System can be evolved for a specific objective
if it is evolved after systematic planning and design. It calls for an analysis of a business,
management views and policies, organization culture and the culture and the management style.
The information should be generated in this setting and must be useful in managing the business.
This is possible only when it in conceptualized as system with an appropriate design. The MIS,
therefore, relies heavily on the systems theory offers solutions to handle the complex situations of
the input and output flows. It uses theories of communication which helps to evolve a system
design capable of handling data inputs, process, and outputs with the least possible noise or
distortion in transmitting the information form a source to a destination. It uses the principles of
system Design, Viz., an ability of continuous adjustment or correction in the system in line with
the environmental change in which the MIS operates. Such a design helps to keep the MIS tuned
with the business management’s needs of the organization. The concept, therefore, is a blend of
principle, theories and practices of the Management, Information and System giving rise to single
product known as Management Information System (MIS).
The Physical view of the MIS can be seen as assembly of several subsystems based on the
databases in the organization. These subsystems range from data collection, transaction
processing and validating, processing, analyzing and storing the information in databases. The
subsystem could be at a functional level or a corporate level. The information is evolved through
them for a functional or a department management and it provides the information for the
management of business at the corporate level (Terrene, 2021).
The MIS is a product of a multi- disciplinary approach to the business management. It is a
product which needs to be kept under a constant review and modification to meet the corporate
needs of the information. It is prescribed product design for the organization. The MIS differs
since the people in two organizations involved in the same business. The MIS is for the people in
the organization (George, 2017).
According to Raymond, (2020), The MIS model may be the same but it differs greatly in the
contents. The MIS, therefore, is a dynamic concept subject to change, time and again, with a
change in the business management process.

20
It continuously interacts with the internal and the external environment of the business and
provides a corrective mechanism in the system so that the change needs of information are with
effectively. The MIS, therefore, is a dynamic design, the primary objectively. The MIS, therefore,
is a dynamic design the primary objective of which is to the information the information for
decision making and it is developed considering the organizational fabric, giving due regard to
the people in the organizational the management functions and the managerial and the managerial
control.

2.8 Review of Related Works

Tejan et al., (2018) intends to detail how to make the sensor system, low maintenance and self-
healing. All the civilized communities across the universe are spending a lot on the maintenance
since it affects the physical, mental and spiritual wellbeing. This maintenance can be divided into
two phases. First phase is observing and reporting. The better the observation and reporting, the
better and faster are the chances of a quality resolution of the issues. It is noted by psychologists
that human mind finds it difficult to take effort and record community issues. Also, studies have
proved that machine or devices behave much better in both these phases of maintenance, and if
these phases are combined into single coordinated and combined ecosystem, the sensor machines
can play a pivotal role in community maintenance.
Seabra et al., (2016) proposed an intelligent, low-cost system, which monitors the behavior of
electrical magnitudes of domestic appliances in real time. The system is able to analyze the
collected data, detect possible faults, and report this situation to the user. This system is
designed to adopt old generation electronics. Also, the necessary interventions are given in form
of TV displays, etc. Fault detection and diagnosis systems available in real-time and on-line add
ease of management to domestic appliances. Fault detection is done through information
registration, recognition, and indication of anomalies in the systems behavior.
Lee et al., (2018) proposed a self- diagnosis technique for faulty node identification in large-
scale internet of thing systems. The technique is based on lightweight processor-level
architectural support to minimize the performance overhead. It is demonstrated by experiments
that the proposed methodology can detect 92.66% of failures, regardless of when the external
monitoring program is connected. A faulty device identification technique which is based on
very lightweight processor-level architectural support.
Abinaya et al., (2017) implemented Smart Street Lights that operates according to the outer
weather conditions. The system is mainly designed to ensure safety and to prevent energy
wastage. This system cuts down the cost of conventional system by 50−60% which improves
21
the economy of the country and saves a huge amount of investment as it can be utilized in
useful ideas.
Tavade et al., (2017) proposed a data logger system which will act like a fault diagnostic
system for mechanical engine and log the data on the web server for remote access. The
development and design of data logger system depends on the application on which it will work.
Choi et al., (2018) presented an automatic method to detect and identify faulty internet of thing
devices with context extraction. The presented system works in 2 phases. In first phase, i.e., pre-
computation phase, the system calculates the sensor correlation and the transition probability
between sensor working states known as context. During second phase, i.e., real-time phase, the
system finds a violation of sensor correlation and transition to detect and identify the faults in
devices.
Chen Wang et al., (2018) proposed a solution by making use of internet of a thing enabling
technologies. This system first discovers the causal relationship of the physical devices by
analyzing the device sensor data without the knowing the physical manufacturing process of the
system. The health of devices is measured according to its previous working states.

22
 CHAPTER THREE

METHODOLOGY

3.1 Introduction
The success of any software development depends largely on how accurately the problem is
defined and understood, and thorough investigation that is properly carried in choice of solution
process. Software development project becomes better understood as it progresses through
analysis and design. However, a system development should not commence until enough
information is available to permit the preliminary planning and to ensure that the system is
feasible

3.2 Software Development Life Cycle (SDLC) Model.

The choice of SDLC model to be adopted in a software development process is a decision that
should be made with an eye towards the nature of the software and the time allotted for the
development. Waterfall model is chosen as the SDLC model to be used. Because, waterfall
model is the earliest SDLC approach that was used for software development. Waterfall Model
illustrates the software development process in a linear sequential flow. This means that any
phase in the development process begins only if the previous phase is complete. In this waterfall
model, the phases do not overlap. The phases in waterfall model are:
1. Requirement Gathering and analysis − All possible requirements of the system to be
developed are captured in this phase and documented in a requirement specification
document.
2. System Design −The requirement specifications from first phase are studied in this
phase and the system design is prepared. This system design helps in specifying
hardware and system requirements and helps in defining the overall system architecture.
3. Implementation −With inputs from the system design, the system is first developed in
small programs called units, which are integrated in the next phase. Each unit is
developed and tested for its functionality, which is referred to as Unit Testing.

23
4. Integration and Testing − All the units developed in the implementation phase are integrated
into a system after testing of each unit. Post integration the entire system is tested for any faults
and failures.
5. Deployment of system − Once the functional and non-functional testing is done; the product is
deployed in the customer environment or released into the market.
6. Maintenance − There are some issues which come up in the client environment. To fix those
issues, patches are released. Also, to enhance the product some better versions are released.
Maintenance is done to deliver these changes in the customer environment.

Figure 1. Water fall model

3.3 System Analysis

System analysis is process of studying a procedure or business to identify its goal and purposes and
create systems and procedure that will efficiently achieve them.

24
3.3.1 Fact Finding Techniques
Fact finding techniques refers to the gathering of information. It is often a part of an initial mission,
i.e., preliminary research, to gather facts for subsequent full investigation or hearing. In this project,
interview technique is adopted.

3.3.2 Interview
One-to-one interview was conducted with 20 students and 5 staffs on how they use to file an electrical
fault in their offices and hostels. The interview was open-ended as there was no pre-define set of
questions. Context free questions were asked to understand the problem fully and to develop a better
understanding of the situation.

3.4 Overview of the System

This project work focus on designing and developing a web-based system for electrical fault in MAU
YOLA. The system will give the admin site privilege to view complaints and rectify it.
On the other side, the users should have the authority to lay their electrical complaint online, by filling
some forms so as to describe their location etc.

3.4.1 Functional Requirement Specification

The functional requirements for this system are as follows:
Requirement ID Requirement Description

Requirement 1 The software should be able to implement a robust authentication system to

report all kind of electric faults

Requirement 2 The software should be able to provide view high level summary of electric fault
problems and their solutions.

Requirement 3 The identity of the reporter and the office should be revealed

25
3.4.2 Non-Functional Requirement Specification
The non-functional requirements of this system are listed below:
Requirement ID Requirement Description

Requirement 1 Registered users should get feedback

Requirement 2 The navigation should be intuitive

Requirement 3 The interface should be user friendly

3.5 System Design

System design involved defining the architecture, modules, interfaces, and data for a system to satisfy
specified requirements. The identified requirements were converted to the architectures and models of
the proposed system.

3.6 Flowchart
Flowchart is a diagram that depicts a process, system or computer algorithm. Is also graphical or
schematic representation of a process or an algorithm.

26
Flowchart of the system
27
3.7 Use Case Diagram
A use case diagram is a graphical depiction of a user’s possible interaction with a system. A use case
diagram shows various use cases and different types of users the system has and will often be
accompanied by other types of diagram as well. The use cases are represented by either circles or
ellipses.

LOGIN

REGISTRATION

CHANGE
PASSWORD

FILE A
REPORT
ADMIN
USER
VIEW
REPORT

UPDATE REPORT

GENERATE REPORT

DELETE REPORT

FEED BACK

LOGOUT

28
3.8 Database Design
In this project we choose to use My SQL as a database of the software.
MySQL Is an open-source relational database management system. Is a database system used on the
web and its very fast, reliable and very easy to use.

3.8.1 Database schema (Tables)

A database schema is the skeleton structure that represents the logical view of the entire database. It
defines how the data is organized and how the relations among them are associated. It formulates all
the constraints that are to be applied on the data. We introduce the following tables.
i. User table
ii. Reports table
iii. Feedback table

3.8.2 User Table

This table is used for authentication and authorization process which stores information of the item: Id,
username, password, last login, first name, last name and finally Boolean field named is_admin, which
is responsible for designing whether a user is an official (admin) or just a regular user.
Field Type

ID (PK) INT (11)

Username VARCHAR (256)

Password VARCHAR (256)

Lastlogin DATETIME

Firstname TEXT

Lastname TEXT

Is_admin Boolean

29
3.8.3 Reports Table
This table is used to store information of the item: Id, reporter, tittle, description and
timestamp.
FIELD TYPE

ID (PK) INT (11)

Reporter (FK) INT (11)

Tittle VARCHAR (256)

Description TEXT

Timestamp DATETIME

3.8.4 Feedback Table

Is an automatic system use to response to a query, and stores information of the following item:
Id, user, time and body.
FIELD TYPE

ID (PK) INT (11)

User (FK) VARCHAR (256)

Time DATETIME

Body TEXT

30
 CHAPTER FOUR

RESULTS AND DISCUSSION

4.1 Introduction
This chapter discussed the results involved in the development and implementation of electrical
faults reporting system, the results of the analysis conducted to ascertain the system
requirements, and the requirements was transformed into a functional system. System
Implementation is a process that converts the system requirements and design into program code.
To implement a system successfully, a number of inter-related tasks need to be carried out in an
appropriate sequence. System implementation refers to the transformation of the logical system
design into program codes. The new system may be completely replacing an existing manual or
automated system or it may be a major modification to an existing system.
This stage also involves the testing of the system to find, debug and handle bugs or errors.
4.2 System Requirements
The resources needed for the development of the new system are:
i. Hardware requirements
ii. Software requirements
4.2.1 Hardware Requirements
Hardware is the physical component of a computer, it provides a platform that support a software
on a computer, for the purpose of these project, the under listed hardware are required for smooth
running of the proposed system. They are as follows:
i. Computer system
ii. 512 RAM or above
iii. 512 HDD or above
iv. 1.0 GHz processor
4.2.2 Software Requirements
Software is a set of instruction that enable a computer to perform a particular task. Software
required for effective functionality of the proposed system is as follows:

31
 i. HTML, CSS, as front-end tools
ii. Python, Django as back-end tools
iii. SQL lite server as database
iv. Operating system
v. Browser

4.3 Results
Below are the results (screenshots) of interfaces for the electric fault report management system

4.3.1 Home Dashboard

Plate 4.1: Home page

Home Page screen give a brief explanation of the site and also give access to navigate through
various pages of the web site, there are Login button for redirecting to the login page, register
button for redirecting to the Signup page, emergency, report a fault and feedback button for
redirecting to complain page and response page respectively, but if you did not log in it will
redirect you to the login page. And also, in the Menu there are some buttons for Home, View
complaint and Logout button.

32
4.3.2 Emergency Report Page

Plate 4.2: Emergency Report Page

Emergency report page is for an urgent, unexpected and unusual situation that poses immediate
risk. It serves as a dedicated interface for users to report urgent electrical faults or hazardous
conditions that require immediate attention. It is designed with simplicity, speed, and efficiency
in mind, allowing for quick submission of emergency reports without overwhelming the user

33
4.3.3 Registration Page

Plate 4.3: Registration page

The Registration Page allows users to create an account on the system, providing necessary
information to verify their identity and grant them appropriate access levels. This page is simple,
secure, and provides a smooth user experience like full name of the user (First Name, Last
Name), a valid email address for communication and notifications and a secure password field
with password strength indicators to guide users in creating strong passwords. Passwords should
meet security requirements such as minimum length, use of numbers, symbols, and both
uppercase and lowercase letters

34
4.3.4 Login Page

Plate 4.4: Login page

The Login Page enables users to access their accounts securely by entering their credentials. The
page is designed to be straightforward while incorporating security measures to protect user data
and prevent unauthorized access. This will provide a login form to the user where he/she will
input the login details and get access such as username and password.

35
4.3.5 Report Page

Plate 4.5: Report page

The Report Page enables users to submit reports about electrical faults they encounter. The page should
collect relevant data about the fault and provide mechanisms for attaching evidence, such as photos or
videos. The information is then forwarded to the appropriate personnel or teams for resolution.

36
4.3.6 View Complaint Page

Plate 4.6: View complaint page

The View Complaint Page allows users to view and track the status of complaints they have
submitted. It serves as a central hub where users can check the progress of their electrical fault
reports, review details, and receive updates. It is designed to provide users with an overview of
all the complaints they have filed, along with detailed information on each one, such as its status,
assigned personnel, and response actions. The page allows users to interact with their complaints
and stay informed about ongoing issues.

37
4.3.7 Feedback Page

Plate 4.7: Feedback page

The Feedback Page allows users to provide input on their experience with the fault reporting and
resolution process. It serves as an important tool for evaluating the performance of technicians
and the system's overall efficiency. The feedback helps the maintenance team improve their
service quality, response time, and user satisfaction

38
4.3.8 Frequently Ask Question Page

Plate 4.8: Frequently Ask Questions (FQA)

The Frequently Asked Questions (FAQ) Page provides users with quick access to essential
information and answers to common questions related to the system, reporting procedures, fault
resolution, and technical support. This page helps users find answers on their own without
needing to contact support, making the system more user-friendly and efficient.

39
4.3.9 Admin Registration Page

Plate 4.9: Admin Registration page

The Admin Registration Page is a crucial component that allows administrators to create
accounts that grant them access to manage the system, oversee user complaints, and perform
various administrative functions. This page should be designed to ensure security, user-
friendliness, and completeness of required information

4.3.10 Admin Back End Page

Plate 4.10: Admin backend page

40
The Admin Backend Page is a crucial interface that enables administrators to manage user
accounts, monitor reported faults, oversee the resolution process, and generate analytics and
reports. This page should be user-friendly, secure, and equipped with the necessary tools to
facilitate efficient administration of the system.

4.3.11 Logout Page

Plate 4.12: Logout page

The Logout Page is an essential part of any web application. It provides users, particularly
administrators, with a secure and straightforward way to end their session. This page ensures that
sensitive information is protected and that users can log out with confidence, knowing their data
is safe.

4.4 Discussion
One of the primary objectives of the Electrical Fault Reporting System was to conduct a comprehensive
system analysis to identify user requirements, evaluate existing processes, and design an efficient solution
tailored to the needs of both users and administrators. This objective was achieved through a systematic
approach involving several critical steps. Following the data gathering phase, a thorough requirements
analysis was conducted to define the system's functional and non-functional requirements. This involved
categorizing the necessary features into modules, such as user registration, fault reporting, complaint

41
tracking, and administrative controls. By utilizing tools like use case diagrams and flowcharts, we were
able to visualize the interactions between users and the system, ensuring that all user scenarios were
accounted for. This structured analysis also helped in identifying critical system requirements, such as
security protocols, data storage solutions, and performance benchmarks, which guided the development
phase.

Another objective was to design model for the Electrical Fault Reporting System was approached
systematically to ensure clarity, scalability, and functionality. The design process included several key
phases, each aimed at capturing different aspects of the system's architecture and workflow. The objective
of designing a model for the Electrical Fault Reporting System was successfully achieved through a
structured approach that included use case diagram, flow charts and Database Schema. This model not
only clarified how the system would function and interact but also provided a solid foundation for the
development phase, ensuring that the final product would meet user needs and operational requirements.
Implementing the Proposed System was executed through a structured and methodical approach, ensuring
that all aspects of the system were developed. The user interface (UI) was built using modern web
technologies such as HTML, CSS, and JavaScript. Frameworks like Bootstrap were utilized to create
responsive and visually appealing pages, including the Registration Page, Login Page, Report Page, and
Admin Backend Page. User feedback was incorporated during the development to ensure that the
interface was intuitive and accessible. The server-side logic was implemented using a robust
programming language (e.g., Python, Java, or PHP). This included functionalities such as user
authentication, complaint submission, and data processing. The relational database was created based on
the entity-relationship diagram designed earlier. Tables were defined for users, complaints, technicians,
and logs, with appropriate relationships and constraints established to maintain data integrity. SQL scripts
were developed to set up the database schema and populate it with initial data.

42
 CHAPTER FIVE

SUMMARY, CONCLUSION AND RECOMMENDATIONS

5.1 Summary
This project has identified a problem of fixing and reporting of electrical fault, appears
much more difficult and time consuming in Modibbo Adama University Yola. This project has
solved this problem by developing a web based system that has the capacity to come up with a
relatively affordable fault reporting system that will mitigate the hardships associated with fault
reporting in university. Several literatures Related to this project have been reviewed and similar
system that possesses similar capabilities has been examined. To make the development process
systematic, waterfall model was adopted as the Software development life cycle approach for the
development. And also some phases of waterfall model have me adopted and they are followed
sequentially. In order to identify its goal and procedure and create systems that will efficiently
achieve them, system analysis is used. Moreover, necessary requirement has been gathered
through one to one interview and the interview was open ended. Functional requirements and
non-functional requirements have been specified. Various diagrams were used to depict various
aspect of the system e.g.; flow chart, and use case diagram. In this project, My SQL (structured
query language) has chosen as database of the software. This is an open source relational
database management system. Some table was introduced, user table: is used to authenticate and
authorize process which stores information of the item, report table: is used to store the
information of the item, and feedback table: is an automatic system use to response to a query,
and store information.
All the result involved in the development of the electrical fault reporting, the result of the
analysis conducted to ascertain system requirements, includes hardware requirement and
software requirements, and they were transformed into functional system. The system is able to
give room for students and the staffs to login, to the home page, emergency page, registration
page, login page, report page, feedback page, and also allow the admin to login, change
password, view report, update report, generate report, delete report feedback and also logout.
Consequently, the software was coded successfully in python programming language, and it was
tested successfully to ensure that it has met the user requirement.

43
5.2 Conclusion
This project set out to address the difficulty that staff and student encountered when reporting
any kind of electrical problem and a fully functional web based system for reporting electrical
faults was developed successfully after reviewing similar works to identify area for improvement
and obtaining vital requirements. Hence it can be concluded that the aim of this project has been
achieved.

5.3 Recommendations
Although this project has successfully developed a web based system for
1. It is recommended that further research be undertaken to develop Symbian or IOS that can run
on various operating systems.
2. I will suggest and improvement of electrical fault (the system should offer report for
Adamawa state)
3. The implementation of the system is highly recommended to simplify, to easily and
conveniently accomplish electrical fault reporting service.

44
References
Abinaya, S., Gurupriya, and M. Pooja, (2017), “IoT based smart and adaptive lighting in street
lights”, ICCCT, Chennai, India.

Abrams, L. S., & Snyder, H. N. (2014). Juvenile offenders and victims: 2014 national report.
US Department of Justice, Office of Justice Programs, Office of Juvenile Justice
and Delinquency Prevention.

Charles A. Gallangher (2021). Define the concept of the MIS has evolved over a period of time
comprising many different facets of the organizational function
https://www.jstor.org/stable/3116556

Chen W., Tam H. and Vo, P. N. (2015), “An IoT application for fault diagnosis and
prediction”, IEEE, Sydney, NSW, Australia.

(Coles, 2021) Defined database is an organized collection of data. http://plus.kuppingercole.

com/article/lc70970/database.

Cottle, C. C., Lee, R. J., & Heilbrun, K. (2018). The prediction of criminal recidivism in
juveniles A meta-analysis. Criminal Justice and Behavior, 45(8), 1095-1115.

Dennis lock, (2020). The purpose of project management, the issue of improved availability is
particularly important. https://www.kobo.com/ww/en/ebook/project-management

Dowds, T. J., & Farrington, D. P. (2020). Digital case management in custody settings: A
review of practice and evidence. Criminal Behaviour and Mental Health, 30(3), 163-
174.

Jiwon Choi, (2018), “Detecting and identifying faulty IoT devices in smart home with context
extraction”, IEEE, Luxembourg City, Luxembourg.

Jorge C Seabra, Mário A Costa Jr., Mateus M Lucena (2016), “IoT based intelligent system for
fault detection and diagnosis in domestic appliances”, IEEE, Berlin, Germany.

Junghee Lee, Monobrata Debnath, Amit Patki, Mostafa Hasan, Chrysostomos Nicopoulos
(2018), “Hardware-based online self-diagnosis for faulty device identification in
largescale IoT systems”, IEEE, Orlando, FL, USA.
Kelly Rainer, jr (2020), define the role of the MIS in an organization can be compared to the role
of heart in the body.https://www.smartsheet.com/management-information-system?amp
Kenneth C. Laudon (2021), define the foundation of MIS is the principles of management and if

45
 its practices.Https://en.m.wikipedia.org/wiki/management_information_system
Pravesh Kumar, Shilpi Kain (2018), “Smart community maintenance ecosystem with Self-
reporting and self-diagnostic IoT sensors”, IEEE, Mumbai, India.
Ravi (2019), http://electricalarticle.com/causes-nature-effect-fault-power-system/
Saha Timo Niemirepo, Markus Sihvonen, Vesa Jordan, Juhani Heinilä (2019) “Service platform
for automated IOT service provisioning”, ICIMS, Blumenau, Brazil.

Smith, Gaoming Shi, Guanghua Yuan, Xuanlong Chen, Zhenfeng Xie, Cheng Chen, (2018)
Case study of no fault founds in household appliances”, ICEPT, Shanghai, China.

Tanaya Tavade, Paresh Nasikkar (2017), “Raspberry Pi: Data logging IOT device”, ICPEDC,
Chennai, India.
Tyler (2019), https://en.m.wikipedia.org/wiki/time-domain_reflectometer

Yalcin, F. and Yildirim, Y., 2019. A study of symmetrical and unsymmetrical short Circuit faults
analyses in power system. Sakarya university journal of science, pp. 879-897.
Zhang et al, 2018 Three-phase Unbalance of Voltage Dips. PhD thesis, Chalmers University of
Technology.

46