i

FAULT REPORTING SYSTEM FOR ABUJA ELECTRICITY

DISTRIBUTION COMPANY

BY

YOUR FULL NAME

(YOUR MATRIC NUMBER)

AUGUST, 2021
 ii

FAULT REPORTING SYSTEM FOR ABUJA ELECTRICITY

DISTRIBUTION COMPANY

BY

YOUR FULL NAME

(YOUR MATRIC NUMBER)

A Project Submitted in Partial Fulfillment of the Requirements for

the Degree Of Bachelor of Science In Department Of Computer

Science, Federal University Lafia.

AUGUST, 2021
 iii

Declaration

This project is my original work and has not been presented for a degree in any other university.

No part of this project may be reproduced without the prior written permission of the author

and/or Federal University of Lafia.

AISHA_______________________________________(Signature)

Date:_________________________________________
 iv

Approval

This is to certify that AISHA; 2031100011 undertook this research work DESIGN AND

IMPLEMENTATION OF A FAULT REPORTING SYSTEM and meets the requirements for

submission to the Department of Computer science Federal University of Lafia, in partial

fulfillment for the award of Bachelor of science (B.Sc.) Computer Science Degree 2021.

……………………………............. ................................................
Your Supervisor’s Name. Date
(Project Supervisor)

……………………………............. ................................................
HOD’s Name. Date
(Head of Department)

……………………………............. ................................................
Professor S.B. Junaidu Date
External Examiner
 v

Dedication

This project work is dedicated to.........................................

 vi

Acknowledgement

First and foremost I want to acknowledge ..........................................................................

 vii

Abstract

The aim of this project is to develop a web-based fault reporting system for Abuja
Electricity Distribution Company (AEDC). To achieve the aim and objectives of this
study, Object Oriented Methodology was adopted. The outcome of this project work is
expected to improve the way data is stored and retrieved and greatly improves the process
of reporting faults thereby, reducing the Mean time to restore (MTTR) faults. Both
primary and secondary methods of data collections were used for the purpose of this
study. The primary data were from gotten from oral awarding of questions to the AEDC
management and staff involved in fault reports and also complementing the interview is
personal observation of the routine of the current fault reporting system of the Abuja
Electricity Distribution Company. The secondary method of data used for this research is
the use of libraries which comprises of textbooks, past project works, the internet, and
other related works. Hypertext Preprocessor (PHP) was used as the server side
programming language for the web application. JavaScript, Cascading Style Sheet and
HTML were used for developing client side application whereas Adobe Fireworks was
used for the graphics design of the web application. The result of the project work is a
web-based fault reporting system for Abuja Electricity Distribution Company.
 viii

Table of Contents

Declaration.....................................................................................................................................iii
Approval.........................................................................................................................................iv
Dedication........................................................................................................................................v
Acknowledgement..........................................................................................................................vi
Abstract..........................................................................................................................................vii
Table of Contents.........................................................................................................................viii
List of Table....................................................................................................................................ix
List of Figures..................................................................................................................................x
CHAPTER ONE: Introduction........................................................................................................1
1.1 Background to the Study...................................................................................................1
1.2 Statement of the Problem..................................................................................................2
1.3 Aim and Objectives of the Study......................................................................................3
1.4 Scope of the Study............................................................................................................3
1.5 Significance of the Study..................................................................................................4
1.6 Limitation of the Study.....................................................................................................4
1.7 Research Questions...........................................................................................................5
1.8 Definition of Terms...........................................................................................................5
CHAPTER TWO: Literature Review..............................................................................................7
2.1 Introduction.......................................................................................................................7
2.2 Conceptual Framework.....................................................................................................7
2.2.1 Fault Reporting/ Management.......................................................................................7
2.2.2 Benefits of a Fault Reporting System............................................................................9
2.3 Resilience of Power Distribution Systems......................................................................10
2.4 Failures of the Poles of Electrical Distribution System..................................................12
2.5 Cost-Benefit Analysis.....................................................................................................12
2.6 Review of Related Studies..............................................................................................13
2.7 Summary of the Chapter.................................................................................................16
CHAPTER THREE: Research Methodology................................................................................17
3.1 Methodology Adopted for this Work..............................................................................17
3.2 System Analysis..............................................................................................................18
 ix

3.2.1 Analysis of the Existing System..................................................................................18

3.2.2 Advantages of the Existing System.............................................................................19
3.2.3 Disadvantages of the Existing System........................................................................19
3.2.4 Alternative Solution to the Problems Identified..........................................................20
3.2.5 Justification for the Proposed System.........................................................................20
3.2.6 Analysis of the Proposed System................................................................................21
3.2.7 Advantages of the Proposed System...........................................................................22
3.2.8 Disadvantages of the Proposed System.......................................................................22
3.3 Data Collection Method..................................................................................................23
3.3.1 Primary Method...........................................................................................................23
3.3.2 Secondary Method.......................................................................................................23
3.4 System Design and Specification....................................................................................24
3.4.1 Dataflow Diagram.......................................................................................................24
3.4.2 Use Case Model...........................................................................................................25
3.5 System Requirements......................................................................................................27
3.5.1 Input and Output Requirements..................................................................................27
3.5.2 Hardware and Software Requirements........................................................................27
3.6 Table Specification.........................................................................................................28
3.7 Design Tools for the Project...........................................................................................30
CHAPTER FOUR: Discussion of Results.....................................................................................32
4.1 Introduction.....................................................................................................................32
4.2 Discussion of Results......................................................................................................32
4.2.1 Client’s Login Page.....................................................................................................33
4.2.2: Client’s Registration Page................................................................................................34
CHAPTER FIVE: Summary, Conclusion and Recommendation.................................................36
5.1 Summary.........................................................................................................................36
5.2 Conclusion......................................................................................................................37
5.3 Recommendation............................................................................................................38
REFERENCES..............................................................................................................................39
 x

List of Table

Table 4.1: Admin Account Table

Table 4.2: Client’s Account Table

Table 4.3: Reports Table

 xi

List of Figures

Figure 3.1:

Figure 3.2:

Figure 4.1:
 1

CHAPTER ONE: Introduction

1.1 Background to the Study

The Fault Reporting System (FRS) involves management of faults within an

organization. It will assist engineers in the electricity distribution center to log faults and

be able to escalate faults to expected Field engineers (Akinbinu, 2018). The Field

engineers are also expected to report observations and activities carried out in respect to a

particular fault to ensure the fault is closed appropriately from the system (Maduka,

2014). The Aim of the project is to improve on the process of escalation, tracking and

reporting of faults from a traditional method of typing in excel files to a more driven

information technology process. This would be achieved by developing a system for

managing faults in an operations environment, ensuring faults are logged promptly,

ensuring quick and prompt escalation to all stakeholders, ensuring reports are delivered

as well as proper management of the fault.

The Fault Reporting System is a web-based application. So, it can be accessed by AEDC

