Talk to us
Talk to us

Tag: RPA

  • Cognitive process automation for Employee Centric Enterprises. Why Now?

    E42 is a Cognitive Process Automation (CPA) platform. The world’s first and most powerful. It’s also very versatile. There are over 180 processes currently being automated using the platform. Processes that needed cognition hitherto only available among humans. When we combined E42 with AI we were able to build that cognition into enterprise systems and have created use cases ranging from AI assistants for employees to report generation for marketing insights.

    Classification Of Processes by Stakeholders

    Let’s just take a group of processes from the entire gamut of enterprise processes. These enterprise processes can be classified by verticals or functions. Normally that’s done because IT systems are made and sold that way for the last 50 years! Let’s take HR processes for a services enterprise. Here we will have an HCM or HRMS that keeps track of the employee, every time he/she shows up or doesn’t, needs leave, or who he/she reports to, or makes a claim for an expense incurred for the enterprise, etc. Now if that employee is in Sales he/she will also be connected to various sales-related processes like the number of leads generated, the volume of the sales funnel, targets, etc.

    There will also be shared services, meeting rooms to be booked, learning and development, upskilling, etc. The CPA can automate all of these processes by removing the dependency on humans to perceive the request (made in natural language), initiate the process, retrieve information from unstructured data (Policy, SOPs, etc), pull-push data into any of the systems (HCM, CRM, LMS, ERPs, etc) and post-execution even give feedback to the relevant stakeholder. Since for the first time, we have a platform that cuts through verticals and functions we can choose a simpler and far more effective classification of processes. We take the stakeholders. A stakeholder/user-first approach has many advantages.

    1. It helps club of processes based on the user that most benefits from it
    2. It gives that user that omnichannel availability he/  she needs to make his / her life simpler
    3. Any department can create use cases that automate their processes relieving humans in the loop that may have been nonessential in the first place
    4. The system can generate insights based on individual and group interactions.
    5. Even users can be connected with each other via a common platform to achieve more.
    6. The classification can be universal and will apply to every industry vertical

    So broadly we classify all processes under customer-centric processes and employee-centric processes. Also there are other stakeholders like management, vendors, franchisees, etc and we will cover them in future blogs. For the purpose of this article, I am taking just the Employee Centric processes.

    Employee Centric Processes, For those enterprises that care!

    Today several enterprises understand how critical it is to let employees do their jobs! To do that we have to make every other part of their lives as friction-free as possible. So at Mahindra and Mahindra (winner of SAP Ace award for employee engagement), every employee has an AI assistant that helps them with almost every need of theirs from syncing calendars, to leave applications, from finance numbers to payslip downloads. The key is one AI assistant that can trigger or help humans execute over 76 enterprise processes! You can find the complete list of employee-centric processes that have been automated on the E42 platform. The same assistant helps conduct dipstick surveys and instant notifications. It’s the holy grail of employee engagement!

    Before COVID-19 we thought that one of the most important reasons employees work in the office is that colleagues are just a few cubicles away. Being close to workers dramatically increases productivity. Working from home, employees cannot walk over to their colleagues’ desks. Hence working from anywhere but an office was considered impossible.

    Today, however, employees working from home can communicate as seamlessly with each other as they could while in the office thanks to collaborative platforms like Teams, Meet, Slack, etc. The E42 AI assistant is available across all these channels from where employees can trigger these processes.

    Broadly within employee-centric processes, we have the following types of processes

    1. Queries – these could be generic like “what’s the maternity policy in my company?” or specific to my band like “If I were to travel to Mumbai, what’s my daily travel allowance?”. These queries get resolved by the CPA doing a natural language search within the unstructured document repository (Corporate policy, etc). There can also be specific queries like “what’s the status of my expense claim that I raised for my Mumbai trip in May?” or “how many vehicles did we sell in June?”. Here the CPA triggers a process that pulls data from a structured data source like Salesforce or Oracle.
    2. Transactions – These processes are either initiated via chat or voice in natural language or sometimes the human in the loop needs to react to push it downstream for further processing. Example “I want to apply for casual leave for the whole of next week” Here the system will have to a) understand that employee id XX is asking for casual leave from Date A to Date B and then b) confirm what it understood with the employee c) check it there is enough casual leave balance and ensure that its not violating any policy for XX c) inform XX if not or else inform approver if there is leave balanced) provide approver additional information along with the approval request e) understand and confirm the approver’s action, etc. All the while it’s pushing and retrieving data from databases and various systems.
    3. Surveys and Competitions – Here the system triggers the process based on events or actions. The responses are collected from the employees and pushed into a system or an excel and computed.
    4. Other processes – these include processes like authentication, notifications, 3rd party systems (employee mental health), etc.

    Omnichannel and versatile

    The versatility of the platform also extends to the channels of deployment and systems of unstructured and structured data sets. We have great IP when it comes to unstructured data, where you can upload and train your entire knowledge base as it is. No more manual intent creation and classification. This means that apart from creating better employee experiences at lower costs you can actually integrate data silos and start generating great insights. So far the E42 CPA platform has successfully integrated with various intranets, Whatsapp, HTML pages, Workday, Slack, Skype, Skype for business, Teams, and various other chat and collaborative platforms. The use cases and channels are not limited to the above.

    When it comes to employees, they have a common pool of data (usually HR policies, Standard operating procedures, etc..) and some of the policies could be role-specific. Based on the employee’s role in the organization they have various systems and data governed by different policies and privileges. With the E42 CPA platform, you have a mechanism to add the data and workflows applicable to specific roles and create an AI assistant that is personal to each of the employees in the organization covering all the aspects of their work. For example, an IT security manager in a particular location will have access to data and workflows of general employees, data and works flow applicable to managers as well as his/her IT security role-specific functions through a single window. You can adapt the workflows, permissions, and data privileges in the organization directly on the CPA platform to create an enterprise AI assistant that helps every employee with Cognitive Automation.

    All of these aspects and many more make the E42 CPA Platform a really powerful tool when it comes to building cognitive abilities within employee-centric systems. Of course, this is just the tip of the iceberg. Imagine the possibilities when we open it up for integration with other systems and solutions out there. It means that for any new vendor you onboard if they have a solution for your employees and a system with an API that service will also be available through the same window. And any other intent classification system out there will collapse as for those systems this will mean not only configuring the new use case but also going back and reworking the older utterances for previously classified intents as the confusion matrix will go through the roof.

    Deep tech Meets powerful UI

    This is only possible when you take superior E42 Algorithms, train with lots of data on Transformational AI neural networks and make it consumable on a great intuitive UI. So now OEMs, SI partners, Developers and even SIs can access the tech and create use cases that automate employee-centric processes like KYC updation, Claims, Attendance regularisations, Approvals, Insights generation, and many more.

    It’s true, now more than ever before that the happier your employees are the better the yield. So as organizations are battling productivity issues while getting their employees back to work to produce and sell their products or services they’ve got to stay motivated and productive. For employees, it means removing all hurdles to their performance. When the systems are able to take care of the mundane, repetitive tasks they do that require them to do it just because the enterprise systems couldn’t, it frees them up to do the real thinking. It helps sales teams to sell better, HR teams to empathize with employee problems better, Operations to optimize resources better and the entire enterprise to deliver more. Cognitive process automation platforms help the employees “see” better, “read” better and act with decisiveness on their core tasks. The classic case of an employee, AI collaborating to achieve much more.

    So if you are looking to deploy an AI workforce that caters to your employees do get in touch and we’ll show you how you can create impact within a week.

  • Operational Resilience: Financial Process Intelligence

    This article was originally printed on the FortressIQ website and includes updates to reflect the company’s change in status. FortressIQ is now part of Automation Anywhere, and its offering is now our process intelligence product FortressIQ

    The Covid-19 pandemic has exacerbated operational risks while increasing economic and business uncertainty. Pandemic-related disruptions have affected internal information systems, personnel, and facilities, as well as relationships with external service providers and customers. In addition, cyber threats (ransomware attacks, phishing, etc.) have spiked, and the potential for operational risk events caused by people, failed processes, and disrupted systems has increased as a result of greater reliance on virtual working arrangements.

    financial survival

    To help the financial industry improve its ability to survive future disruptions, the Basel Committee on Banking Supervision (BCBS) recently issued Principles for operational resilience. It aims to make financial services institutions (FSI) better able to withstand, adapt to, and recover from severe adverse events. Similar guidance has been rolled out by the Prudential Regulatory Authority, Financial Conduct Authority, and other regulators. The goal is to provide additional safeguards for the overall financial system.

    Operational resilience requires detailed process understanding

    The BCBS defines operational resilience as the ability of an FSI to deliver critical operations through disruption. The principles cover topics ranging from governance and operational risk management to business continuity planning and cybersecurity, including activities performed for third parties. The principles have also been expanded to include processes that, if disrupted, would be material to the company’s continued operation or its role in the financial system. In other words, it’s critical to understand every process that makes an FSI tick.

    Mapping the connections

    Of particular note is the document’s fourth principle, which provides guidance on mapping the interdependencies of internal and external processes. It states that FSIs should not just identify critical operations, but “map the internal and external interconnections and interdependencies” to truly understand how they deliver critical operations.

    BCBS further implores FSIs to go deeper than just the tasks and steps to identify and document the people, processes, technologies, information, facilities, and more, including those of third parties. It further calls out the need to define “interconnections and interdependencies” among all these components as they relate to an FSI’s ability to deliver critical operations.

    Capturing this level of detail, at scale, is a daunting task even for smaller FSIs. The typical manual process mapping and application log file-based process mining efforts are too slow, too expensive, and too limited in their scope.

    Process Intelligence Accelerates Operational Resiliency Initiatives 

    The Automation Anywhere FortressIQ Process Intelligence solution uses computer vision, machine learning, and artificial intelligence to effectively capture and discover the details of every process, who performs it, using which applications, and the output generated from it.

    Yes, FortressIQ maps and documents the people, processes, technologies, and information behind every process. Best of all, it captures this process intelligence in just weeks, comprehensively and accurately, without expensive and long engagements. And it highlights process variances across workers due to differences in experience, training, or other factors.

    FortressIQ also documents the people and processes using legacy, home-grown, and user-generated tools, and even productivity tools that lack logs, such as email and spreadsheet apps. FSIs spend millions of dollars buying, building, and maintaining these customized and third-party systems, but allow risk to be introduced as end-users conduct operation-critical work using end-user computing tools (EUC), which are outside of core systems. These EUCs can help make day-to-day work faster and more efficient, but the operational and continuity risks associated with EUCs cannot be understated.

    FortressIQ Process Intelligence requires zero integration, works without disrupting employees, and captures granular process details. Process data is then decoded to provide actionable insights so FSIs can make faster, more informed decisions on the process optimizations, digital transformations, and cloud adoption that support resilience initiatives.

    Decode work for FSI resilience

    FortressIQ follows the human worker with automated process discovery, modeling, and documentation. It works everywhere business happens, capturing process data at the most granular level, performed on any application, with no bias or blind spots, and across global operations. It then presents process visualizations and dashboards across people, process, technology, and information, allowing a view of the data from a broad perspective or focus on a single process thread and empowering leaders to make data-driven decisions with increased confidence.

    The Covid-19 pandemic highlighted the need for operational resilience, especially for FSIs. Given the critical role of FSIs in the global financial system, increasing their resilience to these types of black swan events also increases their ability to absorb the more likely and more common shocks of cyber incidents, technology failures, and natural disasters. Pragmatic operational resiliency provides safeguards for the financial system as a whole. But it all starts by decoding how FSIs work today.

  • How to More Accurately Calculate RPA ROI

    RPA done correctly delivers ROI. High ROI. The average ROI achieved by businesses, according to Automation Anywhere’s most recent Now & Next report, is 250%, typically paid back within six to nine months after deployment. Top performers, those companies that followed industry best practices, received an average of 380% ROI on their RPA investments. These numbers speak to the business value of RPA technology.

    But how do you measure ROI? There are many ROI calculators that attempt to walk you through a series of questions that supposedly will reveal break-even points and the total cost of ownership (TCO). But the fact remains that ROI for RPA is a nebulous thing, difficult to capture precisely. Attempting to apply a simple formula usually won’t work.

    How to More Accurately Calculate RPA ROI

    Difficult to apply

    There is a simple ROI formula. It’s just difficult to apply it to RPA.

    You calculate ROI by subtracting the initial value of your investment from the final value of the investment. This is called the net return. You then divide the net return by the cost of the investment and multiply by 100. Voila!

    Let’s make it even simpler. Let’s say you take the total value you received from your investment in RPA and divide it by the total cost of implementing RPA.

    You can probably see what the problem is. Measuring the costs can be complicated if you want to do it precisely, but it can be done. But the “total value” is not easy to calculate with RPA because it consists of both hard financial returns (good) and intangible, indirect returns (difficult to capture precisely).

    Let’s consider costs and benefits metrics in turn.

    Measuring the cost

    This can be done because it consists of four basic, quantifiable things:

    • The cost of the RPA solution (add up licensing, subscription, maintenance, etc.)
    • The cost of extra infrastructure (the cost of the hardware, software, and networking infrastructure required to support the RPA solution)
    • The cost of development (the cost of development tools plus the time of developers, business analysts, and users to analyze, redesign, and automate the process or processes in question)
    • The cost of ongoing maintenance (add up the time of personnel needed to monitor and maintain the RPA software multiplied by their fully loaded cost to your business)

    This takes attention to detail, but it has to be done.

    Measuring the return

    Measuring the return is more difficult because of the intangible benefits RPA offers.

    Take the example of a hard financial return: By automating a business process, you saved the equivalent of one full-time employee’s (FTE’s) time for a year. You calculate the dollar value of that return by finding out the “fully loaded” annual cost of an FTE (fully loaded means including benefits, taxes, retirement plans, and all other costs). There you have it: $50,000. Or $100,000. Or whatever. That’s a nice hard number.

    But here’s an example of an intangible return: Your employees are happier because they’ve gotten rid of drudge work and are free to do higher-value work. How do you measure happiness? And how do you assess the value of employee activities that are perhaps more strategic to the business? How do you measure the benefit of a better decision being made?

    Measuring the most intangible benefits desired from RPA

    Difficult to apply

    There is a simple ROI formula. It’s just difficult to apply it to RPA.

    You calculate ROI by subtracting the initial value of your investment from the final value of the investment. This is called the net return. You then divide the net return by the cost of the investment and multiply by 100. Voila!

    Let’s make it even simpler. Let’s say you take the total value you received from your investment in RPA and divide it by the total cost of implementing RPA.

    You can probably see what the problem is. Measuring the costs can be complicated if you want to do it precisely, but it can be done. But the “total value” is not easy to calculate with RPA because it consists of both hard financial returns (good) and intangible, indirect returns (difficult to capture precisely).

    Let’s consider costs and benefits metrics in turn.

    Measuring the cost

    This can be done because it consists of four basic, quantifiable things:

    • The cost of the RPA solution (add up licensing, subscription, maintenance, etc.)
    • The cost of extra infrastructure (the cost of the hardware, software, and networking infrastructure required to support the RPA solution)
    • The cost of development (the cost of development tools plus the time of developers, business analysts, and users to analyze, redesign, and automate the process or processes in question)
    • The cost of ongoing maintenance (add up the time of personnel needed to monitor and maintain the RPA software multiplied by their fully loaded cost to your business)

    This takes attention to detail, but it has to be done.

    Measuring the return

    Measuring the return is more difficult because of the intangible benefits RPA offers.

    Take the example of a hard financial return: By automating a business process, you saved the equivalent of one full-time employee’s (FTE’s) time for a year. You calculate the dollar value of that return by finding out the “fully loaded” annual cost of an FTE (fully loaded means including benefits, taxes, retirement plans, and all other costs). There you have it: $50,000. Or $100,000. Or whatever. That’s a nice hard number.

    But here’s an example of an intangible return: Your employees are happier because they’ve gotten rid of drudge work and are free to do higher-value work. How do you measure happiness? And how do you assess the value of employee activities that are perhaps more strategic to the business? How do you measure the benefit of a better decision being made?

    Measuring the most intangible benefits desired from RPA

    Although reducing costs can be a driver for deploying RPA, today, most businesses are after the more difficult-to-measure benefits. In Automation Anywhere’s Now & Next report, productivity improvement was the No. 1 reported benefit, followed by moving employees to higher-value work. Cost reduction came in third, followed by quality improvements.

    How to More Accurately Calculate RPA ROI

    Here are the definitions of the most popular RPA benefits:

    • Productivity: Can workers achieve more in the same amount of time?
    • Quality: Are there fewer errors?
    • Efficiency: Can tasks be completed faster (or perhaps eliminated)?
    • Employee satisfaction: Are employees happier?
    • Customer experience: Are customers getting a better experience?
    • Business agility: Can the company adjust to changes in the market more quickly and effectively?
    • Business continuity: Can the business keep operating no matter what happens?

    So perhaps you can’t get a precise reading on the ROI of having more satisfied employees. But you can identify key performance indicators (KPIs) and use them as “proxies” or stand-ins.

    Finding the suitable proxies for KPIs

    For example, take business agility. How do you measure the dollar benefit of that? You might decide that a good proxy for agility is the number of new apps your development team is able to create in a given period, say a month. Or perhaps it’s the number of new customers you acquire during that same period and the total revenue they bring in. Or perhaps the financial value of new partnerships you’ve signed.

    For customer experience, you could use churn as a proxy for whether you’re getting better, lower churn, greater quantifiable benefit. For quality, you could add up the number of errors and what it cost to fix them in terms of people time and infrastructure cost. You could even find a proxy for the fact that your reputation improves in the marketplace as the result of producing higher-quality goods or services.

    Determine your KPIs before you begin

    It’s essential that you determine upfront what you want to measure. Get a baseline. To measure efficiency, for example, assess how many FTEs it takes to finish a targeted task or process as a “before” snapshot. Then, measure again after the RPA bots are deployed. Or get a before picture of how many invoices can be processed by your account receivables team in a week. Then, get the after picture to get your quantifiable productivity number.

    You can use whatever metrics make sense, given your business. But make sure to do it before you begin your RPA implementation. Given the initial baseline of productivity and efficiency, employee happiness is the first important step.

    Calculating your ROI has many benefits

    You’ll almost certainly find that implementing RPA delivers huge benefits to your employees, your customers, and your business. You probably assumed that. But it’s nice to have confirmation in solid numbers.

    To evangelize RPA, you need sound statistics and proof. Also, you need to know what’s working and what’s not in your RPA initiative. No matter if you’re pleasantly surprised or disappointed in the ROI measures you calculate, you’ll have valuable information that you can use going forward to improve the program. And that’s good for all concerned.