I am an RPA developer and I work with UiPath in that capacity.

Our current use case involves the automation of a process involving healthcare-related data. This is confidential data that is received from the customer and inserted into Oracle forms. Reports are then generated from it and these reports are then used by the organization, which is in the healthcare domain, for their analysis.

The data being analyzed includes medical and treatment history. For example, with the current pandemic going on, there are all sorts of healthcare data that is related to it, including various types of treatments. When somebody walks into any clinic or hospital, all of the treatment is entered into a database and we get an extract of it. The analysis is used to get more details.

Another interesting use case, prior to this one, involved the documenting of invoices. We were working with approximately 250 different samples of purchase invoices, many in different formats. One might be a native PDF file, whereas another could be a scanned PDF, and yet another might be a simple handwritten invoice that was converted into a PDF based on a picture that was taken from a mobile device. We were receiving these invoices from our client and they wanted to extract data from them. It was accomplished by using the Document Understanding features in UiPath.

The other notable use case had to do with issuing refunds for purchases that were made on an e-commerce site. When a customer made an order and there was a problem that resulted in them wanting a refund, there were multiple ways that the client could request one. A refund application could be received by the customer care department in the form of a simple call, which was a verbal request, or as an email written by the customer, or as an automatically-generated email that was created based on filling out a form on the website.

Regardless of which of the three input methods is used, the refund request is gathered and sent to a mainframe application. At that point, the information is extracted from the mainframe and the refund is issued using another application.

The automation of these tasks using features such as artificial intelligence and document understanding has reduced our costs. For example, with the invoice processing use case, there was a team of between 20 and 25 agents who were doing it manually. Obviously, a team of that size has a large cost associated with it. Also, the volume was very high, which meant that the team was not able to deliver on all of the work. There are approximately 250 vendors sending invoices to our customer to process the data, which translates to about 1,000 documents being sent on a daily basis, to be processed by only 25 people. It was a huge task. With this level of volume, people tend to get frustrated. 

We implemented the automation and the team size has now been reduced to only five or six people, and that is only required to monitor the bots. For example, they check to make sure that the data being fetched using document understanding is at par. We have set the minimum confidence of the documents being scanned at 90% and each day, a report is generated and sent to the customer. Overall, it was a very cost-saving implementation.

We have a lot of SAP Extract, transform, and load (ETL). We have human resources and time management. We have a very diverse tool landscape due to natural growth. We are in a very early stage of transformation, so we use it to bring information into multiple systems at the same time.

We also have a good few financial use cases related to tax. We work in Europe. Within the EU, there are different regulations, and sometimes, we have very short deadlines. On the third or first business day, we have to get information out of 16 or 17 SAP systems and format them. We have to get them out to Italy and Spain for government stuff.

The objective that we were trying to achieve by implementing UiPath was hard cost savings, but I changed that a little bit. It is not the right technology for hard cost savings. We have now changed it to quality and efficiency, and what they do with quality and efficiency is up to them.

My domain and expertise are in life sciences. In life sciences there is a process called pharmacovigilance, which involves monitoring the effects of medical drugs after they have been licensed for use. I create end-to-end automations, for case processing and full data entry. The customer will store details in an Oracle-based pharmacovigilance platform called Argus, where clinical data from the client and the product are stored. The UiPath bot has to capture the cases from Argus. Once a case has been input into UiPath, a mandatory status check, duplicate search, and case processing have to be done.

It then needs to perform full data entry in Argus. The full data entry consists of more details like patient information, product information, event information, and so on. The bot needs to validate and input those details into Argus and save the case. 

Some days there will be 1k records and on other days, there will be 2k records. On average the bot will process 12k to 13k records.

We use UiPath to automate business processes.

We use UiPath Orchestrator and other products in the cloud, but we deploy the robots to our own internal network. The robots are managed by the cloud, but they run within our applications on-premises. The UiPath administration system and configuration are also done in the cloud.

I've worked in two organizations where I have used UiPath. The first organization was in banking and we used UiPath to help automate banking and financial forms. The second organization, the one I am currently working for, is a technology company with several sub-companies that include banking/financial, the hotel sector, and some overseas organizations. In this organization, we automate tasks that are repetitive, as well as reconciliations.

We are using it to extract information from invoices. We have different types of invoices from about 180 vendors and we need to automate extraction from about 6,000 invoices. We receive invoices via email and are using automation to extract the invoice, put it into a folder, extract information from the invoice, and then enter this information into a SAP-based solution. Not every detail is taken from the invoice, only the relevant portions. 

We have already developed it and it's in the testing phase, where what is being tested is sending the money to the vendor.

For example, if we have purchased something for £1,000 from a vendor and they have sent us an invoice, we extract all the information, confirm that the purchase has been done by looking at our records, and then we have to submit it to the accounts office. That office will create the payment invoice for the vendor.

I've used it to automate different types of processes. My first project was to automate PDF documents. The process was a bit lengthy for the client. The client actually used to enter the information into the PDF templates and get them submitted to the government websites. And once they submitted their documents, the government released grant payments or other stuff. Previously, they hired people to do the data entry. However, it was taking too long, and some crazy errors. They had to have a pretty formatted, clean Excel sheet.

With UiPath, the bot would choose the data, get the data from there, and then put it into PDF files, save them with the sort of renaming schemes, and then upload them to the drive and then to the portal. That's the first use case I got. I built up workflows in it and automated the whole process. 

I keep exploring it and now have other use cases coming in as well. There are more than 150 or 200 use cases for different types of projects. 

We use the tool for mostly attended and unattended automation. 

We have many use cases, including 50 or more in the finance domain. This solution supports Robotic Process Automation, RPA, and I work with it for website automation. We use it with SAP and use it for Excel automation.

For example, we use it to download an EML file, and using a UiPath application, we extract PDFs using OCR activities and convert them to digital files. Once we've accepted all data from the PDF, we update all of the details digitally and send the particular data to the business via a consolidated business sheet.

We use it for handling processes that involve human effort savings. We are currently focusing on processes and problems that our users are facing in their day-to-day activities. It is used for the automation of business problems that are repetitive and error-oriented with a huge number of users working on them. We list down a set of processes where users are spending a lot of time, then we verify whether the use case is valid for automation using RPA. Once that is complete, we start programming the bot based on the requirements given by the user. We try to mimic each and every action performed by a human being by using UiPath Studio. It replicates what a human being does.

In terms of setup, the development happens in Studio that's on-premise, but the deployment of the robots is done on the cloud. They have their own cloud service called Orchestrator. UiPath hosts that, and it is available at cloud.uipath.com. It is basically the UiPath Cloud. The interface is completely handled by UiPath.

We are on-prem but we will be migrating to the cloud by the end of the month. 

My company has 100,000 people and uncountable departments. One of the biggest bots is in HR and finance. So far we have almost 57 bots in production, almost 45 in pre-production. We will have almost 100 bots by the end of this year. Our target is to reach 800 bots by the year after. 

Our core business is BPO, which is Business Process Outsourcing. We have massive operations that we have to perform for our customers and we have a digital section of the company that is assisting with that. The digital section is relatively new, being no more than two years old. We are building a number of solutions and tools that our digital section is using, and RPA is one of these tools. The goal is to help our customers innovate and assist them with their digital transformation, ultimately making them more efficient and more profitable. This is possible because some of the processes are very repetitive and performing them with humans is a very bad choice.

We have a hybrid environment, where some of our functionality is on-premises and some is on the cloud. For example, we have some cloud-based automation, and we use UiPath Apps, which is on the cloud.

We had a successful use case at the beginning of the year where we needed to process a large number of invoices that had contained errors when they were originally sent to the customers. There were approximately 200,000 invoices and we had a deadline of four days to complete the task.

It began with us developing the bot, which was completed in less than a day. After that, we sent the bot to our production environment to start processing the invoices. We were successful in the task, through the parallelism of 50 robots, we could process 5 invoices per second.

We have some metrics that describe how long it would take the process to be completed manually. It takes a human an average of between 60 and 90 seconds to process just one invoice. We estimated that it would have taken approximately 125 days to complete this task manually, with between 250 and 300 people working on it together.

I use UiPath to automate various processes in the energy industry, including invoice processing and contract registration.

At Aeyon, we use UiPath to develop custom solutions for our clients that drive innovation and digital transformation within the public sector. We work closely with the US Marine Corps, Army, Navy, Coast Guard, NASA and several other Federal agencies. We have built 50+ automations for a wide range of use cases, but the ones we see most often include financial reconciliation, data extraction using AI/ML Models, data entry, data manipulation/consolidation, downloading/moving files in bulk, data validation, and interacting with various web applications.

The business objective that our organization is trying to achieve with its AI-powered automation initiative is to greatly reduce the time spent on repetitive/clerical tasks and allow the employees more time to focus on the important tasks that grow their business such as collaboration and innovation. Aeyon successfully helps our client achieve this objective by using UiPath to develop solutions that increase efficiency, reduce operating costs, and drive ROI.

We're focusing heavily on document understanding processes. We use it to extract invoices, data tables from PDFs, budget, and PITBULL automation that's heavily focused on UI navigation and PDF manipulation. That's our main focus at the moment.

We've had a few calls with UiPath where they've shown demos on how they use the AI Center, but we've yet to find something that we can look in and see because we are a financial institution. We want to trust AI. We need to build our confidence in that before we actually implement it. It's at an experimental stage for us.

I have worked with most of the UiPath use cases. From 2017 to now, I have delivered more than 400 bots. I have worked in healthcare, energy, shipping, and other industries.

When it comes to manual processes, especially IDP and the combination of IDP and automation, the journey has been a bit difficult and challenging, but it has been worth it. Most other automation is straightforward. We take input from multiple platforms, put it into another platform, and so on. But with IDP, we have to read the document, validate the data, and then integrate it with the automation tool in UiPath.

I started integrating IDP and automation before UiPath Document Understanding and the Action Center were available. What I used to do was automate the process and then create a layout in ABBYY. I would then integrate the ABBYY layout into UiPath, evaluate the data, and then automate the rest. I did this in 2018 and 2019.

Now that we have our own Document Understanding and Action Center platform, I don't have to rely on any third-party tools for IDP. The combination of automation and IDP within a single platform has made a big impact on many businesses. It has helped them to reduce their annual efforts in data entry, reading documents, and correcting small errors in data extraction and copy-pasting.

I have seen the best results when IDP is combined with automation. It has reduced manual efforts by at least 80 percent. Automation is always helpful, but the combination of IDP and automation is even more effective.

In one example, we were able to deploy more than 700 bots for a single organization in the manufacturing industry. They had around 25 servers just to run the bots, but now they are running multiple bots on a single server. They are saving millions of dollars per month by using UiPath.

Overall, I think the combination of IDP and automation is a huge game-changer for businesses. It is helping them to save time, money, and resources.

Most of my use cases are spread across all the business units. It's used in accounts payable or for receiving reconciliations. It is also used in directory management and the banking finance sector. 

For a current client, we have around 22 to 25 use cases, and it's all based on the financial side of things. The client is in finance, and we have use cases all of which are comprised of different tools, including SAP and their in-house CRMs. It's about automating the process where we take some data from the CRM tool and upload it to SAP. It also involves uploading the files to the FTP server. 

For example, one use case is where the applications used are Oracle, and SAP, and STP. We just download the data from Oracle. There are different files that we download from Oracle and upload to the FTP server. From that FTP server, there is a different team that takes those files and creates a Tableau dashboard. 

We managed over 500 global tasks worldwide, leveraging UiPath to automate procurement, financial accounting, customer service processes, and customer relations.

We evaluate resumes through the RPA and ChatGPT four. We also arrange service for customers who need repairs to their devices through automation we developed using UiPath.

We use the solution for robotic process automation. We use it across the value chain for our business. We've used it in accounts, including cash management, and in HR for management tasks and IT for password resetting. 

We are an auditing firm who has a certain level of tasks that are open for automating. These are complete steps, which can be performed by anyone, standardized, and do not involve any human intelligence. These are just basic human tasks. It is a long process, where in-between there are certain validation and verification steps as well as certain steps that involve a lot of documentation to go through. The organization is targeting all these tasks, which are completely static and can be automated, so they can get rid of them. Then, employees can work on something more useful as well as more productivity-oriented tasks.

Currently, I am dealing with our internal COE, providing RPA solutions to internal and external clients. UiPath is a driving force in our COE.

It is on-prem. There are a couple of discussions going around upgrading UiPath because there has been so much advancement with the solution.

We have many use cases. We have used it in finance, HR, IT, business supply chain, insurance, etc.

We needed a solution for users that had too many manual tasks. We're in a large bank, and there are tasks like account opening or other items that can be automated using the UiPath system. It can handle auditing as well. 

We use UiPath for web scripting, data loading, data uploading, desktop application scripting, file uploading, and data downloading. 

We have licenses for 15 robots and they are running internal processes. We develop them using UiPath Studio and we only use unattended automation.

Our primary use case, which is 70% of what we have automated, is related to our booking system. Instead of having 10 agents who handle the booking or creating the reservations, the work is done by the robots. Sometimes, bookings are very simple where you have just airfare or the hotel, but in our case, it's quite complex. We call it dynamic packaging, which will have a flight component, you can have a hotel component, different attractions, meal options, a rental car, and more. Instead of entering all of the options manually, which can take up to 10 minutes or 15 minutes just to create a single booking. It is similar when we perform other tasks, such as making a payment. These things are normally done in our target system. I have created robots and workflows in UiPath that are triggered by the database, and they complete these tasks automatically. We have 15 robots conducting the job.

The second use case replaces the agent when once we get all information from the outside system using a .NET application and store it in the database, it creates parameters for the robots to make a booking or reservation at Universal Studios for attractions.

The third use case covers all of Europe and it is a completely automated car booking system. 

Basically, our use cases are all about travel and booking systems for Universal Studios, general dynamic packaging, and car rentals.

We have several use cases. We're a telecommunications company. We use it for anything from order entry, design, activation, and interactions with technicians within our field. We really have an end-to-end solution.

We are using Studio, Orchestrator, and unattended bots.

It is deployed on-premise but on our own cloud.

We use UiPath in various internal departments to automate our HR, financial, and IT operations, including access management and ISO compliance to control traffic.

We have UiPath deployed both on-premises and in the cloud.

We are an EdTech company. We are working on a solution that allows us to customize our offering by reviewing the intelligence that we have about a person. For example, based on how a person learns, we can customize our offering. If a person is more tactile, we can give more quizzes and other things so that the person uses his or her hands to interact. It is a work in progress. We are still implementing it. It is a lot of work.

I'm currently working as a solutions architect as well as the lead developer for UiPath. I have a vast number of use cases in various sectors and with SAP enterprise applications. I worked in the insurance sector and health sector, accomplishing different use cases.

I've used the solution in manufacturing in terms of procurement. We deal with a lot of products that come in and out and everything is being tagged in the SAP Enterprise application. We use UiPath RPA in order to close all the purchase orders that are already accomplished - and this needs to be done in SAP. UiPath is completely responsible for interacting with SAP applications in order to close purchase orders. 

I have developed a process that handles around 500 to 600 invoices a day, purchase orders a day. I'm running through multiple bots simultaneously.

Oracle has three broad categories: HCM, PPM, and finance. I have used UiPath to automate mainframe applications. I have automated all types of automation, including ServiceNow processes, PDFs, APIs, and web-based automation.

We use UiPath to automate back-office tasks.

Our primary use case with UiPath is to create automation software for the HR and the accounting department. Some of the automations that we do are automated attendance tracking, billable hours calculation, work hours calculation, expense reimbursements, et cetera. We have also completely automated our sales processes, such as contract building, invoice creation, etc. We do all this through UiPath automation. Earlier, all this was done manually, and it consumed a lot of time for us, but now, with automation, it's super-quick and efficient.

We are using a public cloud model. We host it on AWS.

We started out with a lot of unattended use cases and then moved into using attended bots to help users. I've been with two separate companies. One was a financial services company. However, there was a lot of support for external clients. In the company now, we're doing a lot around the back office, HR, finance, and supply chain. UiPath just runs the gamut of all different kinds of use cases.

We are an animal health company. We work to provide various products for companion animals, such as swine and equine. We are a global company.

The business objective that we are trying to achieve with its AI-powered automation is to reduce the effort for our business users. There are certainly a lot of tasks that take them away from some more high-value opportunities within their function and improve the overall customer experience. We would like to be able to look at the data differently and to be able to ultimately improve our customers. That is our ultimate goal.

The great thing about our function within the company is that we explore automation throughout the company and all different business functions. A lot of our use cases are for replicating some of the mundane manual tasks that users do. A lot of them are data reconciliations involving extracting and comparing data from different sources. We are also exploring opportunities to be able to understand and process data better by using some of the UiPath task mining capabilities. That is what we have at the forefront right now.

The use cases for UiPath are mostly based on SAP products, web applications, and APIs.

Unattended Automations are the best value from an RPA solution to an organization. It makes sure human employees are now more productive 95X.

Our primary use case for UiPath is robotic process automation and automation fabric with document understanding AI.

Our company is in the dairy industry and uses the solution for automating 25 processes. 

We started with financial items such as utility invoices, vendor invoices, accounts payable, and accounts receivable. 

We are also simplifying the processes for creating recipes and food manufacturing. 

For example, we were able to use machine learning to read invoices for utilities at all of our factories and from 50 dairy vendors. All the invoices look different and AI is able to recognize where important data is located. The AI technology is amazing and we use it for three of our biggest processes. 

We are using UiPath for office automation for our clients. We use many activities of UiPath. We are using CV, RegEx, Excel automation, and email automation.

We are working on a project for a billing company in the US that takes care of patient records for a hospital and saves them on a website. We are handling the patient billing system. We have an email as input at the start of the automation. The bot reads the input. In the input, we have the patient's name and date of birth. The bot searches the patient's name in the EMR hospital application and gets the PDF from the application. We have put some filters on the application. In the PDF, we have a patient's details and a record of their visits and the issues they are having. The bot then uploads the PDF on a website.

We process multiple records. There could be 2,000 pages or 500 pages. It varies based on the patient. For example, an 80-year-old might visit the hospital once or twice a week and will have a bigger file with notes and pictures of their visits. We follow HIPAA regulations for extracting patient information.

I use UiPath for a variety of tasks, including automating user interfaces, processing documents, utilizing process mining, performing test automation, and even handling natural language processing.

Our company, Block Mosaic, automates the creation and management of DeFi (decentralized finance) applications. This involves streamlining the development, deployment, and maintenance of these applications by automating repetitive and rule-based tasks. UiPath enables us to automate tasks such as data collection, communication with customers, integration with blockchain networks, and the execution of smart contracts.

We mostly use UiPath for the integration of bots in websites, as it provides integration features for AI chatbots, and we use it for the deployment of smart contracts on a large scale.

I use the solution with different customers. Sometimes it's used for financial organizations, or for accounting or ecommerce. It can be used for mortgages, or loan processing for example. 

My current retail organization uses UiPath for finance-related activities like invoice generation. We also use the solution for pulling documents from any stored devices for customers. We save customer files like licenses, invoices, and other tax-related documents in the box. If customers want to use such files for any purpose, we need to extract them from the box environment. A bot will check for that particular customer-specific file, download it, and save it in client-shared locations.

Transactional details regarding whether a customer has delayed an EMI or paid the EMI on time will be updated in the system. A bot we defined using UiPath will do it around the clock without any human effort.

I own the robotics process automation program for our life safety segment. I also own the mergers and acquisitions project management for our life safety segment. We've started out by using UiPath specifically for mergers and acquisitions when migrating customer data from the acquired companies to our standard ERP. We're also implementing sales and use tax, filings, and things like that as well.

We have automated tasks within our organization and are automating our marketing applications. Internally, we have automated in-person and webinar event creation for Microsoft. Whenever there is a request for creating an event that is covered on, for example, either on Jira or the Dynamics 365 application, the task makes an API and pulls data from both sources. It then creates an event on Marketo. It runs totally unattended. We have actually saved the build time that was previously around 45 minutes and we have reduced it to just four minutes.

I am a UiPath developer and my role in the company is as an automation developer specialist. I'm working mainly in UiPath Studio, not Studio X, and I also work with Orchestrator. We are using attended automation.

We are automating the processes in our company, for example, in the finance department. One of the ones that are now automated is invoice coding determination, which no longer involves humans. At this time, 80% of our processes are completed by robots. The remaining 20% is approved by humans but I think that this will improve later. 

We currently have 150 bots in production. It is used the most where there are repetitive, cumbersome tasks. Where we do need to have somewhat of a decision made, we put it into a decision tree. This is our primary use case. 

We are looking into other use cases, such as:

• How do we use it as a platform for pretotyping?
• How do we use it as a platform to drive forward machine learning and artificial intelligence usage in our company? 

We use UiPath primarily for tracking purposes. We are a logistics provider and have external portals and websites. The tool aggregates information from these systems to our core application. 

We use a feature called Document Understanding to extract data from invoices and generate reports. It uses the invoice number, amount, line amount, description, addresses, remit address, and other fields. This is the current project I'm working on. I'm using all the features available in UiPath to train the invoices to identify all the fields. Then, I deploy the training, create a pipeline, and use that ML skill in my coding while developing a project.

We are doing this for our team talent payments team. They usually receive different invoices from vendors for various reasons. My company currently has 700 vendors listed. These vendors send invoices for their services, and the talent payment team used to fetch and extract the data manually before we started working on this project. Whenever they received an invoice, they would open it and write down the data.

We have now completed phase one of the project and are in phase two. For this process, the bot will receive all the invoices and extract all the data needed by the team. We will then create a consolidated report in Excel for each vendor and present it to the talent team. This automation saves the talent team time. In addition, I have used email automation, Excel automation, API calls, and UI automation in this project.