clients from any region: any state, through any means: mobile devices, tablets, laptops

etc. The system is divided into two modules:

1. The Client Module: This is the interface where AEDC clients report faults detected

within their vicinity. This can be through uploading pictures, video footage or just simple

text messages, with the details of the location where the fault is detected so that AEDC

staff and respond for repairs.

 2

2. Admin Module: This is the interface of the Web-Based Application where AEDC staff

can view and access all reported faults from their clients, process it and dispatch a

response team for repairs.

The system can be accessed via a web browser on a personal computer, tablet or mobile

phone. It is against this background that this study tends to develop a fault reporting

system for AEDC clients/staff.

1.2 Statement of the Problem

The current Fault Reporting System adopted by the Abuja Electricity Distribution

Company (AEDC) is done manually. The AEDC staff log faults on Excel sheets on

computer systems and these faults are escalated by SMS (short message service) to field

engineers, reports are prepared as needed which could be cumbersome especially when

there is a need to get updates from field engineers over the phone or via SMS (short

message service) as regard failure on network elements (Abubakar & Bala, 2017). Also

when faults are detected via alarm systems to the network operations center engineer, the

process of escalating this fault to the field engineer is a slow process as the engineers

need to manually type the fault type into an SMS application platform and also manually

input the contacts of the appropriate field Engineers before sending out the SMS (Folarin

& Abdul-Hameed, 2015).

Operators in the electricity distribution industry are saddled with increasing competition

worldwide and their ability to provide uninterrupted services keeps them at the edge of

the market flow (Chukwudebe & Chika, 2016). To ensure the systems are properly

monitored most electricity distribution outfit have a Network operations center where all
 3

faults are monitored adequately, logged for management purpose and escalated to the

field engineers for immediate actions (Wojuade, 2019).

The Fault Reporting System will ensure faults are logged, escalated and reported as

against different processes that are used to log, escalate and report faults on the network.

It will also provide a platform for escalation through SMS to all stakeholders involved. It

will also provide a wider query for reporting and provide better data analysis of faults

resolution details.

It is in light of the above stated problems that this research work tends to find a lasting

solution, by developing a fault reporting system for AEDC clients.

1.3 Aim and Objectives of the Study

The main aim of this project is to develop a fault reporting system for AEDC clients.

However, the specific objectives of this project are to:

1. Develop a web-based application for AEDC clients to report fallen electric poles,

sparks, leakages and other electrical fault within their vicinity.

2. To develop and test the prototype of the system with a centralized database for storing

and managing all reported faults by AEDC clients.

3. Develop a web-based fault reporting system with a control panel where AEDC staff

can view and access reported faults for consequent action.

1.4 Scope of the Study

This project work focus mainly on the design and implementation of a fault reporting

system that can be applicable to any electricity distribution company in Nigeria but with
 4

particular reference to AEDC clients/staff. It is expected to improve the way data is

stored and retrieved and greatly improves the process of reporting faults thereby,

reducing the Mean time to restore (MTTR) faults.

1.5 Significance of the Study

The design and implementation of a fault reporting system will be of significant to staff

and clients of Abuja Electricity Distribution Company as the successful implementation

of this project will bring relief to the staff and management as the system will ensure

faults are logged, escalated and reported as against different processes that are used to

log, escalate and report faults on the network. It will also provide a platform for

escalation through SMS to all stakeholders involved. It will also provide a wider query

for reporting and provide better data analysis of faults resolution details.

This study is also significant to other researchers who may want to carry out research in

the same study area as this report will serve as a guide and resource material to carry out

the research work.

1.6 Limitation of the Study

This study “Design and Implementation of a Fault Reporting System for AEDC” has the

following limitation:

1. The system is a web application; hence, it will require internet connectivity by

AEDC clients to access it.

2. The system is only limited to Abuja Electricity Distribution Company’s Clients.

 5

1.7 Research Questions

The following research questions will guide the study:

1. What are the features of the existing fault reporting system adopted by Abuja

Electricity Distribution Company?

2. What are the strengths and weaknesses of the existing fault reporting system adopted

by Abuja Electricity Distribution Company?

3. What are the alternative solutions to the weaknesses/problems of the existing fault

reporting system adopted by Abuja Electricity Distribution Company?

1.8 Definition of Terms

Fault: is an imperfection in the electrical circuit due to which current is deflected from

the intended path. In other words, the fault is the abnormal condition of the electrical

system which damages the electrical equipment and disturbs the normal flow of the

electric current.

Fault report: a report of disrupted or degraded electronic communications service that is

made by a customer and is attributable to an electronic communications network of the

licensee or any interconnected public electronic communications network, and that is not

found to be invalid.

Web Application: is application software that runs on a web server, unlike computer-

based software programs that are run locally on the operating system (OS) of the device.

Web applications are accessed by the user through a web browser with an active network

connection.
 6

Storing: is the action of saving information for later use. With computers, you store

information on a storage device, such as an internal hard drive, optical disc drive, or an

external storage device.

Accessing: is simply the process of being able to get what you need. Data access is being

able to get to (usually having permission to use) particular data on a computer. Web

access means having a connection to the World Wide Web through an access provider.

Data: referred to known facts that could be recorded and stored on computer media.

These are facts made up of text, numbers, images, and sounds.

Database: A systematically arranged collection of computer data, structured so that it

can be automatically retrieved or manipulated. It is also called Databank.

Computer Program: This is a set of instruction that guides the computer on the action to

perform.

System: system is a combination or arrangement of parts to form an integrated whole. A

system includes an orderly arrangement according to some common principles or rules.

 7

CHAPTER TWO: Literature Review

2.1 Introduction

This chapter presents and reviews the relevant literature that has been documented by

various scholars and authors in the area of the study. The literature was reviewed in

accordance with the major themes of the study as identified in the specific objectives.

2.2 Conceptual Framework

2.2.1 Fault Reporting/ Management

Fault reporting allows users and contractors such as the field engineers to view and

review all stages of a electrical fault incident through a consolidated report. The web

portal report is accessible anytime, anywhere with an internet connection. This function

allows users to file a fault incident via an online web portal or mobile application.

Indication of the specific area, location and type of equipment that require for service are

available as well as photo attachment selection (Salman et al., 2015).

According to Salman et al. (2015) when using a fault reporting system, an email or SMS

notification will be sent to relevant contractors once a fault incident is filed. Contractors

can update the remedial action taken via the mobile application. Once the case is closed,

a rectification SMS will be sent to notify the user and management. Live monitoring and

summary report of fault incidents filed will also be available for viewing via the online

web portal and mobile application.

Fault management is defined as the characteristic by which a distributed system can mask

the fault’s occurrence and recover from it (Gadgil et al., 2017). This means that when a
 8

system can determine a fault and recover from it, then we can say that it has fault

management capability. The main role for fault management is to increase the ability of a

