What is the best way to balance cost and value in RPA implementations?

Ideally we should always prioritize rule based, high value, high volume and low complexity processes but this depends on other factors as well. Mainly it depends on what licensing plan you have, which automation tool you are using and your automation team strength. All this accounts to RPA CoE to design their strategy for optimum ROI. I personally target processes which have high man hours consumption. Furthermore during requirement gathering phase I try to reengineer whole process to further improve bot license consumption but for this one should have thorough business knowledge to fully understand requirements. Simply automating as is process is never enough, time should be spent on designing better to be process.

Priorizar processos mais estáveis e com alto grau de repetitividade é a melhor estratégia para come?ar a jornada de RPA. Um ponto importante dentro desta estratégia é fugir do "mundo perfeito", que é a automatiza??o do processo completo. O mapeamento deve ser completo, porém a execu??o pode (e funciona muito bem) sendo ágil. Pequenas entregas realizadas constantemente aumentando o engajamento e otimizando as atividades. Desta forma, a captura de valor é realizada rapidamente, o ciclo de feedback é encurtado e a percep??o de valor para a organiza??o alavanca novas iniciativas.

Prioritize “low hanging fruit”. Small, simple, high volume, highly repetitive processes with no reasonable expectation that human intervention would be necessary. This is also a great time to identify opportunities for optimization and simplification. Avoid automation of a poor process. Garbage in… garbage out.

With low hanging fruits having dried up, it is necessary to look at processes not just with RPA lens but also thinking from the perspective of using products like OCR, BPM to provide a holistic solution that can increase value.

Somewhat underdiscussed tip: The devs tend to make up ~5x higher cost base than the licenses in RPA. So naturally your optimization formula here is heavily skewed for dev time, not runtime. Make sure devs don't overoptimize solutions, especially if that results in less readable/maintainable solution. Human time is key here, not license time.

Grande barreira para continuidade de uma jornada de automa??o está no Custo de propriedade, para que a estratégia possa seguir forte e eficiente a escolhas das ferramentas devem estar alinhadas a complexidade de gest?o, desenvolvimento e sustenta??o. Existem dezenas de ferramentas e tecnologia, com seus prós e contras, para que você tenha sucesso selecione algumas que atendam as seguintes necessidade: 1. Robustez e seguran?a: Para processos complexos e que envolvam dados sensíveis. 2. Facilidade de uso: Para processos simples que possam ser desenvolvidos por seus próprios usuários. 3. Alta tecnologia: Para processos com alta necessidade de inova??o, flexibilidade de redesenho e design.

Carefully select RPA tools that align with the complexity and requirements of your processes. Evaluate both the initial costs of implementation and ongoing maintenance expenses. Consider factors such as scalability, ease of integration, and vendor support. Choosing the right tools is essential for optimizing costs while ensuring the value of automation. Leverage insights from the LinkedIn community and industry experts to make informed decisions about the most suitable RPA tools for your organization.

In terms of licensing, every RPA tool is different. Hence RPA tools selection should be based upon the budget allocated and also strong comparison should be made between the manual process cost and once the process is automated.

By now many companies have already acquired RPA product and developed automations on them. If they plan to switch RPA product they will have to migrate existing automations. Selecting RPA product mainly depends on what licensing model you get, what ecosystem you are currently using internally and how strong community is. Having strong community is an important factor and should not be ignored. Normally I tend to write code and integrate with automation to optimize performance. To speed up excel manipulation I treat excel as a db and write SQL or write inline VB/Python code. Selecting RPA tool depends upon stability, license consumption and how fast you can rollout your automation in production.

N?o vejo como fundamental a escolha da ferramenta em si porque muitas vezes, fatores como budget s?o essenciais na tomada de decis?o. Ent?o, analisar a aderência ao que se pretende ter de entrega seria interessante. S?o muitas as ferramentas e os valores e formas de cobran?a s?o variados também. De certo que as ferramentas gratuitas n?o entregam o mesmo das pagas. Dentre as mais baratinhas o Power Automate da Microsoft considero uma boa escolha. Já uma intermediária seria a Eletronic e uma mais parruda seria a Yank.

