Migration from a legacy decision engine

• RinggitPlus had been using a decision engine from a large vendor for several years
• The solution wasn’t flexible enough, it was technologically out-of-date & required support from the vendor
• As a consequence, it had been significantly hindering RinggitPlus business growth. Moreover, it was very expensive

Why has RinggitPlus chosen TaranDM

• Tremendous flexibility for the business users & risk managers. No dependence on IT/engineering
• Modern technology stack. Decisioning logic versioned, archived, timestamped, attached to specific user & can be easily deployed or roll-backed
• IT security & compliance aspects. TaranDM runs on client’s infrastructure (cloud/on-premise). Vendor doesn’t store or have access to any production data
• Great references from the existing clients

Migration scope

• 2 strategies (credit card, personal loan)
• 3 stages (pre-bureau, post-bureau, offer optimization)
• Close to 50 policy rules
• 5 scorecards
• 8 decision trees/decision tables

Implementation approach & highlights

• The RinggitPlus was concerned that the migration will take as long as the initial setup of the legacy engine (> 6 months)
• However, the design of decisioning strategies in TaranDM is significantly more efficient & flexible than in traditional decision engines. For example:
• Long decision trees are replaced with decision tables, which are easier to prepare & maintain
• Scorecards can be uploaded in one click, no need to manually configure binning and transformations
• Decisioning logic shared by multiple strategies can be easily re-used via so-called components. No copy pasting or manual re-creation is needed
• Ultimately, the implementation has been successfully finished within ca 2 months, from the very start of the project to migrating 100% of the traffic through TaranDM