system to perform its function correctly even in the presence of internal faults, thus

increasing the dependability of a system (Burns and Wellings, 2011). Three main actions

must be performed at any fault occurrence; i.e detection, reporting and recovery (Denaro

et al., 2016).

Fault detection is the first step in the system to assess if a specific functionality is, or will

be faulty. After the system has detected a fault, the next step is to report the faults and

then prevent or recover from this fault, this is defined as fault recovery. The goal of fault

detection is to verify that the services being provided are functioning properly. The

simplest way to perform such a task is through observation (e.g., log file) and manual

removal of incorrect values. The techniques for detection are the following: self

diagnosis, group detection and hierarchical detection. Through self diagnosis the node

itself can identify faults in its components. With group detection, several nodes monitor

the behavior of other nodes. Finally, in hierarchical detection, fault detection is

performed using a detection tree where a hierarchy is defined for the identification of

faulty nodes (Burns and Wellings, 2011).

According to Liu et al. (2019), there are two general techniques used for developing

robust systems against system faults. These are:

1. Fault tolerance aims to control either hardware or software faults and continues the

system operation with a reduction in throughput or an increase in latency. The main

 9

method used is exception handling, which provides activities to handle various faults

( Liu et al., 2019).

2. Fault management provides users with information of existing faults as accurately and

informatively as possible, to enable detection of malfunctions of desired properties, and

diagnosis of the root causes.

2.2.2 Benefits of a Fault Reporting System

Chukwudebe & Chika (2016) reported the following as the benefits of a fault reporting

system:

Accountability on Defects or Faults

A central channel is utilized to monitor incoming fault incidents. This helps to decrease

the downtime and number of unattended cases. Any fault incidents filed will also be sent

to the respective service team immediately for the next course of action. Latest servicing

personnel can also be identified based on historical records.

Fast Response Time and improves in Customer Service Standards

Upon receiving a fault incident, system alert will trigger a notification SMS or email to

the relevant service team for immediate service remedial. This minimizes service

downtime and users complaints, in turn, improves users experience. Paperless fault

incidents records and invoices are also readily available through emails.
 10

Proof of Service and Minimize Dispute

Experience full transparency with real-time service report using GPS tracking and images

with digital signatures which helps in minimizing miscommunication between users and

service team. Proof of service will also be provided to validate any disputes and

complaints.

2.3 Resilience of Power Distribution Systems

As the severity and frequency of natural hazard-induced disasters increase year by year

(NOAA 2017), utility companies are very keen to develop resilient power distribution

systems. An electric pole-based resilience assessment can establish a strong base for

prestorm planning. The literature shows a variety of definitions of resilience, and there is

no consensus on the one accepted definition of the term. Resilience can be simply defined

as the capability of a system to anticipate and absorb threats to mitigate adverse effects as

well as develop response and recovery actions to resume its normal operations (Eren

Tokgoz and Gheorghe, 2013). According to Hosseini et al. (2016), resilience is ‘‘the

ability of an entity or system to return to normal condition after the occurrence of an

event that disrupts its state.’’ Similarly, Nan and Sansavini (2017) define resilience

capability as ‘‘the ability of the system to withstand a change or a disruptive event by

reducing the initial negative impacts, by adapting itself to them and by recovering from

them.’’

Haimes (2009) also defines resilience as ‘‘the ability of the system to withstand a major

disruption within acceptable degradation parameters and to recover with a suitable time

and reasonable costs and risks.’’ The concept of resilience is multidimensional, and the
 11

quantification of it depends on several factors (MacKenzie and Zobel, 2016). It is hard to

consider all possible factors and vulnerabilities against various disasters, but preparation,

response, recovery, and mitigation efforts, which are resilience strategies, can reduce the

adverse consequences of disasters (Eren Tokgoz et al., 2017). Carlson et al. (2012)

claimed that the concept of resilience plays a vital role in assessing the threats for various

entities, such as owners and operators of critical infrastructures, communities, regions,

and the nation. Resilience can be assessed at the asset/facility level and critical

infrastructure level to develop methodologies that provide resilience-related information

to critical infrastructure owners, operators, state, and local partners. Power distribution

systems are complex systems and increasing their resilience by implementation of some

mitigation actions could be costly.

Moreover, investment in increased resilience of power distribution systems involves

several complexities, such as a lower rate of future return, strict regulatory restrictions by

the Public Utility Commission (PUC), lack of strong value propositions, and inadequate

incentives (Mukhopadhyay and Hastak, 2016). Mukhopadhyay and Hastak stated that the

present investment analysis framework has flaws; hence it is not cogent and persuasive to

PUC. A report published by the U.S. Executive Office of the President mentioned that

investment in electric grid modernizations and increased resilience of the electric grids

would reduce hardship and recovery time during weather-related disasters as well as cut

down the costs associated with damages based on these disasters over time (Executive

Office of the President, 2013). According to this report, the annual cost of lost power due

to outage consists of foregone output and wages, spoiled inventory, delayed production,

inconvenience, and damage to the electric grid itself.

 12

2.4 Failures of the Poles of Electrical Distribution System

Several studies have been conducted on the failure of utility poles in the power

distribution system. Shafieezadeh et al. (2013) found that wooden poles often fail due to

a wind load greater than the flexural capacity of a pole. Han (2008) examined two

mechanisms that cause the failure of poles flexural failure due to the wind load and

foundation failure. A structural analysis involving wind loads and the probabilities of

failure has been conducted in the Caribbean Disaster Mitigation Project (1996). In this

project, the wooden pole was assumed to be a cantilever beam that will fail if the bending

stress exceeds the modulus rupture of a pole. Taras et al. (2004) argued that the strength

of a pole is subject to decay over time and a pole may fail due to lateral bending. United

States utility companies have struggled to strike a balance between over- and under

preparation because they lack a rigorous methodology with which to estimate the damage

caused by hurricane winds (Guikema et al. 2010). Various methods have been proposed

by researchers to increase the reliability of power distribution systems under wind-related

disasters and to decrease the time required to restore damaged systems. These efforts can

be largely divided into two groups: predictive models and storm hardening models

(Salman et al. 2015; Wanik et al. 2015).

2.5 Cost-Benefit Analysis

Several studies have been conducted to perform a cost–benefit analysis on upgrading the

electric power distribution network. In the Caribbean Disaster Mitigation Project (1996),

a cost–benefit analysis was conducted on the replacement of wooden poles to mitigate

damage due to hurricanes. The results of the analysis revealed that the replacement of the

wooden poles in a high voltage network with Class 1 poles results in a significant cost
 13

saving, but the same action with the lower voltage network is over investment. Taras et

al. (2004) considered the cost of poles, labor expenses, and power outage cost as the cost

of pole replacement. Quanta Technology (2009) conducted a cost–benefit analysis of

utility infrastructure upgrades and storm hardening programs based on data collected