Assemble a skilled and knowledgeable team for RPA implementation. Ensure that team members possess expertise in both the chosen RPA tools and the specific processes being automated. Investing in training and upskilling can be a cost-effective strategy to build an internal team. By having a well-equipped team, you not only enhance the efficiency of the implementation process but also contribute to the long-term value by fostering in-house expertise.

Additionally, invest in employee training to maximize the technology's potential and ensure sustainable benefits. Moreover, establish a structured training program that covers not only technical skills related to RPA but also emphasizes adaptability and problem-solving. Encourage a culture of continuous learning to keep employees abreast of evolving automation trends. Monitoring progress and seeking feedback will aid in refining the training process, ensuring that your workforce effectively leverages RPA capabilities.

Not necessary every RPA project requires individual people for every role. Sometimes one person can act for multiple roles and this will surely save a lot of cost. For example: If the process is not too complex then an individual can contribute as a Solution Architect, Business Analyst and a Developer as well.

A constru??o do time é uma etapa bem interessante. Entender quais s?o os papéis necessários, buscar as pessoas certas (n?o apenas com domínio da tecnologia, mas com o fit cultural para cada projeto/empresa), selecionar parceiros fortes. O time é essencial para o sucesso do projeto. Ele engajado, motivado e com as ferramentas corretas ir?o levar ao sucesso e garantir mais um passo da jornada de automa??o.

Having proper team plays a crucial role in successful RPA implementation. Personally I advice to have BA to act as a bridge between Business and Developer but to play more valuable role BA should have some development experience as well. This way BA can identify and resolve many issues that developer may face in future. Secondly having separate support/operations team is also important to monitor process in production closely. Since we are covering team aspect, I believe having fulltime DevOps Engineer in your team is highly advisable. Based on my experience having CICD for whole implementation process can streamline a lot of things and can maintain proper version controlling as well.

Mitigate potential risks associated with RPA implementation to maintain a balance between cost and value. Identify and assess risks related to data security, compliance, and system integration. Implement robust risk management strategies and contingency plans to address unforeseen challenges. Proactively managing risks ensures a smoother implementation process, minimizing the impact on costs and maximizing the value derived from RPA.

In RPA there are numerous risks involved because our BOT has to interact with applications of different nature. Hence thorough testing is very important. Also the security mechanism should be robust in order to handle any unforeseen situation.

Mitigar os riscos é fundamental, mas além disso, aprender rapidamente com os erros e corrigir. Nenhum projeto está isento de riscos ou falhas (seja RPA ou qualquer outro tipo). Desta forma, encurtar os ciclos de feedback permite que o time ajuste a rota e n?o tenha ruptura para a entrega de valor esperada.

Failure is part of whole RPA journey, its unavoidable but with the passage of time a lot of things will be streamlined. Once again I will emphasise on fact to have fulltime DevOps Engineer in your time who can streamline deployment process by implementing CICD. Secondly it is advisable to have a checklist of tests which should be completed by other team member. Code should be reviewed in detail and it should pass all test cases from checklist to eliminate common issues. One other strategy for damage control is to have proper version controlling incase latest package is not working we can immediately go back to the previous one. This again can be facilitated if CICD is implemented

from a risk management perspectice take the RPA case look at the processes and the risks inside them. Show them openly and let management decide which one can be accepted and which one rather not.

De acordo com o nível de maturidade e expectativa de sua empresa, procure estabelecer indicadores claros que possam sem estabelecer de maneira comparativa os resultado pré automa??o e pós automa??o. Alguns das dimens?es interessantes a serem medidas, s?o: * Performance x Tempo : Me?a o total de itens executados x volume de itens total em uma determinada unidade de tempo. * Eficiência x Tempo : Me?a quantidade de itens executados com sucesso x volume total de itens em uma determinada unidade de tempo. * Velocidade: Compare a velocidade de execu??o de um ser humano hábil x automa??o. Importante: Tenha claro qual é o principal indicador para seu processo, n?o é mandatório todos serem positivos.

