REALIZATION OF ROBOTIC PROCESS

AUTOMATION (RPA) INITIATIVES IN INDUSTRIAL

A PROJECT REPORT- Phase-I

Submitted by

DIVYAN S 142220104302

SHIVA SHANKARAN R 142220104315

In a partial fulfillment for the award of the degree
of

BACHELOR OF ENGINEERING
in
COMPUTER SCIENCE AND ENGINEERING

SRM VALLIAMMAI ENGINEERING COLLEGE

(AN AUTONOMOUS INSTITUTION)
ANNA UNIVERSITY: CHENNAI 600 025
NOVEMBER 2023
 BONAFIDE CERTIFICATE

Certified that this project titled “REALIZATION OF ROBOTIC PROCESS

AUTOMATION (RPA) INITIATIVES IN INDUSTRIAL” is the bonafide work of
“S.DIVYAN (142220104302) and R.SHIVA SANKARAN (142220104315)
who carried out the project work under my supervision during the academic
year 2023-2024.

SIGNATURE SIGNATURE

Dr. B.VANATHI, M.E., Ph.D., Ms. G. SATHYA, B.E., M.Tech.,

Professor & Head Of The Department Assistant Professor (Ordinary Grade)

Department of CSE Department of CSE

SRM Valliammai Engineering College SRM Valliammai Engineering College

Kattankulathur-603 203 Kattankulathur-603 203

Submitted for the university examination held on ______________ at SRM

Valliammai Engineering College, Kattankulathur-603 203.

INTERNAL EXAMINER EXTERNAL EXAMINER

 ACKNOWLEDGEMENT

We sincerely express our gratitude in depth to our chairman

Thiru.Ravi Pachamoothoo,M.A, and authorities of SRM VALLIAMMAI
ENGINEERING COLLEGE for the patronage on our welfare rooted in the
academic year.

We express our sincere gratitude to our respected Director

Dr.B.Chidambara Rajan, M.E., Ph.D., for his constant encouragement,
which has been our motivation to strive towards excellence.

We thank our Principal Dr.M.Murugan, M.E., Ph.D., for his constant

encouragement, which has been our motivation to strive towards
excellence.

We also thank our Vice Principal Dr.S.Visalakshi, M.E., Ph.D., for her
constant motivation to strive towards excellence.

We extend our hand of thanks to our Head of the Department,

Dr.B.Vanathi, M.E., Ph.D., Professor for her unstinted support.

We are thankful to Project Coordinators, Dr.V.Dhanakoti, M.E., Ph.D.,

Professor for providing us with the essential facilities.

We are grateful to our internal guide Ms.G.Sathya, B.E., M.Tech

Assistant Professor without whose invaluable guidance and
encouragement, this project would not have been a success.

We also like to thank all teaching and non-teaching staff members of

our department, for their support during the course of the project. We
finally thank our friends and family for their support during the course of
project.
 TABLE OF CONTENTS

CHAPTER TITLE PAGE

NO
NO

ABSTRACT V

LIST OF FIGURES AND TABLES VI

1. INTRODUCTION

1.1 System Overview 1

1.2 Purpose 2

1.3 Scope 2

1.4 Existing System 3

1.5 Literature Survey 3

1.6 Proposed System 9

1.6.1 Advantages 9

1.6.2 Limitations 9

2. SYSTEM REQUIREMENTS AND SPECIFICATION

2.1 Software Requirements 12

2.2 Software Environment 12

2.2.1 Arduino IDE 12

 2.2.2 Proteus Design 13

2.3 Coding Language 14

2.3.1 Embedded C 14

2.4 Module Description 15

3. SYSTEM DESIGN

3.1 System Architecture 19

3.2 UML Diagram 20

3.2.1 Use Case Diagram 21

3.3 System Study 22

3.3.1 Feasibility Study 22

3.3.2 Economical Feasibility 22

3.3.3 Technical Feasibility 22

3.3.4 Social Feasibility 23

3.4 Data Model 23

3.4.1 Data Model- Level 0 24

3.4.2 Data Model- Level 1 25

3.5 Input Design 26

 3.6 Output Design 27

4. IMPLEMENTATION

4.1 Crime Data Processing 29

4.1.1 Dataset Collection 29

4.1.2 K-Means Clustering 31

4.1.3 Predicted Output 32

4.1.4 Implementation of Code 32

5. SYSTEM TESTING AND MAINTENANCE

5.1 Testing 35

5.1.1 Software Testing 35

5.1.2 Purpose of Testing 37

5.1.3 Characteristics of Testing 37

5.2 Types of Testing 39

5.2.1 Unit Testing 39

5.2.2 Integration Testing 39

5.2.3 Functional Testing 40

5.2.4 System Testing 41

6. CONCLUSION AND FUTURE WORK 44

7. APPENDIX 47
 8. REFERENCES 72

ii

ABSTRACT

Wearable and non-contact sensor technologies have spread to many

diverse areas with their ease of use and application, and the variety of
applications has been increasing rapidly thanks to technological
developments in the recent years.This work ensures the usability of
wearable and non-contact sensor technologies in various industrial
fields. In this study, it is aimed that operators can easily control
industrial robots in real-time without the need for a specialized
programming environment.
In conclusion, the intellectual healthcare robot is expected to promote a
new field and to pave the way for a new product.The interest in a healthy
and happy life for seniors has increased of late as the quality of life in
old age has become a hot issue. Moreover, the interest in health has led
industrial companies to concentrate on healthcare technology.
Healthcare robot technology is one of the biggest issues in the robotics
field, and many companies and institutes have sought to develop a
healthcare robot technology. The healthcare robot must have certain
abilities that would allow it to help a person mentally and/or
physically.To sense the High toxic chemicals Gases,Fire and PIR to
sense the Highly restricted areas in Human Beings .Finally to check the
labor health issues based on Heart beat,respiratory sensor etc..To store
the database AWS IOT plateform.

iv

க
அணிய ய ம ெதாட அ லாத ெச சா
ெதாழி ப க அவ ற எளிதான பய பா ம
பய பா ட பல ேவ ப ட ப த க பரவ ளன,
ேம ச ப தய ஆ களி ெதாழி ப
வள ச க ந ற ெதரிவ வைகய ப ேவ
பய பா க ேவகமாக அத கரி வ க றன. இ த
ேவைல ப ேவ ெதாழி ைற ைறகளி அணிய ய
ம ெதாட அ லாத ெச சா ெதாழி ப களி
பய பா ைட உ த ெச க ற .
இ த ஆ வ , ஆபேர ட க ஒ ச ற ந ரலா க ழ
ேதைவ இ லாம ந க ேநர த ெதாழி ைற
ேராேபா கைள எளிதாக க ப த எ பைத
ேநா கமாக ெகா ள .
வ , அற சா காதார ேராேபா ஒ த ய ைறைய
ஊ வ ம ஒ த ய தயாரி வழிவ
எ எத பா க ப க ற . ைமய வா ைக தர
ஒ டான ப ர ச ைனயாக மாற ளதா தவ க
ஆேரா க யமான ம மக ச யான வா ைக கான
ஆ வ ச ப காலமாக அத கரி ள . ேம ,
காதார த தான ஆ வ ெதாழி ைற ந வன கைள
காதார ெதாழி ப த கவன ெச த வழிவ த .
ெஹ ேக ேராேபா ெதாழி ப ேராேபா ைறய
மிக ெபரிய ச க களி ஒ றா , ேம பல
ந வன க ந வன க ெஹ ேக ேராேபா
ெதாழி ப ைத உ வா க ய ளன. ெஹ ேக
ேராேபா ஒ நப மன த யாக / அ ல உட
த யாக உதவ அ மத ச ல த ற கைள
 ெகா க ேவ . வா க , ெந ம PIR