from several utility companies. In Quanta report, the estimated benefits were calculated

against the duration of a power outage and the projected rate of failure or damage.

Results were evaluated by selecting and strengthen 10% of distribution poles in Texas,

the United States. The potential net benefit from the hardening was estimated as well.

However, it did not show how the most vulnerable part of the distribution network was

selected for strengthen purpose.

Chang (2003) developed a framework of extended life-cycle cost to evaluate efforts for

mitigating the impact of disaster on infrastructure systems. This framework consists of

four major costs-planned cost, associated cost imposed on the society, unplanned cost,

and societal cost due to a power outage. Salman et al. (2015) adopted Chang’s framework

to evaluate the cost-effectiveness of a targeted hardening strategy for a power distribution

system that is susceptible to the impact of hurricane damage under both probabilistic and

scenario-based hurricane conditions.

2.6 Review of Related Studies

Jorge 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
 14

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.

Pravesh & Shilpi (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 find it

difficult to take effort and record community issues. Also studies has 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.

Junghee et al., (2018) proposed a self diagnosis technique for faulty node identification in

large-scale IoT 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.

Timo et al. (2015) proposed a method DICE, to detect and identify faulty IoT devices

with context extraction. DICE identified faulty devices successfully with an average of
 15

94.9% precision and 92.5% recall. Our system took an average 3 minutes to detect faults

and average 28 minutes to identify faulty devices.

Tanaya & Paresh (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. This is implemented using the Controlled Area Network (CAN) protocol for

communication and Raspberry Pi which is a card size computer which acts like an

Internet of things (IOT) device. The development and design of data logger system

depends on the application on which it will work. The fault diagnostics system is done in

two methods online and offline detection.

Guikema et al. (2010) developed a model to predict the number of utility poles that need

to be replaced based on wind-related damage data from previous storms by applying

regression analysis and data-mining techniques;

Salman et al. (2015) applied fragility analysis and Monte Carlo simulation to determine

the probability of pole failure with varying wind speeds from which they proposed

targeted hardening strategies based on an index of important components. They

considered the whole system rather than an individual pole;

Ouyang and Duenas-Osorio (2014) introduced a component fragility model to quantify

the resilience of the electric power system in which poles are considered to estimate the

fragility of the entire distribution system;

Shafieezadeh et al. (2013) developed a fragility curve of wooden poles based on the

moment capacity of the pole and the moment demand placed on those poles by wind
 16

loads. However, they did not consider the deflection and deformation of a pole incurred

by wind loads;

Darestani et al. (2016) proposed a boundary model to capture the boundary effects of

adjacent wooden poles in response to wind-induced forces. They used a time dependent

decay model and a probabilistic wind model to perform a Monte Carlo simulation to

determine the probability of pole failure.

2.7 Summary of the Chapter

This chapter presents and reviews the relevant literature that has been documented by

various scholars and authors in the area of the study. The literature was reviewed in

accordance with the major themes of the study as identified in the specific objectives.

The chapter discusses the following:

i. Conceptual framework

ii. Fault reporting/management

iii. Benefits of fault reporting system

iv. Failures of the Poles of Electrical Distribution System

v. Resilience of Power Distribution Systems

vi. Cost-benefit analysis

vii. Review of related studies

viii. Summary of the chapter

 17

CHAPTER THREE: Research Methodology

3.1 Methodology Adopted for this Work

The methodology adopted for this research work is object oriented methodology (OOP).

We live in a world of objects. These objects exist in nature, in man-made entities, in

business, and in the products that we use. They can be categorized, described, organized,

combined, manipulated and created.

Therefore, an object-oriented view has come into picture for creation of computer

software. This methodology asks the analyst to determine what the objects of the system

are, how they behave over time or in response to events, and what responsibilities and

relationships an object has to other objects. Object-oriented analysis has the analyst look

at all the objects in a system, their commonalties, difference, and how the system needs to

manipulate the objects. OOM of building systems takes the objects as the basis, Firstly,

the system to be developed is observed and analyzed and the requirements are defined.

Secondly, the objects in the required system are identified e.g. AEDC clients, admin,

computer systems, online fault reporting system etc. in simple terms, OOM is based on

identifying the objects in a system and their interrelationships, once this is done, the

implementation of the system is done.

The basic steps of system designing using Object Modeling may be listed as:

a. System Analysis

b. System Design

c. Object Design

d. Implementation
 18

Advantages of Object Oriented Methodology

Object Oriented Methodology closely represents the problem domain. Because of this, it

is easier to produce and understand designs. The objects in the system are immune to

requirement changes. Therefore, allows changes more easily.

Object Oriented Methodology designs encourage more re-use. New applications can use

the existing modules, thereby reduces the development cost and cycle time.

Object Oriented Methodology approach is more natural. It provides nice structures for

thinking and abstracting and leads to modular design.

3.2 System Analysis

System analysis is a process of collecting factual data, understanding the processes

involved, identifying problems and recommending feasible suggestions for improving the

functionality of the system. This involves studying the business processes, entity

relationships gathering operational data, understand the information flow, finding out

bottlenecks and evolving solutions for overcoming the weaknesses of the system so as to

achieve the organizational goals. System Analysis also includes decoupling of complex

processes that make up the entire system, identification of data store and manual

processes.

3.2.1 Analysis of the Existing System

The current Fault Reporting System adopted by the Abuja Electricity Distribution

Company (AEDC) is done using computer systems but not web-based. The AEDC staff

log faults on Excel sheets on computer systems and these faults are escalated by SMS
 19

(short message service) to field engineers, reports are prepared as needed which could be

cumbersome especially when there is a need to get updates from field engineers over the

phone or via SMS (short message service) as regard failure on network elements. Also

when faults are detected via alarm systems to the network operations center engineer, the

process of escalating this fault to the field engineer is a slow process as the engineers

need to manually type the fault type into an SMS application platform and also manually

input the contacts of the appropriate field Engineers before sending out the SMS.

3.2.2 Advantages of the Existing System

The existing system enables the AEDC staff to log faults on Excel sheets on computer

systems and these faults are escalated by SMS (short message service) to field engineers.

The existing system even though is not completely paper-based makes use of computer

systems even though it is a desktop application and not web-based application.

3.2.3 Disadvantages of the Existing System

The existing system is characterized but not limited to the following inefficiencies:

a) The current system is vulnerable to natural disaster like flood, fire outbreak and

rodent attack of files which will cause loss of information.

b) The current system lacks a web-based database for the storage of files which makes

these files to occupy the physical storage space.

c) Lots of time is devoted to the filling of forms in logical for easy retrieval of

information.

d) There is insufficient manpower to cope with the growing population of electricity

users.
 20

3.2.4 Alternative Solution to the Problems Identified

The alternative solution to these identified problems with the existing system is

development of a web-based fault reporting system; the proposed system will eliminate

