How do you or your organization use this solution?
Please share with us so that your peers can learn from your experiences.
We mainly use UiPath in CRM business process controls and transferring contracts to the ERP system. In addition, many information messages sent to our customers are managed by our robot. In this way, we provide more accuracy and efficiency by doing routine work with the robot.
We use it for financial use cases: purchase-to-pay processes, reconciliation processes, vendor payment, and merchant payments. This is just in finance. Then, we have retail order processing, order creation, PO generation, delivery note generation, and all those things in retail. We even have banking processes as well, such as a payments portal. We use it in most of the fields. We don't use cloud licenses. Most of our licenses are on-prem. We use both attended and unattended automation in UiPath.
We started using UiPath for our finance department where it provides us fantastic capabilities by automating one of the processes that is running overnight, a process which includes non-variable and repetitive tasks. Using SAP, as part of our regular operations, we have to submit some account details every night. We automated a process which was very time-consuming and structured, with rule-based tasks. Then we started with the sales department as well, on the promotion side. We are a beverage company and we have to set up promotions for our distributors and our customers. We have a third-party application that helps us with our promotions, but it's a very complicated application. We use UiPath to help automate parts of that application. These are two of the early and major processes which I have developed. As of now, we have more than 100 use cases which we have developed. Some are related to ServiceNow, some are related to SAP, and some are for Salesforce. We are using both its attended and unattended capabilities. We have more than 30 robot licenses, unattended and attended licenses. We are using their Automation Cloud.
I'm using it for automation.
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.
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.
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 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.
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.
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.
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.
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 processing of intended and unintended regulatory transactions in the banking industry. We are just starting to use the AI function of the solution.
Our company uses the solution to automate used to be a completely manual set of processes.
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 provide RPA solutions to different companies in FinTech, finance, and other fields. We are mainly working on their recently launched product called UiPath Apps, and I'm designing apps with UiPath Apps.
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 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 20 ERP developers and 10 solution architects. We plan to automate some of the business processes regarding financial reporting.
We use it for the automation of internal HR processes in our company.
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 suggested UiPath for one of our company's clients to automate DevOps processes. This is a part the company doesn't want to touch. They tried automating with Ansible Playbook and Terraform. We wanted to eliminate human intervention altogether. We are still transitioning from dev to staging and then production. We have done most of the research. We will move from staging to production if it works with our architecture and can be scaled. Our client is one of the biggest companies out there. There are maybe a million users worldwide. They primarily focus on the Asia-Pacific region, but there are also users in Europe and the Americas. The client has several web applications and a hybrid structure. Some data are on the cloud, while other data is on the on-premise servers. We created solutions for them over the years. We have an SI and DevOps team working in parallel for years. Our goal was to automate everything that could happen without intervention.
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 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.
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 have plenty of processes that need to be automated, including IT processes like user onboarding. We need to create profiles across all systems for every user that joins the company. There are also custom processes. For example, there is an insurance process when our company leases a vehicle and also a loan creation process. We need to automate internal hospitalization claims. UiPath handles all of the associated data and document automation. We use UiPath with Aviro for document automation. We use UiPath's drag-and-drop APIs, but not much because we only have three APIs connected to UiPath. We aren't using AI or machine learning because the AI applications weren't available when we deployed and our current license doesn't include UiPath AIs. In the future, we plan to use AI. Our current goal is to automate all the old departments. We've done about eight departments, and four more are in progress. After we complete this part, we'll implement the AIs. Until then, we're just working with the existing features. We use the on-premises version of UiPath, with all the servers running through on-premises platforms. We have separate database and application platforms and a robot that runs through the VM, so we have a separate VM blade for that entire robot. We also have another data warehouse for that storing that data. We currently run on 19.4.4, but we plan to upgrade to 21.10 in the near future. The latest version doesn't support Internet Explorer, but our co-banking system only runs on IE platforms. We need to rebuild our operations before switching to the new version. That will take some time because several large processes need to be automated. Until then, we will continue using 19.4.4.
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.
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.
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.
My primary use case is automation. I worked in multiple companies with the same product on the same profile, and most of them were automation. The actual business use case would vary from company to company, and project to project as well.
One of the projects we have been working on is for a medical company. It includes fetching medical records from the company's web-based portal. These records have to be pasted into Excel and consolidated. We then send them back to the client via email. We use Orchestrator to schedule the process to run every day at three intervals. It is running as an unattended bot. We have also used it for another company to help with their employee onboarding process.
The solution is used for automating repetitive processes within our entire organization.
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.
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.
We are partners with UiPath and Automation Anywhere. We use this solution for IT services and for the education sector.
We are using UiPath for automation processes in an insurance company in the finance department.
We have deployed a chatbot in our system.
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.
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.
We're doing mortgage loan processing. When people are applying for a new loan, we're using it to gather all loan documents and validate the property ownership and do a title search. We then put the loan documents in a package. We are using its latest version.
The solution has provided assistance with the removal of repetitive human transactional activities; document to text solutions; complex data extractions; cut and paste operations; information content management. This is either supported in promoting strategies with our business partners, or implemented at our clients, or included in products we develop for our clients. We use it in our own operations that have been migrated to other products or solved with coding or third-party software offering solutions to specific needs. Solutions are based on client sites and our clients pay for their own licensing.
Our primary UiPath use case is reconciling data and getting data from the web and writing to either Excel or our system. The automations are very reliable.
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 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.
We primarily use the solution for legacy data transfer, UI automation, CRM and ITSM automation, and call centers. Specifically, in call centers, using UiPath forms and form render has been really helpful.
We primarily use the solution for our clients.
I work at a financial firm where we do trade settlement activity. We are using UiPath for cleaning up data, doing reconciliation, and finding where the trade breaks and trade files are. It helps us lay the groundwork for the value add work, which comes later.
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.
We have multiple accounts sellable, accounts payable, corporate finance, and supply chain use cases. We have started some use cases at the factory floor automation 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.
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.
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.
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.
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 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.
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 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 work for a banking company. We use UiPath for tracing and collecting customer's credit information. We also use it to deploy a bot when clients have specific requests for changes to their information or accounts. We're able to change their service via these requests. We can also remove some processes of manual intervention. We've deployed bots across various processes. We have been able to remove human intervention for multiple processes and have seen a general improvement in terms of cost-effectiveness. We used to handle dashboards manually. Now we've turned customers into kind of specialists in that, whenever they want to change something, such as adding debit, or opening/closing accounts, changing addresses, et cetera, they can handle it. They no longer have to push that request through us and have us intervene. They can do it themselves using the bots.
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.
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.
I am a service provider and developer who implements UiPath for our clients. But in the company that I work for, we also use UiPath to make invoices for ourselves and, mainly, for payroll activities. We need to get reports from our HR tool and combine them with another source of information where employees are recording the hours they spent with various clients. We then create the documents needed for the IRS. In our case, all the users of UiPath are data entry specialists in different departments, such as HR, finances, and marketing.
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.
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.
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.
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.
I'm using the product primarily for building automation projects for shared services users. It's for internal customers. It's a shared services center for finance, HR, IT, and all processes like that. UiPath enables you to implement end-to-end automation starting with process analysis, then robot building, and finally the monitoring of automation. I use UiPath mainly for building a robot. I always use unattended bots. However, I also use it for task capture. I use the Task Capture feature a lot. It's pretty much a game-changer since Task Capture has become available, as creating documentation takes a lot less time than before. As for UiPath, I'm using it for building a solution and then testing using not only UiPath but also Orchestrator. In the end, we also use some document templates from UiPath. It's pretty much present all the way through the life of a project.
I am an automation lead in my company. I have eight to 10 people on my team. We do process automations, end-to-end automations, and any business application automations. We are implementing solutions to improve our organization's efficiency and speed of work. We are using AWS and Azure. We implemented UiPath on our Azure Cloud, so we don't need any physical devices or physical servers. We are now moving towards a hybrid cloud where we are using Azure Cloud.
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 am a part of an eCommerce company. Our company is separated across the country, and we have more than 30 locations/sales offices across the country. We have a couple of manual use cases that my team automated. One of those use cases is data entry. As an eCommerce company, we have a lot of data that we need to enter on time so that our customers can use and can order with it. We have a sales team of 20 people (out of 50 to 60 people) who are just doing promotions. For promotions, we need to analyze some financial analytics for the next month. Most of the time, there are various formulas in our Excel. Using UiPath, we have successfully automated this. This is a third-party tool where we just analyze all the promotions and sales per the market. Basically, we need to capture the price offered by our competitors, e.g., what is the price of their product? We need to analyze and set some good prices for our customers. UiPath helps us to accept all the information from over the web, putting it into Excel and saving it. We have a weekly activity, and UiPath helps us accept the data within five or six hours. We just accept the data from our competitors' sites and analyze all the information, then we set our prices. Therefore, this is a wonderful tool for processes, which we have automated in our area recently. We are using both attended and unattended automation. We are using Automation Cloud as well as doing work on Microsoft Azure.
Most of the automations that we work with are internal to our systems. We are also trying to use it with BPM.
We are using UiPath primarily for unattended automation. We are automating processes for business functions like finance and go-to-market. We have Orchestrator which is hosted on the cloud and we also have UiPath deployed on-premises. We have three different instances of Orchestrator: one for development, one for staging, and one for production.
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 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.
One of the use cases that I have recently completed is related to SAP and the interaction with Excel and our internal application. We are going with the JD Edwards EnterpriseOne ERP application and we used UiPath to help in this area, and were able to do so within a few days. Some of our people are going for process automation and some are doing desktop automation.
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.
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.
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.
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 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 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 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're mainly focused on finance for the time being so we've used UiPath for invoice processing and e-billing reconciliation. It makes sure that all of our converting information matches within our client databases. We've done a couple of solutions that track budget spend for certain clients, making sure that if the budget overruns or comes close to overrunning, then someone gets notified. If we get a new client or if a new legal case is opened, automation can make sure that all that information is then uploaded into our database. We've done a couple of smaller automations for the legal teams. These have been fairly basic ones though. There were a couple that download files from an email for them, and then rename them with the correct naming conventions, and saves them into correct drives. Another use case is to remove outdated users or information from our databases in line with the GDPR system.
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 a UiPath customer, working with them to develop some products. It is a bit of a mixed thing where we are developing some products with them from scratch, but they are acting as the provider. We develop things, and if they're useful for others, then others can use them. We are doing some pretty bespoke things to help us develop some solutions, but also help them develop their UI solutions in the legal area. We are working on a few things with UiPath to develop some search robots, some solutions to automatize subcontracts, and some timekeeping entries. These are several things that we are doing right now. We are doing three things with them: * A robot to help us with software for time management, automating time entries. * A robot to help us with filling in our engagement letters (contracts). * A robot to help us with various public searches, i.e., the automation of searches of the public record. We are adjusting robots from similar things that they do. The robots are not yet in production.
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 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 the '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 back orders. First thing, when they walk in the morning, they know what their back orders 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 distributor 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 in under. We have a vendor who delivers us a report daily of all their back orders because we use a main distributor, so they deliver us a back order 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 use it to automate searches in public databases. We have lawyers who need to search for various companies. For example, we are searching insolvency files for a list of business partners, so we use the robot to perform the search and notify clients about its results. Thus, it helps us with our work in searching public registries. We have the Studio license and attended robots.
We have developed a product for a court of arbitration. UiPath provides the automation engine behind it. Our product is a platform that is live online. It allows a party to provide some contract information, and the robot assembles a document and communicates with DocuSign, our signature provider. It then sends out a correspondence to the other party and manages the signature process for a bespoke contract for an arbitration agreement. This is a service that we provide to the world, pro bono, as it were, to promote arbitration and the adoption of a particular arbitration clause. It's accessible to all. Parties can log in and it helps them to negotiate and conclude an arbitration agreement in a mediated fashion. The robot sends out email on behalf of a third-party, a court of arbitration, and it helps the parties get that agreement done. It's about concluding an arbitration agreement before the dispute goes any further.
RPA - Novigo Automation Framework Solutions - Setup an Automation Factory Model. Automation Focus has been Productivity, Quality, Cost, Process Optimization, and compliance. Focused on delivering Process Automation for Oracle EBS ERP application for various departments including IT, Finance, Operations, Engineering, Sales .etc * Manufacturing: Master data maintenance & monitoring Inventory transactions, BOM error fix & transfer, WIP issue & complacent * Finance: Financial closing, IC transaction, security & FA master & transactions, Master data, duplicate check, auto-CM creation & auto-payment, Customer Master, running letter, print errors & auto-receipts * Supply Chain: Sales order Integration with the portal, shipment, RMA, digital shipping & backorder, item cost update & inventory interface, procurement, receiving & monitoring * System Admin: Access provisioning, - Creating responsibility, Monitoring pending transaction & analyzer.
I am using it for a project that we did for our client e.g HR automation in which we create, update, and delete the employee the database which includes master data management, active directory, and SNOW as the used environments for the solution.
Start small and then excel it is important for the Organization to increase the awareness and literacy about RPA.
1. You will need to start with Task Automation in most of your initials automation. ( Don't think big to start or else you will end up with only discussion no conclusions)
2. These tasks will be tied up to some part of the business process. ( Please see the tips below)
3. Focus only on task automation with a simple rule of targeting tasks that consume a lot of time of your IT/Business Users.
4. As a quick win go ahead with IT automation cases 1st and they easily help to spread awareness within the business by doing Show-n-Tell session with business.
5. It took me 2 IT RPA cases as our 1st quick win and took me 41 sessions with business users from various departments to get the pipeline for RPA cases.
6. If you follow this mantra you will soon see the results flooded with RPA opportunities - we have 40+ Identified cases and 175+ cases on task automation for ERP.
Please find attached snapshots :
1. How to Choose a correct RPA case: https://drive.google.com/file/d/1NtwVaaxP-fpHgkP4hQNAZilq0xiDC1HW/view
2. RPA Case automation life cycle as you mature -> Task -> Component -> Sub-Process -> Process: https://drive.google.com/file/d/140zUzHTwSZ7lwEibOLt1JsNUZeMt7NNu/view
1. Identify RPA cases which are Highly-repetitive, Highly manual, Too many FTEs required.
2. Information intensive activity: Copying, pasting and validating data between systems, portals, application, pdf/excel files etc.
3. Rigorous keystrokes and mouse clicks, Hopping between applications
4. Any mind-numbing office task that kills time and energy
Our primary use of this solution, as a company, was to eliminate or at least simplify and reduce the number of boring, repetitive administrative tasks that take our precious time. We are a business consulting company and lots of clients try to contact us on multiple channels that we are available on. Our company, in partnership with UiPath, implemented an unattended robot that saves our time and energy. We call it our colleague that works independently, full time and helps us without requiring emotional support.
We use robotic process automation to automate the business process of the company. We are using the Oracle JD Edwards. We have automated the HR process for the payroll and payslips. We used UiPath for the scanning of attachments and uploading/attaching them in the Oracle system automatically. Previously, we used to take a day or two in doing so. Most of the daily human errors are minimized. We used this for automated internal requests including automatic reconciliation instead of several clicks from the user and automatic correction of the master records or any change required.
I have been using UiPath in the healthcare area and right now, I am developing a healthcare project. I have also used it in retail projects and we have automated entire retail systems for vendors and customers. This has given them more reliable action and product services that are beneficial for both the organization and the user.
We have a system to create a multiple orders to perform automation testing. Here, UiPath helps us to create a bunch of orders without the hassle of creating a separate automation suite for this need. When creating orders manually became a tough job for the user then it needed a benchmark for us to resolve this kind of situation to make teams more agile at work. This motivated us to find a solution to counter this problem in our organization. Definitely, it has helped to make us more agile.
I started using UiPath version 2017.1 and currently, I am using 2018.4.6. We had a requirement of fetching emails, which are basically requests from clients filled on our website form. We read those emails and process the data filled by the user in the form. There are different forms like a request to provide reports, a request to add or delete a user, etc. After reading these emails, the bot has to take the necessary action on our Primary CRM application. Depending on the request type, the bot will navigate to the necessary module in the application and perform the request as defined in the email request.
We are a company that provides technical services and this is one of the solutions that we implement for our clients. One of our use cases is to help automate simple processes for banks.
In our organization (Global Business Services), we do a lot of automations in the Windows environment. In the past, we've used a lot of VBA macros and VB scripts but maintaining support for more than 1000 macros has become a very difficult task. UiPath, as an end-to-end RPA solution, solves many issues and limitations of the previous setup.
UiPath has been quite useful in terms of getting data from thousands of webpages online and arranging it in a predefined format. You can easily create robots and define operations in Uipath.
Primary use cases involve the following automation environments and processes: * Oil and Gas Domain: Automation of various applications specific to this domain such as Gopher, Tow, Toad, Excel, and various browsers. * 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. * 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.
I have worked in many industries and domains like healthcare and finance. I have automated web-based applications and Email automation. Automated an end-to-end process that starts with the user raising a request in BMC Remedy. It handles requests for respective Roles in the GRC System of SAP. This process includes identifying the Request number from the BMC remedy Ticket. The BOT identifies respective control owners for requested roles and requests the controlling owner for their approval. Then BOT performs the Approval/Rejection process accordingly.
I've used UiPath Studio to develop Automation projects that help me automate repetitive and manual tasks. This lets me focus on other, more important jobs to do.
Our primary purpose is to automate our internal processes so we can increase our profits and reduce our headcount. We are an IT service provider, so our main focus so far has been our Service Desk but we are starting to work with our Finance, Payroll, and HR teams in 2020.
My primary use case of this solution was to automate BMC Remedy and SAP use cases. I used UiPath to automate various tasks in SAP. I developed several bots in client virtual machines using UiPath and then connected the virtual machine to the UiPath Orchestrator. Once connected, I scheduled the Bot.
One of my primary use cases is invoice processing. In this process, there are two applications including one for data and the other for the main application. The main application needs to take invoice data from the data process and match it with invoice details that it has. After this, the status needs to be recorded in the data process.
I actually went for a powerup automation hackathon conducted by UiPath, which gave me the idea to implement this in my organization. I used the product, experienced it, and I'm here. UiPath reduced a lot of manual work and I am getting positive reviews from the company.
The primary use case for this solution is to reduce manpower and achieve the best result with minimal time compared to doing tasks manually. This is a great advantage of this product because when doing tasks manually it takes many minutes of time but when the bot does it, it is finished in a few seconds.
We use UiPath for: * Financial domain * Excel automation * SAP automation * Citrix automation * Usage of Orchestrator queues * RE framework * Automating password resets * Security and governance * Rule-based exception handling * Large group deployment * Centralized repository for version control * Execution logs and credentials
UiPath is the go-to tool if you need to automate tasks that can be combined to create an automated process. We provide services to customers using UiPath. They come to us with their needs, be it to improve performance, accuracy, or reduce costs, and we help them by automating processes that, most of the time, consume too much in terms of unnecessary human resources.
My primary use case of this solution is automation. Where there are tedious tasks, we use the automation in those areas or sectors. I am a trainer and learner. It also helps others because it does not involve much coding.
I'm working at a computer software company, where we're bringing digital transformation using UiPath. All rule-based and mundane tasks are identified and automated using RPA. We have about 25 bots in production now. Data processing, file handling, email automation, and related activities are running in production.
We use this solution to automate business processes and save millions of dollars in operational efficiency. We are developing new automated solutions for our clients and partners, and also training new developers to use this tool to deliver great results by the end of the year.
I am using UiPath RPA for my ERP entry where I update hundreds of data elements within minutes by RPA robots. UiPath gives you the degree of freedom in these robots to work according to your requirements. It is very easy to use even without coding knowledge, and it can be implemented with little knowledge of RPA.
I am an RPA developer and I am primarily using this solution to fill up timesheets in an internal portal. I use Windows 10, 64 bit. My team uses a mix of Windows 7, 8, and 10. It is suitable for daily and weekly tasks, which pretty much don't change over time, and is what I choose to automate parts of my team's work.
Our primary use case is RPA Consultancy for clients. We have been building robots for our clients in many environments. These include attended and unattended robots that are on both web-enabled machines and local machines (Due to Security Concerns). They span across many industries as well.
We primarily use UiPath to bridge process gaps between various pieces of software. Overall, it is a cost-effective tool to quickly move data and reduce repetitious tasks. For example, we use UiPath to produce SAP reports, format the data and then enter it into reporting tools.
I use it to provide training on UiPath. In the past, I have used UiPath to automate the debit card activation web portal. The task is to read data from Excel and put it into the web portal. I used it for DMS portal automation as well, after reading scanned PDFs and updating data in the DMS portal.
We primarily use this solution for one of our business use cases. We are building robots with Safyr CRM. They are scheduled by Orchestrator and we are handling every step: Solution, design, followups, stacks, consulting, and finally implementation. Nowadays we are using robots internally but we will start with third-party clients in 2020 Q2.
I am responsible for developing and improving RPA-software bots in my organisation. The processes we work on improving are in the field of finance. We started using UiPath and RPA as a technology about two years ago and are still improving and growing.
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 work with third-party recruiting software to organize candidates and track applicants. We utilize the bot to pull information from these pages and organize it and run actions. Utilizing the bots to screen resumes helps prevent time being wasted on initial tasks around recruitment.
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!
The primary use case of this solution is to automate the repetitive tasks in the workplace. UiPath is connected to the Orchestrator to centrally manage the robots. Mobile Orchestrator is what we use to control the robots using Android and iPhone mobiles.
I am using UiPath for automating finance processes. One example is AP invoice processing. I am integrating ABBYY with UiPath so that we can easily extract information from an invoice with different templates. Then once done, the UiPath robot will input the information into an Oracle system.
We are doing some RPA projects for our customers at my company. Our customers are really good in their area. We are using UiPath studio for creating robotic process automations and using the Orchestrator for monitoring processes.
I use it professionally to build software robots for an international company.
My primary use case for this solution is to create a more user-friendly process automation system so that customer eccentricity can be on top. My company's employees can perform in a better way with increased efficiency and greater redundancy. In general, they can handle tasks in a more efficient manner.
We use UiPath for process efficiency and task automation. Our primary use case is process automation and avoidance of manual tasks and activities, reducing human errors and leaving resources to think on tactical and strategical matters rather than executing non-value-added activities.
The first process automated by this solution was downloading reports from SharePoint and injecting them inside an Excel sheet that was filled with formulas. This was done in order to produce output files that are then uploaded back into SharePoint and sent by email using Outlook. The environment was Windows 10 (desktop), and the process uses the user interface to do all of the SharePoint tasks, except for the Excel ones, which are made in the background.
Our primary use case is the Automation of invoice processing. We're looking to automate some processes like invoicing in order to make the organization more efficient and reduce workload for the employees. Invoices are non-structured or semi-structured data, so we're going to use OCR to extract the data and then automate the invoice process.
The solutions or test cases where we have used UiPath are: * Formatting different types of files (.csv, .dat, and .xls) to .txt * Reconciling data between different applications * The direct-debit application process We deployed the solution inside a virtual machine in Cloud.
We use UiPath for building business cases for customers and internally building RPA competency within my department. Our organization is just starting to implement RPA. As a business consultant, UiPath is our chosen solution for RPA implementation.
We primarily assist clients in deploying UiPath within Finance/Accounting and Internal Audit but have also realized the benefits of deploying it within our accounting function to assist with expense reporting and invoice processing. We have also successfully complemented our technology solutions practice, which deploys ERP systems such as Workday and Coupa, where we have built some specific automations to accelerate deployment and assist with normal processing.
We have IT solutions that are oriented to service our call center because we are a contact center company. For example, we have a CTI (Computer Telephony Integration) solution to help manage our phone calls. It is something that we developed in house. We are developing a UiPath (the company that acquired ProcessGold) solution using RPA robots to improve our processes. So, that is our main use for the ProcessGold solution. We use the UiPath product in order to reuse processes that we manage better and use the time of our agents more efficiently. When we established a connection with a client by phone, our agents spend a long time talking with the client and are also responsible for doing some back-end tasks. In order to reduce back-end tasks, we use RPA robots to reduce the time you need to spend on follow-up calls. For example, after a second call with the same client, you may need to fill in a form or a CRM entry. If we can simplify this task of filling out a form where we insert all the information automatically the robot saves that time. That is the main idea and the reason we use these robots.
My primary use case is data scraping and entry for an insurance firm.
Our primary use is RPA in insurance.
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.
We use the entire UiPath suite for healthcare revenue cycle management. Our automations are not run 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 it a four. On a scale of one to five, judging how beneficial it is, I would rate the training a four. The information about the automation processes was really useful. At the same time, I would suggest including more industry-specific training and knowledge sharing. From the point that we purchased our UiPath license until we had our first robot was approximately one month. I felt that the process was straightforward. It was very intuitive. Most of the resources were available to us and we've got it up and running with no problem.
We have a bunch of uses for the product so it is hard to judge which is the most important. We started working with data structures for websites and then moved into more complex automation like speech detection and making more cognitive decisions based on rules. Our automation using bots is essentially on the verge of using artificial intelligence.
We use all of the products in the UiPath platform. We have use cases ranging from back-office to manufacturing, which include large project management, accounts payable, accounts receivable, and treasury management. Most of the areas in the company have processes that we have automated. We run our automations in the Citrix virtual environment, although we are unhappy with Citrix. It is pretty bad, and it's very difficult to keep up the performance. AVS or Azure do not offer a good service yet, but we are looking for alternatives with respect to the 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. We have been using UiPath for quite a long time, and we have seen this evolving. It has been getting better over the last few years. On a scale of one to five, judging how beneficial it is, I would rate the training between three and four. The training is good, but the content doesn't have the depth required for people to go ahead and do something if they're not technical. It's still pretty high-level. From the point that we purchased our UiPath license until we had our first robot was three to four weeks. The process is getting better, but when we started in 2016 and UiPath was small, it was good but needed refinement. I would have rated it three out of five back then.
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.
Our primary use for this product is to automate processes that we are capable of automating at our tier-one level human resources center.
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.
We use Studio, Orchestrator, Studio and Orchestrator right now for RPA development for automating pretty much anything that rules-based processes can accomplish that are mundane and take time.
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 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.
We play significantly in the BFSI and healthcare space. A lot of use cases have been related to BFSI. Insurance is much bigger, with claims and underwriting, policy admin, health benefits, and so on so forth. There are also good use cases on the functional level, HR and finance, and that cuts across industries.
We primarily use the solution for insurance processes where we have redundant activity and we have pain points for our customers. It allows the employees to do more insightful work.
We are using Orchestrator for both development and production. We are using attended and unattended bots, and we are using Studio to develop them. We use this solution for front-office processes, back-office processes, IT processes, and automating anything that we can. We run our automations inside a virtual environment. We use Citrix and Citrix Server. We have sixty-seven processes that we've automated to run in the virtual environment and its very straightforward. It's deployed out of Orchestrator, and for attended processes, it's as simple as going in, opening a UI robot, and clicking the start button. It's phenomenally easy. 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's a five. It's very easy. I'm a software developer by trade and I was able to automate several processes in a very short time span. In two weeks I can automate an entire process, end-to-end, which is incredibly fast for the ROI. One of our processes was extremely complex, which was our customer onboarding process. The complexity was, in part, because it is handled by six different departments. The PDD for it was one hundred and forty pages long. One or two we've done were simple automations, and the rest have been medium to high complexity. My first robot went into production within a month of me being in my position. That included going through all of the UiPath training, getting familiar with our IT systems, and then actually vetting out a process and automating. On a scale of one to five, judging how beneficial it is, I would rate the training a five. It was very informative and very detailed. We are using the unattended robots more than we are the attended ones, and we're trying to continue that drive. We understand that there's a need for some processes to run attended, but if we can, we do process optimization to make it work and be unattended.
We are using Orchestrator, Studio, attended and unattended robots. I am on the business analyst side, so I do not have much experience with Orchestrator. We are using this solution to automate processes for our clients. They typically have mundane processes or something that's super repetitive, that we're able to quickly automate for them and see that return. We did do an attended bot with them as well, to improve their call center. With respect to how easy it is to automate our company's processes, on a scale of one to five, I would say it's a four. This is a rating from the business side, as opposed to the development side. We understand what the features are, and when new releases come out we have an understanding of what's feasible. I am not rating it a five because sometimes we do not know whether a use case is feasible or not. It means that I may have to speak to one of the developers to see whether it can be done with the tools and the features that are out there. We host the UiPath Academy RPA training every other month for our clients. I have not taken the full course, but on a scale from one to five, I would rate it a five. This is based on the number of people who sign up for it and look forward to attending it, just to learn the basics of RPA. In terms of how long it takes from purchasing a UiPath license until having the first robot, the average is probably four weeks. It depends on the complexity of the process.
We use only unattended robots with Studio and Orchestrator. Our primary use for the bots is in finance, so we only do finance use cases like AP (Accounts Payable) invoice retrieval.
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 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 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 are using UiPath Studio, Orchestrator, and attended bots. We are automating twelve 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 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 have two customers. One is in the insurance industry. We are implementing it within our own company to automate HR and finance processes: back office. This is the same thing with the customer: back office. That's the focus. We are using Studio, Orchestrator, and attended bots. We are not using unattended bots yet.
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 Studio, the Orchestrator, and we have attended and unattended robots. Our primary use case is automating back-office processes from the corporate side. One example is the automation for ticket closure for some of the customer complaints. We also use it to fill information gaps between systems. Instead of having information run through standard APIs, we have it copied over from one system to another. We run automations in a virtual environment, and the implementation was pretty easy and quick. We used the Community Edition before purchasing our license. From the point that we purchased our UiPath license until we had our first robot was approximately one week. We found it to be very easy and very fast. We, as a Contact Center, usually face a lot of problems when we suggest any requirements. When we started with RPA, it took approximately one month for a very complex process to be automated. 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 is very easy. You can use the UI, or you can use APIs for the connection. In the end, you can do it. On a scale of one to five, judging how beneficial it is, I would rate the training a five, for sure. In two or three weeks, an RPA developer can do everything.
We are in the finance industry, so we use Studio and Orchestrator to automate a lot of Excels and making reports.
We are using Studio, Orchestrator, attended and unattended robots. Our primary use for this solution started with automating processes in finance, procurement, and HR. Now, we are researching various directions in logistics. We do not run our automations in a virtual environment. This is something that we are trying to avoid. 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'm an IT-based person, and for IT people it is easy to learn. UiPath claims that it is easy to learn and it's for everybody, but it's not true. For business people, it is hard to learn and hard to understand how to code to make things work. They need a lot of help with things like exception handling. If somebody lacks technical or programming skills then it makes it much more difficult to use. Although UiPath is getting closer to business users, there are still some basic skills that they need to have to make it work. On a scale of one to five, judging how beneficial it is, I would rate the training a five. When I get new hires it doesn't matter whether they have previous experience in RPA or development, they have to go through all of the basic training from the Academy. This includes the Orchestrator and I've been recommending SAP training because we are experiencing growth in the use of SAP. Going to my team, this is the base, and then we have created our internal framework and standards that also require training. Some people may already have experience with UiPath or Blue Prism, but they still need to take the training from the Academy. Before I arrived at the company, there were already some automations running. However, fifteen months ago we shut down a couple of robots because they were failing terribly. From that time, it took us five months to create the first robot.
I am a developer so I primarily use Studio. Once the bots are developed they go to Orchestrator. We have a combination of different use cases. Sometimes it deals with Outlook, the Microsoft Office Suite, or certain integrated web applications. You build a solution to integrate all of the applications that are part of the same process. We do not run our automations in a virtual environment at the moment, but we are currently evaluating how we can do this. 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. The majority of the simple tasks are done through recording, which saves on our development time. You just record the things that you want to achieve and then customize to get it going. Since I was new to the product, I used the training. I took the developer training, as well as business analyst training. On a scale of one to five, judging how beneficial it is, I would rate the training a five. It's truly very beneficial because you can just touch base with the actual tool and get it done. From the point that we purchased our UiPath license until we had our first robot was approximately six weeks. This was a complex use case and it worked well, so it was a good proof of value.
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.
Our client's companies have extensive issues with SAP and getting information out of it. They have another technical ERP system with an in-memory database where they don't get the information out of it, then have to add it manually to SAP. That will be probably the first big use case for automation. So, we will get a bot reading it on the database from the Citrix environment and probably moving it to SAP. The client will probably have it on-premise. They tend to be really risk adverse in terms of Cloud solutions. We have tried to get them to use the cloud more because it's just easier. We are using Studio Orchestrator, and unattended bots. I have programmed attended bots before.
Right now, the primary use case is document retrieval from our client system. We are a healthcare billing company, so we have to pull things like medical records and different documents from hospital stays. So, we used the robots to pull those versus an FTE. We have both unintended and attended robotics that we use. We haven't really delved into Studio a lot yet. That's going to be part of our staging and going into the next phase. We built all of our basic bots, so now we're going into the more complex bots. We are on-premise. We were looking at moving to the cloud, so that will be something in our next steps.
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.
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'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.
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.
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 this solution for our business purposes. We use it from the back end all the way to the front end. That's where we are looking to use this, although we haven't fully implemented it yet. We are exploring more processes to use it for.
Our most prevalent use case is invoice processing. We are using Studio, Orchestrator, attended bots, and unattended bots.
We use Orchestrator, Studio, and Robot to work with automation in our finance department.
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 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.
We use Orchestrator, Studio, and of course the bots for indexing documents received from outside providers.
I use Studio, Orchestrator, attended and unattended robots. My primary use for this solution is back-office automation in a banking environment. We run automations in a virtual environment, both for development and production. The robots are implemented in a development environment first, which is connected to Citrix. Once the process automation is finalized, including deployment and UAT has passed, we move the same file from the development Orchestrator to the production Orchestrator in the production environment. Production is also in 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 three. We have legacy Oracle applications and I'm finding it difficult to find selectors for the older, legacy systems. On a scale of one to five, judging how beneficial it is, I would rate the training a four. Some of the lessons are really easy, whereas others are more difficult, but you need to finish everything, otherwise you cannot go further. This is what I didn't like about it. It took approximately one month to implement our first robot. Prior to purchasing the license, we implemented our PoC using the Community Edition. That took three weeks. After that, my company bought the license and it took about a week to put into production.
We don't have a single primary use case. We use the Orchestrator studio to deploy attended and unattended robots to relieve the workforce of the mundane tasks that they currently do.
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 currently use an on-premise Orchestrator instance along with VDIs for Studio development, testing, and production Robots. We use UiPath in a few different ways: for repetitive high volume and or high complexity time-intensive tasks, for tasks with high error rates and or low error tolerance, and as a component in larger digital workstreams requiring the interaction of multiple systems and workers.
We use this solution mainly for data validation. To start with, we are using Studio for many of our processes.
We are using Studio and Orchestrator. Our primary use case is automating data processing for clients translating into other systems. 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 three. I think that the technology that we use in the printing industry is a little more difficult to automate. I am currently involved in the UiPath Academy training. We have third-party contractors who have been doing the development, and I am the first internal employee who will be developing. I find that the training is good in the first step, and also in the second step where we're learning about Orchestrator. However, when it moves to the third step and they are talking about the framework, I think that it is a pretty big leap and that is where I'm struggling. This is the section that I am in right now. There was one project that was completed before I started, at my understanding is that from the point that we purchased our UiPath license until we had our first robot was less than six months. For my project, it has taken two months.
Our primary use case is IP invoice automation. We are currently using Orchestrator and bots.
We are using Studio and Orchestrator. We use this solution for financial analysis, accounting, invoice processing, and other menial tasks. We run 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. The ease of use comes from many things including the user interface and the coding. On a scale of one to five, judging how beneficial it is, I would rate the training a four. I feel that you can have people who are directly thrown into the training, but sometimes it is difficult for people to pick up on topics that are not related to the processes that they are dealing with. From the point that we purchased our UiPath license until we had our first robot was approximately two weeks. The implementation was straightforward both on the setup and the development side.
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 Orchestrator and unattended robots. We use this solution for automating financial tasks. Some of our use cases including reconciling amounts, such as those related to invoicing. We run some of our automations in a virtual environment. We have been running into roadblocks with Citrix, so we run them on virtual desktops. 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. Building automation using a standard set of rules is not a problem. It can become problematic depending on the data and the types of tasks. On a scale of one to five, judging how beneficial it is, I would rate the training a four. We are using it to gain experience with the platform. From the point that we purchased our UiPath license until we had our first robot was probably three or four months. The first robots that we created were for account reconciliation, and the implementation was straightforward.
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 use Studio, Orchestrator, and robots. 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. It's been going for about six months now, and we are still having challenges here and there. On a scale of one to five, judging how beneficial it is, I would rate the training a three. The material is on the technical side, and not being a technical person, it makes it pretty challenging to get through. From the point that we purchased our UiPath license until we had our first robot was approximately three months.
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 use unattended robots and the Orchestrator module. I am most familiar with the Orchestrator. We are very new to this solution and just getting into it. We are a financial insurance company and we do VoW, Verify on Web. We have a bunch of different insurance carriers. We run automations in a virtual environment, VMware, and I haven't seen any problems 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 it a five. For my part of it, this solution seems very useful. I have limited exposure to it because I do more of the installation, the configs, etc. I don't really work with the workloads, although I see what is being worked with. We have our in-house developers who are doing the integration into our in-house programs, so I watch what they do and it just seems that it's very easy to pick up on. I have not used the UiPath Academy, although I think that the developers have. I did not get any feedback from them about it. I was not involved at the time, but I think that from the point that we purchased our UiPath license until we had our first robot was approximately three to four months.
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.
We are using Orchestrator and Studio and we are using both attended and unattended robots. We use this solution in the compliance space to manage risk. We do not run our automations in a virtual environment. With our first process going into production just last week, we are just new to RPA. The RPA involvement across our organization is very small given our stage of development, with less than ten people. These are both developers and business users. 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's about a three. The software itself is relatively straightforward and easy to use. However, the task of automating processes can be challenging. Each company is going to be different than others. My experience tells me that process automation perhaps is not as straightforward as businesses may think it is. On a scale of one to five, judging how beneficial it is, I would rate the training a five. I found the training at the UiPath Academy really good and easy to understand. We were able to download trial versions of the software and apply our training to the trial versions. It is very straightforward and easy for .NET developers to actually use the tools. They felt comfortable, and there was nothing new, just a different way of doing what they do. My company is probably not a good example of judging how long it takes to build your first robot. We implemented the system and did the process at the same time. So, combined, it took several months. Going forward, because we're no longer putting a system into place, I expect that timeframe to shrink significantly.
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.
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 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 solution for the financial processes.
I am a developer so I primarily use Studio most of the time, and when the bots go live, they move to Orchestrator. We have a combination of different use cases. Sometimes it is dealing with Outlook or the Microsoft Office Suite. The idea is to build a solution that integrates all of the applications that are part of the same process. We are not currently running our processes in a virtual environment but we are currently evaluating how we could make it work.
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.
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 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.
I'd say our finance applications, like accounts payable, have been our biggest use cases for this solution.
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 this solution for a POC and Pilot stage for RPA deployment.
I use this solution for the automation of Accounts Payable invoices.
The primary use case is for a medical claims process automation using UiPath RPA.
We are checking products in search of a better RPA solution for our landscape.
We use this solution for automating manufacturing processes from invoice processing to accounts payables. All of these use cases are solved using UiPath. For insurance sectors, reconciliation is another process that is automated using UiPath. I have been using UiPath at various enterprise levels.
Our primary use case is to develop automation projects, like automating Excel activities for repetitive tasks and operations on files. We also automate operations on Citrix. With UiPath we can easily manage all of the projects in a single page (i.e. in orchestrator).
The primary use case of this solution is to generate a report by scraping data, filtering it and combining the data for input to another system.
We primarily use it for delegating access permissions to help desks, for example. We use it to automate certain things, like onboarding new users, or deprovisioning leaving users. When we add somebody to a group, it triggers some kind of automation workflow. Lastly, we use it to sanitize data entry, so to make sure that capital first letter in the street name is used, certain zip codes aren't allowed, others are, etc., so data is controlled.
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 are using UiPath primarily for process automation. We are trying to consolidate information, eliminate redundant manual tasks, and save some money.
We use UiPath to log into a system, run a report, extract the information from the report, and send emails to hundreds of people, all in just seconds.
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.
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.
Our primary use case for it right now is in human resources. We are using it as a recruiting capability where we receive resumes in from recruiters, one in particular. Then, we're looking at the emails, pulling data off the resumes, and loading it into a database. We are also identifying resumes which might need some additional clarification. This saves a lot of time, so somebody doesn't have to go through each email, evaluate them, and pull the resumes down. Our customers are the DoD, mostly, and some civilian agencies.
We are using it for financial applications in the financial sector. We also have a couple of bigger federal customers who started RPA development on their own, then needed our help. Internally, the RPA offerings team is developing more resources, so we can support all our customers. This involves a lot Pegasystems, ERP, and homegrown systems.
The primary use case is data management.
One of the main use cases is stringing together different applications, like a financial system to a database for data manipulation or data extraction. Then, all sorts of little things are added onto that from a process prospective.
We are trying to focus on using UiPath for our mission. A lot of people use RPA for things that happen everywhere, such as in financial or HR. We are a bit different. We are trying to focus on things which will improve what our customer are doing. For example, one of our customers is a bank. Therefore, we are focusing on improving their relationship with the bank's customers by using RPA. While there are use cases everywhere, we are focusing on trying a company better and more streamlined at their core.
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 work for the financial management office. We do a lot of manual processes. Our use case right now is that we look at all of our financial business processes, break them down, and identify the subprocesses that we can use UiPath to automate. This is very manually, so we try to find some efficiencies which have the most the value for our organization.
The primary use case is invoicing and billing. The first thing that we used it for was some content migration from one video hosting provider to another. We later on moved to invoicing and billing, which included time sheets, management, and feeding data into our accounting system.
We have multiple primary use cases for UiPath. We have already implemented three, but I foresee many use cases in the future. For example, I am working on one which will automate the gathering of information to comply with subpoenas.
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 automate processes across a number of different agencies. We automate whatever use case they determine. We tend to focus on the financial management side, but we have other areas that we've delved into such as HR and general data pulls for executive dashboards. Oddly enough, a lot of our clients have not focused on work where there are people actively doing the process already. They've chosen to focus their efforts on processes for which they haven't had the manpower. It has been a little bit of a challenge in that the use cases tend to be coupled with a lot of process-development stuff. We have to figure out what the process is before we can even begin to automate it. But over time, we plan on trying to shift that focus back to areas where they have a large number of people doing a process all the time and getting them to shift those people into doing the complex processes where there isn't a structure already determined.
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. * How do we help the government realize these benefits? * 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.
Internally, we use UiPath to automate financial transactions, specifically for invoice processing. Externally, on the client side, we use automation in the financial space, primarily. There are various use cases from generic file uploads to transaction processing that we implement for our clients.
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.
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.
We have multiple use cases. We are a distributing company, so we are moving containers around at sea. There are a lot of things that you need to do around that. We are trying to automate to help with our bookings created, etc.
The handling of different types of insurance tasks.
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.
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 have a lot of maps worldwide which order some stuff from my department, and this is the compiled path. This goes into our database, then it comes to us.
We are mostly using it for HR processes. We have two departments: Accounting and HR/Payroll. However, we mostly use it for payroll and travel. We are only using Unattended Robots. We need to start talking about Attended Robots more.
I'm not using it myself. I'm working around it with consultants. I am in network IT. I have seen the product at work and tried it myself. It is sort of easy to use.
The primary use case is to have a platform which allows us to scale rapidly without adding a lot of human labor. We are looking to go global without being dependent on recruiting heavily on back office functions.
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 use it for customer-facing and internal processes.
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.
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).
We are working on trying to optimize some of the current processes which have been selected for review. I have been talking with our business partner to try and find the best way or tool to optimize these processes.
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.
We automate mostly finance processes, which is our largest area. We also automate some HR and logistic IT processes.
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 primary use case is business services (finance).
We use it to automate functions in supply, finance, and HR.
We are working on changing all the administrations tasks at the college. For example, with travel refunds to the students, students currently have to go from their homes to the school before they can be refunded their expenses. We want to make a robot which does that instead of the people doing it. I'm using a measurement tool for distance to calculate the measurement from student's homes to the school. Then, this should calculate the amount the student should be refunded.
We are looking at processes and automatization and are at the very beginning of our journey. We have been looking at finalizing the job and making the use cases in insurance assistance.
Getting data from the SharePoint site and processing the data with business logic, and after this, inserting the data one by one into the QuickBase site. The environment was development, QA, and production. We are working for back office automation so work with Microsoft office products.
I have tried the RPA tool for the first time and I already love it. How easy it is: you can do all of the daily tasks which you repeat at one click. Primary use case: educational purpose and automation for content writing. Secondary use case: additional content writing and data scraping.
As a system administrator, I have to create a roundup report before the office begins and at the end of the day. The report consists of statuses of each thin client we have. The robot does all the stuff in just 2-3 minutes, saving our 1-2 hours of time done by a dedicated person.
I have been using UiPath for quite some time now, and I have realized that it is one of the best automation tools out there. We primarily use this tool for automating our business processes and removing repetitive work with the help of automation. The most interesting part about this (easy-to-learn) tool is that it is accepted almost everywhere in the RPA industry. There are a lot of activities in this tool which will help you automate processes easily.
* Primary use case: Excel automation and email automation. * Secondary use case: PDF scraping and CSV management.
Our primary use case is to create a proof of concept using UiPath. Here we automated the business process, and it's a repetitive task. So we used UiPath and automated our internal project, and we also automated the client process as well. We automated SAP application, and we also automated mainframes. UiPath also has the Orchestrator which very flexible.
Reading non-PO invoice details form a SharePoint form, validating it, sending it for manager approval, and on receiving manager approval, entering the invoice details with invoice and approval attachments to SAP.
To automate various business processes which include generating reports, data entry into certain applications, email automation, and web automation.
* Automating web applications is the primary use for my organisation. * Also, data scrapping is another main usage.
Work automating demands of our clients like emails and withdrawal of data from PDFs to database.
We use it for price quotes on the internet, looking for the best cost benefits for our customers after researching our thefts, creating a table and sending the data by email to the customer.
The main request of our clients is the integration with the SAP system and specific tasks of email, like sending and downloading of NFS.
The primary use case is probably the swivel chair operations where data is extracted from one system and used as input in another.
* Automatization of the collection process, downloading information from the web to Excel, and processing this information in our core systems * Policy issuing for standard products * IT: security accounts maintenance * Regulatory reports.
The robots have completed the job in a short time by reducing the personnel load.
We use UiPath internally to automate the repetitive processes of our company. We use the tool for the generation of reports and automatic sending of emails, as well as automation of registrations and the likes.
The software is used for automating the process improvement and simplifying workflow as our organization is an insurance-based organization. Also, it is used to create some small repositories which can be used for future use of process improvement.
To automate day-to-day tasks for the user in the current project, for example, reports, tickets, price quotation and sending and receiving e-mail.
We started with UiPath to automate activities that required gathering data from different applications and posting the data to another app.
Account opening and order placing for insurance application with web and Windows application and mailing report.
To reduce or eliminate routine manual and clerical tasks, and to reduce manufacturing lead time.
Gone are the days when you have to deploy 100s of people for repeated tasks. We regularly update invoices of different channels and merchants to our workflow. Capturing each invoice requires some human attention. There are chances of using OCR or text-based extraction of invoices. We easily automate each type of invoice extraction to our spreadsheet. This reduces one hour (max 1.5 hr) of 100 employees in our organization.
I have performed the following use cases: * Excel operations: taking data from Excel and using it in the desktop automation (environment: Tally ERP, MS Excel). * Email automation: sending, analyzing and receiving mails (environment: MS Outlook). * Security-related: such as getting reputation scores of different IPs and sending a mail for each IP which is found malicious (environment: McAfee ESM, different websites to get a score of the IP, MS Excel to store the score of each IP, MS Outlook to send mails to the concerned person). * Invoice processing: taking data from a mail and using the OCR tool to extract details of the invoice, inputting the data to a desktop application provided by the client and sending a mail after the successful completion of the task (environment: MS Outlook, Kofax). * Web-related use case: taking data from Excel and onboarding to a web application (MS Excel, web application).
Automation of high volume, repetitive processes. Both desktop and VDI/Citrix environments. We are going to implement it in the WFM team to reduce their workload and let them concentrate on more complex tasks.
I basically use UiPath robotic process automation for everyday processes that can be done without my intervention.
UiPath is used as an RPA platform to automate the engineering-based repetitive and rule-based tasks in my company. UiPath has proved itself to be a very user-friendly and easy-to-adapt kind of software which does not require any core knowledge or coding background to start with.
We use UiPath mostly for automating data entry forms and automatically copy-pasting between different apps.
We currently use the tool to sell solutions to internal customers. Most of the work that we automate is the migration of data between systems, automation of emails, extraction of data from PDFs with OCR, among others. The gain has been perceptible from the first moment, as human errors have been noticeably reduced to almost zero. Another good point for us is that we can leave the robot working for as long as we want.
It was used for the automation of web-based applications in the banking sector. The challenge was to read information in image-based forms.