Establish key performance indicators (KPIs) to measure the outcomes of your RPA implementation continually. Regularly assess the impact on efficiency, accuracy, and cost reduction. Use feedback from end-users and stakeholders to refine and optimize automated processes. By consistently measuring outcomes, you can identify areas for improvement, demonstrate the value of RPA to stakeholders, and make informed decisions about future automation initiatives.

Medir resultado é essencial para qualque trabalho. Antes de automatizar qualquer coisa, primeiro, deve-se ter bastante claro o ROI do negócio e entender se a automa??o de fato irá atingir o resultado. Uma vez estando claro que a automa??o vai trazer o resultado esperado e entendido que a melhor solu??o de fato é a automa??o, avalie o ciclo de vida da automa??o e quanta manuten??o poderá ocorrer no decorrer do período. é muito importante medir e colher as li??es aprendidas de cada automa??o, já que isso serve de insumo para a próxima. O cliente apenas fica satisfeito quando um bom trabalho de consultoria é prestado e o valor é percebido de forma clara e isso acontece quando há uma demonstra??o clara e numérica do ganho.

Um Kosten und Nutzen bei RPA-Implementierung auszugleichen, ist eine pr?zise Ergebnismessung entscheidend. Definieren Sie klare Leistungsindikatoren (KPIs) im Vorfeld, um den Fortschritt zu bewerten. Berücksichtigen Sie nicht nur finanzielle Aspekte, sondern auch Effizienzgewinne, Fehlerreduktion und Mitarbeiterzufriedenheit. Regelm??ige überprüfungen der Implementierungsergebnisse helfen, Anpassungen vorzunehmen und die Effektivit?t sicherzustellen. Kommunizieren Sie die erzielten Erfolge transparent, um das Vertrauen der Stakeholder zu st?rken. Durch eine kontinuierliche Messung und Anpassung der Ergebnisse k?nnen Sie sicherstellen, dass die RPA-Implementierung nicht nur kosteneffizient, sondern auch langfristig erfolgreich ist.

ROI is always a key indicator of success when it comes to RPA. Also time saving, data accuracy are also some of the key Indicators. These indicators will help to identify the improvements if needed in process automation.

To balance the cost and value in case of RPA implementation it's important to consider the following things: 1. Complexity of the process 2. Frequency of the process whether daily, monthly, weekly 3. Number of FTE savings 4. Number of hours saving. 5. Risk involved. 6. Annual capacity crested.

I would recommend: 1) Identify high-value, low-complexity processes for initial automation. 2) Calculate Total Cost of Ownership 3) Focus on the quality of data used in RPA systems to ensure accuracy and reliability. 4) Measure and monitor performance using key performance indicators (KPIs). 5) Invest in employee training and effective change management for smoother RPA integration. 6) Adopt an iterative approach to RPA implementation, starting small and scaling up.

Scalability and Future-Proofing: Design RPA solutions that are scalable and adaptable to future business needs. This foresight reduces the need for costly rework and ensures long-term value. Maximize Utilization of Bots: Ensure that the bots are utilized to their full capacity. Idle RPA resources can be a drain on ROI.

The best way to balance cost and value in implementing RPA solutions is to have all your ducks lined up in a row before trying to shoot for the record. What this means: - Know your processes. Not just based on dry documentation, but actual working knowledge. Get trained up the same as a new starter would. - Understand your costs. You cannot predict anything unless you have reliable data to work from. Starting from infrastructure, support and maintenance, going through staff salaries, performance and efficiency, up to "red tape" and all the bureaucracy involved in your lifecycle. Calculate not just based on averages, but factor in variables over time as well. - Use technology. Have an automated process for evaluation and calculation!

Balancing value against cost can be boiled down to process maturity. Process maturity can be ascertained very quickly, can the business area immediate provide you with metrics on the process that would satisfy a green belt in six sigma. If so, then the decision should be relatively easy and the path forward is clear. If the process isn’t maturity, then short periods of observation as part of the feasibility assessment will be invaluable. Monitor the volume, frequency, and variation: if high, high, and low then you’re golden. If you remain unsure, then build a testing rig in dev: MVP style, just capture the amount coming in and how often, categorise the cases where possible.