We deploy UiPath on-premises, cloud, and hybrid environments depending on the organization's requirements.

We use UiPath for PDF annotations, Excel detections, and filtering data.

UiPath can be deployed on-prem or in the cloud. We are primarily using UiPath on the cloud.

Our company uses the solution to activate machine learning and automate processes for clients in the banking, supply chain, healthcare, and pharmaceutical industries.

For one use case, we instruct a bot to pull data from various sources to Excel where we manipulate it and run macros to produce output that is uploaded to other target systems. 

For another use case, we automate report downloads from Salesforce and SAP.

For a third use case, we automate invoice and purchase order processing by combining machine learning with OCR to extract information, output it to a CSC file, and upload it to the SAP finance system. 

A fourth use case involves scientific analysis for a pharmaceutical company. We collect research and clinical trial data, use a bot to conduct analysis, and produce a final report for scientists to inform their next steps. Before automation, scientists would spend four hours manually pulling and analyzing data before moving to lab work. Now, the bot does all the groundwork so data is immediately available to scientists. 

A fifth use case focuses on leveraging image analysis to study molecule or protein structures and produce predictions. We train bots in a third-party machine learning model to understand the science and then integrate it with the solution. 

For a sixth use case, we use bots to translate clinical data that is common across multiple countries. A thousand pages of data used to take three months to manually translate in 30 languages, but now bots can complete the task in four hours. This also removes the expense and security risk of a third-party translator who would need to have access to sensitive data. 

Our goal across all use cases is to speed up operations with bots that work 24/7/365 so that staff can focus on other important work. In the last three years, we have built 100 bots with 80% unattended and 20% attended. 

We use it for admissions policy and also for other financial items such as 1099 reporting from the IRS and things of that nature. There are some manual refreshes of systems and Excel documents that we have automated.

It is currently deployed on-prem, but we are looking at the cloud option. We are using version 2019, which is probably one of the oldest ones. It's pretty old. We're looking from a perspective of whether we upgrade it before we move to the cloud or whether we move to the cloud and upgrade.

We mostly use it for unattended bots. We are a construction company. Our RPA team does more of the complex processes for users. We take high-end complex items, that are redundant, off of the users' hands, then we host it on our servers.

We have a bunch of unattended processes, about 284 processes.

We typically solve for any use cases that falls under different business functions within our company. That includes finance, supply chains, services, IT by itself, and a little bit of engineering.

My company has multiple processes across various lines of businesses like finance, contact center, HR, tax, etc. Our use cases are based on the business corporation. They have to agree with the use case and what they want to automate. They have to provide the business details about the exact process. The developer or the lead will design the solution accordingly.

For example, in the revenue accounting area, we have around 5,000 to 15,000 requests in a day. It's all based on the number of sales that they made. We have implemented a multi-board approach, where the process can simultaneously run in almost 15 to 30 missions, whenever there is a requirement. We can increase the number of licenses based on the requirements.

We use Automation Cloud and Task Capture. They're trying to implement Task Capture with a couple of lines of businesses right now. We did not implement it completely, but it's in process.

Our use cases are all across our enterprise, from HR to finance, to customer service, to laboratory operations, to logistics, to compliance, to medical, et cetera.

We use UiPath primarily to drive efficiency within the company and introduce a new technology, which is only going to become more popular and more prevalent in the industry in the next few years.

At the moment, we use Orchestrator, Studio, and unattended robots.

We invested in an RPA solution because competitors were doing it. They do it because it's the next wave of this industry, the fourth industrial revolution. Everyone's saying that you can't escape it. It's also because our company, in the shared services department, is thinking about how to challenge our existing models. Traditionally, you chose whether to take the processes onboard or streamline them offshore, but robotics and automation are a competitive alternative to outsourcing. It's very easy. We are challenging the status quo and making sure we're evaluating all our options effectively.

We do a lot of claims processing for healthcare providers. We handled the billing, and it was very beneficial for us to use automation to perform those claims management and submit the claims for those various providers.

We utilize Orchestrator, the robots, both attended and unattended, and team sites.

In the past, we have used UiPath to automate repetitive manual processes for companies in the finance and banking sectors, but healthcare is our current focus. This industry involves processing tons of data from patients, customers, and doctors, so it's a huge field. 

Previously, I developed bots for compliance at financial companies. I've also created processes for reading PDFs, sending emails, Excel automation, logging, and exception handling. We have also contracted with insurance companies that need to pull data from emails into their main enterprise application.

UiPath is an end-to-end automation tool that helps businesses accelerate their processes by providing solutions for automating routine activities. These solutions enable faster and more efficient business exchanges.

I'm the lead robotics engineer in my organization, and we are involved in marketing and research for new technologies such as mobile phones and laptops. We are an organization with 219 employees and started using UiPath for laptop marketing and advertisement for our customers.

Our clients have different requirements and strategies, and we build software robots tailored to their needs. A customer can send an email with attached PPTs, Excel sheets, PDFs, and images, and the bot can extract all the data and express it in the required format. This is uploaded as an article onto our website, and on our platform, so the marketing, advertising, and technology solutions specs are taken care of without any human intervention or involvement. We designed 39 robots for the same number of clients.

Our second use case is for invoicing; customers share checks for payments with us via email, and we have bots to extract that data and input it into our SAP ERP system, which is fantastic. The RPA automates billing on the financial side of our organization. 

We use the solution across 17 locations with servers managed centrally from our main office, connected using the UiPath Orchestrator. We have 19 licenses but only use 17 currently. We don't have more than seven end users as this is purely a tool for internal use; our customers don't have access.

At my company, we automate everything, including the ERP. It's for logistics as well as the production. 90% of our use case is automating SAP and the bonus software.

I mainly use UiPath for all automation tasks. We focus on the security automation side. We are doing some research on security automation regarding incorporated SIEM. We mainly are focusing on the security automation side using UiPath.

It is looking externally at how we can enable the government to identify efficiencies and improve effectiveness. The other is, internally, how can we drive efficiencies within HR and finance, with everything that a big corporation can do. 

1. How do we help the government realize these benefits? 
   
2. How do we help our internal workforce benefit?

It is two different things, and they are similar, but they're not the same thing.

A lot of people externally are worried about the elimination of jobs, but at the same time, they still want that efficiency, and they are looking for it. We want to drive the effectiveness of the workforce, whomever we're working with. 

There are plenty of automation opportunities out there: DoD, the federal government, and commercial space. There are all sorts of stuff that we can do. Internally, we feel the same way. There are lot of things that we can do to make ourselves run more efficiently. If we are preaching to the government that they need to be using this, it's beneficial for us to say, "This is what we have done as a company."

Our company is 25,000 people across the globe. There are certain opportunities for us to include automation in what we do every day. We are doing it now by instituting RPA, specifically, and the tools that the UiPath bring to the table. It will be a game changer for us, if we can get it done at scale.

Automation is growing at our company. A lot of what we do is focused on AI. Going from zero to AI is a Herculean task. It's extremely difficult. However, there are many steps in-between zero and AI that we can do now to help realize the benefit to the company or the federal government, such as the benefits of the efficiencies that we can identify. That intermediate, non-threatening first step can be RPA, which ultimately will lead to enabling AI, but is not AI. 

Within our company, we are looking to identify what those pre-AI steps are, with the goal in mind that we know that the federal government is asking for AI. What we do in the interim is a type of level set, where you can build an algorithm, AI, or machine learning algorithm. This ultimately is what they want, but what they need right now is to aggregate their data in a structured way to be able to feed into those algorithms. That's step one. This is the first step to getting all your data right. It's not easy, because you have to take people out of the mindset of AI.

I am working with a Telecommunication company. I work on the software side and IT infrastructure side for the company. We had an EFT, and we needed to automate some functions. That is the main reason for using UiPath. We are able to do service failure handling, order handling, and other tasks. Currently, there are ten to twelve use cases related to telecommunication, but we are planning to automate most of the systems.

We have not yet used the AI functionality, but we are planning to use it in the next year.

We have multiple use cases, including banking and finance. We are primarily taking data from PDFs and manipulating it in Excel, but we also build some UI-related automations. 

We use UiPath to build attended and unattended automated processes for public and private sector clients. I try to make the processes as slim as possible so that they aren't as dependent on external applications. We have an abundance of documentation, and the goal is to have very little overhead. 

UiPath is a general automation tool that's useful in multiple cases, such as finance, HR, and cybersecurity. We have around 8,000 indirect users. Thousands see the reports generated by UiPath daily. 

Our use case started with the financial sector. We are expanding it to the navy's other operational aspects, such as HR, legal, procurement, etc. 

My use cases for UiPath include finance, HR, SAP, and technology. 

I've worked on many use cases for UiPath, primarily automation use cases, but the most recent one was for the HTS sector.

The customer was inquiring about payments, whether the payment was fully paid, partially paid, or whether there was an outstanding balance or payment discrepancy.

It was for a US client, and based on some validations, checks, and settings, I needed to identify if the payment was on time, delayed, or never paid. I had to commit to determining the information or data for my customer, which included many validation business rules. I had to consider the checkpoints before replying to the customer's query.

The query used to come through email, and I needed to extract the emails, identify what the query was for, and then go ahead and provide the solution.

We use UiPath to create automation for our clients. The best use cases are the ones where we automate an old system. We had instances where we migrated one customer's data over to another. Until that migration occurred to the new system, we could get an automated solution using the old system.

We use UiPath to understand and refine supply chain business processes. Our company is a solution integrator developing solutions for clients. We help companies undergo a digital transformation and digitize existing processes and systems.

You can monitor and automate existing processes, but it's challenging if there's a skill involved. You need to optimize the process and ensure the system is fully integrated. You're pushing the data into UiPath and optimizing the process. You want to integrate it with another system that isn't part of your environment or improve your process. In that case, sometimes you don't have the data in place. That is what you call process mining or process automation.

We primarily work with banking clients at a high level, automating solution points, nodes, and bot processes to reduce demand. For example, if a task was previously performed by a hundred people, we have now limited it to around five to ten people by implementing automation to closely monitor the bots in real-time to ensure their effectiveness.

I'm using it for the automation of various tasks. It depends on the tasks the users define. If we have a task that results in human error, or if we want a positive output in a small amount of time, or if we are working on huge amounts of data, we use UiPath.

Our customer had one attended robot and wanted to scale up. We used UiPath to identify possible processes that could be automated and also required the ability to scale up the architecture.

We develop and deploy use cases in the area of the cloud. We have deployed over 100 use cases. Most of our use cases are related to SAP applications, web applications, and mainframe applications.

One use case example is related to mainframe applications. The bot monitors mainframe applications 24/7. If there are any new jobs, they are identified, then the bot changes the status of the job to differentiate it. 

Previously, we are using the 2016 version of Orchestrator, then we upgraded to the 2018 version of Orchestrator. Some clients are deploying the 2020 version. It depends on the client. We suggest using a version back to clients, i.e., the 2019 version. 

We automate retail, sales, and agricultural services.

I have several use cases but primarily I use UiPath to input transaction data to the websites.

We are an insurance company. We mainly deal with all types of insurance from casualty and specialty to even aviation and medical stop loss.

I have had use cases where we have been taking information from emails and phone calls to put them into a mainframe. We have done claims intake for insurance, and then we have notifications. For the policy system, we have done a lot of back-office accounting work.

By implementing UiPath, we were trying to seek a way to free hours up at critical times. It is not just about hours saved. It is also the quality of the hours that we save and freeing people up for more value-added work.

We use UiPath to automate the repetitive tasks typically performed by knowledge workers, with a primary focus on areas such as finance, HR, and supply chain.

I am a UiPath developer. I have automated web-based processes like HR and finance. I have also worked on a use case consisting of web-based automation, Excel automation, and email automation.

We can't disclose our exact use cases, but we do intelligent automation with UiPath.

We utilize UiPath for the automation process within our organization.

The business side of our company has different processes and they send us requests to develop automation for them.

Right now, we have nine production animations.

Our first use case is to convert video to audio and then upload it to a legacy system. We have another use case that takes an Excel spreadsheet of 2,000 rows and searches one row at a time on the federal court website to get the results of our cases. 

We also have another use case that generates an SAP report daily, downloads a report, and feeds a Power BI dashboard. 

The last use case monitors a client's email, and as soon as there's the form request, we open the request, and we add it to their system automatically.

Our company uses the solution to understand documents, process invoices, move data from one system to another, conduct background investigations, and other day-to-day use cases for federal and state offices. 

For one use case, we built a sandbox for malware analysis using the bot. 

For another use case, we scan thousands of resumes to find an individual with a specific skill set. 

We have completed 90 automations with mostly attended bots that we have built. We are not using AI much right now, but plan to use it to solve problems in the future. 

I use this solution to download investor suspenses from 35 different investors in warehouses and populate those suspenses into our loan origination system. Once those suspenses are cleared, we get purchase advice to receive money and give capacity back to the warehouse lines to continue lending. 

We have 10 operational robots as well as other automations. These automations include populating interim servicing payments that come into the LOS, so we have a historic record of it. I am working on a project to reduce the amount of new folders or maintain existing ones. This helps us reduce the cost of document storage in our LOS. 

We make use of UiPath's user community to see different people's insights, exchange ideas, and identify features that could work well for our business. We also make use of the UiPath Academy.

We provide a lot of financial services. Its use cases are specifically in banking. There is a lot of Excel transformation where we are moving data from Excel into in-house applications. That's probably about 80% use of it.

We are using UiPath to automate processes that deal with a good cause. We run a lot of charity work, and there is a bit of work going on there to automate the operational aspects of running these charitable causes and things like that.

We have not yet used its AI functionality in our automation program, but we would love to.

The first use case is related to our email process. We need to download multiple attachments in the form of PDF and Excel files from emails. We only accept the PDF files into a specific folder, while the Excel files go into another. We split them based on the file extension.

The second use case is related to the retail domain, in which we need to update an application with data that we get from a client. We process a few Excel operations and then update all of the invoice records in the application and generate a PDF invoice form with the client's details from Excel. That PDF is then emailed to the client.

We are a consulting firm. We started last year, and we are growing pretty rapidly.

We have quite a few document-understanding processes that we are working on. We are a partner of UiPath, so we have various clients in different industries. Currently, we are processing vendor statements to create payments in NetSuite. We also have a three-way match cache application process, and then we have a basic user interface for scraping vendors' websites for payment data and that kind of thing.

We are trying to figure out how to incorporate LOMs with everyday processes and get reliable information back. We are also training a lot of machine learning models to extract data from PDFs along with processing contracts. I hope that those get easier to train and that there are more reliable answers or outputs from the models that we train.

We use UiPath for invoice processing and PDF extraction.

We use UiPath for SAP automation, detecting document sections, web automation, and external applications. 

We use both UiPath RPA and UiPath Document Understanding.

UiPath Document Understanding is for data extraction, while we use UiPath RPA for basic purposes and use .NET.

We also used UiPath once to automate processes dealing with good causes, particularly in Ecolab. The company dealt with floor cleaners and hand sanitizers for hospitals in the US, and at that time, the demand for sanitizers and floor cleaners was through the roof. It was so high that we had to automate processes using UiPath to fulfill the number of orders coming in, for instance, thirty thousand orders a day.

We use UiPath in multiple departments, such as HR, Procurement, and Manufacturing.

We do regular process automation for web applications and Excel. In one use case, we have a web application, and we need to scrape data and update it in a specified format in a spreadsheet and then upload it into another application. This is the use case on which I am currently working. There is another use case where I extract data from a web application and add the data into another web application, input the data into my Jira using APIs, or directly insert the records into a database.

We do not use UiPath to automate processes that deal with a "good cause" that our company is involved in. We are automating internal processes for the project engagement we have with our customers. We have general developer access. We do not do process mining, but we use UiPath Task Capture.

I work for a telecommunications company, which involves various processes in different areas. For all the company's needs, I primarily utilize UiPath. We have employed it to automate tasks such as packet installation, software attribute utilization, and coupon allocation. These are time-consuming tasks that involve a significant amount of data, making it impractical for a single person to handle. Therefore, we assign these tasks to a bot to expedite the process.

We are a platinum partner of UiPath. We work exclusively for UiPath and do implementations. We provide solutions using UiPath products.

One of the use cases was for a client from the manufacturing industry for onboarding apprentices. We did this project in India. They were onboarding 300 to 400 apprentices. Their insurance and other things were done manually, which was time-consuming. It used to take them a week to complete the whole process, which was a problem in case an accident or incident happened in the first week. They wanted to do automation to ensure that on the first day itself, after the employees are onboarded, the insurance and other tasks are completed.

We utilize UiPath to automate manual and repetitive tasks that range from simple Excel manipulations to web scraping. We have several use cases related to refinancing, such as handling accounts payable for invoice processing, remittances, and accounts receivable, among others. In addition to that, UiPath enables us to develop public-facing applications that are integrated with automation. This automation is triggered automatically whenever there are user interactions or events, resulting in numerous use cases. For instance, if the requested data is not already available in the document, we can obtain input from customers using UiPath. 

Furthermore, we employ UiPath products for automatic invoice processing. When we receive invoices in PDF format, we digitize them using our own OCR engine. Subsequently, this information can be utilized to save data into systems like SAP. We extensively automate ERP systems, including SAP, Oracle, and NetSuite.

We also use UiPath for application testing. We have built several test cases for suppression, user acceptance, and so on, which can be scheduled to run or run on demand.

One of the use cases is related to material billing. For the material billing process, previously, when a vendor invoice came into our SAP system, our staff had to write invoice data and process the invoice. We transferred this process to RPA. We now have only one robot focusing on this project. It handles about 120 invoices in a month.

We have not yet used UiPath's AI functionality in our automation program. We are always thinking about using AI and machine learning in our development, but we have not had a project in which we could use AI. We might use it in the near future.

It is deployed on-prem, but we are thinking about changing it to the cloud.

My use cases are mostly in finance, including settlements and reconciliation processes.

We use it mostly for our sales and for our clients, with relatively simple, stand-alone robotic solutions. Some are attended and some are unattended. We use it for reporting in our finance and HR departments. 

We use UiPath to automate the processing of large volumes of data. The company has multiple sites, but the organization's data warehouse is at one location. Around 80 people use the solution. 

It depends on the task that is assigned to me, but mainly, I'm using it for PDF automation and Java API-related automation. It is being used for extractions of PDFs and automation of the APIs to get a better and more rapid response.

I'm using it for PDF automation.

We're in the supply chain industry and we use UiPath for automations for purchasing and selling and to make people's lives easier within the organization. We have 20,000 users in our organization. 

We do not currently use the AI functionality in our automation program but we have in the past. I've found Document Understanding in the AI Center valuable. In the past, the action center was slow compared to some competitors in the IDP sphere, which can be detrimental if you're dealing with millions of documents but this has since been improved.

We use unattended robot processes almost exclusively and this includes approximately 130 to 140 processes. We do have plans to increase this usage and create more core automations. Certain automations have a shelf life and need to be retired at a certain point. A lot of times we're working with systems that are eventually going to be replaced. The reason why we use UiPath over strictly APIs or something programmatic is that we don't have access to something programmatic. 

We use it for everything. We use it for very simple things, such as moving data around in Excel, and bigger things that include using more advanced technologies, APIs, and some of the newer stuff that UiPath has had, such as Action Center, etc.

We have not yet used its AI functionality in our automation program, but we plan to do that in the coming months.

We're a consultancy and I am the strategic architect. I have implemented the product at 25 different client locations spanning multiple industries. Their RPA requirements range from pretty standard, bread-and-butter workflows that navigate an application and follow some business rules, to more sophisticated ones that are integrating Document Understanding and a little bit of chatbot.

I have deployed it on multiple application stacks, including out-of-the-box SAP, Oracle, Microsoft, and some specialty, third-party products like DNA, Encompass, LendingQB, and others.

My use cases are as a QA engineer. I mainly test automations that have already been built. I'm not part of the development side. We started small and some of the business processes we have used it for include onboarding, document processing, and payer processing. Our company is involved with healthcare and we're trying to grow the help we can give our healthcare workers.

My primary use case with UiPath is to automate workflows for processes in web-based applications, such as email and Excel automation. We also use it as a task or workflow management tool, capable of assigning tasks, checking on the status of tasks, and more.

Another thing that I have been doing with UiPath is replacing repetitive tasks performed within the organization. Automating such tasks makes the related process smoother and faster. 

We are using the UiPath automation cloud offering, which is a SaaS solution. One advantage to this type of environment is that we can get updates instantly. If it were an on-premises or hybrid model then the setup and maintenance take time, but this isn't the case with a SaaS model. This instant setup is what we needed because it made for a smooth transition from manual processes to automation. 

We are a services company. In terms of how we use UiPath, we handle a lot of the financial processes, including our customer billing, our time tracking, and our time reporting exceptions - such as looking at who has not submitted a timesheet. When this exception happens, there are automatic emails that go out using the RPA, from UiPath. 

The whole process from our inventory, which is our asset, is automated. With the asset, which is the time that our people spend on clients, we make sure that we capture what we need to create and send invoices out. The whole collection and AR process, including making sure that we get the money and send reminders to clients, that whole process, is automated - with human intervention, as needed.

It's widely used across the bank. Some are dealing with regulatory issues, for example, taking documents out of one system, moving them into another. Others are opening new accounts for clients. Some are doing payment transactions and that involves looking at emails that come in and determining what type of document that is so it gets routed and processed correctly. We've touched every line of business within the bank.

We're in the financial services industry, so we target the operations. We use it in finance but we're also going after our wealth management group, capital markets group, and fixed income capital markets group.

In one year we've done 17 automations in about 3,500 hours. We're just getting started. 