the problems encountered in the manual system. If implemented, it will play a great role

such as:

Increase efficiency: the computerized system formulates accurate efficiency, faster and

effective way of processing hostel activities, with the intervention of computer.

Storage: the new system provides a better means of information storage, all records

related to electrical faults are stored on a centralized database and encrypted to avoid

unauthorized access.

Error free: the new system with the computer intervention in processing, errors will be

avoided or minimized.

Speed: the new system offers the AEDC staff and the management an opportunity to

retrieve and sort files in the shortest possible time compared to the manual method.

3.2.5 Justification for the Proposed System

After a thorough analysis of the existing system and a careful feasibility study to find out

if there is need for automation of the existing system, the adoption and implementation of

the proposed system will in no doubt be of great benefit to the organization (Abuja

Electricity Distribution Company) which will help in overhauling the current system

which is characterized by inconsistency, data security, lack of data integrity and

concurrency problem.
 21

The proposed Fault Reporting System is a web-based application. So, it can be accessed by

AEDC clients from any region: any state, through any means: mobile devices, tablets, laptops etc.

The system can be accessed via a web browser on a personal computer, tablet or mobile phone.

3.2.6 Analysis of the Proposed System

The Fault Reporting System is a web-based application. So, it can be accessed by AEDC

clients from any region: any state, through any means: mobile devices, tablets, laptops

etc. The system is divided into two modules:

The Client Module: This is the interface where AEDC clients report faults detected

within their vicinity. This can be through uploading pictures, video footage or just simple

text messages, with the details of the location where the fault is detected so that AEDC

staff and respond for repairs.

Admin Module: This is the interface of the web-based application where AEDC staff

can view and access all reported faults from their clients, process it and dispatch a

response team for repairs. The system can be accessed via a web browser on a personal

computer, tablet or mobile phone.

The Fault Reporting System will ensure faults are logged, escalated and reported as

against different processes that are used to log, escalate and report faults on the network.

It will also provide a platform for escalation through SMS to all stakeholders involved. It

will also provide a wider query for reporting and provide better data analysis of faults

resolution details.
 22

3.2.7 Advantages of the Proposed System

a) A central channel is utilized to monitor incoming fault incidents. This helps to

decrease the downtime and number of unattended cases. Any fault incidents filed will

also be sent to the respective service team immediately for the next course of action.

Latest servicing personnel can also be identified based on historical records.

b) Upon receiving a fault incident, system alert will trigger a notification SMS or email

to the relevant service team for immediate service remedial. This minimizes service

downtime and users complaints, in turn, improves users experience. Paperless fault

incidents records and invoices are also readily available through emails.

c) Experience full transparency with real-time service report using GPS tracking and

images with digital signatures which helps in minimizing miscommunication between

users and service team. Proof of service will also be provided to validate any disputes

and complaints.

d) The proposed system can be accessed by AEDC clients from any region: any state, through

any means: mobile devices, tablets, laptops etc.

e) The proposed fault reporting system can be accessed via a web browser on a personal

computer, tablet or mobile phone.

3.2.8 Disadvantages of the Proposed System

a) The system is a web application, hence, it will requires internet connectivity by

AEDC clients to access it.

b) It will take time to train the adequate manpower required to operate the proposed

system.
 23

3.3 Data Collection Method

For the purpose of this project work, data were collected from both primary and

secondary methods of data collection;

3.3.1 Primary Method

This primarily centers on direct involvement with personnel or experts in the field of

discipline the researcher is carrying out his/ her research on. The major tool for the

collection of the primary data for this researcher work is:

Interview: Use of interview-oral awarding of questions to the AEDC management and

staff involved in fault reports. The accuracy in using this method of obtaining data for

processing is high because there are no assumed figures or data. The information gotten

is trusted to be genuine. The awarding of oral questions to respondents was to aid the

researcher get a leverage ground of the technical know-how of the impact of the use of

the web especially in Abuja Electricity Distribution Company which is chosen as the case

study for this research. All this aimed towards arriving at a good conclusion.

Direct observation: Complementing the interview is personal observation of the routine

of the current fault reporting system of the Abuja Electricity Distribution Company.

3.3.2 Secondary Method

The secondary method of data used for this research is the use of libraries which

comprises of textbooks, past project works, the internet, and other related works. This

method of data collection is to broaden the scope of the researcher and to look into
 24

several peoples work and what has been done so far in order to give his/her own quota to

the topic under review.

3.4 System Design and Specification

The system design shows the blueprint of any system that is to be developed. It gives the

very detail about every component of the system that is to be built. Here the researcher

gives the general outline of the final product (what could be referred to as manual). The

various procedure of usage of the new system is given here, i.e. how to, what to and on

what shall the system be used on. The importance of the design is to enable system

designer or researcher to know the cost consequence of the product on the user and the

developer. In that the effectiveness of the system will not be obsolete. (Investing much

resource and having less productivity).

3.4.1 Dataflow Diagram

A Data Flow Diagram (DFD) is a structured analysis and design tool that can be used for

flowcharting. A DFD is a network that describes the flow of data and the processes that

change or transform the data throughout a system. This network is constructed by using a

set of symbols that do not imply any physical implementation. It has the purpose of

clarifying system requirements and identifying major transformations. So it is the starting

point of the design phase that functionally decomposes the requirements specifications

down to the lowest level of detail. DFD can be considered to an abstraction of the logic of

an information-oriented or a process-oriented system flow-chart. For these reasons

DFD’s are often referred to as logical data flow diagrams. Below is the dataflow diagram

for the proposed system.

 25

Start

Login Register
Request login credentials

Authentication Layer Database

Submitting login credentials

Manage AEDC
View Reported View Statistics of View List of Registered
Clients
Faults Faults by location AEDC Clients
Database
Web Application

Figure 4.1: Dataflow Diagram of the Proposed System (Admin)

3.4.2 Use Case Model

Use case diagrams describe what a system does from the standpoint of an external

observer. The emphasis of use case diagrams is on what a system does rather than how.

They are used to show the interactions between users of the system and the system. A use

case represents the several users called actors and the different ways in which they

interact with the system.

 26

Below is the diagram of the use case for the proposed system.

Register

Login/Logout

AEDC Admin/ Staff AEDC Client

Manage AEDC Clients Database

Report Fault

View Reported Faults

View Statistics of Faults by Location

View List of Registered AEDC Clients

Update Account Profile

Figure 4.2: Use case Diagram of the Proposed System

Actors: The actors in the proposed system are the AEDC Admin/Staff and the AEDC

Client

Use Cases: The use cases in the proposed system are: Login/logout, Register, report

faults, manage AEDC client’s database, view reported faults, view statistics of faults by

location, view list of AEDC clients, update account profile.

 27

3.5 System Requirements

To be used efficiently, all computer software needs certain hardware components or other

software resources to be present on a computer. These prerequisites are known (as

computer) system requirements and are often used as a guideline as opposed to an

