TransInsure - Are legacy constraints a barrier to implement Digital Insurance
Upcoming SlideShare
Loading in...5
×
 

TransInsure - Are legacy constraints a barrier to implement Digital Insurance

on

  • 120 views

Legacy constraints are one of the reasons of delay to implementation a Digital Insurance strategy. Generally the vision is that mobile and web portal solutions need to be integrated with the Back-End ...

Legacy constraints are one of the reasons of delay to implementation a Digital Insurance strategy. Generally the vision is that mobile and web portal solutions need to be integrated with the Back-End legacy systems to prevent inconsistency of data.

Statistics

Views

Total Views
120
Views on SlideShare
120
Embed Views
0

Actions

Likes
0
Downloads
4
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

TransInsure - Are legacy constraints a barrier to implement Digital Insurance TransInsure - Are legacy constraints a barrier to implement Digital Insurance Document Transcript

  • Are legacy constraints a barrier to implement Digital Insurance? Legacy constraints are one of the reasons of delay to implementation a Digital Insurance strategy. Generally the vision is that mobile and web portal solutions need to be integrated with the Back-End legacy systems to prevent inconsistency of data. If we accept this constraint, we will never implement Digital Insurance as legacy problems and constraints are not easy to solve and needs most of the time a full redesign of the legacy system environment. There is a way out of this problem. The implementation of an Enterprise Service Bus and a transactional database in a cloud are the basis of integrating the mobile and web functionality with the back-end legacy systems. This view needs adaptation as it changes the dominant position of the legacy systems which could be a bridge to far for many people in the organization. However it is a way to decouple the IT components and a start to implement a more agile IT system environment. How does it work? The implementation of Insurance services on mobile devices connected to a transactional database in the cloud, connected to your legacy back end needs a state of the art IT design developed by experienced (in Digital Insurance) IT architects and designers. These architects and designers are by default not available in the organization as IT is back-end focused, the available IT architects and designers in the IT organization are lacking experience and knowledge in this field. They have to be involved and educated but you need knowledge and experience from outside to define an agile, scalable and sustainable Digital Insurance solution architecture. In between the mobile application and the legacy systems a transactional database will be implemented containing all data, necessary to deliver products and services through the mobile applications. Data components included are leads, customers, distributors, quotations, policies, claims, cases, documents, payments, messages, calendars, etc.. The transactional database contains real time data and is available 24x7. The mobile and web applications are using and feeding the transactional data. Page |1
  • Are legacy constraints a barrier to implement Digital Insurance? The legacy systems will be integrated through an ESB which will transport and convert data to and from the legacy systems. The connection to the legacy systems does not have to be a real time connection as the transactional database will be 80%-90% accurate depending on the usages of the mobile and web applications. The more the mobile and web applications are used by all customers and partners the more accurate the transactional database will be with less concerns about a small percentage of data fed by the legacy systems. The legacy systems will still be the single source of truth as 100% of the data is stored in these systems for regulatory and compliance purposes. The preference is to store the transactional database in a cloud outside the company’s datacenter to prevent that this will be another obstacle. Cloud computing is safe when implemented by experienced and reliable vendors who will help to convince regulators on the security and compliance topics. In a later phase cloud computing should be a part of the data center strategy and this (temporary) cloud serving the transactional database will be integrated in that strategy. It is of course easy to write this approach down in a few sentences, the architectural design and implementation is more complex but with the right mindset this can be implemented in 3-6 months. Are legacy constraints a barrier to implement Digital Insurance? TransInsure Consultancy Paul de Bruijn Singapore, October 30, 2013 First edition V1 © TransInsure © Paul de Bruijn www.transinsure.net www.pauldebruijn.com www.digital-insurance.net Page |2