We use mostly unattended automation, but we do have both.

We use all three of the UiPath components which include: Studio, Roboyo, and Orchestrator. There are a bunch of use cases that we explored for the POC (Proof of Concept) to be sure the product fits with our expectations for automation. For example, one use case is reconciliation processes for insurance group retirement and LOB (Law on Occupational Benefits) plans. We built it, tested it, and now that is one of the primary things we use the product for.

We are using Studio, Orchestrator, and mostly the unattended bots.

Our primary use for this solution is to give time back to the employees.

We do not run our automations in a virtual environment.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a five. It's drag-and-drop, and all of the activities are there.

On a scale of one to five, judging how beneficial it is, I would rate the training a four. All of this information there is self-explanatory and it works. 

From the point where we started using the demo version, it was a couple of months until our first robot was ready.

I use UiPath for work projects that involve various applications, including license rebate processing and healthcare licensing. I develop reusable components for these projects.

Specifically, the process involves launching different licensing websites and extracting essential information such as license number, status, effective date, expiration date, and any disciplinary actions. This data is collected from providers like physicians, dietitians, opticians, and speech therapists. We validate the extracted information against existing databases or applications, updating records where necessary.

This validated information is crucial for determining the approval or denial of applications, such as those related to provider enrollment. Essentially, my work centers around creating processes with defined inputs and desired outputs.

Currently, I'm focused on a project within the manufacturing sector, specifically a constant bidding branch. Here, we gather order information for stakeholders, including tracking numbers, tracking statuses, and approximate order values. We store this data in an Oracle database, generate a CSV file from it, and distribute this file to stakeholders via email.

I work in the banking industry and have used UiPath to automate end-to-end processes for seven projects. I am also currently using UiPath to help our clients automate their RPA lifecycle end-to-end.

In my role within the banking domain, I am typically responsible for complex bots. I currently have two applications and data messaging tasks requiring the creation of BRM reports and their subsequent email delivery to users.

We use UiPath to replace the manual tasks done by humans through automation.

We use UiPath across a diverse range of functions and departments, encompassing accounting, human resources, loan servicing, employee progress tracking, and loan origination.

Our primary use case is more of a reactive ad hoc use case to solve business problems on the fly. We can build automations to update thousands of records. 

We're putting a little bit more money and resources into it, and we're starting to go down more of the unattended automation path to actually do more end-to-end processes. 

Our company deals with data analysis and we use the RPA to help with various functions related to data analysis and to keep our operations moving 24/7.

I have been in three different organizations working with UiPath. In all of them, I had to create the center of excellence for UiPath. For automation, we decided to use UiPath because it was easy to learn. We had citizen developers involved. Most of the use cases were typical manual repetitive tasks and did not involve too much intelligence. I did not use the AI components in any of the use cases that I have done in the past. We mainly had end-to-end automation of simple processes. They were not too complex.

I have worked in the energy sector, and there were processes that were connected to renewable energy projects, but they were not related to a good cause, such as improving sustainability. We also had processes that did not provide any financial gains for the company, but they improved the motivation of employees. For example, we automated a process to check employees' birthdays and sent an email congratulating the person and tagging their manager as well. There were no financial gains, but it had a good impact on employees.

50 percent of our business involves Digital Integration Automation, specifically in the banking and finance sectors. In this domain, we automate various processes, primarily focusing on banking processes such as lending and loan administration. Our operations primarily revolve around the core banking systems of the banks. Essentially, we maintain complex systems and infrastructure utilizing over 20 automation robots through UiPath.

We deploy on-premises, in the cloud, and also utilize hybrid models.

My company builds software for various businesses, and we use UiPath to automate data entry, perform repetitive tasks, and develop and deploy the software. We also use UiPath for document management, reporting, and analytics.

We use UiPath in multiple departments, including marketing and analytics. There are 17 users. Most of them are software engineers and developers, but our entire executive team also has access. 

We use the solution for RP automation to perform any processes we require, automate workflows, and integrate with third-party tools like SharePoint and Outlook. The deployment model varies based on client needs. 

I'm using it for automation.

We use UiPath to make processes. In addition to UiPath Studio, the platform that develops processes, UiPath includes other applications like Orchestrator, AI Center, Test Suite, Action Center, etc. 

I had the opportunity to work with UiPath Studio to develop and deliver processes to clients and scheduled them in production using the Orchestrator. I had the chance to automate many platforms in Excel, emails, et cetera. I developed around 20 processes.

I work with many medium-sized and large enterprises and a few small ones. Typically, the clients send us their PCs, and we work on their infrastructure. My clients usually have many departments, and all of them use UiPath. I use Orchestrator in the cloud, but clients, like banks, prefer the on-prem version because of security constraints. For me, there is no significant difference between the Orchestrator in the cloud and on-prem. We can schedule and maintain robots. They have essential common functionalities.

We started with a pilot for our payroll department. It essentially takes the transactions that come into our payroll department on Fridays and Mondays, and sorts through those transactions. If there are any discrepancies or errors based on the defined criteria, it notifies the payroll department, and they can rectify those. Otherwise, paychecks don't process. 

Other than that, we have some data migration between Excel spreadsheets that we do, and we have contracts that we host on a web server that, if they don't have transactions for the same period of time, we have the automation go in and close those contracts out so the transactions can't go against them.

My company's major use case for UiPath is to create automations for web and desktop applications. For example, we use it to automatically download content from another page or PDF. It's creating automatic programs to help us download data from the website or application.

We use it mainly for automating customer management processes and to speed up team collaboration. We use many different kinds of software, ranging from cloud services to legacy. We need our team to work between those applications and sometimes data has to be actioned. We were doing those processes manually and, as we grew our business, we realized robotic processes could intervene. We heard of UiPath, we tried it, and we were able to automate our process of working with the legacy system and other software.

We have a mix of attended and unattended processes. We are able to run some of our processes end-to-end, but some processes need moderation. We need someone to attend those processes to complete them.

We are using UiPath as our RPA solution for finance, supply chain, revenue cycle, HR, and IT. At the moment, we're using it mainly for unattended automations of big jobs.

We've used it to automate most of our processes. Our organization is completely technology-driven and we have been able to automate a lot of our processes with UiPath. The main thing that we are using it for is document creation with multiple fields and approval processes.

We're using it to automate daily tasks, using small bots for multiple processes. In the long-run, they're actually connected together. A lot of people have left our organization in the past couple of years and, instead of hiring new employees, we actually try to build a bot for whatever the work those employees were doing.

We have 12 bots in production right now. I can't speak exactly to all the bots. My role is in process mining. With process mining, we're using the PDP process and we're building out a model for sales orders.

We are in healthcare, and the supply chain can be a fragmented process, and now with the Pandemic quite fragile. In recent years, companies have been implementing leaner supply chains to reduce their costs. We found that our best approach to dealing with supply distributions was to create a partnership with a distributor who could provide us with a very large percentage of our day-to day-supplies. We have Central inventories in each of our hospitals; however, we use a stockless operation Monday-Friday. This means we fill supplies for our nursing units on the weekends, but during the week, the distributor is picking, packing, and shipping those supplies in a low unit of measure. Orders are placed electronically by noon daily, and start arriving by late evening. A 'back order' list is sent to us each workday in the late afternoon - too late to do anything with it. 

We did work with our distributor to develop a more customized spreadsheet that detailed each item, by hospital and delivery location. Each following day we would break the file down so that we could e-mail it to each area, to get feedback from them on critical needs.  This took our resources time to prepare and send the next morning. Staff getting the information didn't have much time to review and respond. In addition, we would update each PO line item with the revised 'due date', for back-ordered lines - this was a manual process.  This same resource would then use a tool to send each requestor a 'delayed delivery' e-mail notice.  The overall PO update and communication process took an additional 1-2 hours a day in staff resource time.

With the robot doing this work for us, the vendor sends a file to an address by a certain time. They send it in at about 3:30 PM every day. The robot now takes that file and works that file, which it has ready for us usually by 4:30 PM. Now, it still may be too late for us to work, but the first thing in the morning, we have the file, and the Bot has already sent out notifications to all the users of any backorders. First thing, when they walk in the morning, they know what their backorders are. They didn't know that until halfway through the day before. Now, they get the information first thing in the morning so they can react. Now, we are getting the information first thing and have the time to work with the manufacturers and distributors to come up with other products so that we might backfill or get a branch transfer.

Our end goal was to make sure that we had a daily tool that was 100 percent accurate and could be deployed across a broad spectrum of healthcare workers. Then, they could get information faster and more accurately with as much information to eliminate a lot of extra calls and communication. That is what we embarked on. We dissected our current process and looked at all its different triggers to see how we could turn this into an automated tool. We broke down our process and identified everything that we were doing, then UiPath helped us identify what we needed to modify. We worked that into a tool where a Bot could come along and process it every day, then deliver every afternoon. That was our end result, and it's been extremely successful. We started using the tool last December.

We combined some automation that we already had in this process into this tool to make it a whole automated process, rather than partially bringing it under. We have a vendor who delivers us a report daily of all their backorders because we use the main distributor, so they deliver us a backorder report. Therefore, we made sure that they aligned it in a way that the robot could read it. Then, we wanted to break that down in a way so each of our hospitals could see their section. So, we added some data to this tool which allowed the robot to see that record, and say, "This belongs here, and this belongs here."

We are using Studio and the attended robots, but we haven't implemented Orchestrator yet.

Our primary use is to automate tasks within the accounts receivable, accounts payable, and trade settlement realm that we work in. We're also getting into some more internal audit automation.

We run automations in Windows Virtual Machines. It was a long process for us to get started, getting our IS to buy into letting us set up this environment and get started with it.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a two or three. They offer upfront training, the UiPath Academy, and that makes it easier but you still need to have a technical mindset to understand it, as it is now.

We have all used the Academy. On a scale of one to five, judging how beneficial it is, I would rate the training a five. It's a great experience and very beneficial.

From the point that we purchased our UiPath license until we had our first robot was approximately six months. It took us a while because we had a bunch of other projects in front of getting our first automation. The process was hard, although it was not complicated. The approval process involved going through a security review. 

We are using Orchestrator, attended robots, and unattended robots.

Our primary use case for this solution is in the financial industry.

We do not yet run our automations in a virtual environment.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a four. The whole interface needs some TLC because it can be a bit tricky.

We have used the UiPath training and it has improved a lot since we first tried it. When I used it a while ago, it had its problems. I think it came due to the fact that it was not developed by native English speakers. For example, they had questions that were simply wrong. It has improved a lot and now it is beneficial. I think that the biggest challenge is for them to stay up to date.

From the point that we purchased our UiPath license until we had our first robot was approximately four and a half months.

We are using unattended bots, Orchestrator, and Studio.

We use this solution for doing a variety of things. It includes a lot of back-office finance and accounting, tax, and a little bit on our operations side. We're also using it for some test automation within our IT group, so helping to test our points of sale, and some of our data transfers as well.

Orchestrator runs on a dedicated server, but our bots all run on virtual dedicated machines in our data center. There were some challenges in setting everything up to run in a virtual environment. We implemented a couple of years ago, so I think that it has improved by now, although it was challenging.

Part of it was on our end, where our people were not familiar with it. The challenges included picking the right type of VM to run on, having the right kind of setup, and having the environment configured correctly. We needed this to allow the RPA team to have enough control over the day-to-day maintenance, and not have bottlenecks with the technical side. Managing things when we had issues or needed to add something new was also a challenge.

The documentation was kind of broad and didn't go into the detail that we wanted it to, although I have seen that get better, so that is really good. I'm sure if we were trying to implement it today, it would probably be a lot smoother with the tools that they've come up with.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a four. I think there are still a few things they could do and it looks like they are working towards that. It still requires a good bit of training and ramping up for someone brand new to it, especially without a programming background, to jump in and start building. I think they can continue to refine that and they definitely are moving in the right direction. It's a little bit of a technical hurdle to overcome to be able to build not only just basic automations but enterprise-scale automations and automations that are reliable and can check up on themselves. I think they can work some more of that into the actual tool because we've had to do a lot of figuring out how to build best practices and how to program it directly, and the best way to be able to allow us to support it cleanly through the lifecycle. It is good, but there are some things they can add in to truly make it a five. My standards are pretty high, but I'm sure they'll get there.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. We are big fans of it. I typically don't get the luxury of hiring people with technical backgrounds. We usually have people coming out of school or people transferring from other departments who are interested in RPA. So, the Academy tools have been a lifesaver for us and they've been very good, especially for the RPA developer track. It is very detailed and we can really get someone through that training and feel like they're at least able to perform the basic functions of the tool pretty well. From there it is up to us in terms of getting them familiar with our best practices and how we program things and get some hands-on training with the more senior RPA developer to learn some further tips and tricks. Overall, I'm very pleased with the Academy offerings and they're one of the best I've seen from many of them.

From the point that we purchased our UiPath license until we had our first robot was perhaps a month or two. It did not take long, and that included time for training. When we started off, we bought the software, went through the training as a team, and then started building a few small things. We probably had the first one in production within two months of buying the software.

I'm using UiPath on an automation project for my company in the banking domain. The use cases are for things like insurance claims and debit card transactions. We use it for our clients' requirements and also internally to address any of our company's needs for UI automation. 

UiPath fills the gaps; it's a type of bridge between daily tasks and end-users. For example, on a daily basis, a user may need to prepare and send a report on time. There are many tasks like that on a daily basis that are boring if you are doing them continuously. UiPath can act smartly, eliminate human involvement, and capture everything.

I find the solution easier to use than other platforms and it's a user-friendly way to automate.

The way I'm using UiPath is to create workflows related to financial services. I work for a company called Cedar Financial here in Pakistan. The workflows are related to our data statements, clients' financial documents, and the like. It mostly involves Document Understanding and creating workflows to generate reports. My use cases are restricted to UiPath Studio, where I use the Activities to create workflows and automate some of my clients' work.

Currently, I'm working with the regular UiPath, but in the past, I've worked with UiPath for healthcare use cases.

My use cases for UiPath vary. I've worked with the banking, renewable energy, marketing, and publishing domains. The most recent use case was for data entry, where my company used SAP applications to create orders for the vendor.

My company also uses UiPath to automate processes that deal with courses, such as environmental, employee diversity, sustainable production, etc.

UiPath is set up in my current organization. My organization takes advantage of the vendor's offer for end users to build smaller automation, which is another use case of UiPath.

I work for a software solution company, and its use cases are related to HR products.

We are a gaming company using UiPath to automate some development-related tasks. We integrate the API keys provided by UiPath into our app to extract user data that helps us improve our apps and games. We also use the UiPath application-building solution for Android or web app development.

We are a partner of UiPath, and we utilize their solution for welfare unions and document understanding.

We use UiPath to automate activities that are typically done on a computer by an individual. It's used to automate purchases involving a large volume of transactions for hundreds of organizations. 

We have done a lot of things with UiPath for different customers. I have done Java application automation and PDF automations. We use it for all kinds of automation. For example, for one client, we're working on invoice processing, supply-chain automation, and their technical services.

Our use cases are a lot of both data scraping and data reconciliation. We tend to find that we're going into web portals, we're going into spaces that require a user interface, and extracting some kind of information or data from those places. Then, we transform them. Sometimes it's just as simple as saving it as a different type of data. Still, it can sometimes be rather complex to combine that data with SQL queries to enhance it, or even just clean up and remove extraneous data that our users don't need.

We touch on other areas, such as averting risk by double-checking things or replacing manual transcription. We find that due to the size of our team, we're relatively small, and the biggest bang for our buck tends to be in the data reconciliation and gathering.

Our client wants to reduce their manual work, so they feel an automated solution would work better. The company has one staff member who is well-versed in automation, but they wanted us to suggest more solutions. We decided we should stick with UiPath since they are familiar with it. It's a local community bank with many feeds at the end of each business day. They have about 50 agents handling those feeds.

The client caters to poor people in the community who tend not to trust banks. The community bank sends agents into the fields and shops. They show them a card and suggest that they save a certain amount of money each day. They collect it and take it in a book. They then have to bring the book back together with the money. They're helping the poorest of the poor to save money. Based on what they've saved, they can get a loan. 

The bank encourages customers to save, so they collect daily. They were bringing this data back to the office and entering it by hand. We showed them that UiPath could do all that for them.

We prefer a cloud-based solution because we are a digital-transformation company. However, the client wanted to keep everything on-premises, so we needed to show the benefits of migrating to the cloud. In Africa, power is a problem. Energy costs a lot, and power outages can disappoint customers. In the end, we won them over by showing them the advantages of the cloud, so UiPath is deployed on the cloud. It's highly available, and they want their data to be accessible all the time.

We have about 30 UiPath users, most of whom are IT Administrators. We use the generic term IT Administrators. The company is structured so anyone can be deployed anywhere at any time. We use UiPath extensively in the particular scenario that necessitated our initial use. If we get more clients seeking to reduce repetitive tasks, I believe we will continue to expand our usage. 

We're a blockchain company that provides finance and analytics solutions, so we have multiple use cases, including organizational process automation. We do some end-to-end automation and automate some repetitive tasks. In the future, we plan to target some advanced processes like blockchain and machine learning. 

One example of a specific use case is market auditing. We are auditing our sales team and plan to audit our customers. This entails inspecting data produced by two third-party platforms, Salesforce and SAE, and combining that data into one Excel workbook to perform some calculations. We perform some analytics and then export the data from Excel to our CRM. Transferring the customer data to our CRM is incredibly time-consuming because we deal with more than a thousand lines of data. It takes a minimum of two hours to upload all the data to the portal.

UiPath helps us extract the numbers from the CRM side and share them with our marketing and financial team. This involves four processes that we combine into one automated endpoint process. The reduced workload across the three involved departments translates to cost savings equalling about 2.6 FTE monthly.

Another use case is to promote our components, services, and products. We are building a promotions portal that is attached to Excel. The promotion will involve maybe 500 line items and multiple roles. While you can do this manually, there is a significant potential for human error that could mean a loss of revenue. For instance, if we accidentally offer the same customer two discounts, we have to honor that. We haven't had any errors using UiPath in the last six months. 

We have three offices in our country, but the solution is deployed on a virtual machine in the head office. If a branch location requires process automation, we automate that solution at headquarters, and all the infrastructure is centrally managed. The primary users are six people from my team, including me, a business analyst, a developer, and three consultants. There are also two people from another group managing the UiPath infrastructure. 

We use UiPath Action Center, a capability that allows us to engage businesspeople and incorporate them into our automation. In total, we have about 12 to 15 people using UiPath, but some of them have limited privileges. 

We are working with automation, and it is very useful for my enterprise and our clients. We are using UiPath for building applications for automation purposes. Some of our clients are in the banking industry. They ask us to create applications to automate their processes, and we use UiPath for that.

We are an agency, and we implement it for our clients. We are not a direct reseller of UiPath. We manage the marketing services and the operations for some companies, and we provide the service of implementing it without having any contracts with UiPath. It is just a service from us.

It is being used in almost all industries and departments, but we have been focusing on finance and operations, such as handling the orders, getting invoices, reading invoices, and managing the orders. We use OCR to read invoices and process them. We also use it for the service department. UiPath is perfect for service and finance.

It is deployed on the cloud and on-premises.

We use it with ServiceNow for maintaining tickets. Our task works to automate some scenarios such as software updates. In that scenario, there are some repeated steps. We use UiPath with Python scripting to automate those repetitive steps.

We use Orchestrator, Studio, and Robot to work with automation in our finance department.

We are using this product to develop automation in the billing section of our website. We are integrating bots so that they can do the basic listing and then our salesperson can take it from there.

There are multiple use cases. We have use cases for the ticketing system for assigning the ticket, resolving or maybe closing the ticket, and opening a new ticket. We also have a business use case related to insurance. I worked for an insurance client, and by using automation, we could create a policy that is used for testing purposes. If they had a new enhancement or an issue, they wanted to test whether it was working properly or not. They provided us with some raw data, and we tested that.

We use UiPath to automate PDF processing and extract financial and other information from PDF files. We store the extracted information in our database for our orchestration tool to process.

We have used UiPath both on-premises and in all the cloud services. 

The use cases have been really broad for us. We have been trying to go in a bunch of different directions. The use cases started out small with attended automation, trying to automate a bunch of reports for our operations departments. That's where we started just to prove the concept, and now we're branching out into some of the document understanding.

We use UiPath to automate business processes. 

We use UiPath to automate data entries for ERP and CRM.

We automate transactional processes such as sales order creation and PO creation for UiPath automation.

UiPath is one of three automation products that we use to build solutions for Canadian federal departments. We use it for several automations based on the client's requests and tie it with an NLP AI to query a large database of documents and auto-generate responses to thousands of clients.

We have to surrender certain documents to the public, but the documents have to be deduped. We use UiPath to collect those and perform deduplication with another system. 

I tend to use what UiPath offers, but I also have a full AI shop and Microsoft, so we've been using more of our solutions. Their document understanding features have helped a lot. We haven't used any of what I'd call their "Black Box" AI because explainability is super important. You need to understand what's going on under the hood. You can't always fully understand because it's their proprietary technology. We run into issues because we're with the Canadian government and we cannot allow services that are based in the United States.

We use it to automate output from PDFs.

We were looking for robotic process automation and we have been trying the UiPath Community Edition. We mainly need to automate day-to-day activities related to wireless connections, such as our WiFi device registration process. We currently have three to four employees currently doing this process and it is really time-consuming. We want a bot to do these repetitive procedures.

We will be doing the same procedure for server-side configurations as well for repetitive Windows-based processes. We are looking to save most of the system admin headaches.

