Large Blue Prism environments with more than 300 Digital Workers are becoming more and more common. As these environments grow optimizing becomes critical. Optimizing solution designs, data retention, archiving, database maintenance... All of these things need to be running well.
Until recently the biggest issues we would see were mainly due to the technical architecture. Now as environments with more than 100 Digital Workers become far more common we are seeing very solid technical environments where the performance problems lie with the solution designs. One of the biggest issues is using Item Tags for data instead of classification. Combine that with another issue, solutions that cause items to be retained for extended periods in Work Queues, and you have a recipe for slowness because of the queries needed to run Get Next Item.
Why should I care when I'm only running 10 Digital Workers? Following design best practices may seem like a bit of overkill at the beginning but as things start to scale and grow due to your automation genius you will be glad you did. Create a Design Authority to insure design best practices from Day 1. Blue Prism environments can grow and become very critical in the blink of an eye. Going back and updating automations months or years from now will not be trivial, particularly when there is a large pipeline for new automations. Organizations will not want to allocate development resources to rebuild existing automations.
Forgive me if I am preaching to the choir but I see this everyday. I don't want to see relatively small RPA programs become overwhelmed.
------------------------------
Steve Waters
Platform Consultant
Blue Prism Professional Services
America/Chicago
------------------------------
#BPtechtips
click the hashtag to explore more helpful content like this