Elaboration of registration system of

derangements for Moldtelecom JSC

telecommunication network

MASTER ANDREEV VASILE

 Goals

To allow an engineer to spend more time on more complex issues

that require more indepth review and analysis.
To increase efficiency and quality of work done by network
operator.
 Tasks

To prove the necessity of elaboration of a software for automatic registration

of network faults.
To determine with which types of troubles a network operator has to deal with
during his workday.
To study current solution algorithms of such types troubles and to determine
which operations can be done by a program.
To elaborate a new solution algorithm of such types troubles which implies
that a part of the job will be done by a program.
To elaborate and integrate a software in production management environment.
To describe program architecture, its components and their algorithms of
operation.
To describe how the program interacts with the user and different network
systems.
 Necessity of elaboration of a software for automatic
registration of network faults

Weekdays ~ 39 46 faults per day

Weekends ~ 7 16 faults per day
Average number of network faults

Day of the week

 Necessity of elaboration of a software for automatic
registration of network faults

Maximum: from 9:00 till 11:00 ~ 5 faults per hour

Minimum: from 03:00 till 04:00 ~ 0.19 faults per hour

Average number of network faults

Period of time
 Necessity of elaboration of a software for automatic
registration of network faults
3 weeks = 710 network faults
Duration: 31,54% - till 20 minutes, 21,69% - till 1 hour, 22,11% - till 3 hours,
16,9% - till 12 hours, 7,6% - more than 12 hours
Duration, hours

Sirial number
of a fault
Types of troubles a network operator has to deal with during
his workday.

93% of network are faults related with electrical power disconnections.

478 67%

181 25% Power failure of electricity supplier

Planned power supply shutdowns
Other
51 7%
 Current solution algorithm

1 2 3 4

Handling 1 trouble ticket

1 No
9
0 8 5
takes from 4 till 16 minutes.
Yes Is
Power
fault
Yes Failure?
solved? No No Yes
1 Is power 1connected?
6
What about 40
1
Is trouble
fault
2
Waiting solved?
20
Waiting 2 hours
tickets a day?
No minutes
Yes

= many hours of routine work7

 New solution algorithm

1 2 3 4

The program can handle

No 8 5
from 37.5 till 100% of the new
1
0 Is fault
IsIsallowed
timer
9
solved?
Yes
expired
Yes
to close?6 No
No

algorithm
No Waiting operations.
Power failure?
4 minutes
Yes Yes
7

It11 saves up to 10 minutes of

network operators work time.
The software architecture
User Interface
 Conclusion

The research of faults demonstrates that 93% of network faults can be

handled by a program.
The program can handle from 37.5 till 100% of the new algorithm of network
faults what saves from 2 till 16 minutes of operator's work time for each
network fault.
With the use of the program each trouble ticket will be opened automatically
what guaranties that every fault will be registered at fixed period of time what
increases quality and efficiency of work done by a network operator.
The program architecture is ideally suited for solving the goals of the thesis,
what allows a user to perform flexible control of opening, accounting and
closing of trouble tickets.
The user interface design is made in a minimalist style, it contains only
necessary elements, is intuitive understandable and simple in use.
THANK YOU FOR ATTENTION!!!