Digital Labor

From RPA to Cognitive Computing: Finding the right robot for the job

Artificial Intelligence. Digital Labor. And Robotic process automation. Finding the right answer for your business. (1).png

Digital Labor.  Artificial Intelligence.  Cognitive Computing.  Robotic Process automation (RPA). The possibilities of new A.I. business model are increasing by the month, as is the hype.  Finding the right platform, adoption process, and long term value can be a challenging journey.

Insights on what works and why are becoming more clear, and sharable.  Earlier this month, I participated in a panel on robotic process automation and cognitive computing sharing such experiences, as part of the DePaul University Digital Innovation conference. I was joined by several business leaders with deep practical experience, including Dwayne Prosko from Deloitte, John Stiber from Mondelez International, and Steven Pyke from W.W. Grainger.  The panel discussion was wide-ranging, and provided the assembled audience much to consider with the challenges and benefits of digital automation.  

6 key insights from the panel discussion included:  

  1. Automation, of any sort - is a process transformation before it is anything else. Realize you need to focus on the process(es) you wish to change, understand the why (business and mechanical), consider the human factors (job / performance changes and differences in work ‘speed’), and evaluate which platform(s) help achieve the business / process goals. Do not start with an automation 'hammer' and look for 'business problem nails' to hit.
  2. There are many layers (and complexities) to digital automation.  While the business process itself may jump off the page needing to be improved - deeper thought on the underlying systems, processes, and connective tissue of a business function need thought.  Something as simple as a Windows software patch, normally done without thought to the impact in a company - can completely disrupt the performance of an automated platform that is handling thousands of returns an hour. Third parties are also bringing their own automation tools to the table now - consider how your automation solution will interface with third parties for joint automation (e.g. procure to pay, or payroll processing / outsourcing). You might be surprised which platforms do and do not work well together.
  3. Digital automation does not mean digitally unattended.  The ability to automate a business process or event does not preclude the need for human supervision.  Sampling for accuracy in the automation, review of exceptions, and performance tuning are all part of the journey of digital automation. Ensure you have a clear vision who will be 'managing the digital labor / platform' (both from IT and from the business) as part of your change journey. And be ready for surprising adjustments / changes to the situation as you accelerate the pace of performance.
  4. Crawl, Walk, Run, then Fly.  Many times, businesses respond to the hype that can proceed a digital automation investment. The better advice - be clear on the why, take it at pace and go patiently forward. Focus on a single function / department business process change you want to transform as a starting point to prove out the benefits, and increase organizational buy in. Learn how the business responses to faster, increased accuracy, or differences in efficiency. Ensure your culture can sustain the change and grow on the knowledge gained from the automation experience (vs. rebel and resist - see the next point).  
  5. Human / cultural alignment is key to success. Putting a human face on the automation process increases the acceptance and utilization / leverage of digital automation in a business.  Something as simple as ‘naming’ the automated platform, including in work schedules, and ensure team members who are working with the digital colleague’ understand the ‘why’ and the ‘WIFM’ - improve the chances of cultural adoption long term.   If you do not address - myths and worries will manifest around the 'real reasons' for the automation change- something which can become difficult to overcome in a culture that relies on the automation process.
  6. The idiom - “Horses for courses” certainly applies to digital automation.  A key insights agreed: No A.I. platform can do it all in the area of digital automation. Companies are now finding that ‘moonshot’ A.I. programs that focus on becoming a digital game-changer can quickly miss the value target (and revenue / ROI expectation) if implemented in an eco-system or scenario that fails to integrate the digital automation itself.    

And last - a better automation model:

Consider having a 'automation eco-system' vs. a singular platform. Instead of relying on a singular answer - consider how you can optimize the benefits of multiple platforms to your digital advantage (and do this over time, learning and absorbing in your culture).

An automation eco-system model: an RPA solution gathering normalized data and performing entry / validations at record speed, a digital autonomics platformevaluating and managing exceptions and acts as an ‘engagement agent’ to support high volume customer interactions, while a cognitive computing solution provides analytics, guidance, and exception ideation that helps surface new value in the business.

Leveraging these insights above, achieving a digital automation platform (or eco-system) for your company can be a smoother transformation in the digital world. Focusing on process, the change journey (and the human factors), and finding the right digital 'horses for courses' will improve your chances for digital success!

Digital Labor and RPA: Part 3 in our services on RPA benefits and better practices

 Blog post by Don Sweeney (don.sweeney@practicallydigital.net)

Blog post by Don Sweeney (don.sweeney@practicallydigital.net)

Key steps to a Successful RPA Implementation

In June 2017 , the Institute for Robotic Process Automation and Artificial Intelligence (IRPA-AI) conducted a study of business technology leaders in more than 22 industries and 40 countries, which showed that digital automation has become part of almost every process and industry in the world.

But where—and how—does RPA fit into this? While RPA can drive a lot of process efficiencies and cost savings, it also can be a huge financial undertaking that requires a lot of change management.

So, how can your organization be sure it’s implementing RPA where it will be most beneficial to the bottom line instead of just using technology for technology’s sake?

