Downloaded 65 times
Uploaded byMuleSoft
Becoming a Connected Insurer With API-led Connectivity
The document discusses the transformation towards becoming a connected insurer through API-led connectivity at Sagicor Life Insurance Company. Key business needs include improved customer engagement and empowering agents, with challenges presented by legacy systems. The proposed solution involves modernizing API services for mobile consumption, establishing governance, and utilizing an integration platform for enhanced claims management.
More Related Content
Similar to Becoming a Connected Insurer With API-led Connectivity
![cloud enabling tecnologies , unit ii [cc]](https://cdn.slidesharecdn.com/ss_thumbnails/unit-ii-240619035331-08614007-thumbnail.jpg?width=640&height=640&fit=bounds)
Becoming a Connected Insurer With API-led Connectivity
- 1. 2 Becoming a ConnectedInsurer with API-Led Connectivity Patricia Hines, CTP Industry Solutions Director, FS&I MuleSoft Teri Townsend, MBA, PMP Vice President Technology Sagicor Life Insurance Company Alex Sherry Senior Solutions Consultant MuleSoft
- 2.
- 3. 4 Business needs • Richercustomer engagement • Empower agents/partners
- 4. 5 What’s holding usback • Legacy services for internal consumption only • Do we do nothing at all? • Rip & replace core business capabilities? • Change is dangerous - Facebook, Microsoft, Dropbox, Google, Adobe
- 5. 6 What’s the solution • Expose services • Governance • Modernized API for mobile device consumption
- 6. 7 Integra)on Pla-orm Anypoint Studio HYBRID Accounts Database JDBC Orchestra3on Before Modernization Ac3vi3 REST Ac3veMQ JMS Drools Rules 3rd Party Registry HTTP WEB Service (SOAP) HTTP/REST Connector JMS Connector Drools Connector Database Connector HTTP/REST Connector
- 7. 8 API Gateway Integra)on Pla-orm Anypoint Studio Claims API API Manager HYBRID Accounts Database JDBC Orchestra3on Web Services Consumer After Modernization Ac3vi3 REST Ac3veMQ JMS Drools Rules 3rd Party Registry HTTP WEB Service (SOAP) HTTP/REST Connector JMS Connector Drools Connector Database Connector HTTP/REST Connector
- 8.
- 9. 10 Legacy Web Servicefor Claims The Claims department ini3ally implemented a web service to expose func3onality
- 10.
- 11. 12 RAML for DelightfulAPIs Claims dept designed a RESTful API and leveraged the mocking service to engage API consumers prior to implementa3on and allow them to test out the service.
- 12. 13 Modernized Claims Service The “APIKit Router” handles incoming RESTful API requests and routes to the appropriate flow below The “Web Service Consumer” provides a drop-‐down configura3on to access a web service. The datamapper components translate the web service call data into RESTful JSON responses.
- 13. 14 API Governance Governing who can consume the API, at what rates and by what authoriza3on mechanism
- 14.
- 15. 16 API Gateway Integra)on Pla-orm Anypoint Studio Claims API API Manager HYBRID Accounts Database JDBC Orchestra3on Web Services Consumer After Modernization Ac3vi3 REST Ac3veMQ JMS Drools Rules 3rd Party Registry HTTP WEB Service (SOAP) HTTP/REST Connector JMS Connector Drools Connector Database Connector HTTP/REST Connector
- 16.