Platform Migration

Platform migration - Insurance Sector

An Overview: The Customer

The Customer is one of the largest Insurance providers of the LATAM region. The company provides both general and life insurance products. The customer has a home-grown ecosystem of applications to serve its needs. The ecosystem includes the Core Insurance management platform called Tronador as well as 46 satellite applications that manage other related business functions.

Key Challenges
  • The landscape was a mix of packaged and mostly in-house developed applications
  • There was a marked absence of an enterprise Integration platform which is a must for a large financial services organization.
  • The Tronador platform and other applications exhibit excessive use of DB Links for integration which leads to performance and maintenance issues subsequently.
  • The in-house team had Strong domain skills and knowledge base. However, Knowledge is compartmentalized leading to excessive dependence on key personnel, which was a risk.
  • The environment was a mix of different platforms mostly oriented towards Oracle.
  • The lack of processes induced risk in terms of compartmentalization of knowledge
  • It was important to evolve a company-wide architecture and technology standard to reduce Total Cost of Ownership of solutions
  • The Forms components operate in character mode and have been migrated from Version 3 of Oracle Forms. As a result many of the features available in Version 4.5 and above have not been used. E.g. the generation of Lists of Values was done using programs and not through LOV constructs in the forms.
  • The Cobol components form the back end and do not have any user interface of their own.
  • The forms front end makes direct system calls to the COBOL program. The Cobol Programs include embedded SQLs for database interaction.
  • The ecosystem of satellite applications interact with Tronador using some APIs and for the most part using DB Links.
  • The database of the core application does not have any Referential Integrity constraints and therefore Referential Integrity is also maintained through programs.
  • There was practically no technical or architectural documentation of the system.
  • The satellite applications were developed using a number of different technologies. While many of the application have been developed using Oracle Forms 6i, several others have been developed using ADF faces.
  • The online Transactional part of the system comprised of approximately 10% of the forms, COBOL programs and tables. The rest are used for batch processes, reporting purposes as well as static data management.
  • A significant number of tables in the database are used for interfaces with satellite applications
The Solution:
  • Distributed, multi threaded and modular applications is provided
  • Service oriented and distributed applications to leverage existing and future hardware resources and achieve lower TCO.
  • It is important to make the solutions more vendor and platform independent to conserve options and reduce future expense.
  • All New satellite application and reporting applications developed using portlet frameworks.
  • A flexible architecture with ability to distribute applications and database to multiple servers.
  • Automatic fault tolerance at application and data level
  • N-tier architecture using LINUX windows servers and browser based client interfaces.
  • Utilization of shared LAN/WAN with ability to firewall backend servers.
  • Production access to staging environment for user pilot trials and training.
  • Completely Service Oriented architecture (SOA) with the possibility of seamless addition of multiple types of clients such as Web front ends, mobile devices etc.
  • Database was normalized to remove data redundancy and proper foreign key concepts.
Business Benefit:

Migration of data to the new schema without hindering the ongoing business processes.

  • With SOA the maintenance costs and risks were reduced significantly.
  • Automatic fault tolerance at application and data level ensured 24 hour * 7 days a week access and no data loss.
  • Dramatically reduced future integration needs.
  • Flexible architecture providing the ability to distribute applications and database in a distributed or centralized manner based on client requirements
  • Ability to grow to support increased volumes of users and data
  • The speed of system increased dramatically
  • Total Scalable Architecture.