ஆக ய அத க ந இரசாயன கைள உண த , மனித களி
மிக க ப த ப ட ப த கைள உண த . இ த யாக
இதய , வாச ெச சா ேபா றவ ற
அ பைடய ெதாழிலாள உட நல ப ர ச ைனகைள
சரிபா க. தர தள AWS IOT ப ேள ஃபா ைம ேசமி க.

vi

LIST OF FIGURES AND TABLES

S.NO FIG.NO TITLE PAGE NO

1 2.1 Module Description 21

2 3.1 Overall Architecture Diagram 25

3 3.2 Use Case Diagram 27

6 3.5 Data flow Diagram-0 32

7 3.6 Data flow Diagram-1 33

9 4.1 Sample Voice dataset 37

10 4.1 Parameters of voice dataset 39

11 4.2 Decision tree of voice dataset 41

12 4.3 Implementation of code in RStudio 42

13 4.4 Sample spiral drawing dataset 44

14 4.5 Classification by random forest 46

15 4.6 Working of Random forest classifier 47

16 4.7 Confusion matrix table 49

17 4.8 Implementation of code in Visual Studio 51

Code

18 4.9 Pattern of spiral drawing 52

19 A1 Output of clustering 59

20 A2 Decision tree output 59

21 A3 Accuracy of voice data 60

22 A4 Prediction output of spiral drawing dataset 60

vii
 CHAPTER 1

INTRODUCTION
 1. INTRODUCTION

1.1 SYSTEM OVERVIEW

In the dynamic landscape of industrial operations, the convergence of

technology and efficiency has become paramount. Robotic Process
Automation (RPA) stands tall as a transformative force, revolutionizing the
way industries conduct business. RPA integrates cutting-edge automation
technologies to streamline repetitive tasks, enhance operational agility, and
elevate productivity to unprecedented heights.
Industrial sectors worldwide are recognizing the transformative potential of
RPA initiatives. These initiatives aren’t just about automating routine tasks;
they embody a paradigm shift in operational methodologies. By deploying
software bots that mimic human actions across various processes,
industries are witnessing a seismic shift in how operations are conducted.
The rationale behind embracing RPA is clear: to optimize workflows, reduce
human error, and unleash the untapped potential of human resources. In
industries where precision, scalability, and speed are indispensable, RPA
emerges as a game-changer. From manufacturing to supply chain
management, from quality control to data analysis, RPA holds the promise
of amplifying efficiency while fostering innovation.
However, the realization of RPA initiatives in the industrial sector is not just
about adopting sophisticated software. It encompasses a strategic
rethinking of processes, a meticulous understanding of operational
nuances, and a collaborative approach among stakeholders. It requires a
fine balance between human expertise and the prowess of automated
systems.

1
1.2 PURPOSE

RPA initiatives aim to streamline and automate repetitive, rule-based tasks

within industrial processes. By deploying software bots to perform these
tasks, efficiency is significantly increased while reducing the time required
for completion. This allows human resources to focus on more complex
and strategic tasks that require creativity and decision-making.
Implementing RPA in industries often leads to cost savings by minimizing
human error, increasing accuracy, and reducing operational costs
associated with labor. Automation of routine tasks through RPA results in
cost-efficiency, contributing to overall financial savings.

1.3 SCOPE

The scope of RPA initiatives in the industrial sector is dynamic and

expansive, encompassing various functions and processes across
industries. It aims to bring about efficiency, accuracy, scalability,
compliance, and innovation, ultimately driving operational excellence and
competitive advantage in today's industrial landscape. RPA plays a pivotal
role in streamlining supply chain management, including order processing,
invoicing, shipment tracking, and inventory optimization. It facilitates
smoother coordination between different stakeholders, ensuring timely and
accurate deliveries while minimizing operational bottlenecks.

1.4 EXISTING SYSTEM

• There are mainly two existing types of gesture recognition methods,

2
 i.e., vision-based and accelerometer and/or gyroscope based.
• These have some limitations like ambient optical noise, slower
dynamic response, and relatively large data collections/processing of
vision-based method.
• Less accuracy.
• High maintaince
• High time consumption.

Disadvantages of existing system

• Analogue joysticks are used.

• Wired connection.

• Germs will be affected in analogue joysticks.

1.5 LITERATURE SURVEY

DESIGN AND DEVELOPMENT OF A MULTI-CONTROL GESTURE-

RECOGNITION BASED ROBOTIC ARM, SAKET SAMEER PRADHAN

2020

With the advent of automation technology, Human-Machine Interface (HMI)

