Inspiration
One of our customer was having issue by having a transaction monitoring on multiple systems
What it does
We built a tool which can monitor the transactions in real time and near real time by integrating with Hbase, Kafka queue, Eventhub and external database. This tool will find the fraudulent transactions based on the business rules defined in the system then disposition the record as a control break case in Pega. We are able to process 15000/sec and 17 million records in 6 hours.
How we built it
We built system using the Pega OOTB rules like dataflows, strategies, decision strategies and integration connectors to external data repositories and event management systems. Runs on realtime node.
Challenges we ran into
Here we had a requirement to have a portal where citizen developer should be able to change business rule in easy way. Pega OOTB rule delegation for decision tree and decision table was not so flexible for citizen developers to modify at runtime. Here we built a component like configuration management system where that portal will have all business rules to be modified with ease.
Accomplishments that we're proud of
Simplification and automation of the end-to-end control break process by leveraging a single unified solution (Pega) versus multiple solutions Automated creation and escalation of cases for identified breaks Remediation of processes and policies that caused breaks Visibility into breaks through dashboard reports Decrease in regulatory failures Processing speed was 15000 records/sec on single node.
What we learned
We proved Pega is highly flexible on data processing along with business process flows.
What's next for Control Monitoring Systems
We are planning to build a risk monitoring framework for BFS customers
Built With
- bre
- eventhub
- hbase
- kafka
- pega
Log in or sign up for Devpost to join the conversation.