We have many solutions, like Data Rebate, for example. We need to compare this information, regardless of the information that we save in the Experian databases, against information in government websites, in order to ensure that everything is up to date. The information of the company address, for example, took around 47 minutes to compare, while using RPA it now takes around 10 minutes for each one.
Automation Anywhere has improved our company a lot, because we are currently trying to leverage automation in different departments to allow employees to work where more human intervention is needed. The SLA of some tasks that we need to deliver to some clients has improved greatly. The productivity has increased a lot in my organization.
Interaction with websites is the feature most valuable to us. Most of the systems are web-based, so using a very accurate web-based identification like objects, extracting information from tables inside websites, and checking websites differences using MetaBots is very helpful with Internet Explorer. This allows us to separate the functionality by using an object where we store all the assets, or screenshots of the webpages, instead of changing the logic of a website. It's very useful.
Ease of use of this solution depends on how complete you want to go. From my perspective as a system engineer, the curve was very, very low because you have a lot of understanding about technology. On the other hand, we have examples of people that the curve was a little bit high, but coaching them to improve their knowledge about Automation Anywhere and how friendly the interface is right now is very useful.
MetaBots and Control Room may have some room for improvement.
The bot store has a large amount of pre-designed bots. I made some tests related to language, browser scene, and image recognition. It was very nice.
I would rate Automation Anywhere as seven out of ten. There are a lot of things that need to be improved, especially related to the Control Room, but you can develop and scale with this tool very, very fast.
Our primary use case is banking/financial. Processes we have automated include loans, ledgers, mortgage loans, and even some of the record management systems.
In some of our use cases, people were spending more than three hours per day just generating reports. And then we created an automation for this and it reduced the time to 30 minutes. It improves employee productivity so they can use their time in other areas.
I like the way it works with structured data in the back office and the way it does repetitive work.
In terms of ease of use for developers, we're able to create reusable components. We don't want people to have to rebuild things from scratch. In this way, developers can take the reusable components and complete their development processes more quickly.
The bot creation process is pretty straightforward. Anyone can go in and learn it easily, and then they can build a bot. I like it.
When it comes to integrating the solution with other applications, there are some challenges. For some third-party solutions, there are no direct interconnections. For example, there were no direct connections with SAP systems. So, we had to create connectivity between Automation Anywhere and some third-party solutions. They have now improved that situation a lot and we can connect SAP and other systems as well.
If they want to sustain their position in the market, they have to be flexible, working on how we can integrate with third-parties, working on a machine-learning product. People are expecting that and it would be really helpful.
From the IQ Bot perspective, frankly speaking, they still have to improve a lot. I got IQ Bot training in San Jose. My expectation from a straight, technical, architectural point of view was that I would be able to create my own algorithm and integrate it. But with IQ Bot, I am not able to integrate anything. It is already well-defined, so I have to use that particular option only. I know I can not go with any other machine-learning platform. I hope they will be coming out with version 12 where we can integrate it with Python algorithms and other stuff. It might only be in the future, it might only be on the roadmap. But as of now, it is lacking a lot in that area. We are expecting, for most of the documentation, things like tags, that there would be a checkbox option. That's lacking in IQ Bot.
The stability has increased a lot. When we started with version 10.2, there was a lot of instability. There was no way we could keep the bots active, there were scenarios where it became disconnected. There is also the code deployment perspective and a lot of other angles. People are always only thinking from the business perspective, but as a technical architect, I think about operational effectiveness and how they can improve the product's maturity.
The stability has improved a lot.
However, when upgrading, they changed their internal architecture. They moved it to a JT Java platform. When moving, some of the existing features did not work in the new version. It might be that they have to improve their regression testing to improve clients' satisfaction. It can happen that what is running in production currently, if I move to a new version, suddenly is not working tomorrow. People are not happy with that and say, "I want to roll back to the older version." They are not able to use the new features.
When moving to a new version, they have to think about what features people are using and what kind of impact there will be. Small business users will be fine, those who have ten bots or 15 bots. But there are organizations like mine that have around 700 to 1,000 bots, and that makes changes very difficult to handle. It could be that 10,000 tasks are using something and if that thing is changed it will be hard to update. I might have to spend a year on that. People will never accept that.
Scalability-wise, they have increased it a lot, based on the clustering method. As a technical architect, I'm going with always-on production and data centers. That means that if any data center goes down - there is a natural disaster or something else that happens - how do you make it such that you can bring up another data center? I'm coming up with a design for that based on the latest version, version 11.
The initial setup is very simple. It's Windows-based and it's a straightforward installation. We used to say they need to come up with a silent installation option, with the previous version. But now, with version 11, they have introduced, even at the server level, a silent installation. That means we can make it automated instead of manually installing it.
We measure the ROI of automated processes by how much of a benefit we're getting from it. We look at how much time it takes and how many robots we're using and we include the licensing and operations costs. Finally, we take into account how much faster the performance of the bot is, compared to how long it took to do the process before automation.
We have saved time and money, but when people think of going with RPA they cannot expect that they will immediately see ROI. They have to sustain and increase the RPA options. They will have to spend a minimum of one or two years increasing their use cases for automation. Then they will see a good ROI. They should not expect, within three months, to say, "Hey, I have automated, where is the ROI?"
All organizations have a certain strategy or checklist. In this case, management will think first about licensing cost, about the total cost of investment. After that, they will think about the product's features and functionality. They will also look at support. They will consider the use cases, the current processes they have identified already, and based on all that they will decide whether to go with Automation Anywhere or another product.
In terms of our bot creation process, people come to me and say, "I have a process. How do we automate it?" We need to understand if it's a cognitive use case or a straightforward use case. If it's straightforward, we tell them we'll use this product and build it for them with four to six weeks of development. Then it can go to production. If it's cognitive, then we really need to understand it better. We need to use a third-party product, like Kofax or maybe an IQ Bot if it is fit for the scenario. Based on that, it takes some time and then we'll move it to production.
We have a process architecture review committee where we review all the processes. We cannot blindly go forward with all the processes that have scope for automation because it's all licensing cost. We need to think about whether we can automate a given process with any other IT automation solution, like scripting or macros. If that is not possible then we have a fit for RPA. Then we have to go through our checklist, walk through the use cases, and look at the percentage of the automation scope: Is it a 100 percent automation scope or 80 percent or 20 percent? We need to to know if there is any manual validation or manual intervention required and how that is handled.
Initially, we failed with the Citrix automation where we have a lot of use cases. We ran into a lot of limitations with Automation Anywhere in version 10.5. But with version 11, they have AI Sense which we can use for Citrix applications. We are currently exploring this option.
I have taken courses at the Automation Anywhere University and I have advanced professional certification from Automation Anywhere, which I completed for version 10.5. I'm also doing it for version 11. I also have an official certificate for IQ Bots.
At the moment, for us, everything is on-premise. We're not ready to go with cloud. So we have to build our own platform. We have to build our own bots.
I would rate this solution at seven out of ten. They have to improve on the product's maturity level. When they are introducing new versions, they have to conserve the existing commands and features, so that they work when we move to the new version. And they also have to come up with more flexibility, so their solution can integrate with our scripting and our own algorithms. That will make it easy to convince our business areas to increase the adoption of RPA.
I have implemented it for multiple use cases.
One of the use cases that it was implemented for is filling out timesheets from the managers. There are certain managers who have to allocate hours to multiple employees, around 40 to 45 employees. Each month, they decided how much time that they will allocate to each of resource. Using a robot, they can automatically fill in the timesheet on Zoho, which is the timesheet system that the company uses.
Another use case was that we used to have certain lists of vendors who billed every month. They had a specific format to their invoices. Using bots to read through those invoices, we were able to pick up relevant data and enter it into the finance systems.
It has improved the efficiency and reliability of the data in the systems. A user is always going to make errors. By adopting robots, we are able to have more accurate processes, plus time is saved.
It saves time for the people who operate it. This particular bot is an attended automation bot, and before running the bot, the manager tweaks some of the values which are important. Overall, this will save the managers time during their processes and create value.
It is not always required to have a technical background. It is not necessary to know programming languages. This makes it easier for a business user to create his own bots.
It is pretty stable on a day-by-day basis. It is much better than when I started working on RPA solutions three years ago.
Manually, I have worked on adding/scaling bots, but I need to work on cloud availability, possibly discussing scaling with cloud providers, like AWS.
For different processes, the scaling time period is different. For some processes, we could develop bots in two weeks, then go to production with one or two bots. For other processes, it could take three months or more. It varies based on the process.
We did not use another solution previously.
The setup process is not easy compared to the competition, and this can be a barrier to entry.
We implemented it ourselves.
The time savings depends on the process. By using a bot, we have saved 40 to 70 percent. If the process uses unattended automation, it saves a lot of time.
Currently, I don't think that we have saved money with this solution.
When I started working on it, it was difficult to obtain a trial version (barrier to entry). Now, they have a Community Edition, which may make it easy to get started.
We looked into UiPath, Blue Prism, and Automation Anywhere. Our client was interested in Automation Anywhere.
UiPath has an easier setup process.
I recently took a look at the Bot Store, and it's a good initiative. I haven't started using it. I downloaded a couple of the bots, and hopefully soon, I will try to use some of them in a production environment.
The real beauty of robotic automation is when it is running from the back-end (unattended).
I have worked for two companies in the past who have used Automation Anywhere. Both primary use cases have fallen under finance and accounting, with a lot of finance and accounting based functions primarily for data processing:
Integrating this solution with other application has been good for the most part. A lot of the issues that I have are related to the actual applications than with Automation Anywhere. Any additional functionality which comes out in regards to integrating it better with more widely used applications, like Salesforce, Oracle, or Workday, is definitely beneficial and helpful at the end of the day.
I have been hearing great stuff in terms of upping the product's cognitive game. Anything that can be done to work with unstructured data sets would be helpful, like increasing the subjectivity of bots, and moving away from solely rules based processes to anything which actually requires subjective judgment. If Automation Anywhere could code that into the bot design and framework, having it sort of act like a human, that would be helpful.
Anything that can be done to increase the stability from a system standpoint in regards to large-scale systems, which are being used by a number of applications, e.g., Salesforce or Workday. This would help us, as well.
Automation Anywhere should work to continue maintaining its ease of use.
One to three years.
My current and previous companies have had stability issues.
I started on version 11 of Automation Anywhere, then when I joined a new company, they used version 10. Therefore, I have seen both versions. With version 11, some of the development stuff was a bit clunky in terms of the tasks that we were performing. They didn't perform as expected, or perform properly, when we were developing the bot. Then, once we deployed it into production, the bot would run for a specific process and work properly about 10 times, but on the eleventh time, it would break. It was always random. Nothing had changed at all, in regards to our system, architecture, or infrastructure.
On version 10, things had been a bit more stable. We made sure that we build code which effectively captures all use cases and exceptions, but stability is key. When you're building automated solutions using bots, people are already skeptical and hesitant to adopt them. Anything you can do to improve the stability is definitely helpful. Ultimately, it depends on what your goal with RPA is. If you're using RPA as a stop-gap to build large-scale system integrations, then it's very helpful. If you're using it as a be all, end all, then stability is your number one concern.
The product is definitely scalable. A lot of it will depend solely on the architecture of the organization who is implementing it. If you are using on-premise servers, it is much harder to scale up versus if you are using cloud-based architecture. Automation Anywhere provides the tools and expertise to make it scalable.
At the previous company that I was with, we had a pilot in September 2017 with approximately 20 bots. Then, in production, it took nine to ten months. With the organization that I'm currently with their process took a little longer, but they were standing up their COE initially. So, they went from pilot to about 30 bots in production. This took roughly a year and a half to two years.
With regards to process, there is a lot involved. If you want to have a successful RPA and Automation Anywhere implementation at the ground level, you need to lay the foundation and the framework. Therefore, you need to build your center of excellence, and make sure you have dedicated people who will focus on whatever their role is: People related to support, governance, development, architecture, oversight (who will work with your security teams to get your reviews done), and IT personnel (who will provision servers and licenses and do Control Room administration). There is a lot involved to take it from inception to a successful program.
The technical support has been helpful from what I've used. Initially, when we were exploring solutions and using Automation Anywhere, as a vendor, their technical support seemed to be lacking a bit. It seems like in the last few months or year, they have been stepping up their game, in this regard. They are very prompt to follow up with issues and want to make sure issues are thoroughly resolved before they close tickets and move on, which has been helpful.
At both companies, we never used a different solution before Automation Anywhere.
We had individuals working at the companies who spent years going to school, but could not necessarily download reports nor input data into spreadsheets, and this was something that could be easily automated. We wanted to free up users and people to perform higher value-add activities, exercising analytical and critical thinking, as opposed to being cogs in the machine.
Certain aspects of the initial setup were complex, but that's a given when you're talking about technical architecture and getting the infrastructure you need in place for a successful rollout. Though, some aspects of the initial setup were simpler.
The simpler aspects are designating roles for people based on what it is they want to provide to the center of excellence for RPA and how they see their fit in the organization. The more complex piece of it is working with all the stakeholders, internally and externally, to get all the infrastructure in place that you need in order to develop, deploy, test, and run bots in production.
For deployment, at the first company that I worked for, that was all in-house, as we were deploying our own bots. The architecture, development, and deployment were all in-house.
At the company that I currently work for, we have a managed services company who does development for us, and we still handle deployments. It is more like a segregation of duties, where we handle the full deployment on the end once code is ready for production.
We have seen ROI, otherwise we would have stopped using the product.
At a base level, for ROI, we equate a dollar value out to the process owner, or the business user, and multiply that out by the number of hours being saved. However, that is really base level. There are other factors involved that will help:
On the shortlist were some of the largest players in the industry: Blue Prism, UiPath, and Automation Anywhere. This was in 2017, when I was involved with the PoC. We chose Automation Anywhere because of ease of use and overall functionality. I think the cost was also a big factor, but I don't have much insight into it.
People seem to be a bit skeptical about the cognitive document processing. I don't know if they see the power that IQ Bot provides relative to other world leading software products, such as ABBYY, which is another big OCR technology that I have used. If Automation Anywhere is stepping up its game in the cognitive aspect, this will help guide adoption in the future.
Consider all relevant factors before making a decision on a provider. Don't just randomly decide to choose one provider over another. At the end of the day, it comes down to what you are trying to achieve by implementing an RPA solution, what you're looking for in an RPA service provider, and who is willing to best address that and meet the needs of what it is you're hoping to achieve. You should consider RPA as a solution, and there are a whole host of other automation software solutions across the spectrum, as well, which are relevant for different things, but RPA has its place in any organization. Just know exactly what it is you are hoping to achieve. Based on that, you'll be able to find the best provider for you.
For developers, it's relatively easy to use. I know some developers are hesitant to use it because they come from traditional technical backgrounds. The product is counter-intuitive to everything that they have studied. If they studied computer science, they're really reticent towards something that can just automate what they learned. For someone with a nontechnical background, it's relatively easy to use and easy to build tests out. It takes a bit of effort to master and build sustainable solutions, but it is easy to use from a development perspective.
I have not been able to take courses in Automation Anywhere University for the new platform. I started using Automation Anywhere back in 2017, and the Automation Anywhere University wasn't available. There was another platform, at that time. We did the online training center for it, and it had eight different sections. Back then, it was a little clunky. You had to go through one section and complete it before moving on another. From what I've heard about Automation Anywhere University, it's much better and more functional. I haven't had the opportunity to use it yet, since I haven't really needed to use it. However, I do plan on exploring it in the future.
I don't use Citrix automation.
We use it to augment our staff and remove some of the manual processes in our business.
Our team, consists of two college kids who are doing almost all the work, along with a couple of business people to help teach them what is going on. The ease of use has been pretty simple, or they would not have been able to catch onto it so quickly.
With the new regulation on China tariffs, we were hit with a regulation that we weren't prepared to take on. By using a few bots, we were able to satisfy the requirements for that regulation without going into programs and making changes.
We have automated our China tariffs, some invoicing stuff, a lot of processes for finance, and some mundane closing tasks.
We have had a lot of great success with attended automation. The business has taken a hold and embraced it. So, we're very excited about it.
I would like more with OCR and data capture. We are partnering with IBM to help bridge this gap, but Automation Anywhere should continue to expand on their product line and provide these capabilities, as well.
The installation and setup for the bot runners and bot creators need improvement. The installation and setup for the control room is also a difficult task. Therefore, improving the ease of implementation would help out a lot.
We've not had any problems with the platform going down. Right now, it's been very stable.
We're still pretty small, so we haven't had a need to scale out too much.
We have seen the roadmap for scaling out, and it doesn't look to be too difficult. So, we should& have a problem with it.
We have only had the tool for about eight months. From start to finish, we have put over a dozen bots in place, some of which are highly complex and took a lot of weeks to properly deploy.
The tech support for Automation Anywhere has been really good, so far. We haven't had to call them very much, but when we have, we have received a good response.
This was our first bot solution. We did do our research and looked to our partners to see what they were using, then created a shortlist. This product was on everyone's shortlist. Also, they partner well with IBM, and we have partnered with IBM for years. This made it very attractive and was the key selling point.
The initial setup was pretty complex. Everyone who offers this platform is still trying to find the right tools which go with it. Without an integrator, we would have had a lot of difficulty getting it set up ourselves.
As this product matures, it will continue to get easier to set up.
We used an integrator (BP3) for the deployment. They've been tremendous to work with, satisfying all of our needs.
We measure our ROI mostly by time saved, from a real person doing a task versus a bot. In some cases, we have been able to recoup revenue because processes weren't being followed correctly. Because the bot was doing the task the same way every time, we have recouped some revenue that we had lost in the past.
We save 34,000 hours of time per year and have recouped up to $6000 in lost revenue.
We have a three-year contract with Automation Anywhere.
UiPath was also on our shortlist.
Every piece of software has its goods and bads. For your organization, you have to ensure that the goods outweigh the bads for your use case. This solution has been great for our company in almost every way possible. Obviously, we made a good choice. Therefore, I would recommend taking a good, hard look at Automation Anywhere as your bot platform.
With the latest version, I know they have improved the UI. That will already be a big help,
Return of investment has been pretty easy, so it has not been a problem with getting funding for this solution. Our executive team was immediately involved, where I know with most IT projects, they really don't care until they see the output. They had done their research, as well. So, they were really excited for us to take on this endeavor.
Our primary use case is to automate all the back-end processes, which are accounts receivables, accounts payable, automatic settlement, and a lot of processes in the supply chains. Afterwards, we move onto the front-end transactions.
It provides, not only hard benefits, but also soft benefits. This means to leave the human capital (which they are required to do); leave the human mind free of all voluminous repetitive tasks. Let the workers do the work that they are intended to do, which is thinking. The bot can work for you. There is no comparison to the human mind.
The customer engagement is really deep, and they work with the “gemba”. They work with operations very closely. I also believe they have a good product roadmap.
I’ve already mentioned the future of our human mind and thinking are limited. We only think in arithmetical progression, not GP. So, I have no answer for this.
When you scale up, like on Proof of Value (PoV), it’s okay. You can have one full, dedicated person working on the site. However, when you scale up, and imagine there are 150 people including bots in an organization of 20,000 people, then they need to be loved and cared for (every single one of them). They will need much more support, because it is a new thing and it’ll never fail because of productive partners. It will fail if people on the “gemba” don’t adopt it.
We are in the Proof of Value stage, not proof of concept. Like any business, production lines, or bots, there will be outtakes that you’ll have to deal with and build up.
If you ask me, my personal belief is you can’t even begin to imagine what you can do. You can imagine, but you are limited by your own imagination and thinking, so you can go exponentially.
On a scale of one to ten, Automation Anywhere would be a seven to eight.
From my point of view working in the market and examining at it, this market needs more skill sets. This market needs more bilingual people and some more process-oriented people who can understand the business processes and help the customers grow.
Every industry has its own unique business processes, but this market is short on labor, even in skills, and also in terms of people who can articulate the value of process automation. That is a value piece from Automation Anywhere’s side. These guys need to build a good team.
There were five big criteria:
In our office, there was a full team with a full process and close to 10 to 15 people from procurement, technology, business, and also “gemba”, as I keep calling operations. They went into the evaluation and had a very scientific way of doing so.
There was another partner who we felt was very close, but the edge was the customer service and the support. That was the edge.
It was very easy and simple.
We brought in a partner. However, it was very easy the way things, and if someone has moved in the industry and business processes, they can do it. It was not that difficult at all.
Of course, yes, we have seen ROI. Especially in this market, human capital is valued in an ageing society. If you don’t find skilled people, who’s going to do the job? If you remove the neutrality of people and build it through the bots, that is the best way to do.
For my company and me, we come from a good technology company. Every company is a technology company. Without technology, you cannot live. When you are building up your back-end processes, especially in the shared services, what next?
In the Asian markets, they have come to a point of maturity where labor is the normal average. Looking at China, the Philippines, Malaysia, or even India, these markets are becoming more exponentially expensive. Therefore, what is our next wave of forward industrial evolution? To me, these digital automation RPAs going into artificial intelligence and machine learning are the areas of industry that we’ll need to move into very quickly. We need to take a very conscious call in preparing ourselves for the future.
Did we try some other solutions, to that extent, of automating the right business processes? I don’t know.
Was the solution good or bad? I don’t know.
But the perceived value of it, either in terms of real value or dollar value, or in terms of releasing the sources to do better thinking work, those are the areas where personally I was not convinced. So, let’s try something which has a more futuristic outlook. I call it glocalization, globally present and locally present. That was the whole idea behind our inception into reality.
The moment you say you are a vendor and looking at your contract, your relationship is over. You want business partners who can help the industry. We know how to make beverages, and for example, we make the best. I hope so, and I’m confident. We need some partners who know their stuff as well, and who understand the pain points of the industry and can help with them. Those are a couple of criteria which can make you successful partnerships and business relationships, not a vendor.
I would rate this product an eight.
If I fast forward two to three years. At that point in time, how would it look like? Maybe we have the same amount of enthusiasm, or if it we become very big, then we may become less agile. If you are small, you are more agile. The moment you become big, it goes into its own dimensions.
I’d would advise, first of all, if you are an end user like me, don’t think of yourself as a customer. You have to see your customer as your “gemba”, as the people in operations. Your product partners, implementation partners, and you are responsible for servicing the customer. Thus, it will always be a win-win game for everyone. Don’t try to put a blame on the product or the partner. You are all equally responsible, and need to put your skin in the game. Just go ahead for it.
Foreign Language: (Japanese)
この製品を主にどのように使用していますか？
我が社の場合の主なユースケースはまず、自動バックエンド業務全般です。これは通常APつまり未払金と売掛金、それにサプライチェーンの多くがあります。後はフロントエンドコミッションです。
Automation Anywhereのどんなところに満足していますか？
顧客関与が非常に深く、彼らは現場でよく働くと思います。 業務部と密接に協働してくれます。それに製品ロードマップが良いと思います。
では、彼らと築いた関係に満足しているということですね。
当ソリューションを使用するとどのようなメリットがありますか？御社が機能する上でどのような改善をもたらしましたか？
はい、後で話しますが、大きな点の1つはハードメリットだけでなく、ソフトメリットでもあります。つまり、実際にすべき仕事に人的資本を使うことです。それは少なくとも人間の精神を大量の反復作業から解放することにつながります。彼らがやるべき仕事をする。ボットは私達のために仕事をしますが、人間の頭には及ばないと確信しています。
には考える力を発揮させる。
当ソリューションの安定性に関して、どのような印象をお持ちですか？
それはまだです。まだ価値実証の段階で。実証実験を多く行っています。でもどんなビジネス、どんな生産ライン、どんなボットでも同じように対処して構築しなければならない支障はあります。
当ソリューションの拡張性に関して、どのような印象をお持ちですか？
それはまだです。まだ価値実証の段階で。実証実験を多く行っています。でもどんなビジネス、どんな生産ライン、どんなボットでも同じように対処して構築しなければならない支障はあります。
Automation Anywhereのテクニカルサポートを利用しなければいけなかった経験はありますか？ある場合は、サポートをどのように評価しますか？
はい。 10が最高の評価とすれば、彼らは7から8ですね。
10に達するには、何が必要ですか？さらなるサポートですか？
私の見解では、この市場は－私はこれまで様々な市場で働いてきましたが－この市場にはさらなるスキルセットが必要です。より多くのバイリンガルの人々、そしてビジネスプロセスを理解して顧客の成長を助けるプロセス指向の人々が必要ですね。
具体的な例を挙げると？ ビジネスプロセスやスキルセットについて？
どんな業界にも独自のビジネスプロセスがありますが、この市場は明らかに労働力が足りません。労働力が足りない上、スキル、それにプロセスの自動化の価値を明確に表現できる人がいません。ですから、Automation Anywhere側からの価値観で言うと、彼らは良いチームを確立させる必要があると言います。もっともっと。
もちろんです、はい。でも 拡大の余地はあります。急激に進めるための余地、そして急激に進めるなら、パートナーも同時に成長する必要があります。生態系全体が成長する必要があるので、ビジネスが成長するだけでなく、生態系が成長しなければサポートも難しくなります。
Automation Anywhereからのサポートを直接受けていますか？
そうです。直接…名前は言いませんが、製品部で指導を受けたパートナーがいました。というのは、製品を最大限に活用するためには、全機能を探索する必要がありますので。
初期セットアップはどうでしたか？簡単、それとも複雑でしたか？
とても簡単でシンプルだったと思います。
自分達で、それともパートナーを使って？
パートナーを連れてきましたが、そのままでもとても簡単だし、ビジネスプロセスで移動したことのある人になら誰にでもできます。全く難しくはありません。
当ソリューションの次のリリースに含まれていたらいいなと思うのはどのような機能ですか？
すでに言いましたが、人間の思考の将来は限られています。私達はGPではなく、自動化の進歩で考える。だからこの質問への答えはありません。
現在のバージョンで改善されると思いますか？
まだ完全に見れていないので、改善に関して答えるのは難しいです。
スケールアップをすると、価値実証でのように、現場で働く専任スタッフを1人増員することはできますが、その場合、規模を拡大して2万人の組織内でボットを含む150人がいるとします。その一人一人が親身なケアを受ける必要があります。そうすると、もっともっと沢山のサポートが必要となります。というのもこれは新しいものであり、失敗すれば、これは生産パートナーのせいではなく、現場の人間がそれに適応しないからなのです。
ROIは出ていますか？
もちろんです、はい。言うまでもなく。この市場では特に人的資本が少ないです。高齢化社会で熟練した人がいない。なら誰がその仕事をするのでしょうか？ そこで人の中立性を取り除いて、ボットを使って構築するのです。それが最善の方法でしょう。
新しいソリューションに投資をする必要があると思ったのはどうしてですか？
私自身そして我が社は素晴らしいテクノロジー会社を経て来ています。先ほど申し上げたように、このテクノロジーについては後でお話しますが、会社はすべてテクノロジー会社です。テクノロジーなしでは生存はできないし、特に共有サービスにおいてバックエンドプロセスを構築するなら、必要なものは何でしょうか？アジアにおけるこれらの市場では、労働が通常平均という成熟の地点に実際に達しています。中国、フィリピン、マレーシア、もしくはインドを見てください。これらの市場は急速に高価になってきています。では今後の産業革命の波は何か？私の思うには、これらのデジタルオートメーションRPは、人工知能、機械学習へと移行します。これらは非常に迅速な移行が必要となる分野です。 そこで私たちは未来に向けて意識的に自分達自身を準備する行動を取ったのです。
以前に別のソリューションを使っていましたか？その場合はどうして変更しましたか？
これまでにいくつかのソリューションを試しましたが、適切なビジネスプロセスを自動化したかどうかは分かりません。そのソリューションが良かったか悪かったかも分かりません。でも、本当の価値、あるいはドル価値のどちらかの観点で認識した価値、またはより良い働き方をするために情報源をリリースするという観点から言えば、私個人的にはあまり納得していませんでした。なので、より未来的な見通しのあるものを試そうと思ったのです。私はそれをグローバリゼーションと呼んでいます。グローバルに存在し、ローカルに存在することなので、これが発端から現実までの背景の全体像です。
他のベンダーも検討しましたか、それともAutomation Anywhereだけでしたか？
12のパートナーから選出されたプロセスから始めました。
ベンダーを選ぶ際、決め手となる、その他の条件は何ですか？5つのうちトップの2つはどれですか？
違う答えをしたいと思います。まず彼らはベンダーではなく、ビジネスパートナーです。なのでその定義は違うと思います。彼らが、自分達はベンダーだと言い、契約を見始める瞬間、私達の関係は終わりだと思います。欲しいのは業界に役立つことのできるビジネスパートナーなんです。例えば、私達は飲み物を作る方法を知ってるとします。最高の製品を作っている。私はそう思うし、確信もしています。ここで必要なのは自分達の製品に精通していて、業界の支払いポイントを理解し、助けてくれるパートナーです。こういったことがベンダーではなく、成功するパートナーシップやビジネス関係を作るための2つの条件でしょう。
Automation Anywhereを選んだわけは何ですか？
条件を決めていました。5つの大きな条件が。もちろん、コスト。まず、特徴と機能。 グローバルおよびローカルサポート。3つ目はもちろんカスタマーサービスです。そしてもちろん、テクニカルサポート。私たちのオフィスは完全なチームがあり、完全なプロセスがありました。 調達、技術、ビジネス、そして私が「現場」と呼び続けている運営からの10〜15人近くが非常に科学的な方法で評価を行っています。 非常に密接だと感じていたパートナーがいましたが、決め手は明らかにカスタマーサービスとサポートです。それが最重要です。
Automation Anywhereについて、その他に付け足すことはありますか？
いいえ、何もありません。皆さんのご清栄をお祈りすると同時に、Imagineを東京デビューさせてくれた彼らに感謝します。彼らはロンドンへ行き、ニューヨークに行き、今ではインドにも進出したことを知っているので、うまくいけば私たちの市場はこれから持つべく相互作用から恩恵を受けることでしょう。
製品、サポート、環境の全体に1から10の評価（10＝最高）を付けるとしたら、どのように評価しますか？
8
特定したものではないです。2、3年時間を早送りしたとしたら、どうなっているでしょうか？同じだけの情熱を持っているか、もしかしたらとても大きくなっているかもしれない。だとしたらアジャイル性を失います。小さければもっとアジャイル性があります。大きくなった瞬間に自分だけの次元に入ってしまうんですね。
このソリューションあるいは同様なソリューションを探している、同社あるいは他社の同僚の方に、どんなアドバイスをなさいますか？
まず、私のようなエンドユーザーであれば、自分を顧客とは考えないことです。自分の顧客を現場の人として、運営の人として見る必要があります。 製品パートナー、実装パートナー、そしてあなたは内部にいる顧客にサービスを提供する責任があります。だから、これは皆が勝つことのできるゲームです。製品やパートナーに責任を被せてはいけません。皆で同時に責任を負い、ゲームを進めるべきです。
We use it to automate all kinds of business processes. The primary use case is the RPA platform, even though they have the cognitive platform and the analytics platform. We use it for so many different things it's hard to focus on one, but it's automating business processes in our banking system.
We're interfacing a lot with Excel, our ERP systems, some legacy systems, the databases, file folders, text files, CSVs. It's hard to pin down one.
Through the software, we have been able to reduce the time that we spend on manual, repetitive tasks, so that we can focus on activities that add value to the business or to our partners and customers. The most important things are saving time, increasing control, and increasing automation.
If you ask our CFO, I think he would say that the most important thing is that we saved some money, with more efficient operations, etc. But I feel the ability to change from doing non-value-added tasks into work with added value is important.
We have saved the equivalent of about $40,000 to $50,000 by using it, during my time here. That's a lot. We recently did a large migration that saved us a lot of time on things that were going to be done manually. We were able to automate it and we saved around $15,000 to $20,000 on just that migration. That's quite substantial.
One of the features that we have used the most is an action in the Workbench called Object Cloning. We find that very reliable and very useful for implementing different business processes.
In general, the security and role-based access control - credentials security - are also important. We have a high focus on security in the bank. It's obviously a very highly regulated environment, so security is a top priority for us. To be allowed to automate different processes, we need to have a good set of controls around who is allowed to do what, and what credentials people can and can't use. It allows us to manage access to make sure that we have full control.
Other things that I also find very useful are the Bot Store and the Apeople community. If we run into troubles, we can always ask the forum and get an answer. People know if there is a pre-existing bot in the Bot Store that we can use to solve a problem. It's very useful to take advantage of the community. When they launched the Bot Store, it was a unique thing in the RPA market and it is providing tremendous value to a lot of businesses.
Also, their MetaBot tool is a very useful building block. We call it Lego bricks, here in the Nordic region. So if you build a wheel for your car, you don't have to build three more, you just use the same wheel over again. That's very useful and it makes the development phase even quicker. I hear other people talking about how they're spending three months on one process and that's a bit crazy. We deliver new processes every week and we estimate a process should not take a lot more than two weeks. But on average, we're spending two weeks per process, to get from idea to production.
The main things I've found that could be better are small things that can be annoying when you're using them a lot. I would recommend they add a feature where, if you mark the start of an "If" sentence it will highlight the end of the "If" sentence. That would make it easier to get a better overview. The small things are the most important in our day-to-day work with their software. Incremental improvements for a better overview or better user experience would help.
Also, we would like to see more options for merging and un-merging PDFs. More flexibility there would be good. We've figured out ways around this and, using their software, we've been able to do everything we wanted to do. It just took a bit more time to do it. We were on version 10.5 and in their Bot Store they actually had a bot that did exactly what we wanted to do, but it was for Version 11.0.
I find that they are making a lot of improvements that we are able to take advantage of with every release. I can't really think of something large that's missing.
It's been very stable. I can't really put my finger on things that haven't been stable that are under Automation Anywhere's control.
There have been some troubles for us when it comes to doing monthly Windows updates. That always turns off the Bot Runner machines and we have to do a complete, new log-on once a month on those machines. But we are aware of it and it's on our side, not Automation Anywhere's side.
Other than that, the runtime might differ. Sometimes it goes very fast, sometimes it can go a bit slower but I think that's also due to the speed of internet access as well as the computers we're running it on. Some of them have less computing power. We don't have the perfect virtual environment yet, so we're still working on improving that. But we can't blame Automation Anywhere for our having a legacy infrastructure.
In general, it works very well and we're really happy with the stability.
The scalability is good. I think we haven't really used the Bot Farm product yet, but that looks very exciting. We're planning on moving the infrastructure into the cloud and it's then a very interesting prospect to be able to scale up from 100 bots to 1,000 bots with just the click of a button. To my knowledge, it's probably the most scalable RPA software out there. We haven't really met any major challenges when it comes to scaling up, other than our own computers. But that's an in-house problem, not an Automation Anywhere problem.
I've talked to people using other RPA vendors and they have said they face some major issues once they pass 40 automated processes, but we haven't really faced those kinds of challenges. It has been running smoothly.
It's very scalable and it's easy to have control. There is a good audit log in the Control Room. And there is the ability to create your own roles and have strict, role-based access control where you say: This role is able to run this bot on this machine but it's not able to run another bot on the same machine. That's good from a security standpoint.
Technical support is really eager to close tickets as fast as possible, which is good. But as with any support, it can sometimes feel like it's slow because they have to do these standard checks to rule things out. Even though I say I've done them, they have to do them anyway. They have to be able to say, "Okay, this is checked off, this is checked off, this is checked off. Alright, now we can move to the actual issue." It can be a bit slow at the start, but they're always able to resolve our issues.
In general, I'm very happy with it and I can understand why they have to do those checks because if it's a stupid error, it's good to identify that early.
The initial setup is pretty straightforward. I've actually done installations of Automation Anywhere and I have no IT background. I've been able to set it up on a server and some virtual machines and get everything working.
The deployment took some time for us, but that was due to a lack of a good environment on our side. To do a clean install would take some three or four hours to get everything up and running, depending on what kind of machines you have. If you have all the accesses you're supposed to have it can take a very short time. But, if you're installing it in an enterprise environment, it can take longer because you might not have all the accesses. At least for me, coming from the business side, I don't have all the administration accesses that I would need, but that's not Automation Anywhere. Overall, it's pretty straightforward and doesn't take a lot of time.
For our implementation strategy, we started out with a pilot, together with a consulting partner. We automated two processes and created a proposal for an operating model, governance, and a framework. After that, we just tried to pump out new automations as fast as possible to prove the value to upper management. After a while, we got some traction and we went from being just me in 2015 to between 12 and 15 people now. Some of them are not working full-time on it but we have at least 12 full-time employees working on RPA across our organization. We started out in Norway, but now we also have operations in Sweden, Denmark, and Finland, with people working full-time on automation in all of those countries.
All the developers are doing some maintenance. We don't have anyone who is assigned to doing only maintenance because we all find that a bit boring. We share the responsibility among all the developers so that everyone has the chance to do new processes and maintenance when needed.
We have a two-pronged approach there. The processes that are important for business continuity, the business-critical processes, are often maintained proactively. We are notified that a change is coming to the system, so we need to test it out and make a new version that will work when the upgrade of the system is live. So we're proactive in those kinds of processes. Non-business-critical processes are maintained reactively. We try to do it in the most sensible way possible, but there's always room for improvement, obviously.
We put a lot of responsibility on the process owners. They're responsible for notifying the RPA team in case of any changes in the graphic user interface or changes to the process, because of new rules and regulations or any other reason. The process owner or someone in his or her team will always know if there is a change in the user interface or the process.
If there is an error in the code, it is the RPA team's responsibility to fix it and we do most of that ad-hoc, when it happens. We always have some resources available to do those kinds of things and that's taken into account when estimating how long we will spend on creating a new process. We know that something might happen during that week or those weeks, so we add some padding.
In addition to the developers, we have a lot more people using the Control Room to schedule the processes.
So we tried to run fast and then we took a step back and re-evaluated. We built an even better framework, redid the infrastructure, put more thought into the security aspect, and we have industrialized our implementation. We still have some issues when it comes to our operating environment, but that's not Automation Anywhere's fault; that's more in our IT department's hands.
We used Accenture, they're our technology partner in Norway. We had good experiences with them, but I think it could have been better planned on both sides. We were not able to mirror their organization as we should. Ideally, we would have been more self-sufficient after those ten weeks, and it was only by chance that I had the time to be present during all ten weeks, every day, in the project. If we didn't have the people learning how to develop, how to do the business analysis side, and working closely with them, we would have been in some trouble going forward.
The project was a success either way, given where we're at right now. But they should have been a bit clearer on how much time people would need to spend and what was expected of us. It's always better to make the customer self-sufficient.
I think they also proposed a bit too-ambitious operating model with a bit too many people from the get-go. That was not that well received by our management. We're a larger organization right now than what they proposed, but I don't think that our management would ever have accepted or have had the guts to do the leap of faith and say, "Okay, we will have six people working full-time with RPA from today," in 2016. They didn't know the potential and didn't really see that we had that many manual processes.
These are small things. In general, we're happy with what they did. It's just that if I were to point my finger at something that could have been done better, those are the things that could have been done better.
Regarding the number of people involved in the deployment, from Accenture's side there were two developers, two business analysts, and one project leader. On our side, we had a project leader and seven or eight other people, but eventually, it was just me and the project leader who spent our full time on the project, while it was going on. Everyone else was also doing their day-to-day jobs. And with all those people, it was still too few.
We have triple-digit returns, in percentage. I feel it's worth every dollar we paid for it. We have seen a lot of the returns in operations and back office because we had so many manual tasks there.
A good example is a process that we automated where, on that specific process, the return on investment is above 30,000 percent. The total cost of ownership is around $1,000 and the return is something like $400,000 in direct cost savings. And that's still increasing. It's an ad-hoc cleaning job that we're doing, but for every contract we change, we save about half-a-dollar per month, per letter we're sending. It amounts to a lot.
We spent one day creating that process and four days running it so the cost of ownership is really low. Those kinds of processes are unicorns. You won't find them in every business and you have to have the right people and the best ideas. But we were lucky to find that process and, by itself, it has paid for a lot of the license cost.
We just did a round of price comparison on a global scale and found it's so hard to compare the license prices. But, Automation Anywhere, in general, is on the same price level as the other vendors, a bit lower in some cases.
If we're thinking about the list prices, the Enterprise platform license fee is quite high. If you have five Bot Runner licenses, five bot creator licenses, a Control Room, and an Enterprise License fee, Automation Anywhere is much more expensive than the others. But if you have a global agreement with them, the Enterprise platform fee is shared between all the entities that are using Automation Anywhere. In that scenario, it would be a lot cheaper. The prices are quite okay.
We evaluated Blue Prism at the time.
We did the assessment together with Accenture and I think they actually recommended Blue Prism vs Automation Anywhere. I find that a lot of the consultants in our region are recommending Blue Prism or UiPath because they have generous compensation and incentive packages for the consultants who sell their products. I'm not sure if Accenture would recommend Blue Prism if they didn't have some interest in it. If they were totally agnostic, I'm not sure if they would have done the assessment the same way. But it's hard for me to say.
If I were going to do a new evaluation today, I would evaluate Automation Anywhere vs UiPath, but I would still choose Automation Anywhere. I've seen demos of both Blue Prism and UiPath and I think the basic capabilities are the same - they're all based on the .NET framework and you can kind of do a lot of the same things with them. But when it comes to the scalability, security, etc., I think Automation Anywhere is superior.
Another major factor that played a role in why we chose Automation Anywhere was their prompt replies to any questions or issues.
I'm not sure how this part is with the other main providers, but Automation Anywhere has a really good customer success program. I have a customer success manager that I'm in contact with daily. He helps us elevate our issues to the correct people and makes sure that, if we have any action points that are pending on someone at Automation Anywhere, they are resolved as quickly as possible. The follow-up from Automation Anywhere's side has been fantastic. They give us information about what's in the roadmap and what's to come, and if we need any additional information for our IT teams or our management team - anything to would help us with information - they are available to do calls and presentations.
My advice is to get started and get help. It's very useful to have consultants come in to help you get started. That will kick-start your implementation journey. Also, look at it as a journey. You won't get to an end-state where you will say, "Alright, now I'm done," because you will have to improve your implementation at all times, keep progressing, moving towards AI.
In my opinion, the vendor you choose in the first year is kind of irrelevant. But when you come to a point where you're about to scale up, then it's important to be associated with the best vendors out there. For us, being a customer of Automation Anywhere puts us in a really good place to keep progressing and keep scaling up.
It's important to remember that we are not doing a full integration here, we are doing RPA. It's okay to do 80 percent of a process - the high volumes - and then do all the exceptions manually. You won't necessarily get a good enough return on spending an extra month to do all the exceptions. You want to go live with the volume that represents the 70 or 80 or 90 percent, as soon as possible. Then see if it makes sense to handle all the exceptions, the last ten to 30 percent. It's important for us to be able to deliver fast, as well as securely and controlled, and with the MetaBot and the other tools that we have through Automation Anywhere we are able to do that.
We have automated in excess of 60 processes running on 17 Bot Runners, which are like machines we can operate 24/7. We have 15 bot developers and we are closing in on capacity so we would have to expand the number of licenses soon.
Our plans for ramping up are about pumping out new processes every other week. We're working Agile with the RPA so we try to do short sprints and deliver something every week. The usage increases every week actually. I'm not sure if we are planning to have even more developers because we don't want to be in a position where people don't have things to do. We would rather have some backlog rather than having to fire five developers.
We are planning to continue on the same pace and ramp up the number of bots, rather than the number of developers. We did a proof of concept last year with Automation Anywhere's IQ Bot which was very successful. We did not, however, have time or resources available to implement that last year. Hopefully, this year we will have time and we will make the purchase of the IQ Bot license and start using their cognitive platform. We're thinking about implementing their analytics platform as well, because that's very useful for keeping track of our progress.
I would rate Automation Anywhere at nine out of ten. There's always room for improvement and, of course, we would want cheaper licenses and would want them to add even more things that we haven't thought about to their product. Still, we're really happy with the software provider that we're using.
Most of our use cases are for primary supply chain management. We have a lot of business processes and back office automation that we do primarily for our product people and our finance team. Most of the work is automation done in supply chain management, product setup, and product administration.
I have been using this solution for almost four years and one year at my current company.
We have automated our critical functions, like supply chain management and purchase orders. Overall, there's been a direct benefit from it so far. We just completed our Phase I project this year. We have staff who have been moved out of the mundane tasks and are now doing value-added activities.
Object cloning is the primary way of capturing inputs from screen scraping or mimicking the user flow, and it is 70 percent of the work that we do using Automation Anywhere.
We have a few issues which have persisted. These end up restarting the machine. We are hoping in version 11.3 of Automation Anywhere, our compatibility and infrastructure issues will be resolved.
If you are using object cloning, it is stable. However, if you work with image recognition and custom objects, there are stability issues.
We are on version 10.5.7. We have upgraded bits of it to 11.3, but it is still not operational on 11.3. We are currently working on migrating our infrastructure to version 11.3.
We are still small from a robotics implementation standpoint. We are just about 20 bots right now with no issues. If we scale up to 500 bots, I am not sure how the infrastructure and systems will behave, but I have had a good experience from a scalability standpoint on the tool so far.
I have a team of about 25 people with six people in support with the rest in development. At any given time, we have more than 50 people running Automation Anywhere.
This particular ticket management system works well. It's a reliable. If we need to a raise ticket for any issue, there is an escalation mechanism. Though, I have not used it. I try to utilize our customer success manager to be able to right person from Automation Anywhere. My experience has been good, though not excellent, from a support standpoint.
We were not using a solution before Automation Anywhere.
In version 11.3, the setup changed. So far, it has been simpler. Also, in version 11, they have changed the design into a Java Jetty architecture, which is more stable. However, we were not familiar with it, so we had some issues with it. Thankfully, Automation Anywhere diligently answered our calls and helped us through the installation. It wasn't easy to install on our own using the guide. We needed support from a technical entity from the support site to be able to do it.
It needs a lot of coordination between the DBAs, which is a separate team within our organization, the infrastructure team, our team, and the Automation Anywhere teams to execute the deployment. Getting them all together was a good three hours exercise just to install.
Two people from my team worked on the deployment, one of them being a DBA.
I have a technical team of support members who know our internal infrastructure. We built it in-house and the support is not outsourced to any IT vendors. We take care of the infrastructure provisioning, support, etc. We do everything ourselves, along with the help of Automation Anywhere.
I have a deployed team of six people for maintenance.
We have seen more efficient processing and less number of errors due to quality control.
Savings have not been able to catch it that much. I believe there is huge potential here. This year, we are focusing a lot on the indirect benefits of speeding up the process. For example, we want our key customers to benefit, or buyers and suppliers boost up their business to receive benefits indirectly by freeing up their time.
They give us a good deal on the licensing because we bundle and customize things. If you ask to get a bulk business deal, you will receive more benefit. If you take other products from the suite, like IQ Bot, you can also receive a deal on the licensing.
We have also worked with them for so long now that we have developed a relationship.
My current company looked at UiPath. We decided to go with Automation Anywhere vs UiPath, because of cost, reliability, and scalability.
We do look at companies like Microsoft Azure to do unstructured data processing for us.
It is a good with a good support app, but I would like it to work 100 percent of the time.
We are looking to increase our usage in the future. First, we need to locate the opportunities to automate within our organization to automate which are good contenders for RPA engines. We are also trying to standardize our processes to push more processes into the automation pipeline, leading to expansion. We are getting Automation Anywhere to assist with this as part of our Phase II project, and increase our bot usage by the end of the year.
If you are implementing it, you should have a good business case. Know what you're using it for: Is it for your direct or indirect benefits and what is the business value that you're going to bring in on the tool. Providing the tools for your business are important before onboarding it. Once you have onboarded it, you will need a good, capable team in-house to be able to keep the infrastructure maintained.
Start slow. Don't start with a huge approach, then you decide that you failed. Do some proof on concepts. Ensure there is work for your organization. Gain the trust of your stakeholders. Then, take baby steps to move forward.
