Automation Anywhere (AA) Bot Creation Process

How would you describe the bot creation process?

Luis Romero
CIO at Binary Technologies Inc
We have worked on several different projects, so far. From prototypes to production, on average, scaling our bots takes somewhere from three to six weeks.
View full review »
VP IS Global Development at a manufacturing company with 1,001-5,000 employees
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.
View full review »
Manager, Business Process Integration at a manufacturing company with 501-1,000 employees
Our first bot took ten weeks to create. It took six months to create the number of bots that we are currently using.
View full review »
Process Architect at a media company with 5,001-10,000 employees
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.
View full review »
Engineer at a healthcare company with 10,001+ employees
The bot creation process is very straightforward compared to other tools I have used. ServiceNow has a workflow which is a drag-and-drop activity itself, and then you configure it. Here they are going in that direction too: flow, design. It's really good.
View full review »
Technical Lead at a manufacturing company with 10,001+ employees
As long as you have a technical mindset or are able to think in a certain manner, the creation of a bot is very intuitive, especially since the tool is drag and drop. For example, I am able to take any of the commands that I need and put them in the right sequence of orders. This makes it very intuitive to create a bot from start to finish.
View full review »
RPA Developer at Verizon Communications
We have built many bots. It is good to use the best practices when developing them. For example, we add logs and error handling to each bot, so if it is not working, then we can see why. This helps our developers a lot.
View full review »
Architecht at a insurance company with 1,001-5,000 employees
For our bot creation process, we first have a business meeting to understand what the business processes are doing and we look at the process metrics. We have a spreadsheet to capture the processes for which it's feasible to do automation. Then we look at the suitability of automating a given process and what would be the return on investment if we do the implementation. Once everything has been finalized, we will contemplate the development time, do the development, the testing, and then put it into production.
View full review »
Vandana Khanna
Sr Manager Emerging Tech at Verizon Wireless
I like the bot creation process, because it is very simple. If the process is not complicated, then the bot is really easy to create.
View full review »
Automation Architect at a tech services company with 10,001+ employees
Bot creation is a cool feature. It allows the developer to do complex things.
View full review »
Business Transformation Manager at a maritime company with 10,001+ employees
The bot creation process is pretty user friendly for a lot of tasks, such as the object cloning.
View full review »
BPM Analyst at a financial services firm with 1,001-5,000 employees
The bot creation process is easy. It does require more thought if you truly want to incorporate some good error handling in the process.
View full review »
IT Project Lead at a financial services firm with 51-200 employees
They designed the bot creation process where we can drag and drop and all of the commands are available to us on the left side of the screen. There is a lot at a developer's fingertips to do their development process.
View full review »
Senior IT Design Analyst at a retailer with 1,001-5,000 employees
The bot creation process is good. It is pretty simple to understand.
View full review »
Application Lead at a financial services firm with 1,001-5,000 employees
For our bot creation process, we get somebody from the business unit to walk us through their process. We usually record that session, then we determine how to create the bot from there.
View full review »
Senior Manager at a tech vendor with 10,001+ employees
Building a bot can be pretty quick. If you understand what the problem is that the bot is trying to solve, then you can get it done pretty quickly since the process is easy and straightforward.
View full review »
Software Engineer at The Travelers Companies, Inc.
I would describe bot creation with the word "exciting." We've had a couple of team members who have been working on projects who say, "Let me do it!" They're familiar with the product and they're very comfortable with the building process.
View full review »
Vice President & Head of HR - L&T Defence at a tech services company with 10,001+ employees
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 automation scope 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, for example. 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.
View full review »
Configuration Specialist at a energy/utilities company with 1,001-5,000 employees
Compared to the other different tools I have been experienced with, Automation Anywhere is so good. It's double friendly.
View full review »
Senior Group Manager at a financial services firm with 1,001-5,000 employees
For the bot creation process, we ask the end user, "Don't tell me how you do something, show me what you do." Then, as IT personnel, we build it.
View full review »
Developer at a financial services firm with 11-50 employees
The bot creation process is easy, manageable, and everything is well-organized for a developer. Everything is centralized.
View full review »
Software Engineering Manager at a financial services firm with 10,001+ employees
The bot creation process is easy enough with its drag and drop, then add some logic.
View full review »
Bill Weathersby
Board member at Transform AI
Bot creation is relatively straightforward. Probably within 20 hours, you should be pretty good at it. There are some nuances around it though that I think separate first time developers versus seasoned developers. What you will see in the marketplace is how easy it is to develop one compared to how easy it is to develop one that runs in production 99.9 percent of the time.
View full review »
Senior RPA Consultant at a Consumer Goods with 10,001+ employees
In the automatic invoicing system, we created a file which pushes onto a shared folder. The bot will pick up the file automatically from the shared folder and process the invoice. Therefore, if tomorrow, another bot were to be created, we could just create a file and copy it to the shared folder, then it would pick up the file and process the invoice.
View full review »
Chinmay Dhabal
Application Developer Analyst at a tech services company with 5,001-10,000 employees
I do the coding as well as the deployment side. I prepare documents and the user ID. Sometimes, if the user ID is not prepared, then I jump into the process to get it done. With the technical feasibility of the document, I take the technical feasibility and do an estimation to code the bot. I configure the bot, then code it according to the entity and get it reviewed from the client. Then, I run the bot through the Hapi port, as well as different scenarios which might come up.
View full review »
Reginald Christian
Head IT Operations and Infrastructure at a consultancy with 10,001+ employees
We need to asses the right approach, selection processes, choosing what to automate and what not to automate, and what would be the scale of automation.
View full review »
Technical Analyst at Tesco India
For the bot creation process, we first check the requirement. Then, we check with each application, whether it is applicable through the Automation Anywhere tool or not. Some applications, like Oracle, do not work correctly. We make a feasibility report and advise the developer to use certain commands only. We provide a process map, e.g., how to create the bot according to Automation Anywhere guidance and what are the coding standards provided. We deliver everything. Then, the developer will start building our bot.
View full review »
Sagakumar Gangipelly
Sr. Software Engineer at Ryan India Tax
The bot creation workflow is pretty simple. We check for feasibility, and if it is feasible, then we go about creating bots for the task. We have some measurements for ROI. We check the return on Investment to determine if it's feasible or not. We check the typical measurements, then go for Bot creation. After creating the bot, we don't have a production environment after creating the bot. We just deploy and run that bot.
View full review »
Principal Analyst at a Consumer Goods with 10,001+ employees
Bot creation process: We identify the process. That process will be well-documented along with the operations people, who will develop the BRDs. After the BRD creation, we'll come to know whether the process is feasible to automate. Concurrently, a solution design document will be developed. Developers will create the bot. Once the Bot is developed, UAT will be given to the operations people telling them whether the bot is performing as per their requirements. Once finalized, we'll get a UAT sign off and the code will be moved to production where the bot will go live.
View full review »
RPA Developer at a financial services firm with 10,001+ employees
For the bot creation process, we have a solution architecture team. They will analyze the process and check for feasibility before proceeding to next level. They'll check whether the process can be automated, then prepare a document which will come to me. Then, I'll try to make the SDLC. I'll check whether the process is possible, then we'll go for development.
View full review »
Technical Lead at Verizon Communications
Bot creation process: We have a PDD document available once the use case is identified. Once the PDD is available, if it is a legal/security issue, then we go for the next stage: development. We develop the SDD. Based on the SDD, the bot is developed. Once it is all developed and the UAT testing is done, we'll show it again to the legal/security. Then we go for the approval across the business teams. There will be lot of approvals required. Once it is approved, then it goes to production. We'll create a bot ID in-between once the use case is good.
View full review »
Shashi Pagadala
Manager of RPA Development at a manufacturing company with 10,001+ employees
A business user, whoever is doing the manual process currently, will send their request with the details of the use case. Those details will be assessed by IT and the business functional groups to measure what will be the man-hour savings. Also, is it a possible candidate for RPA?Based on those measurements, we identify candidates for RPA, then we determine if they meet the current threshold of 500 hours. If it is more than 500 hours, we consider that a candidate for RPA. Based on that criteria, we identify and prioritize it. Afterward, it comes to the development team for development.
View full review »
Automation Lead at Universtity of Melbourne
If you use object cloning, which is another function within the software, it's more dynamic. It'll wait for certain fields to appear, then you will lower the risk of breakages of code.
View full review »
Sign Up with Email