In the oil and gas industry, we are mainly using UiPath Automation Cloud for all RPA processes. We use UiPath Automation Cloud for deploying the process and understanding the process. By understanding the process, we will decide whether we want to go with RPA or not. Once we have confirmed from UiPath Automation Cloud, then we will start developing it and deploying it to UiPath Automation Cloud. There is usefulness of attended and unattended robots. Previously until 2021, in the same Orchestrator, we could use attended and unattended. With the particular license, we could convert into attended or unattended. However, now UiPath Automation Cloud is providing a separate license for unattended and a separate license for attended. Currently I am working for one of the oil and gas industries. Previously I worked for one of the big oil and gas industries where I used automation as an RPA process. In the current oil and gas industry, I am using it for test cases. It has been useful for them because some of the test engineers work for the US time zone, and some of the test engineers work in the Indian time zone. Test cases are a continuation, so to complete one particular test case, we need to complete the previous trial test cases. For that reason, it is very useful for running at twenty-four seven. Previously we had more than sixty processes and more than sixty processes had more than twelve developers supporting them. At some point in time, they fully converted or they wanted to migrate it from UiPath to Power Automate.
My main use case for UiPath Automation Cloud involves all the RPA related automation including sales order creation, ServiceNow ticket and job ID creation, booking order, and enterprise level work. A specific example of how I use UiPath Automation Cloud for sales order creation or ServiceNow ticketing is that end users create a ticket in ServiceNow, and the bot goes through ServiceNow and picks up the tickets. It reads the request type and based upon the type, it either opens SAP or opens Oracle. If it is an SAP request, it opens the respective SAP system and then goes to the respective T-code to create the order and then fetches the final transaction ID to go back to ServiceNow to write down the transaction ID and change the status of the ServiceNow ticket. This is one example. I have several scenarios and around 175 plus bots which are developed in UiPath Automation Cloud. It is working well, and we have bots in several functions including supply chain, finance, with most of the bots being finance-related, and then HR. We have plenty of use cases.
For our IDP projects and RPA projects, the major use case for UiPath Automation Cloud is that we use a Validation Station and similar tools. I use both attended and unattended robots. Some of them are working in simple terms; some of them are using Robot Studio, and some of them are working independently.
UiPath Automation Cloud offers scalable automation services with a focus on ease of deployment, comprehensive management, and robust security. It's designed for enterprises seeking to optimize operations by automating processes and enhancing productivity across departments.UiPath Automation Cloud provides a cloud-based platform that allows businesses to manage their automated workflows seamlessly. With an intuitive interface and powerful features, users can enhance their process efficiency...
In the oil and gas industry, we are mainly using UiPath Automation Cloud for all RPA processes. We use UiPath Automation Cloud for deploying the process and understanding the process. By understanding the process, we will decide whether we want to go with RPA or not. Once we have confirmed from UiPath Automation Cloud, then we will start developing it and deploying it to UiPath Automation Cloud. There is usefulness of attended and unattended robots. Previously until 2021, in the same Orchestrator, we could use attended and unattended. With the particular license, we could convert into attended or unattended. However, now UiPath Automation Cloud is providing a separate license for unattended and a separate license for attended. Currently I am working for one of the oil and gas industries. Previously I worked for one of the big oil and gas industries where I used automation as an RPA process. In the current oil and gas industry, I am using it for test cases. It has been useful for them because some of the test engineers work for the US time zone, and some of the test engineers work in the Indian time zone. Test cases are a continuation, so to complete one particular test case, we need to complete the previous trial test cases. For that reason, it is very useful for running at twenty-four seven. Previously we had more than sixty processes and more than sixty processes had more than twelve developers supporting them. At some point in time, they fully converted or they wanted to migrate it from UiPath to Power Automate.
My main use case for UiPath Automation Cloud involves all the RPA related automation including sales order creation, ServiceNow ticket and job ID creation, booking order, and enterprise level work. A specific example of how I use UiPath Automation Cloud for sales order creation or ServiceNow ticketing is that end users create a ticket in ServiceNow, and the bot goes through ServiceNow and picks up the tickets. It reads the request type and based upon the type, it either opens SAP or opens Oracle. If it is an SAP request, it opens the respective SAP system and then goes to the respective T-code to create the order and then fetches the final transaction ID to go back to ServiceNow to write down the transaction ID and change the status of the ServiceNow ticket. This is one example. I have several scenarios and around 175 plus bots which are developed in UiPath Automation Cloud. It is working well, and we have bots in several functions including supply chain, finance, with most of the bots being finance-related, and then HR. We have plenty of use cases.
For our IDP projects and RPA projects, the major use case for UiPath Automation Cloud is that we use a Validation Station and similar tools. I use both attended and unattended robots. Some of them are working in simple terms; some of them are using Robot Studio, and some of them are working independently.