Community Blueprints

 View Only
last person joined: 3 days ago 

Find inspiration with tried and tested automation use cases, submitted by the community members who deployed them.

Banking Card Cancellations

  • 1.  Banking Card Cancellations

    Posted 10-03-2023 09:59
    Community Blueprints are tried-and-tested examples of automation projects, created by our community members. You can submit your own project to the Blueprints library here.


    Cancelling Banking Cards


    Which industry did you deploy this use case in?

    • Financial Services


    Which functional area / department within the organization benefitted most from this automation?

    • Customer Service


    Which SS&C Blue Prism tools did you use?

    • SS&C Blue Prism Enterprise


    Describe the problem your automation aimed to solve

    Banks have different types of cancellation- Debit, Credit, Bulk, Corporate

    During Covid, there was a large increase in card cancellation requests made from different regions. The requests were so high that the team were not able to meet their SLA. 

    The cancellation process involved downloading a set of documents; verifying the card details; cancelling the same & updating the database with set of details. As this was observed to be a repetitive task, it seemed to be ideal for automation, rather than hiring a team.


    Provide a brief, step-by-step outline of how you set up your automation

    Discovery

    Our initial step started with understanding the requirement. We asked the business to cancel a couple of cases manually to get an end-to-end understanding of the process. It wasn't enough to get a perception of the applications & the process, we also had to identify the differences in the procedure for different types of cancellations in different regions. All the interpretations were mapped into a Visio flow to plan our approach.

    Design

    The Visio map was ready but the business needed solution to be used for 5 different regions. Time was critical; the solution had to be in place as quick as possible. The Solution Design for this process helped me mark the differences in decision making of the bot across types & regions. As the process involved web applications, mainframe applications, Excel & Word documents, it was a complex process.

    Build

    Multi-bot architecture was the final plan of implementation with some basics to be taken care of:

    • File Locking
    • Case Locking
    • Differentiate cases by pushing data in different queues
    • Completion Mail/Termination Mail specifications
    • Application Credential Management
    • Exception Handling Specifications
    • Startup parameter management (Process Level)

    We divided the process into 3 major parts: Loader Process, Main Process & Reporting Process

    Loader Process
    Picks all the cases & lined up in the work queue with required information for the main process to run.


    Main Process
    Interacts with the web, mainframe & MS Office applications; processing all the necessary business rules. 

    This process was designed in such a way that it could be run on 5 different bots at a time to process all 5 regions at once.


    Reporting Process
    This was a general process which did reporting for all the bots, with regards to automation rate.

    QA

    We started testing the process in chunks & also planned to deploy in chunks/phases. Initially we faced some challenges but we rectified the code & tried to get a consistent solution.

    Deployment

    As mentioned above the deployment was done in phases. The bot readiness responsibilities such as- Setting up the business applications on Production Bot, confirming the credentials, synchronizing the team mail box, etc. were taken care by me.


    What were the main challenges you faced during this project, and how did you overcome them?

    As an RPA developer, I think the common challenge for the automation team is to gain confidence & trust of business on the solution provided to them. 

    Also, other than that faced several challenges like:

    • Downloading of file was successful but the name used to be a random one; identification of the correct file for that particular case id.
    • As the deployment used to happen in phases not every time the integration would go smooth.
    • Mainframe commands used to be faster than the applications; that synchronization also was a great challenge.


    What was the impact of your project?

    The business had team of 30 working on this process, who were not meeting their SLAs due to the increased load. Now, they are a team of 8 who work to audit the reports shared by the bots. The business had planned on hiring 20 FTEs per region to accommodate the increase in requests so, ultimately, this resulted in a good FTE return. This process continues to be run today.


    Additional information

    When you get an automation request, remember some key points-

    • Design the solution on a Visio or paper to get a vision on the final solution (SDD) & then start the development.
    • It is not always necessary that the automated solution & as-is solution is same. Understand the process & try to make it easy for the bot.
    • Consider the risks involved, while dealing with critical/PII data.
    • Explore additional tools or ideas wherever required like some of the calculation loops can be skipped if we create an excel template with a set of formulas & lookups.



    Like this Community Blueprint? Be sure to click the "Recommend" button to reward the author! You can also ask the author questions about this Blueprint by clicking "Reply".



    ------------------------------
    Shreya Satish Udagave
    Technical Architect | Associate Consultant
    Northern Trust Operating Services, Pune
    Email- shreya14khot@gmail.com
    ------------------------------