ProSafe credit reference agency retrieves data from bank and other credit providers where customers have missed payments or gone into default. The data is very sensitive and fed directly into a Blue Prism work queue via a web service. Blue Prism process must process the data within 4 hours. The Blue Prism solution runs continuously and each case takes approximately 30 seconds to process. It is expected that an average of 10,000 cases per day will be required and up to 10
Blue Prism robots are available.
The Blue Prism solution is sown below:
Answer : ADF
MedBank have recently introduced a new Credit Card platform Cred+. There is a requirement to migrate account and card details from the existing banking platform PCBS on to Cred+.
Account IDs of the cases requiring data transfer will be held on a SQL database. The requirement is that, for each account ID specified on the SQL database, the following data must be read from the PCBS application and input into the Cred+ application:
-> Account ID
-> Product Type
-> Name
-> Address
-> Date of Birth
-> Card PAN (Primary Account Number or credit card number)
-> Card Issue Date
-> Card Expiry Date
Once the data has been successfully input into Cred+ the correct record on the SQL database will be updated to indicate data transfer is complete. All work queues will be encrypted, however due to the sensitivity of the data, MedBank insist that a single robot account does not have access to both PCBS and CRED+ systems.
The following high level design has been proposed:
Answer : BE
Pacific West Banking has a payments process that automatically receives pending payments from multiple regions into their payment system (Paytex).
Paytex contains a queue of cases awaiting payment. When processing the case manually an agent must use two other systems, the core banking system
(DataPlus) and online account checker (FireWire).
The manual processing must perform the following steps:
-> Open the next case where the status is null in Paytex
-> Set the status to "In Progress" in Paytex
-> Validate source account in DataPlus
-> Confirm source funds in DataPlus
-> Check for fraud flags in Paytex
-> Confirm recipient IBAN details in Firewire
-> Perform payment in Paytex
-> Update case in Paytex queue. Add payment confirmation number to case and set status to "Completed"
-> Where cases cannot be fulfilled due to validation errors (e.g. invalid account details, insufficient funds, suspected fraud etc.) the customers will be contacted by the agent to resolve.
A proposed Blue Prism solution with the following properties has been created to automate the payment processing:
-> There will be one Blue Prism process that will perform the steps described above.
-> Where a case is an exception the status will be set in Paytex to "Manual Review" in order that the manual team can pick up the case from Paytex and contact the customer and conclude the case.
-> It is anticipated that to meet the SLAs of the expected volumes up to 5 instances of the Blue Prism process will be required to run concurrently.
-> A Blue Prism work queue will be used to host the payments. The queue will be configured for only 1 attempt per case and the key will be (region) & {source account number}.
The process will be started by the scheduler at 06:00 and will stop at 05:50.
Answer : BCD
VivaBank have an account closure process that can take up to three days to close an account. All requests within the bank"™s core system to close an account take place overnight during batch processing. There are two scenarios:
Answer : CD
The following Object Design has been created for a mainframe banking application.
Answer : BE