absolute rule. Below are the requirements for the proposed system:

3.5.1 Input and Output Requirements

The input requirements includes: users ID, AEDC clients’ details, staff details, locations,

etc.

The output requirements includes: fault reports, fault locations, staff information, client’s

details, statistics of faults by location etc.

3.5.2 Hardware and Software Requirements

The hardware is the physical and tangible components of a system unit which will

function together to perform the required task.

The system requirements and minimum specifications for running the application are

given below:

1. Operating Systems: Windows, Linux, Mac OS, Android (the Web Application

can be accessed via any OS).

2. Web browser: Google Chrome, Mozila Firefox, Opera, Microsoft Edge.

3. RAM: 1GB (for minimum high performance)

4. Hard Drive: 10GB (for minimum high performance)

5. Processor: AMD, Intel (R) Pentium (R) @ 1.60GHz

 28

6. System type: 32, 64 and x86-bit.

3.6 Table Specification

The information on the database of the website which is in formatted tables, making it a

relational database, it has to be regularly updated and edited. Implying that there should

be masters file which according to Mr. Adegoke (introduction to file processing, 2008) is

not permanent in nature, since it has to reflect current changes to reflect the current

events as they unfold. Among the tables to be regarded as master files in this research

work is;

i. Admin Account Table

ii. Client’s Account Table

iii. Reports Table

Table 3.1: Admin Account Table

The admin account table stores details and data of all the admin in the database. Details

such as the admin id, admin’s name, email, phone number, username, password etc. The

Admin Account Table is shown below;

FIELDNAME DESCRIPTION FIELD DATA TYPE FIELD SIZE

Adminid Admin Id Integer 10
Name Admin Name Varchar 100
Email Admin email Varchar 100
Phone_number Admin Phone No. Varchar 12
Username Admin username Varchar 100
Password Admin password Varchar 100
 29

Table 3.2: Client Account Table

The client account table stores details and data of all the registered clients in the database.

Details such as the client id, name, email, phone number, gender, state, L.G.A, address,

username, password etc. Below is the client account table.

FIELDNAME DESCRIPTION FIELD DATA TYPE FIELD SIZE

Client_id Client Id Integer 10

Name Client Name Varchar 100

Email Client email Varchar 100

Phone_number Client Phone No. Varchar 12

Gender Client gender Varchar 100

State Client state Varchar 100

LGA Client LGA Varchar 100

Address Client address Varchar 100

Username Admin username Varchar 100

Password Admin password Varchar 100

Table 3.3: Reports Table

The reports table stores the details of faults reports stored in the database. Details such as

client_id, fault, state, LGA, address, date, report, evidence, certification, action etc.

Below is the reports’ table.

FIELDNAME DESCRIPTION FIELD DATA TYPE FIELD SIZE

 30

Client_id Client Id Integer 10

Fault Fault Varchar 100

State State Varchar 100

LGA LGA Varchar 100

Address Address Varchar 100

Date Date Integer 10

Report Report Varchar 100

Evidence Evidence Varchar 100

Certification Certification Varchar 100

Action Action Varchar 100

3.7 Design Tools for the Project

The technologies/tools that will be used for this work are as follows:

Programming Language:

Hypertext Preprocessor (PHP) will be used as the server side programming language for

the web application. Consequently, JavaScript, Cascading Style Sheet and HTML will be

used for developing client side application. Adobe Fireworks will be used for the

graphics design of the web application.

 31

Database Architecture:

MySQL relational database management system will be adopted to store all the reports of

AEDC clients from the web application, including the text, pictures and videos. However,

the videos will be stored in a secure folder on the web server for efficiency. MySQL

implements SQL (Structured Query Language), which is used for storing, manipulating

and retrieving data stored in the relational database.

The features of MySQL include the following:

 Open Source (free to download and use)

 It is scalable

 High flexibility

 Client/server architecture

 It has high security

 Easy to use and implement

 Allows execution of large-volume data

 Provides maintenance features such as debugging, upgrades, backup, restore, rollback

of transactions etc.
 32

CHAPTER FOUR: Discussion of Results

4.1 Introduction

This chapter presents the discussion of the outcome of the proposed system (Fault

reporting system: A Case Study of Abuja Electricity Distribution Company) the details of

the web application showing the various modules. This chapter summarizes the project

from its objectives to implementation and results. The project primarily aimed at

mitigating the difficulty faced in detecting and locating the electrical faults in the

distribution level.

4.2 Discussion of Results

Below are the system modules and how the system operates, it will give the users better

understanding of how the system works. There are two different users of this system; the

admin and the AEDC clients. Each of the user has his different activities in the system.
 33

4.2.1 Client’s Login Page

The client’s login page is the page where users of the system (AEDC clients) can login

and have access to their dashboard. The clients will use their username and password to

gain access to their dashboard. Each client must be registered before gaining access to

their dashboard. Below is the client's login page.

Figure 4.1: Showing the Clients’ Login Page

 34

4.2.2: Client’s Registration Page

The client’s registration page is the page where each AEDC client must sign up so as to

become a user of the system. Each client fills in the sign up form so as to get his/her data

in the database for retrieval when needed. After filling the form, on clicking the signup

button, the clients information are then stored in the database.

Figure 4.2: Showing the Client’s Registration Page

 35

4.2.3 Admin Login Page

The admin login page is the page where the admin of the system i.e the AEDC staff logs

in with using their login credentials (username and password) to gain access to the

system. An admin must be registered so as to gain access to their respective dashboards.

The login by imputing his username and password then click on the button ‘sign in’, if

the username and password are valid, the will then grant the admin acess. Below is the

admin login page.

Figure 4.3: Showing the admin login page

 36

4.2.4: The Admin Dashboard

The admin dashboard is the page that is displayed to the admin after a successful login

with a valid username and password. As can be seen from the left hand side of the figure

below are the activities executable by the admin. The admin can view the client’s

database, view the statistics of fault’s report, edit his profile, change his/her username and

password etc. below is the figure showing the admin dashboard.

Figure 4.4: Showing the Admin Dashboard

 37

4.2.5: Falling Poles Report Form

On this page, the AEDC client can report any case or fault of fallen poles. The client

report the fault of a fallen pole by filling the falling poles report form. There are several

other reports that can submitted by a client such as; report of low current, report of spark

wire, report of loss of face, report of loss of supply, report of high voltage and current etc.

The page is build in such a way that a client can add an attachment of either a picture or

anything so as to viewed by the AEDC clients. Below is the figure showing the falling

poles report form.

Figure 4.5: Showing the falling poles report form

 38

4.2.6: Clients Database

As one of the activities that can be performed by the admin who must be a staff of the

AEDC, the staff can view the client’s database by clicking the button AEDC client’s

database. The admin can delete a client if he so desires to by clicking on the button delete

as can be seen on the figure below.