I implement UiPath for other companies. My specialization is software integration and digital transformation. I also manage UiPath for some organizations. We're a digital marketing agency that helps companies undergo a digital transformation for data and analytics. We help them automate marketing and data analysis for researchers and the organization itself.

The primary use case is to help the marketing department collect data about user experience and interaction. We also automate repetitive IT work and connect it with marketing. In other words, we extract data from the IT operations to use for marketing purposes. UiPath is also used in every department to reduce manual work.

UiPath has workflows and templates for every use case. We use nearly all of them in all departments with pre-configured templates and workflows, but we mainly use UiPath for IT operations, marketing, and finance. And the three are our primary use for it. We build the procedures and generate automation. We use public, private, and hybrid clouds, but we mainly use public and hybrid clouds for our services. It depends on the client, but sometimes it's private. 

We are a financial services company, and our primary use is to increase daily efficiency and create automated solutions for our operations team. Our primary concern is time. By implementing a robotic solution for mundane tasks, it frees up our teams to focus elsewhere. For example, going to a website, extracting data, putting the data somewhere, and manipulating it can all be automated, freeing up the team to focus on data analysis. This makes us more time and cost-efficient. 

As a smaller company, it was very important to us that scale automation would be taken care of by the vendor. It was one of our key points in choosing a solution.

We are handling millions of users' data that comes in via raw formats, like PDFs, invoices, hard copies, et cetera, and we have to capture that data into our applications so that it can be transformed into usable data for the users. We use UiPath to develop bots to analyze and capture the information in the required format, and to automatically upload and enter the data into Excel.

Our primary use cases are within the financing and HR teams right now. But of course, there's a lot of opportunities in the clinical space and with MB services. We have use cases in all of those departments throughout the organization, but right now we are engaged primarily with the HR and finance team.

We have two automations in production right now. We just started our COE and it's been exciting so far. We are building things and have identified quite big end-to-end opportunities. 

I have used UiPath Orchestrator, and we have created both attended and unattended robots for our clients.

We have been using the new AI and OCR technologies with UiPath, and we are currently trying to implement the Citrix log capability that was recently introduced.

We are not running our automations in a virtual environment. When we automate any Citrix-based application, it's all email-based. There is a Citrix receiver and we communicate with that, which helps automate Citrix applications much faster.

Most of the clients I had seen have been running in virtual environments, although I have seen some of our clients running on the desktop. We have also seen hybrid scenarios.

One thing is that virtual environments can be standardized pretty quickly. So, that's an advantage. Normally, the companies, which are leaning towards more cloud now, will be happy with this. So, I think that is one factor. As you move virtual machines to the cloud you can migrate your bots to the cloud faster.

I have worked on various different domains including the public sector, commercial, healthcare, energy, utility, and federal. These are the different customers for which we are implementing solutions. Now, the customers are moving towards AI and natural language processing. They are more into chatbots, how they can use artificial intelligence, making use of data science, and putting more machine learning on board.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate it two and a half. I'd say it is about marketing. You can develop anything. There are very small processes that you can develop with having minimal experience. However, when you start implementing complex processes, I would say you need to be a background developer.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. All of my team members have been using UiPath Academy for training and certification. It's not just with the U.S., but outside the U.S. as well.

From the point that a UiPath license is purchased until the first robot is ready totally depends upon what use case we are implementing. There are different methodologies that people use. Some build the bot without exceptions and it can go to production. Like a very simple process can go to production in two to three weeks. A more complex bot will take eight to ten weeks, and depending upon the process, it can go longer. I have seen tasks when a human is performing the job and it takes him around twenty minutes per transaction. But, when the bot comes in, it actually completed that same transaction in five minutes. But, to develop that five minutes of processing, it was understanding system availability and testing. Then you have to do load testing. It takes ten weeks or so.

Our clients decide to implement RPA for several reasons. The first reason, of course, is to have work completed faster. Second, when there is a workload, you can work on it more efficiently and with fewer people. Consider an open enrollment in October, where the open enrollment starts at 10:00 AM and there are a lot of transactions flowing in. Now you have to hire a human and train them. With the bot, we can just scale up instead. Finally, the bots are errorless.

We are primarily automating business processes from SAP applications and a few from a web-based application. 

We are using UiPath to automate many processes. In my first job, I worked on billing and ticketing. We were automating the process for ticketing and billing for audit. The robot was responsible for auditing the process of an application. It was responsible for calculating the difference between the amount deposited by the visitors and the amount calculated and predicted by the application. It would then decide if it was the correct currency or not.

Currently, I am working on many applications, but the classic ones are where we are reading data from Excel or databases and then clarifying the data or closing some billings. I am also working on the process of taking some reservations on some sites.

I also sometimes use it to automate something on my personal laptop.

I developed several use cases using UiPath. One involved website scraping, where I extracted data like temperature, humidity, and pressure for various cities from a specific website and displayed it in an Excel sheet. This was a small project, but my main focus was a prototype for a client: digital marketing automation. Using UiPath, I created an automation to automatically post articles on different social media platforms.

I am a mechanical engineer, and I am in charge of seeing various production processes. We have various equipment and systems. Sometimes, they were unmanageable, and we used to experience breakdowns because of poor maintenance or poor management by our staff. That is what prompted us to try automating the systems and making them more efficient. That is why we acquired UiPath, and we have been using it to automate various production and design systems and processes.

I have been using UiPath for automation purposes. I have designed processes for various business requirements in the insurance sector, such as policy comparison, application contact confirmation, and underwriting notes.

I have been mostly designing processes for clients' purposes, but I have also designed processes for internal business logic and other purposes such as HR automation to help HR. We have automation where all resumes get downloaded in the local folder. We grab the information from the PDF and store it in the Excel format.

We use it for various purposes like account management, finance, HR, and procurement.

I develop RPA processes at a financial services company. We use UiPath for tasks like data entry, image processing, and reporting. 

We use the product for contact center, HR, and airport operations. 

I work in the financial sector, so my organization mostly used UiPath for disputes, fraud, and chargebacks. My organization had a pretty straightforward use for the tool as it had rule-based manual processes that required automation; otherwise, the organization had to hire temps for manual tasks. My organization used UiPath primarily for fraud and dispute bots, and chargebacks.

We use multiple types of applications, including SAP. I work on contract documents with UiPath mostly. I work with different clients in different companies. We use the solution to automate processes. It helps by reading contract documents and updating details in SAP applications. 

I'm using one or two robots. We use the solution for reports. We have another software yet we don't have support. Instead of pulling reports manually, we use the program to get the reports and pull them for us. 

We use it for automation with different applications and use Document Understanding, AI Center, and Action Center.

We use UiPath to automate the repetitive reporting tasks in our organization. I am currently using UiPath for five Oracle-based projects.

We use UiPath to automate routine tasks in our organization.

We use UiPath for data scraping to extract information. Specifically, as a financial institution, we gather financial information from various websites. UiPath helps us extract the required data from these web pages. Additionally, we have another use case where we track tickets for vehicles here in Guatemala. Furthermore, we utilize UiPath for internal processes, such as generating reports and publishing information on social media.

I work at a large retailer and we use UiPath to support the HR and e-commerce departments. For example, we can automate the management of HR tasks, such as scheduling training courses for associates. We have around 500 bots running in production. 

We do not have any specific use cases for UiPath. We automate areas where we have a large volume of work.

We do workflow automation for some of the functions such as form-filling or filtering data accession on the client's web application. We use UiPath RPA for data accession and other processes. We have done workflow automation that:

1. Opens a client's website.
2. Filters out the current data.
3. Lists out all the records that need to be processed.
4. Opens each record.
5. Enters the details gathered from a spreadsheet or somewhere else.
6. Submits the application. 

It does that for all these users that have been filtered out. That's why we're using UiPath.

I'm a web developer. This solution is used in the backend and frontend of my organization. 

The solution is deployed on cloud through AWS.

We mainly use UiPath for automation testing processes. I am from delivery and project management, and I have a team member under me who is developing automation processes for me.

We use UiPath for intelligent automation integrated with machine learning models.

We use UiPath Studio, specifically the enterprise version, for developing projects per organizational requirements.

We're a consulting firm and we use the solution to automate various systems, mostly in data processing, including in the customer service department. We're also using it to take advantage of artificial intelligence.

We use the solution for automation. I have implemented the solution in many ways. Some clients need to send us files via email or through Excel. We are reading and creating the file into some internal systems. 

Some other clients need the solution to read invoices from different vendors. We get them from Outlook email and fetch data. 

We use UiPath for document manipulation. It helps us split PDF files, clean and submit them to the government website. 

We generally use UiPath for invoice processing, finance-related processes, and other similar processes in the oil and gas industry, including government and child welfare use cases.

My organization also used UiPath to automate processes for a good cause, particularly for a US organization that was into child welfare and adoption, so that was one of the use cases: automation for a child adoption and child welfare organization.

We use UiPath to automate daily repetitive tasks.

We're using UiPath for healthcare use cases. It is primarily used for automating document-related tasks, such as moving documents around, classifying them, and extracting the information we need. 

We primarily use UiPath for automation processes. One of the major use cases is the approval system that we have. Our system goes through a lot of approval and workflow steps, and we have automated the entire process using UiPath.

We automate the entire revenue and order to cash and then process it to payables. It is used for processes, from generating customer invoices to ensuring that all our vendors are getting paid timely. We also use it for data reporting, audit requirements, or whatever information gathering that the company may need.

We've automated about 30-ish processes, and that's just the tip of the iceberg of where it's going.

All of the processes are attended to right now. We're still getting the backend set up to move some of them to unattended.

We have very restricted usage, primarily around integration situations where we don't have any APIs. We primarily want to do just unattended automation. We discourage attended automation at this time. We have ten to twenty processes happening right now.

When I started at my company, they were building their RPA journey. I was the first person to help them do that. As no one in my company was aware of what RPA is, we needed to showcase and publicize what UiPath is and what RPA is.

I work for an insurance company and there are handwritten scripts that need to be scanned in, and this was the first use case that I had to work on. We used the OCR technology to scan handwritten documents and its capabilities are evolving day by day. When I initially started, it was not as robust as it is today. We had some challenges with the OCR technology, but today we are able to do it successfully with validations.

Right now, there are 24 automations of which 22 are in production and two are being built. These are all unattended bots. I also use this solution in a personal capacity to delete all the junk emails I receive as I usually get 20,000 junk emails a week. This saves me a lot of time. 

The UiPath's user community, in terms of the value that we gain by being part of it, is very helpful. If I'm stuck with coding, that is the place I go to get assistance. The ideas and the solutions that they provide are very helpful. There are a few people in the community who are very accurate and their solutions always work.

I have also made use of the academy. Currently, I'm taking the certification training and planning to get my certification done by the end of this year. It has taught me new ways of doing things including dynamic selectors. Previously, the bots used to break because of a selectors issue, but the dynamic selectors solved this. 

My previous company was in the banking sector, and we had done automation with websites, UI, SAP, Excel files, and PDF. In my current company, it is being used for finance and HR. We have ERP, CRM, chatbots, etc. We are using this solution to integrate different systems.

I use UiPath Studio to develop the code, and I use UiPath Orchestrator to publish my work. We have our own UAT systems to test the code. We can install the UiPath in the test environment and find all the compilation errors in the debug mode and fix them. We also have version control. If we upload a version and it doesn't work, we can downgrade the version. Everything is tracked in UiPath Orchestrator.

We are using it on-premise. In my previous company, it was on the cloud, and we accessed it through the cloud. 

We are on-prem within the insurance industry. Our use cases are in auto reports and micro use cases within that.

We have worked on multiple use cases, but most recently, we have worked on a payroll system. Previously, every month, we had to manually get certain details from HR, and we used to do the pay run for all employees in the organization. Now, we automatically extract the required information from the current system by using UiPath. We then prepare a sheet by using Excel, and the entire Excel sheet is processed by a bot. The final sheet is sent for the payslips for the entire organization, and the entire pay report is sent to the bank for payment details.

I have been using it for a couple of different things, mainly insurance-related. As of now, we are using it mainly in insurance platforms, insurance portals, and doing some admin support in terms of the backend insurance tasks.

I've used it before in payroll where it was processing the payroll, generating the payslips, creating the payments for our outsourced invoices, processing invoices, making payments, sending reports to banks, and more.

We are using the on-premises UiPath solution for both attended and unattended bots. At this time, we use unattended bots primarily to facilitate integration between applications, and we are not using the attended bot capabilities.

Generally speaking, we develop integrations for our core banking system, which was written in-house and running on a mainframe. It is a highly-developed system that we started using more than 30 years ago. When it was created, we didn't have the integration capabilities that exist in other applications or core systems, today. This means that in order to have external applications communicate with the core system, we need to develop integrations. Examples of this might be web services or other APIs, and that's why it takes time to do.

We have teams to do the integration, but considering that the core banking system is in Turkey and all of our teams are busy, we don't have enough resources to implement all of our integration projects. Now, for the past three years, we have been implementing bots to handle integration by moving data from the applications to the core system, and from the core system to the applications.

We have a use case that involves an invoice billing process, where vendors from an external organization submit their details for the invoice. This automation works as expected, independently of anything else. It is also a good example of how we were able to scale RPA benefits in the company with the automation of a specific process that requires human-robot collaboration.

Our internal tools include the database where all of this information is stored, and we have a second automation that is used by the billers in our organization to tally the data that includes details such as what each vendor has submitted to get their payments.

We built a third automation in UiPath, which basically compares these first two. But, due to the complexity and the nature of the tally that has to occur, we require some human input in between certain steps.

For these particular steps, we have developed a four-bot configuration. These are four separate bots that run and a couple of them have an attended automation part, where a human can intervene. It's a verification step, where the human can decide whether or not something is okay. Specifically, the bot compares two fields and if they match, then it's great, but if not, it triggers a request to a human user for manual verification. If they approve then it is marked as a successful verification.

Because we use technologies like OCR, there are details that cannot always be interpreted properly. This is where we need an additional check, which is the reason that we have humans in the loop as part of the process.

We are developing processes with UiPath for clients in the government and banking sectors. 

I am a consultant working on RPA solutions in general. UiPath is one of the solutions that I am using.

The use cases depend on the clients. I have done automation of sending mail with invoices in it. We have used it for analyzing PDF documents, getting information out of these documents, preparing in three different languages depending on the client, and sending invoices by email.

We are also checking VAT numbers on the EU side to validate the client's VAT numbers and related data. We have automated the generation of reports out of SAP for two different managers and teams. We have also automated including specific signature images within PDF documents and sending them to the related service or email address.

We have mainly used UiPath to focus on processes related to the finance department. The targeted processes are the ones that are the most repeatable and require a lot of effort but there is no real focus and attention from the user. Because of its repeatable nature, the risk is that users do not pay attention to the process itself and make mistakes.

Generally, we do not implement end-to-end automation. The idea is not to automate an end-to-end process but to automate a part of the process that takes a lot of time and resources. That is the focus point, so it is not a matter of having an end-to-end process implemented. It may occur, but often, it is a part of the process where the focus needs to be reliability or time and resource consumption.

We're a tech consulting company that works for insurance companies. We use UiPath for tasks related to payment processing, deductibles, and denial of coverage. We check each part of the process to ensure that the patient has met a set of criteria. We're checking the deductible to see if it has been met, and we update the notes on the platform. UiPath is useful for all of our clients regardless of the industry. For example, we have used it for payroll and payment processing at Citibank and Doshi Bank. 

One of the use cases I've worked on involved uploading a small book containing mathematical formulas, images, and other content to a website. We converted the book's introduction into an XML file and utilized UiPath to seamlessly upload all the information onto the publication website via a step-by-step process using notes.

Another use case involved generating reports by scraping data from specific websites, particularly in the banking sector. The information gathered from one website was then uploaded to another website. These automation tasks included handling schedules, duplicative tasks in Excel, and automating financial processes. This encompassed tasks such as fetching data from databases, manipulating the data, and updating the database accordingly. Furthermore, reports were generated and distributed to users both via email and Excel files.

The automation processes also extended to extracting data from various sources, such as PDFs, images, and tables, showcasing the versatility of the automation solutions implemented so far.

While we haven't incorporated AI or machine learning into our automation programs yet, I have acquired knowledge about these technologies through the Academy.

The primary use case for document processing, automating data extraction from previously hard-to-access documents. This saves time, reduces manual work, and makes hidden data more accessible and usable.

We use UiPath to automate various processes across different functions within our organization including back-office operations, with a particular emphasis on finance, procurement, HR, and IT, as RPA technologies initially emerged from the finance sector.

Also, we extend our automation services to areas directly associated with production and supply chain operations.

We have a variety of use cases, primarily in finance and HR, which make up around seventy percent of our use cases.

We use UiPath to automate the extraction of information from PDF files and populate websites with this data. 

Our primary goal is to save time for our business users, allowing them to focus on more engaging tasks instead of manually clicking and inputting information on various websites.

In my last company, we focused on Document Understanding. We received medical claim forms through Outlook and extracted the data from them. That is one use case. At my current company, I'm doing SAP automation.

I use UiPath to automate getting the relevant data from Excel and PDF files and for normalizing the data.

I use UiPath for PDF automation. About 10 to 15 employees use this tool in our organization.

We did AP automation. We started with AP invoice automation first. Then we did a proof of shipment delivery. That was the second concept. After, we expanded to the inputting of contractor timesheets. We moved to publish the metrics on a dashboard and log in to different databases. Slowly, the demand picked up in the last year.

We have about 180 bots we're doing now. I think the most interesting one we have is an underwriter bot. It collects information about a person who has just applied for a product, and it does research for the underwriter. It does financial research and medical record research, and it compiles all that into notes for the underwriter. It actually gives them a recommendation on how to proceed with the application. We do all sorts of use cases, including financial and claims, and have a hand in everything that MassMutual does.

We can use UiPath for pretty much anything, including document reading, day-to-day processing, or maintenance cases. For pretty much anything that the business comes up with, we can use UiPath. 

We have quite a few use cases, and a few big ones are creating purchase orders, reviewing invoice PDFs and extracting information from them, and creating customer orders from forms that are emailed in.

We have implemented a couple of use cases. One is with our creative collection scenario. We are also working on order automation. That will go live in October.

Our company uses the solution for documentation understanding, email automation, and onboarding. Many of our use cases include AbbVie. 

We implement automation for clients to create savings by cutting the number of FTEs. We've used UiPath for various kinds of automation, including mainframes, browsers, Excel, account payables and receivables, fixed assets, healthcare projects, HR projects, reporting robots, and IT services projects. 

Recently, we did a massive US taxation project that spanned eleven months and covered enterprise and individual taxation extensions. It was a huge project that yielded a lot of savings. 

If I want to leverage a specific UiPath use case, I build small use cases around that particular feature and try to envision a product out of it. I've had several hackathons and general discussion calls because I'm a solution architect. Everybody wants to work on apps, and UiPath is comparable to the blank canvas apps that Microsoft PowerApps provides. 

We are using UiPath for automation processes in an insurance company in the finance department.

We primarily use the solution for operations processes in our corporate investment bank. For example, screen scraping, querying from databases, or any transactional processes. Those are what we're really looking at the most.

My experience in using UiPath, in general, is in developing traditional bots, assisted bots. There are the typical mundane applications that we're trying to remove in order to add value to customers. 

The solution is used for extracting information from documents and consolidating data, maybe from various Excel sheets. I've used applications, such as PDF, Tableau, and a number of different entities as well. It varies.

We are using the solution to create application reports. What we've done is take all of that information, where somebody was initially doing everything as it happened, and create templates that work in another application. Due to our business model, we have multiple applications that are similar but very different. Rather than have somebody go into this application and update it and then go to another application and put in the same information, we've developed bots. We'd go to the template, input the information one time, and let the bots go in and open up the other applications.

I am a software developer and I am a full-time RPA developer for my company. We create automation for internal purposes as well as for our clients.

I have implemented 15 to 16 processes end-to-end that cover use cases including Excel, front-end web-based applications, backend Windows applications, and sometimes Citrix. I have also done some Adobe Flash Player automation.

The REFramework (Enhanced Robotic Enterprise Framework) is what we use for most of our use cases.

We are using Studio for development on-premises and we use Orchestrator in the cloud.

We mostly use UiPath in the healthcare and banking/finance sectors. Our use cases depend on the different sectors we use it for. A typical use case would be an Excel file with lakhs (hundreds of thousands) of records that we need to filter and apply some business rules to. We may have to check whether numbers are in integer or alphanumeric format so that they can be accepted by a particular application, or whether date data is formatted correctly.

We use it for end-to-end automation. We take all the input from users, regarding the full life cycle of a process, and use UiPath to create a business solution. An end-to-end project can include taking an Excel file and putting the data into a data table. Based on that, we create some business rules, check things with validations, and then create some templates. We upload the templates for different legacy applications so that they can be automated. A bot will run these scenarios in the backend, in either attended or unattended mode.

The primary use case is the automation of many reports, dashboards, and tables that were created manually by some of my colleagues. The tasks involve collecting information from SAP Solution Manager, manipulating some of the data based on business rules that have been implemented, and then storing the data in a specific way that can be used in the next part of the workflow. This includes using Excel and the aim is to create a PDF report that is sent to the top business line managers.

UiPath is the perfect tool to implement a solution like this, with continuous operative tasks between Microsoft native applications such as Excel, Outlook, and PowerPoint.

We primarily use UiPath for end-to-end automation. We develop both attended and unattended bots and we use the Orchestrator module, hosted in Azure.

Some of our typical use cases involve automating operations like downloading files online, analyzing and capturing details, saving them in another location, transferring them, and uploading them in other forms.

We are using Orchestrator and robots.

Our primary use for this solution is Accounts Payable invoice automation.

