RPA in the Real World
- May 9, 2018
- 0 Comments
Andrew: We have several customers who are actively RPA right now. I’ve noticed a theme across a lot of them where, it’s not being used so much within the enterprise walls but where they have to reach outside to other systems.
Andrew: There’s a lot of different use cases where you have what we would call, multi-jurisdictional problem. And, RPA fits into that nicely. For example, there’s a lot of state websites that allow you to do look ups for certain things such as, information around a corporation of companies within the state. All of them have their own website. There’s not agreed upon API that they all conform too. But, they have the same general information. Today without RPA, what our customers wind up doing is having to have individuals get assigned tasks to go to these websites, perform the look up and then, provide the data the underlying digital process that they’re trying to achieve.
Andrew: With RPA, we can take that roadwork off of those people’s hands and put it on the bot and allow them to concentrate more on the areas that their unique human intelligence is required to meet within the digital process platform.
Krista: So, what are some other edges? So, beyond reading from a website. Maybe, writing or repetitive work?
Andrew: Yes. Any sort of repetitive work where you’re interacting with these systems on a regular basis and especially, if those systems don’t provide an API today. Those could be either, Legacy systems such as Green Screen systems, which we’ve found tend to be fairly slow moving. And, people are very resonant to add code in because, they have accumulated code over such a long period of time, that they’re not sure what the impacts are going to be.
Andrew: By using RPA, you can put an API layer on top of that existing enterprise system, without the need to actually affect the underlying code. Likewise, we can see that people wind up using it for coordination between multiple Cloud systems where again, some of the Cloud providers in order to achieve lock in, may not make as many APIs available as we would like, but have a user interface to achieve our goals. If the item that we’re doing is inserting data in a reliable format from a known source, we can create a bot to do that and realize the underlying need without having to again, have a person go in and be our “integration bus” if you will, for that.
Krista: Those are great examples and I think, that will help a lot of people get started with RPA. So, thanks for joining us today and we look forward to seeing you again soon.
Andrew: Your welcome.