Emirates NBD, via Synechron · 2024 – present
Decision Management System
A bank’s in-house platform for deciding who is eligible for a loan, a credit card or an overdraft.
The system
Every application for a personal loan, credit card or overdraft has to be checked against the bank’s eligibility rules. The Decision Management System is the platform that runs that check. The rules themselves are written and maintained in their own application, the Business Rule Management System (BRMS).
This is a transformation project: the platform is being built in-house to replace the third-party tool the bank has used for these decisions. It is already live for multiple products, with more of the rollout due over the next couple of months.
My part
I lead four of the engineers and work on the BRMS myself. I also handle the non-functional requirements, such as memory use and security.
- BRMS: I designed the configuration panel from scratch, including the flow-builder canvas where nested risk-eligibility models are composed.
- Memory: I virtualised the heaviest UI modules. Memory use during large calculations fell by 35%.
- Security: I set the frontend security baseline for public and private APIs, to meet the bank’s compliance requirements.
The hard part
One rule set holds several rules, and each rule is a chain of if, else if and else branches built from AND and OR conditions. The interface has to let someone write all of it without losing their place.
- Rule sets: a single rule set can hold several rules.
- Rules: each rule is a chain of if, else if and else branches.
- Conditions: one to a row. The first row opens the branch, and each row after it joins with AND or OR.
- Actions: each branch closes with a then block, the action to take when its conditions hold. One block can assign several values.
- Drafts: work can be saved as a draft before it is finished.
- Screens: the same editor fits a phone, a tablet and a desktop.
Rule 1
if
- Income meets the threshold
- andAge is within range
then- eligible = Yes
else
then- eligible = No
- reason = Criteria not met
Rule 2
if
- Employer is on the approved list
- orSalary is transferred
then- limit band = Standard
else if
- Existing customer
then- limit band = Lower
else
then- decision = Refer for review
The shape of one rule set. An illustration, not the bank’s rules.
- −35%Memory use during large calculations
Rule authors
Business teams who own the eligibility rules
write and maintain
BRMSMy area
Flow-builder canvas for nested eligibility models
rules
Decision engine
Checks each application against the rules
Applications in: personal loans, credit cards, overdrafts
decision
Eligible, or not
The answer the bank acts on