We run automations in the virtual environment provided by the Amazon service. Our implementation has been finicky at times. The latest release is a lot more stable, but I've had a two-week production outage where DLLs weren't registered and someone from Vegas had to log in for eight hours to our servers. They had to uninstall and reinstall the solution, as well as all of the different apps. I lost a bit of faith in the solution with that incident.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate it a four. It's pretty easy to use, but it wouldn't be a five because it isn't doing everything for me. Things still need to be done.

I have not taken the Academy training but my team has. On a scale of one to five, judging how beneficial it is, I would rate the training a four.

From the point that we purchased our UiPath license until we had our first robot was approximately two weeks. The process was pretty straightforward.

We're starting within our finance group, so a lot of different processes in our finance group are being automated. Our main project was for our tax department, extracting data from PDFs and putting them into Excel.

We have two people involved with RPA in our company.

We just purchased this solution last week so we're still installing everything. We did automate four processes with the community edition. The length of time in development varied by the process. The longer ones required help from UiPath. They came on-site for the PoC, so that helped us out. Some other easy ones we just did ourselves within a couple of days.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would say that it is a four. But with Studio X, I think it will probably be a five. I say four because as you get more complicated with your processes, you need to learn how to code and there's a brunt learning curve. A lot of people will get turned off by that. So, I made some good sessions with Studio X, it's all drag and drop, mostly, so that's perfect for the business users.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. We are actually in the process of taking it right now. It's good that they have something like that available. There are not that many who have aced it.

We are a partner of UiPath and a system integrator for our clients.

For most clients, we tend to begin by focusing on areas with the highest potential for automation. This typically includes finance, procurement, or HR functions, with the first two being the most common choices. These areas are chosen because their processes are generally stable and repetitive, making them ideal starting points for RPA implementation.

However, our experience doesn't end with just one client. We've had numerous engagements, including with large, multi-company groups. Once one division like the "glass division" successfully implemented RPA, it often sparked interest in other divisions like the pharmaceutical division. Demonstrating a solid proof of concept makes it easier to scale the technology to diverse use cases across the organization.

Ultimately, overcoming the initial hesitation and showcasing the tool's benefits is crucial. Once the value becomes apparent, a shift often occurs, transitioning from a client-driven demand to a proactive push from various departments eager to eliminate tedious manual tasks.

UiPath provides a platform for building, managing, scheduling, and monitoring automated processes. We use it for various processes, such as cost analysis, repairing permissions, and manipulating Excel data. 

I automated the use cases related to medical processes such as posting the payments, downloading the files from the portal, and claiming medicals.

I have worked on use cases for three domains, which include the banking, health care, and insurance domains, and designed bots for automating processes.

I use UiPath to automate my client's PDF files and emails.

We leverage UiPath for customer service use cases and process automation to improve employee productivity and reduce time spent on repetitive work. UiPath is mainly used for financial processes like automated invoicing, but we also use the solution for IT processes. 

UiPath is deployed on-prem on a private cloud, and all our BFSI customers are on-prem. BFSI customers tend to use fully on-prem environments. UiPath offers cloud and on-prem versions, but the functionality is the same. A few technical aspects are a little different. 

We use the solution for building automation. 

We have been using UiPath to automate regular activities for a business. I'm currently working for a vendor that has a contract with a business. We are using the UiPath solution to automate all the activities that they have been doing on a regular basis. These activities have simple functions, mostly with Excel data entry and some internal applications that the client needs.

So we use UiPath to take some input, and then we process the activities for the business. Then, we share our output with them as a report on a daily basis or a monthly basis.

I am the head of a division of IT that supports clients. We deal with various use cases in banking, insurance, and retail.

I've used the solution within the healthcare system in the past. At this time, I use it for mortgages. 

I use the solution to automate any digital processes that have specific rules and steps to follow and can potentially save the company a lot of time and money.

I utilize UiPath to automate the majority of tasks that we previously had to implement manually.

My main use case for this product is process automation. For example, we use UiPath to make quick and easy applications for our internal office use.

We use it mostly for reconciliation, automatic emails, and monthly, quarterly, and yearly reports and extractions. Document Understanding is another big use case for us.

We use it to transfer information from one system to a government system.

We also use UiPath to automate processes that track mileage on vehicles, which would then allow us to calculate some of the GHG emissions.

We have a team with a set of developers, business analysts, and managers who are constantly looking at processes within our organization that we can automate to ease the burden of our employees. Our use cases align with departments like finance, inventory management, and HR. They include all the corporate level and core processes within our organization. Most of the automations are unattended.

A simple example would be that we have sales reps who get orders from customers. Those reps have to use some of our internal systems including our ERP system which is SAP. They use the systems to create orders and generate sales order numbers, invoices, et cetera. I have worked on these processes wherein we automate all those steps for them so that they don't have to go through the basic steps and do the same things for different orders.

We generally work on integrating it with our support ticketing system, which is ServiceNow. That way, we can standardize our input and get better results. It has been working really well for those kinds of processes.

Our company is in the insurance industry and uses the solution to run RPA processes for the claims department to free up staff time. 

Our company uses the solution to automate used to be a completely manual set of processes. 

We work as a center of excellence and we develop automations centrally for other departments. All our deployments are unattended bots that are deployed and managed by us, centrally. They are all running on a virtual machine. Nothing is running on client computers or laptops. We do not have any attended use cases. The process owners are interacting with the bots.

We use the bots for a lot of reporting, including monthly and weekly reports. We are a construction company and we have a lot of reports for all kinds of things, such as construction projects, different construction sites, and various subsidiaries for regional departments. A region like Bavaria, for example, needs its reports. And there are plenty of controlling departments in all of the subsidiaries.

We also have some ticketing use cases. One of them is for IT services, meaning internal ticketing. That bot regularly checks our ticket software and automatically processes some of the tickets. For example, when an employee needs rights to a specific system, the bot checks whether they fulfill the requirements and approves or declines the ticket.

Another type of ticketing use case is more about processing customer tickets. As a construction company, we also do facility management, and that means there are a lot of external customers with their own systems in which they record tickets. The tickets are not visible in our local systems so someone has to go to the external systems, export the tickets, filter them, and then tell everyone what they're supposed to do to their buildings as a result. The tickets might be about small repair jobs, for example. We run this daily and, in the morning, everyone receives an email with all the tickets that have to be done within one day, three days, one week, et cetera.

Both of the ticketing use cases are connected with SLAs. If you miss a certain time frame before processing a ticket for external customers, you have to pay a penalty fee. For the internal tickets there are SLAs for internal tracking purposes. Because those tickets have to be processed within two hours, that bot runs every two hours and checks for new tickets.

Another IT services use case is for getting access rights to local drives.

We also have many recurring processes. For example, in HR they have to go to the system and confirm a process. It’s a necessary evil which is probably due to the legacy systems we have. Someone defined this process a long time ago and it still has to be done.

We also have use cases in finance and treasury. They are not tickets, but they process requests from employees. For example, they can request cash on a specific card and the bot will check the emails and then basically transfer data from an email, or from a PDF form attached to an email, and enter it into the finance system.

One last type of use case is where the bot works as an interface between systems. Data has to be exported from one system and imported to another system and there is no existing API. The bot exports and imports the data. We have one bot that exports PDF documents and sends them to an email interface. It defines a specific subject and then attaches the file. That file will automatically be uploaded to another system. Or the bot may log in to a system and upload the document. These use cases are due to the fact that there is no interface between two systems and they're either not big enough to develop an API or they may involve an external customer system and the customer has no interest in providing an API.

It serves our day-to-day work. The product is used for robotic process automation. We have some manual tasks that we need to automate so that we can save our organization costs and manpower, and we use UiPath to help us do this.

We are partners of UiPath, and we are also programming for them. We are using it internally in our group, but we're also using it to develop automations for our clients. 

In terms of its use cases, we have implemented several automations in financial departments, mostly related to preparing reports, but UiPath is not limited to that. We also had use cases in HR departments for calculating bonuses, for instance, for large companies with more than 1,000 employees or for centralizing the hours worked at certain building sites for a construction company, etc. 

We automate whatever a client needs to be automated. We will discuss possible use cases with a client and prepare a short evaluation regarding the costs and benefits, then it´s up to the client to decide.  

UiPath develops increasingly towards cloud solutions. We still have clients who prefer to have it on-prem, but new clients will mostly opt for cloud solutions. The clients decide on the cloud provider, and we basically use whatever the client wants. 

Some of our use cases for UiPath range all the way from development to operational support through to business enablement. Our biggest focus internally is to enable a business to do what they do best. We generally provide solutions through the use of UiPath to cater for streams, e.g., Procure-to-Pay, Hire to Retire, and quote-to-cash.

We are using it to build solutions that can heal themselves. So, we make sure that our operational team is aware as soon as something fails with the processes that we have built. If one of the use cases or failures has already been listed, we note the fix and try to implement that. If that doesn't work, then we hand it off to a human to look at the task. 

In terms of some of the use cases that we have in the business, we do quite a lot of ERP automation. So, we work with SAP quite a lot. We also have a lot of back-end data that we need to bring in and process as well. So, we use our SQL databases to perform tasks, e.g., allocating payments to bank accounts in our ERP system.

Because our development team is rather small, we try to create as many reusable components and solutions on the UiPath platform to make our day-to-day jobs a lot easier.

Our primary use cases are in our financial department. We had a bit of a downturn, but we still had work that needed to be completed. So we developed several automations to manage a lot of the financial work and a lot of our payment processing systems. We expanded that out to include more of our traders' work processes, just because we saw there were a lot of workloads coming in and a lot of repetitive work. So we used UiPath to eliminate a lot of that for our commercial traders, then we did the same thing for our operations and production teams so that they have their own automated processes.

We plan on scaling it and using it in more functions.

UiPath was used in-house in my first company for automating processes. We had deployed it on-premise. In my current company, we are giving UiPath automation as a service. We help companies with automation. We set up UiPath from scratch and help them achieve their automation goals or strategies. As a service, we have done on-premises and cloud deployments.

From a service perspective, we deal with a lot of clients who are predominantly in the oil and gas sector and energy sector. They have SAP systems for their ERP, and their use cases mostly revolve around automating SAP processes such as invoice automation, joint venture reconciliation, balance sheet reconciliation, and intercompany netting. So, the use cases usually revolve around the finance tasks, but sometimes, we have also seen use cases related to the supply chain and planned maintenance, such as purchase order closures, work order closures, and comparison of the work order plan with the deviations. 

In terms of the version, we always have the latest version. I've also used 19.4 and 20.4 on-premise versions.

We have a cross-platform infrastructure, where two servers are sitting. We have Orchestrator, which we connect to our virtual desktop infrastructure (VDI). In the VDI, we have a UiPath stationed. 

From India, I work for an Australian client. Previously, I worked for a European client. In order to work with the client network, we have a dedicated Wipro laptop. In that Wipro laptop, we log in and connect via the VDI. In that VDI, we have UiPath Studio. Using UiPath Studio, we are doing development for the client and automating functional business processes.

We are extracting data from Salesforce using a particular report that is sent by the business SMEs. We pick exact fields end-to-end, then we put these values into Salesforce. Next, we extract the value and data from Salesforce, putting that into an Excel application. After putting the return to Excel application, we generate a service request for the business and send transaction reports of the bot's performance and accuracy at the end of the day. The business was taking around four to five hours. Our robot takes around eight to nine minutes in order to automate this end-to-end automation.

For another use case, there is an application that submits invoices for an insurance client in Australia. Right now, the business is doing this. Whereas, the bot operations reads a file on the hard drive, picks up that file, and puts it into SharePoint where the bot performs some operations. After doing those operations, the bot will report the status, whether it is valid, invalid, or an exception. When we get the file, we develop the application that submits the invoice. After that, we capture the data from the Excel application and submit a request. This is an end-to-end process. This bot only runs after business hours, five days a week, so it doesn't impact the application. With this process, we send daily transaction reports, the success ratio to the client, and present the entire picture to our peers and business holders.

We have set up our own cloud, which is internal. UiPath has a different cloud. Per our governance, we are not allowed to use another cloud. We are using our hosted internal cloud, which is hosted on our internal servers in Australia.

We provide RPA services and I am currently working on two different projects.

These projects are for two different clients that are each using a different version of the platform. In both cases, it is an on-premises deployment. Our clients only use the end product and don't do any development themselves.

One of my clients is a retail organization and the primary use case is invoice automation. Previously, the process was totally manual. They have different products and different departments and for each and every department for which they bill, like HR, there are printing and supply chain tasks to be completed. As part of their process, they generate invoices monthly.

To generate invoices, they need to gather data from different sources, such as a database or Excel files. What we have done is fully automated the process. They now only need to work with a consolidated Excel sheet and then email it, once complete.

Once they send the email to a particular email address, the robot retrieves it and reads the attached Excel sheet. After doing some cleaning, consolidation, and validation, it generates invoices each month in a particular template, and then it submits them to the EBS portal.

The manual invoicing task used to take between two and two and a half weeks. Now, they start it at 4:30 when they leave and it works overnight. The process is now fully completed within two days. The time saved is now time that can be used to focus on higher-value work. It has also improved employee satisfaction.

We are a small but global company. We are about 1,200 people. We are a logistics company, and most of our employees work in our warehouses. So, our office workers are somewhere between 400 to 500 across the globe. Being a logistics company, we are maybe a little bit old-fashioned. There are a lot of papers going back and forth, and we are trying to automate different scenarios. We cater provisions to ships, so we are basically a grocery store for ships. 

One important thing is when a ship is going into port somewhere, they put in an order for whatever provisions they need for when they leave port again. So, we need to be quick at expediting their orders. When they put in a request for a quote for whatever products they need, we need to respond very quickly, because the tendency is that whoever responds first gets the order. So, we want to do that. We are trying to sort of increase the speed of those types of operations as well as the quality of them. 

It is hard to really pinpoint what it is we are doing, but it's the communication between customers. When we receive a communication from a customer, we want to move the process through our company as quickly as possible and with high quality.

We are fairly new to UiPath still. We do intend to use it company-wide and have started out with purely unattended scenarios so far.

Originally, we were using UiPath to draft documents and send emails on mass to where we had large communication exercises. We used a robot instead of a small army of paralegals to generate the documentation and draft up the emails where we had to communicate with 2,000 to 3,000 people. It was a little bit more involved than just doing a standard mail merge, but we were able to use UiPath to create a number of documents and email it to an individual customer, all through a central email address.

Fast forward to where we are now, we have a few of these things focusing in on what we call post-completion activity, like the things you do after you sign a contract. So, it may be you're uploading it to the client's contract management system, applying stamps, or registering the contracts in an official register. The robot is able to do that for us post-completion. Those are our primary use cases at the moment. We're looking at more data integrity type stuff, like comparing our internal data sources against public record.

We are automating back office business processes focusing on business finance and tax, specifically. We are just recently starting our implementation, but we have been doing a proof of concept for the last year or so on the community edition. We recently signed the license agreement will be moving forward with implementing it full-time.

I am functioning as a lead developer. 

My company delivers projects to clients based on their requirements. We use the tool for web and UI automation.

Our company is considering UiPath and Automation Anywhere for automating a mainframe application. I have explored UiPath, evaluated its capabilities, and completed a use case.

We had two distinct automation needs. First, we aimed to simplify the process of obtaining weekly updates on new employees. This involved automating navigating a portal, identifying new employees, and distinguishing between contractors and full-time employees and aims to streamline maintaining an accurate and current employee database for your company. 

The second use case focused on case number categorization. We needed to categorize cases originating from sources like SSM, DC Salesforce, and others into different categories, such as origin-related or finance-related, to prioritize and address them based on their urgency and type.

We use UiPath to automate simple, everyday processes like email automation.

We have deployed UiPath both on-premises and in the cloud.

We use UiPath in all business areas like finance, HR, accounts payable, production,  etc. 

We are primarily using the solution to automate manual processes for users. The solution helps reduce their efforts. We connect it to databases and do web automation.

The use cases depend on the processes. The processes we have so far have been complex. It took almost six months to complete each process. We required four developers per process. We have been working for the same client since 2021. Before this, we worked for other clients and automated almost five to ten processes, but they were not critical processes like what we currently do.

Our use cases are generally related to front-end UI-based automations that emulate tasks done by teams. For example, we do front-end SAP automation for data entry and scraping or posting data to websites that are related to the organization. We use UiPath for other automations like extracting and manipulating data from Excel. The primary use cases are in finance, HR, and operations. In logistics, it's used in full-sprint solutions.

I work on database automation. We just delivered a dynamic workflow in an Excel automation as well. We work on many types of formulas. In addition, we develop physical automation. For example, we created a process that posts many photos at once on many groups.

We are a distributor and most of our customers were manufacturing and financial companies, so the use cases fell into categories like financial, accounting, and procurement departments. We used it to improve business processes.

Our primary use case is for RPA. We use it for checking invoices and sending out electronic letters. It is also going to check the absence entered by people when they are sick and see if those fill-outs are correct.

We use it mostly for the banking and insurance domains. We are a service-based company and the tools we use depend on our clients' requirements.

I did a proof of concept for a music industry client. It went well, and the client adopted UiPath. 

Our biggest use case right now is around business development. We use UiPath to run reports that we get off of the internet against our internal databases to try and find anyone who is a client because we're a law firm.

Most of my development right now has been on the business development side. We're helping clients with their cases, whether it's a litigation case, a bankruptcy case, or a real estate case. I use UiPath to help identify potential clients or current clients so that we can help them in their legal space.

We're currently rolling out some of our first few automations. So far, it's been in finance and procurement. We're just automating some of their inventory processing workflows.

The automation will be unattended. We have three that are in active development and another six in backlog awaiting development.

I use this solution for mortgage loan origination, loan servicing, and IT administration. I'm currently using version 21.

We use the solution on-premises.

Our primary use case for UiPath is the automation of some of our processes. The main departments that have been affected are accounts payable and accounts receivable.

We are developing expertise internally. At least for the first year, we worked with an outside consultancy to provide us UiPath development. They were working with the business team here closely, but also helping to train our people.

The main parts that we've got are in the area of invoice automation, but we also have some bots that deal with the automation of some of our engineering applications within Oracle.

We run six bots, primarily dealing with invoice automation from our suppliers. That is working in conjunction with Abbyy. So, part of the process is UiPath and part of it is Abbyy FlexiCapture. We also have some engineering applications in Oracle that we also use it for. Examples of this are updating bills of materials, or printing out invoices.

The key savings and kind of the real business case of the project were to do with invoice automation.

We have a web application, and we also have iOS and Android applications. We are automating the regression testing part for these applications. Mainly, we are navigating and interacting with UI elements, and we are verifying certain buttons. We are also verifying certain data with RDBMS outputs.

We are using it to automate various tasks of mortgage onboarding.

We use UiPath Assistant and Studio. We are using the cloud version. 

We primarily use the solution for the typical banking and transactional use cases. An example could be something such as homeowner's association transactions. That incorporates multiple departments in a bank, including treasury management accounts and opening an ACH. All of those areas are very transactional in terms of the rules-based processes that they follow.

We also use the solution for wire transfers. We have a lot of those. Then, from a business perspective, we look at lines of business as well. It can be used for residential and commercial lending. It's very process-driven and very transactional. We're able to incorporate automation in those areas very easily.

We have around more than 300 bots that are active right now. All the automation we have is based, basically, on Oracle and Oracle ERP. We have other automation as well, however, for now, I am focusing only on Oracle-based automation.

We have so many other use cases that we want to implement within our organization. We try to look at how we can save time for our employees so that they can spend their time on other valuable things, and not waste their time on unnecessary time-consuming tasks. 

Our employees use Oracle ERP, so they have to process so many invoices at one time and it takes a lot of time to consume a single invoice. I'd estimate it would take at least 5 to 10 minutes. But with the automation, we can process one invoice within a minute, or maybe less in some situations. It saves a lot of time - likely hundreds of hours for each employee. It saves manpower for the company and saves you valuable time for the employees. They don't have to do the same things again and again and waste their time on that.

For example, if they have to download an invoice and process that for some reason. They have to go to some ERP tool, log it onto that first, type in the information, and then download the invoice. It takes a lot of time. They don't have to do this once or twice, it's hundreds of times due to the fact that they're not for the same couple of invoices. Therefore, this is one of the best use cases that we have for now. We are still looking for other future use cases, but for now, this is the one we have.

We use attended and unattended bots, Orchestrator, and Studio for development.

We're seeing increasing adoption of Studio because more people see how easy and straightforward it is to use a lot of the features. It helps that UiPath training is free. Our entire team, including our salespeople, have gone through the training. It's free and it makes a big difference. For the salespeople, they're able to talk more intelligently about RPA.

On a scale of one to five, judging how beneficial it is, I would rate the training a five, for sure. In fact, I have taken a lot of ideas from their training to educate my customers about RPA. When it comes to RPA, a lot of it is education because some of them don't know exactly how automation can be done. I've told UiPath that I use their training in my presentation, and it is great.

We are working with a technology company called Rammer, Rammer.ai. What the Rammer software does is listen to conversations to learn the details of what is being discussed. A third-party system is used to transcribe the conversation into text, then Rammer will learn the details without much training. It knows the topics, it understands what is talked about the most, talked about the least, how much we are adhering to the script if it's a call center use case, or if it is a simple meeting use case then it knows who is assigned what tasks, it recognizes the follow-ups, and it knows the summary of the discussion. All of this is summarized in a nice, consumable manner. So now, when a bot knows all of this information, it goes into Orchestrator, logs all these activities that are picked up by unattended bots downstream, and they trigger all those processes back. So it's a massive consumption of all of those heavy use cases.

