Written by Scott Craig|Posted on July 21, 2020
As a major financial institution, effective receipt and processing of loan applications is an essential part of an organization’s ability to keep up with its growing business. For years, our client, a multinational financial institution, had been relying on legacy mainframe applications to support their loan application process, which, over time, became limited in functionality, expediency, and unable to scale with the increasing amount of data quality that was required. Furthermore, because of its antiquated platform, it was becoming harder and harder to find developers to support and maintain the system.
As a result, our client decided to upgrade its mainframe applications to web applications.
Initially, our client contracted another company that underperformed on the project, generating errors and critical delays that required them to seek out a new team to complete the project.
The chosen solution was a system that would allow lending operators and credit officers to follow all the credit approval processes, from the beginning of a loan application from the prospective borrower, through to the last point of approval to fund the applicant. The process needed to start from the collection of data from the loan candidate, along with relevant relative’s data, through to the time at which the mortgage was granted.
Our client wanted to keep its core apps of the business in the AS400 and mainframes system for reasons of continuity and protection, but the rest of the systems needed to be revamped, starting with standard back-end interfaces and three-tiered architectures.
In order to achieve the goal of moving all of our client’s applications to the web-based solution, it was necessary to create an architecture and programming standard based on Microsoft .NET platforms and XML messaging between back-end and front-end interfaces, as well as to integrate different and disparate applications used throughout the group seamlessly.
A team of 10 was configured to execute the project, which included a project manager, team leader, architect/DB expert, senior business analyst, (5) senior .NET developers and a senior web designer/UX expert.
The project was divided into modules that followed the logical flow of the application. Milestones were associated with those modules or their respective sections. The first version was released three months after the project had started and provided the first and most complex step of the mortgages tracking process. The main purpose of this version was to perform QA on a real-world data sample and evaluate the tool and its User Experience (UX). The second version was released after six months and was deployed immediately for use.
After six months, a fully functional version was deployed for immediate use and regionalized to several different countries in which the financial institutions maintains operating facilities.
Based on the further discovery of the commercial loan officer’s daily work requirements, a third version of the product was released, which further improved both the UX and performance.
This loan application product continues to be used to this day.
Kirkland, WA, USA