In this third post of the three-part blog series on RPA, we are going to talk about how businesses can ensure a successful RPA implementation and what to consider prior to rollout.

RPA map.png

Making RPA work right: Identifying the right processes for RPA

The IRPA-AI survey noted that the processes most ripe for RPA are typically in shared services organizations – areas where there’s a lot of repetition and well-defined processes but also a lot of human intervention.

Surveyed companies specifically called out financial processes as the most common processes they planned to automate in the future. RPA can help improve financial processes by automating expense receipts, collections, approval workflows and some standard reporting.

The second most common area prime for RPA mentioned in the survey is Human Resources (HR). RPA can enable HR staff to rapidly track timesheets, store documents, calculate benefits, and issue on-boarding information to employees. 

Finally, the survey also mentioned procurement as another target area for RPA influence. The automated approval of requisitions and invoice processing can significantly help reduce human intervention in procurement processes. Not only can organizations reduce costs and gain efficiencies by using RPA for procurement, but they also can improve the vendor management process with more communication and better expected planning.

RPA priorities: Narrowing the field

There are other areas in which RPA can fit as well, including high-volume and high-frequency activities, repetitive, transactional activities, data-intensive activities, rule-based activities (interrogation of data, tax and compliance), tasks that pull data from disparate systems, and activities with standardization opportunities.

While there’s a host of processes that could benefit from RPA, organizations should evaluate them each separately to determine how they can ensure a successful implementation for each one.   Before diving in and making any RPA project a reality, consider these suggestions:

  • Define “transformation” before thinking about the tools. Technology does not solve the problem. It’s the vehicle to get you to the solution. Would you select building materials before designing the house?
  • Define automation objectives – e.g. headcount cost reduction, improving productivity, accelerating financial reporting cycles, redeploying resources to higher-value activities, enabling the organization to bring roles back onshore while maintaining an efficient cost structure, or improving compliance and controls.
  • Establish the right governance. To accelerate transformation, an organization will need to expand automation in a managed and thoughtful manner and not just as a series of separate projects. With this in mind, it is useful to plan and work in concert with business-led, end-to-end process improvement initiatives.
  • Plan for transformation. Change Management is key for any RPA implementation. Considerations should include changes to job design, roles, capabilities and skills required.
  • Conduct a pilot to demonstrate and prove out your RPA thesis of value.   This can be helpful for understanding the effort required to program and run the tool and the impact on resources.

Alignment and sponsorship: gaining executive—and employee--buy-in for the RPA journey

 Once your organization has begun a RPA implementation, it’s essential to show ROI beyond cost savings to ensure you gain buy-in from both executives and employees for future projects.

You can do so by identifying and quantifying opportunities for how RPA can be used in revenue-generating activities in addition to cost-saving or compliance activities. Don't just focus on RPA’s ability to reduce labor costs as its only benefit. Carefully set expectations of what the tools can do and how your organization can use them to support automation in an overall digital transformation strategy.

You also can identify other processes that touch multiple systems across the enterprise that could benefit from a nonintrusive approach to automation. Evaluate RPA opportunities where you have people acting as "swivel chair integration" — rekeying data between systems — and where they’re performing work that involves structured, digitalized data processed by predefined rules. This analysis forms the basis for your enterprise automation roadmap.

Lastly, identify alternative existing tools or services which have most of your required functionality at a suitable price point and evaluate these solutions in parallel with RPA, or as a hybrid solution. Also keep an eye on future artificial-intelligence-based options to ensure your organization chooses the right technology for each future automation project! 

 

As always, please reach out if you have questions, comments or concerns about RPA. We appreciate your feedback!   

Digital Labor and RPA: Part 1 in our series on the benefits of robotic process automation

 Blog post by Don Sweeney (don.sweeney@practicallydigital.net) 

Blog post by Don Sweeney (don.sweeney@practicallydigital.net) 

Digital Labor.  Artificial intelligence.  Robotic process automation.  Lately there is a lot to talk about the potentials for digital labor, and the benefits of automation in all companies.   While moon shots like cognitive computing / platforms require heavier investments of time and capital, there are easier and faster ways to generate digital labor benefits.   Specifically, a strong first step is through the use of robotic process automation.   

To help clarify the how and where, we wanted to create a multi-part blog to bring more awareness to the topic and cut through a lot of the noise that is out there.  This first post is defining what is RPA since there are a lot of items that sometimes fall into the overall bucket of RPA.  Our next installment will be why RPA is important and why it matters to you.  Finally, we will  provide steps to focus on for a successful implementation.  

So, what is RPA?

The Institute for RPA and AI  defines Robotic process automation (RPA) as “the application of technology that allows employees in a company to configure computer software or a “robot” to capture and interpret existing applications for processing a transaction, manipulating data, triggering responses and communicating with other digital systems.”  So what does that mean?  Simply put, RPA is the automation of a process (or processes) that will remove or reduce the human intervention in that process. 

This can be as simple as removing the redundancy of re-entering data in multiple systems or removing the frequently updated items based on simple logic.  Overall, the benefit of RPA is to reduce the manual intervention in repetitive, routine tasks within a process flow and automate it so it is accurate and predictable going forward but also to free up the human intervention for more significant tasks like analyzing and interpreting the data.