We have not yet run automations in a virtual environment, although we do have customers who are asking for it. We are not sure if we will need UiPath's help for this yet because we haven't tried it.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate it a five. Really, it depends on how clearly we understand the requirements. So a lot of times we are able to find process gaps, which wasn't the case earlier before we started thinking about automation in this manner. I would say the ease of use is actually dependent on some of those factors as well.

Usually, starting is the biggest challenge for most people, and I think this is because it is in a trial environment and there is a lack of documentation, with multiple people doing one part of a small subset of a task. There are these challenges and then if none of them are documented, you need to figure out the process flow. From person one, where does it go? This can change when people can do multiple things.

It becomes a very complex web to understand and navigate through. We need to understand the task and how it should be performed. For developing the robot, it's very important to have the clarity upfront, otherwise, we cannot code them. That is the biggest challenge, I feel.

From the point that a UiPath license is purchased until the first bot is ready is almost immediate. This is because we usually start with a PoC on a small scale, just to see if automation with this approach makes sense. By the end of the PoC, we'll normally know exactly how many bots are needed. Sometimes it is on us, more than the customer when we cannot estimate every process that is outside of the departments and division that we work with because we just work at finance. For example, we can't just estimate what marketing would use, and so on. That will sometimes delay things.

I've created an app for conversions and exchange rates. Every day I need the exchange rate of a certain currency and I use the API free exchange and UiPath.

It's also used for the reconciliation of invoices.

I've used it for the creation of an onboarding bot for employees to be onboarded onto a website with a remote system. I used AWS and a virtual machine and created a Google Form from there, and used UiPath's computer vision to do onboarding activities and extract data from files. PDF files can then be entered into the remote system. UiPath can be used to fill the forms.

It can be used for web extraction tasks as well, for example, for booking flights, where you can extract the flight details for particular search criteria and place them into an Excel sheet.

It can also be used to extract data from invoices in order to populate an Excel sheet, for a portable format. I've created a process that used documents as a learning model and extracted the invoices, using logic to output the transactions. 

Another use case I tried was extracting data from Amazon based on exact data. The same can be done on Linkedin using the Linkedin API. I'm fine-tuning and extracting data, putting the outputs on Google Sheets.

I've experimented with many use cases and automated many processes. 

I use this solution to automate business processes that are rule-based. This includes the automation of different applications and background processes, such as posting invoices.

We use Studio and Orchestrator. I personally use unattended bots but we're releasing one of the largest attended implementations right now.  

For the most part, it's still in the back office, finance, and accounting, that's typically where we've been starting. That's where for me, as an inexperienced developer, is easier for me to get started.

We primarily use the Studio, which is for developing the robots, and we deploy to Orchestrator.

We went through a large SAP transformation and we had a lot of issues getting the users to accept the new systems. They were issues related to the adoption of new systems. We decided to build these attended bots in order to guide the users through the system. Essentially, it is navigation or guidance assistance. By helping the users with proper data entry and design, flowing in a logical sequence that is easy for the user to follow, it minimizes end-user training.

Running our automations in a virtual environment is something that we had tried during our PoC. Currently, we have attended bots deployed in more than twenty thousand laptops, and eventually, we're planning to have more than eighty thousand deployments. Because of the large scale, initially, we were having a lot of challenges because of things that go on with the users' machines. We wanted to explore Citrix because there is just one virtual environment that every user logs on to, and then run the processes from there. Unfortunately, it did not work for us. We were seeing a lot of issues and felt that it was much more stable deploying individually to each laptop, instead of using Citrix.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a four. There is always room for improvement.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. The material is very sequential and logical. You don't get lost because you just follow the modules from beginner to intermediate to advanced. You cover everything from end-to-end, and it is very structured.

From the point that we purchased our UiPath license until we had our first robot was approximately one year. This included our pilot project, then the development and the UAT. When we went live in production there were three thousand users. 

We use UiPath Studio, Orchestrator and Robots, all unattended currently. Our primary use case is one-off for mediation projects because we're trying to set up our infrastructure. Once the infrastructure is set up, we plan on creating a federated model throughout our entire organization.

Our primary use for this product is to automate processes that we are capable of automating at our tier-one level human resources center.

The primary use case is around manual conversion of data from one system to another. These are big processes right now.

We are using Studio, Orchestrator and the robots.

We use UiPath primarily for our financial operations.

We use this solution in a virtual environment called VMware Horizon. It has allowed us to get started without investing a lot, which was good for us. We need to go to the enterprise solution using Orchestrator as soon as possible. That said, I wouldn't do it differently, because if we were counting on the enterprise environment to get started, we wouldn't have deployed anything in the past year. Because we had this virtual environment, we've been able to deploy 16 bots so far.

We automate mostly finance processes, which is our largest area. We also automate some HR and logistic IT processes.

We use the solution for automation. It helps with Excel automation, validation, data extraction, et cetera. We use UiPath for a client project we are working on. 

We use the solution to automate our processes. 

My previous company was a share market or brokerage company, and we used UiPath for the client's reports. We used automation to get the records of their clients and get their financial reports in the desired manner. We go to the company database, get the proper data of the clients, and arrange it in the desired manner of our company's officers or the manager for the back office or the accounting department.

We arrange the data in a particular manner. We give it to them so that they can analyze and get the record for themselves, analyze their market reports, and get the desired result. We use automation to get the data in the Excel database so they can use that data in a particular manner for the future aspect of the company's client.

My current organization is a service-based company. Our client is a US-based company that manages the insurance portal of the US. They arrange the insurance portal for their US insurance client. We go to their particular portal and automate it, get the desired data, and save it to the database of the client's company.

Firstly, we used Excel for database use. We are currently managing SharePoint using UiPath and arranging the data on SharePoint, where all the clients can access their data and save the record on their own.

We use UiPath for robot authentication. We primarily use the software for accounting, particularly in our financial department, where we place some details from the client site, put them on a particular website, download the details, and then send those to a specific client.

I work for a big organization with many team members who access UiPath. On the client side, mostly enterprise clients, UiPath also has many users.

I create robots for clients of our company. We have an insurance client that asked us to help with sending letters by email and extracting documents related to insurance, between their insurance agencies.

We also do e-signatures using an API with a server to get digital signatures for all the customers of a bank. And with other banks, we have worked on onboarding clients. We have all the information about them and we do subscriptions for them.

We also have a lot of clients that ask for filters and updates in Excel files.

We use UiPath in the banking industry to help with the loan process. UiPath can check the title and address, and get documents from government and public websites. It can also check UCC scripts and the depth of support before feeding the information into the line of business application for the loan process.

We primarily use UiPath for science-related automations.

I've used UiPath in multiple industries, including medical, banking, retail, etc. It's a good platform for RPA.

We started by looking for something easy to change our process, and we liked a lot of systems that had low code. We started to submit and sell orders and transform reports into dashboards with the robot.

We're doing a lot of accounts payable automation and accounts payable invoice automation. 

We have about 70 bots in production right now. They are unattended.

We use this solution for finance, HR, and for handling invoice reconciliation. We also make use of donation approvals.

I find that UiPath's user community was more helpful a few years ago. When I go to use the UiPath forum, a lot of the answers are copied and pasted from old answers and they don't make a lot of sense. That being said, I do still occasionally get some value from it. 

We also make use of the academy courses. We have put all contractors through the basic courses to make sure that they've got a basic level of competence. The academy courses are useful to test that people know what they should. The architecture courses have been most beneficial to us.  

UiPath offers direct integrations with multiple platforms that we need, like Google Drive, Slack, Visio, etc. For Slack, UiPath automates the process when we upload a new file, document, or a new version of it. It automatically sends an email or any other sources that we automate through it. That is our main use case.

I use it for automating activities and processes in my company, and for discovering new automation opportunities. UiPath is my main tool for automating every process in business operations.

One of my main use cases for UiPath is around service desk and support center operations. I use it to take tickets from customers and users and automate answers using UiPath's machine learning. It links the questions to documentation where we already have answers.

I also use it for automating invoices with the pricing and other information and sending them to customers when they buy an item.

In addition, when somebody subscribes to a newsletter I have set up a process to send an email in reply.

Currently, we're doing digital transformation in finance. We expect to expand that out to operations based on our test case of five robotic implementations and to get those in the center of excellence and understanding, and then go further. In fact, in our naming conventions, we're trying to make sure that we leave room for HR, Operations, IT, et cetera. Right now, we're just in finance.

We use UiPath for OCR, for our subrogation department to analyze credit report organization letters that come into our company to identify whether they're identity theft, fraud, or any other type of keyword phrase within the document. It also extracts the information coming out of the CRO to properly assign it to accounts associated with our subrogation department. 

Another use case is navigating through one of our third-party clients in order for us to get documents out of their system and into our system so that we can analyze and package them.

We're using UiPath on the customer side, where we have lots of data and PPs on the customer information. We're trying to put in what the customer is including, and then using machine learning. We created a Python type of UiPath to do machine learning and automatically build that so that items can be automated. That was our POC. That said, we're exploring more, to get into the finance area, where we can take invoicing and general revenues and the closing worksheets and automate those processes.

We're the shared services divisions to contact centers and handle back-office work. Most of our use cases with UiPath so far have been automating back-office work, taking information from Excel files, and putting them into legacy systems or some mainframe integrations. All of our robots, as of right now, are unattended automation. We haven't really used the attended robots just yet.

My use case is to automate a bunch of office processes. It helps my team and finance organization save time and money.

Our current use case is primarily to automate business processes pertaining to finance, HR, and IT. Finance and HR have been bigger players, and other supply chain areas are currently being targeted. It's still in the ramp-up phase. We do not use it in a contact center environment.

I have multiple use cases as part of this solution, since I work in different domains with different technologies and applications. We use attended and unattended bots.

One use case was for a credit-based client where we worked on the UI automation of the application. We were using UiPath Automation Cloud because our team is spread across different geographical locations, like the U.S, APAC and EMEA regions. We had different RPA developers who are developing the script simultaneously and putting it on the system, and our business case was that we wanted to automate the UI applications. Since there were different developers in different geographical regions, they created the bots on their system. Due to the cloud offering, we were able to move the bots to production using a click of a button. There is also an Orchestrator offering as part of the cloud, which is hosted. Once we had a thorough peer review of the bots being developed, we pushed it to our production-ready cloud-based Orchestrator. From there, we use it to run the script. That is an unattended bot, which is also one of the features. Since it is a credit-based UI automation, there are some instances where manual intervention is required in order to see whatever data is sent out to the client, if it is in the correct order or not. That is why we use the unattended offering of UiPath. Both these technologies help us a lot in creating our production-ready implementation. 

For another use case, we did an implementation in the SAP application. It was a procure-to-payment (P2P) cycle, where a third party sends out the invoices which get fed into the SAP application, then it gets verified and goes out to the payroll team. Once that is verified by the payroll team, the payment is released to the concerned vendors. All these points of entry were being done manually: the third-party invoices entered into the SAP application, SAP verification, and the payroll team verification. Since it involved a lot of financial data, people were very hesitant to get it automated. However, since we had this UiPath offering, that initial hesitation was turned into a very good implementation of whatever we wanted to achieve as part of this UiPath automation. We were using the unattended bot as part of the cloud offering. We ran the processes at night from Orchestrator, so people working from home didn't need to stay up late in order to run the processes. Since we were using the cloud unattended bot service of UiPath, we were able to trigger the whole process in a single click of a button, which is amazing.

As part of the UiPath offering, we have three offerings: Studio, StudioX, and Studio Pro. These three offerings are provided via cloud on a single system and installed on our laptops or desktops.

I am working as a senior analyst. As part of this particular role, I have to cater to the client's needs if they want to get a UiPath implementation. Then, I do the consulting as part of the implementation. I also get involved in the PoC development and how we should use the cloud offering, e.g., what benefits are there.

I'm working for one project where we're trying to automate processes for a logistics company, specifically in their back-office accounting processes.

We're using Studio, Orchestrator and the bots. In other words, we're using the whole platform.

We use Studio, Orchestrator, attended and unattended robots.

We use this solution to solve the things that people don't want to do. They spend a lot of time and there is a high potential to make manual errors. Quality suffers because it takes too long and users can get fatigued. There are the things that we are targeting and we have already seen some of the benefits.

We do not run our automations in a virtual environment.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a four. It is easy, but there are some improvements that can be made.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. It is my lifeline. 

From the point that we purchased our UiPath license until we had our first robot was approximately six to eight months. I felt that the process was complicated, in part because of UiPath but also partly because of internal things.

Internally, in order to get set up, the entire infrastructure needs to be in place. All of the servers have to be set up and you need the right permissions because the bots need their own security. You have to explain to people that this is going to be a service account, and you have to explain the need for it. These are all internal, but necessary issues.

The solution is primarily used for invoice processing in combination with intelligent data captures. It's used for anything to do with lots of finance processes. Typically they go into lots of HR processes as well. They're the two main business functions that we work in.

Primary use case is to find the highest value add processes and automate them to allow people to work on other things, which are of higher value and more strategic.

I currently have a team of about 15 people on my team, as a central team. We are at 35 licenses, so we have about 35 developers across the company.

We have a lot of use cases for UiPath including automation of processes and reconciliation.

We use UiPath for marketing, accounting, and sales.

We work with the government on HR-related data and banking reconciliation. We use the solution in the insurance industry for claims management.

We use the product in different use cases. We use it for automating repetitive tasks, email and document parsing, and posting data from different systems to centralized systems. In most cases, we use it to compare different Excel sheets for reconciliation and updating the master system.

I'm using the solution for web applications and for integration.

We utilize UiPath to manage workflows and deploy application solutions into our customers' environments. UiPath simplifies various business tasks, such as automating applications, Excel, and segregating data.

We deploy UiPath both on-premises and in the cloud depending on the customer requirements.

We used this solution to automate monitoring, implement robots, and monitor the robots. We use it for network monitoring, ticketing systems, and remediation activities. This is a SaaS solution. 

This solution is mostly used by network engineers in managed services. The engineers look after telecom networks, and they are the end users. For automation, a sizable team of developers, specialized automation developers, and solution architects used the solution. There were about 40 RPA developers and 10 solution architects.

We plan to automate some of the business processes regarding financial reporting.

Our company uses the solution to process state reporting uploads for clients. 

For one use case, we automated the process of dragging forms, filling in fields, capturing confirmations, logging information, and moving files for upload. 

For another use case, we automated the process of manipulating data, setting filters, and generating reports in Excel. 

We are now moving to another department that uploads yearly tax reporting files to websites. 

We do not yet use AI but have many possible use cases for reading invoices and PDFs so we will try these processes first. 

Our company uses the solution to automate processing of intended and unintended regulatory transactions in the banking industry. 

We are just starting to use the AI function of the solution. 

We do a lot of manual work on a routine basis. We brought in UiPath to reduce a lot of routine work and mundane tasks that we do. An example would be that we have developed internal tools in our company. We need to back up the logs for these tools. Earlier, we used to log into a system, copy the logs, and then store them at another place, such as Amazon S3. With the introduction of UiPath, we are able to achieve this completely in an automated way. We have set up a UiPath automation to log into a system automatically, take all the logs, and then put them in S3 so that we have a backup for all those logs. This was one of the major use cases that we had, and UiPath helped us to achieve that at scale.

We are using the cloud version. We have more of a hybrid model. We have a pipeline through which we deploy everything related to UiPath. We have a beta endpoint and a production endpoint. Everything goes through the pipeline. Once everything is deployed in beta, we do our testing, and when we know that everything is safe in the beta endpoint, we push everything to the production endpoint. It is basically a pipeline system that we manage.

Initially, we had some manual test cases running in the background, where we tried to call our UI and do end-to-end testing of the login, checkout, etc. We now automate end-to-end testing using UiPath to reduce the workload. We use UiPath for process analysis and making robots, but not for monitoring. We already have other tools in our system to monitor each and every step of our process

We work in a hybrid environment, but we're increasingly cloud-based. We are not driving as much traffic to our on-premises system. 

Our use case for this solution is for hosting and deployment purposes of web applications.

We are using the latest version.

I work for an international consulting firm and we work with enterprise clients. Our job is to provide them with RPA solutions and ultimately, we would like to provide opportunities for them to have every kind of automation.

We began with use cases in accounting and controlling departments, after which we moved to automate banking, legal, and IT processes. Nowadays, we are reaching out to HR to help automate some of their minor processes.

To this point, our implementations have been in an on-premises environment. At this time, we are in the process of migrating our on-premises UiPath environment to the cloud.

When I joined the RPA team, coming from a DevOps position, I assisted them with IT-related tasks such as implementation, packages, etc. I went on to become an RPA developer and began working on business sue cases. As part of my duties, I search for opportunities, help find internal clients, and improve governance inside of our enterprise. I am involved in all of the steps in the framework.

Our first automation was an on-demand service, used internally for us. We deployed an on-premises orchestrator, also used on an on-demand basis. Once we got this experience, we started building other solutions.

We deployed an internal chatbot named Alex, and our employees can ask whatever they want. For example, you can ask Alex what your salary is. Depending on your privileges, you will get more or less information. Everything is done using robots.

Our use cases have evolved over time. We have use cases for screening and onboarding candidates, feeding new hires into the payroll system, and timekeeping. Right now, we are working on a document understanding use case. It is going to help us read supplier insurance forms.  

We work with TMS, a technology-management resolution division. We use UiPath to read the PDF documents that we get. We manage a business service for TMS and as part of that business contract, we read the PDFs and enter that information. We get that information out via documents from the templates where we have to enter information related to that particular case. 

These are the use cases that we are currently working on, but we are also looking to use this for quality assurance of all the steps because this is a highly visible, very critical process for TMS. We have to make sure that everything is done on time and that all of the information is relevant and responsive. Quality assurance is a big deal for us, and we are looking to use UiPath quality checks at different stages in the process.

Currently, we're doing the digital transformation in finance. I'm more of a functional person who understands the design and the processes but not the programming, coding, and details. 

I am using their automation cloud offering.

Most of our use cases come in finance functions, however, we certainly have use cases spread across all sorts of other functions. For example, in HR. We've had a lot recently in IT operations and then also in broader operations. Obviously, that depends on the company we're working with. We're getting more and more customer-facing automation that is running all the way through the organization, from front office through middle office and back, across all different verticals within a company.

Our primary use case is to document image processing. We're six months in, so our first case was sorting and filtering the data, extracting the image, and determining if it's a certain type of document. If it is, it starts putting it into different buckets, which ultimately we'll run something to extract and put those into our data source. 

Our second use case is for the healthcare industry. We're looking at catalog data and a customer might want to know about a product. Is this product safe? Who provides this product? Is it on a contract somewhere? We go out to multiple different web sources to look up information about that document, put it back in our database, save it for that customer, then save it for any future customer that asks the same question.

We're looking at other things like taking snapshots of the image of the product. We also want to automate other basic automation, low-hanging fruit type functions, like automating uploads of data to sites, spreadsheets, contact-center, and Salesforce.

Longer-term, we want to take what we're doing in the document image and apply it to other areas of our business. We have purchase orders, invoicing, shipping documents, compliance documents, credential documents, a lot of images in this particular space. We'll go as deep as we can in the data processing side of things.

We use UiPath for cases where we have to do a workflow-related mechanism. Most of these use cases are small, Excel-based solutions and desktop-solution-related workflows, where one or two applications have to be connected, along with the Excel operation, for the end-to-end workflow creation.

We use both attended and unattended automation.

We primarily use it to reduce manual effort and to increase accuracy and on-time implementation. We perform end-to-end automation, since we are a company where SAP is used very widely. We use UiPath for SAP automation.

We develop both attended and unattended solutions. We're using the platform as a service and it's hosted on-premises.

We use UiPath to automate business processes such as certain types of reporting that have to be repeated on a month-to-month basis. Another example is invoicing processes, which can be automated. Generally, it applies to different business cases for enterprise automation.

We use all of the UiPath products: UiPath Studio, Orchestrator, attended robots, and unattended. Primarily, we use them for financial liquidation. Our customers frequently use it for different cases. Some use it with chatbots.

Sometimes, our customers run automations in a virtual environment. In terms of implementing UiPath within a virtual environment, UiPath staff are working on the cost. Currently we have UiPath with a Citrix client and you need to go to the Citrix virtual station to activate. It's more difficult to implement as a user.

Our customers' organizations have involved about 15 to 20 people in their automation programs.

We are using attended and unattended bots. The attended ones are very low profile. We are also using Orchestrator.

Our primary use case for this solution is to automate underwriting processes.

We do not run our automations in a virtual environment, yet.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate it a four. I think that we still struggle sometimes with what kind of a bot we need to use for what kind of work. It may be a lack of understanding on our side. We need to have more clarity on this.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. This is what I have heard from my team members. I did enroll in the training but I didn't make much progress. That said, I have heard good things about it.

From the point that we purchased our UiPath license until we had our first robot was approximately a six-month transition.

We are using the unattended robots and Orchestrator modules of UiPath.

We have built close to fifty processes in the three years that we have been a client. Our primary use case, the one the gives us the biggest relief, is the processing of premium border rows. The robot will pick up Excel files with between four hundred and a thousand rows of data, and then does the data entry into our policy issuance system.

All of our automation runs in a virtual environment and we do not have any problems. At the start, of course, there were a few bumps in the road, but we got it figured out and now have no issues at all using the VM.

When we began working with automation, I was the leader and I had three BAs and three developers offshore. When our company decentralized, we created three other robotics divisions. There are now twenty-eight of us including the project manager, the BAs, the testers, and our developers. People are spread across four different divisions within the corporation.

With respect to how easy it is to automate our company's processes, I will consider the individual components. With the Orchestrator, on a scale of one to five, that's easy, it's a five. It is very evident how to use it. The Studio, I am not a developer but I got six developers up and running on it in a very short period of time. It has a very short learning curve, so on a scale of one to five, I would rate it a four.

