Professional Documents
Culture Documents
I am immensely grateful to my professional supervisor, Mr. Moudji Ferdinand Ndille, for his
guidance and support throughout my internship, for this project would not have been realised
without him. I equally pay my deep sense of gratitude to Mr. Ivo Sumelong, Founder of
UWACO Cameroon PLC, for taking me in and providing me continuous support.
I also wish to thank my academic supervisor, Prof. Fopah Lele Armand, for his guidance in
the completion of this project.
I feel the need to acknowledge my indebtedness to Mr. Norbel Ambanumben, Chief Technical
Officer of Zinger Systems, for his technical support during my internship. I am also grateful
to the entire Zinger Systems team for hospitality.
I express my sincere to Mr. Eddy Nkouadjio, CEO of UWACO, and the UWACO staff for
their guidance and support.
Finally, yet importantly, my family are also an important inspiration to me. So with due
regards, I express my gratitude to them.
i
TABLE OF CONTENTS
ACKNOWLEDGEMENT...........................................................................................................i
TABLE OF CONTENTS...........................................................................................................ii
LIST OF FIGURES...................................................................................................................iv
LIST OF ABBREVIATIONS.....................................................................................................v
ABSTRACT...............................................................................................................................vi
General Introduction.................................................................................................................vii
CHAPTER 1: INTRODUCTION...............................................................................................1
1.1. Definition of Internship................................................................................................1
1.2. Goals and Objectives of Internship..............................................................................1
1.3. Posting/Application for Internship...............................................................................1
1.4. Company Presentation..................................................................................................2
1.4.1. History...................................................................................................................2
1.4.2. Location................................................................................................................2
1.4.3. Branding................................................................................................................3
1.4.4. Mission..................................................................................................................4
1.4.5. Vision....................................................................................................................4
1.4.6. Ambition...............................................................................................................4
1.4.7. Values...................................................................................................................4
1.4.8. Company Structure...............................................................................................5
CHAPTER 2: INTERNSHIP ACTIVITIES...............................................................................7
2.1. My First Day at UWACO............................................................................................7
2.2. Technical Supervisor....................................................................................................7
2.3. Departments in which I Worked..................................................................................8
2.3.1. Cybersecurity........................................................................................................8
2.3.2. Agile Methodology...............................................................................................9
2.3.3. IT Administration................................................................................................10
2.3.4. Software development........................................................................................10
2.3.5. Hardware Development, Testing and Quality Control.......................................11
2.4. Tasks which I Executed..............................................................................................11
2.5. Main Internship Task Performed................................................................................15
2.5.1. Introduction.........................................................................................................15
2.5.2. Overview.............................................................................................................15
2.5.3. Purpose................................................................................................................15
ii
2.5.4. Scope...................................................................................................................15
2.5.5. Literature Review................................................................................................16
2.5.6. Methodology Adopted........................................................................................17
2.5.7. Results.................................................................................................................23
2.5.8. Performance When Accomplishing Tasks..........................................................24
2.5.9. Challenges Encountered......................................................................................24
2.5.10. Measures Taken to Solve Challenges.................................................................25
CHAPTER 3: OVERALL BENEFITS OF INTERNSHIP......................................................26
CONCLUSION AND RECOMMENDATIONS.....................................................................28
References.................................................................................................................................29
Appendix...................................................................................................................................30
iii
LIST OF FIGURES
iv
LIST OF ABBREVIATIONS
v
ABSTRACT
The objective of this project is to Design and Implement a “Smart Vehicle Information
System” which will guarantee the security of vehicles to all subscribers, home and abroad.
The system contains a 4G Tracking device with Immobilization capabilities installed in a
vehicle, connected to a tracking server and a database from which data about the vehicle is
pulled and viewed on Mobile and Web applications. It also enables users to remotely
immobilize their vehicles.
In order to realise this project, the UWACO team used the Angular framework to design the
Web application, Flutter to build the mobile application, JavaScript to build the backend
server and knowledge of electronics to build the tracking device.
vi
General Introduction
This report is written on account of my internship at UWACO Cameroon PLC. It explains all
the activities carried out before and after the internship and the project which was realised
during the internship period.
1. Chapter One: It contains the objectives of the internship and a detailed description of
the host company. It covers aspects like the history, mission, location, values and
administrative structure of the host company.
2. Chapter Two: This chapter describes all the activities carried during the internship
period and how they were executed. Furthermore, it explains the main internship
project which was carried out, the functionality of the project and its benefits. It also
describes the challenges encountered and the measured taken to overcome them.
3. Chapter Three: It explains the overall benefits of the internship. The final section
contains the conclusion; stating whether the goals of the internship were attained. It
also contains recommendations to the host company and the school administration
vii
CHAPTER 1: INTRODUCTION
Being part of the school curriculum, and a major requirement in the completion of my
degree program, the academic internship plays a very key role in our development.
With this in mind, the objectives I had for the internship were:
To connect theoretical and practical knowledge on our subject field with actual
work experience, in order to complement our field specific skills and learn new
ones.
To be able to apply and analyse our skills. Also, to improve our problem solving
and critical thinking.
Exposure to the professional world and learning of work ethics.
Networking and developing business contacts for potential employment in the
future.
1.4.1. History
1.4.2. Location
In 2021, UWACO’s office was within the Zinger Systems building, behind Express
Exchange Molyko. But later on in early 2022, their head office was moved to the
2
Vallée Commissariat – Bonamoussadi, Douala, so as to enable them get a bigger
market
1.4.3. Branding
i. The Logo: The colours of the logo refer to our African identity. The colours
include: Giza brown and Mwanga brown.
3
The curved separator under the “U” symbolizes the protection they offer to
their customers. The logo can also be displayed horizontally as shown in figure
2 above.
1.4.4. Mission
1.4.5. Vision
UWACO aims to transform the lives of the African population with easy-to-use
affordable solutions. The gap in technological advancement between the western
world and most African nations is still large. However, UWACO is trying to reduce
this gap by improving on the day-to-day lives of Africans with up-to-date
technologies. Also, UWACO provides affordable solutions for the African context.
1.4.6. Ambition
“The starting point of all achievement is desire” (Napoleon Hill). Hence, with the
ambition to dominate the market as a driving force, UWACO strives to be the leader
in day-to-day IT solutions in Cameroon within 5 years and in the CEMAC Zone
within 10 years.
1.4.7. Values
At UWACO, there are three basic values, which must be upheld: simplicity, trust and
loyalty.
i. Simplicity
One of the key objectives of UWACO is to provide user-friendly solutions to
its customers. What would be the use of all the services the company renders if
the customers cannot properly use or understand them? This is why the
company keeps things simple with high quality service. Simplicity also
4
stretches across to the working environment, which makes it very efficient and
easy to work in.
ii. Trust
Providing solutions to problems regarding security would not be possible if the
customers do not trust the company, hence, UWACO builds a strong
relationship with its customers, ensuring them about the trustworthiness of its
services. In addition, the management fully trusts its highly skilled team, as
members of the team are also confident in the abilities of one another. This
creates a very productive working environment.
iii. Loyalty
UWACO shares its vision with all its employees, believing in their strengths
and pushing them to get better every day. Ivo Sumelong (founder of UWACO)
once told me he doesn't believe there anything his team could not do. He
always motivates the team to stay committed and provides support in any way
he can. This is one of the incentives to the hard work the team puts in. And
with this, they stay fully committed and loyal to the company. Furthermore,
with the high quality services and strong relationships built with its customers
through great customer services, UWACO is assured that its customers will
stay loyal to its services.
5
The management of UWACO is done by the corporate strategist (Ivo Sumelong) and
the executive manager (Eddy Nkouadjio), as they work hand-in-glove to define
strategies, ensure the administrative and financial situation of the company. Despite
their huge roles, everyone in UWACO was treated the same, as we never used titles to
address each other; a sign of equality and humility.
6
CHAPTER 2: INTERNSHIP ACTIVITIES
2.
Upon reporting to the office on the 20 th of October, as early as 7:30 am, I met up with
the head engineer of UWACO, Moudji Ferdinand Ndille. Subsequently, he introduced
me to the other members of the team and the neighboring company, Zinger Systems.
Later on, he spoke to me about the company values, encouraged me to be very
inquisitive and self-motivated. I then had a meeting with the company founder (Ivo
Sumelong) on Skype, wherein more light was thrown on the company values, mission
and goal. He also spoke about the dressing code and the importance of punctuality,
self-discipline and professionalism. “You should always have a pen and paper in
hand”, he said to me; to enable me learn as much as I could by jutting down new
concepts and organizing tasks assigned to me.
After the session with Ivo, the head engineer introduced me to the project the
company was working on at that time – the Smart Vehicle Information System
(SVIS). He explained the main components of the systems and how the system
operated, and then gave me manuals of the all the tracking devices they used (GS10,
GS18, GS20 and GS22) to study their respective features and specifications. At the
end of the day, I was asked to report all that I learnt in the evening meeting (a daily
routine of meetings in the morning and evening) and was asked to research on the
generations of network technology, GPS, GSM, OBD and GPRS. Astonished by the
level of technological advancement the projects carried out by the company were at, I
went home feeling enthusiastic about learning more about those new concepts in
telecommunication introduced to me.
7
task assigned to me, or simply uttering motivating words. I believe I would not have
learnt a lot if he was not there and will always remain grateful.
At UWACO, following the work plan, which was made for me, I worked with the
departments of software development, hardware development and maintenance, and
hardware installation. This was so that I would not only improve my skills in the field
of electrical engineering, but also acquire skills in other fields, which would be very
helpful to me. Under the previously listed branches, I was specifically trained on:
Cybersecurity, Agile Methodology, IT administration, Hardware and Software
development processes, Testing and Quality Control.
2.3.1. Cybersecurity
With the growing number of cyber criminals in the world and the need for secured
systems, I was trained on the following:
The PKI strategy
This involved the extensive use of certificates (keys) for authentication and
authorisation into all the platforms UWACO used. In the PKI strategy, public
keys were used for encryption and private keys were used to decrypt encrypted
messages. This eliminated unauthorized access (for example, through stolen
credentials) into their system.
Securing workspaces
The main reason behind this was to protect all files related to UWACO. This
was done by creating a highly encrypted drive in which all company files were
stored, such that even if an employee’s PC was hacked, the hacker won’t have
access to company related files. The application used for creating encrypted
workspaces was VeraCrypt.
Secure file sharing methods
At UWACO, sharing files through platforms like Skype and WhatsApp, or
through USB sticks was prohibited. The safest method of sharing files was by
uploading them to the file repository – Alfresco, and then sharing the link to
the file with the intended recipient.
Complex password generation
8
For platforms that needed passwords for access, complex passwords were
generated with a length of at least 30 characters including: lowercase letter,
9
Figure 6: Jira board; Web view
2.3.3. IT Administration
This training was carried out by Ivo himself, wherein I managed the Identity Access
and Management (IAM) system of UWACO. Here, the main idea was to manage the
central system which controlled access to all the other platforms used by the company.
Creating user accounts for new employees, disabling accounts for employees on leave
or no longer with the company and providing support to any issues regarding
authorization to UWACO’s platforms. All these were done on the Active Directory.
The training was on the web application development process. Since I had to no prior
knowledge on this, I had to learn the basics of HTML, JavaScript and CSS. Since
UWACO used the Angular framework for developing applications, I also had to learn
TypeScript. Angular is a development platform, built on TypeScript. As a platform,
Angular includes: a component-based framework for building scalable web
applications, a collection of well-integrated libraries that cover a wide variety of
features, including routing, forms management, client-server communication, and
more and a suite of developer tools to help you develop, build, test, and update your
code. Next, I learnt about Git; a free and open source distributed version control
system designed to handle everything from small to very large projects with speed and
10
efficiency. I was taught basic Git commands, how to ‘commit’ code and ‘pull’ code to
and from the Git repository (GitLab). Finally, I was introduced to Jenkins; an open
source automation server which enables developers around the world to reliably build,
test, and deploy their software.
The hardware development process starts from analysing the feasibility of the project,
writing down all ideas about the project including its features, configurations,
competing products and number of resources required. Next, the preliminary hardware
design, with a block diagram to specify all the electronic functions and how they
interconnect with other functional components. The next phase, the system block
diagram is used as a reference to design the Schematic Circuit Diagram. While system
block diagram focusses on the high-level functionality of the product, the schematic
marks the tiniest details of microchips, resistors, sensors and components connected
together making the functional circuit. The final phases include: designing of
mechanical and industrial components, designing the PCB and generating the final bill
of materials. The software used for PCB design at UWACO is KiCad.
Testing and Quality Control simply involved testing the performance of services
offered by UWACO. I was trained on how to develop efficient test cases and
document them. The main idea was testing with aim of trying to ‘break’ the service, to
find any vulnerabilities. This goes a long way to ensure the quality of services offered
by UWACO.
At UWACO, I worked during weekdays and working hours were from 8:00 to 17:00.
The normal daily routine included daily morning meetings from 8:00 – 8:15 am,
wherein employees were expected to state the tasks for the day and predict possible
challenges. There were also daily evening meetings from 16:45 – 17:00, in which
employees were expected to state the tasks they worked on and challenges they
encountered. Stated below are some of the tasks I executed.
Employee On-boarding
With the training I received, I was tasked with introducing new employees to
all the platforms used by UWACO, how to navigate the platforms, issues
regarding security such as creating secure workspaces and secure email
11
communication. In effect, I was the IT support personnel always on standby to
help out other employees.
Developed a Web application
After the lessons on software development, I had to build a Task Tracker,
applying all that I learned. The aim was to build an application which would
enable a user add, save, view and deleting tasks created on the application. The
application was built with the Angular framework. Although it took a while to
get done, the results were exquisite.
Device Configuration
With the numerous amount of tracking devices present, I had to configure
some of them using SMS commands. The first part of the process involved
configuring the APN setting and then connecting devices to a particular Server.
I also had to configure other features like motion detection for all devices.
12
Testing and Troubleshooting
Before installing the tracking devices, I had to test if all their features were
functioning properly. To do this, I had to mount circuits using bulbs as loads,
taking walks to test the GPS precision of the devices.
13
I provided support to the electrical technicians during device installation
sessions in vehicles. In addition, I had to document the installation process, so
that new technicians would easily grasp the technique used for such
installations.
14
2.5. Main Internship Task Performed
2.5.1. Introduction
Since the invention of the automobile, they have been prized possessions and
invaluable assets. As cars became more accessible and less of a luxury item, people
began to leave them unoccupied and vulnerable to thieves. Thus, the need to keep
them safe and theft-proof increased. The first recorded car theft took place in Paris,
France, 1896, when a mechanic stole a Peugeot from Baron de Zuylen, founder of the
Automobile Club of France. While the vehicle was eventually recovered and the thief
caught, it set forth a series of innovations that would see our cars become more theft-
proof. These include removable steering wheels, locks, alarms, immobilizers and
finally, the use of trackers. While technology has allowed manufacturers to make cars
more theft-proof, regardless of how secure you think your car is, it is imperative that
you stay vigilant and take every precaution to protect it from theft. A GPS tracker is
the only device that can give you your car’s location after it has been stolen.
2.5.2. Overview
The threat to vehicle security is still large despite several innovations developed to
solve the problem. However, the SVIS will bring about the ultimate form of vehicle
security, as knowing your vehicle’s location even after theft will be possible with a
mobile phone or PC. The system consists of a GPS tracking device installed in a
vehicle, which is linked to a server, mobile and web applications, which provide
interfaces through which users can track their vehicles.
2.5.3. Purpose
This project was aimed at providing a secure vehicle monitoring system to effectively
track vehicles, detect theft and the engine status of vehicles, remotely immobilize
vehicles, mileage, over speeding and to detect when a vehicle enters and leaves a
particular geographical region.
2.5.4. Scope
15
This project is applicable to all vehicles within Cameroon, Nigeria and the CEMAC
zone.
Several systems like alarms, locks and removable steering wheels were put in place in
the past and are still currently used as a means of securing vehicles.
Removable Steering Wheels: They were one of the first anti-theft technology
in cars, developed in the 1900s. The idea was that the driver would remove the
steering wheel after driving and carry it along to deter thieves.
Locks: It seems like a no-brainer to secure cars using locks. However, most
early cars didn’t even have doors, which wouldn’t be standard until the early
1920s. By then, companies started to add locks to their cars. However, early
car locks were easy to pick and it wouldn’t be until the 1970s when more
sophisticated locks were introduced.
Alarms: Car alarms can be dated back to 1913 with a snippet of newspaper
claiming that an unnamed Denver prisoner invented an alarm that would
trigger when someone tried to hand crank the engine. Three years later, in
1916, the magazine “Popular Science Monthly” reported an inventor
developing a wireless alarm system which would make a buzzer vibrate when
their car’s ignition was tampered with. Modern car alarms have sensors to
detect when a vehicle is touched or tampered with and then make a buzzer
vibrate.
Although the systems listed proved to be helpful, they still have many flaws.
Removable steering wheels were quite inconvenient to carry around, as they
were heavy and easily noticeable.
Alarms are easily disabled and their effectiveness up to this day is
questionable.
Locks are easily picked or broken; hence do not fully guarantee security.
16
2.5.6. Methodology Adopted
The main components of the SVIS are the tracking device, the socket server, parse
(database) and the client applications (web and mobile).
a. Device
The main device used is a 4G immobilizer device. It is called an immobilizer because
it provides the functionality of being able to remotely stop a vehicle from moving. The
main components of the device are:
GPS sensor
GSM module
Vibration sensor
Power circuit
17
Backup battery and switch
Memory unit and an MCU
SOS button
In terms of functionality; the GSM module is used for signal transmission, the GPS
sensor receives the specific location GPS location of the device and either transmits to
the socket server or stores in the memory unit, the vibration sensor detects vibrations
within the vehicle in which the device is installed, the memory unit stores data
concerning device configuration and tracks when the device is on but cannot transmit,
the power circuit regulates the charging of the backup battery and powers the entire
device and all of listed components are controlled by a central MCU (STM32F401).
To perform the immobilizing action, the device is coupled with an electrical relay.
With this, an electrical signal from the device controls the relay which when
connected to a vehicle’s ignition line or fuel pump line would immobilize the vehicle.
A diagram of the device coupled with the electrical relay is shown below:
18
Furthermore, the device has LED indicators, to show the connection status of the GPS
and GSM modules. The SOS button is an additional feature for emergencies; when
pressed it sends an alert to the server. Finally, the device is able to detect the engine
status (ON or OFF) using its ACC wire; which is connected to the vehicle’s ignition
line and a SIM card slot. The figure below shows the specifications of the device.
Choice of Relay: The electrical relay chosen was a negatively triggered Bosch
Relay. This 5 pin relay is powerful and performs the switching action
effectively. 12 and 24 V Bosch relays were used depending on the type of
vehicle; 12 V for small vehicles and 24 V for large vehicles.
b. Socket Server
This is the central component of the SVIS. It is an application responsible for
receiving tracks sent by the device and then storing the tracks in Parse (the database).
The Socket Server is a backend server application which was built with JavaScript, in
addition, it is hosted and runs on a remote server. The device is connected to the
Socket server through a socket connection.
A socket is the combination of an IP address and a port, and it acts as an endpoint for
receiving or sending information over the internet, which is kept organized by TCP. A
software port is a number that identifies the specific application or service on your
computer that’s attempting to access the network.
19
The device sends a connection request to the Socket server which is constantly
listening. Then the Server allocates a specific IP address for the device.
20
Figure 16: Data Flow Diagram of Device Communication
c. Parse Server
Parse server is an open source backend server which was integrated to our system. It
basically acts as a database storing data from the socket server in well-organized
tables. All data sent to socket server is decoded, analysed and then stored under
specific sections in the parse server.
21
d. Client Applications
The Web application and Mobile application are the two client applications through
which users can view and interact with the SVIS. These applications get data from the
parse server through queries, then display the data through navigable UI’s. The web
application was built with the Angular framework, while the mobile application was
built with Flutter.
The device is initially configured through SMS. Parameters such as the transmission
rate, APN setting, Server setting, vibration sensor sensitivity and more are configured
by sending SMS commands which the device recognizes. The device intend sends
SMS messages to confirm each configuration. Also, the status of any parameter can be
queried through SMS commands.
Once the device is connected to the socket server, it starts transmitting data to it. Also,
the user can communicate with the device through GPRS commands sent through the
socket server to the device and receive response through the same channel.
22
Figure 17: SVIS Operation
2.5.7. Results
With all the tracks stored in the parse server, comparisons and calculations are done to
get values for speed (using successive location data values), mileage, and other
features. These are all displayed on the client applications.
23
Although I always gave my all to the tasks assigned to me, I still encountered a few
difficulties during my stay at UWACO. Initially, I couldn’t communicate my ideas
clearly to my supervisors since I didn’t know how to appropriately express myself in a
cooperate environment. Next, since I had no history in software development, I
encountered difficulties in developing software applications at first (the task tracker).
Finally, during the period when the company was going live, working hours increased
and the working conditions became quite stressful.
24
25
CHAPTER 3: OVERALL BENEFITS OF INTERNSHIP
26
During the execution of some tasks, I was assigned to organize and coordinate team
members. The feeling of being the lead was new to me, but fortunately, I got through
it and the outcome was successful.
27
CONCLUSION AND RECOMMENDATIONS
At the end, my stay at UWACO was very productive as I accomplished all the
objectives I set for myself. Getting into the corporate world was exhilarating and the skills I
attained will greatly help me in future projects.
My recommendation to the UWACO management is that they develop specific work plans for
their interns which are related to their fields of study. Although acquiring skills from different
engineering fields is important, internships are meant to improve on the practical skills of the
student regarding his field of study.
I would also further recommend to the school administration to help with the internship
application process by obtaining internship placements for the students in different
companies. This is because the application process is very tedious and students are not always
guaranteed internship spots upon application.
28
References
[2] F. Moudji, “Mission and History of UWACO,” UWACO Cameroon PLC, January
2022. [Online]. Available: uwaco.net. [Accessed January 2022].
[4] E. Kaplan, “365 Days of Motoring,” Cellutrak , 21 March 2021. [Online]. Available:
http://www.365daysofmotoring.com/blog/car-maintenance/evolution-car-security-
features-brief-history/. [Accessed 31 January 2022].
[5] H. Damian, “A Brief History of Car Security Systems,” Black Knight Global Tracking
Systems, October 2021. [Online]. Available:
https://www.blackknighttracking.com/post/2019/07/10/a-brief-history-of-car-security-
systems. [Accessed 31 January 2022].
[9] J. S. Team, “Jenkins User Documentation,” Jenkins, June 2016. [Online]. Available:
https://www.jenkins.io/doc/#what-is-jenkins. [Accessed 7 February 2022].
[10] S. Nott, “How do Car Alarms Work,” WarrantyWise, 17 April 2012. [Online].
Available: https://www.warrantywise.co.uk/blog/how-do-car-alarms-
work#:~:text=Shock%20sensors%20detect%20hits%20and,detecting%20when%20an
%20impact%20occurs.&text=The%20car%20alarm%20is%20then,they%20might
%20occasionally%20activate%20accidentally. [Accessed 1 February 2022].
29
Appendix
30
Appendix 3: SVIS Mobile Application Dashboard
31