Figure 4.6: Showing the Client’s database

 39

4.2.7: Reports Database

This page displays the list of reported electrical faults as submitted by the AEDC clients.

As one of the task that can be performed by the admin, the admin can view the list of

reported electrical faults, the admin can also take an action by clicking on the button

‘resolve fault’ and also view evidence of the reported electrical faults by clicking on the

button ‘view evidence’. Below is the figure showing reports database.

Figure 4.7: Showing the reports database

 40

4.2.8 Admin Profile Update Page

The admin profile update page is the page where the admin can edit his profile. The

admin perform such task by filling ‘profile edit form’. On clicking the button ‘save

changes’, the admin’s profile information is updated in the database. Below is the figure

showing the admin profile update page.

Figure 4.8: Showing the admin profile update page

 41

4.2.9 Client Profile Update Page

The client profile update page is the page where the client can edit his profile. The client

perform such task by filling ‘profile edit form’. On clicking the button ‘save changes’, the

clien’s profile information is updated in the database. Below is the figure showing the

client profile update page.

Figure 4.9: Showing the Client profile update page

 42

4.2.10 Faults Statistical Report

On this page the admin can view the statistical reports of faults. The admin perform such

task by simply clicking on the button ‘statistics reports’. Below is the figure showing the

statistics of faults reported in the database.

Figure 4.10: Showing faults statistical reports

 43

4.2.11 Username and Password Update

On this page a client can change his username and password. The client does that by

filling the form shown below. On clicking the button ‘save changes’, the client’s login

details are updated in the database.

Figure 2.11: Showing the username and password update page

 44

CHAPTER FIVE: Summary, Conclusion and Recommendation

5.1 Summary

The main aim of this project is to develop a web-based fault reporting system using

Abuja Electricity Distribution Company (AEDC) as a case study. Other objectives of the

study are; to develop a web-based application for AEDC clients to report fallen electric

poles, sparks, leakages and other electrical fault within their vicinity, to develop a

centralized database for storing and managing all reported faults by AEDC clients and to

develop a web-based control panel (admin module) where AEDC staff can view and

access reported faults for consequent action. To achieve the aim and objectives of this

study, Object Oriented Methodology was adopted. The outcome of this project work is

expected to improve the way data is stored and retrieved and greatly improves the process

of reporting faults thereby, reducing the Mean time to restore (MTTR) faults.

Both primary and secondary methods of data collections were used for the purpose of this

study. The primary data were from gotten from oral awarding of questions to the AEDC

management and staff involved in fault reports and also complementing the interview is

personal observation of the routine of the current fault reporting system of the Abuja

Electricity Distribution Company. The secondary method of data used for this research is

the use of libraries which comprises of textbooks, past project works, the internet, and

other related works.

Data flow and use case diagrams were used to explain the system architecture of the

proposed web-based fault reporting system. Hypertext Preprocessor (PHP) was used as

the server side programming language for the web application. JavaScript, Cascading
 45

Style Sheet and HTML were used for developing client side application whereas Adobe

Fireworks was used for the graphics design of the web application. The result of the

project work is a web-based fault reporting system for Abuja Electricity Distribution

Company.

5.2 Conclusion

This project was tested for performance and proved to be working according to the design

specifications. The functional requirements were achieved. The system is capable of

indicating the fault location, reporting faults to the AEDC clients from the control room

as well as the magnitude of fault, report of fallen electric poles, sparks, leakages and

other electrical fault within their vicinity. The accuracy depends on the specifications in

the instruction codes. On the other hand, all the specific objectives were achieved as well

as the project deliverables.

Before now in Abuja Electricity Distribution Company, when faults are reported, the

field engineers either notifies the appropriate individuals by a call and SMS, records the

fault in a book or an excel file and waiting till the fault is resolved. This system has been

developed to aggregate all the functions of the field engineers into a system that logs the

fault, tracks the fault, notifies via an SMS and generates a report accordingly thereby

improving the efficiency of the operations by 70.48% in comparison to the old system.

The design and implementation of this web-based fault reporting software became

necessary because the manual diagnosis method is inefficient. The design and

implementation of this web-based fault reporting system will be of significant to staff and

clients of Abuja Electricity Distribution Company as the successful implementation of

 46

this project will bring relief to the staff and management as the system will ensure faults

are logged, escalated and reported as against different processes that are used to log,

escalate and report faults on the network. It will also provide a platform for escalation

through SMS to all stakeholders involved. It will also provide a wider query for reporting

and provide better data analysis of faults resolution details.

5.3 Recommendation

The researcher wishes to recommend that:

1. Instruction manual has been developed on how to use the system so it is

recommended that this instruction is followed strictly.

2. The system can only detect electrical faults and report the faults detected to the

field engineers but not resolve the faults so users should ensure they report any

slight in change of any electrical fault as valuable human life can be lost due to

negligence.
 47

REFERENCES

Abubakar, A. N. and Bala, B. G. (2017). "Strengths, Weaknesses, Opportunities and Threats

(SWOT) Analysis on Globacom Ltd," International Journal of Information Technology
and Business Management, vol. 16, no. 1, pp. 83-91,

Akinbinu, A. (2018). "New Telecommunication Technologies And The Financial Health Of The
Nigeria Telecommunications Ltd," Nigerian Journal Of Engineering Management, pp.
14-22.

Burns, A. and Wellings, A. J. (2011). Real-Time Systems and Programming Languages: ADA
95, Real-Time Java, and Real-Time POSIX. Addison-Wesley Longman Publishing Co.,
Inc., Boston, MA, USA.

Carlson, J.L., R.A. Haffenden, G.W. Bassett, W.A. Buehring, M.J. Collins III, S.M. Folga, F.D.

Petit, J.A. Phillips. (2012). Resilience: Theory and application. Lemont, IL: Argonne

National Laboratory. https://publications.anl.gov/anlpubs/2012/02/72218.pdf. Accessed

25 Jan 2018.

Chukwudebe, O.G. and Chika, I.E. (2016). "Sustainable National Telecommunication

Development: An Overview Critical Requirements," in Proceedings of the National
Engineering Conference of the Nigerian Society of Engineers, pp. 269-278.

Denaro, G., Pezz´E, M., Tosi, D., and Schilling, D. (2016). Towards self-adaptive service
oriented architectures. In TAV-WEB’06: Proceedings of the 2006 workshop on Testing,
analysis, and verification of web services and applications. ACM, New York, NY, USA,
10–16.

Eren Tokgoz, B., M. Safa, and S. Hwang. (2017). Resilience assessment for power distribution

systems. International Journal of Civil and Environmental Engineering 11(7): 806–811.

 48

Folarin, D.A. and Abdul-Hameed, T.A. (2015). "Developing a Software Package for Forecasting
Mobile Communications Network Subscribers in Nigeria," International Journal of
Science and Technology, vol. 1, no. 6, pp. 289-298.