My rating of four is because I know that we had some challenges with using the recorder. Things would shift and there were a couple of things that had worked and then stopped working. We found a little instability, and it was hard for us to know whether it was us, or the application, or the studio. Ultimately, we were not able to get a final answer on the root cause of those problems.

We are no longer experiencing these problems. When we upgraded, a lot of that went away. Also, when we went to Orchestrator, a lot of that went away. Exactly as UiPath had told us when we went to them with the issue, they gave us some solutions and once we implemented them, the issue was corrected.

I did not attend the UiPath Academy, but my Business Analysts took the BA course and my offshore developers all took the Academy. On a scale of one to five, judging how beneficial it is, I would rate the training a five easily. Before the Academy came around, they were kind of self-taught. When they took the Academy, it closed some of their gaps.

When we started with this solution, we did a PoC with the help of a UiPath developer. In two weeks we built a PoC for a bank reconciliation, which was pretty fast. That helped us decide whether we wanted to go with the product, and of course, we did. After that, we took the code, which really didn't have a lot of bells and whistles in it, and we gave it to one of our developers to really soup it up and make it more robust. That took them about a month to do.

I personally do a lot of process automation and data visualization. I work with a lot of people in procurement and finance to pull data from a lot of different systems, consolidating it, and creating reports, then presenting it. What I do a lot of is taking that consolidated data and creating automated reports with Microsoft Power BI and visualization tools. A lot of where people get hung up is pulling the data and the amount of time it takes to do that. So, people want to be able to automate their processes, as well as have my reports.

When I heard about UiPath, it addresses the initial problem of having to constantly pull data, get updates, consolidate the data, then model it in Excel or other sources, like databases. Being able to speed up that process, then connect it to automated reports, can fully lay out that entire pathway. 

I am working for a client. I am using on-premises UiPath Orchestrator. I have installed UiPath Studio and deployed some processes for automation. 

I have used it for SAP automation, Excel automation, and web automation. I have not yet used the AI functionality. I might use it in the future.

I have done the certification in Microsoft Certified Solution Associate (MCSA) and Microsoft Azure Administration. I look after the actual environment site where we can run the bots. We watch the environment's behavior, and we operate the Orchestrator, which is connected to the AI system. We run different types of processes through Orchestrator, and I am the administrator of Orchestrator. I give the rights and assign roles to the users. 

We use UiPath to minimize human effort by automating repetitive business processes.

I am a developer, and I use UiPath to extract PDFs for invoices and logistics in the banking industry. 

UiPath can be deployed either on-premises or in the cloud, depending on the customer's requirements.

I use UiPath to automate tasks in our internal HR and finance departments, as well as to dispatch back office requests, close accounts, process insurance claims, and make international money transfers.

UiPath is a robotic process automation tool used for large-scale end-to-end automation. It provides solutions for businesses to automate routine office activities.

We use UiPath for replicating manual tasks and PDF automation. 

Our company uses the solution for financing, accounting, and commercial operations. Right now, we are automating the lowest-hanging fruit. We look at people or personal productivity and automate their desktop tasks. 

We currently do not use AI functionality. 

We have a lot of use cases. A lot of them are based on SAP transactions. From SAP to SAP, or SAP to local documents, or local documents to transfer information to SAP.

We have multiple use cases for this solution. We have applications built on Microsoft platforms and we use UiPath for our automation and automation testing. Being able to do this means that we do not need to keep reverting back to test every use case when we complete upgrades. 

We also use this solution for the automation of responses to support tickets. Any tickets that come through that can be automated, rather than it being done manually. 

My organization is an outsourcing company. We work with various clients. So, we have many use cases. The current use case I'm working on is related to invoice processing.

We don't use attended automation. We use its AI functions a bit. Usually, we work with document understanding.

Currently, I'm using the latest version. It is deployed on the cloud and on-premises. It is the UiPath cloud.

We have a variety of projects we use it for. We have automated about 72 processes within six verticals, including sales, finance, HR, and purchasing.

We use the solution to speed up automation. We were looking to overcome the challenge of handling vast amounts of data, and we use UiPath to create bots to handle that. Tasks can be automated, and human error is reduced.

We have four robots. One we're sending out shipping labels as our members do returns. Once they create a return, we used to have someone that was manually entering in and creating the shipping labels. That was like the first robot that we built. The cost savings on that alone covered the costs of UiPath in total. We have a few other ones that we've been playing with, however, that first one was a big one that covered the cost of UiPath. 

We're a revenue cycle management company for medical billing. What we've done is we've replaced or reallocated our charge entry employees. We're using bots now to do the charge entry on medical claims and then also payment posting along with eligibility and AR. So we've been able to reallocate just within this last year, probably about eight employees. They've been reassigned to more valuable work, for example, things that the bot can't do and actually requires a human to do. We've been understaffed, therefore, it's actually worked out great.

Our use case is mainly for PDF automation for invoicing. Specific data from the invoice needs to be gathered, entered into, and compared within the SAP application we use. We face challenges as the formats of the invoices change and can range in length from a single page to up to 100 pages. 

We've integrated a tool called ABBYY FlexiCapture and ABBYY will help format and be used as the source of input for the UiPath bot. This bot in turn will process each and every necessary customer detail to the SAP application. If everything is correct, and the data meets the parameters, an email will be sent to the customer, attaching the necessary invoice. If there's an exception, we'll be able to look at that too.

There are some other sets of use cases as well, which include SAP or Hyperautomation. However, we also do generic workflows where we have data from multiple domains and will need to build our XML output. The XML output will contain a lot of data (such as the date, time or name of the customer) which will keep changing and is not fixed. I built a bot using UiPath that I host on Orchestrator which can monitor this data.

Another use case is placing job descriptions into an analyzing tool to search for keywords. Depending on the sort of description which we have pasted in, it will throw out a certain set of outputs, such as if the word is feminine, masculine, how many details it contains, how long it's going to take to complete the description, et cetera. This part has been done using an API key, and therefore it's not a normal cut and paste job. 

I am an API developer and I use UiPath for development. I use it to develop solutions for banking problems, like banking automation.

For example, in my previous company, I used the API for developing automated reporting solutions that take a lot of Excel files, check their data, and try to generate a web page containing many graphics based on the Excel data. It's basically translating the data on the web and it's made automatically every month. 

For my current company, it's a banking company, and I'm working on the banking solution. It's a process of verification of the user identity or the client's details. This process is based on taking the ID card of the person and digitalizing the data. It's a technology meant for reading data from documents. After reading this data, we automatically take this data and put it into the database and create accounts for the user or do a lot of automated things. 

At my current company, the use case is for the process of managing the relationship between the client account and any fees. A robot always checks if there is something to pay for the client and can take the fee automatically if that is the case. Then there is a transfer of money based on the request.

For example, when someone wants to do a transfer they add the money and sign a paper. This paper contains the information of the client's account, including details such as the client name, the account number, and the amount of the transfer. We take the data and the robot automatically takes the data and, via the web, goes to the apps of the bank in order to search for the client, search for the account, say the amount, and take the proper amount from his account, et cetera. We're able to save steps as everything is automated.

In our organization, we are using UiPath as a service model. It is an on-premise model where UiPath is deployed on-premise. We are not using it on cloud services. 

We have a center of excellence that has been set up to communicate with UiPath for all the licenses, for all the tools, et cetera. Individual teams will connect and will communicate with the development team to get those licenses. For the team structure, we have a COE manager, and a COE is again communicating all the relevant information to the teams.

First of all, you would have to go and submit an idea to the COE team. The COE team will review and see this is the correct candidate for our solution and we can leverage it as automation. They provide us with the required licenses and the cycle continues.

The use-cases for the UiPath are limited. For example, if you are coming from a banking background, there would be use-cases it comes from the data solutions. If you are coming from an insurance background, would have use-cases where you would have benefits that are being reconciled. Healthcare might be dealing with patient data, et cetera.

If I talk about the support teams, in general, the use-case for the UiPath is as a ticketing system, where you have a lot of data to add to the queue to remove the need to add items manually.  

UiPath has the ability to implement with multiple systems. You can extract the data from any other application, click the data to enter the specifications, and start the automation cycle. That way, you have a technology that helps you to build a fully automated enterprise.

Our use case depends on the client and their needs. It's specific to their industry. We basically use the product to build automation for them.

We're a consultant, so we help customers use this solution to develop automation and help set up COE. We provide the means for an entire organization to build its use cases. That's how we use Orchestrator both attended and unattended.

I primary use Studio, but I also use Orchestrator.

I develop robots for reducing tasks for our business users.

We run some of our automations in the Citrix virtual environment. We have found that the Citrix environment tends to present challenges, so it can take a little longer.

With a year and a half of experience, I am still learning with this platform. I find that the ease by which processes can be automated is not as much of an issue with the platform, but rather how it behaves with other applications that the robot controls. The learning curve is mostly how the robot behaves in maybe a Citrix environment, or in how it behaves with the applications that it's controlling. Sometimes they have their own little quirks that you have to learn.

I got started with this solution by using the Academy training. On a scale of one to five, judging how beneficial it is, I would rate the training a three. It is easier to get started because you are learning by experimenting.

From the point that we purchased our UiPath license until we had our first robot was approximately seven or eight weeks. 

We are using UiPath primarily for process automation. We are trying to consolidate information, eliminate redundant manual tasks, and save some money.

In general, we use it for automating monotonous, manual processes which a lot of our clients have. We also use it for internal employees in our company.

We are a system integrator. We work with clients such as the US Federal Government and help them automate whatever their processes are. We have two entities. I work as part of the government solutions unit, and then we have the commercial side which is a global organization. On the global side, there have been some internal implementations as well.

We use it to automate administrative functions, like finance and HR tasks. We are also automating a lot of things in our SAP systems, e.g. updating prices. 

We use it for a lot of small tasks, like downloading something from an particular internal website (e.g., SharePoint in Office 365) and uploading it back, or for doing modifications, then loading them back.

We are using UiPath to automate our cache application and to download documents to help our finance team.

I have worked on multiple use cases with UiPath dealing with SAP, SharePoint, or a web application. We had to extract the data and do some automation of data processing. We were taking data from one environment, such as from an Excel sheet, and processing it. These were the use cases for which we used UiPath extensively.

In addition to app integration, there were use cases related to various frameworks such as REframework and State Machines. We used the REframework at the enterprise level to be able to handle exceptions and bot failures and make automation healthy, robust, and steady.

We have also done automation for a healthcare department for claim processing.

The use cases are quite broad.  UiPath is used in customer contact centers, supply chain management, operations, etc. It is useful for the intelligent automation of task-oriented processes.

I have used UiPath for use cases that are both transactional and linear. It involves human resources, cybersecurity, OEM reporting, IT service management, service delivery, and examining of patents and trademarks. We work with federal agencies in the public sector. 

We use UiPath in the telecommunications and banking sectors to automate various processes, including IT, HR, and financial receipt processing.

We began using UiPath to automate repetitive and rule-based tasks, such as extracting data from documents, inserting data into applications, and sending reports to end users using databases.

We use UiPath to automate some of our financial and HR workflows and to send emails to clients.

We have many use cases, but the primary ones are on the finance side for intelligent automation. We use it for system updates and system manipulations.

We use it for making end-to-end projects. We are working with a commodity trading company where we have automated almost 150 processes. We have automated daily tasks or repetitive tasks.

We use the solution as an automation platform that even those without coding knowledge can use for automation-related tasks, such as PDF and Excel extractions. We're an IT services provider and use the tool for insurance data and other client requirements.

Our primary use case is creating automation for day-to-day activities for our internal use, especially for performance management and reporting. Apart from that, we create some automation applications for our clients as they're using UiPath. That's another use case.

We started using it to automate manual processes from other departments. We service other departments, to begin with, including the media between the business and the IT departments. 

We started automating very repetitive manual tasks that the business side typically had. For example, if they had to open an application early in the morning to try to process transactions. Then, late in the afternoon, they would have to do the same thing as well. Now we have a robot that does that in the morning and the afternoon, which saves a lot of overtime since it has to be done at six or seven at night, and previously sometimes people would be forced to stay. Therefore, this way, we save that time and overtime. 

Another example would be we use it to download ATM transactions from a webpage. The robot downloads those transactions and then uploads them into our data warehouse, which reports for them. Normally, we don't have that information there.

Another use case would be in a department that would print a bunch of wires late in the afternoon. The department would print them out physically and store them somewhere where they review everything later. Now, with UiPath, we scan the transactions from the Fed, and we just print in PDF and send it to them via email, and it saves a lot of time.

UiPath is deployed on AWS EC2 instances, and we use it for basic automation.  Very few developers are working on UiPath here. Our end-users don't deal with this. We only use our database and the data collected from UiPath, but the automation is not visible to our customers. We only use it in our internal development or design phase or to collect some automated data. 

We haven't used UiPath's machine learning capabilities, but we are working on that. That could be useful in a few use cases for triggering some queues and running processes in the background. We are using asynchronous jobs, but we don't rely on AI yet.

We are a service-based development company and we implement automation for our clients. UiPath is one of the RPA solutions that we use for this.

A recent use case that we implemented for a client involved a macro in an Excel sheet. The macro contained approximately 1,000 lines, and it was being used in an Excel spreadsheet about 10 pages long. They had dropdowns within the sheet that had to be set, depending on the action. They also had to work with some of the logic themselves.

With UiPath, we implemented a solution where the bot will create a task. It first checks to see if all of the necessary conditions are there. If they are, then the bot will automatically run the macro. If instead, some of the values are missing and user input is required, then the bot will create a new task to request the missing items from the user. It uses the UiPath forms and the client will receive an email to say that a task has been created and that it will be completed once the necessary values are selected.

Finally, once all of the values have been selected, the bot will run, use the input, and complete the execution of the macro.

A second use case for us was done using the Action Center. In this case, our clients send emails, and we have API calls that are done in response. Once an email comes in, a message ID is created and assigned to it, then it is turned into a Queue item. At that point, the user is presented with different actions that are dictated by the content of the email.

Depending on the user's selection, there are three or four paths that it can take. Ultimately, the bot will send an ETA and some request data to the appropriate parties, which is controlled by yet another process.

I'm not currently using UiPath, but in my previous organization, which I left seven months ago, we had a complex trading application that included a web form and a Windows form. And on the Windows form was an Electron framework. If you want to run a web application inside a Windows application, Electron is a bridge between the web application and the actual Windows app. Because it was a complex application, it was not very easy to automate. That's where UiPath came in. It perfectly fit our automation testing scenario.

As consultants, we have implemented UiPath for clients when they have asymmetric workloads because of COVID and they want to scale up but don't want to hire new people. We've implemented automations for clients that want to decrease their workflows. And we've seen efficiency gains as well when clients want to complement the work that humans are doing with the help of automations.

A good example of a client use case is a client that does mortgage loans. When someone comes to a loan officer, there's a lot of information that needs to be provided. There's a manual process that includes inputting the information into the system. Once the information is in the system, they need to run a lot of services, such as lien and credit checks, location verifications, inspections, flood reports, et cetera, before a loan application can be approved. 

We've automated this entire process for them. Our automations, built on UiPath, run all these services, generate all the reports, and store them in a centralized repository that can then be eyeballed by a human. That way they can make a judgment call on whether a loan should be processed or not.

Our in-house use case right now is around structuring reporting with UiPath. We have a Power BI layer and we use UiPath internally to check employee availability, as well as who is charging hours, and how many, to our projects. Overall, we use it for HR activities. We go into our HR management system, generate and download the reports using UiPath, and then modify and massage the data depending on business rules. We then publish that data into Power BI and that's used as a centralized dashboard for reporting for the organization. 

We have two use cases.

One is for our claim accessing process, for which I have developed a process for logging into the client's application. It includes launching the browser and getting logged into the application by entering the username and password and handling two-step verification. Handling that requires some logic. Once logged in, it navigates to the claim status feed and selects the organization's and payer's details. It then enters the required details of the patients. These details are given by the client in an Excel document that the process reads. It searches for the values, one-by-one. If there is no record for the patient whose details are entered, it will throw an error stating that there are no claims present. It captures such exceptions and records them in a separate Excel file.

If that person's claim is present, it fetches 25 to 35 key details from that record and they are written to an Excel document. Once the process is done, the Excels will be sent as email attachments to the client.

The second process that I am currently developing is one where I need to get the data from Google Sheets. This process involves four or five practice management systems. It has to log into each practice management system and, for each one, it needs to schedule appointments based on the data present in the Google Sheet. The process involves navigating to the respective screens, filtering the details, and entering them in a CSV file. Based on that file, we have all the data related to patients' records. The process checks the patients' payment records. There are exception-handling routines and any errors are noted in an Excel sheet. Once all the patients' records have been completed, it closes the application and sends the data to the respective clients. It produces a log file in Excel as an attachment, as well.

Our use cases for UiPath are all across the board. We started primarily in the finance and accounting sectors and moved to our integration center, which is made up of individuals working with our field operations folks to schedule and conduct work.

We have also moved into HR and found a lot of hours there, as well. We have also done automations for our IT and supply chain sectors. We probably touched about 15 different business units within our organizations with UiPath automations.  

Often, the solution is used for a lot of connecting data from different systems, et cetera. Also, a lot of tasks involve taking data from Excel or an email and putting it into different PDFs at high volumes and then saving everything in a certain spot in the file directory.

We were with the Air Force and had really a lot of different use cases including finance, credit card transactions, flight authorizations for training missions, et cetera. There are a few hundred use cases.

It's on multiple platforms like Oracle EBS and other IT applications. We have a few of the local government applications that the client uses. We have worked on multiple use cases with all of these applications. All of the client's major work is all through Oracle EBS. We have finance-related use cases. They have Seabridge applications, which are one of the applications that we are automating using UiPath.

I have worked on two UiPath use cases. The first use case is for the IT Infrastructure team for submitting server requests. They receive a request from a third-party portal through email, and then my bot reads the email and fills in the details in the company portal.

The second use case is the data extraction from Word documents. The team receives Word documents with some important contract information. I extract those paragraphs and put them in the CSV format given by the customer.

We are using UiPath Studio 2020.10.2, and the Orchestrator version is 2019.

I started my RPA journey as a developer, and I first heard about UiPath as a low-code, drag-and-drop automation platform. Back then, it was very much in the beginning stages of its development. Ever since then, I've seen it evolve quite fast. I would say even faster than other RPA platforms that I've used, in just a few years.

Thinking back to when I first started using it, there are many new features and updates and it's my preferred platform for RPA.

We primarily used unattended automation, where you deploy the bots to work autonomously. This is unattended, end-to-end automation with no human in the loop, other than providing the inputs or checking the outputs.

We have several use cases, but our main one is reducing manual work. The processes that require a lot of manual input and have a lot of human error are the focus. That could be, for instance, processes that have to do with invoicing, billing, reporting, and coding, which require a lot of man-hours, are very reliant on a human being available, and are time-sensitive. Those are the ones that are on the top list to be automated.

Beyond that, I can't specifically talk about the processes that we've automated.

Primary use cases involve the following automation environments and processes:

1. Oil and Gas Domain: Automation of various applications specific to this domain such as Gopher, Tow, Toad, Excel, and various browsers.
   
2. Finance Banking: Here we have to deal with various legacy applications with a lot of PDF and Excel-based automation. UiPath comes with a lot of reliable solutions here.
3. Healthcare: Automation is a big challenge because the Healthcare domain is not a simple thing to automate. The ML extractor and Intelligent Automation activities are best to use here.

At Forest Service, we have a massive onboarding season. Because our primary mission is to combat forest fires, we have a huge intake of firefighters that we hire every season. Because of that, there's a lot of onboarding material that needs to be processed through HR, literally tens of thousands of people in such a short amount of time. I can see, potentially, RPA being able to help with some of the manual work that we do.

It's probably the best bang for our buck, but there are certainly other use cases potentially. That is the area that I'm more familiar with, though.

We use it in our robotics lab to deliver front and back office solutions for the clients. We're a BPO CRM organization, so there is a huge amount of opportunity, not just internally as an organization, but for our clients as well. We use UiPath as a delivery method to find reductions in costs and the like, year on year.

We automate business processes that take up a lot of effort and manhours. Our company deals with a lot of documents. 

I have used UiPath for a city utility. The main purpose is if they want to dig in a particular location, they need to know how many pipelines are underneath the road, what the situation is regarding high-tension wires, gas pipelines, et cetera. For that, we needed to go to about 18 websites and scrape the maps from them into a local repository. We use UiPath to save that data from all the websites.

From there, there is an AI/ML solution that identifies the danger signals and notations on the map. It summarizes them and sends them to a mobile application used by a person who is at that location. That person can determine whether they are able to dig in that particular location or not.

I'm using UiPath for personal use. I'm trying to create an application in which all the work can be automated, such as financial, HR, and educational-related work so that we can have easy access to the details of candidates.

I'm using it for a small edge case and UiPath is able to solve it in a great way.

Our company uses the solution to automate formula-driven processes that are completed on a frequent basis. 

We create unattended bots to handle tasks for our finance, procurement, IT, and HR departments.  

At this time we do not use AI or ML.

The beauty of RPA is that it has many different use cases. We use the product as a standalone and as part of a bigger solution. Obviously, the tool itself is designed to automate activities that humans would do. But as the tool is getting smarter, we are able to do more types of activities.

There were two big challenges in the early days. One was the complexity of the rules that you needed to adopt for a particular task and the other was the type of data that was being used as part of the business process. As we've gone along, the product has evolved and allows us to do more of the business process.

We automate everything using the UiPath solution. We have some ongoing stuff, e.g., generating test cases and testing some of our development platforms. We need to define all the parts, such as how to test the entire environment to determine if everything is working okay.

