To RPA or not to RPA; working towards a composable architecture with hyperautomation

Rens Kaandorp (chapter Lead Solution Design – RPA & BPM) will explain the ABN AMRO “To RPA or not to RPA” journey. Many developers are focused on their own technology, which leads to silos: If you have a hammer, everything looks like a nail. In this journey, we analyzed our robot park and concluded that more than a third of our robots can be replaced by other technologies that align better with the bank’s strategy. This not only entails transitioning technology from A to B but also represents a change for our teams. We need to invest more in multi-skilled hyperautomation teams where developers have more than just one tool at their disposal.

Bram Rekers (IT Engineer & Projectleader Hyperflow Generic Components) then takes over to discuss the ABN AMRO hyperautomation strategy. In this strategy, we are not only building multi-skilled hyperautomation teams but also investing in a platform where multiple technologies work together in a single process or user journey: Hyperflow. Here, we are working on a ‘composable’ architecture where components are highly reusable. The motto here is ‘build once, reuse many.’ Within ABN AMRO, we already have several examples where we are implementing this at a large scale.