RPA seems to be the next iteration of how organizations have focused on technology improvement.  In the late 80s and though out the 90s and 2000s, organizations implemented enterprise software.

The original goals for implementing enterprise software were to A) improve processes with the “built in” best practices and B) have consistent, accurate data that was integrated with other parts of the organization.  For instance, vendor setup was shared with the purchasing application and accounts payable application – thus limiting the redundant data management in both applications. This was the argument for Enterprise ERP or HCM solutions. 

Cloud computing makes a difference with RPA.  For the last couple years, organizations have been moving their enterprise software to the cloud.  This provides the value of having someone else support the software as organizations realized how cumbersome and costly supporting large enterprise applications can become.  RPA becomes the next iteration of the organization’s focus where an entire process flow becomes seamlessly integrated and can require little or no manual intervention. 

My good friend Paula shares an example on this transformation in the telecommunications industry.   Many years ago, if you wanted to call someone you would call the operator and explain to that person who you wanted to call. They would manually connect your line to the destination’s line (sometimes requiring many operators to get involved if the call was of a significant distance).  You could not call someone without the manual intervention of the operator.  Eventually, the telephone systems were all automated and now you simply dial the number you want and it is connected with no manual intervention.  This is significantly more efficient and cost effective as the use of the telephone exponentially grew. This is the same as RPA, but on organizational processes, in real time.

RPA can include “bots”, which are small pieces of a process that are now automated.  An example would be where an organization that automated the process of answering questions for their staff on how much vacation time they had left or questions about their insurance information.  This “bot” (short for robot) would know the identity of the person asking the question based on their active directory authentication when they logged into the network. 

The employee could ask this Human Resources Bot what amount of vacation they had left and it would go and query the HR database for the balance and display their current balance as well as when the last time they took vacation.  It could also answer simple questions like the contact information for their benefits insurance provider or what benefit plans they were signed up for.  All of this minimized the impact of the internal HR team to answer routine questions and allow the staff to work on more important tasks – yet still answering the questions that the employees needed answered. 

RPA is not new, the capabilities to drive enterprise adoption are.  RPA has actually been around for about 10 years already, but has significantly picked up steam in the last 12-18 months.  It is commonly perceived to be the first stage on the evolution of automation and artificial intelligence.  Those stages are:

·       Robotic Process Automation

·       Autonomics (automation augmented by humans)

·       Cognitive Computing (end to end automation with human oversight)

·       Artificial Intelligence (fully automated with computers “learning” by analyzing trends in repeated processes over large numbers of transactions)

We will address the items on the “A.I. Spectrum” in future blogs where intelligent automation services blurs the lines between RPA and A.I.  In the next blog we will address in more detail RPA and why this is important to you and your organization. 

About the author:

Don Sweeney has over two decades experience as a technology consultant and digital visionary, working with companies to automate business processes with digital solutions, including robotic process automation platforms.   Don has worked at global organizations like Andersen Consulting, Oracle, and most recently at Emtec to enable companies in their digital journey.  Don can be reached at don.sweeney@practicallydigital.net 

Sharing the Digital Transformation Bonfire: Our Drinks N Digital events

 Rhinodox leadership including Justin Ullman, Kevin Carlson, and Julia Huang, speaking on July 13th 2017 at TechNexus

Rhinodox leadership including Justin Ullman, Kevin Carlson, and Julia Huang, speaking on July 13th 2017 at TechNexus

 Last evening, we had a great evening with over 40 people attending our monthly Drinks N Digital event, this time with a new innovative technology company Rhinodox sharing their vision and Worklight platform.  

During the event I had a chance to connect with many of the attendees, and heard a frequent question: “Why do we (Practically Digital) host these events,  - they are different than most?!”  

The Answer: every fire needs help to grow, and when we find really cool technology solutions we want to see flourish in the world, we throw a party and invite our friends to help build the blaze! 

Really cool is subjective, we know.  Really cool can be transformative in an industry, bringing a new solution to the market that solves hundred (if not thousands) companies needs.  Rhinodox is one of those we feel.  They have innovated and launched a contextual search and workflow automation platform that helps companies reduce repetitive work.  Impressive capabilities and results for any company - especially those handling large amounts of standard forms, claims, records, or files.   

Other times our events highlight an emerging services companies that is taking a fresh look, often disruptively – to existing industries.   All of these events generate dialog, moments of ‘wow I wonder if…’ and follow up meetings and conversations around the food and beverages provided.   

Our events serve another purpose - they help bridge the enterprise / corporate IT and operations worlds, with the startup / tech community here in Chicago.   There are thousands of emerging tech companies each year, and finding new solutions that help you digitally transform is much easier when there is a location, a time, and free food and beverages to help you get started.   We dig it when great teams come together, and we hope our attendees do as well!    

If you are interested in learning about future events and joining us, sign up to our list below.  If you are interested in presenting (even better!), get in touch at contactus@practicallydigital.net and let’s talk about your awesome tech solution or service!

+ See you at our next Drinks N Digital event!  -Rob