to be successful in the automation
journey
what do you think are the key
considerations for
selection of a solution provider
i'd like to answer this question in two
point of view
the one from our final customer and the
one from us
is a ui rpa solution partner usually
when our customer selects a solution
provider
they consider firstly the rent of the
product
for example the forester wave or in
china we also have some similar websites
who tells the rank of the local software
after picking up some rpa solutions from
the ranking panel
our customer will think about if the
software has any local support
or some reference in similar domain or
similar use cases
on the other words they think if the
solution is enough popular
of course for an international customer
they need to consider
their global decisions while for local
organization maybe they need to
obey some particular political rules
after first selection our customer
usually asks
a small project to prove the concept
they use this poc project to measure the
technical stress of the implementer
and finally of course the price is also
an important
point which brings many difficulty in
most of the situation and the from point
of view of
a solution partner because we are
technical people
our consideration will be more
professional in rp
perspective we have experience
on different rpa solutions when we
select a product
firstly it should be very easy to use
should be optimized
for our clients application so that
project risk and maintenance costs can
be reduced
it should have a large technical
community for example for your house we
can find solution from its own
marketplace
and also from the microsoft nugget
gallery
the last point is the solution provider
needs to have
a matured management methodology
for business analyst solution
architectures project management
support coe etc
when an editor such as ua pass have this
preparation it means they do care about
project
about the future and we can share our
difficulties with them
and we could align the technical tactics
together um so i think
the majority of providers get engaged at
the point of initial pilot
and i think it's easy it's almost um
too easy to be overly successful in a
pilot so
i think to answer that question properly
you have to step back a little bit
and and recognize intelligent automation
rpa
for what it really is it's an amazing
transformational lever
um so it's technology enabled
transformation so
to get good at it it's about being good
at change
and getting people ready to come on that
journey with you
that's really the crux of it so there's
some hygiene issues about being able to
implement technology make sure you
realize your business case but
this is a transformational lever so
um i think you know our prime minister
in australia made a really good analogy
the other day it was around
um something you know huge and very
serious around coburn it's about
building a bridge from a current state
to a future state and that's really what
a solution provider
helps you do it supports you and
provides some of that framework for a
bridge
so what does that mean practically i
think as i said there's some hygiene
issues it's around technical capability
and capacity and i think
you guys have done a great job of making
that fairly easy for people to recognize
certifications and skill sets within um
solution providers um but i would
encourage people to not just look at
that initial requirement
just to think about finding a provider
who's been on that full journey
and talk to their clients about what
they've done don't just talk about the
pilot talk about the full
life cycle and you're really looking for
a solution provider that can
offer services to complement your own
and work in with your own
across that entire life cycle from
identifying the right processes and
building the business case
all the way through to transitioning
into operational support and
being on the end of a phone when you
need it so i think it's
really important to recognize the fact
that you're not
outsourcing ownership of the process
and you really need the right and it's
different for everyone you need the
right level of capability
to own your solution so that means
different things for different
uh organizations some of our clients
they just need
a little bit of education and training
and to know that we're on the end of the
phone when they need it
um others take a more take more of our
managed service offerings so it really
is this sort of continuum
from a very light touch support all the
way through to
a managed service but it is about
enabling you to earn the end solution
you still earn those processes
um so i think in summary it's really
about considering the transformational
transformational nature of
the automation journey rather than just
the tech
yeah i think um there are some lingering
issues to compare
us with other inferior solutions but it
is
already well proven in the market that
uipath is the best solution ever
having that said now remaining question
our clients may ask is which provider
they should
choose to make a long story short it is
all about whether a provider
has the business domain knowledge or not
if they know the industry better and
have enough experience
in the market a provider is already
advantaged
in this battle from our numerous
project experiences the most painful and
time
consuming process in the rp journey is
to interview
the end users to understand as is
process and come up with pdd
of course to be processed included
with the process domain knowledge it
will smoothen out
the most severe wrinkles in the whole
process
and results in the better automation
that's what i'm thinking now about your
question
selecting the right solution provider is
half success
for an automation journey there are a
few points that you can take into
consideration
first thing first you better understand
what you really want to automate
and your automation journey as well the
second thing
is the ease of adaption of the solution
like for example uipath has a very good
ecosystem where a big community exists
for you to learn and share knowledge
with
and the tool should be easy to learn
with
very little technical challenges the
next point is the scalability a lot of
these
companies they start with a small
process to automate subsequently they go
and try automation in other departments
and other lines of business
because they've seen this the benefits
of automation very well
now that they come across technical
challenges like they would like to
automate
uh processors that touches the latest
technologies and the legacy technologies
they would want to use ai ml on
different technology different uh
latest technologies as well so the tool
should support all these things
like for example uipath has a fantastic
ecosystem
which can connect with all these
different technologies and help you with
that
and uh finally now these guys these days
you know like all these companies they
would want to
try hosting their uh softwares and
solutions in
the cloud so the solution that you
choose
should also be able to support your
cloud
the next thing is the security and the
governance you definitely need a
military gate
security secured system that can store
all your data
and the governance a very good framework
that can support the bots the process
and the people all together in one shot
then the pricing the pricing should be
supporting you from the different
journey that you take
on the automation process like the
initial days then subsequently whenever
you want to scale on all these things
and most importantly it should provide
you a very good return on investment
that's one of the key aspects and the
success reasons for
ui path across many of our existing
customers as well
finally having a very good
implementation partner is also very
very important uipath has a fantastic
partner ecosystem so they give a hand on
hand
support in making sure the partners have
a very good
knowledge of the solution and the
implementation they go about it
personally in kgs we've been working
with uipath for the last few years
and together we have grown together in
the region
where we have established ourselves in
many of these countries
including being a diamond partner in one
of the countries here
we have automated hundreds of processors
in the region as part of kicking off the
automation journey
if you're wanting to get a business case
approved what do you believe
are the best processes to nominate for
automation
i think this question had been perfectly
answered
by the process diagnostic course from
uipath training
the main idea is that the process should
have less development cost
and with high benefits in order to have
a relative small cost
the process should be rule-based i
usually tell to my clients
that rpa solution can be considered as
the arm of the artificial intelligence
while the ai itself is the brain the
technology today is not enough mature
to build the whole brain so that's why
we
have to uh build rp solutions
of which the objective is to build the
arm alone
and we do need to define clear rules for
actions
as an alternative solution of the brain
by
understanding this limitation it can be
easily interpreted
that each piece of room has to be hunted
so it has its cost of analysis and of
the development
to reduce this cost it will be easier if
the process
is basing on a stable system instead of
basing on a system which has a lot of
change
for example an internal system such as
erp
is usually more stable than an external
system
such as timor ebay etc
it will also be easier to build process
if it has less steps
less and no scenarios less variety of
data or less
applications talking about benefits
obviously the process needs to be
need to be helpful to people for saving
times
so a simple rule based process
with higher repetitive usage will be
easily targeted
as a first choice of rpa
when we go deeper the benefits is not
only for human workload saving
it could also come from other
perspective
such as risk reducing a fixed arche
process is usually more stable than
human actions
another important benefit is that the
rpa process
can also bring new business
opportunities we need to be more
innovative some of automation scenario
cannot be
done in the past will not be possible
with new technology
of uipath it changes a little bit over
time as well so i think
initially the processes you look at and
pilot in early stages of
an automation rollout tend to focus more
on the
operational efficiency and then if you
look at organizations that are further
on the journey
there there's more acceptance of the
other benefits that come from
automation so reduction in error
increased speed
um happier people things like that so i
think certainly
you're sort of asking that question
about how do i get business cases up and
and through
um you're likely earlier on the journey
and focused on those operational
efficiency cases
and so very usually measured
um in fte and associated cost
and um i think when you're laying out so
rather than sort of calling out specific
processes because
so much depends on the organization so
one organization's
a source of pride is another one's
burning bridge and so if i start calling
out individual processes it can mean
very different things to different
businesses
but i would say there's three things
that you know i would look at and
consider
so number one um have a look at
your organization's strategy and
there'll be a corporate strategy maybe
that's interpreted
uh locally or maybe you're a small
organization
but try to prioritize the processes that
align
to your strategic goals so that may be
increasing the voice of the customer or
turnaround time
or reduction of risk or whatever it may
be
so try to pick those processes that
align with your your border strategy
i would say secondly that cases that are
supported by
data are far more likely to be approved
and so that can be that's great if
you've got operational data and again
some of the ui path technology
is really helping support that um and
i'd encourage anyone to have a look at
that but there's other ways of getting
that data and having a data driven
discussion rather than just an anecdotal
one
so uh certainly one of our um clients at
the moment we are looking
at um looking at cost for casuals so
we're looking at the areas that have
these high
peaks in demand and we're looking to
help support them
and with um automation
uh the third thing i would say uh
you don't just want to create benefit
you want realizable benefits
so if you really want to get your
business goes through
and don't get knocked back it's not just
about benefit creation how are you
actually going to get the benefit so
quite often people will talk about
we just move people into higher value
activities it's almost become a
throwaway state so
i would encourage people to think about
well
what we're going to move them on to
higher value activities what exactly are
we going to be doing
and what support do they need and what
things do we need to put in place
to let them add that position so
training tools whatever it may be think
it all the way through not just from
benefit creation
but all the way through to benefit
realization and and if that is a cost
there if that is about taking people
from one area of business moving to
another or out of the organization
again there's a huge amount of diligence
and thought that needs to go into that
and
mitigating the risk of ip leaving the
business and
the entire human lens on that as well so
it's not just a throwaway thing creating
benefits part a
part b is actually realizing
well oh it's a really difficult question
most cases i prefer to nominate
processes that is roi proven
with process re-engineering or without
process re-engineering
often the process re-engineering may end
up with a failure
so in the early stage of rpa journey
coe may be on the heavy fire of failing
a project
so in the early stage i suggest simple
and straightforward
ones that is easy and roi
proven right
the processes that you would ideally
want to nominate
are the candidate processes that you
want to choose
basically is based on a simple thumb
rule like
one the process should be very high in
volume it should be repetitive in nature
and it should be mature and stable and
finally it should be some
rule based so it would be easy to
automate the different steps involved in
that
um basically you would find these
processes predominantly in the hr
services
or in the finance and accounting
department it services
and maybe in supply chain also so
however i said
all these processes for the initial days
of your automation journey
subsequently down the line that's when
you would really want to automate
more complex processes including
cognitive solutions
cognitive processes where you can put in
the
bring in the hyper automation which is
what is happening in the industry now
so the hyper automation with hyper
automation what you get along
is an ecosystem of various different
tools
and solutions which can support you to
automate all these complex processes
where you have can definitely bigger
benefits
and bring in lot of advantages
by automating those processes