has emerged as new trend in industry today. However, precision control in
such systems has been the main hindrance in path for further
improvements. This paper proposes a wireless communication HMI
framework to operate a human-resembling robotic arm that tracks and
follows the controller's arm movements. A 6 Degree-of-Freedom prosthetic
arm is designed on a 3D CAD software `SolidWorks' to enact human arm

3
activity. The end-effector of this setup is a mechanical human hand. This
model is constructed and then simulated in Simscape. Arduino boards and
IDE are utilized for instruction and data transfer.

IMPROVEMENTS OF A SIMPLE PIEZORESISTIVE ARRAY ARMBAND FOR

GESTURE RECOGNITION. DANIELE ESPOSITO; GAETANO DARIO
GARGIULO; CAITLIN POLLEY; GIOVANNI D’ADDIO; PAOLO BIFULCO

2020

This study presents a simple Human Machine Interface (HMI) for gesture
recognition purpose, based on a wireless piezoresistive armband. The
armband embeds three sensors based on Force Sensitive Resistors (FSRs)
applied on specific forearm muscles, which provide signals comparable to
the electromyography linear envelope. The system aims to recognize in real
-time some hand gestures, opportunely processing the force signals. The
HMI control system is based on Arduino platform and implements a Linear
Discriminant Analysis (LDA) classifier to perform real-time gesture
recognition. The HMI, by means of a Bluetooth module can wireless
connect to a computer and provide commands to custom graphical
interfaces or other applications as videogames.

MULTIPLE SCREEN CONTROL APPLICATION WITH FACIAL

RECOGNITIONS IN A MANUFACTURING CONTROL ROOM, ZHENGJIN
GUO; WILFRED KANG CHEE WONG; KYAW SETT MYO; WENG XIAN
CHOONG

2021

In the age of Industry 4.0, the operators in a manufacturing control room

4
require to work with digital content such as factory KPI dashboards, live
dashboards and controls on multiple displays. Manipulating and arranging
the displays and their layout with a user's face and hand gesture could be
more natural, automatic and interactive for the control room operators.
Therefore, a display control framework is developed in the Manufacturing
Intelligence Control Room (MICR) at the Advanced Remanufacturing and
Technology Centre (ARTC), using the open-source FaceNet facial
recognition and OpenPose hand feature recognition algorithms and
integrating with the display control system; Nerve Center from Mezzanine
system of Oblong Industries.

1.6 PROPOSED SYSTEM

• We using Robot setup based on RISC mechanism.

• We make 2 in 1 robots through the Industry.
• The proposed of the common interface technology is to develop
common processing modules and to support designs of robot bodies
from the healthcare point of view.
• The each labor to carry RF cards whenever they put the Card in Robot
to sense the Heart beat and Respiratory levels.
• Parallelly working Industry based also such as PIR,Flame,Toxic Gases
etc…

1.6.1 ADVANTAGES

 Enhanced Efficiency

 Cost Savings

5
  Improved Accuracy and Quality

 Scalability and Flexibility

 Enhanced Compliance and Reduced Risk

1.6.2 LIMITATIONS

1. Complexity of Implementation: Integrating RPA into existing industrial

systems and processes can be complex and time-consuming. Legacy
systems, diverse software environments, and heterogeneous data
formats might pose challenges in seamless integration.

2. Process Complexity and Variability: RPA is most effective in

automating rule-based, repetitive tasks. Processes involving complex
decision-making, unstructured data, or tasks requiring human
judgment can be challenging to automate using RPA alone.

1.7 ORGANISATION OF THE REPORT

The project report is organized as follows Chapter 1 deals with

Introduction, System Overview, Existing System, Proposed System and
Literature Survey of this project. The system requirements and software
requirements are discussed in Chapter 2. Chapter 3 analyzes the system
designs with module wise implementation. Chapter 4 discusses the
implementation details. Chapter 5 explains in detail about the testing.
Chapter 6 gives out the conclusion along with future enhancement.
Chapter 7 shows the screenshots and the source code of the project

6
Appendix and References are included.

7
 CHAPTER 2
SYSTEM REQUIREMENTS AND
SPECIFICATION

8
2.1 SYSTEM REQUIREMENTS AND SPECIFICATIO

2.1 .1 HARDWARE REQUIREMENTS

• Robotic setup

• Battery 12 v

• Gear motor

• Mq9

• Flame

• Pir

• Heart beat

• Respiratory

• Rfid reader

• Tags

• Iot moderm

2.2 SOFTWARE REQUIREMENTS

• Arduino IDE

• Embedded c

• Proteus design

9
2.2 SOFTWARE ENVIRONMENT

2.2.1 ARDUINO IDE

The Arduino Integrated Development Environment (IDE) is the software

environment used to write, compile, and upload code to Arduino-based
microcontroller boards. It provides a user-friendly interface for
programming Arduino devices. The Arduino IDE supports Windows, macOS,
and Linux operating systems. The Arduino IDE provides a simple and
accessible platform for both beginners and experienced developers to
create projects using Arduino boards. However, while it's user-friendly and
suitable for many applications, some advanced users may prefer
alternative IDEs or text editors that offer more advanced features,
debugging tools, and greater customization options.

2.2.2 FEATURES OF ARDUINO IDE:

 Text Editor: The IDE provides a simple text editor where users can write
and edit their Arduino sketches (programs). It includes syntax
highlighting and auto-indentation to aid in code readability.

 Sketch Management: Projects in Arduino are called "sketches." The IDE

allows users to manage multiple sketches simultaneously, providing
easy access to create, save, open, and organize these projects.

 Compiler: The IDE includes a built-in compiler that translates the written
code (in Arduino programming language, a variant of C/C++) into
machine-readable code (binary) executable by Arduino microcontroller
boards.

 Upload Tools: It features tools for uploading compiled sketches to

10
 Arduino boards via USB, allowing users to transfer the code from the
computer to the board for execution.

 Serial Monitor: Arduino IDE includes a Serial Monitor tool that enables
users to communicate with the Arduino board, display serial output
(debug information, sensor readings, etc.), and send/receive data
between the board and the computer.

 Library Manager: It offers a Library Manager that simplifies the process

of adding, updating, and managing libraries. These libraries contain pre-
written code for various sensors, modules, and functions, extending the
capabilities of the Arduino platform.

 Board Manager: Users can select the type of Arduino board they are
working with through the Board Manager. It provides a list of supported
boards and allows for easy selection and configuration.

 Examples and Tutorials: The IDE comes with a collection of example

codes and tutorials that serve as a starting point for beginners and
provide guidance on coding for different functionalities and components.

 Integrated Help: Arduino IDE offers integrated help, including tooltips

and contextual documentation, to assist users in understanding
functions, commands, and syntax while writing code.

 Debugging Tools (Limited): While basic debugging tools are available,

such as Serial Monitor for output display, Arduino IDE lacks advanced
debugging features found in more sophisticated IDEs used in
professional software development.

PROGRAMMING LANGUAGE:

11
EMBEDDED C

An embedded system is a special-purpose computer system

designed to perform one or a few dedicated functions, often with real-time
computing constraints. It is usually embedded as part of a complete device
including hardware and mechanical parts. In contrast, a general-purpose
computer, such as a personal computer, can do many different tasks
depending on programming.

FEATURES OF EMBEDDED C

 Portability: Embedded C code is designed to be portable across different

microcontrollers and embedded systems. It aims to write code that can
be easily transferred and executed on various hardware platforms
without major modifications.

 Efficiency and Speed: Embedded C focuses on efficiency and speed in

code execution. It optimizes code to work within the constraints of
limited memory, processing power, and resources typical of embedded
systems.

 Direct Hardware Access: It allows direct access to hardware registers

and peripherals, enabling developers to manipulate and control the
hardware components of embedded systems more efficiently.

 Low-Level Programming: Embedded C provides features for low-level

programming, including bit manipulation, memory management, and
pointer operations, essential for interacting with hardware at a lower
level.

12
 Interrupt Handling: It includes mechanisms to handle interrupts
efficiently. Embedded systems often rely on interrupt-driven
architectures to respond quickly to external events, and Embedded C
provides constructs to manage interrupts effectively.

 Fixed-Point Arithmetic: Embedded C supports fixed-point arithmetic,

allowing for precise control over numerical calculations, which is crucial
in embedded systems that require accurate calculations without the
overhead of floating-point arithmetic.

 Memory Management: It offers features for efficient memory

management, such as the use of memory-mapped I/O and optimizing
code to work within the limited memory available in embedded systems.

 Support for I/O Operations: Embedded C provides libraries and

constructs to perform input and output operations tailored for
embedded systems, such as controlling GPIO (General Purpose
Input/Output), communication interfaces (UART, SPI, I2C), and timers.

 Real-time Constraints: It considers real-time constraints and offers

constructs to handle real-time tasks and deadlines in applications where
timing is critical, such as in control systems or automotive applications.

 Vendor-Specific Extensions: Some embedded C implementations

include vendor-specific extensions and libraries to support unique
features of particular microcontrollers or embedded platforms.

2.3 Proteus design

13
Proteus is a widely used software tool for simulating and designing
electronic circuits and systems. While it's primarily focused on electronics
and microcontroller-based systems, it can be utilized to simulate and
design components or systems related to the realization of Robotic
Process Automation (RPA) initiatives in an industrial environment,
especially concerning control systems, sensors, and interfaces. While
Proteus doesn't directly simulate entire industrial processes or complete
RPA implementations, it serves as a valuable tool for simulating and
validating individual components, control systems, and interfaces
associated with RPA initiatives in an industrial context. Its simulation
capabilities aid in the design, testing, and validation phases, contributing to
the development of reliable and efficient RPA systems before actual
deployment in industrial environments. Proteus facilitates iterative
development by allowing designers and developers to prototype and refine
RPA-related systems in a virtual environment. It supports the testing of
different configurations and functionalities, enabling improvements and
optimizations before physical implementation. Proteus enables the
simulation of actuators or output devices, such as motors, servos, or relays.
Designers can simulate the response of these actuators based on the
signals received from the control system, allowing them to validate the
behavior of robotic mechanisms or automated processes.

FEATURES OF Proteus design:

In the context of realizing Robotic Process Automation (RPA) initiatives in

an industrial environment, Proteus Design Suite, a software for simulating
and designing electronic circuits and systems, can offer several features
and functionalities that can be utilized:

14
 Microcontroller Simulation: Proteus allows for the simulation of
microcontrollers commonly used in industrial automation systems.
Users can simulate and test the behavior of microcontroller-based
control systems that manage various aspects of RPA, such as robot
movement, sensor integration, and data processing.

 Virtual Prototyping: Designers can create virtual prototypes of RPA

systems within Proteus. This includes modeling and simulating robots,
sensors, actuators, and their interactions with control systems. It
enables engineers to visualize and test the functionality of the entire
RPA setup before physical implementation

 Sensor and Actuator Simulation: Proteus provides a library of electronic

components, including various sensors and actuators used in industrial
automation. Users can simulate the behavior of sensors (e.g., proximity
sensors, temperature sensors) and actuators (e.g., motors, relays) to
validate their functionality within the RPA setup.

 Electronic Circuits and Interface Design: Engineers can design and

simulate electronic circuits required for interfacing sensors, actuators,
and control systems in the RPA setup. It enables the testing of interface
circuits to ensure compatibility and proper functioning with the entire
system.

 Real-Time Monitoring and Debugging: Proteus allows for real-time

monitoring and debugging of simulated circuits and systems. Engineers
can observe signals, values, and interactions between components,
aiding in the identification and resolution of issues before physical
deployment.

15
 Control Algorithm Validation: The software supports the validation of
control algorithms used in RPA. Engineers can simulate these
algorithms to ensure proper functioning, accuracy, and efficiency in
controlling robotic movements and automated processes.

 Human-Machine Interface (HMI) Prototyping: Proteus enables the

design and simulation of HMIs or user interfaces that interact with RPA
systems. Users can create and visualize control panels or interfaces
through which operators can interact with and control the automated
processes.

 Simulation of Communication Protocols: For RPA systems that involve

communication between different devices or systems, Proteus allows
the simulation of communication protocols (e.g., UART, SPI, I2C) to
ensure seamless data exchange and integration.

Proteus Design Suite provides a comprehensive platform for simulating,

testing, and validating various components and systems involved in RPA
initiatives within industrial environments. By leveraging its simulation
capabilities, engineers can design, prototype, and optimize RPA systems
before physical implementation, thereby reducing development time and
potential risks associated with real-world deployment.

2.4 MODULE DESCRIPTION:

In the realm of Robotic Process Automation (RPA) initiatives within the

industrial sector, several key modules or components play crucial roles in
enabling and facilitating automation processes.Each of these modules
forms a vital part of the comprehensive RPA ecosystem within industrial
settings. Their integration and effective coordination contribute to the

16
successful realization and deployment of robotic process automation
initiatives, leading to increased efficiency, accuracy, and productivity in
industrial processes.These modules encompass various types of robotic
arms used in industrial automation. They come in different configurations
such as SCARA, articulated, delta, etc., capable of performing tasks like
pick-and-place, assembly, or material handling.

ARDUINO (ATMega328) MICROCONTROLLER

• It has 20 digital input/output pins

• 6 analog inputs, a 16 MHz crystal oscillator, a USB connection, a

power jack, an ICSP header, and a reset button.

• Microcontroller ATmega328

• Operating Voltage 5V

• Input Voltage (recommended) 7-12 V

ARDUINO UNO

17
 • Input Voltage (limits) 6-20 V

• Digital I/O Pins 14 (of which 6 provide PWM output)

• Analog Input Pins 6

• DC Current per I/O Pin 40 mA

• DC Current for 3.3V Pin 50 Ma

• Flash Memory 32 KB of which 0.5 KB used by bootloader

2.5 Training and Testing

Workflow Diagrams: Represent the sequential steps and processes

involved in training RPA systems. Use flowcharts or diagrams to illustrate
the data flow, decision points, and actions taken during the training phase.

Training Environment Setup: Images showing the setup of training

environments for robots or automated systems. This might include
physical setups, testing stations, or virtual environments where robots

18
undergo training.

Testing Scenarios: Illustrate different scenarios or use cases where the

RPA system undergoes testing. Show images of robots interacting with
various components, sensors, or performing tasks in a controlled testing
environment.

Testing Metrics and Results: Diagrams or graphs displaying testing metrics

and performance results. This could include accuracy rates, error logs, or
comparative charts before and after testing phases.

Fig 4.2 Training and Testing Flow Chart

2.6 ANALYTICAL MODEL

19
Based on the findings presented in the theoretical framework, and the
ambitions to describe how RPA-implementation may be facilitated, the
following analytical model (seen in Figure 3) was created with the intention
to categorize important themes on the subject to be used in our analysis.

figure 4.3 Analytical model

20
 CHAPTER 3
SYSTEM DESIGN

21
 3. SYSTEM DESIGN

3.1 SYSTEM ARCHITECTURE

Sensors and Data Acquisition:Sensors play a crucial role in collecting data

from the industrial environment. Images might include various types of
sensors such as proximity sensors, cameras, temperature sensors, etc.

Control and Processing Layer:This layer involves microcontrollers, PLCs, or

processing units that receive data from sensors, process it, and make
decisions. An image could represent a microcontroller unit or a PLC setup.

RPA Software Platform:The software platform orchestrates the automation

workflows, integrates components, and executes predefined tasks. An
image might represent an RPA software interface or a flowchart of the RPA
software's functionalities.

Robotics and Actuators: This layer involves the physical robots or robotic
arms that perform tasks based on commands received from the control
layer. Images might include robotic arms or actuators used in industrial
automation.

Human-Machine Interface (HMI): The HMI enables interaction between

operators and the RPA system. An image might represent an interface
where operators monitor or control the automated processes.

Communication and Networking: Networking components facilitate

communication between different layers of the system. Images could
include network diagrams or hardware such as routers, switches, or
communication protocols used in industrial automation.

22
 Figure 3.1- Overall Architecture diagram

3.2 UML DIAGRAM

Use case diagrams depict interactions between users (actors) and the
system to showcase various functionalities and actions the system can
perform. In an industrial RPA context, it can illustrate different user roles
interacting with the automation system.

Example: A use case diagram might display actors like "Operator," "System
Administrator," or "Robot" interacting with use cases such as "Start
Process," "Monitor System," or "Execute Task."

23
ADVANTAGES

● We know exactly what you are getting

● We will have lower development costs

● The software will behave as we expect it

● The right decisions are made before you are given poorly written
code
● It is very easy to understand

● Maintenance cost will be lower

● Working with a new developer will be easier

● Communication with programmers and outside contractors will be

more efficient
● Business process Includes a collection of task producing a specific
service for customers and is visualized with a flowchart as a
sequence of activities
● Logical and reusable software components

24
3.2.1 Use Case Diagram

Figure 3.2 Use Case Diagram

Figure 3.2 describes that use case diagram. Here the actors are user and
dataset. A use case diagram in the Unified Modeling Language is a type of
behavioral diagram defined by and created from a Use-case analysis. Its
purpose is to present a graphical overview of the functionality provided by a
system in terms of actor, their goals (represented as use cases), and any
dependencies between those use cases.

3.3 SYSTEM STUDY

25
3.3.1 Feasibility Study

A feasibility study for the realization of Robotic Process Automation (RPA)

initiatives in an industrial context involves assessing the viability,
practicality, and potential success of implementing RPA technology within
industrial processes. A thorough feasibility study provides valuable insights
into the potential success and challenges of implementing RPA initiatives
in an industrial environment. It helps stakeholders make informed
decisions, ensuring that the investment in RPA technology aligns with
business objectives and leads to tangible benefits.

3.3.2 Economical Feasibility

An economic feasibility study for Robotic Process Automation (RPA)

initiatives in an industrial context involves evaluating the financial viability,
costs, and potential returns associated with implementing RPA technology
within industrial processes.The economic feasibility study provides crucial
insights into the potential financial gains, costs, risks, and overall viability
of implementing RPA initiatives in industrial processes. It helps in making
informed decisions regarding resource allocation and investment in RPA
technology, ensuring that the expected financial benefits align with the
organization's objectives and justify the investment in automation.

3.3.3 Technical Feasibility

A technical feasibility study for implementing Robotic Process

Automation (RPA) initiatives in an industrial context involves assessing the
practicality, suitability, and technical requirements associated with
deploying RPA technology within industrial processes.The technical

26
feasibility study helps in assessing the readiness of industrial systems,
processes, and infrastructure for implementing RPA technology. It enables
stakeholders to make informed decisions regarding technical requirements,
readiness, and challenges associated with deploying RPA in an industrial
setting.

Social Feasibility

Conducting a social feasibility study for the realization of Robotic Process

Automation (RPA) initiatives in an industrial context involves assessing the
potential social impact, implications, and acceptance of implementing RPA
technology within the workforce and society. The social feasibility study
helps in understanding and addressing the social implications, concerns,
and acceptance factors associated with implementing RPA technology in
an industrial context. It facilitates proactive measures to mitigate
resistance, manage social impacts, and ensure that RPA initiatives align
with social values and expectations.

3.4 POWER SUPPLY CIRCUIT DIAGRAM:

27
 .

Electrical Transformers:

In industrial automation, electrical transformers play a crucial role in power

distribution and voltage regulation. They step up or step down voltage
levels to suit the requirements of different electrical components and
machinery used in automated systems, ensuring proper power supply to
the equipment.

Digital Transformation:

The term "transformer" can also be linked to the concept of digital

transformation within industrial settings. RPA initiatives often align with
digital transformation efforts, aiming to automate manual tasks, streamline
workflows, and leverage digital technologies for enhanced efficiency and
productivity.

Transformer Models in AI and Machine Learning:

Within the realm of AI and machine learning, a "transformer" refers to a

type of neural network architecture used in natural language processing
(NLP) and other AI applications. These transformer models, such as the

28
Transformer architecture developed by Google (used in models like BERT,
GPT), excel in sequence-to-sequence tasks and could potentially be applied
in optimizing RPA algorithms for language-based automation tasks or data
processing.

Process Transformation and Optimization:

Within RPA initiatives, the term "transformer" might also be used

metaphorically to signify the transformation and optimization of industrial
processes. RPA aims to transform manual or repetitive tasks into
automated, efficient processes, leading to productivity improvements and
operational transformation within industrial workflows.

Integration and Data Transformation:

In the context of data and system integration within RPA, a "transformer"

could refer to components or algorithms responsible for data
transformation, conversion, or normalization. These transformers might be
part of the RPA software ecosystem, ensuring seamless data exchange
and compatibility between different systems.

3.4.1 RECTIFIER:

A dc level obtained from a sinusoidal input can be improved 100%

using a process called full wave rectification. Here in our project for
full wave rectification we use bridge rectifier. From the basic bridge
configuration, we see that two diodes (say D2 & D3) are conducting
while the other two diodes (D1 & D4) are in off state during the period
t = 0 to T/2.Accordingly for the negative cycle of the input the
conducting diodes are D1 & D4. Thus the polarity across the load is

29
 the same.

3.4.2 DATA MODEL –Level 1

Figure 3.6 Data Flow Diagram –1

3.5 INPUT DESIGN

Input design for Robotic Process Automation (RPA) initiatives in industrial

settings involves defining how data and commands are received,
interpreted, and processed by the automated systems.By focusing on these
considerations during input design, RPA systems in industrial settings can
effectively receive, interpret, and process inputs to execute automated
tasks accurately and efficiently. This design phase lays the groundwork for

30
seamless integration and operation of RPA technology within industrial
workflows.

Objectives of Input Design

Data Source Identification: Identify and specify the sources from which
input data will be obtained. This could include various sources such as
databases, IoT devices, sensors, manual inputs, or external
applications/systems.

Data Collection Methods: Determine the methods and protocols for

collecting data from different sources. This might involve direct API
integrations, file imports/exports, web scraping, or manual data entry.

Data Formatting and Standardization: Standardize input data formats to

ensure consistency and compatibility across different systems and
processes. Implement data validation checks to ensure the accuracy and
integrity of incoming data.

Input Interface Design: Design user interfaces or interaction points for

providing inputs to the RPA systems. This might include GUIs (Graphical
User Interfaces), command-line interfaces, or integration with existing
applications.

3.6 OUTPUT DESIGN

Output design in the context of Robotic Process Automation (RPA)

initiatives in industrial settings involves defining how processed data,

31
results, and actions are presented, communicated, and utilized by the
automated systems or human stakeholders. By considering these aspects
during output design, RPA systems in industrial settings can effectively
present processed data, results, and notifications in a user-friendly,
informative manner, enhancing decision-making and operational efficiency.
This design phase ensures that the output generated by RPA initiatives
aligns with the needs and expectations of stakeholders within the industrial
environment.

Objectives of output design

o Output Format and Presentation: Determine the format and presentation

style for displaying outputs generated by the RPA systems. This might
include reports, dashboards, visualizations, or data summaries.

o Data Visualization and Reporting: Design visually intuitive

representations of processed data to aid comprehension. Use charts,
graphs, tables, and other visual elements to present key information
effectively.

o Output Delivery Mechanisms: Define how and where output data will be
delivered or accessed. This might involve email notifications, file exports,
integration with other systems, or displaying results on user interfaces.

o Customization and Personalization: Allow for customization options in

output designs to meet specific user preferences or stakeholder
requirements. Provide settings to tailor outputs based on user roles or
needs.

32
o Real-time Monitoring and Alerts: Implement mechanisms for real-time
monitoring of processes and outputs. Define alert systems to notify
stakeholders of critical events, errors, or completed tasks.

33
 CHAPTER 4

IMPLEMENTATION

34
 4. IMPLEMENTATION

4.1 SYSTEM OVERVIEW

This sensor contains a sensing element, mainly aluminium-oxide based

ceramic, coated with Tin dioxide, enclosed in a stainless steel mesh.
Sensing element has six connecting legs attached to it. Two leads are
responsible for heating the sensing element, the other four are used for
output signals. Oxygen gets adsorbed on the surface of sensing material
when it is heated in air at high temperature. Then donor electrons present
in tin oxide are attracted towards this oxygen, thus preventing the current
flow. When reducing gases are present, these oxygen atoms react with the
reducing gases thereby decreasing the surface density of the adsorbed
oxygen. Now current can flow through the sensor, which generated analog
voltage values.These voltage values are measured to know the
concentration of gas. Voltage values are higher when the concentration of
gas is high.

4.1.1 DATASET COLLECTION

Collecting a suitable dataset for Robotic Process Automation (RPA)

initiatives in an industrial context involves gathering structured, relevant,
and diverse data that represent the processes, tasks, or operations
targeted for automation. The collected dataset serves as the foundation for
training, validating, and refining RPA algorithms and models. A well-
prepared dataset significantly contributes to the success and efficiency of
RPA initiatives in industrial environments.

35
4.1.2 Training and Testing

Training and testing for Robotic Process Automation (RPA) initiatives in

industrial settings involve preparing and validating the automated
processes and algorithms before deploying them into operational
environments. Organizations can ensure that the RPA initiatives in
industrial settings undergo thorough training, testing, validation, and
refinement processes before full-scale deployment, leading to efficient and
effective automation within industrial workflows.

4.1.3 Recognition

Recognition of Robotic Process Automation (RPA) initiatives in an

industrial context involves acknowledging the significance, achievements,
and impact of deploying automation technologies within industrial
workflows.

4.2.1 Simplified analytical model

Simplified further, the logic of the analytical model of this thesis and
the above-described approach from understanding goals and intentions,
common issues and challenges to overcome to achieve these goals, and
finally looking at potential approaches to avoid/overcome issues and
generally facilitating implementation projects.

36
 Fig 4.2.1 Flow Process of analytical model

The first analytical component of ‘Potential benefits to realize and reason

for RPA usage’ is used to include fundamental drivers of RPA usage (to
enable analysis of what companies may want to achieve with the
implementation and hence what the most important potential issues to
mitigate are). The central part of the analytical model is found under the
horizontal divider, namely ‘common issues and challenges potentially
obstructing implementation’ and ‘implementation models and approaches
suggested by literature’ focusing the analytical efforts on identifying
problems potentially causing implementation issues, as well as to identify
best practices and approaches to avoid issues and facilitate
implementation. Through focusing onand applying the implementation
model suggested by Herm et al. (2020) we intend to 17 benchmark
previous implementation models with the approach used by the case
company. Inspired by Herm et al. (2020), large parts of the data-collection
and analysis will be structured around the models suggested phases of
implementation projects, and the suggested actions for each respective
phase.

4.2.2 The Internet of Things (IoT)

The Internet of Things (IoT) is the network of physical objects or "things"

embedded with electronics, software, sensors, and network connectivity,

37
which enables these objects to collect and exchange data. IoT allows
objects to be sensed and controlled remotely across existing network
infrastructure, creating opportunities for more direct integration between
the physical world and computer-based systems, and resulting in improved
efficiency, accuracy and economic benefit.

Thus IoT has evolved from the convergence of wireless technologies,

microelectromechanical systems (MEMS), microservices and the internet.
The convergence has helped tear down the silos between information
technology (IT) and operational technology (OT).

The internet of things, or IoT, is a system of interrelated computing devices,

mechanical and digital machines, objects, animals or people that are
provided with unique identifiers (UIDs) and the ability to transfer data over a
network without requiring human-to-human or human-to-computer
interaction.ontinued

38
 Fig 4.2.2 IOT in RPA

4.2.3 GYROSCOPES
A gyroscope is a device that uses Earth’s gravity to help determine
orientation. Gyro sensors are devices that sense angular velocity which is
the change in rotational angle per unit of time. Angular velocity is generally
expressed in deg/s (degrees per second). There are three basic types of
gyroscope Rotary (classical) gyroscopes, Vibrating Structure Gyroscope
and Optical Gyroscopes. Its design consists of a freely rotating disk called
a rotor, mounted onto a spinning axis in the centre of a larger and more
stable wheel. As the axis turns, the rotor remains stationary to indicate the
central gravitational pull, and thus which way is down. The gyroscope
maintains its level of effectiveness by being able to measure the rate of
rotation around a particular axis. When gauging the rate of rotation around
the roll axis of an aircraft, it identifies an actual value until the object
stabilizes out. Using the key principles of angular momentum, the
gyroscope helps indicate orientation. Gyroscopes are available that can
measure rotational velocity in 1, 2, or 3 directions. 3-axis gyroscopes are
often implemented with a 3-axis accelerometer to provide a full 6 degree-of
-freedom (DoF) motion tracking system. A gyroscope would be used in an
aircraft to help in indicating the rate of rotation around the aircraft roll axis.
As an aircraft rolls, the gyroscope will measure non-zero values until the
platform levels out, whereupon it would read a zero value to indicate the
direction of down.

39
 Fig 4.2.3 Gyroscope sensor

4.2.4 Performance Metrics

Performance metrics in Robotic Process Automation (RPA) initiatives
within an industrial context are crucial to measure the efficiency,
effectiveness, and impact of automation on industrial workflows. These
metrics help evaluate the success of RPA implementations and identify
areas for improvement. Here are some key performance metrics commonly
used in RPA initiatives in industrial settings:

 Process Cycle Time:Measure the time taken to complete a specific

process or task before and after RPA implementation. Reduction in
cycle time indicates improved efficiency.

 Throughput and Processing Speed:Assess the volume of tasks or

40
 transactions processed by RPA systems within a specific timeframe.
Higher throughput and faster processing speeds demonstrate
increased productivity.

 Error Rates and Accuracy:Track the frequency of errors or

inaccuracies in tasks performed by RPA. Reduced error rates indicate
improved accuracy and reliability.

 Resource Utilization:Measure the utilization of resources, such as

labor hours or machine capacity, before and after RPA
implementation. RPA should optimize resource usage and free up
human resources for higher-value tasks.

 Cost Savings and ROI:Calculate the cost savings achieved through

RPA by comparing the expenses incurred before and after
automation. Determine the Return on Investment (ROI) based on the
reduction in operational costs.

 Process Completion and Workload Distribution:Analyze the

distribution of workload across different processes or departments
after RPA implementation. Ensure balanced workloads and timely
completion of tasks.

 Compliance and Quality Metrics:Monitor adherence to compliance

standards and quality measures in processes automated by RPA.
Evaluate how automation impacts compliance and quality control
measures.

 Robot Productivity and Utilization:Assess the productivity of robots or

automated systems by tracking their active time, idle time, and

41
 utilization rates. Optimize robot utilization for maximum efficiency.

 Scalability and Flexibility:Measure the scalability and flexibility of RPA

solutions to handle increased workloads or adapt to changes in
process requirements. Evaluate how easily RPA systems
accommodate new tasks or process variations.

 Customer Satisfaction Metrics:Assess the impact of RPA on

customer satisfaction by monitoring response times, service delivery,
and accuracy of customer-facing processes. Improved customer
satisfaction can be an indirect indicator of RPA success.

 Operational Metrics Alignment:Ensure that RPA performance metrics

align with broader operational metrics and business goals to
demonstrate the contribution of RPA initiatives to organizational
objectives.

Regularly tracking and analyzing these performance metrics provide

insights into the effectiveness and impact of RPA initiatives in industrial
settings. It enables continuous improvement, optimization, and validation
of the value delivered through automation.

4.2.5 GSM Module:

GSM (Global System for Mobile Communications) can be utilized in

various ways to support or enhance automation processes:
 Remote Monitoring and Control:GSM technology allows remote

42
 monitoring and control of industrial processes via mobile
networks. RPA systems can leverage GSM-enabled devices to
monitor equipment status, collect data, or even trigger
automated actions from a remote location.
 Alerts and Notifications: Integrating GSM modules within RPA
systems enables real-time alerts and notifications. In case of
anomalies, GSM-based systems can send notifications to
relevant personnel or trigger predefined actions, ensuring
timely response to critical situations.
 Data Connectivity and Communication: GSM technology
provides a reliable means of data connectivity for RPA systems.
It allows RPA software or devices to communicate with central
servers, databases, or cloud platforms, facilitating seamless
data exchange and updates.
 IoT Integration: RPA initiatives in industrial automation often
involve integrating Internet of Things (IoT) devices. GSM
connectivity can enable communication between RPA-enabled
devices and a centralized control system, allowing for efficient
coordination and data transfer.
 Backup Communication Channel: GSM serves as a backup
communication channel for RPA systems in case primary
network connections (e.g., Wi-Fi or Ethernet) face disruptions.
This redundancy ensures continuity in data transmission and
operation.
 Asset Tracking and Management: GSM-based tracking
systems can be employed within RPA initiatives to track the

43
 movement and status of assets within an industrial
environment. RPA systems can automate processes based on
the location or condition of assets detected through GSM-
enabled tracking.
 Remote Access and Troubleshooting: RPA-enabled systems
integrated with GSM technology allow remote access and
troubleshooting. Personnel can remotely access RPA systems
to diagnose issues, perform maintenance, or make necessary
adjustments without physically being present at the industrial
site.
 Security and Access Control: GSM-based systems can
contribute to security measures within RPA implementations.
Access control systems leveraging GSM technology can
restrict unauthorized access to RPA-enabled devices or
systems.
 Integration of GSM technology with RPA initiatives in industrial
settings provides enhanced connectivity, remote access, and
efficient communication, contributing to improved automation
capabilities, streamlined processes, and better operational
control.

44
 Fig 4.2.5 GSM Module

4.2.6 Registers

The controller IC has two 8 bit registers, an instruction register (IR)

and a data register (DR). The IR stores the instruction codes and
address information for display data RAM (DD RAM) and character
generator RAM (CG RAM). The IR can be written, but not read by the
MPU.

The DR temporally stores data to be written to /read from the

45
 DD RAM or CG RAM. The data written to DR by the MPU, is
automatically written to the DD RAM or CG RAM as an internal
operation.

When an address code is written to IR, the data is automatically

transferred from the DD RAM or CG RAM to the DR. data transfer
between the MPU is then completed when the MPU reads the DR.
likewise, for the next MPU read of the DR, data in DD RAM or CG RAM
at the address is sent to the DR automatically. Similarly, for the MPU
write of the DR, the next DD RAM or CG RAM address is selected for
the write operation.

Fig 4.2.6 Registers

4.3 Working Methodology

The working methodology of Robotic Process Automation (RPA)

initiatives in industrial settings involves a systematic approach to
implement automation technologies to streamline and optimize
various industrial processes.

46
 Fig 4.3.1 Working Model

Identify Processes for Automation:

Identify and analyze the industrial processes that are suitable candidates
for automation. Focus on repetitive, rule-based tasks prone to human error
or requiring significant human intervention.

Define Objectives and Goals:

Set clear objectives and goals for RPA implementation, aligning them with

47
the strategic objectives of the industrial facility. Establish Key Performance
Indicators (KPIs) to measure the success of automation efforts.

Assessment and Process Analysis:

Conduct a thorough analysis of identified processes to understand their
workflows, dependencies, inputs, outputs, and decision points. Evaluate the
feasibility and potential benefits of automating these processes.

Fig 4.3.2 Work Flow Diagram

Data Collection and Preparation:

Collect relevant data required for RPA implementation. Ensure data
accuracy, quality, and availability. Cleanse and format the data to suit the
requirements of RPA algorithms and workflows.

RPA Tool Selection and Configuration:

Choose suitable RPA tools or software that align with the industrial
requirements. Configure the selected tools based on the specific
processes and tasks targeted for automation.

48
Development of Automation Workflows:
Develop RPA workflows, scripts, or bots based on the defined processes.
Design and build automation sequences that replicate human actions and
decision-making steps while adhering to defined rules and logic.

Testing and Validation:

Perform rigorous testing of the developed RPA workflows in controlled
environments. Validate the accuracy, efficiency, and reliability of
automation by running test scenarios, data validation, and error handling
tests.

Pilot Implementation:
Conduct a pilot implementation of RPA in a limited operational setting or
specific processes to assess real-world performance. Gather feedback,
make necessary adjustments, and fine-tune the automation workflows
based on pilot results.

Full-Scale Deployment:
Roll out the validated and refined RPA workflows for full-scale deployment
across the targeted industrial processes. Ensure proper integration with
existing systems, and provide necessary training to users.

Monitoring and Performance Tracking:

Establish monitoring mechanisms to track the performance of RPA
initiatives. Monitor key metrics, analyze data, and generate reports to

49
assess the impact on operational efficiency, cost savings, and other
predefined KPIs.

4.1.4 IMPLEMENTATION OF CODE

Arduino is a tool for making computers that can sense and control more
of the physical world than your desktop computer. It's an open-source
physical computing platform based on a simple microcontroller board,
and a development environment for writing software for the board.

Figure 4.8- Implementation of code in Arduino IDE

50
 CHAPTER 5

SYSTEM TESTING AND MAINTANANCE

51
 5. SYSTEM TESTING AND MAINTANANCE

5.1 TESTING
Testing is a set of activities that can be planned in advance and
conducted systematically. There are two types of testing according to their
behaviors,
1. Unconventional Testing
2. Conventional Testing

5.1.1 SOFTWARE TESTING

The test scenario is a detailed document of test cases that cover end to
end functionality of a software application in liner statements. The liner
statement is considered as a scenario. The test scenario is a high-level
classification of testable requirements. These requirements are grouped on
the basis of the functionality of a module and obtained from the use cases.
In the test scenario, there is a detailed testing process due to many
associated test cases. Before performing the test scenario, the tester has
to consider the test cases for each scenario. Documentation testing can
start at the very beginning of the software process and hence save large
amounts of money, since the earlier a defect is found the less it will cost to
be fixed. The most popular testing documentation files are test reports,
plans, and checklists. These documents are used to outline the team’s
workload and keep track of the process. Let’s take a look at the key
requirements for these files and see how they contribute to the process.
Test strategy. An outline of the full approach to product testing. As the
project moves along, developers, designers, product owners can come
back to the document and see if the actual performance corresponds to

52
the planned activities. Test data. The data that testers enter into the
software to verify certain features and their outputs. Examples of such data
can be fake user profiles, statistics, media content, similar to files that
would be uploaded by an end-user in a ready solution. Test plans. A file that
describes the strategy, resources, environment, limitations, and schedule of
the testing process. It’s the fullest testing document, essential for informed
planning. Such a document is distributed between team members and
shared with all stakeholders. Test scenarios. In scenarios, testers break
down the product’s functionality and interface by modules and provide real-
time status updates at all testing stages. A module can be described by a
single statement, or require hundreds of statuses,
depending on its size and scope.
● Testing can be done in the early phases of the software
development lifecycle when other modules may not be available
for integration.
● Fixing an issue in Unit Testing can fix many other issues
occurring in later development and testing stages.
● Cost of fixing a defect found in Unit Testing is very less than the
one found in the system or acceptance testing.
● Code coverage can be measured.
● Fewer bugs in the System and Acceptance testing.
● Code completeness can be demonstrated using unit tests. This
is more useful in the agile process. Testers don't get the
functional builds to test until integration is completed.
● Code completion cannot be justified by showing that you have
written and checked in the code. But running Unit tests can

53
 demonstrate code completeness.
● Expect robust design and development as developers write test
cases by understanding the specifications first.
● Easily identify who broke the build.
● Saves development time: Code completion may take more time
but due to decreased defect count overall development time
can be saved.

5.1.2 PURPOSE OF TESTING

There are two fundamental purposes of testing: verifying
procurement specifications and managing risk. First, testing is about
verifying that what was specified is what was delivered: it verifies that the
product (system) meets the functional, performance, design, and
implementation requirements identified in the procurement specifications.
Second, testing is about managing risk for both the acquiring agency and
the system’s vendor/developer/integrator. The testing program is used to
identify when the work has been “completed” so that the contract can be
closed, the vendor paid, and the system shifted by the agency into the
warranty and maintenance phase of the project.

5.1.3 CHARACTERISTICS OF TESTING:

There are several tests (such as unit and integration)
used for testing the software. Each test has its own characteristics. The
following points, however, should be noted.

● High probability of detecting errors: To detect maximum errors, the

54
 tester should understand the software thoroughly and try to find the
possible ways in which the software can fail. For example, in a
program to divide two numbers, the possible way in which the
program can fail is when 2 and 0 are given as inputs and 2 is to be
divided by 0. In this case, a set of tests should be developed that can
demonstrate an error in the division operator.

● No redundancy: Resources and testing time are limited in software

development process. Thus, it is not beneficial to develop several
tests, which have the same intended purpose. Every test should have
a distinct purpose.
● Choose the most appropriate test: There can be different tests that
have the same intent but due to certain limitations such as time and
resource constraint, only few of them are used. In such a case, the
tests, which are likely to find more number of errors, should be
considered.
● Moderate: A test is considered good if it is neither too simp1e, nor
too complex. Many tests can be combined to form one test case.
However this can increase the complexity and leave many errors
undetected. Hence, all tests should be performed separately.

5.2 TYPES OF TESTS

5.2.1 UNIT TESTING:
Unit testing involves the design of test cases that validates the
internal program logic is functioning properly and that program inputs

55
produce valid outputs. The decision branches and internal code flow
should be validated. It is the testing of individual software unit of the
application. It is done after the completion of an individual unit before
integration. This structural testing relies on knowledge of its construction
and is invasive. Unit tests perform basic tests at component level and test
a specific business process, application, and system configuration. Unit
tests ensure that each unique path of a business process performs
accurately to the documented specifications and contains clearly defined
inputs and expected results.

5.2.2 INTEGRATION TESTING

Integration Testing is a level of software testing where
individual units are combined and tested as a group. The purpose of this
level of testing is to expose faults in the interaction between integrated
units. Test drivers and test stubs are used to assist in Integration Testing.
Testing performed to expose defects in the interfaces and in the
interactions between integrated components or systems. See also
component integration testing, system integration testing.

COMPONENT INTEGRATION TESTING:

Testing performed to expose defects in the interfaces and interaction
between integrated components. System integration testing: Testing the
integration of systems and packages; testing interfaces to external
organizations (e.g. Electronic Data Interchange, Internet). Integration tests
determine if independently developed units of software work correctly
when they are connected to each other. The term has become blurred even

56
by the diffuse standards of the software industry, so I’ve been wary of
using it in my writing. In particular, many people assume integration tests
are necessarily broad in scope, while they can be more effectively done
with a narrower scope.

5.2.3 REGRESSION TESTING

Regression Testing is a type of testing that is done to
verify that a code change in the software does not impact the existing
functionality of the product. This is to make sure the product works fine
with new functionality, bug fixes or any change in the existing feature.
Previously executed test cases are re-executed in order to verify the impact
of change.Regression Testing is a Software Testing type in which test
cases are reexecuted in order to check whether the previous functionality
of the application is working fine and the new changes have not introduced
any new bugs. This test can be performed on a new build when there is a
significant change in the original functionality that too even in a single bug
fix. For regression testing to be effective, it needs to be seen as one part of

57
a comprehensive testing methodology that is costeffective and efficient
while still incorporating enough variety—such as well-designed frontend UI
automated tests alongside targeted unit testing, based on smart risk
prioritization—to prevent any aspects of your software applications from
going unchecked. These days, many Agile work environments employing
workflow practices such as XP (Extreme Programming), RUP (Rational
Unified Process), or Scrum appreciate regression testing as an essential
aspect of a dynamic, iterative development and deployment schedule.

5.2.4 SYSTEM TESTING

System Testing is a level of software testing where a complete
and integrated software is tested. The purpose of this test is to evaluate
the system’s compliance with the specified requirements. System Testing
means testing the system as a whole. All the modules/components are
integrated in order to verify if the system works as expected or not. System
Testing is done after Integration
Testing. This plays an important role in delivering a high-quality product.

58
System testing is a process of testing the entire system that is fully
functional, in order to ensure the system is bound to all the requirements
provided by the client in the form of the functional specification or system
specification documentation. In most cases, it is done next to the
Integration testing, as this testing should be covering the end-to-end
system’s actual routine. This type of testing requires a dedicated Test Plan
and other test documentation derived from the system specification
document that should cover both software and hardware requirements. By
this test, we uncover the errors. It ensures that all the system works as
expected. We check System performance and functionality to get a quality
product. System testing is nothing but testing the system as a whole. This
testing checks complete end-to-end scenario as per the customer’s point
of view. Functional and Non-Functional tests also done by System testing.
All things are done to maintain trust within the development that the
system is defect-free and bug-free. System testing is also intended to test
hardware/software requirements specifications. System testing is more of
a limited type of testing; it seeks to detect both defects within the “inter-

59
assemblages”.

60
 CHAPTER 6
CONCLUSION AND FUTURE WORK

61
 6. CONCLUSION AND FUTURE WORK

6.1 CONCLUSION

In conclusion, the realization of Robotic Process Automation (RPA)

initiatives in industrial settings represents a transformative journey
toward enhanced operational efficiency, increased productivity, and
improved competitiveness. Through the integration of automation
technologies and intelligent workflows, RPA brings about significant
advancements in industrial processes. In essence, the realization of
RPA initiatives in industrial settings signifies a paradigm shift
towards a more efficient, agile, and technologically advanced
industrial landscape. It marks the integration of automation as a
strategic asset driving operational excellence and facilitating
sustainable growth in today's dynamic industrial ecosystem.

6.2 FUTURE WORK:

The future work for the realization of Robotic Process Automation (RPA)
initiatives in industrial settings encompasses several areas aimed at
further enhancing automation capabilities, expanding application domains,
and ensuring sustained efficiency. The future work in RPA initiatives for
industrial settings involves ongoing innovation, adaptation to technological
advancements, and a strategic approach to leverage automation for
continued business growth, operational excellence, and positive societal
impact. Embracing eco-friendly automation strategies that focus on energy
efficiency, reduced waste, and sustainability in industrial processes,
contributing to environmentally conscious automation practices.
Facilitating collaboration between humans and robots in the workplace by

62
developing RPA systems that augment human capabilities rather than
replacing them. This involves designing interfaces and workflows for
effective human-robot interaction.

6.3 APPLICATIONS:

● Smart Manufacturing and Industry 4.0: Future RPA advancements will

drive the evolution of smart manufacturing, integrating automation
across production processes. RPA can facilitate predictive
maintenance, optimize inventory management, and enhance supply
chain logistics, contributing to the Industry 4.0 revolution.
● Predictive Maintenance and Asset Management: Advanced RPA
integrated with predictive analytics and IoT devices will enable
proactive maintenance schedules. This includes predicting
equipment failures, optimizing maintenance schedules, and
improving asset lifecycle management.
● Quality Control and Inspection: RPA advancements will enhance
quality control processes by automating inspection tasks with greater
precision using machine vision, reducing defects, and ensuring
product quality compliance.
● Supply Chain Optimization: Future RPA applications will optimize
supply chain operations by automating tasks such as order
processing, demand forecasting, warehouse management, and
logistics coordination, resulting in improved efficiency and reduced
lead times.
● Health and Safety Compliance: RPA can play a role in ensuring health
and safety compliance within industrial environments. It can
automate compliance checks, incident reporting, and safety protocol

63
adherence, contributing to a safer workplace.

CHAPTER 7
APPENDIX

64
OUTPUT

65
IMPLEMENTATION OF CODE

void setup() {

pinMode(5, OUTPUT);

pinMode(6, OUTPUT);

pinMode(4, OUTPUT);

pinMode(7, OUTPUT);

pinMode(trigPin, OUTPUT);

pinMode(echoPin, INPUT);

void loop() {

long duration, distance;

digitalWrite(trigPin,HIGH);

delayMicroseconds(1000);

digitalWrite(trigPin, LOW);

duration=pulseIn(echoPin, HIGH);

distance =(duration/2)/29.1;

66
delay(10);

if((distance>20))

digitalWrite(5,HIGH);

digitalWrite(4,LOW);

digitalWrite(7,HIGH);

digitalWrite(6,LOW);

else if(distance<20)

digitalWrite(5,LOW);

digitalWrite(4,HIGH);

digitalWrite(6,LOW);

digitalWrite(7,HIGH);

67
}

68
REFERENCES

69
REFERENCES

[1] Skraba A., Kolozvari A., Kofjac D. and Stojanovic R. "Wheelchair

maneuvering using leap motion controller and cloud based speech control:
Prototype realization". 4th Mediterranean Conference on Embedded
Computing (MECO2021). IEEExplore ScienceDirect.

[2] Yao D., Jiang M., Abulizi A. and You X. Decision-tree-based algorithm
for 3D sign classification 12th International Conference on Signal
Processing (ICSP2014). IEEExplore ScienceDirect. 19-23 October 2020.
Hangzhou, Pages: 1200 1204.

[3] Reference manual Leap Motion Sensor. (February 2021).

[4] Microsoft Kinect for Windows Programming Guide. (December 2022). [5]
Manual Asus Xtion Sensor. Developer Guide. (December 2021).

70