We utilize all our services on the cloud, then they can be easily used across all our offices.

We only use unattended automation.

With federal governments, a lot of the use cases vary around what they're doing, however, it's just a lot of PDF, Excel, and Microsoft Suite automation and then interacting with their custom and web-based tools for subject information.

We're a revenue cycle management company for medical billing. We've reallocated our charge entry employees. We're using bots now to do the charge entry on medical claims and then also payment posting along with eligibility and AR. We've been able to reallocate about, just within this last year, probably eight employees. They've been reassigned to more valuable work - things that the bot can't do and actually requires a human to do. We've been understaffed, so it's actually worked out great for our company.

Currently, we are using it for reading emails. We download the attachments that we get in emails. After downloading those Excel sheets attachments, we process the data based on a few rules. The processed data is input into the SAP application. In the SAP application, based on the business rules, we process the data and commit.

I have worked on a number of use cases, and one of them that I can discuss was used in a contact center environment. This is a project that we had done for an automotive insurance company, and it had to do with incident management. Our contact center received the first notice of loss (FNOL) from incidents, such as an accident.

When an accident occurs, they raise a ticket to our customer service representative. This can either be done using a chatbot, which is integrated with our ServiceNow platform, or they can call the customer service representative. In the latter case, the customer service representative will pick up the call and get the details. This includes adding their insurance ID and a couple of other fields, and that is integrated into our system.

Our system was acting as an intermediate between their existing platform and ServiceNow. Part of the system included a database, where they were checking to see if the insurance amount the claimant is asking for is above the limit. There were other similar business rules, as well, which the bot was responsible for checking. Based on the result of these checks, the claim was automatically approved, and then a corresponding ticket was raised in ServiceNow.

There was also a manual process, where there was a person who would go to the site where the actual accident took place. They do their analysis, and then they create a review report, and that report would automatically be handled by an attended robot. The robot would take the detail from the agent and based on the review, fetch certain details like the approved amount.

The bot is responsible for sending other information to ServiceNow, including, for example, details about damage to the vehicle. If there are scratches on the front or scratches on the back, then these details are all posted to ServiceNow. At that point, ServiceNow has a workflow that is initiated.

The workflow uses the information taken by the representative and moves from the review stage to agent verification, and then to a mainframe. The system running on the mainframe is responsible for generating checks, according to the amount that is approved, and then mailing them to the claimant at the address they have on file.

Currently, I'm dedicated to working within a finance organization. It develops processes in the scope of five months. I do not use the solution in a contact center environment. I work on projects for shared services.

We are a communications company who works with a lot of clients in our country. Now, we started using automation when working with business clients. Many processes were being done manually, e.g., activation of numbers. In order to alleviate the work of our sales team, this process was automated.

I haven't automated any of my work because the queue for processes that need to be automated is large.

My company uses Studio for our developers and StudioX for attended robots.

I have been using UiPath to develop automations for my company. We are a manufacturing company that uses SAP as our primary enterprise application. We are currently meeting with many different business areas and hearing about all of the different processes that they would like us to automate for them. Since UiPath works within SAP, it should help us get some easy wins!

We are using Studio, the Orchestrator, and both unattended and attended bots. We are using the product primarily to index and process patient records into patient charts when records come in from outside sources.

Currently, we're using Studio and soon to be using Orchestrator. We have not actually deployed any bots yet, but we have looked into both Orchestrator and bots. We have just looked at the solution set of that on why do we need to deploy in the future.

Our primary use will vary from department to department. We have what we call 11 global practices. These range across different platforms, but the underlying theme of that is we want to automate different items which might be finance or accounting or HR or whatever. But where I think it will be most useful is in our core business where I'm looking to apply it to engineering project management.

We use Studio, attended robots, and Orchestrator.

Our primary use case is automating support services for accounts payable and accounts receivable. We are still implementing and our robots are not live in a production environment yet. For the time being, we are using attended robots but we are looking into unattended robots as well.

We run automations in a virtual environment using VMware, and the implementation was straightforward. It was easy to set up.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a four. You don't need any programming skills to be able to leverage the tools. We have used other tools such as Blue Prism and Automation Anywhere, and this solution was easier than those.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. It is very simple and can be easily demonstrated.

From the point that we purchased our UiPath license until we had our first robot was approximately six months. 

We have robots and we have Orchestrator and we are exploring the new analytics model over the next few months. Right now, our primary use is mostly operational processes and deploying apps for the global operations team. We have multiple automation processes in place for them already.

We are using Studio and Orchestrator, and we purchased an unattended bot.

Our UiPath is integrated with Kibana, which is a free tool.

Our primary use of this solution is to automate manual processes. We have approximately eighty use cases to automate.

The RPA team includes two developers, a manger, and two BPOs.

We run automations in a virtual environment, but I am not familiar with the details.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a five. We just drag and drop. If you want to write something we use "Type Into". If you want to click, we use the corresponding click application. For me, it's very easy, and we also have tutorials available on the UiPath website. That is something that is very useful for everyone who wants to learn, and even a non-programmer can start learning to become a developer.

The Academy RPA training was very beneficial and I would rate it a five out of five. You cannot skip one step. There are ten sections and you cannot skip any of them. It means that until you pass a certain test, it will not allow you to go to the next lesson. This restricts people from jumping directly into another section. I really like the training and it is very easy. The tutorials are not very lengthy, they are simple, and the way they are explained is relatable. The practice tests that were conducted at the end were really helpful.

We partnered with IVy to create our first two pilot bots, and from the point that we purchased our UiPath license until we had our first robot was approximately six months. It was very easy because they helped us.

We are using Studio, Orchestrator, and bots.

We are a consulting company that is working with one of our clients to automate back-office accounting processes for a logistics company. There are five people in the core team who are working on the implementation.

We run automations in a virtual environment, but I was not responsible for the implementation.

With respect to how easy it is to automate the company's processes, on a scale of one to five, I would rate it four. It's very easy, but it is difficult to explain to our customers who are not as technical. In other words, it is difficult for people who are coming from the business side.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. Without it, I don't think that I could have started the implementation. I completed the developer program just for a general understanding of how everything works, including the Orchestrator and how it all works together. For me, the training was really important. It was very good and I really liked it.

We were working with the Community Edition at first, but from the point that we purchased our UiPath license until we had our first robot was approximately one month.

I'd say our finance applications, like accounts payable, have been our biggest use cases for this solution. 

We are in the finance industry, so we use Studio and Orchestrator to automate a lot of Excels and making reports.

We are using attended and unattended robots, Orchestrator, and Studio.

We are in the financial services industry. A lot of what we do is background data processing, and we use the unattended robots for a lot of it. We do have some attended robots as well, but most of our processes are unattended.

I am a developer, so I primarily use Studio. I write the instructions for our Orchestrator Application Manager to do everything we need in Orchestrator. 

We are currently operating an on-premises deployment, but we're in the pilot group for Cloud, so as soon as we get a date on that we'll probably be migrating.

One of the primary processes that we've automated is reporting. Prior to automation, our users were only able to run a few of the reports, a few times a week. Now, we're running every single report that there is to run, which is probably four or five times what they were able to do, every single day. Every morning they receive a summary of that work, so they're able to just get on and look at it, rather than during the close of the day. In financial services, the close of the day is crunch time. We work really hard to make sure that everything is done within a set about of time because there is a domino effect. One person has to be done before the next person can finish, and they're not having to dig back and try to figure out when these issues happened. We're providing it to them upfront. We can say exactly what happened, which account they need to look at, and on what date. This means that we're ahead of the issues, rather than trying to backtrack and find them.

We are not currently running in a Citrix environment, but the only reason we're not is that our sister company hosts our Citrix environment, so we can't install any of the services that make those environments much easier to utilize. For example, we can't install the computer vision component because we don't own it, so they won't let us.

Our team is really small, there's only six of us on the actual RPA team. However, we work really hard with the business to get buy-in in every department. We're trying to roll out at least one automation in every single department. Our company's goals for the next year, I believe, every associate of the company is supposed to have proposed a task that they are doing, whether it's daily, monthly, yearly, whatever, that could be automated. Then our team will ingest that, prioritize that, and work through it. But, we're really trying really hard to get our whole company involved, and we're getting ready to kick off this campaign to try and get more attention to it and to try and get people using it. We want it to be more than just a buzzword. We want it to be something that everybody's talking about regularly, and using, and excited about.

When it comes to getting people interested, I think it's probably a combination of education and sharing the experience of those projects that we have rolled out. When people are really seeing that with the projects that we've rolled out, our close is shortening, they become interested. What we say is happening, or will happen when we're rolling these automations out, is happening. Getting that to be shared from process owner to their team, to the teams that they're working with, it acts like word of mouth for those that are affected. We don't like it to just all come from us, the technical team. We don't want to simply tell them that it's going to do something. We want others to talk about what it has done for them and suggest they should take advantage of that too.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate it a five. We don't struggle with it.

I took the UiPath academy training, and I love it. We are looking at an unrelated tool right now, and we found no comparison between their training and the UiPath Academy. We were spoiled with UiPath Academy, and we didn't really realize how good that training really is.

The thing that I love about the developer training; the level one, level two, level three... level one really does walk you through it. It gives you, literally the walkthrough, so when you don't understand, you can go back, you can look at, and see exactly how to do it. But by the time you're in level three, it's not doing that anymore. The requirements are a little bit looser, you have to figure out how to interpret the words or the requirements, and it becomes more challenging, but I think that that's important, because, by the time that you're actually working real projects, it's not a walkthrough anymore. You have to figure it out on your own.

From the point that we purchased our UiPath license until we had our first robot was approximately three months. It did take us a little while, but we knew that we purchased our licenses before we were really ready to hit the ground running. We function out of such a small team, and we were still working with UiPath trying to figure out which partner we wanted to bring in for consultants because we wanted somebody with experience. We didn't want someone who just finished the training just run in and try, and I think we learned a lot working with that consultant.

We did work with a second consulting group, Machina Automation, and we loved working with them. They're great. They're just so supportive, and they really want to make sure things are right. It's never just sending them the requirements and pounding it out to get it into production. We work with them really deeply to try and make sure that they understand the process, we understand the requirements, they express their concerns to us, we express our concerns to them, and we work together. It's not like we just send them the documents and they send it back as a project. The whole way through we touch base with them every single morning. They're always asking what more they can do and how they can help. They ask if we're happy with what we received.

We do time card reviews, so the time that they spend with us we're actually able to go back and validate, based on that, what they've said they did, that indeed it is what they did. We had received some scrum and sprint training from them. We've had actual developer consultants, we've had mentoring hours for our developers. So we've had a lot from them, and they've been able to help us with everything. Anything we ask, they try to accommodate us. For example, we asked if they had any experience with Kibana. They did not but said that they would find somebody who does.

We are a pharmaceutical company, producing insulin, primarily for diabetes. We work with other diseases, as well, but our focus is primarily diabetes.

We have automated many processes, at least 20 RPAs across the company.

It is for automating tasks that are not meaningful for people to do, tasks that are menial and repetitive. The University of Copenhagen, where I work, is an old institution and we have a lot of different legacy systems that don't work well together. So, we have a lot of people doing administrative tasks that depend on moving data from one system to another. We use UiPath to automate these repetitive tasks and make the robots carry them out, so our people don't have to.

Primary use cases would be within the finance sector. We supply financial services for other government agencies. The main robots that we have in use right now are concerning floating of financial periods, uploading reports, commenting on these reports, and so on. We are starting to look at invoice processing, to a larger degree. Then, we have a few quality and control robots which do checks on data quality, customer information, customer carts, etc. 

We are using approximately 20 robots right now for different uses.

We've opted for professional, traditional developers and programmers to do batch robots. We don't use it in our business units. Possibly because we are a government agency, we don't necessarily get enough IT security around the users applying their own robots. 

It is not easy to use in this way because we do use traditional programming skills. We are considering moving some tasks out into the workforce for Attended Robots, etc. We think that this will be a problem for us in regards to getting it pushed out there and still maintaining good quality. However, we haven't tried it yet.

The process is for background checks. There are all kinds of checks such as academic, criminal, and work as well. We receive all the volume through the queues. We are using the citizen developer, StudioX, to get the cases and understand what are the fields and what are the requirements for each one of the cases. The bot will process them accordingly. For example, for each university or academic, there is a different process around the world.

The industry we use it for is HR. What we do with the backgrounds is providing a confirmation to our clients that people have the qualifications that they say they have. It is for data accuracy and consistency within the HR and talent acquisition departments.

We use UiPath for automating tasks for customer operations.

My primary use case is mainframe automation from legacy mainframes that previously hadn't been automated with other automation tools. The product worked like a dream with the mainframe automation.

I've been making some accelerators using it. Each Customer Relationship Management page in the telecom industry has a similar kind of structure, so things do not change a lot. I'm creating an accelerator that can log into a CRM and quickly perform specific tasks as per requirements. For example, the robot will log on to a CRM page, will add updated user information, and check the details of user requests. Another case could be creating specified user service requests and monitoring their status for service efficiency. 

We use UiPath to automate routine tasks using bots.

We use UiPath to automate processes.

We have two primary use cases. We use UiPath to scrape data from multiple websites and platforms, mainly for competitive intelligence and internal use. The other use case is basic automation, that is, moving files from one system to another when there is no direct integration. Through UiPath and leveraging RPAs, we pull data from one system, for example, an S3 bucket or Google Drive, and put it into our database.

We use this solution for voice processing, user onboarding, offboarding, marketing, email consolidation, text form generation, text form ingestion, AP, and AR.

We are using UiPath's AI functionality although we have not been able to do much complex configuration. Theoretically, it works but as soon as we start adding different invoices, it's a very cumbersome, long, and human-centric process. Our company is planning to scale our automation efforts.

Since we are a healthcare organization with HIPAA rules, we're on-prem. Our use cases boil down to claims testing and membership testing. It'd be institutional professional dental claims and making sure our membership is loaded correctly.

UiPath helps us to develop and build a center of excellence for our clients. I do development and technical implementation of the bots, best practices, and teach others how to do the development.

The client that I'm working with now is in the financial services sector. They do banking and life insurance. They do a lot of contracts and billing, backend, data entry-type work. We process all of the return mail that comes in, scan it using Doc Understanding, publish new bills, generate form letters, and all of those tasks that go along with managing the client for life insurance, annuities, 401K, etc.

Most of the time, we work with financial services to automate financial transaction monitoring systems. We go through multiple CRM and financial systems, then query the transactions based on the KYC information. We use OCR operations, using UiPath Robot, to fetch information, such as, identification number, passport number, and their tax information. We extract this information, then validate with our financial data or transactions data to ensure that there is no fraud nor anomalies in the system. If there are any suspicious transactions or potential fraud, we do manual investigations. Those manual investigations are redirected from the robot to a human agent, then the human agent verifies the information. If there are any cost validation requests from other systems, such as Salesforce and PeopleSoft, then another bot will be triggered using UiPath Orchestrator. After that, we do the remaining processing. At the end of the processing, we use the UiPath analytics service. That analytics service uses UiPath logs, which helps us to understand how the bot is performing and how many transactions we have validated. From that, we look at how many were successfully processed and how many were manually handled, i.e., exceptions. We identify business exceptions for any transactions during the initial pre-validation stage, such as the user identification number is not valid or input data validation errors. For example, passport information must be an alphanumeric eight digit. If the bot identifies that the value is not eight digits, but four or five digits, then it is an invalid record straightaway. We can see this from the reporting and performance graphs.

We do automation for our HR processes, such as onboarding processes. On any day, there are five or six people who need to be onboarded. This is one of our standard business cases. We have a UiPath robot design using UiPath Studio and then it deploys in Orchestrator. This robot is being used by the HR admin. They can fill in the key information of the user, e.g., name, level, and their package. So, they import all this information, which includes my identity information, mobile number, email, and IDs on an Excel file, possibly along with a few other associates joining tomorrow. Once those entries are made in the Excel file, then the user can trigger a robot. They also need to keep the file in a designated folder. The robot will read the file from the designated folder. Then, one by one, it will read the records or line items from Excel and open an SAP portal. After logging through the SAP Portal, it inputs the required employee information. After that, it will go to Microsoft Azure Active Directory to QA the user, email, and ID. It will then go to PeopleSoft to create an HR record for the salary information, leave information, and the level at which the associate is joining. At the end of this process, it will update the status to, "The associate has been registered successfully." It will then send the updated final report to HR, saying, "The processing has been completed." The bot triggers information with their newly created email ID. They can then access or receive the onboarding information. This is how it works.

Depending on the client's requirements, we use UiPath AI Center and UiPath Apps for custom requirements. Most of the time, we don't need them. There are some times that we do based on the client's requirements.

I am using UiPath Studio, UiPath Orchestrator, and UiPath Robot.

Initially, I used the on-premises deployment model. For the last two years, we have also been using the cloud deployment option, UiPath Cloud, along with the on-premises. This is based on a client's requirements.

Most of our use cases are related to business, like reconciliation and reporting. Therein, they have some internal applications to automate SAP automation and Salesforce Automation. Our most recent use case is related to documents, like the invoices coming from customers. We have to extract that data from invoices via different formats, e.g., some are digital formats and some are scanned formats. So, we have to extract the data, which we are doing with the help of UiPath.

We are using both attended and unattended automation. For 90 percent of our use cases, we are using UiPath for unattended automation.

I use UiPath almost every day. When I finish developing one process, there is a new process to develop. If a process is complex, it almost takes six to eight weeks to develop it, then you have to deploy it for monitoring. After that, the next process comes up.

We are using attended automation. I help drive a lot of products in UiPath. Now, we are using their data process mining and document understanding features. We are creating forms, then putting data on the forms, so our attended bots will work.

We use UiPath for a lot of different scenarios including recording daily time capture, ordering meals for teams, and more technical work related to tax and audit. The most common uses for me personally are for drafting and sending emails. This has saved a countless hours of time. Basically, if it can be automated then we are automating it.

One use is in our corporate tax accounting group. Our environment includes systems such as SAP, Vertex, several homegrown, and of course Excel. Other use cases include automating a timekeeping system and performing cell phone bill analysis. Environmentally, all use cases involve different systems.

We use Orchestrator, Studio, and of course the bots for indexing documents received from outside providers.

We are using UiPath Studio, Orchestrator, and attended bots.

We are automating 12 shared services processes. They are from the finance, HR, and procurement areas. These processes are run at a high frequency and are required to be captured on two different platforms. We have implemented this solution to stop entry clerks from having to do the same job twice, on two different platforms.

We run automations in a virtual environment and it is successful. The implementation was fast and we realized the benefits quickly. Currently, we have deployed three processes and we are going to roll out more processes in patches.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a four. Some of these processes have difficult exceptions that had to be handled, which is why we opted for the attended robots.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. The training is rich in content and the material, products, and methodologies are explained well. The concept of automation can be very easily digested by anyone, even if they are non-technical.

From the point that we purchased our UiPath license until we had our first robot was approximately a month and a half. I was not the person doing the configuration, but I managed the process through interaction with the technical team. It was a straightforward and easy process.

We primarily use the solution for the financial processes. 

We are using the attended, unattended, and Orchestrator components of this solution.

Our primary use case is developing automation around revenue cycle management in the healthcare space.

We run automations in a virtual environment and we are very happy with that ability. It is much more time-consuming when compared to running it directly on the server, but it is very reliable and it is a great way to create automations that you wouldn't otherwise be able to create. Of course, we prefer to go directly to the same environment.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate it a four. In order for me to give it a five, it would have to be such that a user could go in and develop it easily with a point and a click. I think it would be extremely difficult to build a platform that was that simple for the end-user, but I think UiPath has come a long way and is very good at making it easier and easier as we go along.

We have at least ten developers who have gone through the certification training with the UiPath Academy. On a scale of one to five, judging how beneficial it is, I would rate the training four and a half. The training is wonderful. There are certain elements of the training platform that are not keeping up with the product though. Also, some of the things that are in the documentation are not up to date. Being a little outdated, it can be kind of frustrating for the people that are going through it. But, it's a great way for people to get a good understanding of how to use all of the elements of the process.

From the point that we purchased our UiPath license until we had our first robot was approximately three weeks. 

RPA overall is about routine, mundane, structured tasks. We use a number of them at my client's work in terms of how do we do back office reporting for general deliverables, contract compliance, etc. 

We had a few different reports that we had to do every month. We have to hand-jam them into a very poorly-formatted database which had weird drop-downs. Instead of entering them manually, and spending a day or month just punching in titles and numbers, we compile it onto an Excel sheet and have a bot run and dump all that information. 

All I have to do is tweak what information has changed from month to month. This has made my life a lot easier.

The primary use case of UiPath, with every organization that I've worked with as a consultant, has been to make business processes more efficient and the work of their employees more enjoyable. 

When it comes to finance and HR services the product has great potential. Our company is big, so there are a lot of opportunities.

We are doing automation internally for financial processes.

Externally, for our customers, we are developing a shared service center. This is not restrained to any one specific area, like HR or finance. Anything that is manually or taking a lot of human effort, we try to automate (by selling it to our customers).

Most of the time, I am a developer. I also have to develop some best practices, but a lot of the time, I'm working on the application and creating Unattended Robots. We have a large amount of old school manual processes which we need to automate, because we have a lot of full-time employees just doing boring stuff. 

I started last year, so I am a bit fresh in the organization. We have two people: One who analyzes and other develops.

I am using version 2018.4, which I find easy to use. We can see some major changes with each version. The IT department sort of hates that I come by every quarter of a year and want an upgrade, but it is very much worth it. There is a lot of stuff happening out there, and it's dangerous to be left behind by a few versions.