Anti-money laundering compliance
Changes to government regulations can affect many business operational systems, and none more so than the banking and finance sectors. With New Zealand required to align with international commitments to anti-money laundering, Optimation was called upon to assist this financial institution to make the necessary changes to aspects of its systems. Working with the Microsoft technology stack, and including Reporting Services, our developers fitted into an existing client/vendor team to bolster outcomes. A recent release to Go Live confirmed the success of the project within the time constraints required, and we continue to support the team with further enhancements and user-driven change.
Application consolidation and enhancement
This bank had a multitude of small applications that were essential for use by the customer service staff for a range of calculators, tools and miscellaneous services. Due to major changes within the bank it was necessary to review and assess these for consolidation or retirement. The tools were a mix of Microsoft technologies working to standalone databases. Optimation led the programme of work from a technical perspective as well as providing the project manager. The outcome was extremely successful. As well as ensuring the tools were fully supported, some changes and updates were also made to improve functionality and security, and the changeover in operations was achieved without incident.
Enabling better customer service
Core transaction system support
Optimation has been providing support to this bank's core transaction system for many years. Recently, with a component of the solution reaching end of life, the bank reviewed the system components and, with Optimation's assistance, determined that by developing a Java-based component, the system could do away with the problematic component. Working closely with the bank and its major vendor partner, Optimation designed, developed and tested the solution, which was subsequently implemented successfully. At the same time, we identified some performance improvements, and were able to develop and implement these simultaneously, meaning that only one release was required instead of two.