Gadgil, H., Fox, G., Pallickara, S., and Pierce, M. (2017). Scalable, fault-tolerant management in
a service oriented architecture. In HPDC ’07: Proceedings of the 16th international
symposium on High performance distributed computing. ACM, New York, NY, USA,
235–236.

Han, S.R. (2008). Estimating hurricane outage and damage risk in power distribution systems.

Ph.D. thesis. College Station, TX:Texas A&M University.

https://oaktrust.library.tamu.edu/bitstream/handle/1969.1/ETD-TAMU-2923/HAN-

DISSERTATION.pdf?sequence=1&isAllowed=y. Accessed 13 Mar 2018.

Haimes Y.Y. (2009). On the definition of resilience in systems. Risk Analysis: An International

Journal 29(4): 498–501.

Hosseini, S., K. Barker, and J.E. Ramirez-Marquez. (2016). A review of definitions and

measures of systems resilience. Reliability Engineering and System Safety 145: 47–61.

Jorge, C. S., Mário, A. C.., Mateus, M. L. (2016), “IoT based intelligent system for fault

detection and diagnosis in domestic appliances”, IEEE, Berlin, Germany.

Junghee, L., Monobrata, D., Amit, P., Mostafa, H., Chrysostomos, N. (2018), “Hardware-based

online self-diagnosis for faulty device identification in large scale IoT systems”, IEEE,

Orlando, FL, USA.

Maduka, V. I. (2014). "Telecommunications in NEEDS," in Proceedings of COREN 13 th

Engineering Assembly, Abuja, pp. 68-75.
 49

MacKenzie, C.A., and C.W. Zobel. 2016. Allocating resources to enhance resilience, with

application to super storm Sandy and an electric utility. Risk Analysis 36(4): 847–862.

Mukhopadhyay, S., and M. Hastak. (2016). Public utility commissions to foster resilience

investment in power grid infrastructure. Procedia-Social and Behavioral Sciences 218:

5–12.

Nan, C., and G. Sansavini. (2017). A quantitative method for assessing resilience of

interdependent infrastructures. Reliability Engineering and System Safety 157: 35–53.

NOAA (National Oceanic and Atmospheric Administration) (2017). Billion-dollar weather and

climate disasters: Table of events. https://www.ncdc.noaa.gov/billions/events/US/1980-

2017. Accessed 5 Jan 2018.

Shafieezadeh, A., P.U. Onyewuchi, M.M. Begovic, and R. Des-Roches. (2013). Fragility

assessment of wood poles in power distribution networks against extreme wind hazards.

In Advances in hurricane engineering: Learning from our past, ed. C.P. Jones, and L.G.

Griffis, 851–861. Reston, VA: American Society of Civil Engineers.

Pravesh, K. & Shilpi, K. (2018), “Smart community maintenance ecosystem with self-reporting

and self- diagnostic IoT sensors”, IEEE, Mumbai, India.

Liu, A., Li, Q., Huang, L., and Xiao, M. (2019). Facts: A framework for fault-tolerant
composition of transactional web services. IEEE Transactions on Services Computing 99,
PrePrints, 46–59.

Taras, A., G. Ratel, and L. Chouinard. (2004). A life-cycle cost approach to the maintenance of

overhead line supports. In Reliability and optimization of structural systems, ed. M.A.

Maes, and L. Huyse, 241–250. London: CRC Press.

 50

Tanaya, T., Paresh, N. (2017), “Raspberry Pi: Data logging IOT device”, ICPEDC, Chennai,

India.

Timo, N., Markus, S., Vesa, J., Juhani, H. (2015), “Service platform for automated IOT service

provisioning”, ICIMS, Blumenau, Brazil.

Wojuade, J. I. (2019). "Impact of global system for mobile telecommunication on Nigerian

Economy: A case of some selected local government areas in Oyo State, Nigeria.,"
University of Ibadan, Nigeria, Ibadan, A Med Thesis.
 51

Appendix: Source Code

Index Page

<!DOCTYPE html>
<html lang="en">
<head>
<?php include './headerlinks.php'; ?>
</head>
<body class="bg-theme bg-theme4">
<!-- start loader -->
<div id="pageloader-overlay" class="visible incoming"><div class="loader-wrapper-
outer"><div class="loader-wrapper-inner" ><div class="loader"></div></div></div></div>
<!-- end loader -->
<!-- Start wrapper-->
<div id="wrapper">
<div class="loader-wrapper"><div
class="lds-ring"><div></div><div></div><div></div><div></div></div></div>
<div class="card card-authentication1 mx-auto my-5">
<div class="card-body">
<div class="card-content p-2">
<div class="text-center">
<img src="assets/images/logo.png" width="100" height="100" alt="logo
icon">
</div>
<div class="card-title text-uppercase text-center py-3">AEDC Fault Reporting
System</div>
<div class="card-title text-uppercase text-center py-3">Client - Sign In</div>
<form action="dashbaord.php" method="post">
<div class="form-group">
<label for="exampleInputUsername" class="sr-only">Username</label>
<div class="position-relative has-icon-right">
<input type="text" id="exampleInputUsername" class="form-control
input-shadow" placeholder="Enter Username">
<div class="form-control-position">
<i class="icon-user"></i>
</div>
</div>
</div>
<div class="form-group">
 52

<label for="exampleInputPassword" class="sr-only">Password</label>

<div class="position-relative has-icon-right">
<input type="password" id="exampleInputPassword" class="form-control
input-shadow" placeholder="Enter Password">
<div class="form-control-position">
<i class="icon-lock"></i>
</div>
</div>
</div>
<div class="form-row">
<div class="form-group col-6">
<div class="icheck-material-white">
<input type="checkbox" id="user-checkbox" checked="" />
<label for="user-checkbox">Remember me</label>
</div>
</div>
<div class="form-group col-6 text-right">
<a href="resetpassword.php">Reset Password</a>
</div>
</div>
<button type="submit" class="btn btn-success btn-block">Sign In</button>
</form>
</div>
</div>
<div class="card-footer text-center py-3">
<p class="text-warning mb-0">Do not have an account? <a href="signup.php">
Sign Up here</a></p>
</div>
</div>
<!--Start Back To Top Button-->
<a href="javaScript:void();" class="back-to-top"><i class="fa fa-angle-double-up"></i>
</a>
<!--End Back To Top Button-->
<!--start color switcher-->
<!--end color switcher-->
</div><!--wrapper-->
<!-- Bootstrap core JavaScript-->
<script src="assets/js/jquery.min.js"></script>
<script src="assets/js/popper.min.js"></script>
<script src="assets/js/bootstrap.min.js"></script>
<!-- sidebar-menu js -->
 53

<script src="assets/js/sidebar-menu.js"></script>
<!-- Custom scripts -->
<script src="assets/js/app-script.js"></script>
</body>
</html>